Well you're asking for feedback, and a transaction with support convinced me my Duet hardware is okay. Here is my latest trip to the funny farm with my Duet.
I switched from bridged to hybrid mode on my duet to see if using infrastructure wifi would improve controller receiver interaction. I also wanted to see if I'd do something of a Nokia 770 thats sitting there doing nothing (nice SC skin, but nothing beats the ability of my tablet to freeze and reboot at random :) The controller/receiver was wirelessly connected to a Linksys WRT54G acting as access point & DHCP server. The server was wired to the WRT54G. Worked ok. I used 192.168.1.0/24, my server has a fixed address of 192.168.1.50 on the regular LAN. This DHCP server was set for 1-day long leases. Its address was 192.168.1.100 or somesuch. This was an isolated, temporary test network. After a couple of hours I decided to reconnect the Duet and SC server to my regular wired gigabit net: 192.168.1.0/24, router at 192.168.1.1. No problem with the (static net config) server, no problem on the net where there are at least 5 different dhcp clients at all time. I powered off the receiver and the controller, and on again. I pressed the fan button on the receiver to turn it red, and pair the controller again, bridge mode. At first it seemed to work well, the Controller discovered the receiver. (By the way, I believe you should fix the documentation, the menu path I use to do that is not the one described in my UG.) When the question to use a wired or wireless network to contact SqueezeCenter came, I answered wired, waited a bit and received a failure message. The ethernet plug showed the orange link-up led, and a scarcely blinking rx/tx green-yellow led. There was no lease for the receiver in the dhcp server, and no log of DHCP transaction. Normally the receiver is served a fixed address based on its MAC. There started a seemingly endless loop of rebooting, reset to factory condition on the receiver first, and then on both the controller and receiver. I tried various cables, and even hooked it directly to the router/dhcp server, disconnecting all the rest of my network, removed the fixed address lease in the DHCP server, to no avail. Having discarded the influence of cable types and switches along the path, knowing the DHCP server was working perfectly well, I gave up and left the receiver unplugged for an hour. Tried again, starting with a factory restore, nothing. I was ready to declare the ethernet card in the receiver dead. Then something magic happened. I decided to sacrifice the uptime of my router and see if a reboot would help. It looks like it did, because my next factory restore/reconnect attempt finally yielded a DHCP request on the receiver side. The Duet connected and worked. Not sleeping the server overnight, this morning the Duet still works. I am flabbergasted. The router was in excellent operating condition. Before being disconnected and connected to the test net, the receiver had been connected to this network for 2 weeks I think. I noticed 1 or 2 freezes of the receiver during that time, happened at night when the SC server is asleep, so I can't tell what happened exactly. Anyway, power cycling the receiver was enough for it to reconnect to the network at these times. There is something fishy going on here, and IMO that's on the Duet end, not on the router side. FYI, the router is a pcengines 3-port WRAP board running m0n0wall v1.2 (a BSD variant). It is stable in the extreme and I seldom modify its configuration. Next to the router, on the LAN port, there is a gibabit Dell Powerconnect 2716 switch. The switch port to which the Duet is connected is set to: maximum capability, autoneg, no backpressure, no flow-control. MTU size is standard and there are no VLANs defined on the LAN. I did not powercycle the switch amidst my desperate attempts to revive the receiver. Cabling is CAT6. On the path to the receiver there is a small Netgear 5 port gig switch GS-605v2. I didn't powercycle it either so switches are probably out of the picture. (Mind also I tried direct connection to the router which only has fast ethernet ports, with a short CAT5e cable.) On a second port (call it DMZ), the router serves a separate network (192.168.2.0/24) which is currently only used by wifi clients. During my various attempts I tried connecting to that network (although there is no SC server there) and promptly received a lease. Wifi is provided by a Netgear WG-602v3 AP hooked directly to a port of the router. The last router port is connected direct to a DSL modem. On both LAN and DMZ ports, the integrated dhcpd server default 9-hour minimum leases, and leases to clients requesting a longer duration are capped at 24-hours. I don't know whether dhcpd works in split configuration, or has 2 separate instances running. There are outgoing firewall rules on the LAN port, but I specifically left the SC server and the Duet, both controller and receiver, total outgoing access to the internet until things have settled (the very reason I gave the controller and receiver fixed leases in the DHCP server.) There is no filtering whatsoever within the 192.168.1.0/24 net itself. Inside the LAN, no machine has a firewall. System, firewall and DHCP server logs showed nothing but normal operation (except for lack of DHCP request on the receiver end, that is) on the router before its reboot. There was no on-going leases for the Duet nodes before rebooting the router. Today I re-established the fixed IP leases. It took a powercycle on both receiver and controller to work, but no router reboot this time. The SC server is a debian Lenny/sid machine, running SC 7.2. No plugin except SrvrPowerControl. A Squeezebox Classic client is quite happy with it, WOL and all, day after day. The Controller runs firmware 7.2r2873. The Receiver runs firmware version 47. Can you make something out of this ? BTW: WOL does **NOT** work with the Duet. Only with the Squeezebox Classic. I repeat: *Duet, WOL, no worky.* -- epoch1970 ------------------------------------------------------------------------ epoch1970's Profile: http://forums.slimdevices.com/member.php?userid=16711 View this thread: http://forums.slimdevices.com/showthread.php?t=52702 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
