How to access http://localnode.local.mesh:8080/ through NAT?
In this case, the AREDN GL-AR300M16 node is configured as a WAN interface. It grabs WiFi from a distant Starlink and sends it via ethernet to a LAN port(configured as secondary WAN) on my home router ASUS RT-AC66U. It works fine in this setup providing a fast backup to primary slow 768k DSL. I don't really need the interface, it just works.
The problem comes when I want to enable mesh and reverse the whole setup; using the home router to supply internet to the mesh which is linking my robots. In order to do that, I think I need to access the node webpage, but http://localnode.local.mesh:8080/ does not work. Presumably because the node is not local, but on the WAN. Also it goes through NAT. I think this might require a static route but not sure.
Ideally I would avoid the node web interface all together and load one of two saved configurations, one for mesh and one for WAN interface from a command line. A script could also load the corresponding profile onto the home router. Is that possible?
After writing that, it occurred to me that the solution may be to just change the home router configuration first, turning off dual WAN, so the port becomes a normal LAN port again.
Posting anyway in case people have ideas.
In this case, the AREDN GL-AR300M16 node is configured as a WAN interface. It grabs WiFi from a distant Starlink and sends it via ethernet to a LAN port(configured as secondary WAN) on my home router ASUS RT-AC66U. It works fine in this setup providing a fast backup to primary slow 768k DSL. I don't really need the interface, it just works.
The problem comes when I want to enable mesh and reverse the whole setup; using the home router to supply internet to the mesh which is linking my robots. In order to do that, I think I need to access the node webpage, but http://localnode.local.mesh:8080/ does not work. Presumably because the node is not local, but on the WAN. Also it goes through NAT. I think this might require a static route but not sure.
Ideally I would avoid the node web interface all together and load one of two saved configurations, one for mesh and one for WAN interface from a command line. A script could also load the corresponding profile onto the home router. Is that possible?
After writing that, it occurred to me that the solution may be to just change the home router configuration first, turning off dual WAN, so the port becomes a normal LAN port again.
Posting anyway in case people have ideas.