From: Jose Isaias Cabrera <jicman@outlook.com>
To: Pokechu22 <pokechu022+cygwin-list@gmail.com>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: network trace capturing tool in cygwin
Date: Thu, 13 Jun 2019 17:40:00 -0000 [thread overview]
Message-ID: <DB7PR01MB53860B1731EF251BBCD1AC76DEEF0@DB7PR01MB5386.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <CAEpCGDQcvLadzgEmV+DYWV=VQMe+aW2TzyQzZGXKZzXA2b4hPA@mail.gmail.com>
Pokechu22, on Thursday, June 13, 2019 01:27 PM, wrote...
> On Thu, Jun 13, 2019 at 10:02 AM Jose Isaias Cabrera wrote:
> >
> Hello josé,
>
> To my (limited) knowledge, it simply isn't available, presumably
> because of elevation requirements on windows or something like that.
> I think what you want is winpcap (or npcap?) along with windump... or
> maybe wireshark? All of these are regular windows programs, not ones
> that depend on cygwin (though you should be able to use them from
> cygwin).
Yeah, I know about those. The place where I am trying to use it is work, and they have banned these utilities from downloading, etc. But I thought that I could use cygwin, internally and capture the data I need. Back to the drawing board. ;-)
Thanks Poke.
josé
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-06-13 17:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 17:02 Jose Isaias Cabrera
2019-06-13 17:27 ` Pokechu22
2019-06-13 17:40 ` Jose Isaias Cabrera [this message]
2019-06-18 15:35 ` Andrey Repin
2019-06-18 16:54 ` Jose Isaias Cabrera
2019-06-18 18:20 ` Andrey Repin
2019-06-18 18:27 ` Jose Isaias Cabrera
2019-06-19 18:19 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DB7PR01MB53860B1731EF251BBCD1AC76DEEF0@DB7PR01MB5386.eurprd01.prod.exchangelabs.com \
--to=jicman@outlook.com \
--cc=cygwin@cygwin.com \
--cc=pokechu022+cygwin-list@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).