zurück zur Liste| Nachricht #467 aus Archiv der Liste ecs-t6x@2rosenthals.com |
zurück zur Liste |
|
|---|
On Thu, 03 Sep 2009 22:46:54 -0400 Lewis G Rosenthal wrote:You wouldn't see anything in there on the client machine, even if you had a dozen DHCP servers on your network.
Lewis:
Yes, otherwise I'd see it on the windowlist, right? Just the linksys providing dhcp.Which windowlist? How is your LinkSys connecting to the rest of the network?
The window list when you press ctrl-ecs.
the linksys acts as a hub. The 'internet' socket (port) is not used. From my firewall/gateway os/2 v1.1 boxI did not know that you were running OS/2 as your bastion server and not another appliance (D-Link, LinkSys, Belkin, etc.). So, do you mean that you're not running the DHCP Server service on that OS/2 box? Just trying to get a clear picture, here.
the cable goes to one of the 4 ports on the linksys. And another hub is attached to one of those 4 ports since the 4 ports on the linksys is insufficient for my needs.That's all quite logical.
As soon as I flipped that option off, the problem disappeared. That's when it all made sense. :-) It turned out that Christian had never tested against a hosts file anywhere near the size(s) of ours.I rarely have DHCP issues under OS/2. Interestingly, I happened to expose a bug in XWLAN with my whopping 2MB hosts file. There is an
Hmmm, I never noticed a problem with my 940k hosts file when I used xwLan under rc6a and static IP. But I didn' t use that option you mentioned either. Glad to hear Christian is working on a new version.
And those are all DHCP? I just can't figure out where a bogus gateway address is creeping into your configuration the first time 'round.Other than that, however, DHCP on OS/2 is fairly stable, with the
I guess I have something set incorrectly. I bet it's in the linksys, some of those screens have caused me plenty of confusion. But like I said, no problem with the other family members and their XP machines (and earlier versions of Win before that).
Yes, it's annoying. I wish there were something we could do about it, but that problem lies with GenMAC, and let's not even get into that... Roderick and Joachim are aware of the null MAC issue, as we've discussed it in the bug tracker already. The nice workaround for NetWare services using IPX is that the address may be overridden in PROTOCOL.INI. Unfortunately, the TCP/IP stack has no provision for this, of which I'm aware, causing some DHCP servers, routers, and intelligent switches to freak out (technically, though, a null MAC address, as long as it is unique - i.e., only one device with a null MAC on the network - should be treated just as any other address, simply one consisting of all zeros). Naturally, this handling is not always according to the RFC, and has become something more vendor-specific, leading to unpredictable results.Indeed. I'll be interested to hear what you find. Tell me, does your wired interface still have a null MAC address? I expect that it does.
One of the first things I checked. Yep, all zero's.
|
Abonnieren: Nachricht (Feed),
Sammelnachricht (Digest),
Index. Abmelden E-Mail an ListMaster |