Some LAN networks are based on switch.
How to capture all the packets in this enviromnent? Could winpcap do this?
You cannot capture on switched networks, since the machine running winpcap
does not receive other than packets to/from that host (and some other stuff,
like broadcast).
On switched networks, you have to connect the capturing machine on a
particular port of the switch (which is not present on all
Where to get some working source code for the switch problem, e.g. for
generating such fake ARP replies ?
-Ursprüngliche Nachricht-
Von: nergim [mailto:[EMAIL PROTECTED]]
Gesendet: Freitag, 9. August 2002 09:54
An: [EMAIL PROTECTED]
Betreff: Re: [WinPcap-users] How to capture packets in
- Original Message -
From: nergim [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, August 09, 2002 9:54 AM
Subject: Re: [WinPcap-users] How to capture packets in the future
However you can cheat a little by flooding switch with ARP/RARP packets,
or
generating fake ARP replies,
No, but we plan to support it in the release version (we have received just
two days ago an SMP machine to deal with the problem!)
GV
- Original Message -
From: flyhi [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, August 09, 2002 11:29 AM
Subject: Re: [WinPcap-users] ANNOUNCE:
- Original Message -
From: Jesper Munkholm Jensen (JMJ) [EMAIL PROTECTED]
To: WinPcap Users List (E-mail) [EMAIL PROTECTED]
Sent: Friday, August 09, 2002 11:35 AM
Subject: [WinPcap-users] Changes to the Packet.dll and kernell driver
Hi,
A quick question. I browsed through the new
Hi again,
I meant where all the changes maid to the wpcap.dll, but i then continued
browsing through the new documentation, and found my answers.
But now i have a new one :o)
The function PacketSendPackets() that can send a buffer of raw packets. It
is written that it demands alot of processor
Just a simple question: why don't you use the pcap API, instead of the
Packet one?
GV
- Original Message -
From: Loris Degioanni [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, August 09, 2002 3:40 PM
Subject: Re: [WinPcap-users] Changes to the Packet.dll and kernell driver
Hi,
I have been using the wpcap, but my problem is this;
As i explained earlier, i have to delay the packets f.ex. 40 milli seconds.
My internal clock is updated (Windows 2000) every 15 ms at the present time.
I tried increasing the update interval to 1 ms, but even though my user is
Loris,
Thanks. Yes I agree that the problem is in the application.
When I run the Keita Fujii tcpdump on top of your drivers
I get all the packet data.
I'm running the source forge sniffer with their dll and that is
where I see the problem. Now I have to figure out if the problem
is as you
- Original Message -
From: Jesper Munkholm Jensen (JMJ) [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, August 09, 2002 4:55 PM
Subject: RE: [WinPcap-users] Changes to the Packet.dll and kernell driver
Hi again :o),
Ok. I haven't heard of RDTSC before.
RDTSC is an x86
FYI
I installed WINPCAP 3.0 in hopes of correcting incorrect packet timestamp
with could be off as much as 5 hours.
The packet timestamps are still off by one hour but at least its consist off
by one hour. I'm in Central Time and to get around this
I changed my time zone to Eastern Time.
Thank
Loris,
I got the problem solved. Thanks for the tip.
I was using the wrong PacketCapture.open();
It was defaulting to the 96 bytes.
Loris Degioanni wrote:
What program are you using to capture the packets? It's possible that you
set it to capture only a portion of every packet (for
- Original Message -
From: David [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, August 09, 2002 6:40 PM
Subject: Re: [WinPcap-users] ANNOUNCE: WinPcap 3.0 alpha has been released
Hello,
Can This version solve the problem of loopback ?
That´s means, when I write a packet on
14 matches
Mail list logo
