Re: [Qemu-devel] Win32 usermode only network possible? [was:multiple VMs]

["kazu" <kazoo@r3.dion.ne.jp>]

Hi,

There is TAP for Win32 driver in OpenVPN.  I have not used it, but it
probably needs Administrator privilege to install it. It seems like coLinux
uses it to communicate with host Windows.

>From WinPCAP FAQ, Microsoft's loopback driver doesn't work as /dev/lo. When
I looked WinPCAP about two years ago, it needs physical network up to use as
loopback device.

I think it needs SOCKS server runnning on host Windows to communicate with
host. I wonder there is any SOCKS server that can run in user mode without
installing it.

There is another VPN software that has virtual NIC and virtual hub on
Windows. It is SoftEther, but it needs installing process to use it.

kazu

Joe Batt wrote:
> When NATing, you don't have to match the original source port, so we
> should be able to have a NAT run in a non root mode (if source port <
> 1024, use a different source port).
>
> Before I spent so much time looking for it today, I would have expected
> that there was a userspace NAT program available (something that spoke
> the TUN stream format perhaps), but I didn't see anything.  (TUN stream
> format would have been cool, because it QEMU already speaks that, but it
> would have been slower.)  I would expect the TCP packet to TCP socket
> mapping to be the hard part.  UDP should be easy.
>
> Wont we also need a customized DHCP server to server up IP addresses and
> DNS servers?
>
> I would think that the goal is that you can 'qemu -hda somepartition' or
> 'qemu -cdrom someiso' and have a running NATed machine without any host
> configuration.
>
> Joe
>
> On Wed, 2004-04-07 at 17:04, John R. Hogerhuis wrote:
> > On Wed, 2004-04-07 at 13:10, Fabrice Bellard wrote:
> > > I like very much the idea of enabling network use without any
priviledge
> > > rights for Linux and win32. I have looked at the SLiRP code and it
seems
> > > easy to do (at least for Linux, for win32 I have not looked how to do
> > > that with the SDL event loop).
> > >
> > > Expect this feature to come in the next few days :-)
> > >
> >
> > Cool! The win32 side shouldn't be that difficult since sockets under
> > win32 isn't all that different.
> >
> > Anyway the way you decribe it the strategy should work under Win32 as
> > long as you don't use raw sockets since those are priviledged.
> >
> >
> > A SOCKS proxy would allow two way communication since it allows creation
> > of listening sockets. But it requires configuration of the clients so
> > it's not zero-install. Its other advantage is that it would not require
> > priviledged access to the host. Most important networks apps are
> > socksified and the setup is very easy (tell the app to use a certain
> > socks server IP).