You don't need to set up vrf templates if everyone is going to use the
default radius server and default authentication and au6thorization
groups. It's optional.
Thanks Ivan, now it's clear I don't need templates...
What does debug radius and debug ppp negotiation on Cisco say
about why
Putting a User into a certain VRF is quite simple:
vrfuser User-Password == topsecret
Cisco-AVPair += lcp:interface-config#1=ip vrf forwarding \
VRFNAME,
Thank you Gerald, this is what I need to do.
I tried using this
Hi Kalik,
thanks for your reply.
I had a look at the cisco doc on vrf forwarding, but I think it's not what I
need to do.
I don't need to put all template items in fr, but only to select the vrf based
on group which the user belongs to.
Did I miss the point? Do I need to configure Templates
You don't need to set up vrf templates if everyone is going to use the
default radius server and default authentication and au6thorization
groups. It's optional.
What does debug radius and debug ppp negotiation on Cisco say about why
was the Framed-IP-Address rejected. If it fails on IPCP then
Hi all,
anybody has experience in setting up FR to support IP VRF for cisco equipments?
Can you point me to some clear and simple configuration guide for doing that?
TIA,
Francesco.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Francesco Cristofori schrieb:
Hi all,
anybody has experience in setting up FR to support IP VRF for cisco
equipments?
Can you point me to some clear and simple configuration guide for doing that?
Putting a User into a certain VRF is quite simple:
vrfuser User-Password == topsecret
Only thing you need to set on Freeradius is cisco hack so it would deal
with av-pairs correctly. Than add av-pairs to user or group
configuration and they will work.
If you are looking for a Cisco guide how to set up VRF with Radius:
7 matches
Mail list logo