Go Back   HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials > Linux Forums > HOWTO-Related Questions

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Reply
 
Thread Tools Display Modes
  #1  
Old 9th June 2010, 22:15
Torsson Torsson is offline
Member
 
Join Date: Mar 2006
Posts: 62
Thanks: 0
Thanked 3 Times in 3 Posts
Default Xen DomU cannot go/ping external

Finaly i got my servers working. i have posted about that before and i found out that it was the NFS servers that was the problem, after uninstalling that and installing GlusterFS that workes just fine.

But to my problem.

My DomU's cannot ping or do anything external, not dns or ip, on either of the 2 Xen servers. The Dom0 can ping and do everything, and i have the same /etc/resovled.conf file on both the Dom0's and the DomU's. I can access the DomU's from outside.

i have seen that sometimes the DomU's can ping external but after a few sec/mins it fails again.

I also have problem reciving emails on both DomU's with postfix

This is the only thing that happens when the server tries to get a email. and i thing this has something to do about the resolve issue
Quote:
Jun 9 22:04:16 web2 postfix/smtpd[25787]: connect from unknown[209.85.161.45]
Jun 9 22:04:16 web2 postfix/smtpd[25787]: D53FE1666E: client=unknown[209.85.161.45]
Jun 9 22:04:16 web2 postfix/cleanup[25805]: D53FE1666E: message-id=<AANLkTilEmZmbPrXBoskq0EV3eNAkkgMiYByBPHKHJP19@ mail.gmail.com>
Jun 9 22:04:16 web2 postfix/qmgr[2369]: D53FE1666E: from=<something@gmail.com>, size=1642, nrcpt=1 (queue active)
Jun 9 22:04:46 web2 postfix/smtpd[25787]: disconnect from unknown[209.85.161.45]

Some info:
On the both DomU's i have 1 external IP eth0, and 1 virtual eth0:1 and a internal ip on eth1 connected with a crossed cable between the machines

iptables --list gives me this on the Dom0. could this problem be because its only the local ip that is forwared?. if so can someone tell me how to change this, i suck on iptables
Quote:
Chain FORWARD (policy ACCEPT)
target prot opt source destination
ACCEPT all -- web1 anywhere PHYSDEV match --physdev-in vif1.0
ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif1.0 udp spt:bootpc dpt:bootps
ACCEPT all -- 192.168.13.12 anywhere PHYSDEV match --physdev-in vif1.1
ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif1.1 udp spt:bootpc dpt:bootps
ACCEPT all -- web1 anywhere PHYSDEV match --physdev-in vif2.0
ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif2.0 udp spt:bootpc dpt:bootps
ACCEPT all -- 192.168.13.12 anywhere PHYSDEV match --physdev-in vif2.1
ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif2.1 udp spt:bootpc dpt:bootps
ACCEPT all -- web1 anywhere PHYSDEV match --physdev-in vif3.0
ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif3.0 udp spt:bootpc dpt:bootps
ACCEPT all -- 192.168.13.12 anywhere PHYSDEV match --physdev-in vif3.1
ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif3.1 udp spt:bootpc dpt:bootps
ACCEPT all -- web1 anywhere PHYSDEV match --physdev-in vif4.0
ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif4.0 udp spt:bootpc dpt:bootps
ACCEPT all -- 192.168.13.12 anywhere PHYSDEV match --physdev-in vif4.1
ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif4.1 udp spt:bootpc dpt:bootps
ACCEPT all -- web1 anywhere PHYSDEV match --physdev-in vif5.0
ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif5.0 udp spt:bootpc dpt:bootps
ACCEPT all -- 192.168.13.12 anywhere PHYSDEV match --physdev-in vif5.1
ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif5.1 udp spt:bootpc dpt:bootps
ACCEPT all -- web1 anywhere PHYSDEV match --physdev-in vif6.0
ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif6.0 udp spt:bootpc dpt:bootps
ACCEPT all -- 192.168.13.12 anywhere PHYSDEV match --physdev-in vif6.1
ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif6.1 udp spt:bootpc dpt:bootps
ACCEPT all -- web1 anywhere PHYSDEV match --physdev-in vif7.0
ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif7.0 udp spt:bootpc dpt:bootps
ACCEPT all -- 192.168.13.12 anywhere PHYSDEV match --physdev-in vif7.1
ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif7.1 udp spt:bootpc dpt:bootps

Last edited by Torsson; 9th June 2010 at 22:34.
Reply With Quote
Sponsored Links
  #2  
Old 9th June 2010, 23:32
Torsson Torsson is offline
Member
 
Join Date: Mar 2006
Posts: 62
Thanks: 0
Thanked 3 Times in 3 Posts
 
Default

Found the problem.
My interfaces file looked like this
Quote:
auto eth0
iface eth0 inet static
address 91.142.186.***
netmask 255.255.255.***
gateway 91.142.186.**
network 91.142.186.**

auto eth0:1
iface eth0:1 inet static
address 91.142.186.**
netmask 255.255.255.***
gateway 91.142.186.**
network 91.142.186.**
pre-up sysctl -p > /dev/null
and after changing it to this it started to work on both machines.
Quote:
auto eth0
iface eth0 inet static
address 91.142.186.***
netmask 255.255.255.***
gateway 91.142.186.**
network 91.142.186.**

auto eth0:1
iface eth0:1 inet static
address 91.142.186.**
netmask 255.255.255.***
pre-up sysctl -p > /dev/null
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
howto Windows domU on Xen3.3 - Ubuntu8.10 Xen Server dom0 murali.puligondla Suggest HOWTO 1 8th April 2009 13:09
how do I setup a Ubuntu domU guest on a CentOS / Fedora Core XEN server? SoftDux Installation/Configuration 0 27th July 2008 19:49
XEN: can't ping google.com from domU nomed Installation/Configuration 3 16th April 2008 22:25
Xen question, backup domU rayit HOWTO-Related Questions 2 25th August 2006 16:34
Is it possible to start a domU from Xen 2.x under Xen 3.0? Gurke666 Kernel Questions 1 25th April 2006 16:34


All times are GMT +2. The time now is 05:08.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.