...
Note that the distribution system you use for your network need not be a Wireless Distribution System (WDS). HWMP+ mesh routing supports not only WDS interfaces but also Ethernet interfaces inside the mesh. So you can use a simple Ethernet-based distribution system, or you can combine both WDS and Ethernet links!
| Note |
|---|
Prerequisites for this article: you understand what WDS is and why to use it!HWMPplus is not supported on Wifi interfaces, but can be used on Wireless interfaces. |
Properties
Mesh
| Property | Description |
|---|---|
| admin-mac (MAC address; Default: 00:00:00:00:00:00) | Administratively assigned MAC address, used when the auto-mac setting is disabled |
| arp (disabled | enabled | proxy-arp | reply-only; Default: enabled) | Address Resolution Protocol setting |
| auto-mac (boolean; Default: no) | If disabled, then the value from admin-mac will be used as the MAC address of the mesh interface; else address of some port will be used if ports are present |
| hwmp-default-hoplimit (integer: 1..255; Default: ) | Maximum hop count for generated routing protocol packets; after an HWMP+ packet is forwarded "hoplimit" times, it is dropped |
| hwmp-prep-lifetime (time; Default: 5m) | Lifetime for routes created from received PREP or PREQ messages |
| hwmp-preq-destination-only (boolean; Default: yes) | Whether the only destination can respond to HWMP+ PREQ message |
| hwmp-preq-reply-and-forward (boolean; Default: yes) | Whether intermediate nodes should forward HWMP+ PREQ message after responding to it. Useful only when hwmp-preq-destination-only is disabled |
| hwmp-preq-retries (integer; Default: 2) | How many times to retry a route discovery to a specific MAC address before the address is considered unreachable |
| hwmp-preq-waiting-time (time; Default: 4s) | How long to wait for a response to the first PREQ message. Note that for subsequent PREQs the waiting time is increased exponentially |
| hwmp-rann-interval (time; Default: 10s) | How often to send out HWMP+ RANN messages |
| hwmp-rann-lifetime (time; Default: 1s) | Lifetime for routes created from received RANN messages |
| hwmp-rann-propagation-delay (number; Default: 0.5) | How long to wait before propagating a RANN message. Value in seconds |
| mesh-portal (boolean; Default: no) | Whether this interface is a portal in the mesh network |
| mtu (number; Default: 1500) | Maximum transmission unit size |
| name (string; Default: ) | Interface name |
| reoptimize-paths (boolean; Default: no) | Whether to send out periodic PREQ messages asking for known MAC addresses. Turning on this setting is useful if the network topology is changing often. Note that if no reply is received to a re-optimization PREQ, the existing path is kept anyway (until it timeouts itself) |
...
| Code Block | ||
|---|---|---|
| ||
/interface mesh add disabled=no /interface mesh port add interface=wlan1 mesh=mesh1 /interface mesh port add interface=wlan2 mesh=mesh1 # interface used for AP interconnections /interface wireless set wlan1 disabled=no ssid=mesh frequency=2437 band=2.4ghz-b/g/n mode=ap-bridge \ wds-mode=static-mesh wds-default-bridge=mesh1 # interface used for client connections /interface wireless set wlan2 disabled=no ssid=mesh-clients frequency=5180 band=5ghz-a/n/ac mode=ap-bridge # a static WDS interface for each AP you want to connect to /interface wireless wds add disabled=no master-interface=wlan1 name=<descriptive name of remote end> \ wds-address=<MAC address of remote end> |
...
Here WDS interface is added manually because static WDS mode is used. If you are using wds-mode=dynamic-mesh, all WDS interfaces will be created automatically. The frequency and band parameters are specified here only to produce valid example configuration; mesh protocol operations are by no means limited to or optimized for, these particular values.
...