Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Rogerio Brito <rbrito@iname.com>
To: lartc@vger.kernel.org
Subject: Re: Request for TEXT: [LARTC] "onlink" option for ip route
Date: Sun, 25 Mar 2001 03:43:07 +0000	[thread overview]
Message-ID: <marc-lartc-98549183828901@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98546988301347@msgid-missing>

On Mar 24 2001, bert hubert wrote:
> If someone manages to write a reasonable explanation for the
> 'onlink' option, I'll put it in the HOWTO ASAP.

	As far as I understand it, the situation is as follows:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
	Sometimes, you may want to send packets via a machine
	(i.e., a gateway) which is physically connected to your
	network, but to which you don't specifically have a route in
	your kernel routing table.

	In a situation like this, if you try to add a route through
	such a gateway, the kernel will perform consistency checks on
	the route you're trying to add and will detect that it doesn't
	know how to send packets to that gateway, rejecting the route.

	The "onlink" option of the "ip" command tells the kernel that
	the it does not have to check if the gateway is reachable
	directly by the current machine (i.e., the kernel does not
	need to check if the gateway is attached to the local
	network), so that you can insert your route in the kernel
	table without it being complained about.

	One possible use of this feature is when you're setting up a
	tunnel: you have to tell the kernel in some way that the other
	side of the tunnel is the gateway for your tunneled
	connection. But this other side is frequently very, very far
	away, only reachable via your default route (and, thus, the
	kernel doesn't have a direct route to it). So, to tell the
	kernel that the rest of your tunneled connection is reachable
	via this distant machine, you use the "onlink" option when
	you're setting this special kind of route.

	Of course, "onlink" should be used with caution.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

	Please let me know if this is acceptable. I could write with
	more details (giving a more concrete example), but I'm very
	busy right now. :-(

	I hope that this serves at least as a first approximation to
	the text that will be featured on the HOWTO.


	Hope this helps, Roger...

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-  Rogerio Brito - rbrito@iname.com - http://www.ime.usp.br/~rbrito/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

  reply	other threads:[~2001-03-25  3:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-24 21:36 Request for TEXT: [LARTC] "onlink" option for ip route bert hubert
2001-03-25  3:43 ` Rogerio Brito [this message]
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-98549183828901@msgid-missing \
    --to=rbrito@iname.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox