[MVMA] MVMA Meeting This Saturday - DARA Clubhouse - 9:30 am

[Maurice Riggins]

> On Oct 12, 2018, at 00:39, William Curtice <william.curtice at ieee.org> wrote:
> 
> Managed Switch Configurations

https://www.arednmesh.org/content/network-switch-configuration-files

Every switch port used for an AREDN node needs to be a:
Tagged member of VLAN01 (used for WAN)*
Tagged member of VLAN02 (used for DtD)*
Untagged member of its own node-specific VLAN (for LAN)
- AREDN examples use VLANS 11, 22, 33, 44, 55, and so on.
The port's PVID is the number of its node-specific VLAN.
* from the secondary port on a XW node

Every switch port used for node-hosted equipment needs to be a:
Tagged member of VLAN01
Untagged member of the node-specific VLAN where it gets its 
DHCP IP The port's PVID is the number of its node-specific VLAN.

The switch port used to connect to the home network/router/internet should be an Untagged member of VLAN01 and its PVID is 1.

All nodes can have DHCP turned on without interfering with each other.

All nodes can get a WAN/internet IP from the home router via DHCP. If you want that to be consistent, use Reserved DHCP Addresses in the home router. Avoid static IP configurations if possible. 

A node without equipment (phone, cam, etc) only needs one switch port but that should still have its own node-specific VLAN & PVID.

A node is a LAN unto itself, with 4, 8, or 16 IP addresses, and now with firmware 3.18.9.0, 32 IP addresses. The first is the network address, the second is the node address, and the last is the broadcast address. There are 1, 5, 13, or 29 DHCP addresses between the node address and broadcast address. That’s why the node (and any equipment) should have a unique VLAN.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qth.net/pipermail/mvma/attachments/20181012/d1faa136/attachment-0001.html>