4 Apr
2017
4 Apr
'17
7:01 p.m.
On 4/04/2017 5:29 AM, Marius Petrescu wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Hi again,
Thanks to Jann, DG8NGN, we have some test setups on virtual machines
on his server.
To test the new feature you can ping/traceroute the following hosts to
check the function:
Direct BGP endpoint 44.130.121.2 running amprd, host via tunnel:
44.130.121.3
Direct BGP endpoint 44.130.122.2 running ampr-ripd, host via tunnel:
44.130.122.3
I upgraded my ampr-ripd, but the only one of these I could get to work
was 44.130.121.3. The other 3 were unreachable from 44.136.76/24. :(
This result was identical to those obtained with the previous version,
and I got a bit suspicious. I had been testing from my Windows machine,
which routes everything for 44/8 to the AMPRnet router (confirmed with
tracert -d)
I repeated the test from the Pi running ampr-ripd and all 4 addresses
are reachable from that machine. Traceroutes look good too from there.
With further thought, that is expected behaviour. Directly reachable
BGP advertised endpoints are going to break here, because of
routing/addressing issues. I'm not sure how I'm going to fix this for
machines other than the AMPR router itself.
--
73 de Tony VK3JED/VK3IRL
http://vkradio.com