ASUS RT-N66U new firmware version 178

[richto]

The Android device is capable of wireless N, but the Wifi Analyzer app only shows my router occupying 20 MHz.

But inSSIDer on my Laptop shows it correctly, when my router is running at 40 MHz.

I already have set the TX power to 100mw, more is not legal in Europe... Does a higher setting (maybe 150) make a huge difference?

There are no limits to TX power in Europe. Only to ERP. So 250mW would be quite legal with the correct antenna.

 

[Trentors]

There are no limits to TX power in Europe. Only to ERP. So 250mW would be quite legal with the correct antenna.

Yes there is. And when trying to se the TX power above 100mW the system refuses with the following warning:

ETSI: max. 100mW for Europe, South America and APAC.

Unfortunately it also this is also the case with RMerlins highly recommended firmware.

 

[2000wolf]

Well... I run my RT-N66U with 40mW and get quite good performance.
Double TX power always means only a gain of 3 db for the price of more electro smog / radiation.

 

[Chuck Link]

Please help I am a beginner

I have a RT-N66U router. Brighthouse/roadrunner cable in from the street to the router to an older vaio with windows XP at home. Please tell me ALL I need to do to allow me to access this vaio from my office. The computer has the free dyndns service and I was able to access it previously with my lynxis.
I have been trying to get it to connect for a week.

 

[cbb77]

Just installed the N66U and had to default it to AP mode as could not get it to function as router behind my existing FIOS router. I think I know my error and will re-attempt tonight, but all is working well as AP. However I did notice that several of the functions I had wanted to leverage are disabled / not available in AP mode (DHCP Server, Traffic Monitor, etc). Was wondering if this enhanced firmware would make all functions available or will it still have these disabled in AP mode?

 

[WJKramer]

Just installed the N66U and had to default it to AP mode as could not get it to function as router behind my existing FIOS router. I think I know my error and will re-attempt tonight, but all is working well as AP. However I did notice that several of the functions I had wanted to leverage are disabled / not available in AP mode (DHCP Server, Traffic Monitor, etc). Was wondering if this enhanced firmware would make all functions available or will it still have these disabled in AP mode?

I have FiOS. I am running the N66U as a full functioning router behind the FiOS action tech router. From the FiOS ONT the signal comes into my house via MoCA (coax) into the action tech modem/router. Then ethernet to the N66U wan port. I plugged a laptop into one of the N66U LAN port via ethernet. Set up as router not AP and it should automatically be assigned IP address 192.168.2.1 where as your action tech should still be primary at 192.168.1.1. So far working great. all my devices connect to the the LAN ports or WiFi on the N66U and there fore run on the 192.168.2.X subnet. The only double NATd devices are the FiOS motorola cable boxes which don't matter anyhow. Good luck!

Running Merlin WRT as well....good stuff!

 

[RMerlin]

Just installed the N66U and had to default it to AP mode as could not get it to function as router behind my existing FIOS router. I think I know my error and will re-attempt tonight, but all is working well as AP. However I did notice that several of the functions I had wanted to leverage are disabled / not available in AP mode (DHCP Server, Traffic Monitor, etc). Was wondering if this enhanced firmware would make all functions available or will it still have these disabled in AP mode?

Since an AP sits on the same network segment as the actual router, having DHCP makes no sense, since that would conflict with the router's own DHCP.

 

[cbb77]

Since an AP sits on the same network segment as the actual router, having DHCP makes no sense, since that would conflict with the router's own DHCP.

I was looking to switch over to the DHCP server on the N66U and just use the FIOS router to manage the cable boxes since most of my devices are wireless. I do have a few wired devices but most have static IPs. However again, I find it weird that Asus disables some of the features based on how the router is configured. For example, would love to use the bandwidth monitor to see how well my connections are and throughput. Again, this may be moot as I do plan on trying to set up as router again this evening.

Thanks

 

[darksamus]

I was looking to switch over to the DHCP server on the N66U and just use the FIOS router to manage the cable boxes since most of my devices are wireless. I do have a few wired devices but most have static IPs. However again, I find it weird that Asus disables some of the features based on how the router is configured. For example, would love to use the bandwidth monitor to see how well my connections are and throughput. Again, this may be moot as I do plan on trying to set up as router again this evening.

Thanks

If you think of it from a network managment point of view, it makes sense. If they allow monitoring traffic on the AP, its only traffic going through it. It make sense to look at the traffic going across the router. If you want to monitor traffic going through the AP, you need to set up a pc with monitoring software like PRTG and put it between the router and the AP.

 

[staticfree]

Whats all these log entries mean?

Hi, I just looked at my RT-N66U router log entries and I see a continous stream of the same error messages. The system log is just full all day and night long with this (cut and pasted a sample of the system log here):

