25 May
2017
25 May
'17
8:10 p.m.
Using such an approach is not feasible.
The gateway is obtained by interrogating the kernel routing table via a
netlink socket about the gateway for that IP and it takes milliseconds.
Traceroute needs an implementation in the code, and takes forever.
For those who wish it, they can use traceroute, parse the output, and
place it as the gateway parameter in the ampr-ripd command line.
On 26.05.2017 02:35, lleachii--- via 44Net wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Marius,
Whoa!
(FYI: by finding the
nexthop for 8.8.8.8 which is usual de default gateway)
I missed this reading the
code...I looked this morning to make sure
the Old_AMPRGW IP wasn't hard coded. I need to see more how this next
hop is found. I surmise if I were to disable all output from my WAN by
default, autodetect would fail...unless I allowed output to 8.8.8.8?
(my concern are not firewalls...or Alphabet, Inc...it's a
shied-away-from practice of hard-coding IPs...you don't have
permission from the RFC Editor to hard-code)
In your next version, might I suggest a traceroute to 169.228.34.84
instead?
- Lynwood
KB3VWG
- KB3VWG
PS: I think of you, my friend, when I allow output on WAN by default,
lol. (I don't do that.)
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net