My Fail... Was asked and didnt bother to check it...
----- Original Message ----- From: "Rob Janssen" pe1chl@amsat.org To: "AMPRNet working group" 44net@hamradio.ucsd.edu Sent: Saturday, May 19, 2012 10:51 PM Subject: [44net] bogus encap.txt entries
(Please trim inclusions from previous messages) _______________________________________________ There again are bogus entries in the encap.txt:
ip route add to 44.131.211.1/24 via 91.84.215.75 failed ip route add to 44.136.155/22 via 203.26.188.134 failed ip route add to 44.22.0.136/29 via 64.27.62.53 failed
All of them specify incorrect subnets. Please make sure that all bits outside the subnet you are masking are zero!
So, the first entry should be 44.131.211.0/24 instead of 44.131.211.1/24
Note that while JNOS may accept such entries, they are not correct and the Linux kernel will reject them.
It also appears that the first two entries do not have any hosts in the ampr.org DNS within that address range. Note that only traffic for addresses that have a DNS entry is forwarded.
Rob _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net