4 Jun
2017
4 Jun
'17
11:35 a.m.
On 04.06.2017 05:25, lleachii--- via 44Net wrote:
Marius,
Now I really don't understand what one has to do with another.
1. You get an IP from your carrier, whatever that is.
2. You set up an IPIP tunnel on the same machine (with IP 44.60.44.2).
This info you have been omitting all the time.
3. You have some interface to connect to your local 44 network (br-amprlan).
Now you run ampr-ripd.
Now what is wrong with:
ip rule add from 44.60.44.2 table 44
ip rule add from 44.60.44.2 to 44.60.44.0/24 table (whatever table you
rute your internal 44net with)
ip rule add from 44.60.44.2 to 44.0.0.0/8 table 44
And all of this because your gateway is actual 44.60.44.2, 44.60.44.1
being just another IP on your subnet.
Now, when your gateway (including ampr-ripd) sends out data to another
44net host, it will be sent with source IP 44.60.44.2 via the tunnel.
ip rule add from 44.60.44.1 to 44.0.0.0/8 table
44
This should make your system use table 44 for outgoing 44net traffic,
including the interface address 44.60.44.1
No, it would not, my Kernel received an
IP and Gateway via DHCP from
my Carrier. My ampr-ripd is executed by that same Kernel.
For clarity, technically, 44.60.44.1 is assigned to br-amprlan. I did
assign 44.60.44.2 to tunl0 (I do this EVERY time someone suggests my
problem is because tunl0 doesn't have an de-encapsulated IP address),
but it never has affect. Keep in mind that I also have other
192.168.x.x networks...none of which should reach 44 hosts via
AMPRNet. Perhaps sending via 44.60.44.1 or 44.60.44.2 works in RAW
mode using ampr-ripd; but I use Linux Kmod-ipip as my true AMPR
tunnel, it does not work.
Now this is new and should have been here from the beginning.