From: "Mike Taekema" <mike@netmaster.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Split access problems.
Date: Wed, 22 Oct 2003 19:03:56 +0000 [thread overview]
Message-ID: <marc-lartc-106685147802781@msgid-missing> (raw)
Good day,
I seem to be having getting my split access scripts to run properly. Here is
my split_access script:
IF1=eth0
IF2=eth1
IP1\x10.123.124.52
IP2\x10.123.124.240
P1\x10.123.124.1
P2\x10.123.124.251
P1_NET\x10.123.124.0/25
P2_NET\x10.123.124.128/25
IFE0=eth0
IFE1=eth1
ip route flush all
ip route add $P1_NET dev $IF1 src $IP1 table $IFE0
ip route add default via $P1 table $IFE0
ip route add $P2_NET dev $IF2 src $IP2 table $IFE1
ip route add default via $P2 table $IFE1
ip route add $P1_NET dev $IF1 src $IP1
ip route add $P2_NET dev $IF2 src $IP2
ip route add default via $P1
ip rule add from $IP1 table $IFE0
ip rule add from $IP2 table $IFE1
exit 0
Now here is my rt_tables file:
#
# reserved values
#
255 local
254 main
253 default
0 unspec
2 eth0
4 eth1
#
# local
#
1 inr.ruhep
Now when I run the script I get these errors: (run script using sh -x
split_access)
+ IF1=eth0
+ IF2=eth1
+ IP1\x10.123.124.52
+ IP2\x10.123.124.240
+ P1\x10.123.124.1
+ P2\x10.123.124.251
+ P1_NET\x10.123.124.0/25
+ P2_NET\x10.123.124.128/25
+ IFE0=eth0
+ IFE1=eth1
+ ip route flush all
+ ip route add 10.123.124.0/25 dev eth0 src 10.123.124.52 table eth0
+ ip route add default via 10.123.124.1 table eth0
+ ip route add 10.123.124.128/25 dev eth1 src 10.123.124.240 table eth1
+ ip route add default via 10.123.124.251 table eth1
RTNETLINK answers: File exists
+ ip route add 10.123.124.0/25 dev eth0 src 10.123.124.52
RTNETLINK answers: File exists
+ ip route add 10.123.124.128/25 dev eth1 src 10.123.124.240
RTNETLINK answers: File exists
+ ip route add default via 10.123.124.1
RTNETLINK answers: File exists
+ ip rule add from 10.123.124.52 table eth0
RTNETLINK answers: Invalid argument
+ ip rule add from 10.123.124.240 table eth1
RTNETLINK answers: Invalid argument
+ exit 0
Why am I getting "file exists and Invalid arguments again?
Thanks in advance
-Mike T.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-10-22 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 19:03 Mike Taekema [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-16 20:29 [LARTC] Split Access Problems Mike Taekema
2003-10-17 2:59 ` gypsy
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-106685147802781@msgid-missing \
--to=mike@netmaster.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