# Asian Pacific Network $IPTABLES -A SMTPCHK -p tcp -s 61.0.0.0/8 -j DROP $IPTABLES -A SMTPCHK -p tcp -s 202.0.0.0/8 -j DROP $IPTABLES -A SMTPCHK -p tcp -s 203.0.0.0/8 -j DROP $IPTABLES -A SMTPCHK -p tcp -s 210.0.0.0/8 -j DROP $IPTABLES -A SMTPCHK -p tcp -s 211.0.0.0/8 -j DROP $IPTABLES -A SMTPCHK -p tcp -s 218.0.0.0/8 -j DROP $IPTABLES -A SMTPCHK -p tcp -s 219.0.0.0/8 -j DROP $IPTABLES -A SMTPCHK -p tcp -s 220.0.0.0/8 -j DROP $IPTABLES -A SMTPCHK -p tcp -s 221.0.0.0/8 -j DROP $IPTABLES -A SMTPCHK -p tcp -s 222.0.0.0/8 -j DROP
I worked for a network support company and one of our clients was having constant crashes from their specific software. We instructed him to call his software support line - the answer "You definately have a TCP/IP Wait state problem." to which they of course offerend no further explanation or solution. Buggy software was the real answer.
We adopted this answer as our standard for when someone wanted an answer to an unanswerable (or stupid) question. "Hey, my computer crashed this morning while I wasn't paying attention to what i was doing and I didn't bother to write down any error code. What caused it?" us: "It's a TCP/IP wait state problem. Let us know if it happens again and write down the error code."
Slashdot Mirror
Who needs 'em?
$IPTABLES -A INPUT -i eth1 -p tcp --dport 25 --syn -j SMTPCHK
# Asian Pacific Network
$IPTABLES -A SMTPCHK -p tcp -s 61.0.0.0/8 -j DROP
$IPTABLES -A SMTPCHK -p tcp -s 202.0.0.0/8 -j DROP
$IPTABLES -A SMTPCHK -p tcp -s 203.0.0.0/8 -j DROP
$IPTABLES -A SMTPCHK -p tcp -s 210.0.0.0/8 -j DROP
$IPTABLES -A SMTPCHK -p tcp -s 211.0.0.0/8 -j DROP
$IPTABLES -A SMTPCHK -p tcp -s 218.0.0.0/8 -j DROP
$IPTABLES -A SMTPCHK -p tcp -s 219.0.0.0/8 -j DROP
$IPTABLES -A SMTPCHK -p tcp -s 220.0.0.0/8 -j DROP
$IPTABLES -A SMTPCHK -p tcp -s 221.0.0.0/8 -j DROP
$IPTABLES -A SMTPCHK -p tcp -s 222.0.0.0/8 -j DROP
Works for me! (among other netBLOCKS I use)
I worked for a network support company and one of our clients was having constant crashes from their specific software. We instructed him to call his software support line - the answer "You definately have a TCP/IP Wait state problem." to which they of course offerend no further explanation or solution. Buggy software was the real answer. We adopted this answer as our standard for when someone wanted an answer to an unanswerable (or stupid) question. "Hey, my computer crashed this morning while I wasn't paying attention to what i was doing and I didn't bother to write down any error code. What caused it?" us: "It's a TCP/IP wait state problem. Let us know if it happens again and write down the error code."