All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Engelhardt <jengelh-9+2X+4sQBs8@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
	<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: raw.7 missing ETH_P_ALL hack
Date: Sun, 29 Jul 2012 16:14:51 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.01.1207291614330.13011@frira.zrqbmnf.qr> (raw)
In-Reply-To: <CAKgNAki70auDaFRkk430FNNz3icNEMzr+JOOq=trGigvX_7V0A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Sunday 2012-07-29 06:32, Michael Kerrisk (man-pages) wrote:

>On Thu, Oct 22, 2009 at 1:56 PM, Jan Engelhardt <jengelh-nopoi9nDyk+ELgA04lAiVw@public.gmane.org> wrote:
>> Hi,
>>
>>
>> some codes use a raw socket with ETH_P_ALL, such as
>> http://code.google.com/p/libdnet/source/browse/trunk/src/eth-linux.c
>> However this is not documented yet in raw(7).
>
>Does packet(7) not give you what you are looking for?

Right.. eth-linux.c happens to use AF_PACKET (at least now, two years 
later ;-)
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2012-07-29 14:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-22 11:56 raw.7 missing ETH_P_ALL hack Jan Engelhardt
     [not found] ` <alpine.LSU.2.00.0910221353080.21589-SHaQjdQMGhDmsUXKMKRlFA@public.gmane.org>
2012-07-29  4:32   ` Michael Kerrisk (man-pages)
     [not found]     ` <CAKgNAki70auDaFRkk430FNNz3icNEMzr+JOOq=trGigvX_7V0A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-07-29 14:14       ` Jan Engelhardt [this message]

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=alpine.LNX.2.01.1207291614330.13011@frira.zrqbmnf.qr \
    --to=jengelh-9+2x+4sqbs8@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.