All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Francisco Medina Lopez" <paco@segob.gob.mx>
To: "Andrew J. Meader" <ameader@corp.lcom.net>
Cc: netfilter@lists.netfilter.org
Subject: Re: Bridging Firewall
Date: 27 Mar 2003 15:12:12 -0600	[thread overview]
Message-ID: <1048799532.1325.16.camel@nemesis> (raw)
In-Reply-To: <3E835D19.6000309@corp.lcom.net>

you forgot one step, the whole procedure is like this:


brctl addbr br0
brctl addif br0 eth0
brctl addif br0 eth1
ifconfig eth0 0.0.0.0 promisc
ifconfig eth1 0.0.0.0 promisc
ifconfig br0 up             

ip link set eth0 up

ip addr add 172.16.41.211/24 brd + dev br0
ip route add default via 172.16.41.250




On Thu, 2003-03-27 at 14:20, Andrew J. Meader wrote:
> Hi All,
> 
> I am trying to set up a bridging firewall with Red Hat 8.0. I can not 
> get packets to flow from nic to nic.
> 
> Topology:
>        
>              br0
>                 |
>                 |
>         ------
>         |                |
>     eth1          eth2
> 
> Here are the steps I have taken to setup the bridge:
> 
> ifdown eth1
> ifdown eth2
> 
> ifconfig eth1 0.0.0.0
> ifconfig eth2 0.0.0.0
> 
> brctl addbr br0
> 
> brctl addif br0 eth1
> brctl addif br0 eth2
> 
> ifconfig br0 0.0.0.0
> 
> When I ifconfig br0 I can see that rx packets are incrementing but tx 
> packets are not incrementing. Are there any known issues with RH8.0 and 
> brdiging? Thanks for helping.
> 
> Andy
> 
> 




  reply	other threads:[~2003-03-27 21:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-27 20:20 Bridging Firewall Andrew J. Meader
2003-03-27 21:12 ` Francisco Medina Lopez [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-05 22:01 Tim Roberts
2003-02-06  0:07 ` Joel Newkirk

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=1048799532.1325.16.camel@nemesis \
    --to=paco@segob.gob.mx \
    --cc=ameader@corp.lcom.net \
    --cc=netfilter@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.