Infinet Wireless: Technical Documentation
Page tree

Versions Compared

Old Version 4

changes.mady.by.user Tatyana Drazhnikova

Saved on

compared with

New Version 5

changes.mady.by.user Tatyana Drazhnikova

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Check configuration on all MINT neighbors

Code Block
languagetext
themeEmacs
Unknown node#2> mint rf5.0 -rcmd -node all "co sh"

Force reboot on remote MINT neighbor

Code Block
languagetext
themeEmacs
Unknown node#2> mint rf5.0 -rcmd -node 000435130AD8 "restart yes"

Set new IP address and Default Gateway on remote MINT neighbor

Code Block
languagetext
themeEmacs
Unknown node#2> mint
 rf5.0 -rcmd -node 000435130AD8 "ifc svi1 172.12.77.2/27; route add
 0.0.0.0/0 172.12.77.1;"
Note
titleNOTE

Full syntax of MINT RCMD command with different options has detailed description in WANFleX command reference guide Layer 2 commands set -PHY and MAC.

MINT area prerequisites

In default configuration MINT protocol is enabled and used only between wireless radio interfaces. However, in order to create interconnected (by MINT protocol) MINT area MINT-over-Ethernet interfaces (PRF) are required.

In order to enable MINT-over-Ethernet it is required to:

  • Create virtual Pseudo Radio Interface (PRF). PRF can be created as logical sub-interface for plain Ethernet interface (parent interface) , or as logical sub-interface for another logical interface (for example, VLAN interface can be used as parent interface for PRF);
  • Start MINT protocol for PRF interface;
  • JOIN command connects internal bonds between MINT areas behind Radio interfaces and PRF interfaces.

Within the same Ethernet broadcast domain (LAN) two (or more) IW units with PRF interfaces created, with MINT protocol started can find and establish communication via MINT protocol by sending and receiving Ethernet broadcasts initially. Thereafter, IW units will use Ethernet unicast data transfer.

VLAN considerations

In case two IW are placed within certain VLAN, then configuration of PRF should be corrected with certain VLAN tag. Please pay attention that default configuration (or template part) should exactly use the relevant VLAN tag number.

MINT-over-Ethernet & VLANs

MINT-over-Ethernet does generate broadcast traffic to detect and find other MINT neighbors. Sometimes, such broadcast traffic could be treated as abnormal for network, especially for enterprise networking with comprehensive network security policy.

Note
titleNOTE

It is recommended to segment MINT-over-Ethernet connections into dedicated VLAN zones, thus keeping all broadcast traffic within unique VLAN

Moreover, in vast MINT-over-Ethernet network different MINT-over-Ethernet areas should be isolated from each other in order to provide complex traffic engineering or prevent undesired traffic path selection.  Hence, VLAN separation should be used in such cases.

Configuration part

Steps to configure MINT-over-Ethernet

Only step 1 is different for untagged approach (1a) and for vlan based approach (1b)

CLI based configuration

1a. Create Pseudo Radio (PRF) interface for untagged interconnection