From: Alex Zeffertt <ajz@cambridgebroadband.com>
To: Chris U <chris.uyehara@gmail.com>
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] Bridge Woes...
Date: Thu, 05 Oct 2006 09:18:29 +0100 [thread overview]
Message-ID: <4524BFD5.4080203@cambridgebroadband.com> (raw)
In-Reply-To: <4c9f8dc30610042120o3089cbf6yaaa00728b271953f@mail.gmail.com>
>
> Now for the PROBLEM! The bridge can access IP's outside of the subnet
> via eth0 of the bridge, ie - pinging 128.171.1.1 <http://128.171.1.1>,
> 128.171.3.13 <http://128.171.3.13>, 64.233.167.99
> <http://64.233.167.99>. The laptop cannot ping the previously listed
> IPs. The only thing the laptop can ping is 128.171.103.11
Hi Chris,
I have seen a problem with some ethernet drivers where the interface
does not go into promiscuous mode automatically as the interface is added
to a bridge.
It's worth trying to do this manually with "ifconfig eth0 promisc" and
likewise for eth1, then seeing if things work.
A few ethernet drivers don't support promiscuous mode at all. But it
definitely looks to me the way you describe the problem that the devices
on the bridge are not in promiscuous mode.
Regards,
Alex
next prev parent reply other threads:[~2006-10-05 8:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 4:20 [Bridge] Bridge Woes Chris U
2006-10-05 4:58 ` Jothis T.V
2006-10-05 7:59 ` Chris U
2006-10-05 8:18 ` Alex Zeffertt [this message]
2006-10-05 8:39 ` Chris U
2006-10-05 9:05 ` Jothis T.V
2006-10-05 9:05 ` Alex Zeffertt
2006-10-05 14:39 ` Stephen Hemminger
2006-10-05 19:07 ` Chris U
2006-10-05 19:33 ` Gergely Madarasz
2006-10-05 19:43 ` Chris U
-- strict thread matches above, loose matches on Subject: below --
2006-10-05 9:26 Skept
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=4524BFD5.4080203@cambridgebroadband.com \
--to=ajz@cambridgebroadband.com \
--cc=bridge@lists.osdl.org \
--cc=chris.uyehara@gmail.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.