the way it
uses the network stack.
l2tp runs over UDP packets (port 1701 (like the starship
enterprise))
I have no idea why they want raw packets.
Ther's a sendarp() routine which uses PF_PACKET to directly
access the
netwo
stack.
>>>>
>>>>
>>> l2tp runs over UDP packets (port 1701 (like the starship enterprise))
>>> I have no idea why they want raw packets.
>>>
>>>
>>>
>> Ther's a sendarp() routine which uses PF_PACKET to directly access the
rewrite the way it
uses the network stack.
l2tp runs over UDP packets (port 1701 (like the starship enterprise))
I have no idea why they want raw packets.
Ther's a sendarp() routine which uses PF_PACKET to directly access the
network driver and bypass the stack. Lazy Linuxers who
ay it
> > uses the network stack.
> l2tp runs over UDP packets (port 1701 (like the starship enterprise))
> I have no idea why they want raw packets.
>
Ther's a sendarp() routine which uses PF_PACKET to directly access the
network driver and bypass the stack. Lazy Linuxers who
eases) a new
protocol family has been introduced, named PF_PACKET. This family
allows an application to send and receive packets dealing
directly with the network card driver, thus avoiding the usual
protocol stack-handling (e.g., IP/TCP or IP/UDP processing). That
is, any packet sent throug
duced, named PF_PACKET. This
family allows an application to send and receive packets dealing
directly with the network card driver, thus avoiding the usual
protocol stack-handling (e.g., IP/TCP or IP/UDP processing).
That is, any packet sent through the socket will be directly
passed to the Eth
Elischer wrote:
On 2/10/11 11:22 PM, Da Rock wrote:
"In recent versions of the Linux kernel (post-2.0
releases) a new protocol family has been introduced,
named PF_PACKET. This family allows an application to
send and receive packets de
11:22 PM, Da Rock wrote:
"In recent versions of the Linux kernel (post-2.0
releases) a new protocol family has been introduced,
named PF_PACKET. This family allows an application to
send and receive packets dealing directly with the
On 02/12/11 02:37, Julian Elischer wrote:
On 2/11/11 1:36 AM, Da Rock wrote:
On 02/11/11 18:17, Julian Elischer wrote:
On 2/10/11 11:22 PM, Da Rock wrote:
"In recent versions of the Linux kernel (post-2.0 releases) a new
protocol family has been introduced, named PF_PACKET. This f
quot;In recent versions of the Linux kernel (post-2.0
releases) a new protocol family has been introduced,
named PF_PACKET. This family allows an application to
send and receive packets dealing directly with the
network card driver, thus avoiding the
On 2/11/11 1:36 AM, Da Rock wrote:
On 02/11/11 18:17, Julian Elischer wrote:
On 2/10/11 11:22 PM, Da Rock wrote:
"In recent versions of the Linux kernel (post-2.0 releases) a new
protocol family has been introduced, named PF_PACKET. This family
allows an application to send and re
rnel (post-2.0
releases) a new protocol family has been introduced, named
PF_PACKET. This family allows an application to send and
receive packets dealing directly with the network card
driver, thus avoiding the usual protocol stack-handling
gt;>> protocol family has been introduced, named PF_PACKET. This family allows an
>>> application to send and receive packets dealing directly with the network
>>> card driver, thus avoiding the usual protocol stack-handling (e.g., IP/TCP
>>> or IP/UDP processing). That
On 02/11/11 18:17, Julian Elischer wrote:
On 2/10/11 11:22 PM, Da Rock wrote:
"In recent versions of the Linux kernel (post-2.0 releases) a new
protocol family has been introduced, named PF_PACKET. This family
allows an application to send and receive packets dealing directly
with the ne
On Fri, Feb 11, 2011 at 9:22 AM, Da Rock <
freebsd-hack...@herveybayaustralia.com.au> wrote:
> "In recent versions of the Linux kernel (post-2.0 releases) a new protocol
> family has been introduced, named PF_PACKET. This family allows an
> application to send and receive pack
On 2/10/11 11:22 PM, Da Rock wrote:
"In recent versions of the Linux kernel (post-2.0 releases) a new
protocol family has been introduced, named PF_PACKET. This family
allows an application to send and receive packets dealing directly
with the network card driver, thus avoiding the
"In recent versions of the Linux kernel (post-2.0 releases) a new
protocol family has been introduced, named PF_PACKET. This family allows
an application to send and receive packets dealing directly with the
network card driver, thus avoiding the usual protocol stack-handling
(e.g., IP/T
On Fri, Jun 25, 2004 at 01:24:53PM -0700, Lev Walkin wrote:
> Ivan Voras wrote:
> >Lev Walkin wrote:
> >
> >>Ivan Voras wrote:
> >>
> >>>I'm trying to port open1x xsupplicant, and it uses PF_PACKET to get
> >>>relevant packets (of app
check out netgraph and the ng_etf node
man ng_etf
On Fri, 25 Jun 2004, Ivan Voras wrote:
> I'm trying to port open1x xsupplicant, and it uses PF_PACKET to get
> relevant packets (of appropriate ethernet type). I looked around in
> /usr/include and can't find the su
Ivan Voras wrote:
Lev Walkin wrote:
Ivan Voras wrote:
I'm trying to port open1x xsupplicant, and it uses PF_PACKET to get
relevant packets (of appropriate ethernet type). I looked around in
/usr/include and can't find the support, at least not under that and
similar names. Is there s
Lev Walkin wrote:
Ivan Voras wrote:
I'm trying to port open1x xsupplicant, and it uses PF_PACKET to get
relevant packets (of appropriate ethernet type). I looked around in
/usr/include and can't find the support, at least not under that and
similar names. Is there support for it in Fr
Ivan Voras wrote:
I'm trying to port open1x xsupplicant, and it uses PF_PACKET to get
relevant packets (of appropriate ethernet type). I looked around in
/usr/include and can't find the support, at least not under that and
similar names. Is there support for it in FreeBSD?
(I on
I'm trying to port open1x xsupplicant, and it uses PF_PACKET to get
relevant packets (of appropriate ethernet type). I looked around in
/usr/include and can't find the support, at least not under that and
similar names. Is there support for it in FreeBSD?
(I only need to catch &a
23 matches
Mail list logo
