Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

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: Joerg Mayer <jmayer@xxxxxxxxx>
Date: Thu, 7 Sep 2006 00:02:13 +0200

On Thu, Sep 07, 2006 at 07:56:09AM +1000, ronnie sahlberg wrote:
> "Autoneg does fail sometimes."
> 
> True.
> Autonegotiate is broken by design and one should never ever use
> autonegotiate.

That's a very broad statement. Let's just say I disagree: Acutally I
know of some medium to large installations, where autoneg is the default
by now. Btw, about 6 years ago I would have stated that autoneg causes
more problems than it solves - by now I think the other way round.

 Ciao
      Joerg
-- 
Joerg Mayer                                           <jmayer@xxxxxxxxx>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.

  • Follow-Ups:
    • Re: [Wireshark-users] No TCP traffic
      • From: ronnie sahlberg
  • References:
    • [Wireshark-users] No TCP traffic
      • From: Alan Middlehurst
    • Re: [Wireshark-users] No TCP traffic
      • From: Jaap Keuter
    • Re: [Wireshark-users] No TCP traffic
      • From: ronnie sahlberg
  • Prev by Date: Re: [Wireshark-users] trouble getting packaged installs to work on OSX
  • Next by Date: Re: [Wireshark-users] No TCP traffic
  • Previous by thread: Re: [Wireshark-users] No TCP traffic
  • Next by thread: Re: [Wireshark-users] No TCP traffic
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation