From: Stephen Hemminger <stephen@networkplumber.org>
To: Udaya Puvvadi <upuvvad1@binghamton.edu>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] NFS connection drops as interface added to bridge
Date: Tue, 7 Jun 2016 18:50:23 -0700 [thread overview]
Message-ID: <20160607185023.03519b4b@xeon-e3> (raw)
In-Reply-To: <CAKWq4gNPD5m_=-WPDZWzS0GOgkyHYtY3yh0wsJJy9+gohiwhtg@mail.gmail.com>
On Tue, 7 Jun 2016 12:20:42 -0400
Udaya Puvvadi <upuvvad1@binghamton.edu> wrote:
> Hi,
>
> I am running PXE boot with Debian Stretch image, with eth2 interface
> bound to kernel for doing NFS mounts.
>
> I am trying to add this interface to the bridge, for network
> communication across virtual interfaces, however the NFS drops
> connections as soon as I add the interface.
>
> Can you please help me on how to do the NFS mount's over a bridge connection ?
>
There are two possible issues:
1. When an interface is part of the bridge, you must not try and use the interface
directly. I.e once eth2 is part of br0, don't use eth2 again. Most importantly
never assign an IP address to the interface. Many people doing this kind of thing
end up reading the IP address of the interface (eth2), then removing all addresses
from the interface (eth2) before assigning it to the bridge, then apply the IP address
back to the bridge device.
2. The bridge device itself has a MAC address for local packets. This MAC address is
based on all the devices in the bridge (by default). Therefore when eth2 is added
to a bridge with other devices present, the MAC address for locally sent packets
will change.
prev parent reply other threads:[~2016-06-08 1:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 16:20 [Bridge] NFS connection drops as interface added to bridge Udaya Puvvadi
2016-06-08 1:50 ` 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=20160607185023.03519b4b@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=bridge@lists.linux-foundation.org \
--cc=upuvvad1@binghamton.edu \
/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.