Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.networking > #3976
| From | "Bill Cunningham" <nospam@nspam.invalid> |
|---|---|
| Newsgroups | comp.os.linux.networking |
| Subject | Re: read IP header |
| Date | 2017-02-15 13:34 -0500 |
| Organization | A noiseless patient Spider |
| Message-ID | <o826rh$5j6$1@dont-email.me> (permalink) |
| References | <o7vjc2$sqh$1@dont-email.me> <slrnoa6v0i.vnt.grahn+nntp@frailea.sa.invalid> |
"Jorgen Grahn" <grahn+nntp@snipabacken.se> wrote in message
news:slrnoa6v0i.vnt.grahn+nntp@frailea.sa.invalid...
> On Tue, 2017-02-14, Bill Cunningham wrote:
>> Can you look at the IP header with libpcap? I do know it works with
>> the
>> link layer. If I wanted to write smoething to capture packets and read
>> the
>> IP header, as an experiment what would I need other than libpcap? I am
>> thinking sockets.
>
> No, you just need libpcap, and RFC 791. (And you need to understand
> the link-layer headers, so you can move past them to the IPv4 packet
> which they may or may not contain.)
>
> /Jorgen
pcap_finddev on my machine returns a "nflog" as a device. Does anyone
know what this is?
Bill
Back to comp.os.linux.networking | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
read IP header "Bill Cunningham" <nospam@nspam.invalid> - 2017-02-14 13:49 -0500
Re: read IP header Rick Jones <rick.jones2@hpe.com> - 2017-02-14 21:19 +0000
Re: read IP header Jorgen Grahn <grahn+nntp@snipabacken.se> - 2017-02-14 21:52 +0000
Re: read IP header "Bill Cunningham" <nospam@nspam.invalid> - 2017-02-15 13:34 -0500
Re: read IP header Jorgen Grahn <grahn+nntp@snipabacken.se> - 2017-02-15 19:12 +0000
Re: read IP header "Bill Cunningham" <nospam@nspam.invalid> - 2017-02-15 14:54 -0500
Re: read IP header Jorgen Grahn <grahn+nntp@snipabacken.se> - 2017-02-16 07:04 +0000
csiph-web