All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: tmiller@lisco.com
Cc: bridge@osdl.org
Subject: Re: [Bridge] Bridge works, but how host is limited
Date: Wed, 15 Nov 2006 21:37:40 -0800	[thread overview]
Message-ID: <20061115213740.17f8253f@localhost.localdomain> (raw)
In-Reply-To: <455BBBD2.4060705@lisco.com>

On Wed, 15 Nov 2006 19:16:02 -0600
Tom Miller <tmiller@lisco.com> wrote:

> I've got a bridge up on my Suse 10 box, let's call it the bridge host.
> The 2 NICs are connected, and my main box (Suse 10.1) can print to the
> printer on the other side of the bridge host. Everything pings
> everywhere, i.e. the LAN extends across the bridge as expected. Cool!
> 
> I used the basic configuration:
> 
>    1. ifconfig eth0 0.0.0.0
>    2. ifconfig eth1 0.0.0.0
>    3. brctl addbr mybridge
>    4. brctl addif mybridge eth0
>    5. brctl addif mybridge eth1
> 
> plus:
> 
>     ifconfig mybridge 192.168.100.5 netmask 255.255.255.0
> 
> On the bridge host, I can browse to an Apache-served web page on my main
> box, but cannot browse to the Internet or print on the printer. Wonder
> what is wrong? Any suggestions?
> 
> Is there some way to configure the bridge itself as a network device?
> 
> Thanks
> Tom
> 

You have no default route. You created a static IP entry, but there is no
route to your gateway.  If you use DHCP, then it sets up default route
as well.

      reply	other threads:[~2006-11-16  5:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-16  1:16 [Bridge] Bridge works, but how host is limited Tom Miller
2006-11-16  5:37 ` 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=20061115213740.17f8253f@localhost.localdomain \
    --to=shemminger@osdl.org \
    --cc=bridge@osdl.org \
    --cc=tmiller@lisco.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 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.