Jason, Thanks for figuring this one out, I had almost exactly the same problem with a Linksys WRT54G (using a relatively old Sveasoft firmware) and the Squeezebox, though I have the most basic wireless setup (no WDS).
The Squeezebox would associate with the AP, but detect the Slimserver as being at the IP address of the AP itself, rather than the server hosting it. This problem also showed up in Snort logs whereby wireless traffic appeared to originate from the AP's IP, not the wireless client IP's. I had overlooked the loopback setting in the 'Administration : Management' section when first setting up the AP, and was previously at a loss as to how I could correct this strange behaviour. Thanks again, Tom On Fri, 18 Feb 2005 21:26:39 -0500, Jason Temple wrote: > Greetings all, > As it turns out, this was not a SB/slimserver problem at all, rather > an issue I had with my particular WLAN setup. For those who are > interested the problem had to do with my linksys wrt54g settings. I've > been running the Sveasoft firmware (ability to create a wireless mesh with > one uplink with multiple wrt54g units a.k.a WDS) on two+ wrt54g's for > quite a while now, one the uplink and AP, the other just an AP, bridged > wirelessly to the uplink unit. I had the loopback device enabled which > makes my internal devices appear as external devices (happened to be a > default that had not bit me before now). After disabling that, everything > is as it should be...BTW, that Sveasoft firmware rocks! For $50 each, the > wrt54g's act as AP/uplinks, needing only power, and to be within > (adjustable) range to communicate with the main uplink (hooked up to the > internet). Highly recommended...ok, that's quite enough. > > jas _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
