Bug 7676 - SB2 uses incorrect source IP address after network link disconnect
: SB2 uses incorrect source IP address after network link disconnect
Status: VERIFIED WORKSFORME
Product: SB 2/3
Classification: Unclassified
Component: Slimproto
: 86
: PC Other
: -- normal (vote)
: ---
Assigned To: Chris Owens
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-03-31 03:35 UTC by Alan Young
Modified: 2008-12-18 11:42 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alan Young 2008-03-31 03:35:59 UTC
If I disconnect the network cable from the SB2 while playing and then reconnect it a few seconds later (probably > 5s) then it fails to reconnect to SC. A power-on reboot is required to clear the condition. This does not seem to happen every time and may be a factor of the network traffic at the time or the period for which the link is down.

Using a sniffer on the SC host, I first see TCP connect request with a source IP address that is one greater than before (192.168.1.103 -> 192.168.1.104). I see the SYN and SYN ACK but no ACK.  that is, the 3-way packaet exchange does not complete. Then I see repeated SLIM discovery requests and ARP requests for SC. It very much seems like the SB2 is not seeing the replies. My guess is that it still thinks it has address 192.168.1.103.

It has not DHCP'ed for and been given the new IP address, as this is still unallocated (luckily) in the DHCP server.
Comment 1 Chris Owens 2008-04-18 08:42:09 UTC
I thought I had seen another facet of this bug, where the behavior was visible to the end user if connecting to a network with no DHCP, but I can't reproduce it.

Felix is this enough for you to look at this bug for 7.1 or should QA get an ethereal log?
Comment 2 Chris Owens 2008-06-04 16:17:33 UTC
If anyone sees this again, please re-open.
Comment 3 James Richardson 2008-07-15 14:53:15 UTC
Verified not an issue with r100