From: David Poole <davep@portsmith.com>
To: netfilter-devel@lists.netfilter.org
Subject: Re: Raw Sockets and Netfiter
Date: 25 Mar 2003 07:30:58 -0700 [thread overview]
Message-ID: <1048602658.14036.4.camel@athlon> (raw)
In-Reply-To: <001701c2f29d$20afe1e0$6b01a8c0@COURVOISIER>
On Tue, 2003-03-25 at 00:06, Ethan Dameron wrote:
> If I have a an IP datagram in userspace and I send it via a raw socket
> created with socket(PF_INET, SOCK_RAW, IPPROTO_RAW) using the send()
> system call, will this packet traverse the netfilter chains? If it
> does not traverse the firewall, how can I make it do so?
> Version: 6.0.463 / Virus Database: 262 - Release Date: 03/17/2003
What are you trying to do? Not that I have a solution, but I'm running
into the same problem.
The DHCP client uses PF_PACKET which bypasses the firewall.
Consequently, I can't firewall off certain machines. I've been fiddling
with -j QUEUE and running a user-space DHCP client but the reinjected
packets are going I know not where.
Also, with PF_PACKET, the DHCP client will receive all unicast and
broadcast packets. On a busy network and a slow system (our embedded
Linux product), the client gets flooded.
--
David Poole <davep@portsmith.com>
Portsmith http://www.portsmith.com
960 Broadway Avenue, Suite 300
Boise, ID 83706
208-395-1300 x241
next prev parent reply other threads:[~2003-03-25 14:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 7:06 Raw Sockets and Netfiter Ethan Dameron
2003-03-25 7:25 ` Patrick Schaaf
2003-03-25 8:05 ` Patrick McHardy
2003-03-25 8:12 ` Patrick Schaaf
2003-03-25 9:11 ` Patrick McHardy
2003-03-26 15:32 ` Harald Welte
2003-03-26 16:13 ` David Poole
2003-03-25 14:30 ` David Poole [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-16 16:12 Albert López
2014-01-16 16:53 ` Phil Oester
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=1048602658.14036.4.camel@athlon \
--to=davep@portsmith.com \
--cc=netfilter-devel@lists.netfilter.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.