I see the exact same symptoms here. 

On a simple 11b network (essentially what I wrote about in
http://www.bgnett.no/~peter/pf/en/wireless.simple.html) where I have
two freebsd, one openbsd and a windows box connection quite happily,
the squeezebox manages to associate, but simply will not communicate
via TCP/IP.

I've spent a few days on and off trying to get it to connect, going
through the ususal debugging steps (assigning a static ip address,
trying unencrypted), but the only way I could make it work was to plug
it into the hub in the server room (not an option for actual use). My
dhcp server never even saw the requests from the squeezebox.

One weird thing happened today. After a factory reset, it appears that
my dhcp server is finally seeing the requests now:

Dec 11 21:00:22 skapet dhcpd: DHCPDISCOVER from 00:04:20:06:16:83 via
ath0
Dec 11 21:00:22 skapet dhcpd: DHCPOFFER on 10.168.103.9 to
00:04:20:06:16:83 via ath0

but the squeezebox is claiming that it gets assigned addresses in the
169.n.n.n (IANA blackhole) address range. 

Buying a different router is NOT an option, but my OpenBSD 3.7-current
could probably do with an upgrade.

Now if I find the box and start thinking about returning the unit, will
it start behaving?


-- 
pitrh
------------------------------------------------------------------------
pitrh's Profile: http://forums.slimdevices.com/member.php?userid=2750
View this thread: http://forums.slimdevices.com/showthread.php?t=18938

_______________________________________________
Discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss

Reply via email to