JuniperForum.com
September 02, 2010, 08:41:59 PM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: If you have an interesting idea for an article or knowledgebase entry, please submit it!
 
  Home Help Login Register  
* *
Pages: [1]
  Print  
Author Topic: Routing Traffic From Custom VSYS/VR to Shared Trust-VR  (Read 4308 times)
TripleDES
Jr. Member
**
Posts: 79


View Profile
« on: December 07, 2007, 10:57:39 AM »

I'm having issues getting traffic to route properly from a VSYS-A (attached to VR-A) to Trust-VR.  Even though I have the proper policies and routes are in place, for some reason, the NS tries to send traffic to Untrust-VR.

See this peculiar note in the debug:

  Cross vsys (VSYS-A->Root) at ethernet2/5.50: need loopback  push to Untrust
  policy search from zone 3001-> zone 1

Any help is appreciated.
Logged
sfouant
Full Member
***
Posts: 109



View Profile
« Reply #1 on: December 07, 2007, 02:03:12 PM »

From what I recall, in order to perform any type of Inter-VSYS routing or routing from a given VSYS to a non shared zone in the root VSYS, the traffic needs to loop through the Untrust zone (as this is typically a shared zone).  Is your Untrust zone perhaps bound to the Untrust-VR?  If so you'll need Inter-VSYS routing as well as Inter-VR routing configured.
Logged

Stefan Fouant, CISSP
TripleDES
Jr. Member
**
Posts: 79


View Profile
« Reply #2 on: December 07, 2007, 02:24:37 PM »

Yes, Untrust is bound to the untrust-vr.  Is inter/intra vsys/vr routing an option that needs to be configured somewhere?  I don't see the option in the VR o Zone settings.
Logged
sfouant
Full Member
***
Posts: 109



View Profile
« Reply #3 on: December 07, 2007, 03:38:28 PM »

No it's not an option per se.  I simply meant you will need to configure some additional routing.

Let's say your network in the Trust zone is x and the network in the Vsys-A-Trust zone is y.  What you would need essentially is a route in the Vsys-A-VR to network x with the next-hop as the Untrust-VR.  In the Untrust-VR you will need a route to network x with the next-hop as the Trust-VR (assuming your root Trust zone is bound to the Trust-VR).  Similarly, in order to send the return traffic, you will need a route in the Trust-VR to reach network y with the next-hop set as the Untrust-VR.  You will also need a route in the Untrust-VR to reach network y with the next-hop set to the Vsys-A-VR.  In addition you will need policies from the Vsys-A-Trust zone to the Untrust zone and from the Untrust zone to the Trust zone, and vice-versa if you want to enable sessions originating in the Trust zone to reach the Vsys-A-Trust zone.

If your Untrust interface was bound to the Trust-VR you would still need to perform some of this, but it is exacerbated by the fact that your Untrust zone is bound to the Untrust-VR.  This is a more secure configuration, but requires a few extra steps to get it configured.

Does that make sense?
Logged

Stefan Fouant, CISSP
TripleDES
Jr. Member
**
Posts: 79


View Profile
« Reply #4 on: December 13, 2007, 09:05:14 AM »

I never thanked you for the information.  Thank you!

I managed to get it working by looping things through the untrust-vr.  I call it the boomerang effect where traffic from an unshared zone must pass through the untrust-vr first in order to get to a custom vsys that is also unshared.

The key points are:
VSYS must exist on a shared VR
untrust-vr must contain routes to both destination vr (VSYS) and source VR (shared VR)
Policies are created both in shared VR and custom VSYS (ie. From TESTZone to Untrust and From VSYSZone to Untrust)
Logged
sfouant
Full Member
***
Posts: 109



View Profile
« Reply #5 on: December 13, 2007, 11:43:41 AM »

I never thanked you for the information.  Thank you!

You're welcome!

Quote
I call it the boomerang effect where traffic from an unshared zone must pass through the untrust-vr first in order to get to a custom vsys that is also unshared.

It's not necessarily that the traffic has to pass through the Untrust-VR, rather it has to go through the Untrust Zone... in your case, since the Untrust Zone was bound to the Untrust-VR, there were some additional steps you needed to perform.  Had your Untrust Zone been bound to the Trust-VR which also contained the Trust zone, you would have only needed to configure routing between the Trust-VR and the Vsys-A-VR.  Policies would have been similar however as you would still need to have the traffic go from the Vsys-A-Trust zone to the Untrust zone to the Trust zone and vice-versa.
Logged

Stefan Fouant, CISSP
TripleDES
Jr. Member
**
Posts: 79


View Profile
« Reply #6 on: December 13, 2007, 12:13:13 PM »

Yes, good clarification.

The reason why I'm doing this in the first place is something isn't working properly when I share the zone outright.  Theoretically, if a zone is shared, it can be accessed through custom virtual systems.

However, for some reason sharing the zones and consequently creating a custom vsys forces IP classification instead of VLAN based classification which brings about a entirely new set of complications.
Logged
screenie.
Hero Member
*****
Posts: 1236


View Profile
« Reply #7 on: December 24, 2007, 06:02:29 AM »

Guys,
doesn't this debug output simply means that an interface is missing in the shared zone? Each shared zone should have an interface for routing purposes, if not a real one then at least a loopback if I rember well.
Logged

Regards, Screenie
------------------------
JNSS, JNCIA, JNCIS, JNCI
openking89
Newbie
*
Posts: 3


View Profile
« Reply #8 on: September 25, 2009, 05:31:14 AM »

The exact answer, of course, depends on exactly what the two zones are configured - if they're totally disjoint, or they overlap somewhat, or they're nearly identical except for a few corners.

In any case, you can describe it with the phrase 'Bad Juju Happens". Smiley

Regards

John
Logged

hdharmaraja
Newbie
*
Posts: 2


View Profile
« Reply #9 on: January 25, 2010, 03:59:29 AM »

Guys,
doesn't this debug output simply means that an interface is missing in the shared zone? Each shared zone should have an interface for routing purposes, if not a real one then at least a loopback if I rember well.

Hiya, I have a similar set up and having some issues regarding loopback.

I have created a custom VR in root level and sharing it (VR-intervsys) and have a shared zone (iVSYS) bound to it, hence its zone is shared. Now I am limited to use a physical interface, so I want to use a loopback. How do i go about it?

Would you be able to tell me, where would I define the loopback interface, (root or in vsys) and how about the ip addressing?
Logged
fivefingers8
Newbie
*
Posts: 3


View Profile WWW
« Reply #10 on: July 28, 2010, 06:52:49 PM »

the traffic needs to loop through the Untrust zone (as this is typically a shared zone). 
Logged

Understand what you do so you can do it better.
To be a happy person who choose her love .  The vibram  fivefingers bring happiness to me, so I  select vibram fivefingers shoes.
Pages: [1]
  Print  
 
Jump to:  

Navigation

Donate

Please consider donating if we've saved you time or money. It helps pay for the bandwidth, equipment, and hosting charges to keep this site running

Tools

Submit Article/KB - Do not submit questions here.

Recent

Stats

Members
Stats
  • Total Posts: 40480
  • Total Topics: 11163
  • Online Today: 73
  • Online Ever: 393
  • (August 06, 2008, 07:40:57 AM)
Users Online
Users: 0
Guests: 34
Total: 34
TinyPortal v1.0 beta 4 © Bloc
Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!

Sponsored in part by CollarWise

Page created in 0.231 seconds with 35 queries.