All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gary W. Smith" <gary@primeexalia.com>
To: ro0ot <ro0ot@phreaker.net>,
	netfilter@lists.netfilter.org, bridge@lists.osdl.org
Subject: RE: Bridging Firewall with Kernel 2.6 failed
Date: Sun, 11 Dec 2005 01:11:36 -0800	[thread overview]
Message-ID: <57F9959B46E0FA4D8BA88AEDFBE582900B59D2@pxtbenexd01.pxt.primeexalia.com> (raw)

Hi ro0ot, 

Exactly what part of "doesn't work anymore" doesn't work?  Does it not
work when you create the bridge or does it not work after you apply
iptables?  What commands are you running to instantiate the bridge?
What commands do you think are failing?

Gary Wayne Smith

> -----Original Message-----
> From: netfilter-bounces@lists.netfilter.org [mailto:netfilter-
> bounces@lists.netfilter.org] On Behalf Of ro0ot
> Sent: Saturday, December 10, 2005 11:59 PM
> To: netfilter@lists.netfilter.org; bridge@lists.osdl.org
> Subject: Bridging Firewall with Kernel 2.6 failed
> 
> Hi all,
> 
> I have a bridging firewall running fine with kernel 2.4.31 (Slackware
> 10.1) and iptables 1.2.11
> 
> Yesterday I install the new kernel 2.6.14.3 and iptables 1.3.4 but the
> bridging firewall doesn't work anymore.
> 
> Do I need to patch the kernel 2.6 as what I did it for kernel 2.4? Or
> what I have missed?
> 
> Regards,
> ro0ot
> 
> 
> 



WARNING: multiple messages have this Message-ID (diff)
From: "Gary W. Smith" <gary@primeexalia.com>
To: ro0ot <ro0ot@phreaker.net>,
	netfilter@lists.netfilter.org, bridge@lists.osdl.org
Subject: [Bridge] RE: Bridging Firewall with Kernel 2.6 failed
Date: Sun, 11 Dec 2005 01:11:36 -0800	[thread overview]
Message-ID: <57F9959B46E0FA4D8BA88AEDFBE582900B59D2@pxtbenexd01.pxt.primeexalia.com> (raw)

Hi ro0ot, 

Exactly what part of "doesn't work anymore" doesn't work?  Does it not
work when you create the bridge or does it not work after you apply
iptables?  What commands are you running to instantiate the bridge?
What commands do you think are failing?

Gary Wayne Smith

> -----Original Message-----
> From: netfilter-bounces@lists.netfilter.org [mailto:netfilter-
> bounces@lists.netfilter.org] On Behalf Of ro0ot
> Sent: Saturday, December 10, 2005 11:59 PM
> To: netfilter@lists.netfilter.org; bridge@lists.osdl.org
> Subject: Bridging Firewall with Kernel 2.6 failed
> 
> Hi all,
> 
> I have a bridging firewall running fine with kernel 2.4.31 (Slackware
> 10.1) and iptables 1.2.11
> 
> Yesterday I install the new kernel 2.6.14.3 and iptables 1.3.4 but the
> bridging firewall doesn't work anymore.
> 
> Do I need to patch the kernel 2.6 as what I did it for kernel 2.4? Or
> what I have missed?
> 
> Regards,
> ro0ot
> 
> 
> 



             reply	other threads:[~2005-12-11  9:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-11  9:11 Gary W. Smith [this message]
2005-12-11  9:11 ` [Bridge] RE: Bridging Firewall with Kernel 2.6 failed Gary W. Smith
2005-12-13 18:31 ` [Bridge] " ro0ot
  -- strict thread matches above, loose matches on Subject: below --
2005-12-11  7:59 ro0ot
2005-12-16 15:03 ` Kashif Ali Bukhari

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=57F9959B46E0FA4D8BA88AEDFBE582900B59D2@pxtbenexd01.pxt.primeexalia.com \
    --to=gary@primeexalia.com \
    --cc=bridge@lists.osdl.org \
    --cc=netfilter@lists.netfilter.org \
    --cc=ro0ot@phreaker.net \
    /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.