Hi! Up until last week, I had a dedicated Linux box serving as my home router/gateway. But it makes a lot of noise and eats too much power, so I've installed tomato (1.06.0981) on my WRT54G (v2.2)... But I have this problem with DHCP that's making me go nuts... I have a Linux install here, configured to use DHCP. It used to work fine while I was using ISC-DHCP on my old Linux server, but now with "dnsmasq" it can't obtain a lease most of the time. It keeps pumping out DHCPDISCOVER messages but gets nothing back (and I've confirmed that the box really sees no reply, using wireshark/ethereal). Funny enough, the logs on my linksys show those DHCPDISCOVERs and corresponding DHCPOFFERs... I first thought that it must be something with the DHCP client, some problem that didn't manifest itself with ISC DHCP as server. But I've tried "udhcpc" and the problem remained. Also, the Windows boxes always get their lease... Although I've noticed that most of the time they hammer the linksys a bunch of times before finally getting their lease, as if they aren't seeing the first few replies. After a few hours hitting my head on the wall over this, I finally found a way to reproduce the problem reliably... If I power off the linksys, in the first 30 seconds or so after powering it back on, the Linux box obtains a lease just fine. But, as soon as the router sets its internal clock, the Linux box can't get a lease anymore. I've even tried to disconnect the router from my DSL modem, and the same thing happens: DHCP works fine (for both the Linux box and Windows boxes) up until the moment I reconnect the modem, and the router sets its internal clock... Also, just rebooting the router solves nothing, and that's because the internal clock stays set... I'm wondering if anyone else has noticed this problem, or it's just me... BTW, if anyone thinks this is too weird to be true: this is NOT an April Fools joke.