All of lore.kernel.org
 help / color / mirror / Atom feed
From: ro0ot <ro0ot@phreaker.net>
To: bridge@lists.osdl.org
Subject: Re: [Bridge] Bridging Firewall with Kernel 2.6 failed
Date: Wed, 14 Dec 2005 02:29:11 +0800	[thread overview]
Message-ID: <439F12F7.2050407@phreaker.net> (raw)
In-Reply-To: <1134296796.611.66.camel@gadi>

I am using kernel 2.6.14.3, iptables 1.3.4 and bridge-utils 1.0.6

I did flag the "802.1d Ethernet Bridging" in Networking 
support/Networking options


Gladiston Justini - JustiSecure wrote:

> Mr. ro0ot,
>
>     You need:
>         1. Kernel 2.6.xx
>         2. Iptables 1.3.xx
>         3. brctl-util
>
> In kernel configuration, do you flag  '802.1d Ethernet Bridging' in  
> Network support/Networking options
>
>
> Sorry my english.
> :)
> Gadi
>
>
>
>
>
> On Sun, 2005-12-11 at 15:59 +0800, ro0ot wrote:
>
>>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,
>>    
>>
>
>
>>
>>
>>_______________________________________________
>>Bridge mailing list
>>Bridge@lists.osdl.org <mailto:Bridge@lists.osdl.org>
>>https://lists.osdl.org/mailman/listinfo/bridge
>>    
>>




  parent reply	other threads:[~2005-12-13 18:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-11  7:59 Bridging Firewall with Kernel 2.6 failed ro0ot
2005-12-11  7:59 ` [Bridge] " ro0ot
2005-12-11 18:55 ` T'Krin
     [not found] ` <1134296796.611.66.camel@gadi>
2005-12-13 18:29   ` ro0ot [this message]
2005-12-16 15:03 ` Kashif Ali Bukhari
2005-12-16 15:03   ` [Bridge] " Kashif Ali Bukhari
2005-12-20 17:19   ` ro0ot

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=439F12F7.2050407@phreaker.net \
    --to=ro0ot@phreaker.net \
    --cc=bridge@lists.osdl.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.