All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Ovsienko <linux@pilot.org.ua>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Setting an alias as the "default" IP address, or
Date: Tue, 24 Jan 2006 07:16:47 +0000	[thread overview]
Message-ID: <20060124101647.01e16307.linux@pilot.org.ua> (raw)
In-Reply-To: <43D43FD8.1070008@vivitec.com.au>

> Out of curiosity, I have that command currently in rc.local, but is
> there a better place to put it in the redhat startup sequence?
> Normally it'd do in /etc/sysconfig/network but I'm not sure of the
> possibility of putting that sort of thing in there?
There are two ways:
1. create /sbin/ifup-local, which will run 'ip ro add' or 'ip ro
replace'. Your routing table will be adjusted each time the interface is
brought up (with default route).

2. Wait until I find time for preparing /etc/net for Fedora Extras. Wait
until I get my work accepted into Fedora Extras. Wait until /etc/net
moves to Fedora Core. Wait until next RedHat Linux is built from that
Fedora Core. Buy one and have fun specifying any route attributes in
interface configuration files.

-- 
    DO4-UANIC
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2006-01-24  7:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-23  2:30 [LARTC] Setting an alias as the "default" IP address, Carl Brewer
2006-01-23  3:22 ` Alexander Samad
2006-01-23  6:49 ` [LARTC] Setting an alias as the "default" IP address, or something Carl Brewer
2006-01-23 19:21 ` Alexey Toptygin
2006-01-23 20:47 ` [LARTC] Setting an alias as the "default" IP address, Alexander Samad
2006-01-23 22:10 ` [LARTC] Setting an alias as the "default" IP address, or something Carl Brewer
2006-01-23 22:22 ` Alexey Toptygin
2006-01-24  7:16 ` Denis Ovsienko [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=20060124101647.01e16307.linux@pilot.org.ua \
    --to=linux@pilot.org.ua \
    --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.