The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: Real-Time


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [OT] Windows socket snooper


  • To: ukha_d@xxxxxxx
  • Subject: Re: [OT] Windows socket snooper
  • From: "Patrick Lidstone" <patrick@xxxxxxx>
  • Date: Tue, 05 Dec 2000 10:33:58 -0000
  • Delivered-to: rich@xxxxxxx
  • Delivered-to: mailing list ukha_d@xxxxxxx
  • Mailing-list: list ukha_d@xxxxxxx; contact ukha_d-owner@xxxxxxx
  • Reply-to: ukha_d@xxxxxxx

--- In ukha_d@xxxxxxx, Martin Greenwood <martin@p...> wrote:
> Sorry for unrelated question, but I know you all love Windows PC's!
$**!...
>
> Anyone know of a simple program that can send and receive raw
> ethernet socket packets under windows?
> I have someone saying that they cannot do this without disabling
> normal networking and writing complex software.
> As the above is a 10 line program in unix or Linux, I cannot
believe
> this....or perhaps I can!!
>

I think you are confusing packet sniffing with socket based comms.
Socket based comms works in much the same way under windows as it
does under linux. There are some excellent VB socket libs available
too.

If you want to sniff all packets on a network, you need a packet
sniffer. These require that the network interface operate in
promiscuous mode, and do indeed require a special driver to do so.

Have a look at ethereal, or netXray if you need this functionality.

Patrick

> Thanks,
>
> Martin


-------------------------- eGroups Sponsor -------------------------~-~>
eGroups eLerts
It's Easy. It's Fun. Best of All, it's Free!
http://click.egroups.com/1/9698/1/_/2065/_/976012443/
---------------------------------------------------------------------_->





Home | Main Index | Thread Index

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.