|
|
|
|
|
|
|
|
|
|
xen-users
[Xen-users] Xen networking problem
I am trying out my first xen-project. I have used Debian's
xen-create-image to create a sarge image and I have a problem to get the
network going.
In the virtual machine (vmmail.sun.ac.za) I get the following:
sudo /etc/init.d/networking start
Setting up IP spoofing protection: rp_filter.
Configuring network interfaces...ifup: interface lo already configured
SIOCADDRT: Network is unreachable
Failed to bring up eth0.
done.
/etc/network/interfaces:
auto eth0
iface eth0 inet static
address 192.168.1.200
gateway 192.168.0.1
netmask 255.255.255.254
In dom0:
eth0 Link encap:Ethernet HWaddr 00:60:97:91:50:33
inet addr:146.232.129.117 Bcast:146.232.129.255 Mask:255.255.254.0
inet6 addr: fe80::260:97ff:fe91:5033/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:55819725 errors:0 dropped:0 overruns:5 frame:0
TX packets:14835707 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:606540272 (578.4 MiB) TX bytes:3479501616 (3.2 GiB)
Interrupt:5 Base address:0xe400
eth1 Link encap:Ethernet HWaddr 00:60:08:0F:ED:A6
inet addr:192.168.0.1 Bcast:192.168.1.255 Mask:255.255.254.0
inet6 addr: fe80::260:8ff:fe0f:eda6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:47 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2214 (2.1 KiB) TX bytes:720 (720.0 b)
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:11416 errors:0 dropped:0 overruns:0 frame:0
TX packets:11416 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2720010 (2.5 MiB) TX bytes:2720010 (2.5 MiB)
peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST NOARP MTU:1500 Metric:1
RX packets:766091 errors:0 dropped:0 overruns:0 frame:0
TX packets:115 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:51588542 (49.1 MiB) TX bytes:7908 (7.7 KiB)
Interrupt:11 Base address:0xe800
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:4426 errors:0 dropped:0 overruns:0 frame:0
TX packets:13492 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:337172 (329.2 KiB) TX bytes:936163 (914.2 KiB)
vif6.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:7 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:412 (412.0 b) TX bytes:252 (252.0 b)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet addr:192.168.1.200 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:6362 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:204832 (200.0 KiB) TX bytes:0 (0.0 b)
% sudo netstat -r
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 xenbr0
192.168.0.0 192.168.0.1 255.255.254.0 UG 0 0 0 eth1
192.168.0.0 * 255.255.254.0 U 0 0 0 eth1
146.232.128.0 * 255.255.254.0 U 0 0 0 eth0
default gigabit-router. 0.0.0.0 UG 0 0 0 eth0
In dom0:
% sudo iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
ACCEPT all -- vmmail anywhere PHYSDEV match
--physdev-in vif6.0
ACCEPT udp -- anywhere anywhere PHYSDEV match
--physdev-in vif6.0 udp spt:bootpc dpt:bootps
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
I have been trying to get some sort of understanding but the solutions
offered on the internet is so different and confusing that I have no
idea on how forward.
I have seen on the xensource-wiki that ip-forwarding of the kernel
should be switched off. I do not really understand why. So I have
experimented with that also without seeing that it made any difference.
At the moment the configuration in /etc/sysctl.conf is:
net.ipv4.conf.default.forwarding=0
net/ipv4/ip_forward=0
Reading the Xen-manual I see about networking: "the default setup should
work out of the box" ...
Not for me!
I am just trying to get a basic setup going. In the end I want the
xen-machines to utilise both the private network as well as the public
one. And I want to set up shorewall in dom0 which I understand is not
that straight forward.
Any pointers that can help met to understand what is going on here will
be appreciated.
Regards
Johann
--
Johann Spies Telefoon: 021-808 4036
Informasietegnologie, Universiteit van Stellenbosch
"Moreover if thy brother shall trespass against thee,
go and tell him his fault between thee and him alone;
if he shall hear thee, thou hast gained thy brother."
Matthew 18:15
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-users] Xen networking problem,
Johann Spies <=
|
|
|
|
|