Yeah. This works, and is the best solution for those limited by IPs, or
whatever. It's best to do it this way from a security standpoint as well, so
you can use your Linux to firewall windows.
--
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-796-9023
email: [EMAIL PROTECTED]
> -----Original Message-----
> From: Jonathan Paisley [mailto:[EMAIL PROTECTED]]
> Sent: Monday, June 18, 2001 11:07 AM
> To: [EMAIL PROTECTED]
> Subject: [Win4Lin-users] [HOWTO] Success with VNET and single
> IP address
>
>
> Hi,
>
> I've recently been evaluating Win4Lin 3's VNET networking
> system. After a
> few initial troubles, I managed to get it working well. The
> configuration
> I have come up with involves masquerading the virtual Windows machine
> through the normal interfaces of the Linux host. As such, it
> can use any
> dial-up connection or ethernet-based network without further
> configuration. This means that extra IP addresses *don't* have to be
> allocated.
>
> I'm testing this out on my laptop, which is sometimes connected to the
> internet via ethernet and at othertimes via a modem ppp link.
> The windows
> session is able to use both seamlessly.
>
> I don't know if this is a standard configuration (one that I haven't
> managed to find documentation for!), but I thought other
> people might be
> interested if it's not. Apologies in advance if this message
> covers stuff
> that's already documented elsewhere.
>
> System: Linux 2.2.18 on a laptop, RH6.2, Win4Lin 3 Evaluation This may
> work with kernel 2.4.x, with the appropriate substitutions.
>
> In order to masquerade the W4L machine, I found that I needed
> to configure
> another network device with a different private subnet from any used
> already by the linux host. In this way, the Linux IP stack
> treats packets
> coming from W4L as if they're coming from another network and
> thus will
> forward them if necessary.
>
> The extra network device I configured was an ethertap (tap0) device. I
> tried using the dummy network device but it didn't seem to
> work (:(). If
> you have VMware it appears that you can use VMware's vmnet1 instead.
>
> e.g.
>
> # modprobe ethertap
> # ifconfig tap0 192.168.250.1
> (the 250 here was chosen arbitrarily)
>
> Now start W4L with VNET and configure TCP/IP in the network
> control panel
> as follows:
>
> IP Address: 192.168.250.100 (any 192.168.250.xxx)
> Netmask: 255.255.255.0
> Default Gateway: 192.168.250.1 (same as tap0 address, above)
> DNS: your upstream DNS server
>
> If things don't work, I found I had to sometimes restart the W4L vnetd
> (exit your windows session first!):
> # killall vnetd-2.2
> # /etc/rc.d/init.d/Win4Lin
>
> # ipchains -A forward -s 192.168.250.100 -i tap0 -j MASQ
> (should really do more for security purposes)
> This adds a rule that says that any packets that would be
> forwarded from
> the IP address assigned to the windows virtual machine should
> instead be
> masqueraded. If you've already configured some kind of firewall you'll
> need to set up the appropriate rules more carefully.
>
> I'd be interested to hear from anyone using a similar (or, hopefully,
> better) configuration! Apologies again if this message covers
> stuff that
> is obvious.
>
> --
> Jonathan Paisley
> [EMAIL PROTECTED]
>
> _______________________________________________
> Win4Lin-users mailing list
> [EMAIL PROTECTED]
> https://lists.netraverse.com/mailman/listinfo/win4lin-users
>
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
