Re: [OpenWrt-Devel] WAN dhcp client doesnt recognize unplugged cable and doesnt request new IP on replugged
Hans Dedecker dedec...@gmail.com wrote: By the introduction of linksensing the user experience changed when using the proto static; before the static IP address was present in the kernel when the link was down after the introduction of linksensing the static IP address is not present anymore. I'm not aware of other bugs. Given that this is the way regular desktop linux works too, are we digging a hole here where OpenWrt keeps providing the old behaviour? My desktop has a static ip on one interface, and when I unplug the cable, I get... NetworkManager[995]: info (enp0s20u1u1): link disconnected (deferring action for 4 seconds) NetworkManager[995]: info (enp0s20u1u1): link disconnected (calling deferred action) NetworkManager[995]: info (enp0s20u1u1): device state change: activated - unavailable (reason 'carrier-changed') [100 20 40] NetworkManager[995]: info (enp0s20u1u1): deactivating device (reason 'carrier-changed') [40] And then the static IP is gone too. It might have been a behaviour change but lots of things change. Was this really something critical enough to try and keep? Further, if netifd is the one adding force_link, then surely it should be removing it when you change to dhcp, not just leaving there like a land mine Tested this on the netifd trunk version; switching proto static to dhcp and did not observe an issue regarding force_link as the dhcp client was teared down when the link cable was unplugged. Do you use the netifd trunk version ? no idea, what version would that be exactly? netifd packages just have a date and a git tag :) I'm going to run some more tests on this, thanks for the information and background so far. Cheers, Karl Palsson ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WAN dhcp client doesnt recognize unplugged cable and doesnt request new IP on replugged
Hans Dedecker dedec...@gmail.com wrote: netifd enables by default force_link for interface with as proto static; are you referring to such an interface ? I'm not a big fan of enabling force_link by default as I already discussed this behavior on the OpenWRT Devel mailing list (https://lists.openwrt.org/pipermail/openwrt-devel/2014-August/027166.html). So I share your pain but it seems OpenWRT users expect an IP address to be present even when the link is down in case of a static protocol. If in your case force_link is enabled by default config for a non static interface I would be surprised and indeed consider this as an issue. It's probably because my custom init reconfigures things at first boot, as it could be contained in a package rather than having to maintain patches on openwrt core. What sort of bugs is felix referring to? Surely most of them would/could be addressed in whatever software was behaving badly? Further, if netifd is the one adding force_link, then surely it should be removing it when you change to dhcp, not just leaving there like a land mine Cheers, Karl P___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WAN dhcp client doesnt recognize unplugged cable and doesnt request new IP on replugged
On Thu, May 14, 2015 at 10:45 PM, Jakub Jančo kub...@gmail.com wrote: No I havent, I thought it is Bring on boot but it is another option. So my problem persist. config interface 'wan' option ifname 'eth0' option proto 'dhcp' option metric '1' config interface 'wan6' option ifname '@wan' option proto 'dhcpv6' This is my wan config, and after turn off and on lan port on remote site, no logs entries. netifd relies on events from the kernel to detect link changes; when the cable is unplugged the NO_CARRIER flag of eth0 needs to be set which can be checked via the ip utility (ip link show) or ifconfig (RUNNING flag not set in this case). Further the cmd ubus call network.device status dumps the netifd status of the devices (including the link state). Hans 2015-05-14 22:29 GMT+02:00 Hans Dedecker dedec...@gmail.com: On Thu, May 14, 2015 at 8:23 PM, Jakub Jančo kub...@gmail.com wrote: 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? I don't see any added value of using force_link on a WAN interface unless you would use a static IP address. You verified force_link is enabled on the WAN interface for your board ? Hans 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
Re: [OpenWrt-Devel] WAN dhcp client doesnt recognize unplugged cable and doesnt request new IP on replugged
Hello, After I unplug cable: ifconfig eth0 Link encap:Ethernet HWaddr 14:CC:20:4D:3D:B5 inet addr:10.1.5.246 Bcast:10.1.5.255 Mask:255.255.255.0 inet6 addr: fe80::16cc:20ff:fe4d:3db5/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:747 errors:0 dropped:0 overruns:0 frame:0 TX packets:896 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:84708 (82.7 KiB) TX bytes:487679 (476.2 KiB) Interrupt:4 ip link 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 14:cc:20:4d:3d:b5 brd ff:ff:ff:ff:ff:ff After plug in cable, no change, no logs. ModelTP-Link TL-WR1043N/ND v2 Firmware Version OpenWrt Barrier Breaker 14.07 / LuCI Trunk (svn-r10472) Kernel Version3.10.49 -- S pozdravom Jakub Janco 2015-05-15 9:34 GMT+02:00 Hans Dedecker dedec...@gmail.com: On Thu, May 14, 2015 at 10:45 PM, Jakub Jančo kub...@gmail.com wrote: No I havent, I thought it is Bring on boot but it is another option. So my problem persist. config interface 'wan' option ifname 'eth0' option proto 'dhcp' option metric '1' config interface 'wan6' option ifname '@wan' option proto 'dhcpv6' This is my wan config, and after turn off and on lan port on remote site, no logs entries. netifd relies on events from the kernel to detect link changes; when the cable is unplugged the NO_CARRIER flag of eth0 needs to be set which can be checked via the ip utility (ip link show) or ifconfig (RUNNING flag not set in this case). Further the cmd ubus call network.device status dumps the netifd status of the devices (including the link state). Hans 2015-05-14 22:29 GMT+02:00 Hans Dedecker dedec...@gmail.com: On Thu, May 14, 2015 at 8:23 PM, Jakub Jančo kub...@gmail.com wrote: 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? I don't see any added value of using force_link on a WAN interface unless you would use a static IP address. You verified force_link is enabled on the WAN interface for your board ? Hans 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
Re: [OpenWrt-Devel] WAN dhcp client doesnt recognize unplugged cable and doesnt request new IP on replugged
On 15/05/15 10:48, Jakub Jančo wrote: Hello, After I unplug cable: ifconfig eth0 Link encap:Ethernet HWaddr 14:CC:20:4D:3D:B5 inet addr:10.1.5.246 Bcast:10.1.5.255 Mask:255.255.255.0 inet6 addr: fe80::16cc:20ff:fe4d:3db5/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:747 errors:0 dropped:0 overruns:0 frame:0 TX packets:896 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:84708 (82.7 KiB) TX bytes:487679 (476.2 KiB) Interrupt:4 ip link 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 14:cc:20:4d:3d:b5 brd ff:ff:ff:ff:ff:ff After plug in cable, no change, no logs. ModelTP-Link TL-WR1043N/ND v2 Firmware Version OpenWrt Barrier Breaker 14.07 / LuCI Trunk (svn-r10472) Kernel Version3.10.49 Do you have the switch configured correctly? You can use swconfig to check the physical port status. http://wiki.openwrt.org/toh/tp-link/tl-wr1043nd ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WAN dhcp client doesnt recognize unplugged cable and doesnt request new IP on replugged
This is my original switch config: config switch option name 'switch0' option reset '1' option enable_vlan '1' config switch_vlan option device 'switch0' option vlan '1' option ports '0t 1 2 3 4' option vid '1' config switch_vlan option device 'switch0' option vlan '2' option ports '0t' option vid '3' config switch_vlan option device 'switch0' option vlan '3' option ports '0t' option vid '2' config switch_vlan option device 'switch0' option vlan '4' option vid '4' option ports '0t' config switch_vlan option device 'switch0' option vlan '5' option vid '5' option ports '5 6' But in wiki they say that wan must be vlan2, but I didnt notice difference if it is on vlan5. Anyway I revert switch to original config and add force_link=0 for wan: config interface 'wan' option ifname 'eth0' option proto 'dhcp' option metric '1' option force_link '0' config switch option name 'switch0' option reset '1' option enable_vlan '1' config switch_vlan option device 'switch0' option vlan '1' option vid '1' option ports '0 1 2 3 4' config switch_vlan option device 'switch0' option vlan '2' option vid '2' option ports '5 6' It seems that switch noticed link down on port 5: $swconfig dev switch0 port 5 show Port 5: mib: Port 5 MIB counters RxBroad : 65 RxPause : 0 RxMulti : 47 RxFcsErr: 0 RxAlignErr : 0 RxRunt : 0 RxFragment : 0 Rx64Byte: 310 Rx128Byte : 960 Rx256Byte : 101 Rx512Byte : 16 Rx1024Byte : 62 Rx1518Byte : 1 RxMaxByte : 0 RxTooLong : 0 RxGoodByte : 149935 RxBadByte : 0 RxOverFlow : 0 Filtered: 0 TxBroad : 322 TxPause : 0 TxMulti : 0 TxUnderRun : 0 Tx64Byte: 668 Tx128Byte : 493 Tx256Byte : 135 Tx512Byte : 9 Tx1024Byte : 12 Tx1518Byte : 494 TxMaxByte : 0 TxOverSize : 0 TxByte : 715736 TxCollision : 0 TxAbortCol : 0 TxMultiCol : 0 TxSingleCol : 0 TxExcDefer : 0 TxDefer : 0 TxLateCol : 0 pvid: 2 link: port:5 link:down Link port 6 stays ON, probably because it is cpu. -- S pozdravom Jakub Janco 2015-05-15 12:28 GMT+02:00 Conor O'Gorman i...@conorogorman.net: On 15/05/15 10:48, Jakub Jančo wrote: Hello, After I unplug cable: ifconfig eth0 Link encap:Ethernet HWaddr 14:CC:20:4D:3D:B5 inet addr:10.1.5.246 Bcast:10.1.5.255 Mask:255.255.255.0 inet6 addr: fe80::16cc:20ff:fe4d:3db5/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:747 errors:0 dropped:0 overruns:0 frame:0 TX packets:896 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:84708 (82.7 KiB) TX bytes:487679 (476.2 KiB) Interrupt:4 ip link 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 14:cc:20:4d:3d:b5 brd ff:ff:ff:ff:ff:ff After plug in cable, no change, no logs. ModelTP-Link TL-WR1043N/ND v2 Firmware Version OpenWrt Barrier Breaker 14.07 / LuCI Trunk (svn-r10472) Kernel Version3.10.49 Do you have the switch configured correctly? You can use swconfig to check the physical port status. http://wiki.openwrt.org/toh/tp-link/tl-wr1043nd ___ 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
Re: [OpenWrt-Devel] WAN dhcp client doesnt recognize unplugged cable and doesnt request new IP on replugged
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
Re: [OpenWrt-Devel] WAN dhcp client doesnt recognize unplugged cable and doesnt request new IP on replugged
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
Re: [OpenWrt-Devel] WAN dhcp client doesnt recognize unplugged cable and doesnt request new IP on replugged
On Thu, May 14, 2015 at 8:23 PM, Jakub Jančo kub...@gmail.com wrote: 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? I don't see any added value of using force_link on a WAN interface unless you would use a static IP address. You verified force_link is enabled on the WAN interface for your board ? Hans 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
Re: [OpenWrt-Devel] WAN dhcp client doesnt recognize unplugged cable and doesnt request new IP on replugged
No I havent, I thought it is Bring on boot but it is another option. So my problem persist. config interface 'wan' option ifname 'eth0' option proto 'dhcp' option metric '1' config interface 'wan6' option ifname '@wan' option proto 'dhcpv6' This is my wan config, and after turn off and on lan port on remote site, no logs entries. -- S pozdravom Jakub Janco 2015-05-14 22:29 GMT+02:00 Hans Dedecker dedec...@gmail.com: On Thu, May 14, 2015 at 8:23 PM, Jakub Jančo kub...@gmail.com wrote: 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? I don't see any added value of using force_link on a WAN interface unless you would use a static IP address. You verified force_link is enabled on the WAN interface for your board ? Hans 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
Re: [OpenWrt-Devel] WAN dhcp client doesnt recognize unplugged cable and doesnt request new IP on replugged
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
