Hi Rob and all,
thanks for the prompt answer. It's working now with the help of Brian.
However I'm still sending non-44 source addresses to the amprnet router. An example:
22:27:23.139944 IP 169.228.66.251 > 91.121.90.186: IP 77.236.192.34 > 44.134.19.3: ICMP host 93.89.157.209 unreachable, length 81 (ipip-proto-4) *22:27:23.139999 IP 91.121.90.186 > 169.228.66.251: IP 77.236.192.34 > 44.134.19.3: ICMP host 93.89.157.209 unreachable, length 81 (ipip-proto-4) *
anybody knows how to filter this traffic with IPTables ? It would be very helpful.
Thanks Marco
On 21/04/2017 22:13, Rob Janssen wrote:
(Please trim inclusions from previous messages) _______________________________________________
My understanding is that it's working correctly, because the icmp reply is sent back to 2.238.198.249 inside the tunnel and towards the amprnet router (169.228.66.251).
Unfortunately there's something wrong in the middle because no packets are actually reaching 2.238.198.249
It must be something in your 2.238.198.249 system or the path to it, because I can ping 44.134.160.1 without problem from other internet hosts.
Rob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net