27 Apr
2017
27 Apr
'17
8:08 p.m.
...in the archive's past, I was referring to this tunnel sending packets
I had to block, or saw firewall hits (after looking at netflow I had on
tunl0 for IPENCAP). I did not want to cause alarm by identifying the
operator (and I noted, at the time I was not collecting netflow on
IPENCAP packets that arrived at my WAN, I did see some pcap). I'm not
sure if the IP is dynamic, but the callsign for the AMPR-OP is the same.
I do not recall if I communicated (due to the nature of the packets)...
Many packets were double encapsulated, and had various valid sources and
destination IPs.
73,
- KB3VWG