24 Jun
2015
24 Jun
'15
8:41 a.m.
That is very strange as 44.135.124.9 is not in the dns so ucsd should
block that.
It is not expected that is routed to Maiko's gateway.
Bob VE3TOK
On 15-06-23 08:59 PM, Tom Hayward wrote:
(Please trim inclusions from previous messages)
_______________________________________________
On Tue, Jun 23, 2015 at 5:51 PM, Maiko Langelaar <maiko(a)pcs.mb.ca> wrote:
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)
This kind of thing is expected. It is the Internet, after
all.
This is exactly what the UCSD group studies with 44net. These scans
are present on all of 44/8. Stuff addressed for you is forwarded to
you. Everything that's unallocated is sent to the UCSD group for
research.
Tom KD7LXL
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net