On Fri, Jun 30 2017, Chuck Lever wrote: > > Wouldn't it be nicer if it worked like this: > > (guest)$ cat /etc/hosts > 129.0.0.2 localhyper > (guest)$ mount.nfs localhyper:/export /mnt > > And the result was a working NFS mount of the > local hypervisor, using whatever NFS version the > two both support, with no changes needed to the > NFS implementation or the understanding of the > system administrator? Yes. Yes. Definitely Yes. Though I suspect you mean "127.0.0.2", not "129..."?? There must be some way to redirect TCP connections to some address transparently through to the vsock protocol. The "sshuttle" program does this to transparently forward TCP connections over an ssh connection. Using a similar technique to forward connections over vsock shouldn't be hard. Or is performance really critical, and you get too much copying when you try forwarding connections? I suspect that is fixable, but it would be a little less straight forward. I would really *not* like to see vsock support being bolted into one network tool after another. NeilBrown
Attachment:
signature.asc
Description: PGP signature
