What's new

RT-AC66U - 3G/4G backup mode issue

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Good idea!

I removed your Martineau customcode as suggested and added the bootinprogress statement, but at reboot it seems that still execute your code and not exit?


#!/bin/sh
logger -t "($(basename $0))" $$ Martineau customisation starting.... " $0${*:+ $
# With DUAL-WAN, this event gets triggered for both DSL and 3G
# True REBOOT in progress? see init-start
if [ -e /tmp/BOOTINPROGRESS ]; then
BOOTINPROGRESS="YES"
exit
else
# If Semaphore Lock file exists then exit
if [ -e /tmp/wan-start-locked ]; then
....................................... a
 
Good idea!

I removed your Martineau customcode as suggested and added the bootinprogress statement, but at reboot it seems that still execute your code and not exit?


#!/bin/sh
logger -t "($(basename $0))" $$ Martineau customisation starting.... " $0${*:+ $
# With DUAL-WAN, this event gets triggered for both DSL and 3G
# True REBOOT in progress? see init-start
if [ -e /tmp/BOOTINPROGRESS ]; then
BOOTINPROGRESS="YES"
exit
else
# If Semaphore Lock file exists then exit
if [ -e /tmp/wan-start-locked ]; then
....................................... a



as per the comment....did you also modify the init-start script?

i.e. here is mine....

Code:
#!/bin/sh

/usr/bin/logger -t "($(basename $0))" $$ "Martineau RT-N66U BOOT in progress... [$@]" 

# NOTE: Can't use Flash drive /tmp/mnt/RT-N66U/ 'cos it hasn't been mounted yet :-(

echo `date` > /tmp/BOOTINPROGRESS

# If we ensure that the mount point exists at this stage of the boot, it can eliminate the Hotplug boot error?
#   hotplug[427]: USB /dev/sdxn (ext4) failed to mount at the first try! 
#mkdir -p /tmp/mnt/RT-N66U

#Should be sufficient to cover physical boot process?
sleep 150

rm /tmp/BOOTINPROGRESS

# Move Syslog to USB Flash drive
/jffs/scripts/syslog-move.sh

/usr/bin/logger -t "($(basename $0))" $$ "Martineau RT-N66U BOOT Completed [$@]"

Regards,
 
created the init-start and now all working fine, great scripts thanks! Only one thing the wan-start seems to be called each time the VPN server starts but I do not think is doing any arm.....................
 
created the init-start and now all working fine, great scripts thanks! Only one thing the wan-start seems to be called each time the VPN server starts but I do not think is doing any arm.....................

Not sure if wan-start being called for a VPN server start is specific to the RT-AC66U as I have the RT-N66U.

On my RT-N66U, bouncing the OpenVPN server does not invoke the wan-start script, and bouncing the PPTP server only invokes the nat-start and firewall-start script, again no wan-start script was executed.

Perhaps RMerlin can confirm that this is the expected RT-AC66U behaviour.

Regards,
 
Not sure if wan-start being called for a VPN server start is specific to the RT-AC66U as I have the RT-N66U.

On my RT-N66U, bouncing the OpenVPN server does not invoke the wan-start script, and bouncing the PPTP server only invokes the nat-start and firewall-start script, again no wan-start script was executed.

Perhaps RMerlin can confirm that this is the expected RT-AC66U behaviour.

Regards,

wan-start is only called when WAN is started. At boot time both WAN and VPN get started, which is probably why it seems to work.
 
I have an rtn66u as well....

Sorry I did more testing and the VPN doesn't call the script. I was mislead because after a vpn connection I had an LCP terminated by peer and thought it was the VPN... I had another LCP today, after googling it seems that the internet connection is down, but I don't see wan down like if you disconnect the cable.... or wan restored....

The script is working fine... :)

