<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.network.wireshark.user">
    <title>gmane.network.wireshark.user</title>
    <link>http://blog.gmane.org/gmane.network.wireshark.user</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.wireshark.user/5672"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.wireshark.user/5671"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.wireshark.user/5670"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.wireshark.user/5669"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.wireshark.user/5668"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.wireshark.user/5667"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.wireshark.user/5666"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.wireshark.user/5665"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.wireshark.user/5664"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.wireshark.user/5663"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.wireshark.user/5662"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.wireshark.user/5661"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.wireshark.user/5660"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.wireshark.user/5659"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.wireshark.user/5658"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.wireshark.user/5657"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.wireshark.user/5656"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.wireshark.user/5655"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.wireshark.user/5654"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.wireshark.user/5653"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.network.wireshark.user/5672">
    <title>Re: BPDU packets</title>
    <link>http://permalink.gmane.org/gmane.network.wireshark.user/5672</link>
    <description>
You actually have a bigger problem.  (nit picking: technically, they are 
bdpu frames and not packets).

The problem with BPDU's is that they don't just go on and on and on. 
You have to capture it at each and every subnet.

Find the root bridge, then starting going down the tree from there.

</description>
    <dc:creator>Hansang Bae</dc:creator>
    <dc:date>2008-07-06T03:14:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.wireshark.user/5671">
    <title>Re: How to filter out last 1000 frames in a quick way</title>
    <link>http://permalink.gmane.org/gmane.network.wireshark.user/5671</link>
    <description>
The only thing you could try would be to use "editcap -c xxx" to specify 
how many packets you want per trace file (where xxx = how many packets 
you want)

Or you could try -A option to specify when you want to start seeing the 
"interesting" packets.

</description>
    <dc:creator>Hansang Bae</dc:creator>
    <dc:date>2008-07-06T03:11:33</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.wireshark.user/5670">
    <title>Re: add random packet lost</title>
    <link>http://permalink.gmane.org/gmane.network.wireshark.user/5670</link>
    <description>
You can't just use editcap.  If you do, you'll lose the packets and 
Wireshark will flag the missing packets (prev segment lost).  However, 
you won't see retransmissions, fast retansmissions, triple duplicate 
acks etc. If you want to see what packet loss looks like, create a 
duplex mismatch and push/pull some files via ftp



</description>
    <dc:creator>Hansang Bae</dc:creator>
    <dc:date>2008-07-06T02:38:37</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.wireshark.user/5669">
    <title>Multiple trace file analysis</title>
    <link>http://permalink.gmane.org/gmane.network.wireshark.user/5669</link>
    <description>I have 2 trace files (client.pcap and server.pcap) and they are both sync'ed
to the same time server.  I can manually open both trace files and see that
client-packet 1 left at x and arrived server-packet 1 at y.  Assume there
are the same number of packets in both trace files.

Does anyone have any idea how I could automate this process to simply find
the delta between various packets in 2 trace files.  Initially, I would be
happy with that, but a bonus would be to flag lost or out of order packets.
I'm about to manually write a Perl script to do this, but wanted to throw
this out to the group to save me some brain cells and time.

Thanks in advance

</description>
    <dc:creator>Tony Fortunato</dc:creator>
    <dc:date>2008-07-04T13:15:34</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.wireshark.user/5668">
    <title>Re: Possible network latency</title>
    <link>http://permalink.gmane.org/gmane.network.wireshark.user/5668</link>
    <description/>
    <dc:creator>Visser, Martin</dc:creator>
    <dc:date>2008-07-04T07:16:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.wireshark.user/5667">
    <title>Re: how to print time with epoch formation bytshark</title>
    <link>http://permalink.gmane.org/gmane.network.wireshark.user/5667</link>
    <description>Unluckily,  I am not permitted to use GUI. So is it
possible to achieve this?


On Tue, Jul 1, 2008 at 11:20 PM, Stephen Fisher
&lt;stephentfisher-/E1597aS9LQAvxtiuMwx3w&lt; at &gt;public.gmane.org&gt; wrote:
</description>
    <dc:creator>Ian jonhson</dc:creator>
    <dc:date>2008-07-04T04:18:43</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.wireshark.user/5666">
    <title>Re: Dumpcap crashes all the times</title>
    <link>http://permalink.gmane.org/gmane.network.wireshark.user/5666</link>
    <description>
I note that Windows 'dumpcap -L' crashes for me in V1.0.1 but not in v1.0.0

I suspect a wpcap issue; I'm in the process of checking further.....

I'll file a bug report with some details (bugzilla.wireshark.org).

Thanks
</description>
    <dc:creator>Bill Meier</dc:creator>
    <dc:date>2008-07-03T23:49:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.wireshark.user/5665">
    <title>Re: TurboCap card with Wirehshark under Linux ?</title>
    <link>http://permalink.gmane.org/gmane.network.wireshark.user/5665</link>
    <description>Hi!

