|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-users] Trouble with Nat Xen setup
Hello Xen-Users!
   I've recently installed Xen on my stable amd64 Gentoo box. I set up a PV guest running unstable Gentoo, and it mostly works fine, except I haven't been able to get networking running. Networking works fine on the Dom0 over the WiFi card, which is what I normally use to connect to the internet. I tried bridging, was unable to get it to work, and someone pointed out to me some articles which suggest that bridging over WiFi depends on 4addr, which may work on some combinations of card/router, but is very finnicky overall. I followed the instructions at: and have not had success so far. This is what my iptables NAT rules look like: iptables -t nat -L Chain PREROUTING (policy ACCEPT) target   prot opt source        destination    Â Chain INPUT (policy ACCEPT) target   prot opt source        destination    Â Chain OUTPUT (policy ACCEPT) target   prot opt source        destination    Â Chain POSTROUTING (policy ACCEPT) target   prot opt source        destination    Â MASQUERADE Âall Â-- Âanywhere       anywhere    I've uploaded my Xen guest config file here:Âhttp://dpaste.com/0A46HSV. In my DomU /etc/conf.d/net I have just this one line currently: config_eth0="192.168.0.42". With that line I get the ip that I specified in my configuration file, and no errors: Xen Guest Gentoo ~Â# /etc/init.d/net.eth0 start Â* Bringing up interface eth0 Â*  192.168.0.42 ... Â[ ok ] Â*  Waiting for IPv6 addresses ... Â[ ok ] Without that line, I get a different ip, also with no errors: Xen Guest Gentoo ~ # /etc/init.d/net.eth0 start Â* Bringing up interface eth0 Â*  config_eth0 not specified; defaulting to DHCP Â*  dhcp ... Â*   Running dhcpcd ... dhcpcd[7502]: sending commands to master dhcpcd process Â[ ok ] Â*   received address Â[ ok ] Â*  Waiting for IPv6 addresses ... Â[ ok ] Xen Guest Gentoo ~ # ifconfig bond0: flags=5123<UP,BROADCAST,MASTER,MULTICAST> Âmtu 1500     inet6 fe80::403a:8a9c:e6d7:6094 Âprefixlen 64 Âscopeid 0x20<link>     ether 26:e3:dd:60:36:da Âtxqueuelen 0 Â(Ethernet)     RX packets 0 Âbytes 0 (0.0 B)     RX errors 0 Âdropped 0 Âoverruns 0 Âframe 0     TX packets 0 Âbytes 0 (0.0 B)     TX errors 0 Âdropped 0 overruns 0 Âcarrier 0 Âcollisions 0 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> Âmtu 1500     inet 169.254.15.51 Ânetmask 255.255.0.0 Âbroadcast 169.254.255.255     inet6 fe80::f93a:480:13b3:d902 Âprefixlen 64 Âscopeid 0x20<link>     ether 00:16:3e:28:61:89 Âtxqueuelen 1000 Â(Ethernet)     RX packets 40 Âbytes 27735 (27.0 KiB)     RX errors 0 Âdropped 0 Âoverruns 0 Âframe 0     TX packets 1511 Âbytes 595897 (581.9 KiB)     TX errors 0 Âdropped 0 overruns 0 Âcarrier 0 Âcollisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> Âmtu 65536     inet 127.0.0.1 Ânetmask 255.0.0.0     inet6 ::1 Âprefixlen 128 Âscopeid 0x10<host>     loop Âtxqueuelen 0 Â(Local Loopback)     RX packets 84 Âbytes 6288 (6.1 KiB)     RX errors 0 Âdropped 0 Âoverruns 0 Âframe 0     TX packets 84 Âbytes 6288 (6.1 KiB)     TX errors 0 Âdropped 0 overruns 0 Âcarrier 0 Âcollisions 0 I don't know why it would be getting that ip. That is not an ip that my router is configured to give out, and I don't have a dhcp service running on my host, at least not from what I can tell by looking at the output of rc-update show, which can be found here:Âhttp://dpaste.com/3DZMVE6 The ip of DomU looks different on the host side, which you can see here from the output of running ifconfig: http://dpaste.com/3FQ2HWG. That output looks the same even if I specify the ip address on the DomU side. I assume this is normal behavior.    I also took the time to check the logs, and the only one that has any kind of error is xen-hotplug.log: Âcat /var/log/xen/xen-hotplug.log xenstore-read: couldn't read path backend/vif/4/0/domain xenstore-read: couldn't read path backend/vif/4/0/domain xenstore-read: couldn't read path backend/vif/5/0/domain xenstore-read: couldn't read path backend/vif/5/0/domain xenstore-read: couldn't read path backend/vif/6/0/domain xenstore-read: couldn't read path backend/vif/6/0/domain xenstore-read: couldn't read path backend/vif/7/0/domain xenstore-read: couldn't read path backend/vif/7/0/domain xenstore-read: couldn't read path backend/vif/8/0/domain xenstore-read: couldn't read path backend/vif/8/0/domain xenstore-read: couldn't read path backend/vif/9/0/domain xenstore-read: couldn't read path backend/vif/9/0/domain xenstore-read: couldn't read path backend/vif/10/0/domain I don't know what could be causing this, or whether it's even relevant. Any help will be greatly appreciated. Thanks,                JMW  _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx http://lists.xen.org/xen-users
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |