mOS Frequently Asked Questions¶
1. How can I quit a mOS application?
- Use ^C to gracefully shutdown the application. Two consecutive ^C (separated by 1 sec) will force quit.
2. My application keeps printing “No route to 0.0.0.0”, What do I do?
- Try to turn off your network-manager for mOS-enabled interfaces. The network manager can override the IP configuration set by the mOS installation scripts.
3. How can I deploy a mOS monitor in a testbed?
- For now, a mOS monitor can only be deployed in LAN settings. Users are expected to insert static IP route and ARP entries. In future revisions, we plan to develop a deployment framework in which the mOS monitor can work as an inline Ethernet bridge with MAC learning support. For now we suggest you to refer to the Configuration Parameter Tuning subsection for details on how to fine-tune the configuration of the mOS monitor.
4. How do I know whether my NIC can run a mOS application?
The DPDK driver is our first choice for packet I/O module. Please refer to Intel Data Plane Development Kit (DPDK) Supported NICs webpage to check whether your NIC can work with mOS framework. Users can work with a wider range of NICs if they use the PCAP plugin. We have personally tested the following devices in our testbed:
- Intel-82598 ixgbe (Max-queue_limit: 16)
- Intel-82599 ixgbe (Max-queue_limit: 16)
- Intel-X520 ixgbe (Max-queue_limit: 16)
- Intel-I350 igb (Max-queue_limit: 08)
5. Which OS should I use to run mOS applications?
- mOS has been tested on Ubuntu 14.04 LTS distribution with linux-3.13 and linux-4.2.0. mOS can, in fact, be ported to all linux kernels that DPDK supports. Please refer to this link to view all the requirements to run DPDK applications. DPDK can potentially work in MacOS and FreeBSD OSes as well. However, we have not extended support to these OSes yet.