Noticed that our incoming TLS connection queue was a little high – running at 60 concurrent connections for an hour or so.
A check of the queue revealed that all the connections were coming from a single IP – and were tying up the queue, making it a denial of service attack. This one ip address was connecting and reconnecting multiple times, hogging up all the connections.
I’ve blocked that ip address, and restarted the TLS service, its back at normal levels now.
For the interested –
Connections:
mail:/var/log/qmail/qmail-tls# netstat -an –numeric-ports | grep 587 | grep 58.246.24.242
tcp 0 0 61.129.49.190:587 58.246.24.242:24384 ESTABLISHED
tcp 1 0 61.129.49.190:587 58.246.24.242:39581 CLOSE_WAIT
tcp 0 0 61.129.49.190:587 58.246.24.242:11625 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:42614 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:46630 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:20802 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:51956 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:4463 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:39878 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:43678 ESTABLISHED
tcp 1 0 61.129.49.190:587 58.246.24.242:39181 CLOSE_WAIT
tcp 0 0 61.129.49.190:587 58.246.24.242:62054 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:64421 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:24326 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:58740 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:25779 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:50209 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:41358 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:32383 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:27925 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:46540 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:7049 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:13999 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:62962 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:19771 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:43604 ESTABLISHED
tcp 1 0 61.129.49.190:587 58.246.24.242:38757 CLOSE_WAIT
tcp 0 0 61.129.49.190:587 58.246.24.242:39909 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:30470 ESTABLISHED
tcp 1 0 61.129.49.190:587 58.246.24.242:39754 CLOSE_WAIT
tcp 0 0 61.129.49.190:587 58.246.24.242:61393 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:52072 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:22294 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:60398 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:60530 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:36049 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:1426 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:40190 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:15402 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:23457 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:65187 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:39910 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:23181 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:3286 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:40540 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:12957 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:39829 ESTABLISHED
tcp 0 0 61.129.49.190:587 58.246.24.242:19748 ESTABLISHED
IP Owner:
mail:/var/log/qmail/qmail-tls# whois 58.246.24.242
% [whois.apnic.net node-2]
% Whois data copyright terms http://www.apnic.net/db/dbcopyright.htmlinetnum: 58.246.24.240 – 58.246.24.247
netname: SH-Ribeira
country: cn
descr: Ribeira (Shanghai) Business Consulting Co., Ltd.
admin-c: YR194-AP
tech-c: YR194-AP
status: ASSIGNED NON-PORTABLE
changed: sh-ipmaster@chinaunicom.cn 20081125
mnt-by: MAINT-CNCGROUP-SH
source: APNIC
I’ve sent a note to China Unicom, but don’t expect any reply. A google of Ribiera Shanghai doesn’t reveal any obvious people to complain to either.
Yet another instance where I should put some active logging into the server to notify me when queue / connection sizes stay at high levels…
Post comment
Archives
- December 2011
- November 2011
- October 2011
- September 2011
- July 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
Categories
- Apple
- Badges
- BMW
- China Related
- Cool Hunting
- Exploits
- Firmware
- Food
- General Talk
- government
- IP Cam
- iPhone
- Lasers
- legislation
- MODx
- MySQL
- requirements
- Service Issues
- Tao Bao
- Technical Mumbo Jumbo
- Things that will get me censored
- Travel
- Uncategorized
- Useful Info
Most Popular Posts
- Samsung N310 (Samsung Go) Hackintosh Installation on Snow Leopard (9996)
- BMW Keys and Transponders E36 E38 E46 etc (EWS2) (7283)
- eFrontWPI - Wordpress integration Plugin for eFront (7148)
- IPCam Hacking - pt#2 (6539)
- IP Cam Hacking – pt#5 (4410)
Tags
Recent Comments
-
tryphon: It helped me to fix mine. I used a pair of pliers like you did and it worked fine. I drink a coffee typing...
-
mark: I have a ms10105 v4.1 moshisoft board and here is the pinout: 1 y stepper a (yellow) 2 y stepper a (white) 3...
-
Lawrence Sheed: Haven’t taken a deep look yet, probably next month can check it out. There are people who are...
-
mark: Yes…that moshi software is crap. I used the corel draw plugin for awhile but it only works about 20% of...
-
Kunlun: I tried to get my motorbike lesson after my car driving lesson, they answered me that I needed to wait 1...
Recent Trackbacks
- SISTEMAS O.R.P: Recuperar una cámara Zaapa CIP-RW después de un fallo de actualización
- Blog - DO Bots: Brookstone Rover AC13
- How can I stop Pop3 Brute Force attacks: need to create a regex, and add it to fail2ban Here is a guide....
- shanghailoz is our latest member! -:
- Probleem bij installatie op Samsung N310:



ICP Permit
Webmail
Newsletters
Support
