Closed GoogleCodeExporter closed 9 years ago
First of all, it is not firmware problem.
Try robocfg
Original comment by lly.dev
on 16 Dec 2011 at 4:55
robocfg не помогает. Помогает killall udhcpc с
последующим его запуском:
/sbin/udhcpc -i vlan2 -p /var/run/udhcpc0.pid -bN61 -O33 -O121 -O249
После первого запроса (15 часов назад) dhcp в
файле /tmp/udhcpc0.expires было значение "43200". Сейчас
в файле /tmp/udhcpc0.expires (измененный 3 часа назад)
значение "1324153519". Может из-за этого
интерфейс и ложится если так долго не
обращается к dhcp? Это проблема провайдера?
Original comment by tische...@gmail.com
on 17 Dec 2011 at 11:21
udhcpc renew procedure works as specified in RFC, probably your ISP violate it
(like Beeline Russia). In such case we have two solutions:
1) ISP must follow RFC, best way
2) we have to add special hack for this ISP (busybox maintainers will refuse
such hacks), ugly way
Original comment by lly.dev
on 18 Dec 2011 at 7:30
according described behaviour, dhcp client can't renew lease nor via unicast
(renew), neither via broadcast (rebind).
probably it's router or ISP local hardware fault, please contact to
tech.support, check with other router/without it.
anyway, you could turn off/onn switch ports power
simple shell script for N16
#!/bin/sh
port=0 # wan port
val=$(et phyrd $port 0)
let "off=val|0x800"
let "on=val&~0x800"
et phywr $port 0 $off
sleep 3
et phywr $port 0 $on
Original comment by themiron.ru
on 19 Dec 2011 at 7:20
Original issue reported on code.google.com by
tische...@gmail.com
on 16 Dec 2011 at 4:40