From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Request for TEXT: [LARTC] "onlink" option for ip route
Date: Sat, 24 Mar 2001 21:36:27 +0000 [thread overview]
Message-ID: <marc-lartc-98546988301347@msgid-missing> (raw)
On Sat, Mar 24, 2001 at 12:43:07PM +0100, RoMaN SoFt / LLFB!! wrote:
> Please, couldn't you summarize the meaning of "onlink" option? Is it
> necessary or could I remove it in my multipath setting? See my former
> posts; basically it's a default route with two nexthops for traffic
> balancing between them:
If someone manages to write a reasonable explanation for the 'onlink'
option, I'll put it in the HOWTO ASAP.
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Services
Trilab The Technology People
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next reply other threads:[~2001-03-24 21:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-24 21:36 bert hubert [this message]
2001-03-25 3:43 ` Request for TEXT: [LARTC] "onlink" option for ip route Rogerio Brito
2001-03-25 14:14 ` bert hubert
2001-03-25 17:25 ` Guy Van Den Bergh
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-98546988301347@msgid-missing \
--to=ahu@ds9a.nl \
--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