Asuswrt-Merlin 3.0.0.4.374.32 is out

[RMerlin]

I tried 3.0.0.4_374.33_beta1. Unfortunately, with the same negative result.

To be honest, I pretty much given up on supporting those Russian ISPs using a tunnel on top of DHCP to provide Internet connectivity. I never heard of any other ISPs in the world doing that.

Last time, it took me two or three entire evenings of configuration and tests to fix it, as it requires me to configure a PPTP or L2TP server, and test a bunch of different scenarios. In this case it would also require me to reconfigure a router so I can swap it with the RT-AC56U as I would need it within my LAN to test things out with a local L2TP server.

So if it's broken again, unfortunately I doubt I will find the time or the motivation to go through this all over again. If a developer who actually has an ISP with that kind of setup wants to give it a shot, he's more than welcome. Otherwise, I'm sorry - I just don't have the time at the moment to spend on that single ISP.

 

[its]

Hi RMerlin

Have you heard of this problem? I have a MBPr and on your latest stable firmware.. Randomly (more often than not) when I open the laptop from sleep (open the computer), it cannot see my Wifi network and cannot connect.. I have 802.11n on 5GHz.. AC66U

Only fix is to disable / enable wifi on Mac couple of times till it auto connects.. when it does not connect.. It cannot see the my 5GHz network..

Don't want to drop to original firmware as I don't want to loose traffic monitoring data (saving on USB) and love the feature..

Cheers.

 

[RMerlin]

Hi RMerlin

Have you heard of this problem? I have a MBPr and on your latest stable firmware.. Randomly (more often than not) when I open the laptop from sleep (open the computer), it cannot see my Wifi network and cannot connect.. I have 802.11n on 5GHz.. AC66U

Only fix is to disable / enable wifi on Mac couple of times till it auto connects.. when it does not connect.. It cannot see the my 5GHz network..

Don't want to drop to original firmware as I don't want to loose traffic monitoring data (saving on USB) and love the feature..

Sounds more like a client issue than a router issue if the problem is related to the computer's sleep mode, especially if the computer cannot even see the 5 GHz SSID when it comes out of sleep.

I don't really work with Macs, so no idea. Sorry.

 

[vdemarco]

Hi RMerlin

Have you heard of this problem? I have a MBPr and on your latest stable firmware.. Randomly (more often than not) when I open the laptop from sleep (open the computer), it cannot see my Wifi network and cannot connect.. I have 802.11n on 5GHz.. AC66U

Only fix is to disable / enable wifi on Mac couple of times till it auto connects.. when it does not connect.. It cannot see the my 5GHz network..

Don't want to drop to original firmware as I don't want to loose trSuaffic monitoring data (saving on USB) and love the feature..

Cheers.

I have a rt-ac66u and nothing but macs and it's working great for me.

Have you reset the router to factory defaults?

I have to admit when I first got the router it sucked for about 3 months
Now all is well with the las test firmware

 

[PrivateJoker]

Hi RMerlin

Have you heard of this problem? I have a MBPr and on your latest stable firmware.. Randomly (more often than not) when I open the laptop from sleep (open the computer), it cannot see my Wifi network and cannot connect.. I have 802.11n on 5GHz.. AC66U

Can you go to system profiler > wifi section and do a screenshot (command-shift-4) that includes AirPort Extreme identifier & Broadcom chip identification? I'm curious

And you're running Mt Lion? If you hold down option and click airport menubar icon try going through the wifi/wireless diagnostics option at the bottom. It will do a lot of little tests and checks and save a report of its findings on the desktop.

 

[its]

Can you go to system profiler > wifi section and do a screenshot (command-shift-4) that includes AirPort Extreme identifier & Broadcom chip identification? I'm curious

And you're running Mt Lion? If you hold down option and click airport menubar icon try going through the wifi/wireless diagnostics option at the bottom. It will do a lot of little tests and checks and save a report of its findings on the desktop.

Sent you a PM with that.. I am on 10.8.5 -- latest ML.. As noted below.. happens on MBA 2012 model as well

I have a rt-ac66u and nothing but macs and it's working great for me.

Have you reset the router to factory defaults?

I have to admit when I first got the router it sucked for about 3 months
Now all is well with the las test firmware

It was reset before putting the Merlin Firmware..

Sounds more like a client issue than a router issue if the problem is related to the computer's sleep mode, especially if the computer cannot even see the 5 GHz SSID when it comes out of sleep.

I don't really work with Macs, so no idea. Sorry.

Problem is that my Router is the only 5Ghz one around the area so can't even confirm if this is a general 5Ghz problem or router specific

...

I had a Airport Extreme AC version for 2 weeks and it worked flawlessly.. no issues with the sleep and awake thing with that..

This has not been issue since day one but started soon afterwards and is random... but more frequent now.. Also to note.. this is happening with our MBA 2012 Model as well (not the latest AC model)...

So something to do with router perhaps.. how can i reset with not loosing the traffic data and settings? Don't want to go through all pages of advance setup.. lol forgotten what all i did.. static IP, Wireless.. Port forwarding.. etc.. ? backup -- reset --- restore?? will that keep all ?? is that the possible solution?

Any help will be great...

Ta..

 

[neirity]

Hi Merlin, thanks for the work done ... and hello to everyone who participates in the discussion.
I'm using firmware 3.0.0.4.374.32. Internet connection - only through the 3,5g wimax usb-modem Seowon SWU-3220A (FRESHTEL-ukraine). Every 2 hours:
Sep 23 12:48:28 WAN Connection: Fail to connect with some issues.
Sep 23 12:48:28 stop_nat_rules: apply the redirect_rules!
Sep 23 12:48:28 dnsmasq[26358]: exiting on receipt of SIGTERM
Sep 23 12:48:28 dnsmasq[26701]: started, version 2.65 cachesize 1500
Sep 23 12:48:28 dnsmasq[26701]: compile time options: IPv6 GNU-getopt no-RTC no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack
Sep 23 12:48:28 dnsmasq[26701]: asynchronous logging enabled, queue limit is 5 messages
Sep 23 12:48:28 dnsmasq-dhcp[26701]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d
Sep 23 12:48:28 dnsmasq[26701]: read /etc/hosts - 5 addresses
Sep 23 12:48:28 dnsmasq[26701]: using nameserver 193.19.247.115#53
Sep 23 12:48:28 dnsmasq[26701]: using nameserver 193.19.247.114#53
Sep 23 12:48:53 rc_service: wanduck 975:notify_rc restart_wan_if 1
Sep 23 12:48:53 stop_wan(): perform DHCP release
Sep 23 12:48:53 dnsmasq[26701]: read /etc/hosts - 5 addresses
Sep 23 12:48:53 dnsmasq[26701]: using nameserver 193.19.247.115#53
Sep 23 12:48:53 dnsmasq[26701]: using nameserver 193.19.247.114#53
Sep 23 12:48:55 kernel: tun: Universal TUN/TAP device driver, 1.6
Sep 23 12:48:55 kernel: tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep 23 12:48:57 rc_service: wanduck 975:notify_rc restart_wan_if 0
Sep 23 12:48:57 dnsmasq[26701]: read /etc/hosts - 5 addresses
Sep 23 12:48:57 stop_wan(): perform DHCP release
Sep 23 12:48:57 kernel: br0: port 1(vlan1) entering disabled state
Sep 23 12:48:57 kernel: br0: port 1(vlan1) entering listening state
Sep 23 12:48:57 kernel: br0: port 1(vlan1) entering learning state
Sep 23 12:48:57 kernel: br0: topology change detected, propagating
Sep 23 12:48:57 kernel: br0: port 1(vlan1) entering forwarding state
Sep 23 12:48:59 dnsmasq[26701]: read /etc/hosts - 5 addresses
Sep 23 12:49:01 dnsmasq[26701]: read /etc/hosts - 5 addresses
Sep 23 12:49:34 dnsmasq[26701]: read /etc/hosts - 5 addresses
Sep 23 12:49:34 dnsmasq[26701]: using nameserver 193.19.247.115#53
Sep 23 12:49:34 dnsmasq[26701]: using nameserver 193.19.247.114#53
Sep 23 12:49:34 dhcp client: bound 213.238.5.122 via 213.238.5.122 during 2147483647 seconds.
Sep 23 12:49:37 dnsmasq-dhcp[26701]: DHCPINFORM(br0) 192.168.1.5 70:1a:04:c9:ea:9d
Sep 23 12:49:37 dnsmasq-dhcp[26701]: DHCPACK(br0) 192.168.1.5 70:1a:04:c9:ea:9d GRENOUILLE
Sep 23 12:49:37 rc_service: wanduck 975:notify_rc restart_wan_if 0
Sep 23 12:49:37 stop_wan(): perform DHCP release
Sep 23 12:49:37 kernel: br0: port 1(vlan1) entering disabled state
Sep 23 12:49:37 kernel: br0: port 1(vlan1) entering listening state
Sep 23 12:49:37 kernel: br0: port 1(vlan1) entering learning state
Sep 23 12:49:37 kernel: br0: topology change detected, propagating
Sep 23 12:49:37 kernel: br0: port 1(vlan1) entering forwarding state
Sep 23 12:49:39 dnsmasq[26701]: read /etc/hosts - 5 addresses
Sep 23 12:49:39 dnsmasq[26701]: using nameserver 193.19.247.115#53
Sep 23 12:49:39 dnsmasq[26701]: using nameserver 193.19.247.114#53
Sep 23 12:49:41 rc_service: wanduck 975:notify_rc restart_wan_line 1
Sep 23 12:49:41 dnsmasq[26701]: read /etc/hosts - 5 addresses
Sep 23 12:49:41 dnsmasq[26701]: using nameserver 193.19.247.115#53
Sep 23 12:49:41 dnsmasq[26701]: using nameserver 193.19.247.114#53
Sep 23 12:49:41 start_nat_rules: apply the nat_rules(/tmp/nat_rules_wimax0_wimax0)!
Sep 23 12:49:41 dnsmasq[26701]: exiting on receipt of SIGTERM
Sep 23 12:49:41 dnsmasq[26760]: started, version 2.65 cachesize 1500
Sep 23 12:49:41 dnsmasq[26760]: compile time options: IPv6 GNU-getopt no-RTC no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack
Sep 23 12:49:41 dnsmasq[26760]: asynchronous logging enabled, queue limit is 5 messages
Sep 23 12:49:41 dnsmasq-dhcp[26760]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d
Sep 23 12:49:41 dnsmasq[26760]: read /etc/hosts - 5 addresses
Sep 23 12:49:41 dnsmasq[26760]: using nameserver 193.19.247.115#53
Sep 23 12:49:41 dnsmasq[26760]: using nameserver 193.19.247.114#53
Sep 23 12:49:42 WAN Connection: WAN was restored.