TurboCap runs on Windows, only.
There are no drivers available for Linux.

Have a nice day
GV

----- Original Message ----- 
From: "Huff, David" &lt;david-l0cyMroinI0&lt; at &gt;public.gmane.org&gt;
To: &lt;wireshark-users-IZ8446WsY0/dtAWm4Da02A&lt; at &gt;public.gmane.org&gt;
Sent: Thursday, July 03, 2008 12:06 PM
Subject: [Wireshark-users] TurboCap card with Wirehshark under Linux ?



</description>
    <dc:creator>Gianluca Varenni</dc:creator>
    <dc:date>2008-07-03T19:36:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.wireshark.user/5664">
    <title>Re: Protocol analisys</title>
    <link>http://permalink.gmane.org/gmane.network.wireshark.user/5664</link>
    <description>

SSH: it doesn't identify SSH on ports other than 22; if a user wants to 
dissect SSH traffic on other ports, they'll have to manually specify the 
traffic with "Decode As".

HTTP: the HTTP dissector registers, in addition to port 80, ports 3128 
and 3132 (for proxies), port 8080, and some other known ports for HTTP. 
  There's a preference that gives a comma-separated list of ports; you 
can add ports to that list.  In addition, some protocols that are 
implemented atop HTTP can make their port number dissected as HTTP and 
then hand off the traffic to the dissector (e.g., IPP).  "Decode As" can 
also be used.

FTP command: it doesn't identify FTP command traffic on ports other than 21.

FTP data: it identifies FTP data traffic on port 20, and also looks at 
PORT and PASV requests, if they're captured.
</description>
    <dc:creator>Guy Harris</dc:creator>
    <dc:date>2008-07-03T19:32:11</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.wireshark.user/5663">
    <title>Protocol analisys</title>
    <link>http://permalink.gmane.org/gmane.network.wireshark.user/5663</link>
    <description>Hi!

I want to make TC scripts for traffic control and shaping, so I would
like to know how wireshark identifies various protocols (like SSH,
HTTP, ftp command and data etc.) either if the server uses non standard
ports.

Thanks in advance!

Dchard

</description>
    <dc:creator>Sipos Csaba</dc:creator>
    <dc:date>2008-07-03T18:53:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.wireshark.user/5662">
    <title>TurboCap card with Wirehshark under Linux ?</title>
    <link>http://permalink.gmane.org/gmane.network.wireshark.user/5662</link>
    <description>Anyone using the Cace Tech. TurboCap card with Wireshark under Linux ?

   http://www.cacetech.com/products/turbocap.htm

If so, where'd you find drivers ? Any issues with setup or configuration ?

