Asuswrt-Merlin 3.0.0.4.374.33 is out

[rlcronin]

Control Channel choices?

After I installed 33 and reset back to factory defaults, I set out to manually reconfigure all my settings. I thought I had gotten them all, but then noticed that my 2.4GHz WIFI was on channel 6. I had previously set it to channel 1, so I went to change it back to 1. When I clicked the Control Channel pulldown I got a confusing list of choices:

Auto
1l
2l
3l
4l
5l
5u
6l
6u
7l
7u
8u
9u
10u
11u

What are these? Do I just choose 1l? What does the l and u mean? Sorry if I missed something obvious.
--
bc

 

[HaHirsch]

Hi Merlin, in Bridge Mode the Bridged Device is missing the 2.4 GHz Tab.

 

[pijat]

After upgrade to RT-AC66U_3.0.0.4_374.33_0 FW, this router cannot detect my 4G modem anymore. This log after insert this modem :-

Jan 1 08:02:32 kernel: usb 1-1.1: new high speed USB device using ehci_hcd and address 7
Jan 1 08:02:32 kernel: usb 1-1.1: configuration #34 chosen from 1 choice
Jan 1 08:02:32 kernel: scsi2 : SCSI emulation for USB Mass Storage devices
Jan 1 08:02:34 kernel: scsi 2:0:0:0: CD-ROM GCT Semi CD-ROM 312e PQ: 0 ANSI: 0 CCS
Jan 1 08:02:34 kernel: scsi 2:0:0:0: Attached scsi generic sg0 type 5
Jan 1 08:02:34 kernel: usb 1-1.1: USB disconnect, address 7
Jan 1 08:02:35 kernel: usb 1-1.1: new high speed USB device using ehci_hcd and address 8
Jan 1 08:02:35 kernel: usb 1-1.1: configuration #17 chosen from 1 choice

Reinstall back previous FW (RT-AC66U_3.0.0.4_374.32_0-dwyd) cause only this FW can detect my modem. Please help.Thank

 

[oversim]

Hello!
I flashed this firmware.
Previously I flashed beta 1 after a factory reset and re-entering all parameters.
Now with a simple flash all seems ok, no problem on wifi, no problem associated wifi clients.. Just flashed this .33 version.
How can I check if something went wrong?

 

[Etz]

Looks like IPTV is broken in current build, as ASUS has Rewritten that part of the GUI.
Now it works only on occasions when all vlan`s are tagged on WAN port, including internet. It also includes "manual" setup option.

Unfortunately some ISP`s have Internet untagged (native), IPTV and VoIP tagged so it wont work on such occasions at all so youre pretty much stuck with predefined profiles.

Had to downgrade to 374.32 because of it and probably will have to switch to Tomato

If this is also broken in Asus's release, then it will have to be fixed by them, as I have no way of testing VLAN/IPTV functionality unfortunately.

Actually, its not broken, they changed implementation a bit, rendering it useless for some of us.

 

[HawkInOz]

I just upgraded from 26b to 33 on my RT-N66U, and completed the lengthy process of manually re-entering all of my settings after a factory reset.

So far, the only anomaly that I have found is in the Client Status section of the Network Map page. The router seems unable to deal with my two Linksys WES610N bridges, and the devices connected to them. In the Client Status list, the names and IP addresses of the bridges fluctuate real-time between the actual device names given to the bridges in the Manually Assigned IP list on the DHCP Server tab of the LAN page, and the names and IP addresses of the devices that are connected to/through those bridges. I have 46 devices in this list (all known devices and all using DHCP). This was not an issue with 26b, where the bridges and all the devices connected to them were always listed separately and correctly.

Currently, when the bridge is correctly listed in the Client Status list, the devices connected to it are often (but not always) missing from the list. When a device connected to the bridge is correctly listed, the bridge and the other devices may similarly be missing from the list. Sometimes the device and listed IP are mismatched combinations of the bridges and one of the devices connected to it. And sometimes there are multiple entries for one device name with different IP addresses belonging to the bridges and/or the devices connected to them. Clicking the Refresh button only starts this randomness all over with a different - but incorrect or incomplete - result. Whew! Strangeness.

Not sure if there is a new or old setting somewhere that I should change to have all my devices properly detected and listed in the Client Status list, but I don't much like having entries missing or mismatched - which makes it very difficult to determine if something is offline that shouldn't be.

 

[PrivateJoker]

I just upgraded from 26b to 33 on my RT-N66U, and completed the lengthy process of manually re-entering all of my settings after a factory reset.

So far, the only anomaly that I have found is in the Client Status section of the Network Map page. The router seems unable to deal with my two Linksys WES610N bridges, and the devices connected to them.

