> As has already been suggested, you need to enable ip forwarding. Also,
> forget that your router is already doing NAT, this is different.
>
> Greg
Hi
I did it that way but didn't work... There's a very strange issue with my
Host Interface behalf... Guest can access any host/ip in my subnet EXCEPT
192.168.1.254 that is the router...
The procedure I followed was this:
----------------------------------------
0. LOAD tun/tap KERNEL MODULE AND ACTIVATE IP FORWARD
modprobe tun
echo "1" > /proc/sys/net/ipv4/ip_forward
cat /proc/sys/net/ipv4/ip_forward
1 <--- it is active
1. Create a new bridge with this command:
brctl addbr br0
2. Copy eth0 configuration
3. Remove the IP address configuration from eth0 (here I lose connection)
ifconfig eth0 0.0.0.0
4. Add your network adapter to the bridge:
brctl addif br0 eth0
5. Transfer the network configuration used with eth0 to br0 (note this is
my working configuration I use for eth0, didn't invent it to try vbox) but
applied it instead to br0
ifconfig br0 192.168.1.18 netmask 255.255.255.0 mtu 1500
and add br0 to route
route add -net 192.168.1.0 netmask 255.255.255.0 dev br0
route add default gw 192.168.1.254 dev br0
6. Create vbox0 interface
VBoxAddIF vbox0 myusername br0
Then I enter the guest system (WinXP) and configure
IP: 192.168.1.12
subnet: 255.255.255.0
gateway: 192.168.1.254
DNS: ... (the same ones from my ISP as in NAT)
So I get connection in both ways host<->guest but still do output to
internet... well, in fact am unable to access 192.168.1.254 that is the
router and gateway, all other ip's and hosts are accessible, as if this ip
was blocked and in consequence theres no accessible gateway...
Any idea of what is going on?
Thanks for any idea
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
