Asuswrt-Merlin 3.0.0.4.372.30_2

[RMerlin]

HI Merlin,
Thanks for your hard work!
I use dyndns.org. How do I get the system logs to you since I have reverted back to the .29 firmware?

dyndns.org (free account) is what I use myself and I have no problem. How are you testing DDNS to confirm whether it's working or not?

 

[cariyawa]

First of all, I want to thank Merlin for his excellent work. I tried other alternative firmwares and this is the best. It gives me the best signal strength and best stability.

I noticed one problem when I hide my SSID. Of course it hides the SSID but the router shows ASUS as the SSID with security enabled. May be it is a bug? Not sure.

I am using your most recent firmware(RT-N16_3.0.0.4_372.30_0) on RT-N16.

 

[RMerlin]

First of all, I want to thank Merlin for his excellent work. I tried other alternative firmwares and this is the best. It gives me the best signal strength and best stability.

I noticed one problem when I hide my SSID. Of course it hides the SSID but the router shows ASUS as the SSID with security enabled. May be it is a bug? Not sure.

I am using your most recent firmware(RT-N16_3.0.0.4_372.30_0) on RT-N16.

Where is it showing it, at the top of the webui, or on the Networkmap page (the first page that shows when logging in)? Is it also doing the same with the original Asus FW?

 

[Etz]

will do factory default later and try after that.

It worked, looks like it was something in router Configuration, which prevented upgrade.

 

[cariyawa]

It shows in my computer's list of wireless networks.

More added:
I didn't check it in original Asus FW.

 

[RMerlin]

Yes, that's the chrome extension that I use, and it does make it very easy to verify that IPv6 is up after updating firmware. Good stuff.

And yes, I don't have this line in my system log:

"no auto-selected prefix on interface br0, disabling advertisements"

which sounds very much like things aren't working right. The lines that I have in my log instead are:

Jul 6 10:48:43 radvd[472]: attempting to reread config file
Jul 6 10:48:43 radvd[472]: resuming normal operation

The IPv6 log that I have is very similar to the OP's above, except it lists my desktop system under "IPv6 LAN Devices List". Otherwise, it is 1:1 with the OP's IPv6 log, except it has the addresses allocated to me, of course *smile*. I've also checked the other hardwired and wireless devices in my house, and all also have working IPv6, so radvd is doing its job.

You two might want to compare your IPv6 settings. Try this through the Tools -> Run Cmd page:

nvram show | grep ipv6

@saintdev: Try turning your modem off for about 5-10 mins, then turn it back on, to force a complete reset of your connection. I remember some Comcast IPv6 users fixing weird issues this way in the past.

 

[RMerlin]

It shows in my computer's list of wireless networks.

More added:
I didn't check it in original Asus FW.

Are you sure it's not because you had it configured in the past under the default name, and Windows simply remembered it? Try using a tool like InSSIDer to see what's actually visible.

I'll try to see in the next days if I can reproduce it.

 

[theirongiant]

Hello RMerlin,

Thank you for your hard work. I will definitely be sending $$$ your way.

I reset my router back to factory defaults after upgrading to .372.30, and the wireless settings now work correctly on both bands.

I will be updating to .30_2 shortly.

 

[cariyawa]

Are you sure it's not because you had it configured in the past under the default name, and Windows simply remembered it? Try using a tool like InSSIDer to see what's actually visible.

I'll try to see in the next days if I can reproduce it.

I am using a Linux box. It seems to me that you are exactly right. My Linux box was playing tricks on me. Thanks Merlin!

 

[RMerlin]

I just noticed one change related to CTF... In 354, Asus was disabling CTF if you had IPv6 enabled. I just saw that now they do that only for the ARM routers. Weird... Must be something different in the CTF build used by ARM devices.

I'll have to update the Sysinfo page for this...

 

[RogerSC]

You two might want to compare your IPv6 settings. Try this through the Tools -> Run Cmd page:

