All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julian Anastasov <ja@ssi.bg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] iproute2: gatewayed routes in ancillary tables
Date: Mon, 05 May 2003 23:04:23 +0000	[thread overview]
Message-ID: <marc-lartc-105217588506912@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105215601317386@msgid-missing>


	Hello,

On Mon, 5 May 2003, Martin A. Brown wrote:

> It seems that unless a route to the gateway IP exists in the main routing
> table, I cannot add a route through the gateway IP, even if there is a
> route to the destination in the ancillary routing table.
>
> Why is this?

	Because when we create a route we need to know the
right scope to assign to the new nexthop. Once it is known we don't
need the route to the gateway (and you can delete it).
You can see that there is such comment in the code:

It is not necessary, but requires a bit of thinking

	IMO, this check is necessary because without seeing the
route to the gateway we can not know whether this gateway is:

- local IP (and the resulting route should be device-only, GW IP
is ignored)

- unicast IP (and the resulting route should be via device and GW IP)

	If you do not like this policy you can use static routes
to solve the problem.

Regards

--
Julian Anastasov <ja@ssi.bg>

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

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-05 17:23 [LARTC] iproute2: gatewayed routes in ancillary tables Martin A. Brown
2003-05-05 23:04 ` Julian Anastasov [this message]
2003-05-06  3:33 ` Martin A. Brown
2003-05-06  8:58 ` Julian Anastasov
2003-05-06 13:56 ` Martin A. Brown
2003-05-06 14:33 ` Julian Anastasov

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-105217588506912@msgid-missing \
    --to=ja@ssi.bg \
    --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.