box popped up by "Capture->Start"?
5.6 I'm running Ethereal on Windows; why doesn't my serial port/ADSL
- modem/ISDN modem/show up in the list of interfaces in the "Interface:"
+ modem/ISDN modem show up in the list of interfaces in the "Interface:"
field in the dialog box popped up by "Capture->Start"?
5.7 I'm running Ethereal on a UNIX-flavored OS; why does some network
5.23 When I try to run Ethereal on Windows, it fails to run because it
can't find packet.dll.
- 5.24 I'm running Ethereal on Windows NT/2000/XP/Server; my machine has
- a PPP (dial-up POTS, ISDN, etc.) interface, and it shows up in the
- "Interface" item in the "Capture Options" dialog box. Why can no
- packets be sent on or received from that network while I'm trying to
- capture traffic on that interface?
+ 5.24 I'm running Ethereal on Windows NT 4.0/Windows 2000/Windows
+ XP/Windows Server 2003; my machine has a PPP (dial-up POTS, ISDN,
+ etc.) interface, and it shows up in the "Interface" item in the
+ "Capture Options" dialog box. Why can no packets be sent on or
+ received from that network while I'm trying to capture traffic on that
+ interface?
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
Q 1.4: Can I use Ethereal as part of my commercial product?
- A: As noted, Ethereal is licended under the GNU General Public
+ A: As noted, Ethereal is licensed under the GNU General Public
License. The GPL imposes conditions on your use of GPL'ed code in your
own products; you cannot, for example, make a "derived work" from
Ethereal, by making modifications to it, and then sell the resulting
Q 1.5: What protocols are currently supported?
- A: There are currently 602 supported protocols and media, listed
+ A: There are currently 658 supported protocols and media, listed
below. Descriptions can be found in the ethereal(1) man page.
3GPP2 A11
AOL Instant Messenger
ARCNET
ASN.1 decoding
+ ATAoverEthernet
ATM
ATM AAL1
ATM AAL3/4
AVS WLAN Capture header
AX/4000 Test Block
Ad hoc On-demand Distance Vector Routing Protocol
+ Adaptive Multi-Rate
Address Resolution Protocol
Aggregate Server Access Protocol
Alert Standard Forum
Application Configuration Access Protocol
Art-Net
Async data over ISDN (V.120)
+ Asynchronous Layered Coding
Authentication Header
BACnet Virtual Link Control
BEA Tuxedo
- BSS GPRS Protocol
BSSAP/BSAP
Banyan Vines ARP
Banyan Vines Echo
Banyan Vines LLC
Banyan Vines RTP
Banyan Vines SPP
+ Base Station Subsystem GPRS Protocol
Basic Encoding Rules (ASN.1 X.690)
Bearer Independent Call Control
Bi-directional Fault Detection Control Message
+ BitTorrent
Blocks Extensible Exchange Protocol
Blubster/Piolet MANOLITO Protocol
Boardwalk
Border Gateway Protocol
Building Automation and Control Network APDU
Building Automation and Control Network NPDU
+ CBAPhysicalDevice
CCSDS
CDS Clerk Server Calls
Cast Client Control Protocol
+ Certificate Management Protocol
+ Certificate Request Message Format
Check Point High Availability Protocol
Checkpoint FW-1
Cisco Auto-RP
DCE/RPC Conversation Manager
DCE/RPC Directory Acl Interface
DCE/RPC Endpoint Mapper
- DCE/RPC Endpoint Mapper4
+ DCE/RPC Endpoint Mapper v4
DCE/RPC FLDB
DCE/RPC FLDB UBIK TRANSFER
DCE/RPC FLDB UBIKVOTE
DCE/RPC Repserver Calls
DCE/RPC TokenServer Calls
DCE/RPC UpServer
+ DCOM
+ DCOM IDispatch
+ DCOM IRemoteActivation
DCOM OXID Resolver
- DCOM Remote Activation
DEC Spanning Tree Protocol
DFS Calls
DG Gryphon Protocol
Etheric
Ethernet
Ethernet over IP
+ Extended Security Services
Extensible Authentication Protocol
FC Extended Link Svc
FC Fabric Configuration Server
Generic Security Service Application Program Interface
Gnutella Protocol
H.248 MEGACO
- H225
H235-SECURITY-MESSAGES
- H245
- H4501
HP Extended Local-Link Control
HP Remote Maintenance Protocol
Hummingbird NFS Daemon
HyperSCSI
Hypertext Transfer Protocol
+ ICBAAccoCallback
+ ICBAAccoCallback2
+ ICBAAccoMgt
+ ICBAAccoMgt2
+ ICBAAccoServer
+ ICBAAccoServer2
+ ICBAAccoServerSRT
+ ICBAAccoSync
+ ICBABrowse
+ ICBABrowse2
+ ICBAGroupError
+ ICBAGroupErrorEvent
+ ICBALogicalDevice
+ ICBALogicalDevice2
+ ICBAPersist
+ ICBAPersist2
+ ICBAPhysicalDevice
+ ICBAPhysicalDevice2
+ ICBAPhysicalDevicePC
+ ICBAPhysicalDevicePCEvent
+ ICBARTAuto
+ ICBARTAuto2
+ ICBAState
+ ICBAStateEvent
+ ICBASystemProperties
+ ICBATime
ICQ Protocol
IEEE 802.11 Radiotap Capture header
IEEE 802.11 wireless LAN
IEEE 802.11 wireless LAN management frame
+ IEEE802a OUI Extended Ethertype
ILMI
IP Device Control (SS7 over IP)
IP Over FC
IPX Message
IPX Routing Information Protocol
IPX WAN
- IRemUnknown IRemUnknown Resolver
- IRemUnknown2 IRemUnknown2 Resolver
+ IRemUnknown
+ IRemUnknown2
ISDN
ISDN Q.921-User Adaptation Layer
ISDN User Part
IrDA Link Access Protocol
IrDA Link Management Protocol
JPEG File Interchange Format
+ JXTA P2P
Jabber XML Messaging
Java RMI
Java Serialization
Log Message
Logical Link Control GPRS
Logical-Link Control
+ Logotype Certificate Extensions
Lucent/Ascend debug output
MAC Control
+ MAP_DialoguePDU
MDS Header
MEGACO
MIME Multipart Media Encapsulation
Message Transfer Part Level 2
Message Transfer Part Level 3
Message Transfer Part Level 3 Management
+ Meta Analysis Tracing Engine
Microsoft Directory Replication Service
Microsoft Distributed File System
Microsoft Distributed Link Tracking Server Service
NTLM Secure Service Provider
Name Binding Protocol
Name Management Protocol over IPX
+ Negative-acknowledgment Oriented Reliable Multicast
NetBIOS
NetBIOS Datagram Service
NetBIOS Name Service
Network File System
Network Lock Manager Protocol
Network News Transfer Protocol
+ Network Service Over IP
Network Status Monitor CallBack Protocol
Network Status Monitor Protocol
Network Time Protocol
Null/Loopback
OSI ISO 8571 FTAM Protocol
OSI ISO/IEC 10035-1 ACSE Protocol
+ Online Certificate Status Protocol
Open Policy Service Interface
Open Shortest Path First
OpenBSD Encapsulating device
PC NFS
PKCS#1
PKINIT
+ PKIX CERT File Format
+ PKIX Qualified
+ PKIX Time Stamp Protocol
PKIX1Explitit
PKIX1Implitit
- POSTGRESQL
+ PKIXProxy (RFC3820)
PPP Bandwidth Allocation Control Protocol
PPP Bandwidth Allocation Protocol
PPP CDP Control Protocol
PPP Compression Control Protocol
PPP IP Control Protocol
PPP IPv6 Control Protocol
+ PPP In HDLC-Like Framing
PPP Link Control Protocol
PPP MPLS Control Protocol
PPP Multilink Protocol
PPP-over-Ethernet Discovery
PPP-over-Ethernet Session
PPPMux Control Protocol
+ PROFINET DCP
+ PROFINET IO
+ PROFINET Real-Time Protocol
Packed Encoding Rules (ASN.1 X.691)
Packet Cable Lawful Intercept
PacketCable
Port Aggregation Protocol
Portmap
Post Office Protocol
+ PostgreSQL
Pragmatic General Multicast
Precision Time Protocol (IEEE1588)
Prism
RS Interface properties
RSTAT
RSYNC File Synchroniser
- RTNET
RTcfg
RX Protocol
Radio Access Network Application Part
Radius Protocol
Raw packet data
Real Time Streaming Protocol
+ Real-Time Media Access Control
Real-Time Publish-Subscribe Wire Protocol
Real-Time Transport Protocol
Real-time Transport Control Protocol
SPNEGO-KRB5
SPRAY
SS7 SCCP-User Adaptation Layer
+ SSCF-NNI
SSCOP
SSH Protocol
Secure Socket Layer
Session Initiation Protocol
Session Initiation Protocol (SIP as raw text)
Short Message Peer to Peer
+ Short Message Relaying Service
Signaling Compression
Signalling Connection Control Part
Signalling Connection Control Part Management
Syslog message
Systems Network Architecture
Systems Network Architecture XID
- T38
+ T.38
TACACS
TACACS+
+ TDMA RTmac Discipline
TEI Management Procedure, Channel D (LAPD)
TPKT
Tabular Data Stream
X.509 Information Framework
X.509 Selected Attribute Types
X11
+ X711 CMIP
Xyplex
Yahoo Messenger Protocol
Yahoo YMSG Messenger Protocol
Zone Information Protocol
eDonkey Protocol
giFT Internet File Transfer
+ h225
+ h245
+ h450
iSCSI
iSNS
whether it can capture on them"; we expect that it will be able to
capture on many of them, but we haven't tried it ourselves - if you
try one of those types and it works, please send an update to
- _EWEB_MAILTO).
+ ethereal-web[AT]ethereal.com ).
It can also read a variety of capture file formats, including:
- * libpcap/tcpdump
- * Sun snoop/atmsnoop
- * Shomiti/Finisar Surveyor
- * LanAlyzer
- * DOS-based Sniffer (compressed and uncompressed)
- * MS Network Monitor
- * AIX iptrace
- * NetXray and Windows-based Sniffer
- * EtherPeek/TokenPeek/AiroPeek
- * RADCOM WAN/LAN analyzer
- * Lucent/Ascend debug output
- * Toshiba ISDN router "snoop" output
- * HPUX nettl
- * ISDN4BSD "i4btrace" utility.
- * Cisco Secure IDS
- * pppd log files (pppdump format)
- * VMS TCPIPtrace
- * DBS Etherwatch
- * Visual Networks' Visual UpTime
- * CoSine L2 debug
+ * AG Group/WildPackets EtherPeek/TokenPeek/AiroPeek/EtherHelp/Packet
+ Grabber captures
+ * AIX's iptrace captures
+ * Accellent's 5Views LAN agent output
+ * Cinco Networks NetXRay captures
+ * Cisco Secure Intrusion Detection System IPLog output
+ * CoSine L2 debug output
+ * DBS Etherwatch VMS text output
+ * Endace Measurement Systems' ERF format captures
+ * EyeSDN USB S0 traces
+ * HP-UX nettl captures
+ * ISDN4BSD project i4btrace captures
+ * Linux Bluez Bluetooth stack hcidump -w traces
+ * Lucent/Ascend router debug output
+ * Microsoft Network Monitor captures
+ * Network Associates Windows-based Sniffer captures
+ * Network General/Network Associates DOS-based Sniffer (compressed
+ or uncompressed) captures
+ * Network Instruments Observer version 9 captures
+ * Novell LANalyzer captures
+ * RADCOM's WAN/LAN analyzer captures
+ * Shomiti/Finisar Surveyor captures
+ * Toshiba's ISDN routers dump output
+ * VMS TCPIPtrace/TCPtrace/UCX$TRACE output
+ * Visual Networks' Visual UpTime traffic capture
+ * libpcap, tcpdump and various other tools using tcpdump's capture
+ format
+ * snoop and atmsnoop output
so that it can read traces from various network types, as captured by
other applications or equipment, even if it cannot itself capture on
to see from or to the machine I'm trying to monitor.
A: This might be because the interface on which you're capturing is
- plugged into a switch; on a switched network, unicast traffic between
- two ports will not necessarily appear on other ports - only broadcast
- and multicast traffic will be sent to all ports.
+ plugged into an Ethernet or Token Ring switch; on a switched network,
+ unicast traffic between two ports will not necessarily appear on other
+ ports - only broadcast and multicast traffic will be sent to all
+ ports.
Note that even if your machine is plugged into a hub, the "hub" may be
a switched hub, in which case you're still on a switched network.
In the case of token ring interfaces, the drivers for some of them, on
Windows, may require you to enable promiscuous mode in order to
- capture in promiscuous mode. Ask the vendor of the card how to do
- this, or see, for example, this information on promiscuous mode on
- some Madge token ring adapters (note that those cards can have
- promiscuous mode disabled permanently, in which case you can't enable
- it).
+ capture in promiscuous mode. See the Ethereal Wiki item on Token Ring
+ capturing for details.
In the case of wireless LAN interfaces, it appears that, when those
interfaces are promiscuously sniffing, they're running in a
interface?
A: If you are running Ethereal on Windows NT 4.0, Windows 2000,
- Windows XP, or Windows Server, and this is the first time you have run
- a WinPcap-based program (such as Ethereal, or Tethereal, or WinDump,
- or Analyzer, or...) since the machine was rebooted, you need to run
- that program from an account with administrator privileges; once you
- have run such a program, you will not need administrator privileges to
- run any such programs until you reboot.
+ Windows XP, or Windows Server 2003, and this is the first time you
+ have run a WinPcap-based program (such as Ethereal, or Tethereal, or
+ WinDump, or Analyzer, or...) since the machine was rebooted, you need
+ to run that program from an account with administrator privileges;
+ once you have run such a program, you will not need administrator
+ privileges to run any such programs until you reboot.
If you are running on Windows 95/98/Me, or if you are running on
- Windows NT 4.0/2000/XP/Server and have administrator privileges or a
- WinPcap-based program has been run with those privileges since the
- machine rebooted, then note that Ethereal relies on the WinPcap
- library, on the WinPcap device driver, and on the facilities that come
- with the OS on which it's running in order to do captures.
+ Windows NT 4.0/Windows 2000/Windows XP/Windows Server 2003 and have
+ administrator privileges or a WinPcap-based program has been run with
+ those privileges since the machine rebooted, then note that Ethereal
+ relies on the WinPcap library, on the WinPcap device driver, and on
+ the facilities that come with the OS on which it's running in order to
+ do captures.
Therefore, if the OS, the WinPcap library, or the WinPcap driver don't
support capturing on a particular network interface device, Ethereal
capture on the interface you're currently using. In that case, you
might, for example, have to remove the VPN interface from the
system in order to capture on the PPP serial interface.
- 3. WinPcap 3.0 doesn't support PPP WAN interfaces, and WinPcap 2.3
- doesn't support PPP WAN interfaces on Windows NT/2000/XP/Server,
- so Ethereal cannot capture packets on those devices with WinPcap
- 3.0, or with WInPcap 2.x when running on Windows
- NT/2000/XP/Server. Regular dial-up lines, ISDN lines, and various
- other lines such as T1/E1 lines are all PPP interfaces. This may
- cause the interface not to show up on the list of interfaces in
- the "Capture Options" dialog.
+ 3. WinPcap 2.3 has problems supporting PPP WAN interfaces on Windows
+ NT 4.0, Windows 2000, Windows XP, and Windows Server 2003, and, to
+ avoid those problems, support for PPP WAN interfaces on those
+ versions of Windows has been disabled in WinPcap 3.0. Regular
+ dial-up lines, ISDN lines, ADSL connections using PPPoE or PPPoA,
+ and various other lines 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.
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
response to that question.
Q 5.6: I'm running Ethereal on Windows; why doesn't my serial
- port/ADSL modem/ISDN modem/show up in the list of interfaces in the
+ port/ADSL modem/ISDN modem show up in the list of interfaces in the
"Interface:" field in the dialog box popped up by "Capture->Start"?
- A: All of those devices support Internet access using the
- Point-to-Point (PPP) protocol; WinPcap 3.0 doesn't support PPP
- interfaces, and WinPcap 2.x doesn't support PPP interfaces on Windows
- NT/2000/XP/Server, so Ethereal cannot capture packets on those devices
- with WinPcap 3.0, or with WinPcap 2.x when running on Windows
- NT/2000/XP/Server. This may cause the interface not to show up on the
- list of interfaces in the "Capture Options" dialog.
+ A: Internet access on those devices is often done with the
+ Point-to-Point (PPP) protocol; WinPcap 2.3 has problems supporting PPP
+ WAN interfaces on Windows NT 4.0, Windows 2000, Windows XP, and
+ Windows Server 2003, and, to 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.
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
to capture on that interface?
A: You may need to run Ethereal from an account with sufficient
- privileges to capture packets, such as the super-user account. Only
- those interfaces that Ethereal can open for capturing show up in that
- list; if you don't have sufficient privileges to capture on any
- interfaces, no interfaces will show up in the list.
+ privileges to capture packets, such as the super-user account, or may
+ need to give your account sufficient privileges to capture packets.
+ Only those interfaces that Ethereal can open for capturing show up in
+ that list; if you don't have sufficient privileges to capture on any
+ interfaces, no interfaces will show up in the list. See the Ethereal
+ Wiki item on capture privileges for details on how to give a
+ particular account or account group capture privileges on platforms
+ where that can be done.
If you are running Ethereal from an account with sufficient
privileges, then note that Ethereal relies on the libpcap library, and
on the facilities that come with the OS on which it's running in order
- to do captures.
-
- Therefore, if the OS or the libpcap library don't support capturing on
- a particular network interface device, Ethereal won't be able to
- capture on that device.
-
- On Linux, note that you need to have "packet socket" support enabled
- in your kernel; see the "Packet socket" item in the Linux
- "Configure.help" file.
-
- On BSD, note that you need to have BPF support enabled in your kernel;
- see the documentation for your system for information on how to enable
- BPF support (if it's not enabled by default on your system).
-
- On DEC OSF/1, Digital UNIX, or Tru64 UNIX, note that you need to have
- packet filtering support in your kernel; the doconfig command will
- allow you to configure and build a new kernel with that option.
+ to do captures. On some OSes, those facilities aren't present by
+ default; see the Ethereal Wiki item on adding capture support for
+ details.
+
+ And, even if you're running with an account that has sufficient
+ privileges to capture, and capture support is present in your OS, if
+ the OS or the libpcap library don't support capturing on a particular
+ network interface device or particular types of devices, Ethereal
+ won't be able to capture on that device.
On Solaris, note that libpcap 0.6.2 and earlier didn't support Token
Ring interfaces; the current version, 0.7.2, does support Token Ring,
is boring.
A: We have a collection of strange and exotic sample capture files at
- http://www.ethereal.com/sample/
+ http://wiki.ethereal.com/SampleCaptures
Q 5.16: When I run Ethereal on Solaris 8, it dies with a Bus Error
when I start it.
also using "-V"; note that "-V" produces a full dissection of each
packet, so you might not want to use it.
- To get a fixed version, either build the current SVN version from
- anonymous SVN or a nightly SVN snapshot, or apply to tethereal.c in
- the 0.10.0a source tarball the changes between the broken and the
- fixed versions, which you can download with the URL
- http://www.ethereal.com/cgi-bin/viewcvs.cgi/ethereal/tethereal.c.diff?
- r2=1.211&r1=1.210&diff_format=u and (re-)build from source. It might
- be easier to get the SVN version than to get the patch and apply it to
- the 0.10.0a source tarball, but it's probably easier to build from the
- source tarball than from the SVN version, as you'll need to have more
- tools and make more steps to generate from the SVN version some files
- that are bundled with the source tarball.
-
- Note that to build from the 0.10.0a source tarball on Windows with
- Microsoft Visual C++, you will need to get a file that was missing
- from the 0.10.0a source tarball; see the FAQ for that problem.
-
Q 5.19: When I run Ethereal on Windows NT, it dies with a Dr. Watson
error, reporting an "Integer division by zero" exception, when I start
it.
Web site, the local mirror of the WinPcap Web site, or the
Wiretapped.net mirror of the WinPcap site.
- Q 5.24: I'm running Ethereal on Windows NT/2000/XP/Server; my machine
- has a PPP (dial-up POTS, ISDN, etc.) interface, and it shows up in the
- "Interface" item in the "Capture Options" dialog box. Why can no
- packets be sent on or received from that network while I'm trying to
- capture traffic on that interface?
+ Q 5.24: I'm running Ethereal on Windows NT 4.0/Windows 2000/Windows
+ XP/Windows Server 2003; my machine has a PPP (dial-up POTS, ISDN,
+ etc.) interface, and it shows up in the "Interface" item in the
+ "Capture Options" dialog box. Why can no packets be sent on or
+ received from that network while I'm trying to capture traffic on that
+ interface?
- A: WinPcap doesn't support PPP WAN interfaces on Windows
- NT/2000/XP/Server; one symptom that may be seen is that attempts to
- capture in promiscuous mode on the interface cause the interface to be
- incapable of sending or receiving packets. You can disable promiscuous
- mode using the -p command-line flag or the item in the "Capture
- Preferences" dialog box, but this may mean that outgoing packets, or
- incoming packets, won't be seen in the capture.
+ A: Some versions of WinPcap have problems with PPP WAN interfaces on
+ Windows NT 4.0, Windows 2000, Windows XP, and Windows Server 2003; one
+ symptom that may be seen is that attempts to capture in promiscuous
+ mode on the interface cause the interface to be incapable of sending
+ or receiving packets. You can disable promiscuous mode using the -p
+ command-line flag or the item in the "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.
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
In order to see the raw Ethernet packets, rather than "de-VLANized"
packets, you would have to capture not on the virtual interface for
the VLAN, but on the interface corresponding to the physical network
- device, if possible.
+ device, if possible. See the Ethereal Wiki item on VLAN capturing for
+ details.
Q 5.37: How can I capture raw 802.11 packets, including non-data
(management, beacon) packets?
or /var/tmp on UNIX-flavored OSes, \TEMP on the main system disk
(normally C:) on Windows 9x/Me/NT 4.0, and \Documents and
Settings\your login name\Local Settings\Temp on the main system disk
- on Windows 2000/XP/Server 2003, so the capture file will probably be
- there. It will have a name beginning with ether, with some mixture of
- letters and numbers after that. Please don't send a trace file greater
- than 1 MB when compressed; instead, make it available via FTP or HTTP,
- or say it's available but leave it up to a developer to ask for it. If
- the trace file contains sensitive information (e.g., passwords), then
- please do not send it.
+ on Windows 2000/Windows XP/Windows Server 2003, so the capture file
+ will probably be there. It will have a name beginning with ether, with
+ some mixture of letters and numbers after that. Please don't send a
+ trace file greater than 1 MB when compressed; instead, make it
+ available via FTP or HTTP, or say it's available but leave it up to a
+ developer to ask for it. If the trace file contains sensitive
+ information (e.g., passwords), then please do not send it.
Q 5.46: How can I search for, or filter, packets that have a
particular string anywhere in them?
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, November 18 2004.
+ Last modified: Sun, February 27 2005.
git.samba.org / obnox / wireshark / wip.git / blobdiff