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

[burtal]

Check my signature.....build 05Dj9527 (D for development)...

great builds john, thanks , can you name them a little bit cryptic ?

 

[john9527]

great builds john, thanks , can you name them a little bit cryptic ?

There is actually a reason I named them the way I did. When I originally PM'd Merlin about me doing this fork, one of the things he requested was that I add a personal identifier to the name to make sure it was easy to see it was different from his releases. I don't like adding my initials, so I decided to add a short form of my forum logon 'j9527'....then prepend the release number.....so ended up with 04j9527 added to Merlin's original release name.

 

[john9527]

I am running the latest fork on the RT-N66U in wireless repeater mode, I am getting the following entries in the System Log every 12 hours:

Oct 19 09:52:04 rc_service: udhcpc_lan 8816:notify_rc stop_dnsmasq
Oct 19 09:52:04 dnsmasq[5041]: exiting on receipt of SIGTERM
Oct 19 09:52:04 rc_service: udhcpc_lan 8816:notify_rc start_dnsmasq
Oct 19 09:52:04 dnsmasq[8819]: started, version 2.72test3 cachesize 1500
Oct 19 09:52:04 dnsmasq[8819]: asynchronous logging enabled, queue limit is 5 messages
Oct 19 09:52:04 dnsmasq[8819]: read /etc/hosts - 5 addresses
Oct 19 09:52:04 dnsmasq[8819]: using nameserver 192.168.1.1#53
Oct 19 09:52:04 notify wanduck: wlc_state change!
Oct 19 09:52:06 kernel: dnsmq ctrl: 801a8c0 ^Frouter^Dasus^Ccom

Everything seems to be running well, but what do the log entries mean?? Thanks.

I was hoping someone else might jump in as I don't have any experience with repeater mode. Obviously, something is restarting dnsmasq (the DHCP and nameserver), but I don't immediately understand why that would even be running in repeater mode. If you log into the N66, and go to LAN/DHCP Server does the first entry show DHCP server enabled?

 

[RMerlin]

I was hoping someone else might jump in as I don't have any experience with repeater mode. Obviously, something is restarting dnsmasq (the DHCP and nameserver), but I don't immediately understand why that would even be running in repeater mode. If you log into the N66, and go to LAN/DHCP Server does the first entry show DHCP server enabled?

According to that log, dnsmasq is restarted by udhcpc_lan. Combined to the 12 hours timeframe, my guess is you have a 24 hours DHCP lease that's being renewed by your repeater.

 

[burtal]

There is actually a reason I named them the way I did. When I originally PM'd Merlin about me doing this fork, one of the things he requested was that I add a personal identifier to the name to make sure it was easy to see it was different from his releases. I don't like adding my initials, so I decided to add a short form of my forum logon 'j9527'....then prepend the release number.....so ended up with 04j9527 added to Merlin's original release name.

oh..lol, now it make sense j9527 comes from your nick it was right in front of me duuh you could name it arthur or excalibur

 

[Just Checking]

I am running the 374.43_2 ver. 4 Fork Firmware on an RT-AC68 router. I have been having problems with getting PLEX to connect to my server from outside my network. I got it to work one time by opening a VPN to the network using PPPT. Subsequent attempts to link to the server have failed. I went into the PLEX Server and tried manually setting the port to a number then doing both port forwarding AND port triggering to open both the default ports and the manually set port. I do have UPnP enabled on the router.

The PLEX server software says it is logged in but that it cannot connect to the server from outside the network.

I was reading in the troubleshooting guide to set the LAN subnet mask to 255.255.255.255 from the default 255.255.255.0 . I did that and lost all connection to all the servers and clients on the network. I cannot connect to the router using the IP of 192.168.1.1 when I plug a PC directly into a LAN port on the router. I tried rebooting the router several times with no success as well as resetting the ethernet ports on the servers. Regaining router communication and network connection is the first priority for me.
Do I have to do a hard reset of the router and start the router configuration over from scratch to get the router working again?

The second priority is getting a stable, secure VPN connection to the network. I have not been able to get that since implementing the Fork Firmware. The fact that I cannot get PLEX to connect in from outside the network seems to me to be an indicator that either I am doing something wrong (very possible) or, the Fork firmware has something screwy going on.

Does anyone else have experience with using PLEX and Open VPN while runnning the Fork Firmware?

