virtualbox.org

M4UROX wrote:I want to get the red interface on the 192.168 subnet.

M4UROX wrote:you have to change the way the virtual NIC is being created.

I'm going to concentrate on simplification first. I don't know how much experience you have with VirtualBox, but it has been a while since I used it. I do remember there were several networking modes, and one used a bridged network for the virtuals, putting some rules in it that made it hard to access from the outside.

In this case, I'm assuming you are using the 192.168 subnet for your network, so you want to vpn to a machine on that network. Your firewall does not have that from what I see, so there is no way to connect (ie, I'm assuming if you ping the 10. subnet, you'll get nothing)

IF you have a spare machine you can lose for a quick test, set it up as the IPFire machine (two nic's), assigning one nic to the network at the office (using dhcp is fine), and the other nic to either connect to a baby workgroup switch or even directly to some other machine. Run your test that way to see if it is VirtualBox issues causing the networking wierdness.

I use virtualization for several IPFire boxes, mainly at our NOC, so I know the virtualization does not cause the problem by itself. But the networking I'm seeing does not make sense to me.

IF you do not have a separate machine, figure out how to get the red interface on the 192.168 subnet. I think it is in the virtual NIC configuration, though like I said, it has been a very long time.

1. Lower the resolution of the topology. I just returned from the eye doctor and I'm not farsighted, thank you . Something that matches approximately the size of the rest of the site?
2. (the really important part and why I want to see an edited picture) Include your actual computer (where's the host in the diagram?) and put some numbers (like subnets, masks). Color-names mean absolutely nothing in basic networking. And we have to have a common language if you want for us to understand each other.

Why did you set adapter 1 to NAT? What was that supposed to achieve?

I am more concerned about the network config of your host machine and how you propose to connect your ipfire setup to the physical machine and the physical world. (This has been asked before). It will do nothing otherwise.

I would think that the Internet side of it somehow has to connect to a NIC on the host so that it can connect to the physical Internet. Have you worked out how to do this? Which of the protected networks do you want to connect the Win 7 vm to? I would think it should be the green.