Table 44, where all the tunnle routes reside, has to be used for ALL
outgoing 44net destinations, so that the proper tunnel gets selected.
So all packets 'to 44.0.0.0/8' have to go into table 44.
My net is 44.182.21.0/24
If I would use 'to 44.182.21.0/24', only packets having my subnet for
destination would reach the tabel.
Meaning that outgoing packets e.g. 'to 44.185.1.1' would be processed in the
main table via the default route, instead of going to table 44 where they
would be send to LZ4NY via the needed tunnel.
Again, using 'from 44.182.21.0/24' would direct all packets generated by my
subnet to table 44. This would include internet traffic to non-ampr hosts
(e.g. 44.182.21.1 to
www.google.com), which is not correct, and would skip
incoming packets from other 44 subnets, which would be processed by 'main'
instead (e.g. 44.185.1.1 to 44.182.21.1).
Marius
-----Original Message-----
From: 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu
[mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Cory
(NQ1E)
Sent: Thursday, June 18, 2015 02:18
To: AMPRNet working group
Subject: Re: [44net] (no subject)
(Please trim inclusions from previous messages)
_______________________________________________
On Wed, Jun 17, 2015 at 3:45 PM, Marius Petrescu <marius(a)yo2loj.ro> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
The issue in your setup is
'ip route add default dev tunl0 via 169.228.66.251 onlink table 44'
which should go away if ypu want to reach BGP announced networks.
Why not instead just invoke table 44 when the packet is to or from your
assigned
subnet instead of applying it to the entirety of 44/8? What
exactly does the "to 44.0.0.0/8" rule do that can't be accomplished by
limiting it to "to/from [your subnet]"?