This happens while using the original firmware, as yours, then some do not connect intrenet back. (some versions are not recognized themselves that there is no connection intrenet) ...
Firmware: 3.0.0.4.374.32 (Merlin build) - the most stable product for me (thanks again), but would like to know how to get rid of such a permanent reconnection...

 

[RMerlin]

Hi Merlin, thanks for the work done ... and hello to everyone who participates in the discussion.
I'm using firmware 3.0.0.4.374.32. Internet connection - only through the 3,5g wimax usb-modem Seowon SWU-3220A (FRESHTEL-ukraine). Every 2 hours:

This happens while using the original firmware, as yours, then some do not connect intrenet back. (some versions are not recognized themselves that there is no connection intrenet) ...
Firmware: 3.0.0.4.374.32 (Merlin build) - the most stable product for me (thanks again), but would like to know how to get rid of such a permanent reconnection...

If it's always precisely every two hours then it must be the ISP cutting the connection after that time limit.

 

[neirity]

If it's always precisely every two hours

exactly

then it must be the ISP cutting the connection after that time limit.

і knew that my provider is the best of the best
thank you.

 

[Shayne]

Hi

I have have a problem that I am hoping someone can help with. Since I have installed this firmware openvpn client does not work as it use to.

First I can not turn it off. It goes proceeding..... but always comes back as on.

Second I can not change locations I have always used custom configuration with the following

log /tmp/vpn.log
remote-random
# Chicago
remote 208.53.xxx.xxx 53
remote 208.53.xxx.xxx 53
and so on

It will not switch locations and remains at the vpn location I had prior to upgrading the firmware.

Third I have try to upgrade to the new beta 3 it runs through but still indicated .32 is installed.

Regards

Edit: Try to reset to factory defaults and it runs through goes to the initial screen but are my settings are still there and still connected to vpn location that it was set to prior to firmware upgrade.

Anyone know the correct procedure for a hard reset for rt-n66u? totally confused?

Edit2:

My router would not take commands (at first) clearing the non-volatile ram which I had to use hard 30/30/30 with wps button since the command interface would come up but the router would take no commands (waited 10 minutes for mtd-erase -d nvram with no response). This reset gave me back some control so I set up the router from scratch and was now left with not being able to turn on openvpn client from the web interface. Down graded firmware to RT-N66U_3.0.0.4_270.24.trx same problem?

http://192.168.1.1/Main_AdmStatus_Content.asp

Once at this page, type:
mtd-erase -d nvram
Push Enter key and wait for confirmation in the lower portion that nvram was erased.
Now type:
reboot
Push enter

Worked now .... progress

and set up router from scratch again (I have screenshots and notes so it was set up to prior and have verified after fix)

Only fix that brought me back to a working vpn client interface was to install an old cfg backup to the router. Now I have my router running as it was prior to up grading to this firmware and I can turn it on and off and change locations.

I have no idea what happen but does leave me questioning this firmware. I have a fix and therefore will not be worried about upgrading but think I will pass on this one and the betas. Is this a change to the client setup and one of my configurations is not right now? Why would it not work when firmware was downgrade, I should have been back to at least being able to turn client 1 openvpn on and off (unless an error results in it not turning on)? Not the most knowledgeable when it comes to routers, just needs to connect and vpn. Still confused and any comments/help would be appreciated ......... but it appears we talk to ourselves LoL.

 

[tungsten]

Previously was on RT-N66U_3.0.0.4_270.26b and it ran fine for quite sometime, tried out RT-N66U_3.0.0.4_374.32_0 and the router keep disconnecting from the internet, and Wifi start disconnecting in both 2.4 and 5G. Did a few reboot but still don't work out.

Start trying all previous 372 build but still the same. In the end got to roll back build 270.26b to have a stable connection.

Is there any difference between build 270 and 372? Do I need to have a special step to flash? Thanks!

 

[RMerlin]

Is there any difference between build 270 and 372

Yes, about 6 months of active development, and a lot of changes:

http://www.lostrealm.ca/asuswrt-merlin/changelog.txt

Do I need to have a special step to flash? Thanks!

When making such a big jump in version, it's best to erase nvram settings and manually reconfigure your router.

 

[jsmiddleton4]

roll back build 270.26b

370.32 with SDK5 works very well and is very stable.

SDK6 versions and my wireless card won't connect via 5 ghz and WPA2. Works fine with 370.32 because it is SDK5.

 

[jlake]

roll back build 270.26b

370.32 with SDK5 works very well and is very stable.

SDK6 versions and my wireless card won't connect via 5 ghz and WPA2. Works fine with 370.32 because it is SDK5.

What happens when you use TKIP on the router with sdk6 firmware with your broadcom 4322?

http://answers.microsoft.com/en-us/...com-4322/0b0256ef-91cf-474b-9e71-7ce953fcae75

 

[ZeroBit]

There is a problem in 3.0.0.4.374.32 firmware. I thought it was fixed in ASUS RT-N66R Firmware Version 3.0.0.4.354: Wireless MAC filter can now block clients that connect over guest networks. But blocking Wireless MACs in guest networks still doesn't work in Merlin 3.0.0.4.374.32 firmware.
Parental control based on time doesn't work. It blocks device for all time independently on time settings. If to do "allow" all 24 hours all 7 days a week in still blocks device.

 

[Grievous Angel]

Just as a report . . I left my AC66R up for almost an entire month on this build with no problems. Had almost a full month in the traffic log.

Rebooted it for the hell of it, wan't having any problems . . it just "felt" like it was time.