I think it's a function of how non-WDS client bridging works, it's not perfect but it gets the job done pretty well, and at speeds well above what WDS could do, and using WPA2 as well.

I've run multiple versions of stock Asus f/w, Merlinware, and other f/ws (including DD-WRT) on more than half a dozen G & N routers and the IP addresses aren't visible in some cosmetic way in the router admin UI, though you can still ping them.

I know you said it worked before and now it doesn't, at times I have gotten lucky and I'll see more than I'm expecting to see (in the UI), but I do a lot of stuff on my network testing different configs so I don't expect that part to be stable. Maybe it works different after a certain amount of network stability without any topology changes.

Setting up static DHCP assignments for all devices (and within the bridge too), using a "friendly" name in the DHCP naming all help, and toggling "fully resolve IPs" setting in Asus f/w also might help a bit, but I've come to accept that through the basic (DD-WRT style) wireless bridging, bridged IPs won't always fully appear in the web UI.

Some network searching tools will also just report the IP/MAC of the bridge, some will tell you the # of devices behind the bridge but not much more, but I can go to a TiVo behind one bridge and transfer a show from a TiVo behind another all day long, fast and totally stable (like months of bridge uptime stable). So I know they are communicating with the router fine. They also get content from the Internet no problem.

I can plug a desktop in behind a bridge, turn on its DHCP, and it will get an address that's within the specified range and it will work. Could I do things in the router like QOS based on that desktop's MAC? I really don't know.

 

[RogerSC]

Noticed last night when I was checking out the SDK5 version of this firmware that Comcast's speed test now gives you both IPv4 and IPv6 speed test numbers:

http://speedtest.comcast.net/

Very similar look and feel, just added another set of speed numbers. So if you have IPv6 enabled, check it out *smile*.

 

[RogerSC]

New SDK5 version functionality looks great to me (rt-n66u).

One thing, though, I'm still getting:

Oct 4 13:26:43 kernel: eth1: received packet with own address as source address

I flashed back to 270.26b and still got this, so went forward to the new 374.33 and removed the wireless ethernet bridge and still get it.

Is there anything I can do to get a dump of the packet in question, like setting a router software variable in nvram? I'd like to see the MAC addresses in the packet header, specifically, along with the IP addresses, of course. Maybe there's a debug flag or debug level I can set to see what's going on with this? Seems like one should be able to get more information about this kind of thing?

 

[Deleted member 22229]

Noticed last night when I was checking out the SDK5 version of this firmware that Comcast's speed test now gives you both IPv4 and IPv6 speed test numbers:

http://speedtest.comcast.net/

Very similar look and feel, just added another set of speed numbers. So if you have IPv6 enabled, check it out *smile*.

Yeah I noticed that as well. Its a good idea but it seems the test has issues to, The mileage of the server is way off and the upstream test is not steady it wavers and the speed dial shows a max of 20M but my connection shows 58M then when the upload starts its reversed on the dial.

 

[RogerSC]

Yeah I noticed that as well. Its a good idea but it seems the test has issues to, The mileage of the server is way off and the upstream test is not steady it wavers and the speed dial shows a max of 20M but my connection shows 58M then when the upload starts its reversed on the dial.

It's always had issues. I only use it because Comcast is my ISP. I don't have your issues, though, since I only get about 17.5/2.5 Mbps from Comcast as part of the way over-priced "economy" bundle that I can get from them. No broadband competition around here, so that's the way it goes. Don't care about mileage of server, it's in San Jose, and I know where that is, and I'm used to wavering, since Comcast supplies the wavering as my ISP, and if the test adds to that, so what?

Anyways, I was just noticing the added IPv6, don't expect anything they do to work very well, been with Comcast for too long for that *smile*. I've found that I have a much happier life if I have realistic expectations, especially when it comes to Comcast, Verizon, etc.

 

[Deleted member 22229]

It's always had issues. I only use it because Comcast is my ISP. I don't have your issues, though, since I only get about 17.5/2.5 Mbps from Comcast as part of the way over-priced "economy" bundle that I can get from them. No broadband competition around here, so that's the way it goes. Don't care about mileage of server, it's in San Jose, and I know where that is, and I'm used to wavering, since Comcast supplies the wavering as my ISP, and if the test adds to that, so what?

Anyways, I was just noticing the added IPv6, don't expect anything they do to work very well, been with Comcast for too long for that *smile*. I've found that I have a much happier life if I have realistic expectations, especially when it comes to Comcast, Verizon, etc.

Im with you all the way I have comcrap and have had many issues that took time to solve along with my money, there customer service is the worse but I have no other options here if I did they would be canceled in a heart beat.

 

[RMerlin]

Just updated my N66U to this, As instructed I done a reset and manually reconfigured my router.

My USB-N53 adapter now connects and fluctuates between 81 - 162Mbps according to Windows. This is on 5GHz.

