{% for (let i = 0; i < length(ports); i++) { const p = ports[i]; print(` | ${p.display} | `);
}
%}
dtd vlan: 2 |
{%
for (let i = 0; i < length(ports); i++) {
const p = ports[i];
print(``); } %} |
lan vlan: untagged |
{%
for (let i = 0; i < length(ports); i++) {
const p = ports[i];
print(``); } %} |
wan vlan: |
{%
for (let i = 0; i < length(ports); i++) {
const p = ports[i];
print(``); } %} |
AREDN nodes have three primary networks; DTD, LAN and WAN (shown above in the left column). You can modify the default assignment of these networks to ports (shown across the top) using the checkboxes at the intersection of a network and a port. You can also choose the VLAN to assign to the WAN network. Networks can be assigned to multiple ports, or no ports. Note that on some devices, ports may have names like WAN or LAN. These are just arbitrary names given by the manufacturer and you are not forced to assign networks of the same name to these ports.
Active network ports, where a cable is present and attached to another device, are shown in green.")}}
XLinks provide a way of routing AREDN traffic across external non-AREDN networks. Each is created with a specific VLAN, IP address for both ends, a weight of how likely to link is to be used, and an optional network size and port (on multi-port devices). Think of xlinks as extra dtds between devices. How xlink traffic is routed once it leaves the node is dependent on the non-AREDN network, which allows for the greatest flexibility.")}}