Release [Fork] Asuswrt-Merlin 374 LTS release 46E8 (Superseded)

[dave14305]

Thanks for the pointer....exactly what I am seeing as well....
May be time to wait for the first point release.

Jan 20 13:46:18 dnsmasq[16246]: failed to send packet: Network is unreachable
Jan 20 13:46:18 dnsmasq[16246]: failed to send packet: Address family not supported by protocol

It's interesting that there's no discussion of the log issue on dnsmasq-discuss mailing list.

 

[john9527]

Yes, it was discussed multiple times already, i know about it, but as far as i'm concerned no permanent solution was found Only the temporal "Disable NAT acceleration" option. This solution works, but it is drastically decreases router's performance
Please note, that very first complaints were dated on 2018, still no solution found

Do you see one of the classic symptoms of Android? Repeated DHCPDISCOVER or DHCPREQUEST followed by DHCPACK. The phone refuses to take 'yes' for an answer and gets the router tied up in this loop. Unfortunately, I don't know of anyway to try and intercept that sequence outside of the closed source code.

 

[octopus]

Hi

As discusion in this thread I have found this:
"broken_system_clock set". My clock is synced with GPS.

ASUSWRT-Merlin RT-AC56U_3.0.0.4 Wed Jan 13 11:28:03 UTC 2021
[email protected]:/tmp/home/root# nvram show | grep ntp_
ntp_server0=se.pool.ntp.org
ntp_server1=europe.pool.ntp.org
ntp_ready=1
ntp_log_x=1
ntp_sync=1
ntp_server_tried=none
ntp_update=0

 

[ColinTaylor]

Hi

As discusion in this thread I have found this:
"broken_system_clock set". My clock is synced with GPS.

View attachment 29713

Yes I spotted that as well. It's not actually a bug/problem and should be ignored. It has nothing to do with NTP.

From what I've read it's behaved like this since e2fsprogs 1.41.12 (May 17, 2010) but didn't previously produce a message. The message was added in e2fsprogs 1.44.2.

e2fsck.conf(5) - Linux manual page

      broken_system_clock
              The e2fsck(8) program has some heuristics that assume that
              the system clock is correct.  In addition, many system
              programs make similar assumptions.  For example, the UUID
              library depends on time not going backwards in order for
              it to be able to make its guarantees about issuing
              universally unique ID's.  Systems with broken system
              clocks, are well, broken.  However, broken system clocks,
              particularly in embedded systems, do exist.  E2fsck will
              attempt to use heuristics to determine if the time can not
              be trusted; and to skip time-based checks if this is true.
              If this boolean is set to true, then e2fsck will always
              assume that the system clock can not be trusted.

 

[john9527]

As discusion in this thread I have found this:
"broken_system_clock set". My clock is synced with GPS.

borken-system_clock is an e2fsprogs compiler flag used to indicate there is no realtime clock in the system. As a result, you cannot use interval based checking for fsck (this is done when the drive is mounted, and even with a GPS clock, it won't be set yet),

Now, periodic checking is disabled by default in the mke2fs.conf file. DId you enable it with tune2fs? If you want to enable some automated checking, you can use the scheduler in the gui or use a mount count check via tune2fs which should also work.

 

[john9527]

Just to follow up on my previous post concerning dnsmasq 2.83
I've tabled it for now as being too unstable to pick up, Too many errors and dnssec appears to be broken for many sites.

If you are using dnssec with Stubby/DoT, I recommend using GetDNS as the dnssec validator (it's available in the gui on my fork).

I'lll keep an eye out for any further updates/developments.

 

[RMerlin]

Just to follow up on my previous post concerning dnsmasq 2.83
I've tabled it for now as being too unstable to pick up, Too many errors and dnssec appears to be broken for many sites.

If you are using dnssec with Stubby/DoT, I recommend using GetDNS as the dnssec validator (it's available in the gui on my fork).

I'lll keep an eye out for any further updates/developments.

Are you using OpenSSL or Nettle for dnsmasq crypto? If you use themiron's OpenSSL version, then the crypto code will need to be updated due to some of the changes done upstream by Simon.

That still leaves the IPv6 stuff that's broken however, and will require fixing upstream.

 

[john9527]

Are you using OpenSSL or Nettle for dnsmasq crypto?

I'm using Nettle 3.6 (I didn't go after the OpenSSL support). I checked and they just released 3.7 at the beginning of this month. I suppose I can give it one more shot with that update as well.

 

[octopus]

Yes I spotted that as well. It's not actually a bug/problem and should be ignored. It has nothing to do with NTP.

From what I've read it's behaved like this since e2fsprogs 1.41.12 (May 17, 2010) but didn't previously produce a message. The message was added in e2fsprogs 1.44.2.

e2fsck.conf(5) - Linux manual page

      broken_system_clock
              The e2fsck(8) program has some heuristics that assume that
              the system clock is correct.  In addition, many system
              programs make similar assumptions.  For example, the UUID
              library depends on time not going backwards in order for
              it to be able to make its guarantees about issuing
              universally unique ID's.  Systems with broken system
              clocks, are well, broken.  However, broken system clocks,
              particularly in embedded systems, do exist.  E2fsck will
              attempt to use heuristics to determine if the time can not
              be trusted; and to skip time-based checks if this is true.
              If this boolean is set to true, then e2fsck will always
              assume that the system clock can not be trusted.

Thank you, now I know!

 

[john9527]

It's interesting that there's no discussion of the log issue on dnsmasq-discuss mailing list.

There's now activity in dnsmasq-discuss....trying some test fixes (so far without success, but they have isolated the fix causing the problem)

 

[johndoe85]

I am getting an error when trying to flash my ASUS RT-AC66U B1

Gyazo

gyazo.com

 

[ColinTaylor]

I am getting an error when trying to flash my ASUS RT-AC66U B1

https://gyazo.com/136d535ad0f32282c47da9067953a087

See the installation instructions in LTS_OVERVIEW.pdf

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.

 

[johndoe85]

I cannot find the restoration tool for this.
And how do i access this "built in CFE Mini-Web Server" ?

Found it here:

RT-AC66U B1｜Whole Home Mesh WiFi System｜ASUS Global

ASUS AiMesh WiFi routers and WiFi systems let you create a mesh network with no dead zones, using any AiMesh-capable ASUS routers. Their superb performance and rich features makes them the perfect solution for advanced users.

www.asus.com

Asus.com seems to have diffrent webpages, the US one did not have any software of any kind at all.

 

[john9527]

There's now activity in dnsmasq-discuss....trying some test fixes (so far without success, but they have isolated the fix causing the problem)

The latest fix level, 2.84test3, appears to resolve the initial release problems.
The current beta has been refreshed to 47D7, and includes the dnsmasq DNSPOOQ security updates.

 

[L&LD]

@johndoe85, the link below may help.

RT-N66U not giving full gigabit download speed

I got a 1000 Mbps line since a couple of weeks and I use the Asus RT-N66U. But what strikes me is that the upload speed is constantly 940 Mbps while the download speed fluctuates between 800 and 840 Mbps. Does anyone have any idea if any setting needs to be changed to get the full 940 Mbps...

www.snbforums.com

 

[johndoe85]

So.. where do i find the default login for this firmware?

 

[L&LD]

192.168.1.1
admin
admin

 

[johndoe85]

It was still on my original login after flashing the firmware

I have done a factory reset now after flashing it to this firmware.

Though, i only get 100/100mbit with this firmware? Over CAT6 cable
Same with WiFi-5GHZ

Any settings for this nonsense?

 

[ColinTaylor]

I have done a factory reset now after flashing it to this firmware.

Though, i only get 100/100mbit with this firmware? Over CAT6 cable
Same with WiFi-5GHZ

Go to Tools > System Information > Network and check that HW acceleration is enabled.

 

[Vinzz]

Go to Tools > System Information > Network and check that HW acceleration is enabled.

I just switched from Merlin on an AC66U to this fork. I'm currently trying to identify connectivity issues to my ubiquiti unify APs which didn't happen with Merlin's old firmware (I was dumb enough to update the firmware of the APs at the same time so I guess it might be part of the problem since wired clients have no issue at all...).

Anyway, while doing so I found a tiny UI issue when wifi is disabled :

Just thought I'd report it here.