Marius et al.
Presently my server employs ampr-ripd-2.3 Did not observed any issues so far. encap.txt file at the very beginning contains two entries:
# # encap.txt file - saved by ampr-ripd (UTC) Mon Jun 5 03:20:34 2017 # route addprivate 44.0.0.1/32 encap 169.228.34.84 route addprivate 44.0.0.2/32 encap 169.228.66.251
RIP broadcast are coming through as before.
Best regards. Tom - SP2L
I had to filter those two out on Mikrotik. Otherwise they wound up in the routing table and RIP got broken in the tik.
Ruben - ON3RVH
On 5 Jun 2017, at 08:57, Tomasz Stankiewicz sp2l@wp.pl wrote:
Marius et al.
Presently my server employs ampr-ripd-2.3 Did not observed any issues so far. encap.txt file at the very beginning contains two entries:
# # encap.txt file - saved by ampr-ripd (UTC) Mon Jun 5 03:20:34 2017 # route addprivate 44.0.0.1/32 encap 169.228.34.84 route addprivate 44.0.0.2/32 encap 169.228.66.251
RIP broadcast are coming through as before.
Best regards. Tom - SP2L
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net