Thanks, and regards,
--
    _
 __| |_  David P. Huff, david-l0cyMroinI0&lt; at &gt;public.gmane.org
 \_   _} Network Management Services
   \_(   Texas Instruments, Inc.
</description>
    <dc:creator>Huff, David</dc:creator>
    <dc:date>2008-07-03T19:06:11</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.wireshark.user/5661">
    <title>Re: Capturing Giant Packets Only</title>
    <link>http://permalink.gmane.org/gmane.network.wireshark.user/5661</link>
    <description>I captured all traffic on my port-channel and filtered for ethernet.len
into the 100s of thousands. I opened a case with Cisco and they
confirmed that this is a cosmetic bug on the version of IOS that I'm
running on the 6500 and will require an upgrade to fix it.

thanks for the help on this.

john 


 

-----Original Message-----
From: wireshark-users-bounces-IZ8446WsY0/dtAWm4Da02A&lt; at &gt;public.gmane.org
[mailto:wireshark-users-bounces-IZ8446WsY0/dtAWm4Da02A&lt; at &gt;public.gmane.org] On Behalf Of Guy Harris
Sent: Wednesday, July 02, 2008 1:01 PM
To: Community support list for Wireshark
Subject: Re: [Wireshark-users] Capturing Giant Packets Only

Sheahan, John wrote:
giants?

If giant packets are Ethernet frames &gt; 1514 bytes (if you don't count
the FCS)/1518 bytes (if you count the FCS), a capture filter such as
"greater 1515" (confusingly, the "greater" operation in the
libpcap/WinPcap filter parser is defined to mean "greater than or equal
to") or "greater 1519", depending on whether your adapter supplies the
FCS when capturing, should work.
_______________________________________________
Wireshark-users mailing list
Wireshark-users-IZ8446WsY0/dtAWm4Da02A&lt; at &gt;public.gmane.org
https://wireshark.org/mailman/listinfo/wireshark-users
</description>
    <dc:creator>Sheahan, John</dc:creator>
    <dc:date>2008-07-03T17:11:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.wireshark.user/5660">
    <title>Re: Dissector for ANSI TCAP NATIONALcode:0notimplemented.</title>
    <link>http://permalink.gmane.org/gmane.network.wireshark.user/5660</link>
    <description>

Presumably in that case the dissector would indicate that the command 
code is unknown because the corresponding request isn't in the trace, 
not that there's no dissector for the command code.  (If not, that needs 
to be fixed.)
</description>
    <dc:creator>Guy Harris</dc:creator>
    <dc:date>2008-07-03T17:07:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.wireshark.user/5659">
    <title>Re: Compiling problems</title>
    <link>http://permalink.gmane.org/gmane.network.wireshark.user/5659</link>
    <description>

Dani M wrote:
[...]
[...]

According to:

http://lists.gnupg.org/pipermail/gnupg-devel/2004-February/020779.html

that symbol was new to libgcrypt 1.1.92.  I have checked in a change 
(rev 25666) to our "configure.in" to only try to use that version or later.
</description>
    <dc:creator>Jeff Morriss</dc:creator>
    <dc:date>2008-07-03T16:00:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.wireshark.user/5658">
    <title>Re: Dissector for ANSI TCAP NATIONAL code:0notimplemented.</title>
    <link>http://permalink.gmane.org/gmane.network.wireshark.user/5658</link>
    <description>Hi,
If the request isn't in the trace it's not possible to decode the response
as the command code is unknown(not present).
Regards
Anders

-----Ursprungligt meddelande-----
Från: wireshark-users-bounces-IZ8446WsY0/dtAWm4Da02A&lt; at &gt;public.gmane.org
[mailto:wireshark-users-bounces-IZ8446WsY0/dtAWm4Da02A&lt; at &gt;public.gmane.org] För Abhik Sarkar
Skickat: den 3 juli 2008 16:02
Till: Community support list for Wireshark
Ämne: Re: [Wireshark-users] Dissector for ANSI TCAP NATIONAL code:0
notimplemented.

Hi,

I think you should raise a bug request at
http://bugs.wireshark.org/bugzilla/ with a sample capture so someone
can work on it.

Best regards,
Abhik.

On Thu, Jul 3, 2008 at 12:48 PM, S R I K A S I R A J U
&lt;srikasiraju-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt; wrote:
_______________________________________________
Wireshark-users mailing list
Wireshark-users-IZ8446WsY0/dtAWm4Da02A&lt; at &gt;public.gmane.org
https://wireshark.org/mailman/listinfo/wireshark-users

</description>
    <dc:creator>Anders Broman</dc:creator>
    <dc:date>2008-07-03T15:35:08</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.wireshark.user/5657">
    <title>Re: Dissector for ANSI TCAP NATIONAL code:0 notimplemented.</title>
    <link>http://permalink.gmane.org/gmane.network.wireshark.user/5657</link>
    <description>Hi,

I think you should raise a bug request at
http://bugs.wireshark.org/bugzilla/ with a sample capture so someone
can work on it.

Best regards,
Abhik.

On Thu, Jul 3, 2008 at 12:48 PM, S R I K A S I R A J U
&lt;srikasiraju-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt; wrote:
</description>
    <dc:creator>Abhik Sarkar</dc:creator>
    <dc:date>2008-07-03T14:02:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.wireshark.user/5656">
    <title>Re: Possible network latency</title>
    <link>http://permalink.gmane.org/gmane.network.wireshark.user/5656</link>
    <description/>
    <dc:creator>Albert Jurado</dc:creator>
    <dc:date>2008-07-03T13:54:14</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.wireshark.user/5655">
    <title>Dissector for ANSI TCAP NATIONAL code:0 notimplemented.</title>
    <link>http://permalink.gmane.org/gmane.network.wireshark.user/5655</link>
    <description/>
    <dc:creator>S R I K A S I R A J U</dc:creator>
    <dc:date>2008-07-03T08:48:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.wireshark.user/5654">
    <title>Trace file preview handler</title>
    <link>http://permalink.gmane.org/gmane.network.wireshark.user/5654</link>
    <description/>
    <dc:creator>Jerry Smith</dc:creator>
    <dc:date>2008-07-03T03:12:40</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.wireshark.user/5653">
    <title>Question on the Header File Concerning the FIXProtocol</title>
    <link>http://permalink.gmane.org/gmane.network.wireshark.user/5653</link>
    <description/>
    <dc:creator>Jayakumar Santhanagopal</dc:creator>
    <dc:date>2008-07-02T21:39:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.wireshark.user/5652">
    <title>Re: Compiling problems</title>
    <link>http://permalink.gmane.org/gmane.network.wireshark.user/5652</link>
    <description/>
    <dc:creator>Dani M</dc:creator>
    <dc:date>2008-07-03T13:39:48</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.network.wireshark.user">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.network.wireshark.user</link>
  </textinput>
</rdf:RDF>
