Beta
×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Slashdot port scanning

Martin Spamer (244245) writes | more than 5 years ago

Editorial 0

My logs today revealed the following two port scans.

Fri, 2009-09-04 15:24:10 - TCP Packet - Source:216.34.181.45 Destination:X.X.X.X - [PORT SCAN]
Fri, 2009-09-04 15:24:12 - TCP Packet - Source:216.34.181.45 Destination:X.X.X.X - [PORT SCAN]

So I left wondering why slashdot is port scanning from 216.34.181.45?

My logs today revealed the following two port scans.

Fri, 2009-09-04 15:24:10 - TCP Packet - Source:216.34.181.45 Destination:X.X.X.X - [PORT SCAN]
Fri, 2009-09-04 15:24:12 - TCP Packet - Source:216.34.181.45 Destination:X.X.X.X - [PORT SCAN]

So I left wondering why slashdot is port scanning from 216.34.181.45?

Sorry! There are no comments related to the filter you selected.

Check for New Comments
Slashdot Login

Need an Account?

Forgot your password?