19 May
2012
19 May
'12
4:20 p.m.
The allocation I got doesn't provide for Network boundaries. In fact,
looking at many of the entries in amprhosts, I see that aren't properly
subnetted with a network and a broadcast.
-Don @ 44.22.0.136
On Sat, May 19, 2012 at 5:51 AM, Rob Janssen <pe1chl(a)amsat.org> wrote:
(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(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/**mailman/listinfo/44net<http://hamradio.ucsd.e…