nvram show | grep ipv6

Okay, here's the output that I see from the above command, hope that it helps. If I had source code, I could see what conditions cause the various log messages to come out or not, but I don't, and don't know if the relevant source code is even available. I've also replaced some of the address digits below with "x"'s, since I don't want addresses showing *smile*. Ipv6_rtr_addr below is the router's address.

I'm also assuming that when the OP upgraded to this new firmware that they cleared their nvram after upgrading and re-entered your settings manually. That's what I generally do, unless the versions are very close, and have few problems as a result:

ASUSWRT RT-N66U_3.0.0.4 Sat Jul 6 01:07:48 UTC 2013
admin@RT-N66U:/tmp/home/root# nvram show | grep ipv6
size: 34119 bytes (31417 left)
ipv6_6rd_ip4size=0
ipv6_tun_v4end=0.0.0.0
ipv6_accept_ra=1
ipv6_get_dns=2001:558:feed::1 2001:558:feed::2
ipv6_dhcppd=1
ipv6_ipaddr=
ipv6_state_t=0
ipv6_prefix=2601:9:xxxx:xx::
ipv6_ifdev=eth
ipv6_service=dhcp6
ipv6_tun_addrlen=64
ipv6_gateway=
ipv6_ifname=six0
ipv6_prefix_length=64
rc_support=mssid 2.4G 5G update usbX2 switchctrl manual_stb pwrctrl optimize_xbox ipv6 PARENTAL2 pptpd printer modem wimax openvpnd HTTPS webdav cloudsync appbase media diskutility nfsd
ipv6_ll_remote=
ipv6_dnsenable=1
ipv6_6rd_prefix=
ipv6_sbstate_t=0
ipv6_debug=0
ipv6_6rd_router=0.0.0.0
ipv6_dhcp_end=
ipv6_autoconf_type=0
ipv6_gw_addr=fe80::xxx:xxxx:xxxx:xxxx
ipv6_rtr_addr=2601:9:xxxx:xx:xxxx:xx:xxxx:xxxx
ipv6_dhcp_pd=1
ipv6_6rd_prefixlen=32
ipv6_tun_mtu=0
ipv6_tun_addr=
ipv6_tun_ttl=255
ipv6_dns1=
ipv6_dns2=
ipv6_dns3=
ipv6_get_domain=
ipv6_prefix_len_wan=64
ipv6_radvd=1
ipv6_dhcp_start=
ipv6_dhcp_lifetime=86400
ipv6_6rd_dhcp=1
ipv6_relay=192.88.99.1
admin@RT-N66U:/tmp/home/root#

 

[saintdev]

I'm also assuming that when the OP upgraded to this new firmware that they cleared your nvram after upgrading and re-entered your settings manually.

Sure did.

ASUSWRT RT-N66U_3.0.0.4 Sat Jul  6 01:07:48 UTC 2013
admin@RT-N66U:/tmp/home/root# nvram show | grep ipv6
size: 34119 bytes (31417 left)
ipv6_6rd_ip4size=0
ipv6_tun_v4end=0.0.0.0
ipv6_accept_ra=1
ipv6_get_dns=2001:558:feed::1 2001:558:feed::2
ipv6_dhcppd=1
ipv6_ipaddr=
ipv6_state_t=0
ipv6_prefix=2601:9:xxxx:xx::
ipv6_ifdev=eth
ipv6_service=dhcp6
ipv6_tun_addrlen=64
ipv6_gateway=
ipv6_ifname=six0
ipv6_prefix_length=64
rc_support=mssid 2.4G 5G update usbX2 switchctrl manual_stb pwrctrl optimize_xbox ipv6 PARENTAL2 pptpd printer modem wimax openvpnd HTTPS webdav cloudsync appbase media diskutility nfsd
ipv6_ll_remote=
ipv6_dnsenable=1
ipv6_6rd_prefix=
ipv6_sbstate_t=0
ipv6_debug=0
ipv6_6rd_router=0.0.0.0
ipv6_dhcp_end=
ipv6_autoconf_type=0
ipv6_gw_addr=fe80::xxx:xxxx:xxxx:xxxx
ipv6_rtr_addr=2601:9:xxxx:xx:xxxx:xx:xxxx:xxxx
ipv6_dhcp_pd=1
ipv6_6rd_prefixlen=32
ipv6_tun_mtu=0
ipv6_tun_addr=
ipv6_tun_ttl=255
ipv6_dns1=
ipv6_dns2=
ipv6_dns3=
ipv6_get_domain=
ipv6_prefix_len_wan=64
ipv6_radvd=1
ipv6_dhcp_start=
ipv6_dhcp_lifetime=86400
ipv6_6rd_dhcp=1
ipv6_relay=192.88.99.1
admin@RT-N66U:/tmp/home/root#

