What's new

SSH Command - NAT Acceleration for AI Mesh Node

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

abracadabra11

Regular Contributor
Is there an SSH command to look up whether NAT Acceleration is active on an AI Mesh Node?

Recently connected by AI Mesh Node via MOCA to the Main Router and I'm seeing about 500Mbps when conducting iperf3 testing from my wired Desktop (ethernet connection to AI Mesh Node) to the Main Router. When I remove the Node and connect the Desktop directly to the MOCA adapter, throughput jumps to about 750Mbps so there appears to be a bottleneck with the Node (RT-AC68U).
 
I think the best clue would be to run top on the node and then see if the CPU load goes to 100% when you do your speed test.
 
I think the best clue would be to run top on the node and then see if the CPU load goes to 100% when you do your speed test.
I did that earlier and I was hitting around 75% or so. Not 100% so I suspected that this wasn't the limiting factor, but wanted to check command directly if available.
 
NAT (HW) acceleration is a kernel model that accelerates traffic as it is routed between the WAN and the LAN. Assuming the node works much like an access point it doesn't have a WAN interface and is not routing anything so the NAT acceleration is not applicable.
 
NAT (HW) acceleration is a kernel model that accelerates traffic as it is routed between the WAN and the LAN. Assuming the node works much like an access point it doesn't have a WAN interface and is not routing anything so the NAT acceleration is not applicable.
That's good to know, but the AI Mesh Node is connected through the WAN port to the Main Router. So perhaps it's still relevant?
 
No. The nodes don't do any NAT, only the primary router does. So hardware acceleration is only relevant to the main router.
 
Your post did remind me of a "feature" I came across when trying to debug an anomaly with QoS using iperf in John's fork a few years ago.

The relevant part here was that with my RT-AC68U the maximum router to LAN throughput I could get was about 600 Mbps. Here's part of a conversation I had at that time:

The discrepancy does appear to be caused by generic-segmentation-offload being set on br0. Unfortunately whilst turning off GSO does correct the numbers it also significantly reduces the Router to LAN throughput. The maximum throughput with GSO is about 600Mbps, without it it drops to half that :(. In both cases the throughput is limited by the router's CPU (and TCP buffer size).

It's a shame that TC can't seem to work this out, especially since in different circumstances it could really mess up the traffic flows. Maybe it's a bug. Ironically the TLDP documentation even mentions GSO and recommends turning it off to improve latency.

"Since TSO, GSO, UFO and GRO greatly increase the number of bytes which can be queued in the driver queue you should disable these optimizations if you want to optimize for latency over throughput. It’s doubtful you will notice any CPU impact or throughput decrease when disabling these features unless the system is handling very high data rates."

That last sentence is doubly ironic.:rolleyes:

gso1.png
 
Your post did remind me of a "feature" I came across when trying to debug an anomaly with QoS using iperf in John's fork a few years ago.

The relevant part here was that with my RT-AC68U the maximum router to LAN throughput I could get was about 600 Mbps. Here's part of a conversation I had at that time:
That's interesting - thanks.

I was thinking about reconfiguring the node in AP mode and retesting that way, but I've got a lot of cable ties securing the wiring for both devices (among other things) and am hesitant to test and find that I should go back to the AI Mesh configuration (i.e. if similar throughput, might as well just keep AI Mesh for configuration simplicity). Moving the AI Mesh node to rebind it to the main router would not be fun.

Any idea if there are SSH commands that I can use to backup the current AI Mesh node configuration so that I can just flash the configuration rather than pairing the devices again?
 
Any idea if there are SSH commands that I can use to backup the current AI Mesh node configuration so that I can just flash the configuration rather than pairing the devices again?
I don't use AiMesh but I would assume it's the usual NVRAM "Save settings" normally done through the GUI. From the command line that's:

nvram save yourfilename
 

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top