When terminating PPP into VRF using Accel-VRF-Name radius attribute and with Framed-Route attribute in the radius reply message, the route provided by radius is installed into default routing table instead of the appropriate table corresponding to the VRF.
Example. Access accept packet:
[2022-04-27 15:00:00.303] : fe1b34439de428b9: recv [RADIUS(1) Access-Accept id=1 <Service-Type Framed-User> <Framed-Route "192.168.255.0/24"> <Accel-VRF-Name "client100">] accel-ppp# show sessions ifname | username | ip | ip6 | ip6-dp | type | state | uptime | uptime-raw | calling-sid | called-sid | sid | comp | rx-bytes | tx-bytes | rx-bytes-raw | tx-bytes-raw | rx-pkts | tx-pkts --------+---------------------------+-------------+-----+--------+------+--------+----------+------------+--------------+------------+------------------+------+----------+----------+--------------+--------------+---------+--------- ppp0 | 79779314645@lns.cpm.test2 | 192.168.0.2 | | | l2tp | active | 00:01:40 | 100 | 176.59.63.35 | 10.10.10.2 | fe1b34439de428b9 | | 64 B | 210 B | 64 | 210 | 4 | 6 root@deb-frr:~# **ip route ** default via 10.39.250.1 dev ens192 onlink 10.39.250.0/24 dev ens192 proto kernel scope link src 10.39.250.120 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown **192.168.255.0/24 dev ppp0 scope link** root@deb-frr:~#** ip route show table 100** unreachable default metric 4278198272 local 192.168.0.1 dev ppp0 proto kernel scope host src 192.168.0.1 192.168.0.2 dev ppp0 proto kernel scope link src 192.168.0.1 local 192.168.254.1 dev dummy100 proto kernel scope host src 192.168.254.1 root@deb-frr:~# ip vrf show Name Table ----------------------- IN 10 client100 100