Is this a bug on Asus firmware? WAN disconnections

[RMerlin]

modem is on, and connect to wan, you can tell by the led lights.
modem Ethernet was cutoff , NO led lit.
router stated connected to wan.
No internet connection, have tried.
power off ac66u, and the router was able to assign a new ip address
to the modem, online again.
Does it help?

If the Ethernet link cuts off then the problem is either the cable to the modem, or the modem. Based on your router datestamp I'd say the router didn't crash or reboot.

 

[jabbofresh]

Just throwing this out there. I had issues with the WAN port on some old stock ASUS firmwares as well as all of the DDWRT variants. As soon as I updated to Merlin's firmware the WAN port was fixed and my modem and router were able to communicate. Not sure what is going on but I have seen this issue across several different firmware for the N66R.

 

[Junky321]

I just had this same incidence this week with my RT-AC66/ATT 5301NV Router.

- Reset the Modem (no internet) several times
- If I connected my PC directly to the modem (internet)
- Disconnected Modem/Router and reboot both (no internet from the router)
- I have done these steps several times and during this period, I noticed the router became more and more unresponsive and WebUI was so laggy.
- At the end, the only solution for me was to Factory Restore the router and even without rebooting the modem, it works again.

So was it the modem/router/cable issue? I have no idea but I know if I took the router out of the equation, everything works as normal. Perhaps the router was not crashed or rebooted; it simply entered the zombie stage…xD

At least I now know what I needed to do the next time it happens again.

 

[RMerlin]

One thing to keep in mind for those who aren't aware of it: when using a cablemodem that relies on DHCP, it's almost always required to power off the modem for a good 5-10 minutes to ensure that your ISP notices that your connection was really down. Otherwise, if you just swap devices (for example, switching a router for a directly connected PC, or vice-versa), your ISP might refuse to allocate you a new lease as it doesn't recognize the new MAC requesting the lease. Having the connection down for 5-10 minutes will ensure that your ISP will accept the new MAC that's requesting a lease.

Not saying that it was the issue for some of you here, but still something to keep in mind when doing any test at all with a cablemodem.

 

[stage]

Hey, after about a year of working without a hitch, a couple days ago I started getting very frequent (every 2-10 minutes) disconnections. I tried pretty much every suggested fix: quick reboot of router/modem; turning modem off for 15 minutes, then rebooting; rebooting the router while holding the button down; and plugging computer into modem, then cloning the computer's MAC after being assigned an IP. None of these worked, and I'm pretty stumped. I would appreciate any insight you guys might have. Thanks!

Router: RT-N66U, firmware 3.0.0.4.374.38_2
Modem: Zoom 5241
ISP: Comcast

Log:

