All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sylvain Rochet <gradator@gradator.net>
To: Willy Tarreau <w@1wt.eu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 2.4.37.9 destroying an Ethernet interface with permanent NUD leaves the kernels with undestroyable interfaces when ATM is compiled in
Date: Wed, 21 Apr 2010 16:07:50 +0200	[thread overview]
Message-ID: <20100421140750.GA29137@gradator.net> (raw)
In-Reply-To: <20100420051125.GB7798@1wt.eu>

[-- Attachment #1: Type: text/plain, Size: 1860 bytes --]

Hi Willy,

On Tue, Apr 20, 2010 at 07:11:25AM +0200, Willy Tarreau wrote:
> Hi Sylvain,
> 
> indeed, you've hit a real bug. It reminds me of the sad days I
> was forced to use IPoA over a USB modem to access the net. The
> tiniest config error required a reboot to fix it :-/
> 
> Your fix looks right at first glance, but I'll review it deeper
> before merging it, though it should be OK since 2.6 is similar.
> 
> BTW, is there any reason why you're stuck on 2.4 ? Are you using
> some vendor-specific drivers which are not in 2.6, did you not
> have the time to upgrade yet, or did you not find a long enable
> support for 2.6 releases ? Or anything else ?
> 
> I'm asking because whatever keeps users in 2.4 should be addressed
> one way or another (probably via some doc to add in 2.4 BTW).

Well, if that were only me, this would be a 2.6 kernel, actually one of 
our new xDSL collect provider use Linux routers on operator customer 
edge and they are still using 2.4 kernels. This is going to change 
soon, but well, I discovered that there was this bug, I could not left 
it uncorrected, even on the 2.4 kernel ;-)

I am not sure if collect routers are also used elsewhere than in France. 
This is the server where PPP/L2TP tunnels or VP/VC ATM are ended, so 
that all operators use the same national networks and simply use PPP 
tunnels from xDSL customer to Internet operator router, using Radius, 
PPPoE, PPPoA, L2TP, and PPP protocol to do the authentication, find and 
reach the endpoint.

By the way, the patch also fix another issue, when an interface with 
dynamic NUDs is set to link down sate, you have to wait that NUDs 
entries expire before setting the interface back to link up state. This 
is obvious because dynamic NUDs entries are not cleared when 
neigh_ifdown() is called.

Regards,
Sylvain

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2010-04-21 14:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-07 20:23 PROBLEM: 2.4.37.9 destroying an Ethernet interface with permanent NUD leaves the kernels with undestroyable interfaces when ATM is compiled in Sylvain Rochet
2010-04-08 13:47 ` Sylvain Rochet
2010-04-20  5:11   ` Willy Tarreau
2010-04-21 14:07     ` Sylvain Rochet [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=20100421140750.GA29137@gradator.net \
    --to=gradator@gradator.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=w@1wt.eu \
    /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.