I did set up a DDNS account since I have a dynamic WAN Address from the ISP. I tried turning off the Firewall and DOS prevention to no avail. I followed all the directions in the Wiki on setting up the Open VPN. I followed the troubleshooting guides in the PLEX forum (that's how I messed with the LAN subnet mask).

Interestingly, before I messed up the router by changing the subnet mask, I was able to get easy communication to my PLEX server on several Samsung smartphones using the PLEX App. I couldn't get any communication to my Plex Server, or network from several of my client Laptop P.C.'s at all. I would think that, if I can get communication on a smartphone to my network, getting communication between a client laptop and my network should also be successful.

I am using Windows 7 64-bit Pro OS on all my servers and client P.C.'s. The smartphones and tablets are using android OS (4.1 or higher). The servers and client P.C.'s are all on one workgroup and homegroup.

 

[john9527]

I was reading in the troubleshooting guide to set the LAN subnet mask to 255.255.255.255 from the default 255.255.255.0 . I did that and lost all connection to all the servers and clients on the network. I cannot connect to the router using the IP of 192.168.1.1 when I plug a PC directly into a LAN port on the router. I tried rebooting the router several times with no success as well as resetting the ethernet ports on the servers. Regaining router communication and network connection is the first priority for me.
Do I have to do a hard reset of the router and start the router configuration over from scratch to get the router working again?

Well, I run an OpenVPN client on the router (Private Internet Access) 100% of the time with Plex Media Server so I can definitely say it works....but it is tricky to set up and will change depending on your VPN provider. I'm assuming that's what you mean and not a VPN Server on the router.

But first, with respect to the above quote....what you told the router by changing the netmask is that your LAN consists of exactly 1 device, the router, so yes, you need to do a hard reset and reconfig from scratch. (If I remember correctly that netmask change was suggested for the Plex server setup, not the router).

So, once you get back up, provide a little more info on your VPN setup and I'm sure we can get you running.

 

[x-micro]

I am on latest Fork, and today i have got BUG kernel error in system log(all clients were shut down when in happened and only transmission worked):

Oct 22 02:17:22 kernel: BUG: scheduling while atomic: mtdblock3/258/0x40000002
Oct 22 02:17:22 kernel: module: ohci_hcd bf78f000 19288
Oct 22 02:17:22 kernel: module: ehci_hcd bf780000 34220
Oct 22 02:17:22 kernel: module: xhci_hcd bf76b000 53350
Oct 22 02:17:22 kernel: module: sr_mod bf762000 11507
Oct 22 02:17:22 kernel: module: cdrom bf753000 33318
Oct 22 02:17:22 kernel: module: nf_nat_sip bf74c000 5586
Oct 22 02:17:22 kernel: module: nf_conntrack_sip bf740000 16679
Oct 22 02:17:22 kernel: module: nf_nat_h323 bf739000 5137
Oct 22 02:17:22 kernel: module: nf_conntrack_h323 bf728000 34844
Oct 22 02:17:22 kernel: module: nf_nat_rtsp bf722000 3400
Oct 22 02:17:22 kernel: module: nf_conntrack_rtsp bf71b000 4268
Oct 22 02:17:22 kernel: module: nf_nat_ftp bf715000 1314
Oct 22 02:17:22 kernel: module: nf_conntrack_ftp bf70e000 5131
Oct 22 02:17:22 kernel: module: ip6table_filter bf708000 893
Oct 22 02:17:22 kernel: module: ip6table_mangle bf702000 1093
Oct 22 02:17:22 kernel: module: cdc_mbim bf6fc000 3313
Oct 22 02:17:22 kernel: module: qmi_wwan bf6f4000 6020
Oct 22 02:17:22 kernel: module: cdc_wdm bf6ed000 7856
Oct 22 02:17:22 kernel: module: cdc_ncm bf6e4000 9258
Oct 22 02:17:22 kernel: module: rndis_host bf6dd000 5209
Oct 22 02:17:22 kernel: module: cdc_ether bf6d7000 3456
Oct 22 02:17:22 kernel: module: asix bf6ce000 11741
Oct 22 02:17:22 kernel: module: usbnet bf6c4000 11691
Oct 22 02:17:22 kernel: module: mii bf6be000 3484
Oct 22 02:17:22 kernel: module: usblp bf6b5000 9386
Oct 22 02:17:22 kernel: module: ufsd bf5e0000 595355
Oct 22 02:17:22 kernel: module: jnl bf5d3000 27931
Oct 22 02:17:22 kernel: module: ext2 bf5bd000 55581
Oct 22 02:17:22 kernel: module: ext4 bf574000 234233
Oct 22 02:17:22 kernel: module: jbd2 bf55d000 52386
Oct 22 02:17:22 kernel: module: crc16 bf557000 1081
Oct 22 02:17:22 kernel: module: ext3 bf530000 113117
Oct 22 02:17:22 kernel: module: jbd bf51b000 45524
Oct 22 02:17:22 kernel: module: mbcache bf513000 5156
Oct 22 02:17:22 kernel: module: usb_storage bf500000 35319
Oct 22 02:17:22 kernel: module: sg bf4f3000 21138
Oct 22 02:17:22 kernel: module: sd_mod bf4e7000 23159
Oct 22 02:17:22 kernel: module: scsi_wait_scan bf4e1000 502
Oct 22 02:17:22 kernel: module: scsi_mod bf4b2000 114857
Oct 22 02:17:22 kernel: module: usbcore bf487000 108266
Oct 22 02:17:22 kernel: module: nf_nat_pptp bf481000 1796
Oct 22 02:17:22 kernel: module: nf_conntrack_pptp bf47b000 3739
Oct 22 02:17:22 kernel: module: nf_nat_proto_gre bf475000 1047
Oct 22 02:17:22 kernel: module: nf_conntrack_proto_gre bf46f000 3499
Oct 22 02:17:22 kernel: module: wl bf037000 3956700
Oct 22 02:17:22 kernel: module: igs bf02d000 12935
Oct 22 02:17:22 kernel: module: emf bf023000 16229
Oct 22 02:17:22 kernel: module: et bf00b000 63892
Oct 22 02:17:22 kernel: module: ctf bf000000 17519
Oct 22 02:17:22 kernel: Modules linked in: ohci_hcd ehci_hcd xhci_hcd sr_mod cdrom nf_nat_sip nf_conntrack_sip nf_nat_h323 nf_conntrack_h323 nf_nat_rtsp nf_conntrack_rtsp nf_nat_ftp nf_conntrack_ftp ip6table_filter ip6table_mangle cdc_mbim qmi_wwan cdc_wdm cdc_ncm rndis_host cdc_ether asix usbnet mii usblp ufsd(P) jnl ext2 ext4 jbd2 crc16 ext3 jbd mbcache usb_storage sg sd_mod scsi_wait_scan scsi_mod usbcore nf_nat_pptp nf_conntrack_pptp nf_nat_proto_gre nf_conntrack_proto_gre wl(P) igs(P) emf(P) et(P)
Oct 22 02:17:22 kernel: [<c0043ff8>] (unwind_backtrace+0x0/0xf8) from [<c02dc2e4>] (schedule+0x434/0x75c)
Oct 22 02:17:22 kernel: [<c02dc2e4>] (schedule+0x434/0x75c) from [<c005b994>] (__cond_resched+0x24/0x34)
Oct 22 02:17:22 kernel: [<c005b994>] (__cond_resched+0x24/0x34) from [<c02dc728>] (_cond_resched+0x34/0x44)
Oct 22 02:17:22 kernel: [<c02dc728>] (_cond_resched+0x34/0x44) from [<c00a2de8>] (shrink_page_list+0xa4/0x728)
Oct 22 02:17:22 kernel: [<c00a2de8>] (shrink_page_list+0xa4/0x728) from [<c00a3768>] (shrink_inactive_list+0x104/0x1dc)
Oct 22 02:17:22 kernel: [<c00a3768>] (shrink_inactive_list+0x104/0x1dc) from [<c00a3be4>] (shrink_zone+0x3a4/0x418)
Oct 22 02:17:22 kernel: [<c00a3be4>] (shrink_zone+0x3a4/0x418) from [<c00a42f0>] (try_to_free_pages+0x150/0x33c)
Oct 22 02:17:22 kernel: [<c00a42f0>] (try_to_free_pages+0x150/0x33c) from [<c009dc30>] (__alloc_pages_nodemask+0x31c/0x698)
Oct 22 02:17:22 kernel: [<c009dc30>] (__alloc_pages_nodemask+0x31c/0x698) from [<c0388d04>] (__slab_alloc+0x1b4/0x814)
Oct 22 02:17:22 kernel: [<c0388d04>] (__slab_alloc+0x1b4/0x814) from [<c00c38b0>] (__kmalloc+0xf4/0x104)
Oct 22 02:17:22 kernel: [<c00c38b0>] (__kmalloc+0xf4/0x104) from [<c01c0af4>] (_nflash_mtd_read+0x9c/0x3a0)
Oct 22 02:17:22 kernel: [<c01c0af4>] (_nflash_mtd_read+0x9c/0x3a0) from [<c01c12dc>] (nflash_mtd_read+0x4c/0x64)
Oct 22 02:17:22 kernel: [<c01c12dc>] (nflash_mtd_read+0x4c/0x64) from [<c01a3f94>] (part_read+0x64/0xe8)
Oct 22 02:17:22 kernel: [<c01a3f94>] (part_read+0x64/0xe8) from [<c01a71f0>] (mtdblock_readsect+0x40/0x114)
Oct 22 02:17:22 kernel: [<c01a71f0>] (mtdblock_readsect+0x40/0x114) from [<c01a69f0>] (mtd_blktrans_thread+0x204/0x294)
Oct 22 02:17:22 kernel: [<c01a69f0>] (mtd_blktrans_thread+0x204/0x294) from [<c0079e6c>] (kthread+0x88/0x90)
Oct 22 02:17:22 kernel: [<c0079e6c>] (kthread+0x88/0x90) from [<c003eb8c>] (kernel_thread_exit+0x0/0x8)

Can you please explain what can it be?

Thanks in advance.

 

[john9527]

I am on latest Fork, and today i have got BUG kernel error in system log(all clients were shut down when in happened and only transmission worked):

Oct 22 02:17:22 kernel: BUG: scheduling while atomic: mtdblock3/258/0x40000002

Can you please explain what can it be?

Thanks in advance.

I did a forum search and found 3 other hits with the same signature. Two of these never got a response.

In the third, Merlin responded that this was an error with flash memory (mtdblock) and recommended reflashing the firmware, followed by a factory reset and reconfigure.

The only other thought I had (not knowing if this error is specifically a hardware error) was that since 2 of the 3 hits mentioned Transmission, it may be a bug in Transmission that's causing a wild memory access. So you may want to ensure that you have the lastest level, and possibly dial back the transfer settings a bit.

 

[redderflag]

Noob here. I have installed the latest version of the fork on my AC68U.
Tried overclocking to 1200,800 and the router wouldnt start.
Had to do a factory reset and set everything up again.
When I tried to overclock it to 1100,666, it worked fine.
I read somewhere that the bootloader version 1.0.1.6, which I have, restricts overclocking the memory. Is that true? If yes, is there any way around? Please advise! Thanks!

 

[john9527]

Just wanted to post a reminder/warning to those using the '#a' country code settings to increase channels and power levels. I was testing with the #a settings active, and experienced a loss of access for all my 5GHz clients. After investigating, I found that I had the channel selection on the router set to Auto, and the router had changed channels to a set that was not supported by my clients. Specifying a channel known to be in my region, immediately brought everything back.

So, if you are using the #a country settings, you must specify the channel in the router settings or you may experience random loss of access/disconnects. Although the probability is much lower on the 2.4 GHz band, the same is true of both channel bands (2.4 GHz and 5 GHz)

 

[john9527]

Noob here. I have installed the latest version of the fork on my AC68U.
Tried overclocking to 1200,800 and the router wouldnt start.
Had to do a factory reset and set everything up again.
When I tried to overclock it to 1100,666, it worked fine.
I read somewhere that the bootloader version 1.0.1.6, which I have, restricts overclocking the memory. Is that true? If yes, is there any way around? Please advise! Thanks!

The issue with the 1.0.1.6 bootloader refer to the 'Turbo' option under 'Administration/Performance tuning' tab. With 1.0.1.6 this option does not work and you need to ensure that the LED option is selected.

Once this is done, you should be able to overclock both cpu and memory with the nvram set clkfreq= commands. While most AC68's can overclock to 1200, I've seen a few reports of some that would not and would hang on boot.

To confirm what you are really running.....

nvram get clkfreq show show what you had set
cat /proc/cpuinfo should show the following for the bogomips values

Stock - about 1500
1000 overclock - 1900 to 2000
1200 overclock - about 2400

 

[redderflag]

The issue with the 1.0.1.6 bootloader refer to the 'Turbo' option under 'Administration/Performance tuning' tab. With 1.0.1.6 this option does not work and you need to ensure that the LED option is selected.

Once this is done, you should be able to overclock both cpu and memory with the nvram set clkfreq= commands. While most AC68's can overclock to 1200, I've seen a few reports of some that would not and would hang on boot.

To confirm what you are really running.....

nvram get clkfreq show show what you had set
cat /proc/cpuinfo should show the following for the bogomips values

Stock - about 1500
1000 overclock - 1900 to 2000
1200 overclock - about 2400

Thanks..I set it to 1100,666 and that was what was showing when I do nvram get clkfreq
I get the bogomips value as 2398.61

 

[D._Manley]

Just wanted to post a reminder/warning to those using the '#a' country code settings to increase channels and power levels. I was testing with the #a settings active, and experienced a loss of access for all my 5GHz clients. After investigating, I found that I had the channel selection on the router set to Auto, and the router had changed channels to a set that was not supported by my clients. Specifying a channel known to be in my region, immediately brought everything back.

So, if you are using the #a country settings, you must specify the channel in the router settings or you may experience random loss of access/disconnects. Although the probability is much lower on the 2.4 GHz band, the same is true of both channel bands (2.4 GHz and 5 GHz)

Thank you for posting this John. I lost my 5G as well, thought I'd done something wrong even though everything looked good otherwise. I might try it again now that I know the culprit, I'd love to get just a little more "oomph" from the 5G radio which was why I tried it initially (another corner room router location).

 

[ml70]

If you lose some/all your 5G channels after playing with region settings, you have to specify the channels list you want, see the last 2 lines before nvram commit & reboot, this is for AC66:

wl country #a
wl autocountry_default #a
nvram set pci/1/1/ccode=#a
nvram set pci/1/1/regrev=0
nvram set pci/2/1/ccode=#a
nvram set pci/2/1/regrev=0
nvram set 0:regrev=0
nvram set 1:regrev=0
nvram set wl_reg_mode=off
nvram set wl0_reg_mode=off
nvram set wl1_reg_mode=off
nvram set wl_country=#a
nvram set wl0_country=#a
nvram set wl1_country=#a
nvram set wl_country_code=#a
nvram set wl0_country_code=#a
nvram set wl1_country_code=#a
nvram set wl_country_rev=0
nvram set wl0_country_rev=0
nvram set wl1_country_rev=0
nvram set regulation_domain=#a
nvram set regulation_domain_5G=#a
nvram set wl0_chlist="1 2 3 4 5 6 7 8 9 10 11 12 13 14"
nvram set wl1_chlist="36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165"
nvram commit && reboot

If you want to limit your channels to what's legal in your domain, delete the illegal channels and use the proper country/rev/reg codes.

 

[zbeyuz]

May I ask why RT-AC87U is not the list (yet)?

 

[john9527]

May I ask why RT-AC87U is not the list (yet)?

Will never be for this fork.....requires a whole new set of wireless drivers to be integrated which is outside the scope.

But, it looks like the new AC68P is likely to work if someone wants to give it a try.

 

[onix]

Traffic monitoring

I'm using the latest (version 4) of the fork. Is anyone else have trouble viewing the Wired traffic and speed? Nothing shows except the the bounding box of the graph and the vertical and horizontal axes. Wireless traffic on both 2.4GHz and 5.0GHz display beautifully.

 

[john9527]

I'm using the latest (version 4) of the fork. Is anyone else have trouble viewing the Wired traffic and speed? Nothing shows except the the bounding box of the graph and the vertical and horizontal axes. Wireless traffic on both 2.4GHz and 5.0GHz display beautifully.

The traffic monitor has always been a bit finicky, especially with PPPoE connections (at least from what I've read).

One thing you might try is disabling HW (NAT) Acceleration on the LAN/Switch Control tab and see if that changes things.

 

[john9527]

Another request for an N66 user.....I was catching up in another forum, and may have run across the command to display the power setting for the N66.

Can you try the following via SSH/telnet and post the output (if any)

wl -i eth1 txpwrlimit
wl -i eth2 txpwrlimit

Thanks!

EDIT: No need for any more replies to this, the commands are broken and don't give meaningful data.