Bug 4557 – Ethernet bridge fails after a couple of minutes

Bug 4557 - Ethernet bridge fails after a couple of minutes

Summary:

Ethernet bridge fails after a couple of minutes

Status:	RESOLVED DUPLICATE of bug 3660

Product:	SB 2/3
Classification:	Unclassified
Component:	Misc
Version:	70
Platform:	PC Windows XP

Importance:	P2 major (vote)
Target Milestone:	---
Assigned To:	Richard Titmuss

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2006-11-30 13:49 UTC by Chris Owens
Modified:	2008-12-18 11:40 UTC (History)
CC List:	0 users

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 Chris Owens 2006-11-30 13:49:43 UTC

Sometimes it fails quite quickly, but always within 3 minutes on my system.  It looks like it's still passing a packet or two, actually, but at a snail's pace.

I typically test this function by connecting a wired-only SB2 or 3 to the ethernet port of a connected player.  In this case it manifests by performing normally for a brief period and then freezing.  

Eventually the player will turn itself off as it would normally in the case of a network outage.

Comment 1 Chris Owens 2006-11-30 13:51:06 UTC

Note this also affects Transporter firmware 25

Comment 2 KDF 2006-11-30 16:50:51 UTC

I take it this is FW70/25 specific?  I'm having no trouble with FW69/24

Comment 3 Chris Owens 2006-12-01 11:08:40 UTC

Richard has been able to reproduce using an SB3, but not with a laptop(!)  I definitely did not see this bug on fw69 or tr24, although there's a possibility of course that it just takes longer for the failure to manifest.

Comment 4 Richard Titmuss 2006-12-11 02:58:54 UTC

Chris, I think we have recreated bug 3660. I'm using a Linksys WRT54GS router, it turns out that without wireless encryption or with WEP the bridging works fine, but with WPA or WPA2 the bridging is intermittent. I will looking at this in more detail now, to see if it is easy to fix for the 6.5.1 release.

Comment 5 Richard Titmuss 2006-12-12 02:53:32 UTC


*** This bug has been marked as a duplicate of 3660 ***