VRF delte / re-create then not working

Bugs
#1

Hello,

I am trying to create a VRF and dummy interface, then I found it’s not able to ping the dummy interface IP. Then I reproduce this issue on my other VyOS router, I found that if it’s the first time create the VRF and dummy interface on the router, then it’s okay to ping. But if I delete the VRF and dummy interface, then re-create it, then it’s not able to ping the dummy anymore. Even create a new VRF and new dummy interface, it’s still not able to ping. And I have reproduce this issue on more than 3 VyOS routers. It seems to be a bug?

VyOS version: VyOS 1.4-rolling-202101311232

set vrf name VRF-199 table 199
set interfaces dummy dum199 address '10.99.226.199/32'
set interfaces dummy dum199 vrf 'VRF-199'

run ping 10.99.226.199 vrf VRF-199

delete interfaces dummy dum199
delete vrf name VRF-199
#2

Hello sam

It should be the expected behavior , on linux you couldn’t ping inside vrf itself , you should make a ping between two hosts in the VRF . Also, I would like to suggest updating a nightly version.

regards,

#3

@fernando Thank you for the quick reply. Actually I can’t ping my another router via the VRF interface as well. If it’s the expected behavior, but why I can ping the dummy inside vrf at the first time VRF being created, and it works just fine if I didn’t delete the VRF. This ping issue only happen when I delete a VRF then create a same VRF or a new VRF, then it’s not able to ping.

BTW, I can ping inside vrf itself on the EVE-ng VyOS router without issue. And I can delete/create/re-create VRF many times and it still able to ping and works just fine. The only different is my EVE-NG is running VyOS 1.4.0.

Version:          VyOS 1.4.0
Release Train:    sagitta

Built by:         admin@ovirt.club
Built on:         Tue 20 Apr 2021 05:19 UTC
Build UUID:       f098f5eb-ebac-495d-b475-d6265279469c
Build Commit ID:  a934e73e2738e5

Architecture:     x86_64
Boot via:         installed image
System type:      KVM guest

Hardware vendor:  QEMU
Hardware model:   Standard PC (i440FX + PIIX, 1996)
#4

You use outdated rolling release

#5

it works , although I used latest nightly-version :

vyos@vyos-client:~$ ping 172.16.210.1 vrf BLUE
PING 172.16.210.1 (172.16.210.1) 56(84) bytes of data.
64 bytes from 172.16.210.1: icmp_seq=1 ttl=64 time=0.114 ms
64 bytes from 172.16.210.1: icmp_seq=2 ttl=64 time=0.053 ms
^C
--- 172.16.210.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1046ms
rtt min/avg/max/mdev = 0.053/0.083/0.114/0.030 ms
vyos@vyos-client:~$ show ip route vrf BLUE
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, F - PBR,
       f - OpenFabric,
       > - selected route, * - FIB route, q - queued, r - rejected, b - backup
       t - trapped, o - offload failure

VRF BLUE:
C>* 172.16.210.0/24 is directly connected, dum10, 00:01:33
C>* 192.168.120.0/24 is directly connected, eth1, 00:02:25
vyos@vyos-client:~$
vyos@vyos-client:~$
vyos@vyos-client:~$ showver

  Invalid command:  [showver]

vyos@vyos-client:~$ show version
Version:          VyOS 1.4-rolling-202208010217
Release train:    sagitta

Built by:         autobuild@vyos.net
Built on:         Mon 01 Aug 2022 02:17 UTC
Build UUID:       5595cd3f-204c-47e2-a354-c1f304fed6c0
Build commit ID:  ffc63f19772a5f

Architecture:     x86_64
Boot via:         installed image
System type:      KVM guest

Hardware vendor:  QEMU
Hardware model:   Standard PC (i440FX + PIIX, 1996)
Hardware S/N:
Hardware UUID:    a96e7eb0-b587-4092-978e-7bad4f096053

Copyright:        VyOS maintainers and contributors
#6

@sam999

that was a known bug in the past. Please upgrade to a more recent rolling release.