Re: [j-nsp] Next-table, route leaking, etc.

2020-02-26 Thread adamv0025
> -Original Message- > From: juniper-nsp On Behalf Of > Saku Ytti > Sent: Saturday, February 22, 2020 9:52 AM > To: Jeff Haas > Cc: Juniper NSP > Subject: Re: [j-nsp] Next-table, route leaking, etc. > > On Sat, 22 Feb 2020 at 00:26, Jeff Haas wrote: >

Re: [j-nsp] Next-table, route leaking, etc.

2020-02-25 Thread Andrey Kostin
From: Nathan Ward <mailto:juniper-...@daork.net>> Date: 2/9/20 6:08 PM (GMT-09:00) To: Juniper NSP <mailto:juniper-nsp@puck.nether.net>> Subject: [j-nsp] Next-table, route leaking, etc. Hi all, Something that’s always bugged me about JunOS, is when you import a route from an

Re: [j-nsp] Next-table, route leaking, etc.

2020-02-22 Thread Nathan Ward
> On 22/02/2020, at 10:52 PM, Saku Ytti wrote: > > On Sat, 22 Feb 2020 at 00:26, Jeff Haas wrote: > >> The problem and example in the thread were past the ability of my brain to >> follow this round. >> That said, there's some amount of plumbing that can permit a route that's >> been

Re: [j-nsp] Next-table, route leaking, etc.

2020-02-22 Thread Saku Ytti
On Sat, 22 Feb 2020 at 00:26, Jeff Haas wrote: > The problem and example in the thread were past the ability of my brain to > follow this round. > That said, there's some amount of plumbing that can permit a route that's > been imported into a VRF to locally resolve vs. the local VRF tables

Re: [j-nsp] Next-table, route leaking, etc.

2020-02-21 Thread Jeff Haas via juniper-nsp
--- Begin Message --- > On Feb 10, 2020, at 2:52 AM, Saku Ytti wrote: > > On Mon, 10 Feb 2020 at 05:08, Nathan Ward wrote: > > Hey Nathan, > >> Anyone got any magic tricks I’ve somehow missed? > > Olivier had a cute trick for this. This issue happens because it's the > same route, there is

Re: [j-nsp] Next-table, route leaking, etc.

2020-02-10 Thread Olivier Benghozi
routes work the same whether the exporter of the route is local or >> remote. >> >>> On 10/02/2020, at 4:27 PM, Larry Jones >> <mailto:ljo...@bluphisolutions.com>> wrote: >>> >>> Try a tunnel (lt) interface. >>> >>> >>> --

Re: [j-nsp] Next-table, route leaking, etc.

2020-02-09 Thread Saku Ytti
On Mon, 10 Feb 2020 at 05:08, Nathan Ward wrote: Hey Nathan, > Anyone got any magic tricks I’ve somehow missed? Olivier had a cute trick for this. This issue happens because it's the same route, there is no resolve-on-import and this is something JNPR is open to implement where you'd have some

Re: [j-nsp] Next-table, route leaking, etc.

2020-02-09 Thread Olivier Benghozi
..@bluphisolutions.com>> wrote: >> >> Try a tunnel (lt) interface. >> >> >> Original message >> From: Nathan Ward >> Date: 2/9/20 6:08 PM (GMT-09:00) >> To: Juniper NSP >> Subject: [j-nsp] Next-table, route leaking

Re: [j-nsp] Next-table, route leaking, etc.

2020-02-09 Thread Nathan Ward
the exporter of the route is local or remote. > On 10/02/2020, at 4:27 PM, Larry Jones wrote: > > Try a tunnel (lt) interface. > > > Original message > From: Nathan Ward > Date: 2/9/20 6:08 PM (GMT-09:00) > To: Juniper NSP > Subject: [j-nsp] Next-table, r

Re: [j-nsp] Next-table, route leaking, etc.

2020-02-09 Thread Larry Jones
Try a tunnel (lt) interface. Original message From: Nathan Ward Date: 2/9/20 6:08 PM (GMT-09:00) To: Juniper NSP Subject: [j-nsp] Next-table, route leaking, etc. Hi all, Something that’s always bugged me about JunOS, is when you import a route from another VRF on JunOS

[j-nsp] Next-table, route leaking, etc.

2020-02-09 Thread Nathan Ward
Hi all, Something that’s always bugged me about JunOS, is when you import a route from another VRF on JunOS, the attributes follow it - i.e. if it is a discard route, you get a discard route imported. (Maybe this happens on other platforms, I honestly can’t remember, it’s been a while..) This