Mike Power
2008-Sep-08 15:18 UTC
[Xen-users] Confused, how is network-nat supposed to work
So I want to create some VMs behind the protection of a nat. So I
switched my configuration to network-nat but it does not seem to work.
At this point I get:
mpower@dodtsair:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:22:15:3f:f2:0d
inet addr:75.101.5.130 Bcast:75.101.5.255 Mask:255.255.255.0
inet6 addr: fe80::222:15ff:fe3f:f20d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10441 errors:0 dropped:240470462890 overruns:0 frame:0
TX packets:11629 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14589578 (13.9 MB) TX bytes:975016 (952.1 KB)
Interrupt:18 Base address:0x4000
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:1392 errors:0 dropped:0 overruns:0 frame:0
TX packets:1392 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:143385 (140.0 KB) TX bytes:143385 (140.0 KB)
tap0 Link encap:Ethernet HWaddr 00:ff:5b:d6:e5:12
inet6 addr: fe80::2ff:5bff:fed6:e512/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:126 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:20083 (19.6 KB) TX bytes:468 (468.0 B)
vif3.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
inet addr:10.0.3.128 Bcast:0.0.0.0 Mask:255.255.255.255
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:34 overruns:0 carrier:0
collisions:0 txqueuelen:32
At this point I am too confused to do much more debugging. Given a dom0
and a domU what interfaces should I get with a nat. Is vif3.0 the
interface for dom0 and on the other side of that interface is the domU
emulated card?
Does that mean that the domU should be using 10.0.3.128 as the default
route?
If dhcpd is listening on vif3.0 is it expected that the domU can stand
up its interface with dhcp?
Right now I can ping vif3.0 which seems to be expected but the XP domU
can not pick up dhcp.
Also when i manually configure XP domU to use 10.0.3.127 and 10.0.3.128
as the gateway. I can neither bing 10.0.3.127 from dom0 or ping
10.0.3.128 from domU.
Mike Power
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users