On Tue, 2010-03-30 at 13:08 -0600, Joseph wrote:
> On 03/30/10 14:55, stosss wrote:
> >On Tue, Mar 30, 2010 at 2:08 PM, Joseph <syscon...@gmail.com> wrote:
> >> I'm running Windows XP on VirtualBox, it has a network "NAT" so the IP
> >> address it gets:
> >> IP: 10.0.2.15
> >> Gateway: 10.0.2.2
> >> DNS: 10.10.0.1 ?(Linux router)
> >>
> >> I've tried to access the Windows IP by creating another subnet:
> >> ifconfig eth0:1 10.0.2.0 up
> >>
> >> but it doesn't work, I can not ping the Windows IP: ?10.0.2.15
> >> (Windows firewall is OFF)
> >>
> >> Any suggestions?
> >
> >You could try using Bridged instead of NAT. Bridged would let you set
> >up the NIC on the VM to the same IP address range as the host using
> >the same NIC as the host.
> >
> >If your host IP is 192.168.1.10 on eth0
> >You could set Bridged > eth0 on the VM settings panel and then set
> >your net config inside the VMs OS to 192.168.1.X on eth0
>
> Yes, I'm aware of it.
> I've setup iptables + squid so I can filter here they an connect to.
> If I setup as Bridge, Windows gets the IP from the Router (dhcpd) and will
> by-pass my filter :-/
> My router does not filter outgoing traffic only incoming.
>
> I setup on VirtualBox one interface as NAT and one as Bridge and Windows
> browser selected the one without filer Bridge, so it is bypassing my filter.
>
Check the User Manual for Virtual Box:
http://download.virtualbox.org/virtualbox/3.1.6/UserManual.pdf
Take a look at section 6.3:"VirtualBox.
A virtual machine with NAT enabled acts much like a real computer that
connects
to the Internet through a router. The “router”, in this case, is the
VirtualBox network-
ing engine, which maps traffic from and to the virtual machine
transparently. The
disadvantage of NAT mode is that, much like a private network behind a
router, the
virtual machine is invisible and unreachable from the outside internet;
you cannot run
a server this way unless you set up port forwarding (described below)."
I would suggest to manually set up your ip address and (or tune dhcp
server for VirtualHost).
Then should be easy to adjust your settings for iptables+squid.
If i get you right on you hosting OS you have iptables+squid ?!
Then probably you should do the following:
1) Use bridged connection for you VM (WindowsXP).
2) In Windows XP:
2.1 Set up ip address manually at the same network as your host
machine.
2.2 Make settings for your browser to use proxy server (ip and port of
your linuxbox(hosting machine) with squid).
2.3 If you have forwarding and dns you can also set them at the network
setting window.
3) In your LinuxBox (host machine):
2.1. Use iptables to allow traffic between squid and you winXP.
2.2. Setup squid to allow access from winXP.
In most cases it should be easy.
