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
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@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@hamradio.ucsd.edu http://hamradio.ucsd.edu/**mailman/listinfo/44nethttp://hamradio.ucsd.edu/mailman/listinfo/44net
This one:
ip route add to 44.22.0.136/29 via 64.27.62.53 failed
shouldn't be failing. 136 is an evenly divisible base address by the 8 IP addresses between 136 - 143. I do not understand why that one should be failing on Linux.
-- 73, de Barry, K2MF >> k2mf.bgs@gmail.com
On Sat, May 19, 2012 at 4:20 PM, Don Fanning don@00100100.net wrote:
(Please trim inclusions from previous messages) _______________________________________________ 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@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@hamradio.ucsd.edu http://hamradio.ucsd.edu/**mailman/listinfo/44nethttp://hamradio.ucsd.edu/mailman/listinfo/44net
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
other than the endpoint for that subnet has changed... no idea.
On Sat, May 19, 2012 at 1:34 PM, Barry k2mf.bgs@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________
This one:
ip route add to 44.22.0.136/29 via 64.27.62.53 failed
shouldn't be failing. 136 is an evenly divisible base address by the 8 IP addresses between 136 - 143. I do not understand why that one should be failing on Linux.
-- 73, de Barry, K2MF >> k2mf.bgs@gmail.com
On Sat, May 19, 2012 at 4:20 PM, Don Fanning don@00100100.net wrote:
(Please trim inclusions from previous messages) _______________________________________________ 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@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@hamradio.ucsd.edu http://hamradio.ucsd.edu/**mailman/listinfo/44nethttp://hamradio.ucsd.edu/mailman/listinfo/44net
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Have him try to submit new as I did. That just might work.
I could not get the gateway to accept anything either so submitted new and voila she worked.
73, Don - ve3zda
_____
From: 44net-bounces+ve3zda=gmail.com@hamradio.ucsd.edu [mailto:44net-bounces+ve3zda=gmail.com@hamradio.ucsd.edu] On Behalf Of Barry Sent: Saturday, May 19, 2012 4:35 PM To: AMPRNet working group Subject: Re: [44net] bogus encap.txt entries
This one:
ip route add to 44.22.0.136/29 via 64.27.62.53 failed
shouldn't be failing. 136 is an evenly divisible base address by the 8 IP addresses between 136 - 143. I do not understand why that one should be failing on Linux.
-- 73, de Barry, K2MF >> k2mf.bgs@gmail.com
On Sat, May 19, 2012 at 4:20 PM, Don Fanning don@00100100.net wrote:
(Please trim inclusions from previous messages) _______________________________________________
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@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 tel:44.136.155%2F22 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
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Użytkownik Don napisał:
ip route add to 44.22.0.136/29 http://44.22.0.136/29 via 64.27.62.53 failed
shouldn't be failing. 136 is an evenly divisible base address by the 8 IP addresses between 136 - 143. I do not understand why that one should be failing on Linux.
-- 73, de Barry, K2MF >> k2mf.bgs@gmail.com mailto:k2mf.bgs@gmail.com
It should be correctly "xx.xx.xx.137/29" that is 137-144 ist correct or xx.xx.xx.129/29 that is 129-136 For /29 this will be: 0-8, 9-16, 17-24, 25-32 etc..
Użytkownik Janusz Przybylski SP1LOP napisał:
It should be correctly "xx.xx.xx.137/29" that is 137-144 ist correct or xx.xx.xx.129/29 that is 129-136 For /29 this will be: 0-8, 9-16, 17-24, 25-32 etc..
I apologize mistake: xx.xx.xx.136/29 this 137-143, or xx.xx.128/29 this 128-135 it should be : 0-7, 8-15, 16-23, 24-31, etc....
On 5/19/2012 2:25 PM, Janusz Przybylski SP1LOP wrote:
(Please trim inclusions from previous messages) _______________________________________________ Użytkownik Janusz Przybylski SP1LOP napisał:
It should be correctly "xx.xx.xx.137/29" that is 137-144 ist correct or xx.xx.xx.129/29 that is 129-136 For /29 this will be: 0-8, 9-16, 17-24, 25-32 etc..
I apologize mistake: xx.xx.xx.136/29 this 137-143, or xx.xx.128/29 this 128-135 it should be : 0-7, 8-15, 16-23, 24-31, etc....
Here is a great website that helps ip sub mask http://jodies.de/ipcalc
None of this matters as these addresses are subnetted at a higher level. ( 44.22.0.0/16)
It was up to the local coordinator to work with groups to better organize the subnets within their realm.
To be honest, since I don't live in Alaska anymore, I'd rather be allocated a /24 in the 44.192.0.0/16 subnet.
On Sat, May 19, 2012 at 2:25 PM, Janusz Przybylski SP1LOP < 44net@mail.sp1lop.ampr.org> wrote:
I apologize mistake:
xx.xx.xx.136/29 this 137-143, or xx.xx.128/29 this 128-135 it should be : 0-7, 8-15, 16-23, 24-31, etc....
That's my IP. I'm not having any issues as far as I can tell. The only issue I see is that he's pointing to my old static host. I'm getting BGP updates just fine.
On Sat, May 19, 2012 at 1:43 PM, Don ve3zda@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________
*Have him try to submit new as I did. That just might work.*
*I could not get the gateway to accept anything either so submitted new and voila she worked.*
*73, Don – ve3zda*
Barry wrote:
(Please trim inclusions from previous messages) _______________________________________________
This one:
ip route add to 44.22.0.136/29 http://44.22.0.136/29 via 64.27.62.53 failed
shouldn't be failing. 136 is an evenly divisible base address by the 8 IP addresses between 136 - 143. I do not understand why that one should be failing on Linux.
You are right, this one failed because it is in encap.txt twice, with conflicting next hop addresses.
Rob
That would do it. However, I'd rather Jim N7VR manually edit the file as I don't want to wipe out both entries.
N7VR: Feel free to axe the 64.27.62.53 address.
On Sat, May 19, 2012 at 1:44 PM, Rob Janssen pe1chl@amsat.org wrote:
You are right, this one failed because it is in encap.txt twice, with conflicting next hop addresses.
Rob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
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
-
Barry -
Daniel Curry -
Don -
Don Fanning -
Janusz Przybylski SP1LOP -
Rob Janssen -
VK4FQ/VK4TTT Sam