[Fork] Asuswrt-Merlin 374.43 LTS releases (Archive)

[d4free]

@john9527 First of all, thanks for keeping my beloved firmware up to date. I have a question tho.. Is it possible to select your own extented wifi channel? At this moment i only see a option
showing "auto", it would be nice if i could select the extension channel myself.
And if it's not possible yet, do you think it would be possible for you to add this option? If it's not too much work.. I don't know if it needs to be in a certiain range, e.g. if your default channel is 6, extension channel needs to be between 3 and 8 or not, you probably have more knowledge about this.

 

[ColinTaylor]

@d4free Only certain combinations are allowed. See here: https://en.wikipedia.org/wiki/IEEE_802.11n-2009#40.C2.A0MHz_in_2.4.C2.A0GHz

So by selecting the Control channel and then the Extension Channel (above or below) you get every allowed combination.

 

[Nullity]

@john9527 First of all, thanks for keeping my beloved firmware up to date. I have a question tho.. Is it possible to select your own extented wifi channel? At this moment i only see a option
showing "auto", it would be nice if i could select the extension channel myself.
And if it's not possible yet, do you think it would be possible for you to add this option? If it's not too much work.. I don't know if it needs to be in a certiain range, e.g. if your default channel is 6, extension channel needs to be between 3 and 8 or not, you probably have more knowledge about this.

What device?

 

[john9527]

@john9527 First of all, thanks for keeping my beloved firmware up to date. I have a question tho.. Is it possible to select your own extented wifi channel? At this moment i only see a option
showing "auto", it would be nice if i could select the extension channel myself.
And if it's not possible yet, do you think it would be possible for you to add this option? If it's not too much work.. I don't know if it needs to be in a certiain range, e.g. if your default channel is 6, extension channel needs to be between 3 and 8 or not, you probably have more knowledge about this.

I think @ColinTaylor has the right reference.....only certain combinations are allowed that are covered by the 'above/below' selection.

Same thing for 5GHz band (why there is only 'Auto' selection there). There's a table in this blog that I found that shows the 5GHz channel allocations...
http://www.networkcomputing.com/wireless/channel-bonding-wifi-rules-and-regulations/199326059

 

[scaramonga]

Really shouldn't be necessary. No changes to the wireless drivers and I handle initializing the new nvram variables during the router boot (to avoid having to do a reset).

Of course, if anything looks strange after the upgrade, the first advice will be a reset

Thank you John. I did a full 'wash & go' anyway (lol), and all is just running great buddy Not tinkered with VPN settings yet, will do them tomorrow. But thank you very much for making our devices even better!

 

[telUK]

Thanks John

Working fine on N66U, did a reset as it sounds like a big update.

Cant comment on much as I don't use any of the features really, just use it as a bog standard router, which does a great job with your excellent support.

 

[Zin105]

Port forwarding seems to have absolutely no effect since the new update, any clue what it could be?
These are my settings: http://i.imgur.com/g8LSktd.png

Tried to disable NAT Acceleration and the Firewall with no change.

 

[john9527]

Port forwarding seems to have absolutely no effect since the new update, any clue what it could be?
These are my settings: http://i.imgur.com/g8LSktd.png

Tried to disable NAT Acceleration and the Firewall with no change.

Hmmm....port forwarding is one thing that wasn't touched....

Let's check that the rules are being enabled.....telnet/ssh to the router and enter....
iptables -t nat -L -v | grep DNAT

Please append the output.

 

[Zin105]

Hmmm....port forwarding is one thing that wasn't touched....

Let's check that the rules are being enabled.....telnet/ssh to the router and enter....
iptables -t nat -L -v | grep DNAT

Please append the output.

0 0 DNAT tcp -- any any anywhere anywhere tcp dpts:27030:27039 to:192.168.1.123
0 0 DNAT udp -- any any anywhere anywhere udp dpts:27000:27015 to:192.168.1.123
0 0 DNAT udp -- any any anywhere anywhere udp dpt:1200 to:192.168.1.123
0 0 DNAT tcp -- any any anywhere anywhere tcp dpt:63167 to:192.168.1.165
0 0 DNAT tcp -- any any anywhere anywhere tcp dpts:40000:41000 to:192.168.1.165
0 0 DNAT tcp -- any any anywhere anywhere tcp dpt:8112 to:192.168.1.165
0 0 DNAT tcp -- any any anywhere anywhere tcp dpt:32400 to:192.168.1.165
0 0 DNAT tcp -- any any anywhere anywhere tcp dpt:63168 to:192.168.1.165
0 0 DNAT tcp -- any any anywhere anywhere tcp dpt:63169 to:192.168.1.164:443
0 0 DNAT tcp -- any any anywhere anywhere tcp dpt:www to:192.168.1.165
0 0 DNAT udp -- any any anywhere anywhere udp dpt:48259 to:192.168.1.123:47999
0 0 DNAT udp -- any any anywhere anywhere udp dpt:48270 to:192.168.1.123:48010
0 0 DNAT udp -- any any anywhere anywhere udp dpt:48258 to:192.168.1.123:47998
0 0 DNAT udp -- any any anywhere anywhere udp dpt:48260 to:192.168.1.123:48000

 

[HardCat]

John thanks, installed on RT-N66U running as Access Point. I did do a complete reset just in case. No issues. Great Work!

 

[john9527]