Jan 28 21:56:48 miniupnpd[1498]: Listening for NAT-PMP traffic on port 5351
Jan 28 21:57:01 rc_service: httpd 315:notify_rc restart_wan_if 0
Jan 28 21:57:01 dnsmasq[1483]: read /etc/hosts - 5 addresses
Jan 28 21:57:01 dnsmasq[1483]: using nameserver 192.168.100.1#53
Jan 28 21:57:01 stop_wan(): perform DHCP release
Jan 28 21:57:01 miniupnpd[1498]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Jan 28 21:57:01 miniupnpd[1498]: Failed to get IP for interface eth0
Jan 28 21:57:01 miniupnpd[1498]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Jan 28 21:57:01 dnsmasq[1483]: read /etc/hosts - 5 addresses
Jan 28 21:57:01 dnsmasq[1483]: using nameserver 192.168.100.1#53
Jan 28 21:57:01 kernel: Attempt to kill tasklet from interrupt
Jan 28 21:57:01 kernel: br0: port 1(vlan1) entering disabled state
Jan 28 21:57:01 kernel: br0: port 1(vlan1) entering listening state
Jan 28 21:57:01 kernel: br0: port 1(vlan1) entering learning state
Jan 28 21:57:01 kernel: br0: topology change detected, propagating
Jan 28 21:57:01 kernel: br0: port 1(vlan1) entering forwarding state
Jan 28 21:57:03 WAN Connection: WAN was exceptionally disconnected.
Jan 28 21:57:03 stop_nat_rules: apply the redirect_rules!
Jan 28 21:57:03 dnsmasq[1483]: exiting on receipt of SIGTERM
Jan 28 21:57:03 dnsmasq[1507]: started, version 2.68 cachesize 1500
Jan 28 21:57:03 dnsmasq[1507]: asynchronous logging enabled, queue limit is 5 messages
Jan 28 21:57:03 dnsmasq-dhcp[1507]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d
Jan 28 21:57:03 dnsmasq-dhcp[1507]: DHCP, sockets bound exclusively to interface br0
Jan 28 21:57:03 dnsmasq[1507]: read /etc/hosts - 5 addresses
Jan 28 21:57:03 dnsmasq[1507]: using nameserver 192.168.100.1#53
Jan 28 21:57:27 rc_service: httpd 315:notify_rc restart_wan_if 0
Jan 28 21:57:27 dnsmasq[1507]: read /etc/hosts - 5 addresses
Jan 28 21:57:27 dnsmasq[1507]: using nameserver 192.168.100.1#53
Jan 28 21:57:27 stop_wan(): perform DHCP release
Jan 28 21:57:27 kernel: Attempt to kill tasklet from interrupt
Jan 28 21:57:27 WAN Connection: ISP's DHCP did not function properly.
Jan 28 21:57:27 kernel: br0: port 1(vlan1) entering disabled state
Jan 28 21:57:27 kernel: br0: port 1(vlan1) entering listening state
Jan 28 21:57:27 kernel: br0: port 1(vlan1) entering learning state
Jan 28 21:57:27 kernel: br0: topology change detected, propagating
Jan 28 21:57:27 kernel: br0: port 1(vlan1) entering forwarding state
Jan 28 21:57:29 dnsmasq[1507]: read /etc/hosts - 5 addresses
Jan 28 21:57:30 dnsmasq[1507]: read /etc/hosts - 5 addresses
Jan 28 21:57:30 dnsmasq[1507]: using nameserver 75.75.76.76#53
Jan 28 21:57:30 dnsmasq[1507]: using nameserver 75.75.75.75#53
Jan 28 21:57:30 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jan 28 21:57:30 WAN Connection: WAN was restored.
Jan 28 21:57:30 dnsmasq[1507]: exiting on receipt of SIGTERM
Jan 28 21:57:30 dnsmasq[1530]: started, version 2.68 cachesize 1500
Jan 28 21:57:30 dnsmasq[1530]: asynchronous logging enabled, queue limit is 5 messages
Jan 28 21:57:30 dnsmasq-dhcp[1530]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d
Jan 28 21:57:30 dnsmasq-dhcp[1530]: DHCP, sockets bound exclusively to interface br0
Jan 28 21:57:30 dnsmasq[1530]: read /etc/hosts - 5 addresses
Jan 28 21:57:30 dnsmasq[1530]: using nameserver 75.75.76.76#53
Jan 28 21:57:30 dnsmasq[1530]: using nameserver 75.75.75.75#53
Jan 28 21:57:30 rc_service: udhcpc 1512:notify_rc stop_upnp
Jan 28 21:57:30 rc_service: udhcpc 1512:notify_rc start_upnp
Jan 28 21:57:30 miniupnpd[1545]: HTTP listening on port 36152
Jan 28 21:57:30 miniupnpd[1545]: Listening for NAT-PMP traffic on port 5351
Jan 28 21:57:30 dhcp client: bound 67.183.108.77 via 67.183.108.1 during 329090 seconds.
Jan 28 21:58:25 WAN Connection: Ethernet link down.
Jan 28 21:58:25 stop_nat_rules: apply the redirect_rules!
Jan 28 21:58:25 dnsmasq[1530]: exiting on receipt of SIGTERM
Jan 28 21:58:25 dnsmasq[1558]: started, version 2.68 cachesize 1500
Jan 28 21:58:25 dnsmasq[1558]: asynchronous logging enabled, queue limit is 5 messages
Jan 28 21:58:25 dnsmasq-dhcp[1558]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d
Jan 28 21:58:25 dnsmasq-dhcp[1558]: DHCP, sockets bound exclusively to interface br0
Jan 28 21:58:25 dnsmasq[1558]: read /etc/hosts - 5 addresses
Jan 28 21:58:25 dnsmasq[1558]: using nameserver 75.75.76.76#53
Jan 28 21:58:25 dnsmasq[1558]: using nameserver 75.75.75.75#53
Jan 28 21:58:27 WAN Connection: Ethernet link up.
Jan 28 21:58:27 rc_service: wanduck 304:notify_rc restart_wan_if 0
Jan 28 21:58:28 dnsmasq[1558]: read /etc/hosts - 5 addresses
Jan 28 21:58:28 dnsmasq[1558]: using nameserver 75.75.76.76#53
Jan 28 21:58:28 dnsmasq[1558]: using nameserver 75.75.75.75#53
Jan 28 21:58:28 stop_wan(): perform DHCP release
Jan 28 21:58:28 kernel: Attempt to kill tasklet from interrupt
Jan 28 21:58:28 miniupnpd[1545]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Jan 28 21:58:28 miniupnpd[1545]: Failed to get IP for interface eth0
Jan 28 21:58:28 miniupnpd[1545]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Jan 28 21:58:28 dnsmasq[1558]: read /etc/hosts - 5 addresses
Jan 28 21:58:28 dnsmasq[1558]: using nameserver 75.75.76.76#53
Jan 28 21:58:28 dnsmasq[1558]: using nameserver 75.75.75.75#53
Jan 28 21:58:28 kernel: br0: port 1(vlan1) entering disabled state
Jan 28 21:58:28 kernel: br0: port 1(vlan1) entering listening state
Jan 28 21:58:28 kernel: br0: port 1(vlan1) entering learning state
Jan 28 21:58:28 kernel: br0: topology change detected, propagating
Jan 28 21:58:28 dnsmasq[1558]: read /etc/hosts - 5 addresses
Jan 28 21:58:28 dnsmasq[1558]: read /etc/hosts - 5 addresses
Jan 28 21:58:28 dnsmasq[1558]: using nameserver 192.168.100.1#53
Jan 28 21:58:28 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jan 28 21:58:28 dnsmasq[1558]: exiting on receipt of SIGTERM
Jan 28 21:58:28 dnsmasq[1581]: started, version 2.68 cachesize 1500
Jan 28 21:58:28 dnsmasq[1581]: asynchronous logging enabled, queue limit is 5 messages
Jan 28 21:58:28 dnsmasq-dhcp[1581]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d
Jan 28 21:58:28 dnsmasq-dhcp[1581]: DHCP, sockets bound exclusively to interface br0
Jan 28 21:58:28 dnsmasq[1581]: read /etc/hosts - 5 addresses
Jan 28 21:58:28 dnsmasq[1581]: using nameserver 192.168.100.1#53
Jan 28 21:58:28 rc_service: udhcpc 1563:notify_rc stop_upnp
Jan 28 21:58:28 rc_service: udhcpc 1563:notify_rc start_upnp
Jan 28 21:58:28 miniupnpd[1596]: HTTP listening on port 46606
Jan 28 21:58:28 miniupnpd[1596]: Listening for NAT-PMP traffic on port 5351
Jan 28 21:58:28 dhcp client: bound 192.168.100.50 via 192.168.100.1 during 10 seconds.
Jan 28 21:58:29 WAN Connection: WAN was restored.
Jan 28 21:59:08 dnsmasq[1581]: read /etc/hosts - 5 addresses
Jan 28 21:59:08 dnsmasq[1581]: using nameserver 192.168.100.1#53
Jan 28 21:59:08 miniupnpd[1596]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Jan 28 21:59:08 miniupnpd[1596]: Failed to get IP for interface eth0
Jan 28 21:59:08 miniupnpd[1596]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Jan 28 21:59:09 dnsmasq[1581]: read /etc/hosts - 5 addresses
Jan 28 21:59:09 dnsmasq[1581]: using nameserver 75.75.76.76#53
Jan 28 21:59:09 dnsmasq[1581]: using nameserver 75.75.75.75#53
Jan 28 21:59:09 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jan 28 21:59:09 dnsmasq[1581]: exiting on receipt of SIGTERM
Jan 28 21:59:09 dnsmasq[1624]: started, version 2.68 cachesize 1500
Jan 28 21:59:09 dnsmasq[1624]: asynchronous logging enabled, queue limit is 5 messages
Jan 28 21:59:09 dnsmasq-dhcp[1624]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d
Jan 28 21:59:09 dnsmasq-dhcp[1624]: DHCP, sockets bound exclusively to interface br0
Jan 28 21:59:09 dnsmasq[1624]: read /etc/hosts - 5 addresses
Jan 28 21:59:09 dnsmasq[1624]: using nameserver 75.75.76.76#53
Jan 28 21:59:09 dnsmasq[1624]: using nameserver 75.75.75.75#53
Jan 28 21:59:09 rc_service: udhcpc 1606:notify_rc stop_upnp
Jan 28 21:59:09 rc_service: udhcpc 1606:notify_rc start_upnp
Jan 28 21:59:09 miniupnpd[1639]: HTTP listening on port 34835
Jan 28 21:59:09 miniupnpd[1639]: Listening for NAT-PMP traffic on port 5351
Jan 28 21:59:09 dhcp client: bound 67.183.108.77 via 67.183.108.1 during 328991 seconds.

 

[RMerlin]

Jan 28 21:58:25 WAN Connection: Ethernet link down.

The Ethernet connection between your modem and your router actually went down. Most of the time, this is a sign of the modem having crashed and rebooting itself.

Start by replacing the Ethernet cable between both in case it would just be a simple cable issue, otherwise try to keep a close eye on your modem to confirm that it did reboot itself. If it did, I would replace the modem.

 

[stage]

Thanks - I'll try switching out the cable. I didn't think it was a modem reboot problem because I kept an eye on the LED's and they didn't flicker or go off during periods where I lost connection.

 

[stage]

The Ethernet connection between your modem and your router actually went down. Most of the time, this is a sign of the modem having crashed and rebooting itself.

Start by replacing the Ethernet cable between both in case it would just be a simple cable issue, otherwise try to keep a close eye on your modem to confirm that it did reboot itself. If it did, I would replace the modem.

New Ethernet cable, same problem. I guess I'll see if I can get a cable technician over here to try a new modem.

 

[balwx]

Greetings. I came across this forum this evening, searching for solutions since September for my internet dropouts. I believe I am in a very similar situation as others here so here I am. I will try to give as many of the details without taking too much of your time.

Comcast internet 50/10
Modem: Zoom 5314J
Router: Asus RT-N66U FW: 3.0.0.4.374_979