Code:
Oct 30 18:40:20 dnsmasq-dhcp[497]: DHCPACK(br0) 192.168.1.170 78:52:1a:c1:04:bd android-2ad5680ffb02eee
Oct 30 20:01:43 pppd[417]: LCP terminated by peer
Oct 30 20:01:43 pppd[417]: Connect time 1440.1 minutes.
Oct 30 20:01:43 pppd[417]: Sent 10 bytes, received 0 bytes.
Oct 30 20:01:43 dnsmasq[497]: read /etc/hosts - 5 addresses
Oct 30 20:01:43 dnsmasq[497]: using nameserver 10.1.13.66#53
Oct 30 20:01:43 dnsmasq[497]: using nameserver 10.1.13.65#53
Oct 30 20:01:43 dnsmasq[497]: using nameserver 89.101.160.5#53
Oct 30 20:01:43 dnsmasq[497]: using nameserver 89.101.160.4#53
Oct 30 20:01:43 pppd[417]: Modem hangup
Oct 30 20:01:43 pppd[417]: Connection terminated.
Oct 30 20:01:58 pppd[417]: Serial connection established.
Oct 30 20:01:58 pppd[417]: Using interface ppp0
Oct 30 20:01:58 pppd[417]: Connect: ppp0 <--> /dev/ttyUSB0
Oct 30 20:02:02 pppd[417]: Could not determine remote IP address: defaulting to 10.64.64.64
Oct 30 20:02:02 pppd[417]: not replacing existing default route via 109.255.210.1
Oct 30 20:02:02 pppd[417]: local  IP address 10.4.67.202
Oct 30 20:02:02 pppd[417]: remote IP address 10.64.64.64
Oct 30 20:02:02 pppd[417]: primary   DNS address 10.1.13.65
Oct 30 20:02:02 pppd[417]: secondary DNS address 10.1.13.66
Oct 30 20:02:02 dnsmasq[497]: read /etc/hosts - 5 addresses
Oct 30 20:02:02 dnsmasq[497]: using nameserver 10.1.13.66#53
Oct 30 20:02:02 dnsmasq[497]: using nameserver 10.1.13.65#53
Oct 30 20:02:02 dnsmasq[497]: using nameserver 89.101.160.5#53
Oct 30 20:02:02 dnsmasq[497]: using nameserver 89.101.160.4#53
Oct 30 20:02:02 (wan-start): 1045 Martineau customisation starting....  /jffs/scripts/wan-start 1.
Oct 30 20:02:02 (wan-start): 1045 wan-start LOCKED Wed Oct 30 20:02:02 DST 2013
Oct 30 20:02:02 (wan-start): 1045 NTP client setting time UK.POOL.NTP.ORG
Oct 30 20:02:32 (wan-start): 1045 wan-start UNLOCKED Wed Oct 30 20:02:02 DST 2013
Oct 30 20:02:32 (wan-start): 1045 Martineau customisation complete....
Oct 30 21:13:48 dnsmasq-dhcp[497]: DHCPDISCOVER(br0) 00:06:dc:82:7a:02 
Oct 30 21:13:48 dnsmasq-dhcp[497]: DHCPOFFER(br0) 192.168.1.150 00:06:dc:82:7a:02
 
I could be wrong, but the log seems to show that the 3G connection was terminated after 24hrs (1440) minutes, as I suspect that as the 3G modem is sitting 'idle' maybe your ISP thought it was 'dead'?

Clearly my wan-start script is only designed to effect the switch back from 3G to the WAN when it becomes available, so simply did nothing as the WAN connection was presumably ACTIVE throughout. ;)

It would be interesting to see what would happen if the WAN connection was lost at precisely the same time as this 3G LCP peer disconnect :eek:


Regards,
 
That's strange, same time tonight as the previous log?????? !!!!!!!!

