FAQ

Why "No Routing"

1. Disable rp_filter ! (In Debian 13 Trixie, the /etc/sysctl.conf will not be default loaded. See /etc/sysctl.d/)
2. Disable rp_filter ! (If you are using Alpine or some LXCs, make sure sysctl rules will be applied when system starts)
3. Disable rp_filter ! (Even if you are sure that you turned off rp_filter, you may probably want to check newly created interfaces, via sysctl -a | grep <interface> | grep rp_filter)
4. Make sure forwarding is turned on.
5. Some hardware vendors, like Fortigate, may reject our probe packets for security reasons(our probe packets are tagged with INVALID or UNKNOWN state). In such case, you will have to manually add "allow" rules.

Why "Degraded"

• Who knows? You know. Don't ask me.
• You session will be flagged with Degraded each time packet loss reaches 10%, in one hour window
• See automatic system log at telegram channel: https://t.me/iedon_net

Referrence

• https://wiki.dn42/howto/networksettings/
• https://dn42.jp/howto/networksettings/

Why my peering session is marked as "Torndown" or "Problem Detected"

Your session will be torndown or marked as "Problem Detected" if:

• For node has code 118, 121, 178, your endpoint is not located where these nodes are located
• Your IP for DN42 interface configuration is a public IP, overlaps with iEdon-Net's IP ranges, or is obviously incorrect
• You are initiating peering session from CN to non-CN nodes
• The domain name of your interface cannot be resolved