Every so often (sometimes 3 times a day, sometimes 3 time a week), my internet seems to drop out for 2-3 minutes. The DS & US solid blue light on the Zoom with begin to blink and the modem will go through a complete recycle & reconnect with 2-3 minutes. All computers connected to the router go offline during the 2-3 minutes, then reconnect after the modem 'recycles'.

I have had Comcast over 2 times with their meters telling me all signals are fine well within spec, as well as phone tech support people (who can see two readings not visible to field personnel ?) All wiring is RG6 quad, Comcast installed fittings etc... Modem is on 20' homerun cable.

I read stories in this thread, and it seems there is a possible issue with the Asus FW? I changed a setting DHCP query frequency to 'normal' & rebooted the router a few minutes ago. If I followed correctly, I believe that was a suggestion here.

Comcast told me today there is no evidence of the modem going offline today (if it reconnects within 10-15 minutes, not noticeable to them ?), I know the light cycled through at least twice while I was using the computer.

If anyone has some suggestions, they are greatly appreciated! Thanks

Ant

 

[RMerlin]

Every so often (sometimes 3 times a day, sometimes 3 time a week), my internet seems to drop out for 2-3 minutes. The DS & US solid blue light on the Zoom with begin to blink and the modem will go through a complete recycle & reconnect with 2-3 minutes.