Excluding the IPv6 address(es), mine's identical

ASUSWRT RT-N66U_3.0.0.4 Sat Jul  6 01:07:48 UTC 2013
admin@RT-N66U:/tmp/home/root# nvram show | grep -i ipv6
size: 35545 bytes (29991 left)
ipv6_6rd_ip4size=0
ipv6_tun_v4end=0.0.0.0
ipv6_accept_ra=1
ipv6_get_dns=2001:558:feed::2 2001:558:feed::1
ipv6_dhcppd=1
ipv6_ipaddr=
ipv6_state_t=0
ipv6_prefix=
ipv6_ifdev=eth
ipv6_service=dhcp6
ipv6_tun_addrlen=64
ipv6_gateway=
ipv6_ifname=six0
ipv6_prefix_length=64
rc_support=mssid 2.4G 5G update usbX2 switchctrl manual_stb pwrctrl optimize_xbox ipv6 PARENTAL2 pptpd printer modem wimax openvpnd HTTPS webdav cloudsync appbase media diskutility nfsd
ipv6_ll_remote=
ipv6_dnsenable=1
ipv6_6rd_prefix=
ipv6_sbstate_t=0
ipv6_debug=0
ipv6_6rd_router=0.0.0.0
ipv6_dhcp_end=
ipv6_autoconf_type=0
ipv6_gw_addr=fe80::xxxx:xxxx:xxxx:xxxx
ipv6_dhcp_pd=1
ipv6_6rd_prefixlen=32
ipv6_tun_mtu=0
ipv6_tun_addr=
ipv6_tun_ttl=255
ipv6_dns1=
ipv6_dns2=
ipv6_dns3=
ipv6_get_domain=
ipv6_prefix_len_wan=64
ipv6_radvd=1
ipv6_dhcp_start=
ipv6_dhcp_lifetime=86400
ipv6_6rd_dhcp=1
ipv6_relay=192.88.99.1

I'm going to try rebooting my modem again, as merlin suggested. As I said initially I already tried that, but at least it won't make anything worse

Edit: Nope, didn't help.

 

[Etz]

Found small cosmetic bug on this FW.



Also currently trying to figure out that OpenVPN static.key issue, as I got hit with it also:

Jul  7 10:14:00 rc_service: httpd 308:notify_rc start_vpnserver1
Jul  7 10:14:01 openvpn[521]: OpenVPN 2.3.0 mipsel-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [MH] [IPv6] built on Jul  4 2013
Jul  7 10:14:01 openvpn[521]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Jul  7 10:14:01 openvpn[521]: Diffie-Hellman initialized with 2048 bit key
Jul  7 10:14:01 openvpn[521]: Control Channel Authentication: using 'static.key' as a free-form passphrase file
Jul  7 10:14:01 openvpn[521]: Key file 'static.key' used in --tls-auth contains insufficient key material [keys found=1 required=2]
Jul  7 10:14:01 openvpn[521]: Exiting due to fatal error

