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

[miniterror]

Hello every one,

Im using this Fork on multiple devices but im finding myself to walk into a problem.
I want limited acces to the router as im going to make it accesable from the WAN.
When i enable this i also have to enter a IP from the internal subnet otherwhise i wont be able to acces it locally.
Because of the leasetime of a IP i want the entire intenral range to be added but i cant manage to get that working.
I tried entering 192.168.10.0 without succes, when i have a other IP from the subnet i cant reach the router.
Any ideas how i can manage to give the entire subnet acces?
Thx in advance.

 

[wiz]

if you limit access to the management interface from the WAN interface, you do not have to supply your lan ip address to still be able to do management. Those are separated.

so this "When i enable this i also have to enter a IP from the internal subnet otherwhise i wont be able to acces it locally" is not true.

 

[Deleted member 22229]

A name would be great, I am sorry I must have missed that. Where is that in the menu system?

Log into the router and go to the LAN tab then scroll down and enable manual assignment. Then choose the device from the drop down list and assign the device a name you can repeat that for as many devices that you want. After you assign a name it will show that name in the network map for connected devices.

 

[john9527]

Log into the router and go to the LAN tab then scroll down and enable manual assignment. Then choose the device from the drop down list and assign the device a name you can repeat that for as many devices that you want. After you assign a name it will show that name in the network map for connected devices.

Kel-L's method will work and also assign static IPs to your clients. If you want to keep using DHCP assigned addresses, you can do it via a dnsmasq.conf.add file placed in /jffs/configs

Use the following syntax....

# Assign name for specific clients
dhcp-host=XX:XX:XX:XX:XX:XX,clientname
repeat above as necessary

where XX:XX:XX:XX:XX:XX is the client MAC.
For the clientname, these need to follow DHCP client naming conventions, so only use alphanumerics and the '-' in the name to be safe.

 

[cor_mann]

John,

First, I want to thank you and Merlin for this wonderful firmware. It's great being able to set up my router and not have to see the interface again for months. It runs so well that I forgot what the settings even were because I didn't have to access it for so long.

Second, I have a question about the recent update. I know that your instructions state that a reset is NOT required if coming from a .43 version of the firmware. I'm on .43 update 6 for the AC68U. That said, I made some change to the NVRAM to increase my transmit power. Would I lose these settings by updating? I've searched the forums and found some info, but nothing specific (I apologize if I missed it).

Thanks again.

 

[john9527]

@cor_mann - All your settings will remain intact when switching between fork versions.

Since you said you don't make many changes, I'd recommend you do a save configuration from the gui and just put it aside as a backup just in case (and not have to remember everything you changed).

 

[ika]

Dear john9527;

Would it be possible for you to compile the FW for the n18u? I would love to deploy some N18Us at places with tight budgets. Here in the EU, the N18U can be acquired for as low as $80, so it would be a great value with your awesome fork.

As I understand, the router is almost the same as the AC68U, except that it's single band only. Merlin already stated that he won't support it because it's not high-end and also not available in North America, which makes me sad since this little Asus router is quite powerful and (imho) deserves more.

 

[john9527]

Dear john9527;

Would it be possible for you to compile the FW for the n18u? I would love to deploy some N18Us at places with tight budgets. Here in the EU, the N18U can be acquired for as low as $80, so it would be a great value with your awesome fork.

As I understand, the router is almost the same as the AC68U, except that it's single band only. Merlin already stated that he won't support it because it's not high-end and also not available in North America, which makes me sad since this little Asus router is quite powerful and (imho) deserves more.

I actually took a crack at supporting this in the past....the problem is that the N18U is a single-core ARM vs the AC68U/56U dual-core ARM. When you try and compile for the single-core, there are mismatches with some of the pre-compiled dual-core binaries that kill the compile. We then tried to fake it out and compile it as a dual-core, but then the wireless radios would never come ready.

So it will take some work to import some of the binaries from the N18 ASUS source and create sysdeps for the N18U (which I've not attempted before).

I'll add it to my list of things to revisit, but no guarantees and definitely no timetable.

 

[Deleted member 22229]

Hey John i see in your sig your using Beta2 of ver 8 any time line for a final and what has been changed since ver 7 ?

 

[ika]

I actually took a crack at supporting this in the past....the problem is that the N18U is a single-core ARM vs the AC68U/56U dual-core ARM. When you try and compile for the single-core, there are mismatches with some of the pre-compiled dual-core binaries that kill the compile. We then tried to fake it out and compile it as a dual-core, but then the wireless radios would never come ready.

So it will take some work to import some of the binaries from the N18 ASUS source and create sysdeps for the N18U (which I've not attempted before).

I'll add it to my list of things to revisit, but no guarantees and definitely no timetable.

Thank you for the great info, and also for the hope, that's already more than what I expected. You are awesome!

 

[john9527]

Update-08BETA

Hey John i see in your sig your using Beta2 of ver 8 any time line for a final and what has been changed since ver 7 ?

Funny you should ask...

So far, no security updates have surfaced, so not in any rush to push out an update (also waiting for Merlin's next release where he double checks the security updates).

But, always incremental improvements

• I'm still trying to improve IPv6 so you don't have to reboot multiple times to get an address (have changed a couple IPv6 things)
• Trying to see if I can find anything to explain why some users are reporting that their android devices can't fully sleep and run down the battery
• A few more backports from Merlin/ASUS latest (full syslog header, Extended TTL)
• Unlocked the Wireless/Professional parameters when running in Repeater mode
• A fix for the one fork unique reported problem of resetting the beamforming options during a firmware update

So with that....I've uploaded a couple files to my 'Beta' download area (just 2 builds for now). There's also a full changelog there.
RT-N66U_3.0.0.4_374.43_2-08B6j9527.trx
RT-AC68U_3.0.0.4_374.43_2-08B6j9527.trx
http://1drv.ms/1sDtB1V
A factory reset is not required going to the Beta (or returning to a previous release of the fork from the Beta, but you will need to reset your beamforming options going back).

I'm interested in feedback on:

• Native IPv6 connections and stability
• Any improvement in sleeping Androids - I've been playing with a cheap little Emerson tablet I had picked up to learn android (running 4.1.2 - rooted). Right now I have got it where the wireless disconnects and never reconnects when it's asleep on 2.4Ghz (tablet only supports the 2.4GHz band). I also started with a big battery drain. Unfortunately I made the mistake of changing multiple things at the same time - found 5 autostarting apps that I disabled (using the Clean Master app from Google Play Store) in addition to the router firmware change. Still testing, but would appreciate any feedback from others.
• Improvements for routers in Repeater mode when changing the wireless parameters

PS....I see your signature has changed as well....no more R7000?

 

[Deleted member 22229]

Thanks John. I would be interested in testing comcast IPv6 for you. Question if i upload the beta do i have to run any Telnet/SSH commands or are the fixes already implemented in the beta code ? I dont really want to mess with running commands but will try if they fixes are there after upload. If not i will wait for the final. As always great work.

 

[john9527]

Thanks John. I would be interested in testing comcast IPv6 for you. Question if i upload the beta do i have to run any Telnet/SSH commands or are the fixes already implemented in the beta code ? I dont really want to mess with running commands but will try if they fixes are there after upload. If not i will wait for the final. As always great work.

No commands necessary....load and go

 

[Deleted member 22229]

No commands necessary....load and go

Ok John i will load and give native IPv6 a go and let you know if there is any change.


EDIT: Looks like the beta is actually worse then ver 7 as far as getting a IPv6 allocation. I had to do multiple reboots (6) to even get the router to obtain a V6 address so there is still something not right there. It does work but i really had to go through hoops to get it. Probably going to go back to V7.

 

[RocketJSquirrel]

Odd. My Comcast IPv6 has worked perfectly for the almost 3 years I've had the N66U, starting with the stock Asus firmware. It never fails to get a v6 address on the first try. Comcast is kind of a crap shoot depending on your location, I guess.

 

[Deleted member 22229]

Odd. My Comcast IPv6 has worked perfectly for the almost 3 years I've had the N66U, starting with the stock Asus firmware. It never fails to get a v6 address on the first try. Comcast is kind of a crap shoot depending on your location, I guess.

Yes it's strange. I have always had to do reboots to get a solid V6 with comcast on Asus routers. Although on my Netgear R-7000 it works perfect every time. Go figure..

 

[john9527]

Odd. My Comcast IPv6 has worked perfectly for the almost 3 years I've had the N66U, starting with the stock Asus firmware. It never fails to get a v6 address on the first try. Comcast is kind of a crap shoot depending on your location, I guess.

Merlin calls IPv6 'one big experiment at this point'....

I'm trying a few little tweaks here and there...but in general the fork has been stable and I don't want to end up breaking things in the process.

 

[Deleted member 22229]

Merlin calls IPv6 'one big experiment at this point'....

I'm trying a few little tweaks here and there...but in general the fork has been stable and I don't want to end up breaking things in the process.

As hard as it can be for me to get V6 going once it's there it works and keeps working so i can deal with it until Asus perfects it. Still strange on the Netgear it works flawlessly every time.

 

[john9527]

Ok John i will load and give native IPv6 a go and let you know if there is any change.


EDIT: Looks like the beta is actually worse then ver 7 as far as getting a IPv6 allocation. I had to do multiple reboots (6) to even get the router to obtain a V6 address so there is still something not right there. It does work but i really had to go through hoops to get it. Probably going to go back to V7.

Sorry to hear that.....but it's still an interesting piece of data. The changes I made should have worst case had no effect, not actually have made things worse. This may mean we're dealing with some type of timing condition where a little delay in the code path is making a difference. I may have a Beta update version in the next day or two to try.

 

[Vandergraff]

Odd. My Comcast IPv6 has worked perfectly for the almost 3 years I've had the N66U, starting with the stock Asus firmware. It never fails to get a v6 address on the first try.

Likewise I have had no issues with Comcast IPv6 with an N66U on various Merlin builds and now the fork over the last few years.