This right there is definitely 100% modem-side, and has nothing to do with the router. Most likely the modem is defective/flaky, and should be replaced.

That kind of issue might not register as poor signals from the ISP's end if it's the modem randomly crashing and rebooting. The modem most likely needs to be replaced.

A quick reboot might indeed not be visible from their end (for the same reason that a cablemodem must be turned off for 5-15 mins if you need to REALLY reset the connection with your ISP).

 

[balwx]

This right there is definitely 100% modem-side, and has nothing to do with the router. Most likely the modem is defective/flaky, and should be replaced.

That kind of issue might not register as poor signals from the ISP's end if it's the modem randomly crashing and rebooting. The modem most likely needs to be replaced.

A quick reboot might indeed not be visible from their end (for the same reason that a cablemodem must be turned off for 5-15 mins if you need to REALLY reset the connection with your ISP).

Thanks so much for the quick response. Originally, I had the Motorola SB6141 modem when this started (modem drop outs). After reading threads about the disconnects, I then switched to the current Zoom 5341J since I heard it was less prone to reboots.

I am wondering if I need to get Comcast back for a 3rd time ? It's interesting because I have read a lot of threads with the same problem I am having. At the same time, Comcast is telling me the signals are all well within spec.

 

[RMerlin]

Thanks so much for the quick response. Originally, I had the Motorola SB6141 modem when this started (modem drop outs). After reading threads about the disconnects, I then switched to the current Zoom 5341J since I heard it was less prone to reboots.

I am wondering if I need to get Comcast back for a 3rd time ? It's interesting because I have read a lot of threads with the same problem I am having. At the same time, Comcast is telling me the signals are all well within spec.

Tell them what you can visually observe on the modem. That is a sure sign that they can't just ignore by hiding behind the numbers they see on their own equipment.

 

[balwx]

Tell them what you can visually observe on the modem. That is a sure sign that they can't just ignore by hiding behind the numbers they see on their own equipment.

Thank you so much, appreciate it.

 

[it4geeks]

I have the WAN disconnection problem too

I have: RT-AC66U

Current firmware: 3.0.0.4.374_5517

After a few minutes of using the router, the WAN disconnects and 2 messages appears after the disconnect:

WAN Connection: ISP's DHCP did not function properly.
stop_nat_rules: apply the redirect_rules!

I have to reboot the router in order to get the WAN back. And the WAN changes the IP address, not common with my ISP since you get the same IP for at least 6 months with same mac address.

I tried all the firmwares. With 3.0.0.4.372 and 3.0.0.4.374.130 i don't have that WAN disconnects

I bought this router to use Dual WAN feature (Cablemodem + 4G modem). Works perfect, but the WAN (cablemodem) keeps disconnecting with this messages:

WAN Connection: ISP's DHCP did not function properly.
stop_nat_rules: apply the redirect_rules!

Note: I have disabled the Dual WAN feature 2 days ago, and the router is now stable. I have the same IP for 2 days. Is this feature Dual WAN unstable or what? The first 2 firmwares doesn't have Dual WAN feature and the router was stable too.