0 0 DNAT tcp -- any any anywhere anywhere tcp dpts:27030:27039 to:192.168.1.123
0 0 DNAT udp -- any any anywhere anywhere udp dpts:27000:27015 to:192.168.1.123
0 0 DNAT udp -- any any anywhere anywhere udp dpt:1200 to:192.168.1.123
0 0 DNAT tcp -- any any anywhere anywhere tcp dpt:63167 to:192.168.1.165
0 0 DNAT tcp -- any any anywhere anywhere tcp dpts:40000:41000 to:192.168.1.165
0 0 DNAT tcp -- any any anywhere anywhere tcp dpt:8112 to:192.168.1.165
0 0 DNAT tcp -- any any anywhere anywhere tcp dpt:32400 to:192.168.1.165
0 0 DNAT tcp -- any any anywhere anywhere tcp dpt:63168 to:192.168.1.165
0 0 DNAT tcp -- any any anywhere anywhere tcp dpt:63169 to:192.168.1.164:443
0 0 DNAT tcp -- any any anywhere anywhere tcp dpt:www to:192.168.1.165
0 0 DNAT udp -- any any anywhere anywhere udp dpt:48259 to:192.168.1.123:47999
0 0 DNAT udp -- any any anywhere anywhere udp dpt:48270 to:192.168.1.123:48010
0 0 DNAT udp -- any any anywhere anywhere udp dpt:48258 to:192.168.1.123:47998
0 0 DNAT udp -- any any anywhere anywhere udp dpt:48260 to:192.168.1.123:48000

OK...all the rules are there (along with what looks like a couple of upnp rules) but nothing is being triggered......

Can you double check/append the output of this command
iptables -t nat -L -v | grep VSERVER

Also, can you please run something that you know should trigger one of your manual forwards, then run the first command again....

BTW....the Plex forward is the only one I use, and I double checked that it's working correctly for me.

 

[Zin105]

OK...all the rules are there (along with what looks like a couple of upnp rules) but nothing is being triggered......

Can you double check/append the output of this command
iptables -t nat -L -v | grep VSERVER

Also, can you please run something that you know should trigger one of your manual forwards, then run the first command again....

BTW....the Plex forward is the only one I use, and I double checked that it's working correctly for me.

I have no idea why, but it randomly started working now without me doing anything. It's been 12 hours since I opened the ports. Sorry for wasting your time!

Any idea why this happened?

Edit: I should add that my external IP changed when I updated the firmware, guessing that had something to do with it.

 

[john9527]

Any idea why this happened?

Edit: I should add that my external IP changed when I updated the firmware, guessing that had something to do with it.

If you are accessing things via a DDNS service it can take a while for the change to propagate to the DNS servers. Usually it's not too long, but it can be variable.

 

[TOD]

john9527
I can't download fw for RT-N16 from OneDrive.

Error description:
Unable to scan RT-N16_3.0.0.4_374.43_2-17E2j9527.trx for viruses
OneDrive is unable to scan RT-N16_3.0.0.4_374.43_2-17E2j9527.trx for viruses.

Can you check/fix this problem?

 

[Zin105]

If you are accessing things via a DDNS service it can take a while for the change to propagate to the DNS servers. Usually it's not too long, but it can be variable.

I figured out the issue. I can access my external IP and DNS when I'm outside of my local network, but not from within (tested at work when I said the problem was "fixed", but same problem when I came home).

From what I understand this has something to do with NAT Loopback? Wasn't like this in earlier firmwares.

 

[john9527]

I figured out the issue. I can access my external IP and DNS when I'm outside of my local network, but not from within (tested at work when I said the problem was "fixed", but same problem when I came home).

From what I understand this has something to do with NAT Loopback? Wasn't like this in earlier firmwares.

Yes...that's NAT loopback (assuming you are accessing via url and not ip address). I just double checked and it's working fine for me. A couple of things to check....

- The mark for NAT loopback changed in this release. If you are using any custom marks, make sure you aren't using one that conflicts with 0x8000.

- Second, and more likely, is that Windows is still caching the old address. In testing, I learned a lot....the default lifetime for the Windows DNS cache is 1 day (both positive and negative response). Try flushing the Windows DNS cache with either
ipconfig /flushdns
or
net stop dnscache
net start dnscache

entered in an Administrators command prompt..

 

[d4free]

What device?

ac68u

btw , after updating to latest version at the Hw acceleration section i now see : Enabled ( CTF only ). Is this how it is supposed to be? I remember it used to only say, Enabled..

 

[john9527]

ac68u

btw , after updating to latest version at the Hw acceleration section i now see : Enabled ( CTF only ). Is this how it is supposed to be? I remember it used to only say, Enabled..

Yes...that's normal....the 'CTF Only' got added when I added the FA mode status for 68P users.

 

[punchsuckr]

Love the bandwidth limiter.. this release really is the best. Thanks again for blowing new life into my trusty n66u John.

 

[Zin105]

Yes...that's NAT loopback (assuming you are accessing via url and not ip address). I just double checked and it's working fine for me. A couple of things to check....

- The mark for NAT loopback changed in this release. If you are using any custom marks, make sure you aren't using one that conflicts with 0x8000.

- Second, and more likely, is that Windows is still caching the old address. In testing, I learned a lot....the default lifetime for the Windows DNS cache is 1 day (both positive and negative response). Try flushing the Windows DNS cache with either
ipconfig /flushdns
or
net stop dnscache
net start dnscache

entered in an Administrators command prompt..

Didn't help. Never used this IP before so couldn't have been cached anyway. Never had this problem before in any previous firmware versions (including 17 beta).
Funny thing is that if I go through a VPN both DNS and IP works.