[Beta] Asuswrt-merlin 380.68 Beta is now available

[wideglide123]

Everything is running well on my AC5300 with beta 1....

Thanks...

 

[hjohan13]

Everything is running well on my AC5300 with beta 1....

Thanks...

Totally agree......works like a charm. 18 items connected (online) to the router at the moment. Another 16 offline....

 

[Nigel Jones]

I decided to reflash the router a second time, and this time this error is not present.... Must have been an issue with the original flash....

I'll try reflashing ... I too had the squashfs error. However NTP seems to be fine - no errors.

Ok reflash done ... the squashfs errors have gone.. (no NTP errors either)

This is on the AC3200

 

[tyreman]

Working okay here since yesterday

 

[skeal]

Installed on my AC-3100/CA and it is working great!! I love the new look and feel!!

 

[highwire]

I don't think internal name resolution works while in AP mode, only in Router mode.

DNS resolution does work in AP mode if the user sets the IP address of a DNS server in the LAN->LAN IP->DNS Server1 and/or DNS Server2 field. In my case, I just set the DNS Server1 entry to the IP address of my main router which takes care of the DNS lookups.

 

[skeal]

This may be a bug we can fix. When you go to syslog and click in the log window it will auto refresh for you, however, it also triggers auto refresh while trying to use scroll bars to navigate a long message. Makes it nearly impossible to use scroll bars.

 

[RMerlin]

But while on 380.67 (still AP Mode), the NTP update worked just fine and I never got those messages.... Something must have changed....

Can't reproduce it here, works for me. I would double check your AP configuration, especially if you have it set manually rather than use DHCP.

 

[RMerlin]

This may be a bug we can fix. When you go to syslog and click in the log window it will auto refresh for you, however, it also triggers auto refresh while trying to use scroll bars to navigate a long message. Makes it nearly impossible to use scroll bars.

Works properly for me using Chrome. There is actual code in place to ensure that auto-scroll only occurs if the content is currently at the bottom of the list. What browser are you using?

 

[RMerlin]

DNS resolution does work in AP mode if the user sets the IP address of a DNS server in the LAN->LAN IP->DNS Server1 and/or DNS Server2 field. In my case, I just set the DNS Server1 entry to the IP address of my main router which takes care of the DNS lookups.

I suspect that limitation might have been lifted by Asus at some point in the past, because it used to not have working name resolution.

 

[skeal]

Works properly for me using Chrome. There is actual code in place to ensure that auto-scroll only occurs if the content is currently at the bottom of the list. What browser are you using?

Im using a chrome browser on lubuntu.

EDIT: Tried the same thing on my tablet. Chrome on android. Works fine. So its the version of Chrome used for lubuntu.

 

[MXM]

DNS resolution does work in AP mode if the user sets the IP address of a DNS server in the LAN->LAN IP->DNS Server1 and/or DNS Server2 field. In my case, I just set the DNS Server1 entry to the IP address of my main router which takes care of the DNS lookups.

I made the change you recommended and then NTP worked just fine with the FQDN as opposed to the IP address...

But since in AP Mode the router has the 'Connect to DNS Server Automatically' turned On/Yes, why would it not work that way? Is this a glitch?

 

[MXM]

Can't reproduce it here, works for me. I would double check your AP configuration, especially if you have it set manually rather than use DHCP.

The RT-AC3200 has the 'Get LAN IP Automatically' turned On/Yes.... And the router page is populated with the right IP address/gateway information.

And all wireless devices on it work just fine (get IP addresses from the main router, along with DNS resolution).

 

[RMerlin]

The RT-AC3200 has the 'Get LAN IP Automatically' turned On/Yes.... And the router page is populated with the right IP address/gateway information.

And all wireless devices on it work just fine (get IP addresses from the main router, along with DNS resolution).

Is the DNS pushed by your primary router a public one (ISP, Google, etc...), or the router's own IP?

 

[TheOldMan]

