<div dir="ltr">Hello,<br>After I unplug cable:<br><br><div>ifconfig<br>eth0 Link encap:Ethernet HWaddr 14:CC:20:4D:3D:B5 <br> inet addr:10.1.5.246 Bcast:10.1.5.255 Mask:255.255.255.0<br> inet6 addr: fe80::16cc:20ff:fe4d:3db5/64 Scope:Link<br> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br> RX packets:747 errors:0 dropped:0 overruns:0 frame:0<br> TX packets:896 errors:0 dropped:0 overruns:0 carrier:0<br> collisions:0 txqueuelen:1000 <br> RX bytes:84708 (82.7 KiB) TX bytes:487679 (476.2 KiB)<br> Interrupt:4 <br><br></div><div>ip link<br>2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000<br> link/ether 14:cc:20:4d:3d:b5 brd ff:ff:ff:ff:ff:ff<br><br></div><div>After plug in cable, no change, no logs.<br><br></div><div>ModelTP-Link TL-WR1043N/ND v2
Firmware Version
OpenWrt Barrier Breaker 14.07 /
LuCI Trunk (svn-r10472)
Kernel Version3.10.49
</div><div><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><br>--<br>S pozdravom Jakub Janco</div></div>
<br><div class="gmail_quote">2015-05-15 9:34 GMT+02:00 Hans Dedecker <span dir="ltr"><<a href="mailto:dedeckeh@gmail.com" target="_blank">dedeckeh@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu, May 14, 2015 at 10:45 PM, Jakub Jančo <<a href="mailto:kubco2@gmail.com">kubco2@gmail.com</a>> wrote:<br>
> No I havent, I thought it is "Bring on boot" but it is another option. So my<br>
> problem persist.<br>
> config interface 'wan'<br>
> option ifname 'eth0'<br>
> option proto 'dhcp'<br>
> option metric '1'<br>
><br>
> config interface 'wan6'<br>
> option ifname '@wan'<br>
> option proto 'dhcpv6'<br>
><br>
> This is my wan config, and after turn off and on lan port on remote site, no<br>
> logs entries.<br>
netifd relies on events from the kernel to detect link changes; when<br>
the cable is unplugged the NO_CARRIER flag of eth0 needs to be set<br>
which can be checked via the ip utility (ip link show) or ifconfig<br>
(RUNNING flag not set in this case). Further the cmd ubus call<br>
network.device status dumps the netifd status of the devices<br>
(including the link state).<br>
<br>
Hans<br>
><br>
><br>
> 2015-05-14 22:29 GMT+02:00 Hans Dedecker <<a href="mailto:dedeckeh@gmail.com">dedeckeh@gmail.com</a>>:<br>
><br>
>> On Thu, May 14, 2015 at 8:23 PM, Jakub Jančo <<a href="mailto:kubco2@gmail.com">kubco2@gmail.com</a>> wrote:<br>
>> > Thank you for explanation.<br>
>> ><br>
>> > Why does openwrt use force_link on WAN, when it can break internet<br>
>> > connection and remote access?<br>
>> > Or what are advantages of force_link?<br>
>> I don't see any added value of using force_link on a WAN interface<br>
>> unless you would use a static IP address.<br>
>> You verified force_link is enabled on the WAN interface for your board ?<br>
>><br>
>> Hans<br>
>> ><br>
>> > Thanks.<br>
>> ><br>
>> ><br>
>> > --<br>
>> > S pozdravom Jakub Janco<br>
>> ><br>
>> > 2015-05-14 17:32 GMT+02:00 Hans Dedecker <<a href="mailto:dedeckeh@gmail.com">dedeckeh@gmail.com</a>>:<br>
>> >><br>
>> >> On Wed, May 13, 2015 at 12:35 PM, Conor O'Gorman <<a href="mailto:i@conorogorman.net">i@conorogorman.net</a>><br>
>> >> wrote:<br>
>> >> > On 12/05/15 17:57, Jakub Jančo wrote:<br>
>> >> >><br>
>> >> >> Hello,<br>
>> >> >><br>
>> >> >> I have tplink 1043nd with BB<br>
>> >> >><br>
>> >> >> Problem is that I have dhcp client on WAN and if I unplug cable from<br>
>> >> >> WAN, it doesnt change status, give up dhcp address.<br>
>> >> >><br>
>> >> >> Even worse is that if I plug cable with another end point with<br>
>> >> >> another<br>
>> >> >> network, WAN dhcp client doesnt pull new IP, I must click on<br>
>> >> >> "Connect"<br>
>> >> >> to refresh dhcp client, then new ip is assigned and internet works.<br>
>> >> >> Or<br>
>> >> >> restart device.<br>
>> >> ><br>
>> >> ><br>
>> >> > Have a look at ifpugd.<br>
>> >> ><br>
>> >> > But maybe netifd should/could/might do something for this scenario?<br>
>> >> ><br>
>> >> > Conor<br>
>> >> > _______________________________________________<br>
>> >> > openwrt-devel mailing list<br>
>> >> > <a href="mailto:openwrt-devel@lists.openwrt.org">openwrt-devel@lists.openwrt.org</a><br>
>> >> > <a href="https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel" target="_blank">https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel</a><br>
>> >> netifd has support for link state changes; the network interface will<br>
>> >> be brought up/down<br>
>> >> if the link is active/inactive. However if the force_link parameter is<br>
>> >> enabled for a network<br>
>> >> interface netifd will ignore link state changes.<br>
>> >><br>
>> >> Hans<br>
>> >> _______________________________________________<br>
>> >> openwrt-devel mailing list<br>
>> >> <a href="mailto:openwrt-devel@lists.openwrt.org">openwrt-devel@lists.openwrt.org</a><br>
>> >> <a href="https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel" target="_blank">https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel</a><br>
>> ><br>
>> ><br>
><br>
><br>
</blockquote></div><br></div>