Code:
Oct 31 20:02:00 pppd[417]: LCP terminated by peer
Oct 31 20:02:00 pppd[417]: Connect time 1440.0 minutes.
Oct 31 20:02:00 pppd[417]: Sent 10 bytes, received 0 bytes.
Oct 31 20:02:00 dnsmasq[497]: read /etc/hosts - 5 addresses
Oct 31 20:02:00 dnsmasq[497]: using nameserver 10.1.13.66#53
Oct 31 20:02:00 dnsmasq[497]: using nameserver 10.1.13.65#53
Oct 31 20:02:00 dnsmasq[497]: using nameserver 89.101.160.5#53
Oct 31 20:02:00 dnsmasq[497]: using nameserver 89.101.160.4#53
Oct 31 20:02:01 pppd[417]: Modem hangup
Oct 31 20:02:01 pppd[417]: Connection terminated.
Oct 31 20:02:16 pppd[417]: Serial connection established.
Oct 31 20:02:16 pppd[417]: Using interface ppp0
Oct 31 20:02:16 pppd[417]: Connect: ppp0 <--> /dev/ttyUSB0
Oct 31 20:02:18 pppd[417]: Could not determine remote IP address: defaulting to 10.64.64.64
Oct 31 20:02:18 pppd[417]: not replacing existing default route via 109.255.210.1
Oct 31 20:02:18 pppd[417]: local  IP address 10.4.36.227
Oct 31 20:02:18 pppd[417]: remote IP address 10.64.64.64
Oct 31 20:02:18 pppd[417]: primary   DNS address 10.1.13.65
Oct 31 20:02:18 pppd[417]: secondary DNS address 10.1.13.66
Oct 31 20:02:18 dnsmasq[497]: read /etc/hosts - 5 addresses
Oct 31 20:02:18 dnsmasq[497]: using nameserver 10.1.13.66#53
Oct 31 20:02:18 dnsmasq[497]: using nameserver 10.1.13.65#53
Oct 31 20:02:18 dnsmasq[497]: using nameserver 89.101.160.5#53
Oct 31 20:02:18 dnsmasq[497]: using nameserver 89.101.160.4#53
Oct 31 20:02:19 (wan-start): 1251 Martineau customisation starting....  /jffs/scripts/wan-start 1.
Oct 31 20:02:19 (wan-start): 1251 wan-start LOCKED Thu Oct 31 20:02:19 DST 2013
Oct 31 20:02:19 (wan-start): 1251 NTP client setting time UK.POOL.NTP.ORG
Oct 31 20:02:49 (wan-start): 1251 wan-start UNLOCKED Thu Oct 31 20:02:19 DST 2013
Oct 31 20:02:49 (wan-start): 1251 Martineau customisation complete....
Oct 31 22:14:38 dnsmasq-dhcp[497]: DHCPDISCOVER(br0) 00:06:dc:82:7a:02
 
Well 3G/4G is really a challenge for ASUS



TP-Link and open source development



http://ofmodemsandmen.com/test/index.html



But... I have tried but ASUS is on the stone-age....:eek:


Thanks a lot for pointing out this open source project. It looks interesting indeed!

I'm currently looking a way to add a 3G failover to my home network. I was pretty convinced about buying a 66U (N or AC, not sure yet), but as it seems to represent such a hurdle for Asus I may reconsider the brand of choice and go for tp-link instead.

Are there any news regarding this? @Merlin, do you depend on Asus for providing a user friendly 3/4G failover?

Thanks
 
Last edited:
Thanks a lot for pointing out this open source project. It looks interesting indeed!
Thanks

Well, I found one even better in Shibbys Tomato firmware.

Real LTE/4G high speed support with the cdc_ncm driver included.:D

The ROOter project is also a great project for cheaper routers.
 
Thanks a lot for pointing out this open source project. It looks interesting indeed!

I'm currently looking a way to add a 3G failover to my home network. I was pretty convinced about buying a 66U (N or AC, not sure yet), but as it seems to represent such a hurdle for Asus I may reconsider the brand of choice and go for tp-link instead.

Are there any news regarding this? @Merlin, do you depend on Asus for providing a user friendly 3/4G failover?

I leave all the dualwan and 3G/4G code in Asus's hands, as I lack 1) the time to also devote at the complex DualWAN code, which Asus still extensively changes between new releases, and 2) a mean to test anything 3G/4G related.

At one point it might be an idea for someone to start a Dual-WAN specific thread in the Asus Wireless sub-forum here, and have Asusnet referred to that thread. He can collect all the user feedback and forward it to development then if some specific issues are reported with enough details. That's what I was doing with that PPPoE thread BTW, but looks like Asus already fixed it internally before I could forward the feedback to them.
 
