You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the #connections section displays that when the mesh node router is connected to the internet, that the traffic routes through the Mesh Exit Node. However, that is only true for the peoplesopen.net (and fast) wireless networks. When connected to the pplsopen-admin SSID, the traffic routes through the default from the internet source -- such as my modem provided by my home ISP. This is significant in terms of communicating whether the user (the home network administrator/operator) is connecting to the network under the IP associated with, for instance, the ISP subscriber's identity, rather than the Virtual Public Network (VPuN) of a mesh exit server.
Not sure the best way to resolve this. Could title the diagram for the public network only, or fork to make two branches after Connected over Internet Tunnel on WAN port. The latter could show that private clients route through a particular exit IP (and could display that IP), and that public clients route through the Mesh Exit Server as currently displayed (and also could display which exact public IP that is since there are multiple exits possible).
The text was updated successfully, but these errors were encountered:
Currently the #connections section displays that when the mesh node router is connected to the internet, that the traffic routes through the Mesh Exit Node. However, that is only true for the
peoplesopen.net
(andfast
) wireless networks. When connected to thepplsopen-admin
SSID, the traffic routes through the default from the internet source -- such as my modem provided by my home ISP. This is significant in terms of communicating whether the user (the home network administrator/operator) is connecting to the network under the IP associated with, for instance, the ISP subscriber's identity, rather than theVirtual Public Network (VPuN)
of a mesh exit server.Not sure the best way to resolve this. Could title the diagram for the public network only, or fork to make two branches after
Connected over Internet Tunnel on WAN port
. The latter could show that private clients route through a particular exit IP (and could display that IP), and that public clients route through the Mesh Exit Server as currently displayed (and also could display which exact public IP that is since there are multiple exits possible).The text was updated successfully, but these errors were encountered: