Linux - Security This forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
01-04-2007, 12:11 AM
|
#1
|
Member
Registered: Nov 2006
Distribution: Lots of Debian
Posts: 165
Rep:
|
Strange Apache log
I just had this show up in my apache log. What the heck does it mean? Not an ip address I know of..
82.96.96.3 - - [03/Jan/2007:08:19:48 -0600] "POST http://82.96.96.3:802/ HTTP/1.0" 200 2718 "-" "-"
82.96.96.3 - - [03/Jan/2007:08:19:48 -0600] "CONNECT 82.96.96.3:802 HTTP/1.0" 405 322 "-" "-"
82.96.96.3 - - [03/Jan/2007:22:08:40 -0600] "CONNECT 82.96.96.3:802 HTTP/1.0" 405 322 "-" "-"
82.96.96.3 - - [03/Jan/2007:22:08:41 -0600] "POST http://82.96.96.3:802/ HTTP/1.0" 200 2718 "-" "-"
It really sticks out from all the usual "GET" connections...
|
|
|
01-04-2007, 05:05 AM
|
#2
|
Senior Member
Registered: Dec 2005
Location: Brisbane, Australia
Distribution: Slackware64 14.0
Posts: 4,141
Rep:
|
It looks like some from 82.96.96.3 (a German IP address, according to ripe) was checking whether they could use your server to connect back to their own server on port 802 - the 200 code says that the POST did work. The 405 response for the CONNECT means that your server didn't allow that method to be used.
Last edited by gilead; 01-04-2007 at 02:19 PM.
Reason: Fixed typo
|
|
|
01-04-2007, 09:59 AM
|
#3
|
Member
Registered: Nov 2006
Distribution: Lots of Debian
Posts: 165
Original Poster
Rep:
|
Quote:
Originally Posted by gilead
It looks like some from 82.96.96.3 (a German IP address, according to ripe) was checking whether they could use your server to connect back to their own server on port 802 - the 200 code says that the POST did work. The 405 response for the CONNECT means that you server didn't allow that method to be used.
|
hmm interesting. Thanks
|
|
|
01-04-2007, 12:25 PM
|
#4
|
Member
Registered: Nov 2006
Distribution: Lots of Debian
Posts: 165
Original Poster
Rep:
|
Ok I did some reading on that ip address and it looks like it is normal if you use irc
|
|
|
01-04-2007, 09:09 PM
|
#5
|
Senior Member
Registered: Mar 2003
Distribution: Fedora
Posts: 3,658
Rep:
|
Interesting, I hadn't seen that before. Just to clarify for those lurking in this thread or who come across it via a google search, if you do a whois of the scanning ip (82.96.96.3), you'll see this message:
If you follow that link, you'll see:
Quote:
Open Proxies, IIS and Appeals
Like many interactive networks, we've had our share of problems with denial-of-service attacks. As a result, we've had to develop a variety of measures to reduce the impact of such attacks. freenode may block access to users whose IRC clients run on hosts with open proxies, IIS servers or other categories of software determined to present special risk to our server environment. We reserve the right to use automation to attempt to detect such software on your host, as you connect to our servers, while you remain connected to the network and on occasion during post-connection analysis. Your use of the network signifies your acceptance.
|
It's still be a good idea to correlate the time the scan was received with your IRC activity, just to be on the safe side. Thanks for posting this.
|
|
|
01-07-2007, 01:52 AM
|
#6
|
Member
Registered: Jan 2006
Location: Finland
Distribution: Mainly Gentoo
Posts: 119
Rep:
|
Thank you Capt_Caveman for your eagle eyes. As a daily user of the Freenode network, the 82.96.96.3 indeed have popped up in my webserver logs. However, I have long time ago blocked the whole Probe Networks subnet with no effect in the irc usage of that network.
I also doubt how effective such a measure can be in DoS prevention.
|
|
|
01-07-2007, 10:29 AM
|
#7
|
Senior Member
Registered: Mar 2003
Distribution: Fedora
Posts: 3,658
Rep:
|
You can thank esaym, I was just expanding on what he posted to make it a bit more clear what was going on.
|
|
|
All times are GMT -5. The time now is 10:33 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|