All of lore.kernel.org
 help / color / mirror / Atom feed
From: "raptor@tvskat.net" <raptor@tvskat.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] iproute-save ?
Date: Fri, 28 Jan 2005 10:19:36 +0000	[thread overview]
Message-ID: <20050128121936.394616d9@bugs> (raw)
In-Reply-To: <20050128091239.102bec97@bugs>

that is the hard part to make it not mess with normal if-up/down scripts
and routes they add...
I have alot of manual routes and rules which are not easy handled
especialy when I add another boxes which also happen to have different routes.....
If I can figure out the format of the default-ip-up/down routes I can
skip them with a regex..
will have to look..


|I think it doesn't sound elegant, routing system strictly depends on 
|availability interfaces, so setting up routes should be done in if-up 
|and if-down script, for example, if you unplug a NIC before booting the 
|computer, do you want the route for that NIC to be set up? And sometimes 
|you may need to bring down a NIC - then the kernel will delete your 
|routes automatically, if you have a nice if-up script, the routes will 
|be recovered when you bring it up. An init.d script can't do it.
|If you still want a init.d script, go ahead and write your own script, 
|it's rather easy to do save states and restore on boot, but I guess you 
|may want things to done right instead of a messy solution.
|
|raptor@tvskat.net wrote:
|
|>Anyone to know iproute-save, iproute-restore like script similar iptables-save/restore ?
|>that stores everytihng routes,rules,tables everything ... 
|>then init.d-script that among other things stores the state on shutdown :") (thats easy then)
|>  
|>
|


-----
http://linuxtoday.com/news_story.php3?ltsn 04-12-08-004-32-OS-BZ-DT-0005
snip> MS Office is popular in the same way as heart disease is the most popular way to die.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2005-01-28 10:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-28  7:12 [LARTC] iproute-save ? raptor
2005-01-28 10:19 ` raptor [this message]
2005-01-31 17:25 ` Vincent Jaussaud

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=20050128121936.394616d9@bugs \
    --to=raptor@tvskat.net \
    --cc=lartc@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.