I am sure it is an IP spoof as Scott runs linux and apache web-servers (even though out of date
)
What?
It is _not_ an IP spoof, the attacking IP [1] was his machines LAN ip (192.168.2.12 [2]), and the target was Scotts webserver (see the little ->> arrow, it shows the direction of the attack).
[1]: Not really an attack, the users brain-dead software (or firmware as the case may be) saw multiple connections created by the users browser as a synflood, and there was either some lag or packet dropping, which along with a premature timeout (awaiting ACKs), kept the soft/firmware from seeing the ACKs, a sure sign of brain-dead coding, or a misconfiguration in the firewall settings, probably combined with an over-eager browser (like IE7 or Firefox with the FasterFox plugin (cranked up all the way), or sometimes download accelerators).
[2]: The LAN ip is also a RFC1918 address which are usually not routable over the public internet, and most ISPs do egress filtering, and most firewalls (such as iptables) can be, and usually are configured to not allow incoming from RFC1918 addressess into an outward facing interface from the outside, so spoofing as one of these ips would be likely futile.
P.S. I just _have_ to know, what does what server software Scott use have anything to do with syn flooding or spoofing?