4 Jun
2017
4 Jun
'17
9:25 a.m.
Marius,
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.
You stated:
Actually when sending the notification, you can not
tell it where to
send the info.
I was asking about an argument to tell a system application to use
SRC
IP, like Ping, traceroute, ip(8), etc. When I use them, I always have to
specify the SRC for them to work on an interface other than WAN.
73,
- Lynwood
KB3VWG