All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sebastian A. Aresca" <sebastian@aresca.com.ar>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Two uplink provides with debian ( woody ) - problem to insert route in a table
Date: Wed, 05 Nov 2003 04:23:07 +0000	[thread overview]
Message-ID: <marc-lartc-106800620130231@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106799407121155@msgid-missing>

Try this

ip route $P1 default scope global nexthop via 10.129.30.1 dev eth0 weight 1
\
nexthop via 10.129.31.1 dev eth1 weight 1

> Hello,
>
> I'm trying to configure iproute2 with two providers in a Load balancing
configuration according "Linux Advanced Routing & Traffic Control HOWTO".
>
> I'm working with two links:
> - static ip (adsl link - 256Kbps)
> - dynamic ip (512kbps).
>
> In my HedHat 7.2 everything works well, but in my debian (woody) something
wrong is going on. First I have to create two tables, one for each provider.
That's ok, but when I try to add an route to one of these tables, it goes to
main table.
>
> # ip route add default via $P1 table T1
> looks OK, but the route goes to table main
>
> # ip route add default via $P2 table T2
> NOK, because it goes to table main too, not to table T2.
>
> Any clues???
>
> Thanks in advance,
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>

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

  reply	other threads:[~2003-11-05  4:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-05  0:59 [LARTC] Two uplink provides with debian ( woody ) - problem to insert route in a table alisson-empresas-seguranca
2003-11-05  4:23 ` Sebastian A. Aresca [this message]
2003-11-05 10:05 ` Thomas Themel

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-106800620130231@msgid-missing \
    --to=sebastian@aresca.com.ar \
    --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.