PUSH is basically TCP's way of flushing out the data. Because TCP is
stream oriented, it's great for throughput, but if you want to say "yo,
I've got this bunch of data, and I don't want you to accumulate it into
a nice big buffer for protocol efficiency, send it now". The classic
example of this is in interactive protocols like ssh or telnet where you
want that <return> that you just presses or ctrl-c or other to be sent
to the other side immediately, and not wait.
Why your application is doing that, I couldn't say, but there are quite
a few legitimate uses.
As for the firewall claming 6gbits/sec when you've only sending
1gbit/sec sounds quite bogus. Does your host plug directly into the
firewall or is there a switch in between? If there's network gear in
between, as I expect, it would be easy to look at the port counters and
see actual throughput.
As others have pointed out, the firewall could be having problem with
the number of packets per seconds. Unless the firewall is actively
blocking ICMP, I wouldn't worry too much about MTU. The Path MTU
discovery should take care of all of that.
_______________________________________________
Tech mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
http://lopsa.org/
