From: Steven M Campbell <Netfilter@SCampbell.net>
To: Jason Opperisano <opie@817west.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: What is the diference between ipfw of *bsd and netfilter of linux?
Date: Tue, 05 Oct 2004 15:21:12 -0400 [thread overview]
Message-ID: <4162F428.3000903@SCampbell.net> (raw)
In-Reply-To: <1097000655.4415.4.camel@wolfpack.ljm.dom>
Jason Opperisano wrote:
>On Tue, 2004-10-05 at 13:23, Damjan wrote:
>
>
>>However I agree with you that netfilter is easier to use and has more
>>capabilities, I still can't beleive that netfilter (iptables actually)
>>doesn't have a way to identify rules uniquely (via an ID). So simple
>>feaure, so powerfull, and still iptables doesn't have this.
>>
>>And no, linenumbers don't identify rules uniquely, they can change at
>>any moment.
>>
>>
>
>check out the comment patch from POM.
>
>-j
>
>
>
I feel obliged to add that wrongly configured proxy-arp devices can
bring havoc onto a network. I get a few cases a year where some network
devices had proxy-arp left on (we typically disable it on most devices)
and a routing error was made, the result in many devices is that the
device will start answering for ip addresses it has no actually ability
to communicate with thereby effectively knocking that device off the
net. Just a warning that it can be nasty.
next prev parent reply other threads:[~2004-10-05 19:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 20:06 What is the diference between ipfw of *bsd and netfilter of linux? Carlos Mario Mora (c4y0)
2004-10-04 20:32 ` Aleksandar Milivojevic
2004-10-05 16:58 ` Jose Maria Lopez
2004-10-05 17:23 ` Damjan
2004-10-05 18:24 ` Jason Opperisano
2004-10-05 19:21 ` Steven M Campbell [this message]
2004-10-22 2:16 ` Damjan
-- strict thread matches above, loose matches on Subject: below --
2004-10-04 20:29 Daniel Chemko
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=4162F428.3000903@SCampbell.net \
--to=netfilter@scampbell.net \
--cc=netfilter@lists.netfilter.org \
--cc=opie@817west.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 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.