17 Jun
2015
17 Jun
'15
2:32 p.m.
Hi Jann,
This is a good idea.
It will go in the next version, together with default raw sockets (I
understood that multicast doesn't work as it should on new kernels) and
tweaks to support a pid file.
Marius, YO2LOJ
-----Original Message-----
From: 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu
[mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Jann
Traschewski
Sent: Wednesday, June 17, 2015 21:20
To: 44net(a)hamradio.ucsd.edu
Subject: Re: [44net] AMPRNet Interoperability with BGP
(Please trim inclusions from previous messages)
_______________________________________________
On 17.06.2015 17:06, Marius Petrescu wrote:
For those using ampr-ripd, the latest version (1.13)
does NOT set a route
if
the gateway falls inside its own 44net subnet,
actually preventing those
situations.
The condition for it to work is, of course, NOT to have a default 44/8
route
via ampr-gw, so that unknown 44net destination are
NAT-ed to the gateway's
public IP.
it would be nice if you can add the following feature (optional) to the
ampr-ripd:
* Parse the received routing information by RIP for IPIP-Gateways hosted
on an IP-address within 44/8 (e.g. 44.24.221.1 for HamWAN).
* Load the Defaultgateway of the local system from IP-Table "Main" into
Memory (e.g. 141.75.244.1 at my DB0FHN box)
* Set a hostroute to each individual parsed IPIP-Gateway using the
Defaultgateway in a routing table chosen by the user (e.g. 44.24.221.1
via 141.75.244.1 in table "Main" at DB0FHN)
I did this manually to test the interconnection with the
HamWAN-Community. Worked like a charm :)
73,
Jann
--
Jann Traschewski, Faber-Castell-Str. 9, D-90522 Oberasbach, Germany
Tel.: +49-911-99946898, Mobile: +49-170-1045937, E-Mail: jann(a)gmx.de
Ham: DG8NGN / DB0VOX, http://www.qsl.net/dg8ngn
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net