WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: Qestion about the Xen network?

To: Samuel Thibault <samuel.thibault@xxxxxxxxxxxx>, Bei Guan <gbtju85@xxxxxxxxx>, Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: Qestion about the Xen network?
From: Bei Guan <gbtju85@xxxxxxxxx>
Date: Mon, 25 Oct 2010 09:06:20 +0800
Cc:
Delivery-date: Sun, 24 Oct 2010 18:07:24 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=/9HGs2PMX7VAzpRxERkk0LeHbnT+Q3Ku3Pf7Uxk7cEI=; b=E/znWy8nTagTY2Gp0XJrOTQ9JLpxHjw40fUIuhS9AvXjFU2eEUB1kBmHqWXjyP0VvZ zWlS4grTEpSyp94bAE7aN30tPFOKCXLmjG0C2PRUWPlyYPBOfu+X0G+ffxjuSwPvChJC 2SbrgZW6Oo3A3aaUSqzAEq7Od2lvyDJYcZFP0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=ZQVJbv9oiZYCCgd3YB/QL5ftxXD4l6umL5MzuzVwdPwCT6zvrOzr2wzQ/byIxDiLzg cZTfBzxS02GHlDnV7XvHj/LQcw4IF31pcIzhSDjuIOvWZQ5/kOifHu54wVYn2yOu+fGi k/+uZmnRQt6biOG6UV5KQdYHQ2tTcm7sZqmS4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20101023204952.GB24091@xxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTikju8iBPZ+RTNOnCsOfpCvQwcxi3c0+pHFb_6+F@xxxxxxxxxxxxxx> <AANLkTinasTvF_+fOmomuyEJ10c6RpD_dRKoBbxwEHKji@xxxxxxxxxxxxxx> <20101022150437.GF5227@xxxxxxxxxxxxxxxxxxxxxxx> <AANLkTin63QQ68jkZ9B1W-VZizOHt=hKbBUMmxLiHkWO7@xxxxxxxxxxxxxx> <AANLkTimaqsxJU26MMLTshVVCrRWZ2ZmNkL68NQS1u1gH@xxxxxxxxxxxxxx> <20101023204952.GB24091@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx


2010/10/24 Samuel Thibault <samuel.thibault@xxxxxxxxxxxx>
Bei Guan, le Fri 22 Oct 2010 23:50:54 +0800, a écrit :
> [root@localhost test1]# ./server 8081
>
> root@ubuntu:~/test1# ./client 192.168.1.192 8081
> agrv[1] = 192.168.1.192
> Connect Error:No route to host

Try with 192.168.122.1 instead.


192.168.122.1 also doesn't work.

root@ubuntu:~/test1# ./client 192.168.122.1 8081
agrv[1] = 192.168.122.1
Connect Error:No route to host

 

> :INPUT ACCEPT [0:0]
> :FORWARD ACCEPT [0:0]
> :OUTPUT ACCEPT [0:0]
> :RH-Firewall-1-INPUT - [0:0]
> -A INPUT -j RH-Firewall-1-INPUT
> -A RH-Firewall-1-INPUT -i lo -j ACCEPT
> -A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT
> -A RH-Firewall-1-INPUT -p 50 -j ACCEPT
> -A RH-Firewall-1-INPUT -p 51 -j ACCEPT
> -A RH-Firewall-1-INPUT -p udp --dport 5353 -d 224.0.0.251 -j ACCEPT
> -A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT
> -A RH-Firewall-1-INPUT -p tcp -m tcp --dport 631 -j ACCEPT
> -A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
> -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 21 -j ACCEPT
> -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 2049 -j
> ACCEPT
> -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
> -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 23 -j ACCEPT
> -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT
> -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 443 -j ACCEPT
> -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 25 -j ACCEPT
> -A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited
> -A FORWARD -j REJECT --reject-with icmp-host-prohibited

Apparently your firewall would reject connections actually.

Do you mean this one rejects the connection from VM ubuntu?
-A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited
 


Samuel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel