[Experimental] Asuswrt-Merlin 384.13 test - AiMesh/DNSSEC through OpenSSL

[skeal]

On my ax88u the jffs gets messed up. Marks files as "not executable", changing is successful but doesn't hold up in a reboot. Going back to 384.12

 

[skeal]

Also the static address list was almost complete. I say almost because in the new formatting it dropped the last digit of every address.

 

[skeal]

All kinds of files are found but to be non-executable.

 

[dvohwinkel]

Are you recommending a full reset with default? sounds like a good time for one to me.. and a cleaning of the /jffs

 

[RMerlin]

Are you recommending a full reset with default?

No.

 

[RMerlin]

All kinds of files are found but to be non-executable.

If you ever flashed a recent Asus stock firmware, this is normal - they recently added code that makes all the /jffs/* files non-executable. That shouldn't be the case with my firmware however, unless they hid a copy of that code in a location that I've missed.

EDIT: indeed, Asus added one in a recent AX88U GPL merge that I missed. Removed.

 

[skeal]

If you ever flashed a recent Asus stock firmware, this is normal - they recently added code that makes all the /jffs/* files non-executable. That shouldn't be the case with my firmware however, unless they hid a copy of that code in a location that I've missed.

I browsed the files and they were in fact shown as non-executable. Nothing I could do to make chmod instruction stick.

 

[skeal]

If you ever flashed a recent Asus stock firmware, this is normal - they recently added code that makes all the /jffs/* files non-executable. That shouldn't be the case with my firmware however, unless they hid a copy of that code in a location that I've missed.

EDIT: indeed, Asus added one in a recent AX88U GPL merge that I missed. Removed.

Also the dnsmasq format problem when converting to the new system you have. The conversion somehow loses the last digit of the static addresses.

 

[RMerlin]

Also the dnsmasq format problem when converting to the new system you have. The conversion somehow loses the last digit of the static addresses.

Can you give me an example IP? It was working properly for me.

 

[skeal]

Can you give me an example IP? It was working properly for me.

Yes 192.168.50.51 was changed to 192.168.50.5. When I had a look at the dnsmasq.conf file it showed the addresses with the last digit dropped so I had like 20 devices with only four IPs. I use 192.168.50.x, 192.168.50.2x, 192.168.50.3x, 192.168.50.4x, 192.168.50.5x.
UPDATE: My addresses only use 2 digits in the last octet.

 

[RMerlin]

Yes 192.168.50.51 was changed to 192.168.50.5. When I had a look at the dnsmasq.conf file it showed the addresses with the last digit dropped so I had like 20 devices with only four IPs. I use 192.168.50.x, 192.168.50.2x, 192.168.50.3x, 192.168.50.4x, 192.168.50.5x.
UPDATE: My addresses only use 2 digits in the last octet.

The problem was with the total length - the buffer used during the conversion was only 32 chars large. Large enough for my test using shorter IPs and their MAC.

I increased the buffer size to 64, and started rebuilding all firmwares. I will upload fresh images later tonight. In the mean time I removed the existing builds to prevent more users from having truncated DHCP static lists. I recommend people restore their saved config backup AFTER they flash these new builds, to recover their original lease lists. (or you can also manually fix them all, the issue only occur during the first time conversion process).

 

[karma]

I dirty flashed the build on my RT-AC5300, after a reboot there weren't any AI Mesh options on the network map page. flashing back to stock.

 

[Kingp1n]

I dirty flashed the build on my RT-AC5300, after a reboot there weren't any AI Mesh options on the network map page. flashing back to stock.

All the info is provided in the 1st post ...did u follow the instructions below?

For AiMesh support, during this test phase, you must manually enable it. To do so, log in over SSH, then run the following commands:
Code:
touch /jffs/.gomesh
reboot

After your router is done rebooting, the webui should now be AiMesh-aware.

 

[karma]

All the info is provided in the 1st post ...did u follow the instructions below?

For AiMesh support, during this test phase, you must manually enable it. To do so, log in over SSH, then run the following commands:
Code:
touch /jffs/.gomesh
reboot

After your router is done rebooting, the webui should now be AiMesh-aware.

oh darn, I could have sworn i read everything... my bad. Thanks for pointing it out. I'll wait for the next build.

 

[RMerlin]

Van Halen's "no brown M&M" clause. (Google it).

 

[karma]

Van Halen's "no brown M&M" clause. (Google it).

are you suggesting I trash my dressing room? ;P

actually, i couldn't wait for a new build ( i don't think i have a dhcp static list?not sure what that is? manually assigned?) . Dirty flashed and enabled AI Mesh. I'm seeing clients connected to the node and was able to stream video from one of them to my PC connected via ethernet to the main router.

- removed node successfully.
- factory reset node (I always do it by holding down the wps button and power on) and added it back successfully. clients connected to it successfully.

looking good so far.

 

[RMerlin]

are you suggesting I trash my dressing room? ;P

Nah, leave that part out, unless you have a reputation to maintain

i don't think i have a dhcp static list?not sure what that is? manually assigned?

DHCP static leases on the LAN -> DHCP page. For assigning static IPs and hostnames to specific clients.

- removed node successfully.
- factory reset node (I always do it by holding down the wps button and power on) and added it back successfully. clients connected to it successfully.

Thanks. What are the router models and firmware versions of your routers and nodes?

 

[karma]

both my router and node are RT-AC5300s
router: 384.13_alpha1-g3070c0d611
node: 3.0.0.4.384_45717-gadd52a8

the main reason i was trying this out was to see if your firmware resolved my 2.4Ghz issue ( https://www.snbforums.com/threads/r...s-on-5ghz-cannot-see-devices-on-2-4ghz.54397/ ) but it doesn't look like it

 

[RMerlin]

both my router and node are RT-AC5300s
router: 384.13_alpha1-g3070c0d611
node: 3.0.0.4.384_45717-gadd52a8

the main reason i was trying this out was to see if your firmware resolved my 2.4Ghz issue ( https://www.snbforums.com/threads/r...s-on-5ghz-cannot-see-devices-on-2-4ghz.54397/ ) but it doesn't look like it

Wifi code is closed source, and will always be 100% identical to stock firmware.

 

[RMerlin]

Fresh builds have been generated, they should be published to Onedrive in the coming minutes.