Sep 1 11:23:50 kernel: printk: 10923 messages suppressed.
Sep 1 11:23:50 kernel: protocol 0000 is buggy, dev eth1
Sep 1 11:23:55 kernel: printk: 11435 messages suppressed.
Sep 1 11:23:55 kernel: protocol 0000 is buggy, dev eth1
Sep 1 11:24:00 kernel: printk: 11783 messages suppressed.
Sep 1 11:24:00 kernel: protocol 0000 is buggy, dev eth1
Sep 1 11:24:05 kernel: printk: 10809 messages suppressed.
Sep 1 11:24:05 kernel: protocol 0000 is buggy, dev eth1

I am on the latest ASUS .178 firmware release. Other than this I've not had any connection issues. Just wondering what is causing these log messages.
Any ideas anyone?

 

[DaveMishSr]

Well... I run my RT-N66U with 40mW and get quite good performance.
Double TX power always means only a gain of 3 db for the price of more electro smog / radiation.

Other issues with increasing your wattage is the likelihood of introducing noise into your signal increases greatly and as you increase dB's you also increase attenuation. In ultrasound we were taught the attenuation formula in soft tissue to be 0.5dB/cm/MHz freq. So you lose 1 dB of power for each 2 cm's traveled and every 2 MHz of frequency. That is why the 5GHz band attenuates more than the 2.4GHz band. I do not know the formula for WiFi attenuation. I imagine its more complicated as there are many more mediums to transmit through and greater distances are involved as compared to ultrasound.

 

[RMerlin]

Hi, I just looked at my RT-N66U router log entries and I see a continous stream of the same error messages. The system log is just full all day and night long with this (cut and pasted a sample of the system log here):

Sep 1 11:23:50 kernel: printk: 10923 messages suppressed.
Sep 1 11:23:50 kernel: protocol 0000 is buggy, dev eth1
Sep 1 11:23:55 kernel: printk: 11435 messages suppressed.
Sep 1 11:23:55 kernel: protocol 0000 is buggy, dev eth1
Sep 1 11:24:00 kernel: printk: 11783 messages suppressed.
Sep 1 11:24:00 kernel: protocol 0000 is buggy, dev eth1
Sep 1 11:24:05 kernel: printk: 10809 messages suppressed.
Sep 1 11:24:05 kernel: protocol 0000 is buggy, dev eth1

I am on the latest ASUS .178 firmware release. Other than this I've not had any connection issues. Just wondering what is causing these log messages.
Any ideas anyone?

Disable Broadcast support on the VPN page.

 

[staticfree]

Disable Broadcast support on the VPN page.

RMerlin, I am afraid that did not work. I disabled Broadcast support on the VPN page. Hit apply and looked at log. Messages still there. Went back and hit apply a 2nd time to see if it takes. Nope. Hit apply for a 3rd time to make sure it took. The log still streaming the same buggy protocol message for eth1 but now also occassionally showing same message for eth0. Here is cut and paste sample again:

