On Mon, Jun 6, 2011 at 6:02 PM, Martin T wrote:
> I made a RJ45 hardware loopback connector(connected Tx- with Rx+ and
> Tx+ with Rx-), connected this to my eth2 port, configured
> 192.168.88.0/24 to eth2 and executed:
>
> "ping -i0.1 -c3 192.168.88.88"
>
> ..while running tcpdump like this:
>
.
On Tue, Apr 13, 2010 at 11:53 AM, Edgar, Thomas wrote:
> On Apr 12, 2010, at 4:26 PM, Guy Harris wrote:
> >> I am posting to request a value for DLT_SERIAL and LINKTYPE_SERIAL for
> use with libpcap. I am >working on a project to update libpcap and
> Wireshark to capture and parse RS232 and RS48
On Thu, Nov 6, 2008 at 1:29 AM, Michael Richardson <
[EMAIL PROTECTED]> wrote:
>
> > "Peter" == Peter Volkov <[EMAIL PROTECTED]> writes:
>Peter> Hello.
>
>Peter> Currently SITA will be defined and sita code will be tried to
>Peter> build even if --without-sita is passed to ./config
On Jan 6, 2008 3:40 PM, Guy Harris <[EMAIL PROTECTED]> wrote:
> Fulko Hew wrote:
>
> > I think the code is better when its more
> > obvious, segregated and less intrusive.
>
> I've checked into the main and 1.0 branches changes to make it even more
> s
On Jan 6, 2008 3:40 PM, Guy Harris <[EMAIL PROTECTED]> wrote:
... snip ...
There are still some warnings:
>
> ./pcap-sita.c: In function 'acn_findalldevs':
> ./pcap-sita.c:415: warning: 'port' may be used uninitialized in this
> function
> ./pcap-sita.c :414: warning: 'proto' may be used uninitia
On Jan 6, 2008 4:46 PM, Guy Harris <[EMAIL PROTECTED]> wrote:
> Fulko Hew wrote:
>
> > On one hand, my version queries and interoperates with remote
> > devices to allow remote capture. What it does do (unfortunately
> > right now) is ignore any 'local&#x
On Jan 6, 2008 3:40 PM, Guy Harris <[EMAIL PROTECTED]> wrote:
> Fulko Hew wrote:
>
> > I think the code is better when its more
> > obvious, segregated and less intrusive.
>
> I've checked into the main and 1.0 branches changes to make it even more
> s
On Dec 21, 2007 8:27 PM, Guy Harris <[EMAIL PROTECTED]> wrote:
>
> On Dec 20, 2007, at 4:30 AM, Will Barker wrote:
>
> >> ...and 4 bytes long, as per the earlier discussion, or just 1 byte
> >> (or
> >> 2 bytes)?
> >
> > We may as well make it just 1 byte since it only can specify 2
> > alternativ
On 10/22/07, Guy Harris <[EMAIL PROTECTED]> wrote:
>
> Fulko Hew wrote:
>
> > Rats! I see it used in one spot in tcpdump/print-atm.c
> > and it seems that atmuni31.h is also included as part of tcpdump.
> >
> > So I guess it needs to be changed in that
On 10/19/07, Guy Harris <[EMAIL PROTECTED]> wrote:
> On Oct 19, 2007, at 9:15 AM, Fulko Hew wrote:
>
> > Attached is patch file for enabling DLT_SITA support in libpcap.
> > (so that it can be included in the imminent 1.0 release.)
>
> Checked into the main and 1.0 b
Let me try sending this again, except with a compressed patch
file so it gets through the mailing list's size checker!
Attached is patch file for enabling DLT_SITA support in libpcap.
(so that it can be included in the imminent 1.0 release.)
The patch file was created b
On 9/1/07, Guy Harris <[EMAIL PROTECTED]> wrote:
> If you make any other changes, as per the suggestions below, also change
> FILES in the new patch.
Ack
It also duplicates what's in pcap.3; the problem is that changes to
> pcap.3 might render the duplicated stuff out of date.
>
> A document th
On 8/24/07, Guy Harris <[EMAIL PROTECTED]> wrote:
>
> Audet, Jean-Michel wrote:
>
> > My problem is when I am starting the capture. My function close is
> > called then the find device loop starts, all the device (including
> > Ethernet, lo, ...) are re-open than close and is stuck in a loop. Tha
On 8/21/07, Guy Harris <[EMAIL PROTECTED]> wrote:
>
> Fulko Hew wrote:
> > Attached is the file that contains the patches to libpcap to support
> > DLT_SITA.
>
> 1) Files added to INSTALL.txt also need to be added to FILES.
>
Opps, sorry, I forgot about that file
Attached is the file that contains the patches to libpcap to support
DLT_SITA.
It was created by fetching the latest CVS (from Aug 21) and doing a:
LC_ALL=C TZ=UTC0 diff -Naur libpcap.cvs.master/ libpcap/ >
libpcap.sita.patch
I then tested it by applying that patch file with: patch
libpcap.sita.
I am about to provide a patchset for supporting my newly added DLT type.
Since my changes also involve a minor change to 'configure.in', is it my
responsibility to provide patches 'configure' as well? or does someone
else run the appropriate utilities (aclocal; autoconf; autoheader; automake)
to r
On 8/17/07, Guy Harris <[EMAIL PROTECTED]> wrote:
>
> [EMAIL PROTECTED] wrote:
>
> > Here is possible solution to resolve DCE/DTE origin of a LAPB packet.
> >
> > Wireshark libpcap.h has the struct pcaprec_ss990915_hdr, which has
> > ifindex field ( the interface on which packet came in ). During
On 7/19/07, Guy Harris <[EMAIL PROTECTED]> wrote:
OK, I've assigned you DLT_SITA, with the value 196.
Thank you.
-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.
On 7/18/07, Guy Harris <[EMAIL PROTECTED]> wrote:
Fulko Hew wrote:
> Well, I looked at it, and it sounds like a good idea, but it is
> relatively heavy
> weight (I only need to transport 4 bytes, and PPI has 8 bytes of overhead
> (200% in my case) So I'm going to graci
On 7/17/07, Guy Harris <[EMAIL PROTECTED]> wrote:
Fulko Hew wrote:
> So in the end... I think I'd rather continue persuing this single DLT
> approach
> where I can embed status/signalling stuff into a single dissector
>
> IE. Have a pcap with DLT_ACN_WAN and dissect
On 7/17/07, Guy Harris <[EMAIL PROTECTED]> wrote:
Fulko Hew wrote:
> a given capture will only ever have a single protocol within it,
> but since the header is common for all protocols, I thought it was
> better to
> ask for a single DLT instead rather than one DLT
On 7/17/07, Guy Harris <[EMAIL PROTECTED]> wrote:
Fulko Hew wrote:
> I am formally requesting a new DLT value to support capture traffic
> from my companies
So that'd be SITA:
http://www.sita.aero/default.htm
Correct.
> LAN/WAN router/protocol converter de
I am formally requesting a new DLT value to support capture traffic
from my companies LAN/WAN router/protocol converter device.
Since this device supports WAN protocols, this new DLT will be
used to provide/indicate that the data stream contains a
number of WAN port specific pieces of information
I tried sending this yesterday, but apparently it didn't get through...
I'm new to this list, so please be gentle...
I'm involved with a product that does legacy WAN protocols and IP
translation and routing. One of the features of this product is
supposed to be line monitoring. Since I think E
24 matches
Mail list logo
