4 Jun
2017
4 Jun
'17
7:44 a.m.
On 04.06.2017 03:22, lleachii--- via 44Net wrote:
So, the ampr-ripd was designed to work on ampr addresses, running on
ampr machines, to be used in ham radio gateways.
And it assumes that it has access to the own tunnels it maintains. From
my point of view, any other usage is out of scope.
So the solution is not for me to code anything. The solution is for you
to create a derivative work if you need it.
It is open source, please feel free to do it.
Actually when
sending the notification, you*can not* tell it where to
send the info.
The solution is to code an argument that tells the system to use an
interface/IP as source, you told me that doesn't exist in code. True, they are two separate networks, other anomalies
occur when
mixing them (e.g. I could not sit on a non-44 IP at my house and test
connectivity to 44/8 thru Brian, these anomalies are also how PE1CHL
discovered policy-based routing was needed).
These anomalies are there since ages, at least there where there since
at least 17 years now (I started my first gateway in 2000, with that
"mirrorshades.ucsd.edu" gateway) but the internet was much more
permissive in those days.
The sad thing is that, exactly because of that, not much has changed
until the advent of RIPv2 announcements and Hessu's first daemon. Of
course providers implementing source filtering helped a little in
normalizing the networking approach.
But you actually can sit in your house on a non44 network and use it.
You just need to create proper mapping, routing and NAT rules for it to
work.