Difference between revisions of "VPP/HostStack/LDP/sshd"
From fd.io
Florin.coras (Talk | contribs) (→Server configuration) |
Florin.coras (Talk | contribs) (→Server configuration) |
||
| Line 9: | Line 9: | ||
Since this is experimental work, it is recommended to start vpp in debug mode with the following additions to startup.conf: | Since this is experimental work, it is recommended to start vpp in debug mode with the following additions to startup.conf: | ||
| + | unix { gid vpp } | ||
session { evt_qs_memfd_seg } | session { evt_qs_memfd_seg } | ||
socksvr { socket-name /tmp/vpp-api.sock} | socksvr { socket-name /tmp/vpp-api.sock} | ||
| + | |||
| + | These ensure that vpp starts with gid vpp, the session layer uses memfd segments for event queues and that the binary api can work with a socket transport. | ||
Revision as of 22:24, 4 December 2018
Example of how to run sshd via LDP and VCL on top of VPP's host stack. This is known to work as of vpp gerrit 16340 with OpenSSH 7.6p1 on Ubuntu 18.04.1.
To run the test two hosts with networking connectivity are needed: - server where vpp and sshd run - client where the ssh client runs on top of the linux host stack
Server configuration
Since this is experimental work, it is recommended to start vpp in debug mode with the following additions to startup.conf:
unix { gid vpp }
session { evt_qs_memfd_seg }
socksvr { socket-name /tmp/vpp-api.sock}
These ensure that vpp starts with gid vpp, the session layer uses memfd segments for event queues and that the binary api can work with a socket transport.
