Bugzilla – Bug 8193
SBR with bridging enabled prefers connecting via wired connection instead of wireless, though wireless is preferred for me
Last modified: 2008-05-20 07:02:59 UTC
I've used the UDAP tool to enable bridging on my SBR, however, I've run into a problem. I'm using the SBR to bridge my Dish VIP-622 to my network. Bridging works fine if the LAN cable is unplugged from the SBR while it is powering up. The SBR powers-up (after being unplugged from power, not just the light being off) and it looks for the wireless network, connects to SqueezeCenter and is fine. I can then plug in the LAN cable and my VIP-622 gets network connectivity. However, if the ethernet cable is plugged-in during power cycleing, the SBR tries to connect via LAN instead of wireless, resulting in both the SBR and my 622 being without a connection. My SBC still sees the SBR, but the SBR cannot connect to a music source since it's not really on any network. I've set bridging=1 and interface=0 (using the UDAP utility), but the SBR still wants to try and connect via the wired connection if it's plugged in to something. My SBR stays plugged in to power all the time (as most folk's do, I imagine), however - last night when I left my 622 connected to it with everything working (SBR connected to network wirelessly and 622 bridged through SBR), when I woke up, the SBR was trying to connect via LAN again. The only thing I can think of is that my wireless single dropped for a split second during the night and the SBR reverted back to trying to connect via a wired connection, just like it does when I power it up with the wired connection connected. My SBR is on the fringe of my wireless network, mostly due to heacy congestion in my neighborhood, so it does not get the strongest signal in the world, but plenty strong enough to stream 256kbps mp3s without ever missing a beat (not much of a bandwidth requirement for me). Has anyone else seen this behavior in their SBR? Could this be a bug. I have the lastest 7.0.1 release software and associated firmwares running on all hardware (release date was 14 May, I think).
I use the SBR to bridge to my networked printer. I have no problem leaving the wired side connected on restart. However, the Net-Udap plugin is not supported so no target can be assigned, nor is this a bug. Now, one thing to try is to set up the receiver using the Duet controller, THEN connect to the network wired and use Net-UDAP to set the bridging param. For me, this gives me the right settings. Using Net-UDAP from factory reset doesn't do the trick.
Thanks, I had tried that a couple of times, without success, but I think I did not take it far enough... Trying one more time, I gave the SBR a hard reset (held down button for 10 seconds, or whatever it took), stopped SC so UDAP could connect (I prefer this method to using the button) then reconfigured with SBC, ensured it worked, then connected with net-UDAP with the following commands in net UDAP: discover configure 1 set bridging=1 save_data reset I restarted SC and it worked. I've powered-down the SBR several times with the LAN cable plugged-in now; it still connects via wireless, and my bridged hardware now has a reliable connection! Thanks for the proding to get me to do this the right way. I've changed the status to "INVALID" since, as you said, this isn't a bug.