mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Christopher Friesen" <cfriesen@nortelnetworks.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RFC: ethernet links should remember routes the same as addresses
Date: Thu, 29 Nov 2001 15:59:52 -0500	[thread overview]
Message-ID: <3C06A1C8.C133F725@nortelnetworks.com> (raw)
In-Reply-To: <3C068ED1.D5E2F536@nortelnetworks.com.suse.lists.linux.kernel> <p73r8qhqrmi.fsf@amdsim2.suse.de>

Andi Kleen wrote:
> 
> "Christopher Friesen" <cfriesen@nortelnetworks.com> writes:
> > Currently, if I run "ip link set dev ethX down", all routes associated with that
> > IP address in the additional routing tables are lost.  This is somewhat
> > understandable, as the addresses are not actually available anymore.  However,
> > the addresses are still visible associated with the link.  Then I run "ip link
> > set dev ethX up".  The route in the main routing table comes back, but none of
> > the other routes do.  Somehow, all of those additional routes must be re-added.
> 
> ip route list dev device > BACKUP
> 
> ...
> 
> while read i ; do ip route add $i ; done < BACKUP

Unfortunately, this seems to only list the routes in the main routing table, and
these routes are recreated automatically when I bring the link back up.

The problem is that I have routes in multiple other routing tables, and they
don't show up in this command.  I assume I'd have to run a similar command for
each routing table, which is kind of a pain.

If the driver re-init is totally separate from the routing code, is there any
real reason why shutting down the driver *should* remove all routes to that
device?  Maybe the simplest solution would be a new ioctl that would be a link
*reset*...just down/up the link without affecting anything else....


-- 
Chris Friesen                    | MailStop: 043/33/F10  
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@nortelnetworks.com

  reply	other threads:[~2001-11-29 20:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3C068ED1.D5E2F536@nortelnetworks.com.suse.lists.linux.kernel>
2001-11-29 19:55 ` Andi Kleen
2001-11-29 20:59   ` Christopher Friesen [this message]
2001-11-29 21:03     ` Ben Greear
2001-11-29 21:18       ` Christopher Friesen
2001-11-29 21:18     ` Andi Kleen
2001-11-29 23:04 Julian Anastasov
     [not found] <9u64q7$46m$1@phoenix.clouddancer.com>
2001-11-29 19:38 ` Christopher Friesen
2001-11-29 20:58   ` Colonel

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=3C06A1C8.C133F725@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=ak@suse.de \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®