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

[mihei78]

First thing to try is to make sure 'Enable VPN + DHCP Connection' is set to No on the WAN setup page for PPPoE.

Thank you, problem solved!!! On all other firmware I used before, I didn’t turn off the 'Enable VPN + DHCP Connection' option, but iptv worked. Now I turned off this item on your firmware and iptv started working.
I will stay on your firmware, I like very good wifi speed for ac66u 2013 release. Thanks again.

 

[john9527]

Thank you, problem solved!!! On all other firmware I used before, I didn’t turn off the 'Enable VPN + DHCP Connection' option, but iptv worked. Now I turned off this item on your firmware and iptv started working.
I will stay on your firmware, I like very good wifi speed for ac66u 2013 release. Thanks again.

Glad to hear that worked!

I actually learned something here, having only discovered that option disables igmpproxy/udpxy when looking through the code for things that would prevent udpxy from starting. Since that's really a special case option, I think I'm going to change the default to 'No' in a future release.

 

[Adamm]

I'm finished banging my head against the wall on this one

When you get some free time, it would be nice if you could take a look at IPSet v7 which was recently released.

 

[john9527]

When you get some free time, it would be nice if you could take a look at IPSet v7 which was recently released.

I have already tried 6.35 and it completely broke everything on ARM. We may be stuck on 6.32 for ARM...v7 may be possible for HND, but I don't relish the thought of having to debug ipset again...

 

[flinchlock]

I know this does not have anything todo with John's fork.

I can not find out what this device is...

<snip>
Nov 14 06:47:25 dnsmasq-dhcp[576]: DHCPOFFER(br0) 192.168.1.149 2c:3a:e8:2a:17:7c 
Nov 14 06:47:25 dnsmasq-dhcp[576]: DHCPREQUEST(br0) 192.168.1.149 2c:3a:e8:2a:17:7c 
Nov 14 06:47:25 dnsmasq-dhcp[576]: DHCPACK(br0) 192.168.1.149 2c:3a:e8:2a:17:7c ESP_2A177C
Nov 14 06:47:42 dnsmasq-dhcp[576]: DHCPDISCOVER(br0) 2c:3a:e8:2a:17:7c 
Nov 14 06:47:42 dnsmasq-dhcp[576]: DHCPOFFER(br0) 192.168.1.149 2c:3a:e8:2a:17:7c 
Nov 14 06:47:42 dnsmasq-dhcp[576]: DHCPREQUEST(br0) 192.168.1.149 2c:3a:e8:2a:17:7c 
Nov 14 06:47:42 dnsmasq-dhcp[576]: DHCPACK(br0) 192.168.1.149 2c:3a:e8:2a:17:7c ESP_2A177C
Nov 14 06:48:05 dnsmasq-dhcp[576]: DHCPREQUEST(br0) 192.168.1.130 b4:e6:2d:a7:f1:79 
Nov 14 06:48:05 dnsmasq-dhcp[576]: DHCPACK(br0) 192.168.1.130 b4:e6:2d:a7:f1:79 espressif
Nov 14 06:48:10 dnsmasq-dhcp[576]: DHCPDISCOVER(br0) 2c:3a:e8:2a:17:7c 
Nov 14 06:48:10 dnsmasq-dhcp[576]: DHCPOFFER(br0) 192.168.1.149 2c:3a:e8:2a:17:7c 
Nov 14 06:48:10 dnsmasq-dhcp[576]: DHCPREQUEST(br0) 192.168.1.149 2c:3a:e8:2a:17:7c 
Nov 14 06:48:10 dnsmasq-dhcp[576]: DHCPACK(br0) 192.168.1.149 2c:3a:e8:2a:17:7c ESP_2A177C
Nov 14 06:48:57 dnsmasq-dhcp[576]: DHCPREQUEST(br0) 192.168.1.130 b4:e6:2d:a7:f1:79 
Nov 14 06:48:57 dnsmasq-dhcp[576]: DHCPACK(br0) 192.168.1.130 b4:e6:2d:a7:f1:79 espressif
Nov 14 06:49:10 dnsmasq-dhcp[576]: DHCPDISCOVER(br0) 2c:3a:e8:2a:17:7c 
Nov 14 06:49:10 dnsmasq-dhcp[576]: DHCPOFFER(br0) 192.168.1.149 2c:3a:e8:2a:17:7c 
Nov 14 06:49:10 dnsmasq-dhcp[576]: DHCPREQUEST(br0) 192.168.1.149 2c:3a:e8:2a:17:7c 
Nov 14 06:49:10 dnsmasq-dhcp[576]: DHCPACK(br0) 192.168.1.149 2c:3a:e8:2a:17:7c ESP_2A177C
Nov 14 06:49:49 dnsmasq-dhcp[576]: DHCPREQUEST(br0) 192.168.1.130 b4:e6:2d:a7:f1:79 
Nov 14 06:49:49 dnsmasq-dhcp[576]: DHCPACK(br0) 192.168.1.130 b4:e6:2d:a7:f1:79 espressif
Nov 14 06:50:41 dnsmasq-dhcp[576]: DHCPREQUEST(br0) 192.168.1.130 b4:e6:2d:a7:f1:79 
Nov 14 06:50:41 dnsmasq-dhcp[576]: DHCPACK(br0) 192.168.1.130 b4:e6:2d:a7:f1:79 espressif
Nov 14 06:50:51 dnsmasq-dhcp[576]: DHCPDISCOVER(br0) 2c:3a:e8:2a:17:7c 
Nov 14 06:50:51 dnsmasq-dhcp[576]: DHCPOFFER(br0) 192.168.1.149 2c:3a:e8:2a:17:7c 
Nov 14 06:50:51 dnsmasq-dhcp[576]: DHCPREQUEST(br0) 192.168.1.149 2c:3a:e8:2a:17:7c 
Nov 14 06:50:51 dnsmasq-dhcp[576]: DHCPACK(br0) 192.168.1.149 2c:3a:e8:2a:17:7c ESP_2A177C
Nov 14 06:51:33 dnsmasq-dhcp[576]: DHCPREQUEST(br0) 192.168.1.130 b4:e6:2d:a7:f1:79 
Nov 14 06:51:33 dnsmasq-dhcp[576]: DHCPACK(br0) 192.168.1.130 b4:e6:2d:a7:f1:79 espressif
Nov 14 06:52:10 dnsmasq-dhcp[576]: DHCPDISCOVER(br0) 2c:3a:e8:2a:17:7c 
Nov 14 06:52:10 dnsmasq-dhcp[576]: DHCPOFFER(br0) 192.168.1.149 2c:3a:e8:2a:17:7c 
Nov 14 06:52:10 dnsmasq-dhcp[576]: DHCPREQUEST(br0) 192.168.1.149 2c:3a:e8:2a:17:7c 
Nov 14 06:52:10 dnsmasq-dhcp[576]: DHCPACK(br0) 192.168.1.149 2c:3a:e8:2a:17:7c ESP_2A177C
Nov 14 06:52:25 dnsmasq-dhcp[576]: DHCPREQUEST(br0) 192.168.1.130 b4:e6:2d:a7:f1:79 
Nov 14 06:52:25 dnsmasq-dhcp[576]: DHCPACK(br0) 192.168.1.130 b4:e6:2d:a7:f1:79 espressif
Nov 14 06:53:17 dnsmasq-dhcp[576]: DHCPREQUEST(br0) 192.168.1.130 b4:e6:2d:a7:f1:79 
Nov 14 06:53:17 dnsmasq-dhcp[576]: DHCPACK(br0) 192.168.1.130 b4:e6:2d:a7:f1:79 espressif
Nov 14 06:54:09 dnsmasq-dhcp[576]: DHCPREQUEST(br0) 192.168.1.130 b4:e6:2d:a7:f1:79 
Nov 14 06:54:09 dnsmasq-dhcp[576]: DHCPACK(br0) 192.168.1.130 b4:e6:2d:a7:f1:79 espressif
Nov 14 06:54:10 dnsmasq-dhcp[576]: DHCPDISCOVER(br0) 2c:3a:e8:2a:17:7c 
Nov 14 06:54:10 dnsmasq-dhcp[576]: DHCPOFFER(br0) 192.168.1.149 2c:3a:e8:2a:17:7c 
Nov 14 06:54:10 dnsmasq-dhcp[576]: DHCPREQUEST(br0) 192.168.1.149 2c:3a:e8:2a:17:7c 
Nov 14 06:54:10 dnsmasq-dhcp[576]: DHCPACK(br0) 192.168.1.149 2c:3a:e8:2a:17:7c ESP_2A177C
Nov 14 06:55:01 dnsmasq-dhcp[576]: DHCPREQUEST(br0) 192.168.1.130 b4:e6:2d:a7:f1:79 
Nov 14 06:55:01 dnsmasq-dhcp[576]: DHCPACK(br0) 192.168.1.130 b4:e6:2d:a7:f1:79 espressif
Nov 14 06:55:10 dnsmasq-dhcp[576]: DHCPDISCOVER(br0) 2c:3a:e8:2a:17:7c 
Nov 14 06:55:10 dnsmasq-dhcp[576]: DHCPOFFER(br0) 192.168.1.149 2c:3a:e8:2a:17:7c 
Nov 14 06:55:10 dnsmasq-dhcp[576]: DHCPREQUEST(br0) 192.168.1.149 2c:3a:e8:2a:17:7c 
Nov 14 06:55:10 dnsmasq-dhcp[576]: DHCPACK(br0) 192.168.1.149 2c:3a:e8:2a:17:7c ESP_2A177C
Nov 14 06:55:54 dnsmasq-dhcp[576]: DHCPREQUEST(br0) 192.168.1.130 b4:e6:2d:a7:f1:79 
Nov 14 06:55:54 dnsmasq-dhcp[576]: DHCPACK(br0) 192.168.1.130 b4:e6:2d:a7:f1:79 espressif
Nov 14 06:56:46 dnsmasq-dhcp[576]: DHCPREQUEST(br0) 192.168.1.130 b4:e6:2d:a7:f1:79 
Nov 14 06:56:46 dnsmasq-dhcp[576]: DHCPACK(br0) 192.168.1.130 b4:e6:2d:a7:f1:79 espressif
Nov 14 06:57:10 dnsmasq-dhcp[576]: DHCPDISCOVER(br0) 2c:3a:e8:2a:17:7c 
Nov 14 06:57:10 dnsmasq-dhcp[576]: DHCPOFFER(br0) 192.168.1.149 2c:3a:e8:2a:17:7c 
Nov 14 06:57:10 dnsmasq-dhcp[576]: DHCPREQUEST(br0) 192.168.1.149 2c:3a:e8:2a:17:7c 
Nov 14 06:57:10 dnsmasq-dhcp[576]: DHCPACK(br0) 192.168.1.149 2c:3a:e8:2a:17:7c ESP_2A177C
<snip>

 

[fatspirit]

I know this does not have anything todo with John's fork.

I can not find out what this device is...

Should be some kind of small/smart device.

 

[john9527]

I can not find out what this device is...

Expressif supplies wifi chipsets for IoT devices...

 

[szimat]

I have an RT-N66U, running latest Merlin (380.70). I tried to figure out, but I'm not sure which version should I choose?
I understand it is a common questions... I think the E version is what I need, but how about the numbering and letter code combinations, like 32E4 or 36EA for example? Which version should I choose and why?

My other question is, if I understand correctly, DNS over TLS is implemented in your firmware?

 

[fatspirit]

My other question is, if I understand correctly, DNS over TLS is implemented in your firmware?

 

[fatspirit]

I think the E version is what I need, but how about the numbering and letter code combinations, like 32E4 or 36EA for example? Which version should I choose and why?

See OP for latest version highlights.

 

[john9527]

but how about the numbering and letter code combinations, like 32E4 or 36EA for example? Which version should I choose and why?

Quick key....

• The first set of number is the release number (currently 36). The release number is usually incremented if there is a major new function or there are a significant number of new patches included.
• The next letter is usually one of 3 possibilities
  • 'B' for Beta releases
  • 'L' for 'legeacy' releases. These contain older wireless drivers (circa 2014) that some people think work better, but DO NOT contain the a fix for the KRACK exploit which is necessary if running the router as a Repeater or MediaBridge.
  • 'E' releases have more current wireless drivers and kernel updates, and contains the fix for the KRACK exploit. This is generally the recommended level.
  • I may use other letters if working with someone with test or development special builds.
• The last hex digit (0-F) is an incremental release identifier, incorporating a small number of fixes.

 

[tlsrulz]

Hi, I have a RT-N66U running Tomato Version 1.28 by shibby.... recently upgraded my internet to 500Mbit.. and realized the limitation of WAN-LAN of Tomato.
- Just want to confirm that this fork has enough throughput to support my faster speeds.
- Also I am assuming I would have to use the ASUS utility to upload to this fork.

Thanks

 

[john9527]

Hi, I have a RT-N66U running Tomato Version 1.28 by shibby.... recently upgraded my internet to 500Mbit.. and realized the limitation of WAN-LAN of Tomato.
- Just want to confirm that this fork has enough throughput to support my faster speeds.

Will support into the 900Mb range, but above 100-150 Mb you cannot use QoS or IPtraffic (per device monitoring), or have a USB Modem attached.

- Also I am assuming I would have to use the ASUS utility to upload to this fork.

You may be able to load from the gui, but using the ASUS Recovery Tool or CFE mini web server would probably be safer. Follow up with a factory reset. Note that loading the code on the N66 via the Tool or server may take a long time...on the order of 30-40 min.

 

[tlsrulz]

thanks John for the quick reply.. with 500Mbit connection I dont need QoS or IPtraffic monitoring.. (which was cool back in the day)
Isnt it odd how everything was fine with <100Mbit but once you get something faster you can't go back !

 

[Kobalt]

For supported routers currently running ASUS firmware 380.3000 or above, or Merlin 380.60 or above, you cannot load this fork using the built in firmware update web interface. You must use the ASUS Firmware Restoration Tool from the ASUS support website or the built in CFE Mini-Web Server to install this fork firmware. You must always perform a factory default reset following the firmware update when moving from ASUS OEM or Merlin firmware above level 374 regardless if you updated via the web interface or Restoration Tool.

I think most people with the older ASUS routers are running the last Merlin release (380.xx), and I am curious why this fork needs to go above the normal steps of flashing a newer Merlin version? Or, in other words, why is the ASUS FRT tool or the CFE needed at all if this forked firmware is based off of Merlin's?

Is this just being really cautious, or is there a technical answer as why the procedure outlined above is needed?

 

[ColinTaylor]

Is this just being really cautious, or is there a technical answer as why the procedure outlined above is needed?

From the versions specified Asus changed the firmware format and blocked the downgrading of firmware through the GUI. See: https://github.com/RMerl/asuswrt-merlin/wiki/Installation

 

[mihei78]

Hi, please tell me, where can I read about installing TOR on this firmware?
Does ipset work on this firmware (ac66u)?

 

[fatspirit]

What is the lowest mW value that fork can accept?

 

[jeff288]

What is the lowest mW value that fork can accept?

1mw. That's what mine's set at and I still get decent reception upstairs. Though I only have 30mb internet so doesn't take much wifi to give me what I need.

 

[ColinTaylor]

What is the lowest mW value that fork can accept?

Even though you can enter specific numbers like 7mW in reality the power is set in discrete bands. So any number between 1 and 19 produces the same result. The same is true for 20-39, 40-69, 70-80, 80 and > 80.