[Bridge] Bridge problem

[Bridge] Bridge problem

[Javier Valencia]

I'm getting problems with my bridge (linux 2.6.9, eth0 = via-rhine, eth1 = 8139too).
The problem is that eth1 links up and down intermitently (between 1-2 minutes).

What can i do?

Thanks

Re: [Bridge] Bridge problem

[Stephen Hemminger]

On Mon, 15 Nov 2004 18:58:06 +0000
Javier Valencia <jvalencia@log01.org> wrote:

> I'm getting problems with my bridge (linux 2.6.9, eth0 = via-rhine, eth1 = 8139too).
> The problem is that eth1 links up and down intermitently (between 1-2 minutes).
> 
> What can i do?
> 
> Thanks
> 

You could turn on debugging in the 8139too driver and add additional
instrumentation to see why it thinks it loses carrier. Also, do the
obvious stuff like check the cable and what is connected to (router, hub, switch, 
DSL modem, ...). Maybe there is a duplex or speed mismatch?

[Bridge] Bridge problem

[Seann Jenner]

[-- Attachment #1: Type: text/plain, Size: 361 bytes --]

Hello,
I just installed Ubuntu 6.10 and everything worked fine and I was able to
access the internet, I loaded bridge utils and configured a bridge and set
the bridge as a DHCP client, it all went ok, except I was no longer able to
access the internet. Yet I had the exact same configuration working on
Ubuntu 6.06 yesterday, any ideas?
Thank you for your time

[-- Attachment #2: Type: text/html, Size: 372 bytes --]

[Bridge] bridge problem

[saravanan chanemouganandam]

Hi,

I am a newbie to use the bridge utils and after some serious tests I am 
posting this issue. Actually, I am fascing packet forwarding problem in the 
following network setup under linux 2.6.16. The 2.6.16 kernel is also 
configured to include 802.1d Ethernet bridging, Network packet filtering, IP 
netfilter configuration and Bridge netfilter configuration.

The target ARM board is made to act as a bridge between the Host and the 
Router as shown below.

10.1.111.3 Host(eth0)<---->{ eth0 bridge(10.1.111.1) eth1 }<--->Router( 
10.1.111.254)

On the target board

ifconfig eth0 0.0.0.0
ifconfig eth1 0.0.0.0
brctl addbr br0
brctl addif br0 eth0
brctl addif br0 eth1
ifconfig br0 10.1.111.1 netmask 255.255.255.0 up
echo 1 > /proc/sys/net/ipv4/ip_forward

are configured. The problem is that, I can't ping the Router from the Host. 
But from the bridge, I can ping Router and Host. The "arp reply" from the 
Router is not reaching the Host as there's a problem in the bridge 
(bridge-utils 1.2) interface.

I have cross checked the kernel configuration to include all the packet 
forwarding and bridging. But still panic.

Can any one please precise what could cause this packet forward problem ?

Thanks
Sara

_________________________________________________________________
Gossips, movie reviews, photogallery and more 
http://content.msn.co.in/Entertainment/Default

Re: [Bridge] bridge problem

[Jan Engelhardt]

On Feb 15 2007 22:06, saravanan chanemouganandam wrote:
>
> ifconfig eth0 0.0.0.0
> ifconfig eth1 0.0.0.0

That's a no-op. What you need is `ip l s eth0 up` (same for eth1)

> are configured. The problem is that, I can't ping the Router from the Host. But

brctl sethello br0 1



Jan
-- 
ft: http://freshmeat.net/p/chaostables/

Re: [Bridge] bridge problem

[kevin]

> On the target board
>
> ifconfig eth0 0.0.0.0
> ifconfig eth1 0.0.0.0
> brctl addbr br0
> brctl addif br0 eth0
> brctl addif br0 eth1
> ifconfig br0 10.1.111.1 netmask 255.255.255.0 up
> echo 1 > /proc/sys/net/ipv4/ip_forward

Bridging works transparently and is not routing.

You will not need ip_forwarding set, nor and ip in the same subnet.

forget setting the ip_forward, just bring up your bridge with:

ifconfig br0 0.0.0.0 up

If you have everything plugged in properly, and two ips in the same
subnet on either side, they will start pinging.

As mentioned on this list many times prior it does take 30 seconds for
the forwarding to take place unless you set it to 0 with:

brctl setfd br0 0

Hope that helps,
Kevin Karsh
Ouraynet

[Bridge] bridge problem

[Paolo NOTARI]

[-- Attachment #1: Type: text/plain, Size: 424 bytes --]

Hello,

I have these two card that I'm trying to use in a bridge :

nVidia Corporation MCP67 Ethernet (rev a2)
Davicom Semiconductor, Inc. 21x4x DEC-Tulip compatible 10/100 Ethernet 
(rev 31)

Bridge works if nvidia is the LAN side and Davicom on WAN side, but no 
way to get bridge working if nvidia is on LAN and Davicom on WAN -

Driver for Davicom is dmfe; with driver Tulip interface isn't even added 
to bridge

Paolo

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3484 bytes --]

Re: [Bridge] bridge problem

[richardvoigt]

[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]

On Tue, Jun 16, 2009 at 6:04 PM, Paolo NOTARI <paolo_notari@vodafone.it>wrote:

> Hello,
>
> I have these two card that I'm trying to use in a bridge :
>
> nVidia Corporation MCP67 Ethernet (rev a2)
> Davicom Semiconductor, Inc. 21x4x DEC-Tulip compatible 10/100 Ethernet (rev
> 31)
>
> Bridge works if nvidia is the LAN side and Davicom on WAN side, but no way
> to get bridge working if nvidia is on LAN and Davicom on WAN -


I have no clue what you're talking about.  The bridge logic treats all ports
exactly the same, except when it comes to spanning tree choosing one to shut
down when it detects a link.  Beyond that, your "working" and "not working"
don't seem to be different.

Are you sure you are using bridging, and not routing or NAT?


>
>
> Driver for Davicom is dmfe; with driver Tulip interface isn't even added to
> bridge
>
> Paolo
>
> _______________________________________________
> Bridge mailing list
> Bridge@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/bridge
>

[-- Attachment #2: Type: text/html, Size: 1693 bytes --]

Re: [Bridge] bridge problem

[Stephen Hemminger]

On Wed, 17 Jun 2009 23:26:40 -0500
"richardvoigt@gmail.com" <richardvoigt@gmail.com> wrote:

> On Tue, Jun 16, 2009 at 6:04 PM, Paolo NOTARI <paolo_notari@vodafone.it>wrote:
> 
> > Hello,
> >
> > I have these two card that I'm trying to use in a bridge :
> >
> > nVidia Corporation MCP67 Ethernet (rev a2)
> > Davicom Semiconductor, Inc. 21x4x DEC-Tulip compatible 10/100 Ethernet (rev
> > 31)
> >
> > Bridge works if nvidia is the LAN side and Davicom on WAN side, but no way
> > to get bridge working if nvidia is on LAN and Davicom on WAN -
> 
> 
> I have no clue what you're talking about.  The bridge logic treats all ports
> exactly the same, except when it comes to spanning tree choosing one to shut
> down when it detects a link.  Beyond that, your "working" and "not working"
> don't seem to be different.
> 
> Are you sure you are using bridging, and not routing or NAT?
> 
> 
> >
> >
> > Driver for Davicom is dmfe; with driver Tulip interface isn't even added to
> > bridge
> >
> > Paolo
> >

Maybe one of the drivers (or providers) doesn't do promiscious mode and
expects only a particular MAC address.

-- 

[Bridge] bridge problem

[Metuki Sabhe]

Hello,

When I add interfaces to the bridge *after* I have "tcpdump -n -i br0"
running on the bridge,
my tcpdump don't see any communication. If I kill tcpdump and
re-execute it *after* I added
the interface to the bridge, it works just fine.

The same behavior happens with my DHCP server (which listens only on
my bridge interface);
I need to re-execute (reset) it after I add the interface to the bridge.

Is that normal ?

Why does it happen ?

What should I do ?

It's a little awkward to reset my DHCP server every time I add a new
interface to the bridge..

Thanks,
Sabhe