What's new
  • 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!

ASUS ROG Rapture GT-AXE16000 10G port 1 as WAN link in Aimesh

drabisan

Very Senior Member
If someone already added this information, appologies.
I do have 2xAXE16000, one router and one node. And finally I was able to run a cable between those 2. Wireless backhaul was doing alright, but not great. And I had to do this.
After cabling done, for reason I can't understand, on the node I pluged the cable on 10G port number 1. I switched "ethernet backhaul mode" to on and everything kept working as it should.
But AFAIK instructions were always to plug node on WAN port. Manual says so :)
I know 10G ports can be used as WAN links with a bit of configuration, but it seems that under the hood they can do that without any headache.
So now I have a 10G backhaul link that's stable and works just fine. I don't have enough powerful devices to test if I can exceed 2.5G, I can easily do 2G so I can't tell if the 10G backhaul can actually do that much.

But I thought worth sharing this information.
 
There is an "automatic" detection of WAN input to node, but it is best practice to explicitly configure the WAN port via AiMesh >> Management >> Backhaul Connection Priority.
 
If someone already added this information, appologies.
I do have 2xAXE16000, one router and one node. And finally I was able to run a cable between those 2. Wireless backhaul was doing alright, but not great. And I had to do this.
After cabling done, for reason I can't understand, on the node I pluged the cable on 10G port number 1. I switched "ethernet backhaul mode" to on and everything kept working as it should.
But AFAIK instructions were always to plug node on WAN port. Manual says so :)
I know 10G ports can be used as WAN links with a bit of configuration, but it seems that under the hood they can do that without any headache.
So now I have a 10G backhaul link that's stable and works just fine. I don't have enough powerful devices to test if I can exceed 2.5G, I can easily do 2G so I can't tell if the 10G backhaul can actually do that much.

But I thought worth sharing this information.
I do have the same configuration and can verify that everything is fine. Tested with 5g devices and they were ok . Also tested with a 10g switch on the node that has coloured leds indicators for the connections and the correct color appears. You do not need to have it on ethernet backhaul , auto works also fine on the last firmware ... I need auto because I also have an ET12 connected wirelessly and everything is fine there also ... auto was not working correctly on the 2 previous versions of the firmware but they fixed it on the last. I only wish that they have fixed the guest network pro also so that we could have different wifi signals on the 5ghz band as we could in 3.0.0.4 ... now they are all on top of each other ...
 
Last edited:
You do not need to have it on ethernet backhaul , auto works also fine on the last firmware
I prefer to lose the node rather than fall back to wireless backhaul and me not knowing in the wall cable broke down. Working or not working, I don't want that grey area in the middle.
And having only those 2 routers, I don't need to enable any compatibility.
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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