MME (Mesh Made Easy) is a MikroTik routing protocol suited for IP level routing in wireless mesh networks. It is based on ideas from B.A.T.M.A.N. (Better Approach To Mobile Ad-hoc Networking) routing protocol.
This is MME configuration reference only; for description of the protocol and configuration examples see Manual:MME wireless routing protocol.
|origination-interval (time; Default: 5s)||Interval between originator messages. Obviously, this value should be less than timeout value.|
|timeout (time; Default: 1m)||Node timeout. If no messages at all are received from an originator node during this interval, that node is purged from protocol tables, and so are all routes it has announced.|
|bidirectional-timeout (integer; Default: 2)||How many originator messages from a node can be lost in sequence, while still considering it a bidirectional neighbor. We are assuming that every node originates messages with the same rate as this router (i.e. the value from origination-interval).|
|ttl (integer; Default: 50)||How many times to forward originator messages.|
|gateway-class (none | 56-KBit | 64-KBit | 128-KBit | 256-KBit | 512-KBit | 1-MBit | 2-MBit | 3-MBit | 5-MBit | 6-MBit | >6-MBit | integer; Default: none)||Announce internet gateway capability in the originator messages sent by this node.|
|gateway-selection (no-gateway | best-adjusted | best-statistic; Default: no-gateway)||This node is a MME gateway protocol client.
|gateway-keepalive (time; Default: 1m)||The time interval between successive gateway keepalive messages.
For gateway client, this specifies how often to send out keepalive messages.For gateway server, as client hold time is used 3 * gateway-keepalive seconds. If the server does not receive keepalive messages from a client during this time interval, the client is considered dead. All state information associated with it are deleted, including the dynamic IPIP tunnel.
|preferred-gateway (IP; Default: 0.0.0.0)||Always prefer this node as internet gateway to any others, if it is present in originator tables.|
The symbolic values of gateway-class are compatible with B.A.T.M.A.N. This table describes the mapping from integers to symbolic values:
- 0 no gateway
- 1 modem
- 2 ISDN
- 3 Double ISDN
- 4 256 KBit
- 5 UMTS/ 0.5 MBit
- 6 1 MBit
- 7 2 MBit
- 8 3 MBit
- 9 5 MBit
- 10 6 MBit
- 11 >6 MBit
Entering integer value > 11 means even better gateway class.
/routing mme interface
List of interfaces on which to run the MME protocol.
|interface (string; Default: all)||Interface on which MME will run
|passive (yes | no ; Default: no)||If true, do not send originator messages via this interface, only receive.|
|primary (yes | no ; Default: no)||Include routing information (i.e. network announcements) in self-originated packets send via this interface. (For forwared packets the information is always included.) Only one interface can be primary. If no interfaces are configured as primary, one is selected automatically in a random fashion.|
/routing mme interface print status allows to view status of interfaces.
|messages-tx (integer)||Originator messages transmitted via this interface. For all interface: cumulative statistics|
|messages-rx (integer)||Originator messages received via this interface. For all interface: cumulative statistics.|
/routing mme network
MME Networks is a list of networks to be advertised.
|network (IP prefix; Default: )||Network to advertise|
/routing mme originators
This submenu contains information about active neighbor nodes.
|originator (IP)||IP address of the node.|
|gateway (IP)||The nexthop for this node.|
|gateway-class (none | 56-KBit | 64-KBit | 128-KBit | 256-KBit | 512-KBit | 1-MBit | 2-MBit | 3-MBit | 5-MBit | 6-MBit | >6-MBit | integer)||If none, then this node is not a gateway server. Otherwise this node is a gateway server with specified gateway bandwidth.|
|last-packet-before (time)||Seconds elapsed since last received packet.|