From: Cody Tubbs <tubbs@wispdirect.com>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: ipv4options still broken (posted prev w/ no reply)...
Date: Wed, 31 May 2006 10:45:09 -0700 [thread overview]
Message-ID: <1149097509.6167.9.camel@mbox> (raw)
In-Reply-To: <447DA068.1090507@trash.net>
What about in a bridged firewall situation, you're saying Linux will
strip these ip options out while forwarding? automatically? Is this
something that can be turned on or off?
but oh wait, I forgot...
Why does tcpdump show these ip options still attached even when not
forwarding? :) (latest kernel) heh++
On the contrary, you simply asked me who still supports these ip options
and I gave you a minimal list, thus if giving you an answer is annoying,
this thread must be an act of pissing in the wind.
-Cody Tubbs
On Wed, 2006-05-31 at 15:55 +0200, Patrick McHardy wrote:
> Patrick Schaaf wrote:
> > On Wed, May 31, 2006 at 01:46:07AM +0200, Patrick McHardy wrote:
> >
> > Patrick, at the risk of annoying you some more: the attitude you showed
> > in this thread, is very annoying in itself. While your work on netfilter
> > is really deeply appreciated, slight-of-hand security evaluations like
> > you showed here, are not.
> >
> > Maybe you just need to get some more sleep. I hope so.
>
> I don't like beeing lectured. Linux drops all source route
> options anyway, so this entire discussion is absolutely
> pointless.
>
next prev parent reply other threads:[~2006-05-31 17:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1149033568.27117@www.broadwayinternet.com>
2006-05-30 23:46 ` ipv4options still broken (posted prev w/ no reply) Patrick McHardy
2006-05-31 4:54 ` Patrick Schaaf
2006-05-31 13:55 ` Patrick McHardy
2006-05-31 17:45 ` Cody Tubbs [this message]
2006-05-31 18:39 ` Patrick McHardy
2006-05-31 19:02 ` Cody Tubbs
2006-06-01 3:25 ` Patrick McHardy
2006-05-30 17:47 Cody Tubbs
2006-05-30 19:22 ` Patrick McHardy
2006-05-30 21:16 ` Cody Tubbs
2006-05-30 23:05 ` Patrick McHardy
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=1149097509.6167.9.camel@mbox \
--to=tubbs@wispdirect.com \
--cc=kaber@trash.net \
--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.