Good news on the API-based debug CLI front... Net of a nip here and a tuck there:
DBGvpp# binary-api tap_connect tapname foo hwaddr random DBGvpp# bin sw_interface_add_del_address sw_if_index 1 192.168.4.1/24 DBGvpp# bin sw_interface_set_flags sw_if_index 1 admin-up DBGvpp# api trace save foo API trace saved to /tmp/foo DBGvpp# api trace custom-dump /tmp/foo SCRIPT: tap_connect tapname foo random-mac SCRIPT: sw_interface_add_del_address sw_if_index 1 192.168.4.1/24 SCRIPT: sw_interface_set_flags sw_if_index 1 admin-up link-down DBGvpp# sh int addr local0 (dn): tap-0 (up): 192.168.4.1/24 vpp_api_test and vpp itself can share all of the vpp_api_test code which formats, sends, and receives replies to binary API messages. The bad news: the resulting vpp debug CLI is no more user-friendly than you'd expect. The paint isn't dry yet, and I'm sure that there are still some bugs to fix: I'd rather not release the results in 17.01. Once I've reconciled the nip/tuck work, and tested vpp_api_test, I'll push a (-2'ed) patch so folks can kick the tires. Thanks... Dave
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
