YES I agree!! These encap public source addreses are all probing for standard open ports - Which get dropped by my firewalls 73 Paul G4APL
On 20 April 2017 at 04:33 Brian Kantor Brian@UCSD.Edu wrote:
(Please trim inclusions from previous messages) _______________________________________________ I've been analyzing some of the encap traffic and finding unexpected things.
Several sources of ipencap'd packets being received by amprgw have non-44 inner source addresses.
Would you all agree that a protocol-4 (ipencap) packet reaching the UCSD gateway should always have an inner (encap'd) source address on the 44-net? And that those that don't should be considered bogus and be discarded?
- Brian
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
This email has been scanned by Netintelligence http://www.netintelligence.com/email