Ethernet Bridge development
 help / color / mirror / Atom feed
From: "Fernando Rodriguez" <frod@aitelecom.net>
To: kevin@ouraynet.com
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] Bridge IP not answering
Date: Thu, 1 Mar 2007 14:27:10 -0600	[thread overview]
Message-ID: <001201c75c3f$fd92f470$988086c9@sam> (raw)
In-Reply-To: <4247.204.10.124.3.1172776417.squirrel@squirrel.ouraynet.com>

Do i need to use ebtables to drop the bridge ip into routing chain ?? 

Do u have an example ??

thanks 

-----Mensaje original-----
De: kevin@ouraynet.com [mailto:kevin@ouraynet.com] 
Enviado el: Jueves, 01 de Marzo de 2007 01:14 p.m.
Para: Fernando Rodriguez
Asunto: Re: [Bridge] Bridge IP not answering

Have you used ebtables to drop the bridges IP out of the bridging chain and
into the routing chain?


Kevin


> Hello,
>
> I have set up a bridge with the following script that starts after the 
> network interfaces are started
>
> BRIDGENAME="BRQ"
> GATEWAY="192.168.0.1"
> BRIDGE_IP="192.168.0.122"
> BRIDGE_NETMASK="255.255.255.0"
> STP_ON="yes"
> STP_PRIO="1"
> RETVAL=0
>
> start() {
>         echo "Starting service bridge"
>        ifconfig eth2 promisc up
>         ifconfig eth3 promisc up
>         brctl addbr $BRIDGENAME  ||  return=$rc_failed
>         brctl addif $BRIDGENAME eth2  ||  return=$rc_failed
>         brctl addif $BRIDGENAME eth3  ||  return=$rc_failed
>         ifconfig eth2 0.0.0.0  ||  return=$rc_failed
>         ifconfig eth3 0.0.0.0  ||  return=$rc_failed
>         brctl sethello $BRIDGENAME 1  ||  return=$rc_failed
>         brctl setmaxage $BRIDGENAME 4  ||  return=$rc_failed
>         brctl setfd $BRIDGENAME 4  ||  return=$rc_failed
>         brctl stp $BRIDGENAME $STP_ON
>         brctl setbridgeprio $BRIDGENAME $STP_PRIO
>         ifconfig $BRIDGENAME $BRIDGE_IP netmask $BRIDGE_NETMASK up
>
>         ip route flush cache
>         ip route add default via $GATEWAY
>
> But the problem i have is that i am not able to contact the bridge on 
> its IP
> 192.168.0.122 i am running Centos 4.4 on a 2.6.18 kernel, i have 
> tested this setup on 3 different sets of network cards tg3, b44, 
> via-rhine and in all of them i have the same results no connection, i 
> know the bridge is working otherwise packets couldnt flow on the 
> network, im using bridge utils
> 1.0.4-4
>
> If any one knows what could be wrong??
>
> Or does any one has a script or an example on how they set up their 
> bridge in order to be able to access it via its IP
>
>
> Thanks
>
>
> --
> This message has been scanned for viruses and dangerous content by 
> MailScanner, and is believed to be clean.
>
> _______________________________________________
> Bridge mailing list
> Bridge@lists.osdl.org
> https://lists.osdl.org/mailman/listinfo/bridge
>
>



--
This message has been scanned for viruses and dangerous content by
MailScanner, and is believed to be clean.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


      parent reply	other threads:[~2007-03-01 20:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-01 17:47 [Bridge] Bridge IP not answering Fernando Rodriguez
2007-03-01 18:48 ` Stephen Hemminger
     [not found] ` <4247.204.10.124.3.1172776417.squirrel@squirrel.ouraynet.com>
2007-03-01 20:27   ` Fernando Rodriguez [this message]

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='001201c75c3f$fd92f470$988086c9@sam' \
    --to=frod@aitelecom.net \
    --cc=bridge@lists.osdl.org \
    --cc=kevin@ouraynet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox