4 Sep
2016
4 Sep
'16
12:07 p.m.
1. There is no path from the Internet to your 44 address unless you have
registered it with the AMPRNet DNS server. You can add appropriate DNS
entries by requesting them from your address coordinator or from me.
2. You must configure a tunnel interface and route for each tunneled
subnet. There are more than 400 of these. The gateway router does NOT
handle traffic between tunneled subnets; it cannot be used as a default
route to network 44 as a whole. This need for so many tunnel interfaces
is why Cisco and other conventional routers are a poor choice for an
AMPRNet tunnel endpoint. Most people use Linux because it does not need
separate interfaces to implement the many tunnels, rather just one and
a simple routing table.
- Brian
On Sun, Sep 04, 2016 at 04:47:09PM +0100, Paul Middlehurst wrote:
(Please trim inclusions from previous messages)
_______________________________________________
I have configured a Cisco router, duel Ethernet interfaces on on of my static Internet
addresses. The IPIP tunnel comes up and with wireshark I can see traffic in both
directions to 169.228.66.251 pinging devices in the wider 44. network I never see anything
being returned. Does the gateway router automatically have the reciprocal return tunnel /
routes added (as per the Encap file) or is this something that needs requesting?
Is there a good 44.131.x.x address to test against?
73 Paul - G1DVA
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net