mirror of https://github.com/aredn/aredn.git
2c1bd9ce0e
Aliases in NAT mode allows the node admin to create alias names for hosts on the LAN and then use those for creating port forwarding rules. The aliases DO NOT effect the rest of the mesh network and are not propagated via OLSR. NAT Mode aliases are only usable on the local LAN where the IP addresses are known and routable only on the subnet. Since the NAT hides these IP addresses or the node masquerades, other mesh nodes and devices by definition only know about the node’s hostname. Thus aliases on the LAN in NAT mode are not propagated by OLSR across the mesh. You _CANNOT_ use an alias name in a service listing. You _will_ be able to set an alternate hostname for any host on the nodes' LAN however. A host named `CBY45-DELLLAPTOP` can also be known as `wxc-shack-laptop`. It may make remembering which host is which a bit easier. Since OLSR does not propagate the alias, the "Do Not Propagate" checkbox while in NAT Mode is hidden. |
||
|---|---|---|
| .. | ||
| admin | ||
| advancedconfig | ||
| api | ||
| apiprotected | ||
| channelmaps.pm | ||
| fwinfo | ||
| mesh | ||
| perlfunc.pm | ||
| ports | ||
| scan | ||
| setup | ||
| signal | ||
| status | ||
| supporttool | ||
| sysinfo | ||
| sysinfo.json | ||
| tunfunc.pm | ||
| ucifunc.pm | ||
| vpn | ||
| vpnc | ||