rri question as a follow up on Q_26409434

from http://www.experts-exchange.com/Security/Software_Firewalls/Enterprise_Firewalls/Cisco_PIX_Firewall/Q_26409434.html?cid=1332#a33465386

how does RRI work with dynamic clients like easyvpn with the routing tables on both the local and remote endpoints?

does the hub wait for the connection before adding the route to its table or does only the client wait to populate the routing table?

thanks in advance!

-t
LVL 18
decoleurAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jimmy Larsson, CISSP, CEHNetwork and Security consultantCommented:
I am actually not sure about if RRI is needed at hub-end when running ezvpn in NEM. When you use client-mode it is exactly the same as a software vpn-client but with NEM there is actually a remote network that should be routable.

But this question is very academic. All implementations of ezvpn that I have ever seen has been over internet. That means that the ASA has a default route pointing towards internet and all internal routers has a default route to the ASA. In these cases you dont have to care about RRI.

But I will try this out within a few days. Please hold this question open and I will get back to you with more information. I will set it up in my lab environment.

/Kvistofta
0
Jimmy Larsson, CISSP, CEHNetwork and Security consultantCommented:
Hi again

I had a look at it. When using easyvpn, the different from "static vpn" is that you use a dynamic crypto-map. In there you can set reverse-route just like you do in a static crypto map entry. What happens in a dynamic-map with reverse-route is that the remote endpoint is inserted in the routing-table at the headend upon connection just as you mentioned. If you run client mode each client ip address is added with a /32 netmask (which could quite easily build a big routing table!) and in NEM the remote network is added when connected. For NEM it is the only option since the ip addressing of the remote network is not pre-configured in the hub firewall. It simply doesnt know in advance which remote network will connect in the future. When the session is torn down the route is removed from the routing table.

But again. This is quite rare circumstances. You almost ALWAYS have a default route pointing out to the internet. Only reason I can see is that you have a supernet-route of rfc1918-addresses pointing inwards (like 10.0.0.0/8) and the vpn remote network (or client pool) is a subset of this. Then you need RRI.

Does this answer your questions?

/Kvistofta
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
decoleurAuthor Commented:
This is what I thought, thanks for looking at it.
0
Jimmy Larsson, CISSP, CEHNetwork and Security consultantCommented:
You are welcome. :-)

/Kvistofta
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Cisco

From novice to tech pro — start learning today.