-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Your gateway replies with a private IP:
3 172.31.255.254 (172.31.255.254) 203.731 ms 233.349 ms 233.076 ms
You should initialize your tunnel interface (tunl0, ampr0, etc) with an address from 44/8.
You may reuse an IP from your internal LAN, for example if you gateway has 44.60.44.1/24 on the inside, you may assign 44.60.44.1/32 to your tunnel interface.
This will solve multiple issues:
1) your gateway will use 44.60.44.1 as source IP for any connections that will be initiated from the gateway host via the tunnel interface. So other AMPR stations will actually be able to reply to your gatway's packets.
2) Should your gateway ever have to reply with some ICMP message, the source IP will correctly identify where the ICMP message was generated.
73 de Marc, LX1DUC
On 19/08/2013 22:24, lleachii@aol.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ All,
Please verify my gateway is reachable over AMPR. It appears the problem was not having an iptables rule allowing IPENCAP.
ping and traceroute ping GW- 44.60.44.1 DNS at 44.60.44.3 HTTP at 44.60.44.10, 11, 12 and 13 Public Echolink Proxy 44.60.44.253:443 and 44.60.44.254:80
-Lynwood KB3VWG
On 08/03/2013 09:28 PM, lleachii@aol.com wrote:
Marius,
To clarify:
The OUTTER packet SRC 76.114.216.250 DST <destination gateway>
the INNER packet SRC 44.60.44.x (device being sent from) DST <44.x.x.x>
-Lynwood KB3VWG
-------------- next part -------------- An HTML attachment was scrubbed... URL: http://hamradio.ucsd.edu/mailman/private/44net/attachments/20130819/43bd9d7a/attachment.html
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html