As I glanced over the router boot up log (RT-AC3200 in AP Mode), I saw all these error messages that I've never seen before.... What seems to be the problem, and how do I fix this? Thanks...

Jul 31 18:00:12 kernel: brd: module loaded
Jul 31 18:00:12 kernel: loop: module loaded
Jul 31 18:00:12 kernel: pflash: found no supported devices
Jul 31 18:00:12 kernel: bcmsflash: found no supported devices
Jul 31 18:00:12 kernel: Boot partition size = 524288(0x80000)
Jul 31 18:00:12 kernel: lookup_nflash_rootfs_offset: offset = 0x200000
Jul 31 18:00:12 kernel: nflash: squash filesystem with lzma found at block 29
Jul 31 18:00:12 kernel: Creating 4 MTD partitions on "nflash":
Jul 31 18:00:12 kernel: 0x000000000000-0x000000080000 : "boot"
Jul 31 18:00:12 kernel: 0x000000080000-0x000000200000 : "nvram"
Jul 31 18:00:12 kernel: 0x000000200000-0x000004000000 : "linux"
Jul 31 18:00:12 kernel: 0x0000003b2af0-0x000004000000 : "rootfs"
Jul 31 18:00:12 kernel: PPP generic driver version 2.4.2
Jul 31 18:00:12 kernel: PPP MPPE Compression module registered
Jul 31 18:00:12 kernel: NET: Registered protocol family 24
Jul 31 18:00:12 kernel: PPTP driver version 0.8.5
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache ent�U�4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:12 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <4>dhd_detach(): thread:dhd_watchdog_thread:176 terminated OK
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to r8
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read data cache entry [4f5a10]
Jul 31 18:00:13 kernel: <3>SQUASHFS error: Unable to read page, block 4f5a10, size deb8
Jul 31 18:00:13 kernel: <4>dhd_detach(): thread:dhd_watchdog_thread:16c terminated OK
Jul 31 18:00:13 kernel: <6>br1: port 1(eth1) entering forwarding state
Jul 31 18:00:13 kernel: <6>device eth1 left promiscuous mode
Jul 31 18:00:13 kernel: <6>br1: port 1(eth1) entering disabled state
Jul 31 18:00:13 kernel: <4>g_thread:166 terminated OK

My RT-AC3200 does the same thing. I think it needs to be manually stopped and started to clear the errors. Correct me if I'm wrong?

 

[MXM]

Is the DNS pushed by your primary router a public one (ISP, Google, etc...), or the router's own IP?

The DNS is pushed by my router. I have the RT-AC3200 behind a ER-8 Pro....
I used the router IP address in the RT-AC3200 DNS and that worked fine....

 

[heysoundude]

Im using a chrome browser on lubuntu.

EDIT: Tried the same thing on my tablet. Chrome on android. Works fine. So its the version of Chrome used for lubuntu.

Apologies in advance for this OT diversion, everyone -

@skeal have you tried brave? brave.com

 

[RMerlin]

Currently having some issues with SmartConnect showing SSID as "open" when WPA2 Personal is set on my RT-AC88U.
Not sure what I broke, but I factory reset after updating to this latest Beta just to be on the safe side.
Now if I keep 2.4 and 5 bands as separate, things are fine and will show as "Secured" on other devices.
Going through SmartConnect and setting them with WPA2 for some reason bugs them both into being listed as "open" and is easily reproduced.

Something I'm missing that I may have set before the restore that's messing me up?

Where does it show as open exactly? It properly reports WPA2 for me on the Wireless General page as well as on the Network Map page.

 

[hw1380]

I've installed 380.66_4 on my RT-AC68U and would like updating to 380.68-beta with factory reset.
Do I need to make a factory reset again once I've installed the final release?

 

[RMerlin]

I've installed 380.66_4 on my RT-AC68U and would like updating to 380.68-beta with factory reset.
Do I need to make a factory reset again once I've installed the final release?

No, there shouldn't be any significant changes requiring one, unless you encounter any unusual wifi issues.