From: Stephen Hemminger <shemminger@osdl.org>
To: Sun Zongjun-E5739C <E5739C@motorola.com>
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] How to bridge a eth0 and usb0 device
Date: Fri, 27 Oct 2006 11:21:41 -0700 [thread overview]
Message-ID: <20061027112141.7b271a0e@freekitty> (raw)
In-Reply-To: <565F40B9893580489B94B8D324460AF4E291BF@zmy16exm63.ds.mot.com>
On Tue, 24 Oct 2006 10:46:20 +0800
"Sun Zongjun-E5739C" <E5739C@motorola.com> wrote:
>
> Hi
>
> I intent to use brctl to bridge two devices on linux box. One is eth0,
> the other is USB net which is recognized as usb0 by linux box.
>
> Then I run following command
>
> # ifconfig eth0 down
> # ifconfig usb0 down
> # brctt addbr ipbr
> # brctl addif ipbr eth0
> # brctl addif ipbr usb0
>
> # ifconfig eth0 up
> # ifconfig eth0 0.0.0.0
> # ifconfig usb0 up
> # ifconfig usb0 0.0.0.0
>
> # ifconfig ipv6 up
>
> eth0 usb0
> 192.168.16.2
> Box1<----------------> Linux bridge <----------------------> Box
>
> Then I connet another device into the eth0 interface of bridge. Its ip
> address is 192.168.16.1, the device on the othe end of usb lan is
> 192.168.16.2
>
> When I ping 192.168.16.2 from 192.168.16.1. The tcpdump on bridge is
> message of ARP "who has 192.168.16.2 tell 192.168.16.1", but I neve see
> the ARP reply why?
>
> Thanks
> Best Regards
>
You forgot to bring ipbr up in your example?
Unless ipv6 is a typo for ipbr
Are the mac addresses being picked up?
You probably want to set forwarding delay to 0 (or wait 30 secs)
before testing.
# brctl setfd ipbr 0
--
Stephen Hemminger <shemminger@osdl.org>
prev parent reply other threads:[~2006-10-27 18:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 2:46 [Bridge] How to bridge a eth0 and usb0 device Sun Zongjun-E5739C
2006-10-27 18:21 ` Stephen Hemminger [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=20061027112141.7b271a0e@freekitty \
--to=shemminger@osdl.org \
--cc=E5739C@motorola.com \
--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.