3 Jun
2017
3 Jun
'17
1:57 p.m.
Actually when sending the notification, you can not tell it where to
send the info.
It will use your system's routing policies. So if your routing from that
system is OK, if will go via tunnel. If not, it will choose whatever
route your system uses.
This is actually a good check for a working gateway. And if this
happens, the dot is red - to see it and take action.
On 03.06.2017 14:39, lleachii--- via 44Net wrote:
Marius,
Exactly how do I tell this one system application to use 44.60.44.1,
br-amprlan, tunl0, and table 44 - instead of the defaults (Public IP,
WAN and table main)?
In Linux, this isn't routing issue. Unless you've placed it in code,
ampr-ripd would use my Public IP because my Kernel does, otherwise I
wouldn't have an Internet connection. I actually noticed 1-2 other
systems that appeared with the Public IP, I was trying to screen shot
them so I could contact them, but it moved very fast.
I see no way to tell ampr-ripd to use 44.60.44.1 as its source address
for these sent packets. I even assigned an IP to tunl0, still nothing.
As always, my script is reflected in Startampr. If there's another way
to configure the policies to make this work, (without causing my other
systems applications to use 44.60.44.1), it's open source, just let me
know...
- Lynwood
KB3VWG
This could be an indicator that something
isn't 100% right, e.g. some
policy routing on your system.
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net