15 Nov
2014
15 Nov
'14
9:01 a.m.
John et al;
On Sat, 2014-11-15 at 09:02 +0000, John Wiseman wrote:
I'm adding a rip44 processor and ipip tunnel
support to my BPQ32/LinBPQ
networking software.
As you know from 44.48.0.42, ampr-ripd and a standard linux tunnel works
fine for your software and has for the past year and a half or so; but
for the windows environments to be able to handle rip/ipencap this I'm
sure would be a welcomed thing for those folks.
I've set up an encap entry for 44.131.56.0/27 and
I receive the block of
RIP44 messages every 5 minutes, and random packets addressed to 44.131.56.1,
presumably from network scanners. If I ping 44.131.56.1 from a normal
internet host I also see the encapsulated packets. So far so good. But if I
try pinging any other address in my subnet, I don't get anything. I'd expect
amprgw to send me packets for any address in my subnet.
As Brian mentioned, commercial<>amprnet requires dns entries for the IPs
you want publicly routable, however if you only want to stay within the
amprnet, the portal entry should be enough as 44<>44 routing is
point-to-point. This excludes those announced via BGP. This may be a
useful scenario for test environments on a larger scale, and sites that
are RF only.
--
If Microsoft intended Windows to be for ham usage,
they would have incorporated our protocols into their kernel.
73 de Brian Rogers - N1URO
email: <n1uro(a)n1uro.ampr.org>
Web: http://www.n1uro.net/
Ampr1: http://n1uro.ampr.org/
Ampr2: http://nos.n1uro.ampr.org
Linux Amateur Radio Services
axMail-Fax & URONode
AmprNet coordinator for:
Connecticut, Delaware, Maine,
Maryland, Massachusetts,
New Hampshire, Pennsylvania,
Rhode Island, and Vermont.