I was just wondering if anyone else has seen this behavior.
I haven't had the cycles to do much to further characterize
the issue, so I'll have to describe it in terms of my
application.
Configuration
-------------
1. Three machines, two connected to an Ethernet hub.
2. The one *not* connected at this point is running XP.
3. In my case, the other two are Linux machines.
4. On one of the Linux machines, fire up Ethereal (or another
network capture program)
5. Static IP addrs all around, all on the same subnet (not that
this matters for broadcast traffic)
Steps to produce failure
------------------------
1. Boot the XP box w/o a network connection.
2. Plug in the network cable. Observe that the interface seems
to work ok (i.e. ping one of the other boxes, telnet to one
of them, etc.)
3. Fire up Ethereal on the XP box and verify that both Ethereal
sessions are seeing the same traffic on the network.
4. Send a UDP broadcast out on the net from the second Linux machine
(I don't think the platform of the sender matters, but that's
what I'm using. In my case, it's a BOOTP/DHCP request, but to port
5067, rather than 67. Observe that the XP box that wasn't connected
when it booted doesn't receive the broadcast, while the other machine
running Ethereal does.
If the XP box is booted with a link, it works fine.
This looks like an XP bug to me, as it has been seen on several
machines with different Ethernet chipsets. I haven't been able to
find mention of this issue, though, in the MSKB or using Google to
search USENET and the web.
Has anyone else seen this behavior (say, if you were running a
DHCP server or some such on your XP box)?
|
Similar Threads
Linear Mode
