but I cannot make frr zebra to connect with specific namespace..

when I enable zebra vrf to namespace it crushes..

-n, --vrfwnetns
When Zebra starts with this option, the VRF backend is based on Linux network namespaces. That implies that all network namespaces discovered by ZEBRA will create an associated VRF. The other daemons will operate on the VRF VRF defined by Zebra, as usual.

what zebra backend are you using ?
Linux VRF or Linux network namespace

Linux network namespace

router1# show vrf
netns-based vrfs
vrf LTE_Mgmt id 1 netns /run/netns/LTE_Mgmt
router1#

it finds the netns..

did you start zebra with "-n" ?

yes.. -n -M fpm

I am not sure about the fpm...

any logs when it crashes ?

it seems that zebra is trying to apply routes on the namespace and fails... hence it freezes until the command times out

for example...

zebra get routes for the VRF from iBGP..

router1# show ip route vrf LTE_Mgmt
Codes: K - kernel route, C - connected, S - static, R - RIP,
      O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,
      T - Table, v - VNC, V - VNC-Direct, A - Babel, D - SHARP,
      F - PBR, f - OpenFabric,
      > - selected route, * - FIB route, q - queued route, r - rejected route


VRF LTE_Mgmt:
B>r 0.0.0.0/0 [200/0] via 10.0.27.251(vrf default) (recursive), label 755, 00:00:08
 r                     via 10.3.3.129, ens32(vrf default), label 156543/755, 00:00:08

since 10.3.3.129 is not accesible from the namespace.. it rejects the route from zebra

ok.. I understand it now...

since namespace is a different stack , it need a gateway interface..

it is not using the  connectivity of the default namespace..

so .. the real question is if accel-ppp can manage vrf with Linux VRF  ?? :D