Post-thunderstorm, I turned on the router to meet strange looking ethernet LEDs (1 and 3 are on, and blinking randomly; 2 and 4 remain off unless an ethernet cable is stuck in). Wireless still worked, as did the ADSL part, but dear lord, it partially fried my ethernet ports (they work on and off, and I can't seem to get the TI Remote app to talk to the modem, nor the DarkWolf modded D-Link firmware upgrader program).
So, it looks like I can't reflash the firmware save for using the web interface, which I frankly have ~0% success doing. Normally this wouldn't bother me much, but udhcpd has gone nuts, or so it seems. Running udhcpd manually seems to indicate that udhcpd is working properly, with one exception: none of the DHCP{OFFER,ACK,NAK} packets seem to be reaching the clients, even if udhcpd claims to have sent them. I was pretty curious about this, and set up some iptables rules:
Code: Select all
iptables -I INPUT -p udp --sport 67:68 --dport 67:68 -j LOG
iptables -I OUTPUT -p udp --sport 67:68 --dport 67:68 -j LOG
My firmware version is 2.4, since I was away from home for some time and never got round to upgrading it, and my udhcpd.conf is as follows:
Code: Select all
start 192.168.1.2
end 192.168.1.254
inflease_time 604800
interface br0
opt router 192.168.1.1
opt dns 192.168.1.1
opt subnet 255.255.255.0
opt lease 3600
conflict_time 3600
lease_file /var/tmp/landhcps0.leases