Resending ... anyone has any idea why this is happening?
===8==Original message text===
Hello Francois,
I used the code you posted earlier to capture traffic with raw
sockets. It's the UDP packets I'm interested. It all works fine
with packets specifically addressed to
Jack wrote:
Resending ... anyone has any idea why this is happening?
These components use ICS:
http://www.magsys.co.uk/delphi/magmonsock.asp
Raw sockets which are available with Windows 2000 and later. This uses WSocket
from the François Piette internet component suite, from
These components use ICS:
http://www.magsys.co.uk/delphi/magmonsock.asp
He's using my components already, he does not want to use WinPcap (which
will fix the problem) due to install issues, and I've been unable to
help him about raw sockets, support for which seems sporadic
on the OSs and
Hello Arno,
I know about the components. They use ICS raw sockets. Because
ICS raw sockets does not capture broadcast packets, they don't
either :(
--
Best regards,
Jack
Tuesday, March 7, 2006, 9:58:59 AM, you wrote:
Jack wrote:
Resending ... anyone has any idea why this is happening?
Jack wrote:
Hello Arno,
I know about the components. They use ICS raw sockets. Because
ICS raw sockets does not capture broadcast packets, they don't
either :(
From what I know raw sockets are not reliable, I tried several
applications based on raw sockets when I was looking for a sniffer.
Hello Arno,
I tried a C++ library based on raw socket and it worked. I briefly
looked at the C++ code and didn't find anything obvious.
If you have the source it shouldn't be a big deal to find out the
difference between TWsocket's and their API calls.
Yeah. I actually compared the part of
Hello Francois,
I used the code you posted earlier to capture traffic with raw
sockets. It's the UDP packets I'm interested. It all works fine
with packets specifically addressed to this IP. However, all
broadcast packets are not captured, such as 192.168.1.255.
I tried a C++ library based on raw
