3 Apr
2017
3 Apr
'17
4:57 p.m.
Today I released an update to ampr-ripd (1.16) and
amprd (1.5) to
support ipip encapsulation on subnets which have their endpoints BGP
announced in the 44net space.
Is it described somewhere how that works?
Rob
3 Apr
3 Apr
6:06 p.m.
New subject: New ampr-ripd 1.16 and amprd 1.5 released
No, but it is quite simple.
If the daemon encounters a 44 gateway in the RIP data, it creates a host
route to that specific host via the default gateway of the system.
This default route is detected by finding the gateway for IP 8.8.8.8.
If it is not suitable, this gateway can be forced by using the -g
parameter on the ampr-ripd command line to specify another gateway IP .
The amprd has no option to set that route manually.
Marius, YO2LOJ
On 2017-04-03 23:57, Rob Janssen wrote:
Is it described somewhere how that works?
Rob
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
2602
days inactive
2602
days old
1 comments
2 participants
participants (2)
-
Marius Petrescu -
Rob Janssen