WAN issue after reboot

[Snoopotic]

Hi,
I'm on an Asus RT-AC56U with 380.59. The router is behind a Hitron CVE-30360 cable modem/router in bridged mode.

The issue is: always after rebooting The Asus' WAN does not get internet connection (although it seems it gets an ip...) I only can fix it by also restarting the Hitron modem... This is bad. Because It's not always rebooting it's sometime some other setting I change that makes the Asus restart the WAN interface...

Someone told me I must nit change the WAN ports MAC-Adress... but I don't get it. I don't have set any MAC address - so it shall be the routers one. But nevertheless I tested if it helps if I set up the Router's mac explicitly. Did not work.

The syslog has entries like (i removed the dnsmasq-dhcp entries) but I don't get clever from that:

Aug  1 02:01:17 dhcp client: bound 146.<eek>.174.157 via 146.<eek>.174.254 during 1800 seconds.
Aug  1 02:01:18 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Aug  1 02:01:27 ntp: start NTP update
Aug  1 02:01:42 ntp: start NTP update
Aug  1 02:01:46 afpd[1116]: Netatalk AFP/TCP listening on 146.<eek>.174.157:548
Aug  1 02:01:57 ntp: start NTP update
…
Aug  1 02:02:27 ntp: start NTP update
Aug  1 02:02:27 WAN Connection: Ethernet link down.
Aug  1 02:02:27 stop_nat_rules: apply the redirect_rules!
Aug  1 02:02:42 ntp: start NTP update
Aug  1 02:02:57 WAN Connection: Ethernet link up.
Aug  1 02:02:57 rc_service: wanduck 426:notify_rc restart_wan_if 0
Aug  1 02:02:57 ntp: start NTP update
Aug  1 02:02:58 dnsmasq[441]: read /etc/hosts - 6 addresses
Aug  1 02:02:58 dnsmasq[441]: read /etc/hosts.dnsmasq - 3 addresses
Aug  1 02:02:58 dnsmasq-dhcp[441]: read /etc/ethers - 3 addresses
Aug  1 02:02:58 dnsmasq[441]: using nameserver 2001:4860:4860::8888#53
Aug  1 02:02:58 dnsmasq[441]: using nameserver 2001:470:20::2#53
Aug  1 02:02:58 dnsmasq[441]: using nameserver 83.169.186.33#53
Aug  1 02:02:58 dnsmasq[441]: using nameserver 83.169.186.97#53
Aug  1 02:02:58 kernel: Attempt to kill tasklet from interrupt
Aug  1 02:02:58 miniupnpd[1123]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug  1 02:02:58 miniupnpd[1123]: Failed to get IP for interface eth0
Aug  1 02:02:58 miniupnpd[1123]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Aug  1 02:02:58 kernel: device eth0 left promiscuous mode
Aug  1 02:02:58 kernel: br0: port 1(vlan1) entering forwarding state
Aug  1 02:02:58 kernel: device eth0 entered promiscuous mode
Aug  1 02:02:58 kernel: br0: topology change detected, propagating
Aug  1 02:02:58 kernel: br0: port 1(vlan1) entering forwarding state
Aug  1 02:02:58 kernel: br0: port 1(vlan1) entering forwarding state
Aug  1 02:02:58 dnsmasq[441]: read /etc/hosts - 6 addresses
Aug  1 02:02:58 dnsmasq[441]: read /etc/hosts.dnsmasq - 3 addresses
Aug  1 02:02:58 dnsmasq-dhcp[441]: read /etc/ethers - 3 addresses
Aug  1 02:02:58 dnsmasq[441]: using nameserver 2001:4860:4860::8888#53
Aug  1 02:02:58 dnsmasq[441]: using nameserver 2001:470:20::2#53
Aug  1 02:02:58 dnsmasq[441]: using nameserver 83.169.186.33#53
Aug  1 02:02:58 dnsmasq[441]: using nameserver 83.169.186.97#53
Aug  1 02:02:58 dnsmasq[441]: read /etc/hosts - 6 addresses
Aug  1 02:02:58 dnsmasq[441]: read /etc/hosts.dnsmasq - 3 addresses
Aug  1 02:02:58 dnsmasq-dhcp[441]: read /etc/ethers - 3 addresses
Aug  1 02:02:58 dnsmasq[441]: using nameserver 2001:4860:4860::8888#53
Aug  1 02:02:58 dnsmasq[441]: using nameserver 2001:470:20::2#53
Aug  1 02:03:02 WAN Connection: ISP's DHCP did not function properly.
…
Aug  1 02:05:17 ntp: start NTP update
Aug  1 02:05:40 miniupnpd[1123]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug  1 02:05:40 miniupnpd[1123]: Failed to get IP for interface eth0
Aug  1 02:05:40 miniupnpd[1123]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug  1 02:05:40 miniupnpd[1123]: PCP: Invalid PCP v2 MAP message.
Aug  1 02:05:40 miniupnpd[1123]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug  1 02:05:40 miniupnpd[1123]: PCP: Invalid PCP v2 MAP message.
Aug  1 02:05:40 miniupnpd[1123]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug  1 02:05:40 miniupnpd[1123]: PCP: Invalid PCP v2 MAP message.
Aug  1 02:05:40 miniupnpd[1123]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug  1 02:05:40 miniupnpd[1123]: Failed to get IP for interface eth0
Aug  1 02:05:41 miniupnpd[1123]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug  1 02:05:41 miniupnpd[1123]: Failed to get IP for interface eth0
...
Aug  1 02:05:42 miniupnpd[1123]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug  1 02:05:42 miniupnpd[1123]: Failed to get IP for interface eth0
Aug  1 02:05:44 miniupnpd[1123]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug  1 02:05:44 miniupnpd[1123]: Failed to get IP for interface eth0
Aug  1 02:05:44 ntp: start NTP update
Aug  1 02:05:48 miniupnpd[1123]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug  1 02:05:48 miniupnpd[1123]: Failed to get IP for interface eth0
…

Does anyone has an idea what I might do or set up?
thank you.

 

[Snoopotic]

Me again.
I was able to isolate the problem:

It's the tunnel broker.net DDNS Setting in combination with 6in4 tunnel.
First I disabled the 6in4 tunnel and rebooting worked fine.
then I enabled 6in4 again but disabled DDNS but manually set up the ipv4 address after and before each reboot (because every reboot my ipv4 address changes) and also this works flawlessly.

So. If someone can explain me how to implement own custom scripts via jffs I will write my own script using curl to update my new ipv4 address without the DDNS setting. Or someone finds a bug in the DDNS setting for tunnel broker.net and fixes it - there ire I am not able to
--> Maybe as he.net is one of the last tunnelbrokr for 6in4 maybe the 6in4 implementation could be extended with these settings (taken from the example screen for openwrt):
uci set network.henet.tunnelid=<1234567>
uci set network.henet.username=<example>
uci set network.henet.password='UPDATE_KEY_OR_PASSWORD'
...

alternatively it just needs a simple curl request everytime the ipv4-address changes:
https://<username>:<apikey>@ipv4.tunnelbroker.net/nic/update?hostname=<tunnelid>
(https://forums.he.net/index.php?topic=1994.0)