Riverbed Cascade Pilot Personal Edition: Take Wireshark to the Next Level - Advanced Triggers and Alerts; Web and VoIP Analytics; Long-Term Trending and Forensics; Deep Packet Analysis with Wireshark

Wireshark-users: Re: [Wireshark-users] No TCP traffic

Date Index Thread Index Other Months All Mailing Lists

Date Prev Date Next Thread Prev Thread Next

From: "ronnie sahlberg" <ronniesahlberg@xxxxxxxxx>
Date: Thu, 7 Sep 2006 07:56:09 +1000

"Autoneg does fail sometimes."

True.
Autonegotiate is broken by design and one should never ever use autonegotiate.

On 9/6/06, Jaap Keuter <jaap.keuter@xxxxxxxxx> wrote:

Hi,

Question one: is it really a hub, not a 10/100 switch in disguise? It
would account for the fact that you only captured non unicast packets of
it.
Question two: Are both hub and slow PC agreeing on duplex? If one does
half and the other full, this could lead to 50% packet loss easy. Autoneg
does fail sometimes.

Thanx,
Jaap

_______________________________________________
Wireshark-users mailing list
Wireshark-users@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-users

Follow-Ups:
- Re: [Wireshark-users] No TCP traffic
  - From: Joerg Mayer

References:
- [Wireshark-users] No TCP traffic
  - From: Alan Middlehurst
- Re: [Wireshark-users] No TCP traffic
  - From: Jaap Keuter

Prev by Date: Re: [Wireshark-users] No TCP traffic
Next by Date: Re: [Wireshark-users] trouble getting packaged installs to work on OSX
Previous by thread: Re: [Wireshark-users] No TCP traffic
Next by thread: Re: [Wireshark-users] No TCP traffic
Index(es):
- Date
- Thread