From: stimits@comcast.net
To: bridge@lists.linux-foundation.org
Subject: [Bridge] Bridge "address x.x.x.x" Configuration
Date: Thu, 31 Jul 2014 20:51:06 +0000 (UTC) [thread overview]
Message-ID: <1645433484.36982455.1406839866983.JavaMail.root@comcast.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1380 bytes --]
Hi,
Long ago I used a linux bridge with an IP address bound specifically to one of the two NICs of the bridge. Currently, it seems as though the address configuration cannot be explicitly assigned to just one physical port (I have eth0 and eth1, wanted it bound specifically and only to eth0). I'm hoping this is just a quirk of how my Ubuntu 14.04 LTS is built, and not a limitation of the bridging software. Because I'm binding ports to the bridge, but not binding addresses to ports, I have to bind an address to the bridge as a whole. Using ifconfig after the bridge is up to bind an address directly to a port (independent of the bridge) fails.
One of my concerns is that I want the NIC on the "unfriendly" side to have no response to any address. The other concern is that with the current setup, I have a 10:1 latency increase problem using the address assigned, compared to the NIC just having an IP address without bridging. The latency issues are so bad that there is no use in using this for outside world connections. The system itself is ARMv7 embedded, and the two NICs are all that can ever be connected. No hardware flexibility exists for a third NIC to offload this function. Perhaps specifically binding the IP address to one NIC would remove the latency issue? If not, I have to debug and profile the kernel module on ARMv7, which will not be easy.
Thanks
[-- Attachment #2: Type: text/html, Size: 1472 bytes --]
reply other threads:[~2014-07-31 20:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1645433484.36982455.1406839866983.JavaMail.root@comcast.net \
--to=stimits@comcast.net \
--cc=bridge@lists.linux-foundation.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.