News: This forum is now permanently frozen.
Pages: [1]
Topic: Virtual PC, NAT function  (Read 2832 times)
« on: December 09, 2007, 13:49:28 »
CypherBit *
Posts: 8

I'm trying to configure my own test domain in Virtual PC and came accross some issues when it came to internet access. It was suggested to me (the entire problem is described here: http://groups.google.com/group/microsoft.public.virtualpc/browse_thread/thread/72a9436e0dad9ab3 that I need a NAT router.

I grabbed the 1.2b7 image here: http://chrisbuechler.com/index.php?id=31 configured the virtual network adapters so that NIC one is linked to my physical adapter on the host, NIC two is configured for local only (based on the instructions given at the original URL).
I started the VM and changed the IP to 192.168.1.2/24 with DHCP off (I'm using a Linksys router with IP 192.168.1.1).
Then I set up the interfaces: assign network ports. I didn't configure VLANs and didn't use auto-detection (kept getting no link-up detected). de0 for LAN and de1 for WAN and rebooted. I can access the WebGUI now, but that's it.

I have no idea how to proceed. I want my Linksys router to connect to the internet as it does now (through PPPoE) and would only use m0n0wall as suggested to "act as a router between the virtual network and the physical network."

How should I set up m0n0wall to do so? What changes (if any) do I need to make in General setup, WAN and NAT sections of the WebGUI.

What I'm working with:
Linksys 192.168.1.1

My virtual machines
m0n0wall 192.168.1.2
Domain controller, DHCP, DNS server 192.168.1.130
member server gets the IP from the DC/DHCP server.

If any additional information is needed please let me know and I'll do my best to provide it.
« Reply #1 on: December 11, 2007, 16:17:05 »
CypherBit *
Posts: 8

I appologise for bumping the tread, but would it help if there were no virtual PCs involved (I'll try to incorporate that part in later)?

Just this:

internet
    |
Linksys 192.168.1.1
    |
My pc with m0n0wall acting as a NAT router for the subnets below, the Linksys would be used for internet acess.
      |                      |
   1st subnet              2nd
« Reply #2 on: December 12, 2007, 20:57:21 »
carl *
Posts: 10

I am still new to m0n0wall so take my advice accordingly.

You will probably want to have a different subnet on each side of your m0n0wall. If you have the same 192.168.1.x subnet on the LAN and WAN side of your m0n0wall I think there is more configuration involved.

I am doing something similar with vmware where I have my m0n0wall box setup with 2 nics, one bridged and one is a specific "vmnet".

I have just created a video that demonstrates this setup with m0n0wall in a virtual machine and a virtual machine client.

http://2xod.com/video_tut/m0n0wall%20in%20a%20Virtual%20Machine/
« Last Edit: December 12, 2007, 21:16:51 by carl »
« Reply #3 on: December 13, 2007, 23:41:08 »
CypherBit *
Posts: 8

carl thank you so much, all I needed was a nudge in the right direction and your video provided it.

This is my current setup:

internet
     |
ADSL (PPPoE)
192.168.1.1
Linksys router
     |
192.168.1.130   dg=192.168.1.1
 m0n0wall NAT
10.0.0.1   dg=none
     |
10.0.0.10   dg=10.0.0.1
DC, DHCP, DNS
     |
10.0.0.100-140 (DHCP range)   dg=10.0.0.1
domain members, get their network config from DHCP
DNS=10.0.0.10

The part I got wrong was imagining how it worked, in my head the WAN, LAN were switched (not like the virtual adapters in the video).

I haven't looked at the firewall part of the video, but will do so shortly. I'm ecstatic, the domain is up and running and I can start with my testing.
« Reply #4 on: December 14, 2007, 20:37:52 »
carl *
Posts: 10

You're doing something similar to me.

I setup a test environment for my whole network, so I converted about 5 physical machines to virtual for testing.

My next step after basic configuration was firewall rules so I have remote access directly into the VM's. I did this with Ultra VNC so I added rules for incoming and outgoing TCP on port 5900.

You may want to do something similar so you have easier access to your test environment.

There is more information on how I created this configuration in this thread:
http://forum.m0n0.ch/index.php/topic,1339.0.html
« Reply #5 on: December 16, 2007, 16:35:12 »
CypherBit *
Posts: 8

It is very similar indeed, although you're way in front of me as far as the understanding of NAT is concerned.

I'll probably end up running IIS, Exchange, VNC servers on my virtual network. I want to be able to access those from my physical machine (production network).

I stated with granular settings for example to be able access my m0n0wall from my physical machine, or access my web server running in one of the VMs...I'm unable to do so.

I haven't touched the default LAN firewall rules, but am now testing with the attached config (all open on the WAN). I can't touch any of the VMs.

Advanced Outbound NAT was enabled/disabled, but it didn't make any difference. I rebooted m0n0wall several times.

What am I doing wrong? Which IP should I be using to access them (the one entered in the static ip configuration under Interfaces:WAN, or the local ones in the 10.0.0.x range)?

* config-m0n0wall.local-20071216162614.xml.txt (1.83 KB - downloaded 169 times.)
« Reply #6 on: December 18, 2007, 21:08:36 »
carl *
Posts: 10

You need to enable advanced nat, and then add 1 static route for whatever subnet you are using on your WAN side.
« Reply #7 on: December 23, 2007, 23:26:07 »
CypherBit *
Posts: 8

carl, thank you for your reply/persistance, but it appears I'm still doing something wrong...I'm unable to ping any of my test machines after these changes:

http://img148.imageshack.us/my.php?image=m0n0wallxd1.jpg

EDIT: I realize that the picture above shows the outbound connections (I actually solved that without issues), but I'm still unable to configure inbound connections.
« Last Edit: December 24, 2007, 17:32:05 by CypherBit »
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines