What's new

Asuswrt-Merlin 376.44 Beta 1 is out

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

I installed 376_44_beta2 on top of 374_43_2 on my RT-AC68U without any issues.
Jffs doesn't erase my files and new space is 2.37 / 94.75 MB
I had to reboot 2 times and everything working as is should.

EDIT: Under clientstaus my tv report wifi with 5 stroke when connected but when turn tv off, report as a LAN with lan symbol.

Thank you RMerlin.
 
Last edited:
Issues with mjpgstreamer on betas

I'm having problems running mjpgstreamer on both betas on ac-66u, it was running fine previously. It's seems it could a problem with usb (I think), this is what happens when mjpgstreamer starts:

Jul 30 14:53:57 kernel: Linux video capture interface: v2.00
Jul 30 14:53:58 kernel: uvcvideo: Found UVC 1.00 device Microsoft® LifeCam Cinema(TM) (045e:075d)
Jul 30 14:53:58 kernel: uvcvideo: No streaming interface found for terminal 2.Unhandled kernel unaligned access[#1]:
Jul 30 14:53:58 kernel: Cpu 0
Jul 30 14:53:58 kernel: $ 0 : 00000000 00000000 87a6d80c 00000507
Jul 30 14:53:58 kernel: $ 4 : c032bdc0 c0329260 c02f7f60 00002c83
Jul 30 14:53:58 kernel: $ 8 : 00000000 80290430 00000000 8680d01c
Jul 30 14:53:58 kernel: $12 : 80393a88 80393a90 00000002 00000000
Jul 30 14:53:58 kernel: $16 : 823964f8 8735b000 87b59700 82396480
Jul 30 14:53:58 kernel: $20 : 823964dc 82396480 823964d0 823964dc
Jul 30 14:53:58 kernel: $24 : 00000010 00000000
Jul 30 14:53:58 kernel: $28 : 875aa000 875abcd8 c02f0000 c02f58ec
Jul 30 14:53:58 kernel: Hi : 00000109
Jul 30 14:53:58 kernel: Lo : 99999a82
Jul 30 14:53:58 kernel: epc : c02f590c uvc_status_init+0x78/0x24c [uvcvideo] Tainted: P
Jul 30 14:53:58 kernel: ra : c02f58ec uvc_status_init+0x58/0x24c [uvcvideo]
Jul 30 14:53:58 kernel: Status: 1100fc03 KERNEL EXL IE
Jul 30 14:53:58 kernel: Cause : 00000010
Jul 30 14:53:58 kernel: BadVA : 0000050f
Jul 30 14:53:58 kernel: PrId : 00019749
Jul 30 14:53:58 kernel: Modules linked in: uvcvideo input_core v4l2_int_device v4l2_common videodev 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 sr_mod cdrom cdc_mbim qmi_wwan cdc_wdm cdc_ncm rndis_host cdc_ether asix usbnet usblp ohci_hcd ehci_hcd thfsplus tntfs(P) tfat(P) ext2 ext3 jbd mbcache usb_storage sg sd_mod scsi_wait_scan scsi_mod usbcore jffs2 zlib_inflate zlib_deflate nf_nat_pptp nf_conntr
Jul 30 14:53:58 kernel: Process insmod (pid: 854, threadinfo=875aa000, task=822cd400)
Jul 30 14:53:58 kernel: Stack : 86eb6380 823964dc c02f0000 8002b7c8 82396280 86eb6380 823964dc 86eb6384
Jul 30 14:53:58 kernel: 823964cc 86eb6380 c02edfc4 c02ee064 00000001 00000002 00000001 82396380
Jul 30 14:53:58 kernel: 0000045e 0000075d 800ccb14 82396494 ffffffff 00000000 823964cc 823964d4
Jul 30 14:53:58 kernel: 87a9a600 c02fb338 87a9a6c4 80360000 c02fb368 8034df00 0000002b 0000002b
Jul 30 14:53:58 kernel: c04403d4 c00e3fc0 87a9a600 c02fb540 87518068 87adee60 87a9a620 00000000
Jul 30 14:53:58 kernel: ...
Jul 30 14:53:58 kernel: Call Trace:
Jul 30 14:53:58 kernel: [<c02f590c>] uvc_status_init+0x78/0x24c [uvcvideo]
Jul 30 14:53:58 kernel: [<c02edfc4>] uvc_probe+0x998/0xf74 [uvcvideo]
Jul 30 14:53:58 kernel: [<c00e3fc0>] usb_probe_interface+0x7c/0x12c [usbcore]
Jul 30 14:53:58 kernel: [<801262dc>] driver_probe_device+0xc4/0x29c
Jul 30 14:53:58 kernel: [<8012686c>] __driver_attach+0x204/0x24c
Jul 30 14:53:58 kernel: [<80125180>] bus_for_each_dev+0x58/0x98
Jul 30 14:53:58 kernel: [<80125648>] bus_add_driver+0xb4/0x1ec
Jul 30 14:53:58 kernel: [<c00e3634>] usb_register_driver+0xb8/0x18c [usbcore]
Jul 30 14:53:58 kernel: [<c02af088>] uvc_init+0x88/0xb8 [uvcvideo]
Jul 30 14:53:58 kernel: [<8004eb4c>] sys_init_module+0x178/0x161c
Jul 30 14:53:58 kernel: [<80013aa4>] stack_done+0x20/0x40
Jul 30 14:53:58 kernel: Code: 8c430030 24420004 24c67f60 <8c670008> afa20010 3c028010 24050040 2442b300 0040f809
Jul 30 14:53:58 kernel: Fatal exception: panic in 5 seconds
 
I am running into an odd problem of the IPV6 "Other Stateful Configuration flag" flipping between "true" or "false" every few seconds to every few minutes, and being logged on my Windows 7 machine as below. Both wifi channels are off. When looking at the processes, there are 2 copies of rndnsd AND radvd running at the same time, which I have not noted before. Save for that IPV6 appears to be working, but a lot of messages are randomly being generated in the DHCPv6 logs of at least two Windows 7 machines.

Thanks,

Pablo

"Router Advertisement settings have been changed on the network adapter 12. The current M - Managed Address Configuration flag is false and the O - Other Stateful Configuration flag is true. User Action: If you are seeing this event frequently, then it could be due to frequent change in M and O flag settings on the router in the network. Please contact your network administrator to have it resolved."
I forgot to note that the DHCP flipping is on an AC56, with essentially vanilla install of the beta install described in this thread. The only additions I made were to dnsmasq-conf.add to which I included "read-ethers". I also have an init-script that reboots the router daily.

Finally and related the exclusion of IPSEC from the AC56, it appears that target.mak does has BWDPI = No. This is rather then "Yes". As it stands I can still use the VPN with the beta build for asuswrt - merlin

Pablo Abonia
 
Finally got 5GHz enabled and set to auto I get channel 149 and 80MHz. Any changes it reverts to channel 36 and 20MHz...

Finally got it to work and can change 5GHz settings while maintaining 80MHz and channel. Had to fight with this one and perform several resets unlike any other builds to date.
 
Have AC66U using .44 beta 1 and 2.4 GHz signal is possibly a little stronger. From my favorite location on the other side of the house with a laptop and inSSIDer 2.1 I am seeing a constant -50 dbm signal compared to 50 - 55 dbm with ver .43

Streamed a couple HDX movies last night with Roku box and no issues or buffering. Ipv6 working well on Time Warner cable. New GUI is fast with no issues so far.

Thank you Merlin!

Edit: Just installed .44 Beta 2 and there appears to difference in 2.4 GHz signal strength compared to Beta 1 on my AC66U.
 
Last edited:
Not sure if this will help anyone, but I was having the same 5ghz issues on my AC66U. I only have the standard 4 channels, whereas i had the higher range too, oh well.

My settings
Wireless Mode : Auto
Bandwidth : 80Mhz
Channel : 44

Any other configuration I used was reverting to Channel 36 20Mhz as reported, but with this config I have 80Mhz reported and confirmed on my HTC One.

Oh and I must thank Merlin for a brilliantly stable firmware.
 
Initial observation.

a. Wireless icon at top right does not report the "extension channel" for 5G connection. It only shows the control channel when mouse pointer is ontop of the wireless icon. According to inSSIDer I have the control channel and extension set properly.

Since 374.44 Beta 1, the wireless icon will now display channel + width instead of control + extension channel. This was done because it wasn't always reliable to begin with, and also because the extension channel cannot be retrieved from the Quantenna radio.

b. wl0_country_code is set for US
wl1_country_code is set for Q2
regulation_domain is set for US
regulation_domain_5G is set for Q2
pci/1/1/ccode is set to US
pci/2/1/ccode is set to Q2
Are the Q2 settings above normal for a US RT-N66U B1 model? If not, what changed the settings?


AFAIK, the country settings should now be automatically applied from what's in the CFE. The previous EM builds (up to 376.44 Beta 1) were changing that to Q2. If unsure, try a factory default reset and see which value gets applied to nvram.
 
Have I to set i to 1? N66U, Beta1 flashed, now beta2 ;)

Code:
admin@RT-N66U:/tmp/home/root# nvram get wl1_nband
0
admin@RT-N66U:/tmp/home/root#

Set it to "1" just to be safe, as this is the default value.
 
Cool :cool:


I had 3.0.0.4.374.43_0 intsalled and flashed this over it.

AFter finishing, it said on the scrren to manually reboot.

After manually rebooting, all setting were gone, back to original.

So I quickly flashed back to 3.0.0.4.374.43_0, and did a factory restore, and then uploaded the settings file ( saved before flashing to beta2).

But the username still was admin, DHCP reservations gone, DDNS details gone, guest network details reset, DNS filtering reset, URL filtering reset, country, some other system settings as well.
But on top of that, all my SAMBA/NFS and usb hdd permissions, all gone :(


Is this supposed to happen? is the saved settingsbackup meant to have all those missing on restore??

That's weird, because a good part of those SMB settings are actually stored on the USB disk itself, not in nvram. Maybe you had some corrupted setting in nvram causing issues. I know that in recent versions Asus has implemented some safeguard against corrupted nvram which might lead to reverting to factory defaults in case of an issue.
 
Code:
Jul 30 12:15:02 openvpn[1638]: WARNING: using --duplicate-cn and --client-config-dir together is probably not what you want
Jul 30 12:15:02 openvpn[1638]: WARNING: --ifconfig-pool-persist will not work with --duplicate-cn

I need "pool-persist", is it possible to remove duplicate-cn from default config?

Create an openvpnserver1.postconf script to remove duplicate-cn.
 
Hi Merlin!

Just updated from beta1 to beta2 and decided to give Aicloud + SmartSync a try... until I figure out how to regain secure access to lighttpd (owncloud) and ssh.

In the new graph bar the cpu was at 100% all the time... until I disabled SmartSync (and keep AiCloud on).

The command TOP showed inotify using almost all the cpu constantly.
I have a RT-16N with a 320gb ext3 connected, using entware and firmware .43 beta2
Seems to be a problem with either Asuswebstorage or inotify. I'll take a look, the two versions could be out-of-sync.
 
Installed Beta_2 and it killed my 5GHz band on my RT-AC66R. I ran the nvram commands as instructed.

Go to your 5 GHz wireless settings, and re-apply them.
 
Is this new beta fix the false info in system log > wireless log "2.4 GHz radio is disabled" in the 5GHZ section when we disable 5GHZ?

Yes, that was the nvram corruption entry in the changelog.
 
I installed 376_44_beta2 on top of 374_43_2 on my RT-AC68U without any issues.
Jffs doesn't erase my files and new space is 2.37 / 94.75 MB
I had to reboot 2 times and everything working as is should.

EDIT: Under clientstaus my tv report wifi with 5 stroke when connected but when turn tv off, report as a LAN with lan symbol.

Thank you RMerlin.

That's a known limitation of Asus's new Networkmap code. Once a wireless client is disconnected, networkmap has no way of knowing if it was originally wired or wireless.
 
I'm having problems running mjpgstreamer on both betas on ac-66u, it was running fine previously. It's seems it could a problem with usb (I think), this is what happens when mjpgstreamer starts:

Jul 30 14:53:57 kernel: Linux video capture interface: v2.00
Jul 30 14:53:58 kernel: uvcvideo: Found UVC 1.00 device Microsoft® LifeCam Cinema(TM) (045e:075d)
Jul 30 14:53:58 kernel: uvcvideo: No streaming interface found for terminal 2.Unhandled kernel unaligned access[#1]:


The kernel is crashing. Recompile any custom-made kernel modules you are using, they might not match the current set of kernel options.
 
Finally and related the exclusion of IPSEC from the AC56, it appears that target.mak does has BWDPI = No. This is rather then "Yes". As it stands I can still use the VPN with the beta build for asuswrt - merlin

Pablo Abonia

The kernel options are shared amongst all ARM devices, which is why IPSEC modules are disabled for all three of them. You will have to modify kernel options and recompile the firmware if you want to enable IPsec support.

Plus, once Asus implements DPI support on the other ARM devices (I suspect they eventually will), you will be back to square one, so best get used to it already.
 
EU region AC56 here.
5GHz wireless is always reverting to channel 36, 20MHz no matter what I do.
The client is an 866Mbps so I need an 80MHz fat channel.

Any ideas about what can be made?
 
Since 374.44 Beta 1, the wireless icon will now display channel + width instead of control + extension channel. This was done because it wasn't always reliable to begin with, and also because the extension channel cannot be retrieved from the Quantenna radio.
In this case(N66U), the icon is only showing the control channel, no width.

AFAIK, the country settings should now be automatically applied from what's in the CFE. The previous EM builds (up to 376.44 Beta 1) were changing that to Q2. If unsure, try a factory default reset and see which value gets applied to nvram.

Okay that's good to know. Either mtd-erase -d nvram is not completely erasing the nvram or my bootloader's domain info in 5GHz has changed after flushing to 1.4 bootloader. I have defaulted the settings using the mtd method but after the reset, I've notice the time zone(eastern time) didn't change so it seems the factory reset didn't completely erased the nvram. I'm thinking the bootloader could have not done these since the 2.4/5GHz domains have different country codes, it should be the same?
 
Upgraded to Beta 2 successfully.
One small hiccup though:
After firmware upload i rebooted router as required.
I almost had an heart attack when after router finished booting, all LEDs went off!
Router was accessible though, during booting after upgrade ledsoff.sh script kicked in for some reason (it is set to activate at 22:00 which wasn't the case).
I set that nvram value and rebooted the router. LEDs were fine after that.
 

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top