7 Jun
2017
7 Jun
'17
6:34 a.m.
By not setting an IP on your tunnel, you are sending all traffic
originating on your gateway with an outgoing IP other than your 44net
address (as seen in the output of the ip route get command).
You are creating exactly the situation Brian is fighting for some time now.
Your tunnel should have either 44.98.63.6/32 or, even better,
44.98.63.6/8, which is the 'real' netmask of that tunnel.
For clarification: 44.98.63.6/8 means that behind that interface with IP
44.98.63.6 sits the whole 44.0.0.0 - 44.255.255.255 address space, which
is the real situation.
This will create automatically a route 44.0.0.0/8 via tunl0 in the main
table. Using a /32 netmask will avoid this.
On 07.06.2017 06:22, Tom Cardinal wrote:
This could be me or maybe not.
tunl0 - Tunnel to the rest of the AMPRNET. (no IP Address assigned)
...
If I try to add a route to 44.0.0.0/8 with this command:
ip rule add to 44.0.0.0/8 table 44 priority 48
and then I do "ip route get 44.0.0.1" I get the following output:
root@blackjack:~# ip route get 44.0.0.1
44.0.0.1 via 169.228.34.84 dev tunl0 src 68.109.14.113
cache window 840