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-users

Re: [Xen-users] dom0 can not ping dom3

To: rajarshi das <dazio_r@xxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] dom0 can not ping dom3
From: Brad Plant <bplant@xxxxxxxxxxxxxx>
Date: Sat, 04 Nov 2006 09:54:57 +1100
Delivery-date: Fri, 03 Nov 2006 14:55:40 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20061103143627.47749.qmail@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <20061103143627.47749.qmail@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.7 (X11/20061005)
rajarshi das wrote:
> Hi,
>    
>   I am running SLES10. I did the following:
>    
>   $ brctl addbr test1
>   $ ifconfig test1 up
>   $ xm create -c myconfig # myconfig contains an entry vif=[ 'bridge=test1' ]
>    
>   # in dom0
>   $ ifconfig vif3.0 192.168.0.3 
>   $ ping 192.168.0.4 &
>   $ tcpdump -i vif3.0
>    
>   tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
>   listening on vif3.0, link-type EN10MB (Ethernet), capture size 96 bytes
>   18:47:28.075979 IP 192.168.0.3 > 192.168.0.4: ICMP echo request, id 22552, 
> seq 8, length 64
>   18:47:29.076063 IP 192.168.0.3 > 192.168.0.4: ICMP echo request, id 22552, 
> seq 9, length 64
>   18:47:30.076092 IP 192.168.0.3 > 192.168.0.4: ICMP echo request, id 22552, 
> seq 10, length 64
>   18:47:31.076162 IP 192.168.0.3 > 192.168.0.4: ICMP echo request, id 22552, 
> seq 11, length 64
>   18:47:32.076217 IP 192.168.0.3 > 192.168.0.4: ICMP echo request, id 22552, 
> seq 12, length 64
>   18:47:33.076280 IP 192.168.0.3 > 192.168.0.4: ICMP echo request, id 22552, 
> seq 13, length 64
>   18:47:34.076344 IP 192.168.0.3 > 192.168.0.4: ICMP echo request, id 22552, 
> seq 14, length 64
>   ......
>    
>    
>   # in dom3
>   $ ifconfig eth0 192.168.0.4
>   $ tcpdump -i eth0
>   NET: Registered protocol family 17
>   device eth0 entered promiscuous mode
>   tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
>   listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
>   18:47:39.035054 IP 192.168.0.3 > 192.168.0.4: ICMP echo request, id 22552, 
> seq 19, length 64
>   18:47:40.035114 IP 192.168.0.3 > 192.168.0.4: ICMP echo request, id 22552, 
> seq 20, length 64
>   18:47:41.035158 IP 192.168.0.3 > 192.168.0.4: ICMP echo request, id 22552, 
> seq 21, length 64
>   18:47:42.035226 IP 192.168.0.3 > 192.168.0.4: ICMP echo request, id 22552, 
> seq 22, length 64
>    
>   .......
>    
>   A similar problem was posted on this list before, but the solution (doing a 
> ifconfig <bridge> up) did not work in my case. 
>    
>   Please suggest on how to get dom0 (vif3.0) to ping dom3(eth0) in this case.

Hi Rajarshi,

Try running "ethtool -K eth0 tx off" in your dom0.

Cheers,

Brad

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

<Prev in Thread] Current Thread [Next in Thread>