Thanks a lot Venu. It works for me.
Regards, Chetan On Wed, Mar 24, 2021 at 12:21 PM Venumadhav Josyula <[email protected]> wrote: > Hi Chetan, > > That ability is already there right now also we are using vpp 20.09 and > intend to go 21.x also, we do it this way > ... > dpdk { > dev 0000:19:00.1 { > name vpp-intf19/0/1 <--- "you can give whatever you , we have > chose bus, slot,fn appended with vpp-intf" > } > .. > > } > > We doing this way and it works for us. This generation fo startup.conf > happens to us via some our task ( unix process ). I guess that should good > enough ? > > Thanks, > Regards, > Venu > > > On Wed, 24 Mar 2021 at 11:31, chetan bhasin <[email protected]> > wrote: > >> Hi Team, >> >> We have a requirement to have a predictable interface name , say >> "device_<pci_address>" , instead of GigabitEthernet/TenGigabitEthernet etc >> , so that external scripts can create vpp.conf automatically. >> >> One way is to modify plugins/dpdk/device/format.c code as per our >> requirement . but we want to avoid changes in vpp code base that will make >> vpp upgrade easy for the future. >> Can you please suggest any additional CLI or configuration via which we >> could alias interface names ? >> >> Thanks, >> Chetan >> >> >> >>
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#19008): https://lists.fd.io/g/vpp-dev/message/19008 Mute This Topic: https://lists.fd.io/mt/81570537/21656 Group Owner: [email protected] Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
