No, the clients that can't connect do not have any mention of ECN (explicit congestion notification) in the Wireshark traces.
On Aug 17, 2007, at 8:04 PM, Tom Eastep <[EMAIL PROTECTED]> wrote: >> However, for some, the connection never gets data back >> according to the Wireshark trace. The main site we are seeing this >> problem with is http://java.sun.com >> <https://webmailcluster.perfora.net/xml/webmail/mailContent;jsessionid=6C22B48DC6FD53E5FEA51FEB29A82FF7.TC134b# >> >> > >> (72.5.124.55 <http://72.5.124.55>). > > Does the Wireshark trace indicate that the problem clients are using > ECN? > > -Tom > -- > Tom Eastep \ Nothing is foolproof to a sufficiently talented fool > Shoreline, \ http://shorewall.net > Washington USA \ [EMAIL PROTECTED] > PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key > > --- > ---------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a > browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Shorewall-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/shorewall-users ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