Sep 1 15:06:01 kernel: printk: 3598 messages suppressed.
Sep 1 15:06:01 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:06:06 kernel: printk: 3716 messages suppressed.
Sep 1 15:06:07 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:06:11 kernel: printk: 3860 messages suppressed.
Sep 1 15:06:11 kernel: protocol 0000 is buggy, dev eth0
Sep 1 15:06:16 kernel: printk: 4065 messages suppressed.
Sep 1 15:06:16 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:06:21 kernel: printk: 4070 messages suppressed.
Sep 1 15:06:21 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:06:26 kernel: printk: 4155 messages suppressed.
Sep 1 15:06:27 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:06:31 kernel: printk: 4012 messages suppressed.
Sep 1 15:06:31 kernel: protocol 0000 is buggy, dev eth0
Sep 1 15:06:36 kernel: printk: 4336 messages suppressed.
Sep 1 15:06:36 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:06:41 kernel: printk: 4099 messages suppressed.
Sep 1 15:06:41 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:06:46 kernel: printk: 4314 messages suppressed.
Sep 1 15:06:47 kernel: protocol 0000 is buggy, dev eth0
Sep 1 15:06:51 kernel: printk: 4150 messages suppressed.
Sep 1 15:06:51 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:06:56 kernel: printk: 4274 messages suppressed.
Sep 1 15:06:56 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:07:01 kernel: printk: 4413 messages suppressed.
Sep 1 15:07:01 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:07:06 kernel: printk: 4530 messages suppressed.
Sep 1 15:07:07 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:07:11 kernel: printk: 4649 messages suppressed.
Sep 1 15:07:11 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:07:16 kernel: printk: 4614 messages suppressed.
Sep 1 15:07:16 kernel: protocol 0000 is buggy, dev eth0
Sep 1 15:07:21 kernel: printk: 4489 messages suppressed.
Sep 1 15:07:21 kernel: protocol 0000 is buggy, dev eth0
Sep 1 15:07:26 kernel: printk: 4722 messages suppressed.
Sep 1 15:07:27 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:07:31 kernel: printk: 4558 messages suppressed.
Sep 1 15:07:31 kernel: protocol 0000 is buggy, dev eth0
Sep 1 15:07:36 kernel: printk: 4894 messages suppressed.
Sep 1 15:07:36 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:07:41 kernel: printk: 4665 messages suppressed.
Sep 1 15:07:41 kernel: protocol 0000 is buggy, dev eth0
Sep 1 15:07:46 kernel: printk: 4868 messages suppressed.
Sep 1 15:07:47 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:07:51 kernel: printk: 4936 messages suppressed.
Sep 1 15:07:51 kernel: protocol 0000 is buggy, dev eth0
Sep 1 15:07:56 kernel: printk: 4907 messages suppressed.
Sep 1 15:07:56 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:08:01 kernel: printk: 5043 messages suppressed.
Sep 1 15:08:01 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:08:06 kernel: printk: 4806 messages suppressed.
Sep 1 15:08:07 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:08:11 kernel: printk: 5259 messages suppressed.
Sep 1 15:08:11 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:08:16 kernel: printk: 4784 messages suppressed.
Sep 1 15:08:16 kernel: protocol 0000 is buggy, dev eth0
Sep 1 15:08:21 kernel: printk: 4645 messages suppressed.
Sep 1 15:08:21 kernel: protocol 0000 is buggy, dev eth0
Sep 1 15:08:26 kernel: printk: 4857 messages suppressed.
Sep 1 15:08:27 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:08:31 kernel: printk: 4985 messages suppressed.
Sep 1 15:08:31 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:08:36 kernel: printk: 4972 messages suppressed.
Sep 1 15:08:36 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:08:41 kernel: printk: 5288 messages suppressed.
Sep 1 15:08:41 kernel: protocol 0000 is buggy, dev eth0
Sep 1 15:08:47 kernel: printk: 5396 messages suppressed.
Sep 1 15:08:47 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:08:51 kernel: printk: 5058 messages suppressed.
Sep 1 15:08:51 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:08:56 kernel: printk: 5454 messages suppressed.
Sep 1 15:08:56 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:09:01 kernel: printk: 5372 messages suppressed.
Sep 1 15:09:01 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:09:06 kernel: printk: 5412 messages suppressed.
Sep 1 15:09:06 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:09:12 kernel: printk: 5582 messages suppressed.
Sep 1 15:09:12 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:09:16 kernel: printk: 5521 messages suppressed.
Sep 1 15:09:16 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:09:21 kernel: printk: 5364 messages suppressed.
Sep 1 15:09:21 kernel: protocol 0000 is buggy, dev eth0
Sep 1 15:09:26 kernel: printk: 5479 messages suppressed.
Sep 1 15:09:26 kernel: protocol 0000 is buggy, dev eth0
Sep 1 15:09:32 kernel: printk: 5211 messages suppressed.
Sep 1 15:09:32 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:09:36 kernel: printk: 5442 messages suppressed.
Sep 1 15:09:36 kernel: protocol 0000 is buggy, dev eth1
Sep 1 15:09:41 kernel: printk: 5538 messages suppressed.

 

[RMerlin]

Disable it both on the Server page and the Details page - I don't remember which of these two is responsible (but it's definitely one of the two).

 

[staticfree]

Disable it both on the Server page and the Details page - I don't remember which of these two is responsible (but it's definitely one of the two).

Ahh, okay. That did the trick! Messages stopped streaming in now.
Thank You!

 

[Ormu]

I bought this router a while ago and updated the firmware before doing other configurations... Now I'm unable to add entries to the list that is used to give certain MAC addresses the same local IP every time. The add button (and Apply button) does not work. Has anyone else noticed this? I reported this to Asus technical support as well.

 

[RMerlin]

I bought this router a while ago and updated the firmware before doing other configurations... Now I'm unable to add entries to the list that is used to give certain MAC addresses the same local IP every time. The add button (and Apply button) does not work. Has anyone else noticed this? I reported this to Asus technical support as well.

There's an option above to enable it - set that to Yes first, then click on Apply.

 

[Ormu]

There's an option above to enable it - set that to Yes first, then click on Apply.

Tried that, doesn't work. The Apply button or "add" button doesn't do anything.

 

[RMerlin]

Tried that, doesn't work. The Apply button or "add" button doesn't do anything.

Please post a screenshot showing an entry you are trying to add.

 

[Ormu]

Please post a screenshot showing an entry you are trying to add.

Here:
http://i.imgur.com/WuN9N.png

I set "Enable manual assignment" to "Yes" but I can't save that setting either. The Apply button doesn't work. Other DHCP settings are default.