Do i need to use ebtables to drop the bridge ip into routing chain ?? Do u have an example ?? thanks -----Mensaje original----- De: kevin@xxxxxxxxxxxx [mailto:kevin@xxxxxxxxxxxx] Enviado el: Jueves, 01 de Marzo de 2007 01:14 p.m. Para: Fernando Rodriguez Asunto: Re: 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@xxxxxxxxxxxxxx > 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. _______________________________________________ Bridge mailing list Bridge@xxxxxxxxxxxxxx https://lists.osdl.org/mailman/listinfo/bridge
