Hi Pablo,
After doing all the setting using your script:
Even with setting the ip address in windows manually,
I cannot get windows guest to get on the internet.
Windows does connect with tap 0 (i.e windows can ping tap0
ip address).
But I don't get any name resolution.
So, I cannot get out on the internet.
My default name resolver on linux is 192.168.1.1
which is my router and works just fine for linux.
Setting windows' two resolvers to 192.168.0.1 and 192.168.1.1
also does not yield positive name resolution.
Here is the output of some relevant commands on linux
#ifconfig
br0 Link encap:Ethernet HWaddr 00:03:0D:15:2B:9E
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::203:dff:fe15:2b9e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14188 errors:0 dropped:0 overruns:0 frame:0
TX packets:7496 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:18270317 (17.4 MiB) TX bytes:541571 (528.8 KiB)
eth0 Link encap:Ethernet HWaddr 00:03:0D:15:2B:9E
inet6 addr: fe80::203:dff:fe15:2b9e/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:15101 errors:0 dropped:0 overruns:0 frame:0
TX packets:9251 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:18824196 (17.9 MiB) TX bytes:857305 (837.2 KiB)
Interrupt:19 Base address:0xd800
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:14612 errors:0 dropped:0 overruns:0 frame:0
TX packets:14612 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:115903559 (110.5 MiB) TX bytes:115903559 (110.5 MiB)
tap0 Link encap:Ethernet HWaddr 00:FF:32:0D:59:99
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::2ff:32ff:fe0d:5999/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:422 errors:0 dropped:0 overruns:0 frame:0
TX packets:315 errors:0 dropped:35 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:43556 (42.5 KiB) TX bytes:39174 (38.2 KiB)
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 br0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 tap0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 br0
# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.00030d152b9e no eth0
virbr0 8000.000000000000 yes
# cat /etc/resolv.conf
; generated by /sbin/dhclient-script
search localhost.localdomain
nameserver 127.0.0.1
nameserver 192.168.1.1
# cat /proc/sys/net/ipv4/ip_forward
1
# cat /proc/sys/net/ipv4/conf/br0/proxy_arp
1
Cheers,
JD
Pablo Sanchez wrote:
On Friday 07 March 2008 at 2:40 pm, JD penned
about "Re: [vbox-users] multiple real interfaces and bridging"
Thank you Pablo,
You're welcome.
I guess I can skip iptables thing, because my firewall
is disabled. Is this Right?
Correct.
Also, do I have to enable IP forwarding by
echo 1 > /proc/sys/net/ipv4/ip_forward ??
Yes you do ... well, I did it ... try it with and if it works, then
try without. :) I can't recall why I popped that in there.
Cheers,
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
