Q 1.1: Where can I get help?
- A: Support is available on the ethereal-users mailing list. Subscription
- information and archives for all of Ethereal's mailing lists can be found at
- http://www.ethereal.com/lists
+ A: Community support is available on the ethereal-users mailing list.
+ Subscription information and archives for all of Ethereal's mailing lists
+ can be found at http://www.ethereal.com/lists. An IRC channel dedicated to
+ Ethereal can be found at irc://irc.freenode.net/ethereal.
+
+ Commercial support, training, and development services are available from
+ Ethereal Software.
Q 1.2: How much does Ethereal cost?
Q 1.5: What protocols are currently supported?
- A: There are currently 706 supported protocols and media, listed below.
+ A: There are currently 724 supported protocols and media, listed below.
Descriptions can be found in the ethereal(1) man page.
3Com XNS Encapsulation
Cisco NetFlow
Cisco SLARP
Cisco Session Management
+ Cisco Wireless Layer 2
Clearcase NFS
CoSine IPNOS L2 debug output
Common Industrial Protocol
Common Open Policy Service
Common Unix Printing System (CUPS) Browsing Protocol
Compuserve GIF
+ Computer Interface to Message Distribution
Configuration Test Protocol (loopback)
Connectionless Lightweight Directory Access Protocol
Coseventcomm Dissector Using GIOP API
Data
Data Link SWitching
Data Stream Interface
+ Datagram Congestion Control Protocol
Datagram Delivery Protocol
Decompressed SigComp message as raw text
Diameter Protocol
Distributed Interactive Simulation
Distributed Network Protocol 3.0
Domain Name Service
+ Dublin Core Metadata (DC)
Dynamic DNS Tools Protocol
Dynamic Trunking Protocol
ENTTEC
Ethernet over IP
Extended Security Services
Extensible Authentication Protocol
+ Extreme Discovery Protocol
FC Extended Link Svc
FC Fabric Configuration Server
FCIP
- FTAM
FTP Data
FTServer Operations
Fiber Distributed Data Interface
GSM Mobile Application
GSM SMS TPDU (GSM 03.40)
GSM Short Message Service User Data
+ GSM_SS
GSS-API Generic Security Service Application Program Interface
General Inter-ORB Protocol
Generic Routing Encapsulation
H.248 MEGACO
H221NonStandard
H235-SECURITY-MESSAGES
+ H323-MESSAGES
HP Extended Local-Link Control
HP Remote Maintenance Protocol
HP Switch Protocol
ISO 8073 COTP Connection-Oriented Transport Protocol
ISO 8327-1 OSI Session Protocol
ISO 8473 CLNP ConnectionLess Network Protocol
+ ISO 8571 FTAM
ISO 8602 CLTP ConnectionLess Transport Protocol
ISO 8823 OSI Presentation Protocol
ISO 9542 ESIS Routeing Information Exchange Protocol
ISUP Thin Protocol
ISystemActivator ISystemActivator Resolver
+ ITU M.3100 Generic Network Information Model
ITU-T E.164 number
ITU-T Recommendation H.261
+ ITU-T Recommendation H.263
ITU-T Recommendation H.263 RTP Payload header (RFC2190)
InMon sFlow
Information Access Protocol
+ Init shutdown service
Intel ANS probe
Intelligent Platform Management Interface
Inter-Access-Point Protocol
Link Access Procedure Balanced (LAPB)
Link Access Procedure Balanced Ethernet (LAPBETHER)
Link Access Procedure, Channel D (LAPD)
+ Link Layer Discovery Protocol
Link Management Protocol (LMP)
Linux cooked-mode capture
Local Management Interface
MTP 2 User Adaptation Layer
MTP 3 User Adaptation Layer
MTP2 Peer Adaptation Layer
+ MULTIMEDIA-SYSTEM-CONTROL
Media Gateway Control Protocol
Media Type
Media Type: message/http
Message Transfer Part Level 3
Message Transfer Part Level 3 Management
Meta Analysis Tracing Engine
+ Microsoft AT-Scheduler Service
Microsoft Distributed File System
Microsoft Distributed Link Tracking Server Service
Microsoft Encrypted File System Service
Microsoft Messenger Service
Microsoft Network Logon
Microsoft Plug and Play service
- Microsoft Registry
Microsoft Routing and Remote Access Service
Microsoft Security Account Manager
Microsoft Server Service
Microsoft Service Control
Microsoft Spool Subsystem
- Microsoft Task Scheduler Service
Microsoft Telephony API Service
Microsoft Windows Browser Protocol
Microsoft Windows Lanman Remote API Protocol
Remote Procedure Call
Remote Program Load
Remote Quota
+ Remote Registry Service
Remote Shell
- Remote Shutdown
Remote Wall protocol
Remote sec_login preauth interface.
Resource ReserVation Protocol (RSVP)
SSCF-NNI
SSCOP
SSH Protocol
+ STANAG 4406 Military Message Extensions
Secure Socket Layer
Sequenced Packet Protocol
Sequenced Packet eXchange
Signalling Connection Control Part Management
Simple Mail Transfer Protocol
Simple Network Management Protocol
+ Simple Protected Negotiation
Simple Traversal of UDP Through NAT
Sinec H1 Protocol
Sipfrag
Socks Protocol
SoulSeek Protocol
Spanning Tree Protocol
- Spnego
Stream Control Transmission Protocol
Subnetwork Dependent Convergence Protocol
Symantec Enterprise Firewall
+ Synchronized Multimedia Integration Language
Synchronous Data Link Control (SDLC)
Synergy
Syslog message
Virtual Trunking Protocol
WAP Binary XML
WAP Session Initiation Request
+ WINS (Windows Internet Name Service) Replication
Web Cache Coordination Protocol
WebSphere MQ
WebSphere MQ Programmable Command Formats
Wireless Transport Layer Security
Wlan Certificate Extension
X Display Manager Control Protocol
+ X.228 OSI Reliable Transfer Service
X.25
X.25 over TCP
X.29
+ X.411 OSI Message Transfer Service
+ X.420 OSI Information Object
X.509 Authentication Framework
X.509 Certificate Extensions
X.509 Information Framework
X.509 Selected Attribute Types
+ X.880 OSI Remote Operations Service
X11
X711 CMIP
Xyplex
eDonkey Protocol
eXtensible Markup Language
giFT Internet File Transfer
- h225
- h245
h450
iFCP
iSCSI
iSNS
+ iTunes podCast rss elements
+ rss
Q 1.6: Are there any plans to support {your favorite protocol}?
such as T1/E1 lines are all PPP interfaces, so those interfaces might
not show up on the list of interfaces in the "Capture Options" dialog on
those OSes.
- On Windows 2000 and later, installing the beta version of WinPcap 3.1
- might help, although, as it's a beta version, that might cause some
- other problems that don't occur with older versions of WinPcap; you
- should report those problems to the WinPcap developers, so that they can
- try to fix those problems before the final version of WinPcap 3.1 is
- released. WinPcap 3.1 will not support PPP captures on Windows NT 4.0.
- See the Ethereal Wiki item on PPP capturing for details.
+ On Windows 2000, Windows XP, and Windows Server 2003, but not Windows NT
+ 4.0 or Windows Vista Beta 1, you should be able to capture on the
+ "GenericDialupAdapter" with WinPcap 3.1. (3.1 beta releases called it
+ the "NdisWanAdapter"; if you're using a 3.1 beta release, you should
+ un-install it and install the final 3.1 release.) See the Ethereal Wiki
+ item on PPP capturing for details.
4. WinPcap prior to 3.0 does not support multiprocessor machines (note that
machines with a single multi-threaded processor, such as Intel's new
multi-threaded x86 processors, are multiprocessor machines as far as the
avoid those problems, support for PPP WAN interfaces on those versions of
Windows has been disabled in WinPcap 3.0.
- On Windows 2000 and later, installing the beta version of WinPcap 3.1 might
- help, although, as it's a beta version, that might cause some other problems
- that don't occur with older versions of WinPcap; you should report those
- problems to the WinPcap developers, so that they can try to fix those
- problems before the final version of WinPcap 3.1 is released. WinPcap 3.1
- will not support PPP captures on Windows NT 4.0. See the Ethereal Wiki item
- on PPP capturing for details.
+ On Windows 2000, Windows XP, and Windows Server 2003, but not Windows NT 4.0
+ or Windows Vista Beta 1, you should be able to capture on the
+ "GenericDialupAdapter" with WinPcap 3.1. (3.1 beta releases called it the
+ "NdisWanAdapter"; if you're using a 3.1 beta release, you should un-install
+ it and install the final 3.1 release.) See the Ethereal Wiki item on PPP
+ capturing for details.
Q 5.7: I'm running Ethereal on a UNIX-flavored OS; why does some network
interface on my machine not show up in the list of interfaces in the
of Ethereal and a shared libpcap library with DAG support, in order to do so
with Ethereal. You should ask Endace whether that could be used to capture
traffic on, for example, your T1/E1 link.
- There is currently no hardware to support capturing on SS7 links with
- libpcap. (Note that the fact that Ethereal includes dissectors for many SS7
- protocols doesn't imply that it can capture traffic from SS7 links; those
- protocols can be run over Internet protocols.)
+ See the SS7 capture setup page on the Ethereal Wiki for current information
+ on capturing SS7 traffic on TDM links.
Q 5.10: How do I put an interface into promiscuous mode?
"Capture Preferences" dialog box, but this may mean that outgoing packets,
or incoming packets, won't be seen in the capture.
- On Windows 2000 and later, installing the beta version of WinPcap 3.1 might
- help, although, as it's a beta version, that might cause some other problems
- that don't occur with older versions of WinPcap; you should report those
- problems to the WinPcap developers, so that they can try to fix those
- problems before the final version of WinPcap 3.1 is released. WinPcap 3.1
- will not support PPP captures on Windows NT 4.0. See the Ethereal Wiki item
- on PPP capturing for details.
+ On Windows 2000, Windows XP, and Windows Server 2003, but not Windows NT 4.0
+ or Windows Vista Beta 1, you should be able to capture on the
+ "GenericDialupAdapter" with WinPcap 3.1. (3.1 beta releases called it the
+ "NdisWanAdapter"; if you're using a 3.1 beta release, you should un-install
+ it and install the final 3.1 release.) See the Ethereal Wiki item on PPP
+ capturing for details.
Q 5.25: I'm running Ethereal on Windows 95/98/Me, on a machine with more
than one network adapter of the same type; Ethereal shows all of those
ethereal-users[AT]ethereal.com mailing list.
For corrections/additions/suggestions for this web page (and not Ethereal
support questions), please send email to ethereal-web[AT]ethereal.com .
- Last modified: Thu, August 25 2005.
+ Last modified: Tue, December 06 2005.