Adding blank line after key, as RMerl suggested didnt help.

What I noticed when doing:
cat /etc/openvpn/server1/static.key

Is it adds ">" mark between rows and combines it into single row.
For example:

e5b7e21e79c7f16fee2aaf245da7a4fe
06d540dc0419bd8cc66235b8f5ff6890

becomes to:

e5b7e21e79c7f16fee2aaf245da7a4fe[B]>[/B]06d540dc0419bd8cc66235b8f5ff6890

 

[RogerSC]

Excluding the IPv6 address(es), mine's identical

They do look very similar, except prefix is null, and I don't see router address at all. Linux "diff" command is very useful for directly comparing file contents, I just looked at them so might have missed other differences.

I agree that resetting your modem (and power cycling if you can, my modem has a battery, so it's hard to power cycle *smile*) certainly can't hurt, and might well help. I've done that to clear a problem or two in the past and it has worked.

Good luck with this, I'm sure that it's something simple.

 

[HeadBanger]

DDNS and VPN are two totally separate things - can you elaborate?

I have set up a VPN using Asus's free DDNS. Whilst .30 shows that my DDNS is working when trying to use VPN I just get a message saying VPN not responding contact administrator (or words to that effect). Rolling back to .29 makes everything work again.

Edit. Just installed 30_2 and all is working again. Thank you!

 

[applesnowleo]

Hello Merlin,

I do not know what you did, DDNS is working now. noip working… Connection from the web is working and I can acess my synology now.

Thanks.

 

[frogger]

I have the rt-ac66u. I don't see any difference except that there is a new router been added rt-ac56u.
same wifi driver Jan 22 2013 14:56:50 version 6.30.102.9 (r366174)
and same bootloader (CFE) 1.0.1.4. Does this main the flash to the new version failed? I came from 3.0.0.4_354.29-BETA1.
I have a ac usb3 stick from trendnet TEW-805UB it's not working.
the 260 driver has no problem.

 

[camhusmj38]

VPN won't start 30_2

I have upgraded to version 30_2. Alas, the OpenVPN server still gets wedged while starting up. Any suggestions?

 

[saulos]

I just finish to install it on my RT-AC66U I use the DW build , all seem to be OK.
1) Wifi transfer rate is OK
2) DW interface is a great advance from the old one
3) No-IP is working fine for me I get connected and also from outside I can reach my server
4) Lag form client to router still present ( average 3 ms )

Thanks Merkin great job

 

[Martineau]

I have no way of testing this feature, and you're not giving me enough information either to have any idea what could be wrong. Can you see if the experimental DualWAN version works better for you?

RMerlin, I'm afraid I have not considered the experimental DualWAN version, preferring to stay with 'mainstream' releases given that Asus are apparently still in development with this feature?

I am aware that there is no automated restoration back to the WAN modem , under 354.29 (I simply schedule an 03:00 reboot when the switch to 3G occurs) but if I can have speed,performance and resiliency from a 'consumer' class router then the Asus routers with your firmware definitely get my vote

I have installed 372.30_2 and pulling the LAN cable from the modem causes the 3G modem failure to successfully occur (as under 354.29).....and as already reported by Geko53 in post #17 there is alas no visual confirmation in the GUI showing that the 3G modem I/P connection is defined, although it is actually working.

Unfortunately, after a few minutes the RT-N66U now resets itself and no connection via the 3G modem nor the WAN modem is physically available. Bizarrely, when I simply reattach the LAN cable to the WAN modem, it automatically starts to use it!....so it would appear that Asus are almost there with a fully working 3G WAN fail-over feature!?


I have included an edited syslog (why is dnsmasq persistently repeating my 25 line .conf.add contents?) but it is purely for info as I doubt there is anything to assist in diagnosing this issue.


Once you have refreshed the DualWAN 372.30_2 experimental release I'll see if I can test it later in the week.

Regards,