Thank you for explanation. Why does openwrt use force_link on WAN, when it can break internet connection and remote access? Or what are advantages of force_link?
Thanks. -- S pozdravom Jakub Janco 2015-05-14 17:32 GMT+02:00 Hans Dedecker <dedec...@gmail.com>: > On Wed, May 13, 2015 at 12:35 PM, Conor O'Gorman <i...@conorogorman.net> > wrote: > > On 12/05/15 17:57, Jakub Jančo wrote: > >> > >> Hello, > >> > >> I have tplink 1043nd with BB > >> > >> Problem is that I have dhcp client on WAN and if I unplug cable from > >> WAN, it doesnt change status, give up dhcp address. > >> > >> Even worse is that if I plug cable with another end point with another > >> network, WAN dhcp client doesnt pull new IP, I must click on "Connect" > >> to refresh dhcp client, then new ip is assigned and internet works. Or > >> restart device. > > > > > > Have a look at ifpugd. > > > > But maybe netifd should/could/might do something for this scenario? > > > > Conor > > _______________________________________________ > > openwrt-devel mailing list > > openwrt-devel@lists.openwrt.org > > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > netifd has support for link state changes; the network interface will > be brought up/down > if the link is active/inactive. However if the force_link parameter is > enabled for a network > interface netifd will ignore link state changes. > > Hans > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel >
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