Maybe I'll let it go indefinitely this time.

So, very stable. Thanks Merlin!

 

[jsmiddleton4]

I could be mistaken but I don't think TKIP is an option with WPA2.

 

[Shayne]

Yes, about 6 months of active development, and a lot of changes:

http://www.lostrealm.ca/asuswrt-merlin/changelog.txt




When making such a big jump in version, it's best to erase nvram settings and manually reconfigure your router.

Hi

I have have a problem that I am hoping someone can help with. Since I have installed this firmware openvpn client does not work as it use to.

First I can not turn it off. It goes proceeding..... but always comes back as on.

Second I can not change locations I have always used custom configuration with the following

log /tmp/vpn.log
remote-random
# Chicago
remote 208.53.xxx.xxx 53
remote 208.53.xxx.xxx 53
and so on

It will not switch locations and remains at the vpn location I had prior to upgrading the firmware.

Third I have try to upgrade to the new beta 3 it runs through but still indicated .32 is installed.

Regards

Edit: Try to reset to factory defaults and it runs through goes to the initial screen but are my settings are still there and still connected to vpn location that it was set to prior to firmware upgrade.

Anyone know the correct procedure for a hard reset for rt-n66u? totally confused?

Edit2:

My router would not take commands (at first) clearing the non-volatile ram which I had to use hard 30/30/30 with wps button since the command interface would come up but the router would take no commands (waited 10 minutes for mtd-erase -d nvram with no response). This reset gave me back some control so I set up the router from scratch and was now left with not being able to turn on openvpn client from the web interface. Down graded firmware to RT-N66U_3.0.0.4_270.24.trx same problem?

http://192.168.1.1/Main_AdmStatus_Content.asp

Once at this page, type:
mtd-erase -d nvram
Push Enter key and wait for confirmation in the lower portion that nvram was erased.
Now type:
reboot
Push enter

Worked now .... progress

and set up router from scratch again (I have screenshots and notes so it was set up to prior and have verified after fix)

Only fix that brought me back to a working vpn client interface was to install an old cfg backup to the router. Now I have my router running as it was prior to up grading to this firmware and I can turn it on and off and change locations.

I have no idea what happen but does leave me questioning this firmware. I have a fix and therefore will not be worried about upgrading but think I will pass on this one and the betas. Is this a change to the client setup and one of my configurations is not right now? Why would it not work when firmware was downgrade, I should have been back to at least being able to turn client 1 openvpn on and off (unless an error results in it not turning on)? Not the most knowledgeable when it comes to routers, just needs to connect and vpn. Still confused and any comments/help would be appreciated ......... but it appears we talk to ourselves LoL.

Did that, did not work?

Regards

 

[tungsten]

Yes, about 6 months of active development, and a lot of changes:

http://www.lostrealm.ca/asuswrt-merlin/changelog.txt




When making such a big jump in version, it's best to erase nvram settings and manually reconfigure your router.

Thanks, no short cut..work like a charm now..

 

[RogerSC]

Hmmm...using this version of firmware and am seeing the following messages in my router's log. I don't have an AP, just the rt-n66u router doing routing and wireless. I do have a WiFi adapter for my Verizon Network Extender, though, a Netgear WNCE2001:

Oct 1 01:12:16 kernel: eth1: received packet with own address as source address
Oct 1 01:58:16 kernel: eth1: received packet with own address as source address
Oct 1 03:20:16 kernel: eth1: received packet with own address as source address
Oct 1 03:41:08 kernel: eth1: received packet with own address as source address
Oct 1 05:37:13 kernel: eth1: received packet with own address as source address
Oct 1 06:24:57 kernel: eth1: received packet with own address as source address
Oct 1 06:26:43 kernel: eth1: received packet with own address as source address
Oct 1 07:38:59 kernel: eth1: received packet with own address as source address
Oct 1 08:28:53 kernel: eth1: received packet with own address as source address
Oct 1 10:20:55 kernel: eth1: received packet with own address as source address
Oct 1 11:53:02 kernel: eth1: received packet with own address as source address

Any ideas on what might be causing this? I've had these before in smaller quantities, this is a little disturbing.