Note 2: It is the first time i face a problem like this. Cablemodem is working for 3 years with Linksys routers, i had a RT-16N too and worked like a charm. The cablemodem is NOT the problem i think.

Any ideas? Merlin?

Regards

Ariel Ramos

 

[rassi]

Currently using RT-AC68u with newest (3.0.0.4.374_5517) stock firmware.
I do have ADSL and Cablemodem (trying to use dual-WAN failsafe) lines and both lines keeps doing this even removed dual WAN and using ADSL only at the moment. Do i have that bad luck? Both modems broken at the same time?


May 3 07:08:46 WAN(0) Connection: ISP's DHCP did not function properly.

May  3 07:08:46 rc_service: htctpd 521:notify_rc restart_wan_if 0
May  3 07:08:46 dnsmasq[515]: read /etc/hosts - 5 addresses
May  3 07:08:46 dnsmasq-dhcp[515]: read /etc/ethers - 10 addresses
May  3 07:08:46 dnsmasq[515]: using nameserver 8.8.8.8#53
May  3 07:08:46 dnsmasq[515]: using nameserver 8.8.8.6#53
May  3 07:08:46 stop_wan(): perform DHCP release
May  3 07:08:46 kernel: Attempt to kill tasklet from interrupt
May  3 07:08:46 kernel: device eth0 left promiscuous mode
May  3 07:08:46 kernel: br0: port 1(vlan1) entering forwarding state
May  3 07:08:46 kernel: device eth0 entered promiscuous mode
May  3 07:08:46 kernel: br0: topology change detected, propagating
May  3 07:08:46 kernel: br0: port 1(vlan1) entering forwarding state
May  3 07:08:46 kernel: br0: port 1(vlan1) entering forwarding state
May  3 07:08:46 dnsmasq[515]: read /etc/hosts - 5 addresses
May  3 07:08:46 dnsmasq-dhcp[515]: read /etc/ethers - 10 addresses
May  3 07:08:46 dnsmasq[515]: using nameserver 8.8.8.8#53
May  3 07:08:46 dnsmasq[515]: using nameserver 8.8.8.6#53
May  3 07:08:46 dnsmasq[515]: read /etc/hosts - 5 addresses
May  3 07:08:46 dnsmasq-dhcp[515]: read /etc/ethers - 10 addresses
May  3 07:08:46 dnsmasq[515]: using nameserver 8.8.8.8#53
May  3 07:08:46 dnsmasq[515]: using nameserver 8.8.4.4#53
May  3 07:08:46 WAN(0) Connection: ISP's DHCP did not function properly.
May  3 07:08:46 stop_nat_rules: apply the redirect_rules!
May  3 07:08:47 dnsmasq[515]: read /etc/hosts - 5 addresses
May  3 07:08:47 dnsmasq-dhcp[515]: read /etc/ethers - 10 addresses
May  3 07:08:47 dnsmasq[515]: using nameserver 8.8.8.8#53
May  3 07:08:47 dnsmasq[515]: using nameserver 8.8.4.4#53
May  3 07:08:48 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
May  3 07:08:48 rc_service: udhcpc 10684:notify_rc stop_upnp
May  3 07:08:48 rc_service: udhcpc 10684:notify_rc start_upnp
May  3 07:08:48 rc_service: waitting "stop_upnp" via udhcpc ...
May  3 07:08:48 miniupnpd[10530]: received signal 15, good-bye
May  3 07:08:49 rc_service: udhcpc 10684:notify_rc stop_vpnserver1
May  3 07:08:49 rc_service: udhcpc 10684:notify_rc start_vpnserver1
May  3 07:08:49 rc_service: waitting "stop_vpnserver1" via udhcpc ...
May  3 07:08:49 syslog: SNet version started
May  3 07:08:49 miniupnpd[10724]: HTTP listening on port 46025
May  3 07:08:49 miniupnpd[10724]: Listening for NAT-PMP traffic on port 5351
May  3 07:08:50 openvpn[10637]: event_wait : Interrupted system call (code=4)
May  3 07:08:50 openvpn[10637]: /sbin/route del -net 10.8.0.0 netmask 255.255.255.0
May  3 07:08:50 openvpn[10637]: Closing TUN/TAP interface
May  3 07:08:50 openvpn[10637]: /sbin/ifconfig tun21 0.0.0.0
May  3 07:08:51 openvpn[10637]: PLUGIN_CLOSE: /usr/lib/openvpn-plugin-auth-pam.so
May  3 07:08:51 openvpn[10637]: SIGTERM[hard,] received, process exiting
May  3 07:08:52 dhcp client: bound 109.1xx.x.xxx via 109.1xx.xxx.x during 18000 seconds.
May  3 07:08:53 kernel: tun: Universal TUN/TAP device driver, 1.6
May  3 07:08:53 kernel: tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
May  3 07:08:53 WAN(0) Connection: WAN was restored.
May  3 07:08:54 kernel: ADDRCONF(NETDEV_UP): tun21: link is not ready
May  3 07:08:54 kernel: device tun21 entered promiscuous mode
May  3 07:08:54 openvpn[10782]: OpenVPN 2.3.2 arm-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [eurephia] [MH] [IPv6] built on Apr 14 2014
May  3 07:08:54 openvpn[10782]: PLUGIN_INIT: POST /usr/lib/openvpn-plugin-auth-pam.so '[/usr/lib/openvpn-plugin-auth-pam.so] [openvpn]' intercepted=PLUGIN_AUTH_USER_PASS_VERIFY 
May  3 07:08:54 openvpn[10782]: Diffie-Hellman initialized with 512 bit key

 

