How can I be updated with the latest news from LISPmob?
How can I contact LISPmob team?
You can send your question regarding general usage of LISPmob to email@example.com. For development question or suggestions you can use firstname.lastname@example.org. Those lists are open and anyone can subscribe at https://lispmob.org/mailman/listinfo. When possible use those mailing lists instead of sending mails directly to us.
What is LISP Beta-Network? How can I join?
You will find all the information here: You can request joining the Beta-Network contacting us at our contact form on https://lispmob.org/contact. For Beta-Network requests we prefer to use the contact form to prevent flooding the mailing lists.
I am using the Beta-Network, how can I check if I registered correctly?
How can I enable different debug levels?
Launch lispd with the -d N option, being N the debug level you want. There are three debug levels, from 1 the less verbose to 3 the most. Level 1 or 2 should be enough for common debug. You can also use the configuration file to set the default debug level.
How can I check the incoming/outcoming packets on my system?
Use a tool like Wireshark. You can listen on the physical interface(s) you are using to see encapsulated packets or listen on the lisp TUN interface (lispTun0) to see packets before/after being encapsulated. TUN interface will only appear when LISPmob is running. Use 'lisp' and 'lisp-data' filters to look for LISP control or LISP data packets.
How can I send ad-hoc Map-Request to the Mapping-System?
Use the 'lig' tool: Note that lig can not be used while LISPmob is running.
I obtain no reply to any LISP packets. I see no reply to them in any interface.
Check that there is no firewall blocking LISP packets. LISP uses UDP port 4341 for data and 4342 for control. Both ports must be open in any firewall on the path.
I obtain no reply to my traffic, however I can see how reply traffic is reaching the external physical interface
Check that Reverse Path filtering is disabled. Add the following lines to /etc/sysctl.conf and reboot the system
My packets are not beeing forwarded
Check that IP forwarding is enabled on your system. Add the following lines to /etc/sysctl.conf and reboot the system
The debug output shows this message, "forward_native: No output interface found".
This doesn't mean that LISPmob is not working properly. It just means that it has tried to send a packet natively and it has not found a suitable interface. This can happen, for instance, if you are using IPv4 EIDs with IPv4 only interfaces and your system is generating IPv6 packets
The debug output shows this message, "The entry X.X.X.X is not found in the data base" or this one, "X.X.X.X is not a local EID"
This message appears only when an EID is not found on the local database (the one that stores the EIDs assigned to LISPmob xTR/MN). Before encapsulating a packet, LISPmob checks if the source address is a local EID (looking into the local database and hence printing this debug message). This is done to avoid encapsulating packets which are not meant to. Like packets originated in the xTR itself and not in the EID subnet, or packets addressed to a host on the same subnet on MN operation.
The debug output shows this message, "CRIT: No default output interface. Exiting ..."
Check that the interface name defined in the "database-mapping" in your config file matches the one you want to use as RLOC interface
I want to use multihoming in my OpenWRT router
Most of OpenWRT routers doesn't have more than one wan interface. To enable multihoming support in your OpenWRT router, you should create a virtual interface to be used as a second WAN. You have to assign a different VLAN to each port you want to use as WAN. Check OpenWRT documentation to see how to configure VLANs in your router. Note that not all routers have support for VLANs, and the ports used in network configuration not always match physical ports. Check the OpenWRT wiki to find documentation on your specific router.
I am testing multihoming on OpenWRT using a virtual WAN interface and I see strange behaviour when I force up/down on the virtual interface.
There is a known issue with virtual WAN interfaces on OpenWRT and LISPmob. On normal operation you should not expect any issue, but if you force up/down on the interface LISPmob will not behave as it would do with a physical interface. We are looking into how to solve this.