All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis Miguel Cruz Miranda <luismi@b2bi.es>
To: lartc@vger.kernel.org
Subject: [LARTC] sysconfig changes and problems with ip route add
Date: Thu, 28 Nov 2002 16:05:36 +0000	[thread overview]
Message-ID: <marc-lartc-103849981900395@msgid-missing> (raw)

I edited the file /etc/sysconfig/network-scripts/ifup-routes, and I add...

# Add any advanced routes
grep "^advanced" /etc/sysconfig/static-routes |
     while read ignore dev args; do
         if [ "$dev" = "$1" ]; then
                 /sbin/ip route add $args
         fi
done

Then, I went to /etc/sysconfig and I created a file called static-routes 
with this content:
advanced eth1 194.149.216.1/32 dev vlan2 table 21
advanced eth1 194.149.216.2/32 dev vlan2 table 21
advanced eth1 194.149.216.3/32 dev vlan2 table 21
advanced eth1 0.0.0.0/0 via 10.1.0.254 table 20

Why table 21 is not loaded at boot?
:(

At 17:05 27/11/2002, Martin A. Brown wrote:
>  : >/etc/iproute2/rt_tables contains a mapping of human names to routing 
> table
>  : >numbers.  I call them table identifiers to table ids.  This file does not
>  : >contain routes.
>  : So, if I understand all correctly, I don't need that file to use multiple
>  : route tables, do I?
>
>You are correct.  It simply maps names to numbers so that you can use
>something like this if you want:
>
># ip route add default via 10.0.0.1 table dsl-link
># ip route add default via 10.0.0.2 table t1-link
>
>Where the rt_tables file contains:
>
>1       dsl-link
>2       t1-link
>
>If you do not have the file /etc/iproute2/rt_tables, you can use the
>following syntax .
>
># ip route add default via 10.0.0.1 table 1
># ip route add default via 10.0.0.2 table 2
>
>  : I found a solution here:
>  : http://www.samag.com/documents/s=1824/sam0201h/0201h.htm
>
>I've not seen this before and will have to read this article.  Thanks for
>the link.
>
>I do have some general documentation on the use of "ip route" and "ip
>rule" in the appendices of my documentation available here:
>
>   http://plorf.net/linux-ip/
>
>Let me know if you find any flaws, areas for improvement, or missing
>content.
>
>-Martin
>
>--
>Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com

Luis Miguel Cruz Miranda.
CCNA - Systems Administrator

---------------------------------------------------------------
B2B INTEGRAL, S.A.
Pol. Ind. de Asipo
C/A - Parcela 86-C
33.428 - CAYES - LLANERA
ASTURIAS (ESPAÑA/SPAIN)
---------------------------------------------------------------
Tel: +34 985 980 804 ---- Fax: +34 985 980 794
---------------------------------------------------------------
WEB: http://www.b2bi.es/

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2002-11-28 16:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-28 16:05 Luis Miguel Cruz Miranda [this message]
2002-11-28 22:30 ` [LARTC] sysconfig changes and problems with ip route add Martin A. Brown
2002-11-29  1:56 ` Arindam Haldar
2002-11-29 15:22 ` Luis Miguel Cruz Miranda

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=marc-lartc-103849981900395@msgid-missing \
    --to=luismi@b2bi.es \
    --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.