Closed aparcar closed 6 years ago
dedeckeh:
Is there any reason why you create a static wan dslite interface and not use the dynamic created wan6_4 interface by the dhcpv6 script in case the AFTR option is received ?
You cannot have both together; if you don't want a dynamic dslite interface being created by the dhcpv6 script you need to set iface_dslite to 0 in the wan6 network config or use the dynamic created dslite interface and remove the wan interface network config.
LinuxfarmerHH:
Had a static wan interface because of the AFTR ip address that need to be placed somewhere.
Yes and with disabled dynamic creation the bug disappears, so this can be closed.
Thanks for that:-)
LinuxfarmerHH:
TP-Link Archer C7 V2 behind Fritz6360 cable as bridge. OpenWrt SNAPSHOT r7066-060e1ecefa / LuCI Master (git-18.151.24607-5452cc2)
Using follwing setup the interface wan is switched on and off every second, visible in system.log what slowdown the link to 1/3 and extends pings above 100ms. Mission critical streams with less buffer on IPv4 do stutter by these breaks. System load on the router is higher than necessary, hope that can be fixex until V18 comes out.
/etc/config/network config interface 'loopback' option ifname 'lo' option proto 'static' option ipaddr '127.0.0.1' option netmask '255.0.0.0'
config globals 'globals' option ula_prefix 'fd68:1405:cafe:fabe::/48'
config interface 'lan' option type 'bridge' option ifname 'eth1.1' option proto 'static' option ipaddr '192.168.1.1' option netmask '255.255.255.0' option ip6hint '2a02:2028::' option ip6assign '64'
config interface 'wan6' option ifname 'eth0.2' option proto 'dhcpv6' option reqaddress 'try' option reqprefix 'auto'
config switch option name 'switch0' option reset '1' option enable_vlan '1'
config switch_vlan option device 'switch0' option vlan '1' option ports '2 3 4 5 0t'
config switch_vlan option device 'switch0' option vlan '2' option ports '1 6t'
config interface 'WAN' option proto 'dslite' option peeraddr '2a02:2028:ff00::1:0:3b' list tunlink 'wan6'
Sun Jun 3 09:21:01 2018 daemon.notice netifd: wan6_4 (29263): Command failed: Unknown error Sun Jun 3 09:21:01 2018 daemon.notice netifd: Interface 'wan6_4' is now down Sun Jun 3 09:21:01 2018 daemon.notice netifd: Interface 'wan6_4' is setting up now Sun Jun 3 09:21:02 2018 daemon.notice netifd: wan6_4 (29323): Command failed: Unknown error Sun Jun 3 09:21:02 2018 daemon.notice netifd: Interface 'wan6_4' is now down Sun Jun 3 09:21:02 2018 daemon.notice netifd: Interface 'wan6_4' is setting up now Sun Jun 3 09:21:02 2018 daemon.notice netifd: wan6_4 (29409): Command failed: Unknown error Sun Jun 3 09:21:02 2018 daemon.notice netifd: Interface 'wan6_4' is now down Sun Jun 3 09:21:02 2018 daemon.notice netifd: Interface 'wan6_4' is setting up now Sun Jun 3 09:21:03 2018 daemon.notice netifd: wan6_4 (29470): Command failed: Unknown error Sun Jun 3 09:21:03 2018 daemon.notice netifd: Interface 'wan6_4' is now down Sun Jun 3 09:21:03 2018 daemon.notice netifd: Interface 'wan6_4' is setting up now Sun Jun 3 09:21:04 2018 daemon.notice netifd: wan6_4 (29555): Command failed: Unknown error Sun Jun 3 09:21:04 2018 daemon.notice netifd: Interface 'wan6_4' is now down Sun Jun 3 09:21:04 2018 daemon.notice netifd: Interface 'wan6_4' is setting up now Sun Jun 3 09:21:05 2018 daemon.notice netifd: wan6_4 (29614): Command failed: Unknown error Sun Jun 3 09:21:05 2018 daemon.info odhcpd[1922]: Using a RA lifetime of 1800 seconds on br-lan Sun Jun 3 09:21:05 2018 daemon.notice netifd: Interface 'wan6_4' is now down Sun Jun 3 09:21:05 2018 daemon.notice netifd: Interface 'wan6_4' is setting up now Sun Jun 3 09:21:06 2018 daemon.info odhcpd[1922]: Using a RA lifetime of 1800 seconds on br-lan