You are here

WebServers Not Available through a tunnel

6 posts / 0 new
Last post
n5hzr
n5hzr's picture
WebServers Not Available through a tunnel

Greetings,

Two months ago I upgraded a GL iNet AR 150 router to firmware 3.22.8. It has been running non-stop for two months. This router supports a tunnel server with a half dozen tunnel clients, two radios, and a half dozen client machines with a couple of web servers attached.

Recently we notices that clients who were connected to this part of the mesh via the tunnel could not connect to the web servers. Browser clients directly connected by ethernet, or by DtD radios could connect to the web servers. The browser clients connected by a tunnel received a "Not Available" message on their browsers. These web clients COULD navigate the AREDNMesh web panels on the AR150 and it showed the service correctly (image in the next message). Clicking on the displayed service would give the user the "Not Available" message.

This router is on a net with over 20 nodes.

Rebooting this affected router fixed the problem. All clients could connect to the FLIGHT and PI-STAR web servers.

FYI, in the PING test graphic, the 172.31.64.170 IP address is in the tunnel network that the client is using. 

All is OK with my network now, but there appears to be some trouble with 3.22.8
 

File Attachment: 
Support File Attachment: 
n5hzr
n5hzr's picture
Mesh Image
This is the screen shot of the mesh.
Image Attachments: 
nc8q
nc8q's picture
WebServers Not Available through a tunnel

PingTest: I would expect that
ping pi-star.local.mesh
would resolve to 10.208.169.116 instead of 172.31.64.170 of an 'external router'. ?
Is the 'ping test computer' in the LAN of the AR-150?

While the issue exists:

  • In '/ports/' it may be helpful to see 'DHCP Address Reservations' to confirm that your 'pi-star' server is still 'active'.
  • A 'support data download' may be helpful.


Asides:
Why do you have '(wan)' enabled on your AR-150?
More uinque (and more scalable) hostnames are recommended.

73, Chuck
 

n5hzr
n5hzr's picture
Chuck, thanks for the reply.
Chuck, thanks for the reply. Yes, you are correct that the 172.31.64.170 IP address is in the client tunnel subnet. I have updated the posting to correct that info.

The PING test computers (the ones that fail) are in the LAN of an AR300 router that is connected to this AR150 router by a tunnel (300 is the client, 150 is the server).

The computers (the ones that don't fail) are still able to connect to the web servers are either in the LAN of the AR150 OR the LAN of a DtD-connected radio.

_if_ it happens again, I'll look at 'ports/ and grab a data download during the failure.

WAN is enabled to provide Internet access for the FLIGHT (flight-aware receiver) and PI-STAR (pi-star server).

Any suggestions on naming conventions would be appreciated.

Thanks - Mark

 
nc8q
nc8q's picture
WAN is enabled to provide Internet access for the FLIGHT (flight
"WAN is enabled to provide Internet access for the FLIGHT (flight-aware receiver) and PI-STAR (pi-star server)."
With default settings, if the AREDN router has internet access, then all its LAN connected services have internet access.
See:
/cgi-bin/advancedconfig
'WAN Settings'
73, Chuck

 
 
nc8q
nc8q's picture
Any suggestions on naming conventions would be appreciated.
https://arednmesh.readthedocs.io/en/latest/arednGettingStarted/advanced_...
"...

Attention

The hostnames of computers connected to the mesh at large must be unique.
Typically you should prefix your amateur radio callsign to the computer’s hostname in order to have the best chance of it being unique on the mesh network
."
 

Like AA5KD.

73, Chuck

 

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer