Bug 8641 - With bridging enabled, player uses DHCP server on ethernet interface
: With bridging enabled, player uses DHCP server on ethernet interface
Status: RESOLVED INVALID
Product: SB 2/3
Classification: Unclassified
Component: Wireless
: unspecified
: PC Windows XP
: -- normal (vote)
: ---
Assigned To: Squeezebox QA Team email alias
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-02 19:53 UTC by Andy Grundman
Modified: 2008-07-07 08:52 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andy Grundman 2008-07-02 19:53:33 UTC
Wifi w/ DHCP <---> TP <-eth-> Router w/ DHCP <-eth-> SB3

I setup a Transporter in bridged mode, and there were DHCP servers on both interfaces.  TP got an IP from the DHCP server on the ethernet interface instead of the wireless interface.  The SB3 behind the bridge managed to get an IP from the wireless DHCP server, though.

I had to assign a static IP in order to connect the TP to SC over wireless.
Comment 1 Sean Adams 2008-07-07 08:28:01 UTC
This is not a Transporter bug. If you have two DHCP servers on your LAN then a client could get an IP from either one, and it doesn't matter which side of the bridge it's on.

You need to disable one of the DHCP servers. Also you may not have your network set up properly if you are using multiple access points or routers. It's unclear from your description exactly how things are hooked up. You can visit our forums if you need further help.
Comment 2 Andy Grundman 2008-07-07 08:52:10 UTC
Fair enough, just noticed this while testing a bridged config with a spare access point I had laying around that happened to have a DHCP server enabled.  It just seemed like DHCP should only request on the wireless interface when bridged instead of all interfaces.  Certainly a minor bug and easily worked around though.