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

["Robert Gubler" <rgubler@xxxxxxxxx>]

Hey Rajarshi,

So I discovered that assigning IP addresses to the vifX.Y interfaces on dom0 side didn't seem to do what I expected.  There may be something weird in the implementation of the vif module that is preventing it from working this way -- I really don't know.

Instead, try assign an IP address to the bridge device:

ifconfig test1 192.168.2.2 up

Hope this helps, let me know how it goes!

Regards,

Rob

On 11/3/06, rajarshi das <dazio_r@xxxxxxxxx> 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.

 

Thanks in advance,

Rajarshi

---

We have the perfect Group for you. Check out the handy changes to Yahoo! Groups.

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

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