rh wrote:
If you're going to be sending stuff *that* strange, you shouldn't expect
a receiving machine to run an ordinary networking stack to handle them,
so it seems a bit odd that you're running ttcp on the remote machine,
unless you're trying to use that to test whether your code works if it's
*not* sending strange packets, just normal TCP packets.
Mostly. For now, just using it to work out connection establishment.
Unfortunately, there's a fundamental difference between trying to send
out normal packets (packets where the response would be handled by the
OS's networking stack, e.g. TCP packets sent when you're trying to
establish TCP connections) and trying to send out "abnormal" packets to
test router behavior.
For the former, you'd just have to leave it up to the OS's networking
stack to do the connection establishment, unless you can somehow turn
off the OS's processing of the input in question; for the latter, if
there wouldn't be any responses or the OS would just drop those
responses as "I don't know what this is and I don't care" if there
weren't a raw socket (or something doing packe capture).
So, for better or worse, there's probably not a lot of stuff done to
work out connection establishment that'd be similar to what you'd to
when testing the router's response to packets *other* than TCP segments
or UDP datagrams.
-
This is the tcpdump-workers list.
Visit https://lists.sandelman.ca/ to unsubscribe.
