From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Split Access Problems
Date: Fri, 17 Oct 2003 02:59:53 +0000 [thread overview]
Message-ID: <marc-lartc-106636115315038@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106633755428897@msgid-missing>
> Mike Taekema wrote:
>
> Good day,
Please do not post in html format.
> My first problem is when I run the line: ip route add $P1_NET dev $IF1
> src $IP1 table T1
You have not edited /etc/iproute2/rt_tables. For reference, here's
mine( minus the comments):
255 local
254 main
253 default
0 unspec
2 eth1
4 eth2
6 eth3
8 ppp0
9 mpath
and I specify these as "eth2", Etc. Where your above is T1, I use $IFE1
and IFE1="eth1" appears in my definitions at the top of the script.
> I get the error: Error: argument "T1" is wrong: "table" value is
> invalid
Gypsy
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-10-17 2:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-16 20:29 [LARTC] Split Access Problems Mike Taekema
2003-10-17 2:59 ` gypsy [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-22 19:03 [LARTC] Split access problems Mike Taekema
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-106636115315038@msgid-missing \
--to=gypsy@iswest.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox