From: CARSTEN.SCHILL@NDSatcom.com
To: lartc@vger.kernel.org
Subject: AW: [LARTC] "onlink" option for ip route
Date: Fri, 23 Mar 2001 10:02:52 +0000 [thread overview]
Message-ID: <marc-lartc-98534184326857@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98516286116576@msgid-missing>
Have a look to "Tunnels over IP in Linux-2.2" (ip-tunnels.ps, part of the
iproute package). They use 'onlink' to switch off the consistency check for
gateway reachability during tunnel setup.
Regards,
Carsten
> -----Ursprüngliche Nachricht-----
> Von: RoMaN SoFt / LLFB!! [mailto:roman@madrid.com]
> Gesendet am: Mittwoch, 21. März 2001 09:23
> An: lartc@mailman.ds9a.nl
> Betreff: [LARTC] "onlink" option for ip route
>
>
> Hi.
>
> Would someone be so kind to explain "onlink" option to me? Upon
> reading "ip command" ref.man. I still don't understand what this
> option is intended for. A example where this option may be useful
> would be appreciated.
>
> Regards.
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> ** RoMaN SoFt / LLFB **
> roman@madrid.com
> http://pagina.de/romansoft
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO:
> http://ds9a.nl/2.4Routing/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-03-23 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-21 8:23 [LARTC] "onlink" option for ip route RoMaN SoFt / LLFB!!
2001-03-22 2:19 ` Mike Fedyk
2001-03-23 10:02 ` CARSTEN.SCHILL [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-24 11:43 AW: " RoMaN SoFt / LLFB!!
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-98534184326857@msgid-missing \
--to=carsten.schill@ndsatcom.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.