Also tried deleting my previous wireless profile and uninstalling / reinstalling the latest drivers and get the same results.

No matter what firmware I am on it has never connected at the full 300Mbps but it still connected somewhat higher at around 250Mbps.

Is this lower connection due to the decreased signal caused by using SDK6? My ISP provides around 34Mbps and it is still connecting at around 32Mbps so its still good.

My IOS devices on the other hand are a different story, They all run around 10Mbps slower. The best I have gotten was with my Iphone 5 it is around 25Mbps. In saying this no matter what firmware I am on it has always been the same.

Craig

Don't just rely on the link speed, do an actual file transfer to test things out. The link speed will fluctuate based on various things, including power management.

You don't mention at what range you get these readings, so it's impossible to tell if it's due to the range reduction or to anything else.

 

[RMerlin]

After I installed 33 and reset back to factory defaults, I set out to manually reconfigure all my settings. I thought I had gotten them all, but then noticed that my 2.4GHz WIFI was on channel 6. I had previously set it to channel 1, so I went to change it back to 1. When I clicked the Control Channel pulldown I got a confusing list of choices:

Auto
1l
2l
3l
4l
5l
5u
6l
6u
7l
7u
8u
9u
10u
11u

What are these? Do I just choose 1l? What does the l and u mean? Sorry if I missed something obvious.
--

Instead of having separately configurable channels, Asus now has one single channel selector. This is for 40 MHz channel width, where two channels are used.

1l means that channel 1 will be the lower channel (so, the other channel the router will use is 3). Likewise, 11u means 11 will be the upper channel, so 9 will be used as the lower channel.

 

[RMerlin]

How can I check if something went wrong?

If your wireless is working normally and you have no weird issues while changing settings, then it should be fine.

 

[RMerlin]

Looks like IPTV is broken in current build, as ASUS has Rewritten that part of the GUI.
Now it works only on occasions when all vlan`s are tagged on WAN port, including internet. It also includes "manual" setup option.

Unfortunately some ISP`s have Internet untagged (native), IPTV and VoIP tagged so it wont work on such occasions at all so youre pretty much stuck with predefined profiles.

Had to downgrade to 374.32 because of it and probably will have to switch to Tomato



Actually, its not broken, they changed implementation a bit, rendering it useless for some of us.

What happens if you set Internet to either "0" or "1" while on a Manual profile?

What particular change did Asus do that reduced the functionality?

 

[RMerlin]

New SDK5 version functionality looks great to me (rt-n66u).

One thing, though, I'm still getting:

Oct 4 13:26:43 kernel: eth1: received packet with own address as source address

I flashed back to 270.26b and still got this, so went forward to the new 374.33 and removed the wireless ethernet bridge and still get it.

Is there anything I can do to get a dump of the packet in question, like setting a router software variable in nvram? I'd like to see the MAC addresses in the packet header, specifically, along with the IP addresses, of course. Maybe there's a debug flag or debug level I can set to see what's going on with this? Seems like one should be able to get more information about this kind of thing?

Personally I wouldn't worry about these, unless you notice any particular problem.

That error message comes from the Linux kernel itself, so there's little that I could do to get more info about it - it's not generated by the firmware.

 

[bradyrtech]

running the SDK6 build on my rt-n66u, did factory reset and all seems to be great.

getting full "net" speed (50/10Mbps Comcast), after doing some iperf testing between my laptop (Linux, wireless) and server (Linux, wired) getting around 130-135Mbps on 5GHz band, both ways (sitting next to the router). Can't really complain. Intel 6300 ultimate-n chipset.

(remember, cut your connected rate in half to get your real world speed, give or take)

way I see it, as long as I'm getting full internet speeds over wireless, i'm happy. If i need to do some heavy file transfers, i always just plug in a wire.

 

[jlake]

Personally I wouldn't worry about these, unless you notice any particular problem.

That error message comes from the Linux kernel itself, so there's little that I could do to get more info about it - it's not generated by the firmware.

Any possibility he could be under a DNS rebinding attack?

http://blog.trendmicro.com/trendlab...router-against-possibl-dns-rebinding-attacks/

 

[RMerlin]

Any possibility he could be under a DNS rebinding attack?

http://blog.trendmicro.com/trendlab...router-against-possibl-dns-rebinding-attacks/

No, this has nothing to do with DNS. I suspect this has to do with the bridging. I have seen that error message too a long time ago, and it seemed quite random as I don't remember having seen it again, at least not recently.

I think one user was getting them frequently, until he disabled the broadcast/network neighbourhood support on the PPTP VPN pages.

Someone would have to dig up the kernel source code to see what triggers this particular message. Pretty sure a lot of info could be found on Google as well, since I think this is a fairly common warning message.