MerlinAU MerlinAU v1.5.3 - The Ultimate Firmware Auto-Updater (WEBUI + GNUTON SUPPORT!)

[pdc]

Option MN from the opening menu, see below
View attachment 67302
[...]
At least for me this is the case...
Note: From the command line/SSH, not in the GUI...

Thanks for clarifying. However, my main node menu does not have the 'AiMesh Node(s) Info' option. The AiMesh node is running Merlin, and MerlinAU is active and up to date (v1.5.2) on both nodes. If I type "mn" anyway, I get invalid selection.

Any ideas on how to enable the menu item? Thanks!

 

[ExtremeFiretop]

However, my main node menu does not have the 'AiMesh Node(s) Info' option.

That is your issue, your checking on the node instead of the primary router, read this part of his reply:

if running MerlinAU on the node the MN opption does not appear on the node, see below

 

[pdc]

That is your issue, your checking on the node instead of the primary router, read this part of his reply:

Sorry I wasn't clear, by main node I meant the primary router. I am using amtm via putty.

I dug into the code a bit, and nvram get sw_mode returns 1, so $aiMeshNodes_OK should be true.

For node_list,

asus_device_list=<3>GT-AX6000>[router-IP-addr]>[MAC addr]>0>dejeuner24>255.255.255.0>1

That doesn't have the mesh node listed, nor do I see the mesh IP address in any nvram variable, so I guess the answer is my router doesn't have the AiMesh node listed in nvram for some reason. It's not critical, I was just curious...

Thanks!

 

[ExtremeFiretop]

Sorry I wasn't clear, by main node I meant the primary router. I am using amtm via putty.

I dug into the code a bit, and nvram get sw_mode returns 1, so $aiMeshNodes_OK should be true.

For node_list,

asus_device_list=<3>GT-AX6000>[router-IP-addr]>[MAC addr]>0>dejeuner24>255.255.255.0>1

That doesn't have the mesh node listed, nor do I see the mesh IP address in any nvram variable, so I guess the answer is my router doesn't have the AiMesh node listed in nvram for some reason. It's not critical, I was just curious...

Thanks!

Ah I see, my apologies I thought you were trying to say the main menu on your node, when you said: "my main node menu"

That might be a bit of my diagnosed dyslexia showing and me reading stuff backwards.

I'm surprised it's not being populated. Do you experience any issues with the nodes at all? What models and firmware for each?

 

[kda]

thanks for the good works.
i have a question, the log files is this cleaned up automatic? (sometimes)

 

[ExtremeFiretop]

thanks for the good works.
i have a question, the log files is this cleaned up automatic? (sometimes)

It keeps one month of logs
Anything older than a month is deleted.

 

[pdc]

I'm surprised it's not being populated. Do you experience any issues with the nodes at all? What models and firmware for each?

The router GUI shows the AiMesh topology correctly and everything looks good. The router and mesh node are each GT-AX6000 routers running Melin 3006.102.4. I use 5 GHz wireless as the backhaul if that matters.

I looked at nvram getall and I don't see any nvram variables that include the IP address of the mesh node. If I look at MAC addresses, the mesh node shows up in a few nvram variables: apg1_dut_list, cfg_rekeylist, cfg_relist, and cfg_relist_x, but none have an obvious IP you could use to get info.

The mesh node is in auto-update mode so I mostly just ignore it, but it would have been interesting to see a summary from the router.

 

[visortgw]

The router GUI shows the AiMesh topology correctly and everything looks good. The router and mesh node are each GT-AX6000 routers running Melin 3006.102.4. I use 5 GHz wireless as the backhaul if that matters.

I looked at nvram getall and I don't see any nvram variables that include the IP address of the mesh node. If I look at MAC addresses, the mesh node shows up in a few nvram variables: apg1_dut_list, cfg_rekeylist, cfg_relist, and cfg_relist_x, but none have an obvious IP you could use to get info.

The mesh node is in auto-update mode so I mostly just ignore it, but it would have been interesting to see a summary from the router.

I see my node IPs in asus_device_list and cfg_device_list.

 

[ExtremeFiretop]

I see my node IPs in asus_device_list and cfg_device_list.

Those are the two keys we use, but it seems to me that it's missing from his device based on this:

For node_list,

asus_device_list=<3>GT-AX6000>[router-IP-addr]>[MAC addr]>0>dejeuner24>255.255.255.0>1

But I don't think he provided his value for: cfg_device_list

 

[visortgw]

Those are the two keys we use, but it seems to me that it's missing from his device based on this:



But I don't think he provided his value for: cfg_device_list

Personally, I would consider removing and re-adding the nodes.

 

[pdc]

I see my node IPs in asus_device_list and cfg_device_list.

Do you use a wireless backhaul? I'm a little suspicious that is why some folks see the IP there and some do not.

nvram get cfg_device_list = <GT-AX6000>[router IP]>[router MAC]>1

 

[visortgw]

Do you use a wireless backhaul? I'm a little suspicious that is why some folks see the IP there and some do not.

nvram get cfg_device_list = <GT-AX6000>[router IP]>[router MAC]>1

I use 6 GHz wIreless backhaul for one of four nodes with 2.5/10 Gbps wired backhaul for the remaining three nodes.

 

[aex.perez]

Personally, I would consider removing and re-adding the nodes.

A little curious...

I don't have a lot of flexibility to test this and not running 3006.102.5 or those devices either. But curious if the node, second GT-AX6000, is configured to operate as a AP instead of a node, would it still show up in the AiMesh Topology map, but not in either NVRAM variable on the main node/router? Can you access the GUI of the second GT-AX-6000 or upon accessing it are you redirected to the main device/router GUI?

On my nodes, these nvram variables have the IPAddr of the router. These two login_ip_str and cfg_masterip?

 

[ExtremeFiretop]

Do you use a wireless backhaul? I'm a little suspicious that is why some folks see the IP there and some do not.

nvram get cfg_device_list = <GT-AX6000>[router IP]>[router MAC]>1

I'm using wireless for the backhaul for everything myself

 

[visortgw]

A little curious...

I don't have a lot of flexibility to test this and not running 3006.102.5 or those devices either. But curious if the node, second GT-AX6000, is configured to operate as a AP instead of a node, would it still show up in the AiMesh Topology map, but not in either NVRAM variable on the main node/router? Can you access the GUI of the second GT-AX-6000 or upon accessing it are you redirected to the main device/router GUI?

On my nodes, these nvram variables have the IPAddr of the router. These two login_ip_str and cfg_masterip?

APs do not appear in AiMesh topology.

 

[aex.perez]

APs do not appear in AiMesh topology.

I know, but since I'm not running these devices, or firmware
Figured its worth asking about the operating mode of the devices, redirection when accessing the GUI or something in the firmware/device combo that allowed it

 

[pdc]

I'm using wireless for the backhaul for everything myself

So much for my hunch I might try dropping and reestablishing the mesh node, but it would be a while. I'll report back if I do.

 

[ExtremeFiretop]

MerlinAU 1.5.3 Released!

What's Changed/Fixed?:

PR: [ #508 ] - Manual F/W Update Checks When Automatic Switch is Disabled

• Modified code to allow users to perform manual F/W Update checks via the menu option even when the "Automatic F/W Update Checks" functionality is still disabled. (As requested by @vlord )
• Minor changes to show additional version tag when running the 'development' branch version. This allows users to quickly and easily check if they're running the latest 'development' version for testing & validation purposes.
• (Thanks @Martinski4GitHub )

PR: [ #510 ] - Fixed Issue with Uninstallation on Gnuton F/W

• On Gnuton F/W, there was an issue that generated an error and was preventing a full uninstallation of MerlinAU.
• See the report from @ExtremeFiretop here: Manual F/W Update Checks When Automatic Switch is Disabled #508 (comment).
  -(Thanks @Martinski4GitHub )

PR: [ #511 ] - Don't purge the configuration file early

• Modifying expected behavior while debugging. No expected user impact.

As always, we highly recommend you update ASAP as this includes functional improvements and little bug fixes.
Thanks!

 

[ExtremeFiretop]

I updated via the web UI this morning, and I noticed a minor cosmetic nit, which has probably been long-standing as I usually update either via auto update or CLI: when the update completes, the version number at the top of the web page is not updated until I refresh the browser.

@visortgw Just wanted to circle around that I am unable to replicate this report.
Just tested after the latest update we pushed out