Bug 1302 – SB2 loses connection if ethernet cable is disconnected in bridge mode

Bug 1302 - SB2 loses connection if ethernet cable is disconnected in bridge mode

Summary:

SB2 loses connection if ethernet cable is disconnected in bridge mode

Status:	CLOSED FIXED

Product:	SB 2/3
Classification:	Unclassified
Component:	Misc
Version:	unspecified
Platform:	Other All

Importance:	P3 normal (vote)
Target Milestone:	---
Assigned To:	Blackketter Dean

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-04-03 06:34 UTC by Felix Mueller
Modified:	2008-12-18 11:37 UTC (History)
CC List:	2 users (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Felix Mueller 2005-04-03 06:34:04 UTC

SB2 is connected wireless to SlimServer, bridge mode is turned on and wired
interface is connected to a switch, hub or computer. Everything works as expected.
But as soon as the wired connection gets disconnected (ethernet cable unplugged)
SB2 looses connection to SlimServer.
Plugging the ethernet cable back in restores connectivity to SlimServer.
The problem exists whether SB2 has a static or dhcp address.

Comment 1 Felix Mueller 2005-04-03 07:25:57 UTC

If I comment out the call to lan_eth_link_is_down() in function
lan_eth_link_change() in source file config_interfaces.c SB2 doesn't loose
connection.
I doubt this is the correct solution, but it seems setting the ip address to
0.0.0.0 on the wired interface also affects the wireless interface.

Comment 2 Vidur Apparao 2005-04-03 12:20:51 UTC

Reassigning to Dean, since he's worked on this more.

Comment 3 Blackketter Dean 2005-04-04 13:31:32 UTC

I think that this _is_ the right solution.  If the link goes down, we shouldn't slam on the IP address.  Let 
the TCP timeout do its thing.

Comment 4 Blackketter Dean 2005-04-04 13:31:53 UTC

I think that this _is_ the right solution.  If the link goes down, we shouldn't slam on the IP address.  Let 
the TCP timeout do its thing.

Comment 5 Kevin Pearsall 2005-05-02 16:40:14 UTC

a customer just reported this issue as well...  will this be fixed for 6.1? 
(can a fix be checked in for people to try?)

Comment 6 Blackketter Dean 2005-05-02 20:17:14 UTC

Sorry, forgot to update the bug.  This fix is already in the 6.1 nightlies.  Please confirm and reopen if 
it's still busted.

Comment 7 Chris Owens 2008-03-11 11:28:06 UTC

This bug was marked resolved in Slimserver 6.1, which is several versions ago.  If you're still seeing this bug, please re-open it.  Thanks!