[rassi]

This is weird. See picture.



Incoming connections does work even if Asus router says 0.0.0.0 for IP.. and outgoing do not work then.

Need to go to WAN settings to push Apply to get IP and if i want and start browsing.

 

[octopus]

Try to remove your nameserver settings and test again:

May  3 07:08:46 dnsmasq[515]: using nameserver 8.8.8.8#53
May  3 07:08:46 dnsmasq[515]: using nameserver 8.8.8.6#53

When you have WAN connection, what Ip-number do you have then?

Some provider block you a while when you have tested mych in a short time.
Uplug for ~10min and test again.
Change "DHCP query frequency" from "Aggressive mode" to "Normal mode", uplug ~10min and test again.

 

[rassi]

Try to remove your nameserver settings and test again:

May  3 07:08:46 dnsmasq[515]: using nameserver 8.8.8.8#53
May  3 07:08:46 dnsmasq[515]: using nameserver 8.8.8.6#53

When you have WAN connection, what Ip-number do you have then?

Some provider block you a while when you have tested mych in a short time.
Uplug for ~10min and test again.
Change "DHCP query frequency" from "Aggressive mode" to "Normal mode", uplug ~10min and test again.

Thanks. Added Goodle DNS´s to test if it will help, but no. Same thing for Normal mode, it were Aggressive but now Normal. Need to do factory reset and clean install for Merlin. This is hilarious, i do have cable modem + ADSL, but using now 3G connection

Something to do with the router as server connection from out to home do work pretty stable i think.


edit: When i do have working internet connection from home, IP is normal from ISP, like now when it´s not working it shows 0.0.0.0 as in picture. I can get connection back when push apply to WAN settings, but it wont last long.

and if factory reset for Asus + Merlin won´t give any help, i´ll need to test my old router again to see behaviour with it.

 

[RMerlin]

This is weird. See picture.



Incoming connections does work even if Asus router says 0.0.0.0 for IP.. and outgoing do not work then.

Need to go to WAN settings to push Apply to get IP and if i want and start browsing.

Disable "Enable VPN + DHCP Connection" on the WAN page.

 

[rassi]

Disable "Enable VPN + DHCP Connection" on the WAN page.

Cant see that kind of item?



Checked all WAN tabs without an luck