From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problems with iproute2
Date: Sun, 10 Jul 2005 00:35:05 +0000 [thread overview]
Message-ID: <42D06D39.2D18BB91@iswest.com> (raw)
In-Reply-To: <20050709193002.BF59BCC4@agile.dk>
Jan Andersen wrote:
>
> I'm using Debian (sarge)
>
> I do now have 2 ISP, one DSL and one cabel.
>
> I want to use the DSL as my primary and only use the cabel-modem if the DSL
> fails.
>
> The setup is:
>
> IP1 -> Router -> NAT_IP1 -> eth0 -> eth2 (LAN)
> IP2 -> Cable-Modem -> eth1 -> eth2 (LAN)
>
> I wrote the following in my /etc/iproute2/rt_tables
>
> ip rule add from NAT_IP1 lookup 1
> ip route add 10.1.0.0/16 via 10.1.1.1 table 1
> ip route add 0/0 via NAT_IP1 table 1
>
> ip rule add from IP2 lookup 2
> ip route add 10.1.0.0/16 via 10.1.1.1 table 2
> ip route add 0/0 via IP2 table 2
>
> The problem is identical to http://www.samag.com/documents/s\x1824/sam0201h/
>
> But if I write "ip rule list" I get the following error:
>
> Database /etc/iproute2/rt_tables is corrupted at ip rule add from
> 192.168.100.254 lookup 1
>
> Does anyone know and have a solution to this problem?
>
> Regards
>
> Jan Andersen
No, I don't have a solution. What is in your /etc/iproute2/rt_tables file?
Normally, everything should be commented except
255 local
254 main
253 default
0 unspec
Are you sure 'route add' should work when both routes are identical?
Where does the 192.168.100.254 come from?
Why allow NAT of the internet IPs?
OPINION 1: One NAT is plenty, two is begging trouble.
OPINION 2: Most of the problems reported here have "example.com" ip addresses,
so avoiding NAT is A Good Thing.
--
gypsy
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2005-07-10 0:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-09 19:29 [LARTC] Problems with iproute2 Jan Andersen
2005-07-10 0:35 ` gypsy [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=42D06D39.2D18BB91@iswest.com \
--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 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.