netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andre Tomt <andre@tomt.net>
To: Thomas Graf <tgraf@suug.ch>
Cc: netdev@oss.sgi.com
Subject: Re: unregister_netdevice: waiting for tun6to4 to become free.
Date: Thu, 23 Sep 2004 10:07:25 +0200	[thread overview]
Message-ID: <4152843D.6010204@tomt.net> (raw)
In-Reply-To: <41527796.4010204@tomt.net>

Andre Tomt wrote:
> (CC'ed to netdev)
> 
> <snip>
> 
> I can taste the bug now :-)
> 
> Me and Thomas Graf have been discussing this a bit off-list; so for 
> those on netdev, this is my current setup:
> 
> server A sets up a sit tunnel to server B. server B has a sit tunnel to 
> Provider. All communication between A, B and Provider is going over 
> ethernet on the physical layer.
> 
> server B is the one getting stuck in "waiting for <device> to become 
> free.." when ifdown'ing (ip tunnel del) the interface to Provider.
> 
> 
> If I boot with net.ipv6.conf.default.forward = 1 in sysctl.conf - but 
> then after the boot do echo 1 > /proc/sys/net/ipv6/conf/all/forward (to 
> actually get it running)
> 
> we'll crash and burn when taking down the interface.
> 
> Only setting /proc/sys/net/ipv6/conf/all/forward = 1, but never touch 
> default, it goes down cleanly.
> 
> I have the ipv6/conf/default/forwarding set in sysctl.conf on all the 
> routers, and it seems zebra sets the ipv6/conf/all/forwarding later on.
> 

Possibly important note:

if I set up both conf.all and conf.default (order does not matter) 
before the tunnel devices are created, everything works as expected.

eg. in sysctl.conf:
net.ipv6.conf.default.forwarding=1
net.ipv6.conf.all.forwarding=1

if default is set first, then tunnels created, followed by setting 
"all"; everything breaks down on ifdown.

pretty neat :)

  reply	other threads:[~2004-09-23  8:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-20 21:24 unregister_netdevice: waiting for tun6to4 to become free Pekka Pietikainen
2004-09-21  0:59 ` Jeff Garzik
2004-09-21  6:24   ` Andre Tomt
2004-09-22 12:08     ` David Woodhouse
2004-09-22 18:15       ` David S. Miller
2004-09-23  6:18         ` YOSHIFUJI Hideaki / 吉藤英明
     [not found]     ` <20040921121332.GR31616@rei.reeler.org>
     [not found]       ` <4151E680.80203@tomt.net>
     [not found]         ` <20040922211942.GA1674@postel.suug.ch>
     [not found]           ` <41523670.1090603@tomt.net>
     [not found]             ` <41523EC5.20805@tomt.net>
2004-09-23  7:13               ` Andre Tomt
2004-09-23  8:07                 ` Andre Tomt [this message]
2004-09-23  8:22                   ` YOSHIFUJI Hideaki / 吉藤英明
2004-09-24 19:05                     ` [PATCH/RFC] PATCH: IPV6: Fix multiple leakages (is Re: unregister_netdevice: waiting for tun6to4 to become free.) YOSHIFUJI Hideaki / 吉藤英明
2004-09-24 20:51                       ` Andre Tomt
2004-09-27 19:23                       ` David S. Miller
2004-12-16  0:32                     ` unregister_netdevice: waiting for tun6to4 to become free Pekka Pietikainen

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=4152843D.6010204@tomt.net \
    --to=andre@tomt.net \
    --cc=netdev@oss.sgi.com \
    --cc=tgraf@suug.ch \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).