From: "Kertész Viktor" <kviktor@i-trade.hu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] howto equalize two uplink?
Date: Wed, 26 Mar 2003 13:39:44 +0000 [thread overview]
Message-ID: <marc-lartc-104868605610139@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104867316529270@msgid-missing>
May I ask you something?
What is the difference between these:
10.5.0.0/16 proto static
nexthop via 10.0.1.6 dev eth1 weight 1
nexthop via 10.0.1.8 dev eth1 weight 1
AND
10.5.0.0/16
nexthop via 10.0.1.6 dev eth1 weight 1
nexthop via 10.0.1.8 dev eth1 weight 1
Thanks for your answers. Now it's working but I want to make these settings
permanent and I haven't found answers to the above problem.
Viktor
_______________________________________________
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-03-26 13:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 10:04 [LARTC] howto equalize two uplink? Kertész Viktor
2003-03-26 11:03 ` Kim Jensen
2003-03-26 13:00 ` Kertész Viktor
2003-03-26 13:16 ` Kim Jensen
2003-03-26 13:39 ` Kertész Viktor [this message]
2003-03-27 1:42 ` William L. Thomson Jr.
2003-03-27 7:41 ` Kertész Viktor
2003-03-28 18:40 ` William L. Thomson Jr.
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-104868605610139@msgid-missing \
--to=kviktor@i-trade.hu \
--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.