All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karl Hiramoto <karl@hiramoto.org>
To: netdev@vger.kernel.org
Subject: loosing connections on bridge topology changes
Date: Wed, 13 May 2009 17:13:41 +0200	[thread overview]
Message-ID: <4A0AE3A5.20100@hiramoto.org> (raw)


Hi,

I have a user space application, that puts eth0 into bridge br0.  At 
this moment all connections seem frozen. Telnet, HTTP, and NFS.

For development i have nfs root fs.

There is a ioctl() that does the equivalent of "brctl addif br0 eth0"

That cuts all the connections for a few seconds.

nfs: server 192.168.10.51 not responding, still trying
br0: topology change detected, propagating           
br0: port 1(eth0) entering forwarding state          
nfs: server 192.168.10.51 not responding, still trying
nfs: server 192.168.10.51 OK                         
nfs: server 192.168.10.51 OK  


Then everything is OK..

Is there anyway i can fix this, so my applicaion goes ahead at full speed?


using libnl i tried flushing the ARP cache on all devices, but it didn't 
seem to help.


Thanks
--

Karl.


             reply	other threads:[~2009-05-13 15:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-13 15:13 Karl Hiramoto [this message]
2009-05-13 17:44 ` loosing connections on bridge topology changes Stephen Hemminger

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=4A0AE3A5.20100@hiramoto.org \
    --to=karl@hiramoto.org \
    --cc=netdev@vger.kernel.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.