At one point it might be an idea for someone to start a Dual-WAN specific thread in the Asus Wireless sub-forum here, and have Asusnet referred to that thread. He can collect all the user feedback and forward it to development then if some specific issues are reported with enough details. That's what I was doing with that PPPoE thread BTW, but looks like Asus already fixed it internally before I could forward the feedback to them.

Merlin, thanks for stepping in. I've learned about your alternate firmware project today and I must say I'm pretty surprised. What a great job!!

If 3g failover support is not working as expected, I 100% agree with you that it would be best to give Asus visibility on this. Unfortunatelly I don't yet own an Asus router and, thus, I think it would be not appropriate for me to open it.

May I ask where does it fall short?

thanks
 
I recommend waiting a bit tho. The latest GPL code includes a few changes related to 3G/4G modems. Those fixes are included in the new AC68U firmware that Asus released today. They might not resolve recovery from a primary WAN failure (I don't know), but it should take care of other issues. Some of the changes also involved support for Android phones in tether mode.
 
They might not resolve recovery from a primary WAN failure (I don't know), but it should take care of other issues.
It would be great if somebody could check that out and report back on that issue. I'm about to pull the trigger and get myself an Asus router, but since I switched network provider recently, I was given a cheap TP-Link router, on which I recently installed dd-wrt a few days ago; I can hold out a bit for some news from Asus with regard to this problem.

One question, has Asus posted any formal documentation regarding 3G backup? When I look into the RT-N66U or RT-AC66U (the two candidates I'm currently considering), I don't see any reference to 3G back-up.

@Merlin, a little off-topic but what's your opinion between the RT-N66U and RT-AC66U? Which one would you buy If you were to get your primary home router? I don't have any AC devices yet apart from our smartphones and tablets (1 iPhone 5S, 1 iPhone 5, 1 iPad Mini 1st gen and 1 iPad Mini 2nd gen). Apart from our 2011 MacBook Air, we don't use any wireless device; all our networked equipment is hardwired with CAT 5e to my 8-ports gigabit switch... I don't think I currently need AC, but purchasing a router which does not support AC speed does not sound appropriate. In case you consider that this discussion is being held in a specific thread, would you care to point me to it?

Thanks a million in advance,
 
One question, has Asus posted any formal documentation regarding 3G backup? When I look into the RT-N66U or RT-AC66U (the two candidates I'm currently considering), I don't see any reference to 3G back-up.

The option is under the USB tab.

@Merlin, a little off-topic but what's your opinion between the RT-N66U and RT-AC66U? Which one would you buy If you were to get your primary home router? I don't have any AC devices yet apart from our smartphones and tablets (1 iPhone 5S, 1 iPhone 5, 1 iPad Mini 1st gen and 1 iPad Mini 2nd gen). Apart from our 2011 MacBook Air, we don't use any wireless device; all our networked equipment is hardwired with CAT 5e to my 8-ports gigabit switch... I don't think I currently need AC, but purchasing a router which does not support AC speed does not sound appropriate. In case you consider that this discussion is being held in a specific thread, would you care to point me to it?

I prefer the AC66. The N66 was kinda crippled by the switch to the new wireless driver, and builds based on the old driver are kind of a dead-end as they won't get improved in any way. Provided a good deal can be had on the AC66, which hasn't dropped in price as dramatically as the N66 yet.
 
RMerlin said:
I prefer the AC66. The N66 was kinda crippled by the switch to the new wireless driver, and builds based on the old driver are kind of a dead-end as they won't get improved in any way. Provided a good deal can be had on the AC66, which hasn't dropped in price as dramatically as the N66 yet.

Ok, no n66u then :)

Provided I will be looking into the AC family, why not the 68U then? I think I've read somewhere that you now a 66U right?
 
Last edited:
@Merlin, I've just contacted Asus via twitter about this. I'll report back if they ever respond.

Thanks
 
Ok, no n66u then :)

Provided I will be looking into the AC family, why not the 68U then? I think I've read somewhere that you now a 66U right?

AC68 is quite expensive right now. If it fits your budget, then go for it - it's definitely a better router than the AC66.

My main router here is currently the AC68, the others are delegated to development duties. It's been perfectly stable for me.
 
Do you still use those scripts or have it been some progress or development ???
If so please share
else I'm going to give this a try, asis.
 

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top