Socket Sabotage

I would like to test my network client with respect to robust network
failure recovery. It works fine if I use iptables to drop communication
back from the server. But I want the socket to generate an error. Aside
from hacking the source, is there a way to tickle a connected socket to
cause it to generate an error when attempting to read / write?

Thanks,
Mike

Michael B Allen schrieb:
> I would like to test my network client with respect to robust network
> failure recovery. It works fine if I use iptables to drop communication
> back from the server. But I want the socket to generate an error. Aside
> from hacking the source, is there a way to tickle a connected socket to
> cause it to generate an error when attempting to read / write?
>
> Thanks,
> Mike
>
I am not a TCP/IP wizard at all but ... would it make sense to change
the MTU size of the NIC's and disable ICMP transfer using the firewall
.... by this, communication should stop as the interfaces are not more
able to negotiate a new MTU size ...