⏺ Found the issue! E2SAR 0.2.2 has a bug in IPv6 mode. Even when the destination is the remote IPv6 address 2001:400:a300::10 (which Netlink correctly identifies as using
interface dtn1.916), E2SAR reports "Using interface lo".
Summary of Findings:
| Test | Destination | Expected Interface | E2SAR Reports | Status |
|---------------------|-------------------|--------------------|---------------|--------|
| IPv4 mode | 192.188.29.10 | dtn1.912 | ✅ dtn1.912 | Works |
| IPv6 mode | 2001:400:a300::10 | dtn1.916 | ❌ lo | Bug |
| Direct Netlink test | 2001:400:a300::10 | dtn1.916 | ✅ dtn1.916 | Works |
The Bug:
When dpV6=true in the INI file, E2SAR's interface detection incorrectly reports "lo" even though:
1. The destination (2001:400:a300::10) is remote
2. Netlink correctly returns dtn1.916 for that destination
3. Connected sockets correctly bind to 2001:400:7001:1190::3 (on dtn1.916)
The packets likely still go out the correct interface (dtn1.916) because the connected socket binds correctly, but the reported interface name and MTU are wrong, which
could cause issues if E2SAR or your application relies on this information.
Recommendation: Report this as a bug to the E2SAR team. For now, use IPv4 mode which works correctly.
