24 Jun
2015
24 Jun
'15
7:51 a.m.
I'm seeing tons of ip-ip packets directed to my
44.135.124.0/24 subnet, which unfortunately is my
RF port, so I've been forced to 'drop' that route
so that not to overwhelm our local frequency.
From CN ??? Like someone is scanning the 44 nets ???
Tue Jun 23 19:42:49 2015 - vhf sent:
KISS: Port 0 Data
AX25: VE4KLM-1->QST UI pid=ARP
ARP: len 30 hwtype AX.25 prot IP op REQUEST
sender IPaddr 44.135.124.1 hwaddr VE4KLM-1
target IPaddr 44.135.124.25 hwaddr
19:49:32.324324 IP amprgw.sysnet.ucsd.edu > node201.1.168.192.in-addr.arpa: IP
80.3.46.59.broad.sy.ln.dynamic.163data.com.cn.http > 44.135.124.9.45871:
Flags [S.], seq 2685507706, ack 4207607809, win 16384, options [mss 1460],
length 0 (ipip-proto-4)
19:49:32.324401 IP node201.1.168.192.in-addr.arpa > w143.pcs.mb.ca: IP
80.3.46.59.broad.sy.ln.dynamic.163data.com.cn.http > 44.135.124.9.45871:
Flags [S.], seq 2685507706, ack 4207607809, win 16384, options [mss 1460],
length 0 (ipip-proto-4)
And lots more of them ...
Maiko / VE4KLM