5 Apr
2017
5 Apr
'17
2:08 a.m.
Tony,
If you have your gateway running on the Pi, for your windows machine you
need to use the Pi as a gateway for 44.0.0.0/8.
This could be achieved in 2 ways:
a - If you use 44net addresses in your LAN add a permanent route
44.0.0.0/8 via PI
b - If you use private addresses, it gets a little more complicated:
- use the above method and do NAT on the Pi
- add a second network adapter with a 44net address and the
above route via Pi
- set up a vlan on your computer and on the Pi and use that one
for 44 access (this is quite tricky on windows)
Marius, YO2LOJ
On 2017-04-05 2:01, Tony Langdon wrote:
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.