Asuswrt-Merlin - Traffic Analyzer - Statistics: Hostname NVRAM Variable

[garycnew]

All:

Which Asuswrt-Merlin - Hostname NVRAM Variable is used for Traffic Analyzer - Statistics?

# nvram show | grep RT-AC66U_B1
odmpid=RT-AC66U_B1
lan_hostname=RT-AC66U_B1
lld2d_hostname=RT-AC66U_B1
wps_modelnum=RT-AC66U_B1
wps_device_name=RT-AC66U_B1

In older versions of Asuswrt-Merlin firmware, the Traffic Analyzer - Statistics used the lan_hostname to associate related statistics.

However, in the last version, it seems an alternate NVRAM variable is being used.

Thanks, again.


Gary

 

[garycnew]

None, Traffic Analyzer stores its data in an sqlite3 database located in /jffs.

Hi @RMerlin

What I meant to suggest is that Traffic Analyzer obtains the hostname from some Asuswrt-Merlin variable prior to storing it in the sqlite3 database.

In older versions of Asuswrt/Traffic Analyzer it was the lan_hostname variable that was used by Traffic Analyzer. However, it seems to have changed in more recent versions.

I noticed these Zeroconfig lines in the log and wonder if they are related?

<CODE>Jul 31 14:50:26 Living_Room-C293-07B6BDD-C avahi-daemon[1791]: Loading new alias name RT-AC66U_B1.
Jul 31 14:50:27 Living_Room-C293-07B6BDD-C avahi-daemon[1791]: Alias name "RT-AC66U_B1" successfully established.</CODE>

Note that the lan_hostname is set to Living_Room-C293, but Traffic Analyzer uses RT-AC66U_B1.

Thanks, again, for your time.

Respectfully,


Gary

 

[garycnew]

UPDATE:

It appears that "Network Map" uses the same hostname (RT-AC66U_B1) variable in question. It no longer seems to be the lan_hostname variable.

Which hostname variable does "Network Map" use to populate the "Clients Name" field?

Thanks, again.

 

[ColinTaylor]

I don't understand your question. You talk about lan_hostname, which is the host name of the router. Then you ask why this name doesn't appear in the client lists on the Traffic Analyzer and Network Map pages. So my question is why would you think the router's name would appear in the client list?

 

[garycnew]

I don't understand your question. You talk about lan_hostname, which is the host name of the router. Then you ask why this name doesn't appear in the client lists on the Traffic Analyzer and Network Map pages. So my question is why would you think the router's name would appear in the client list?

Hi @ColinTaylor

Apologies for the the lack of information. The lan_hostnames in question are those of the peripheral Asuswrt-Merlin Access Points (i.e., Living_Room-C293). However, the Primary Asuswrt-Merlin Router sees them as "RT-AC66U_B1" (opposed to their uniquely identified lan_hostname).

In older versions of Asuswrt/Traffic Analyzer, changing the lan_hostname variable on the Asuswrt-Merlin Access Points was seen and used by the Primary Asuswrt-Merlin Router for Network Map and Traffic Analyzer.

It appears that the Old & New NVRAM variables are the same.

Old NVRAM Variables:

# nvram show | grep RT-AC66U_B1
odmpid=RT-AC66U_B1
lan_hostname=Living_Room-C293
lld2d_hostname=RT-AC66U_B1
wps_modelnum=RT-AC66U_B1
wps_device_name=RT-AC66U_B1

New NVRAM Variables:

# nvram show | grep RT-AC66U_B1
odmpid=RT-AC66U_B1
lan_hostname=Living_Room-C293
lld2d_hostname=RT-AC66U_B1
wps_modelnum=RT-AC66U_B1
wps_device_name=RT-AC66U_B1

I did notice that the same "RT-AC66U_B1" hostname is reflected within the DHCP Server configuration; where, in older firmware versions it was the uniquely identified lan_hostname. Now, there is an (Optional) Hostname field for each DNCP reservation, but it does not seem to have any impact.

Something definitely changed in the newer firmware versions.

I'm wondering if the hostname is taken from Zeroconfig (avahi-daemon), now? How is the Zerconfig alias set?

Once, again, I appreciate your time and assistance.

Respectfully,


Gary

 

[ColinTaylor]

Ah, OK.

Perhaps the router is using "old" client names from its nvram custom clientlist?

nvram get custom_clientlist

 

[garycnew]

Ah, OK.

Perhaps the router is using "old" client names from its nvram custom clientlist?

nvram get custom_clientlist

It appears the Office and Living_Room Asuswrt-Merlin Access Points are listed, but there are several other Asuswrt-Merlin Access Points that are not.

RT-AC66U_B1>C0:56:27:7A:3C:73 (Office-3C73)
RT-AC66U_B1>94:10:3E:82:C2:93 (Living_Room-C293)

# nvram get custom_clientlist
RT-AC66U_B1>C0:56:27:7A:3C:73>0>2>>>>><RT-AC66U_B1>94:10:3E:82:C2:93>0>2>>>>>

 

[ColinTaylor]

If those two entries are the only ones in the nvram variable I suggest you erase them, restart networkmap and see what happens.

nvram set custom_clientlist=""
killall networkmap

EDIT: Getting back to your original idea. I have a vague recollection that AiMesh uses lld2d LLTD to detect clients. So perhaps you do need to manually change lld2d_hostname on your nodes.

 

[RMerlin]

I don't know, I never looked at that code. You will have to look at it yourself.

My initial guess would be that it's from networkmap. The webui has a series of functions in client_functions.js to provide detailed client information. It could also be from the Trend Micro code itself, if it's stored in the sqlite3 database. You will have to investigate the code.

 

[garycnew]

If those two entries are the only ones in the nvram variable I suggest you erase them, restart networkmap and see what happens.

nvram set custom_clientlist=""
killall networkmap

EDIT: Getting back to your original idea. I have a vague recollection that AiMesh uses lld2d to detect clients. So perhaps you do need to manually change lld2d_hostname on your nodes.

No Difference.

# nvram get custom_clientlist
RT-AC66U_B1>C0:56:27:7A:3C:73>0>2>>>>><RT-AC66U_B1>94:10:3E:82:C2:93>0>2>>>>>

# nvram set custom_clientlist=""

# nvram get custom_clientlist

# killall networkmap

# ps w | grep -i networkmap
32121 admin     3424 S    grep -i networkmap

# ps w | grep -i networkmap
  384 admin     3424 S    grep -i networkmap
32129 admin    15236 S    networkmap