Bug 4154 - Ethernet bridging capability does not work for 10Mb only types of devices
: Ethernet bridging capability does not work for 10Mb only types of devices
Status: RESOLVED WORKSFORME
Product: SB 2/3
Classification: Unclassified
Component: Hardware
: 64
: PC Windows Server 2003
: P2 normal (vote)
: ---
Assigned To: Chris Owens
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-09-19 17:27 UTC by Alex
Modified: 2006-10-03 10:54 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 Alex 2006-09-19 17:27:59 UTC
If a 10 Mb only device is plugged into the ethernet port to take advantage of the bridging capabilty of SB2, the networking does not appear to function.

I have tried two type of devices:  a generic 10Mb hub, and an HP JetDirect EX network printing device. Neither one is able to communicate to obtain an IP address from the DHCP server on the network (a Linksys WRTP54G device).

The product spec does not specify that 100Mb only devices are supported, hence this bug entry.
Comment 1 KDF 2006-09-19 20:22:37 UTC
have you confirmed that there is nothing wrong with the cable being used? 
is it a proper crossover cable?
can you bridge with a 100Mb device?
have you stepped through setup and have you been asked to turn bridging on, or does that option never show up?
Comment 2 Alex 2006-09-19 21:08:39 UTC
If I plug in my laptop, which has a 10/100 port in the same cable, everything works - SB2 bridges. When I plug in the 10 Mb device into the router directly, everything works.

The options does not show up when the 10Mb device is pluged in. It does for the 100.
Comment 3 Chris Owens 2006-09-21 17:34:08 UTC
Ross could you try this by connecting an SB1 or SliMP3 to the ethernet port of an SB3?  I have an SB1 and a crossover cable if you need one?
Comment 4 Ross Levine 2006-09-21 18:26:09 UTC
I was not able to reproduce this with the situation you've described Chris, would you like me to try it with a 10base hub or something other than a SB1?

When I connect my SB3 wirelessly to the network, while connected via a crossover cable to an SB1, I enable the bridging option. Then once SB3 has been connected to the network, and obtained an IP address via DHCP, then I connect the SB1 (via ethernet) and it also obtains an IP via DHCP. Both connect to SlimServer without a problem. 

I'll put your crossover cable back ;) let me know if you want me to try anything else. 
Comment 5 Blackketter Dean 2006-09-21 18:59:06 UTC
Alex: can you confirm that you are using a crossover cable?  Many laptops (including all Macs) can do auto-crossover.  The Squeezebox doesn't do that, so you _need_ a crossover cable to connect to a non-hub/switch device.
Comment 6 Chris Owens 2006-09-28 16:39:44 UTC
I can't seem to reproduce this either.  Alex if you are using a crossover cable and are still having this problem, would you contact support@slimdevices.com so they can try to figure out the issue?  Thanks!
Comment 7 Alex 2006-10-03 09:22:14 UTC
I did not have the crossover cable plugged in to the device. My assumption was that a crossover was not necessary given that it was not used for a direct ocnnection and I could not find it in the documentation or product description. The fact that my laptop was working, made me issue the bug report.

Thanks for your help.

Perhaps the SB can perform the crossover if a bridging option is used, this was the ciosumers do not need "special" cables?
Comment 8 Chris Owens 2006-10-03 10:54:11 UTC
This is a hardware limitation of the components in the SB3.  We'll certainly bear this in mind for future products, however.