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] Xen domains not replying to arp requests


Thanks Braulio : that was exactly the problem , i got it sorted now ,

On Thu, 2006-02-09 at 11:09 -0200, Bráulio Gergull wrote:
> On Feb 09, 2006 05:42 AM, Digvijoy Chatterjee
> <digvijoy_chatterjee@xxxxxxxxxxx> wrote:
>
> >
> > Hi List,
> >
> > I am running FC4-2.6.11-1.1369_Xen0 as my Dom-0 and
> > FC4-2.6.11-1.1369XenU as my domains and Xen shipped with Fedora
> >
> > this is how the picture is :
> > [root@Aarya ~]# xm list
> > Name              Id  Mem(MB)  CPU  State  Time(s)  Console
> > Cluster-1          3      255        1      -b---     43.1        9603
> > Cluster-2          4      255        1      -b---     41.5        9604
> > Domain-0        0       256        0      r----    155.4       
> >
> > now my Domain-0 has two network cards , i am intending to setup a
> > virtual private network in this way
> >
> >                 Dom-0 eth0(172.25.243.133/27)----connected to outside
> > world( bcast 172.25.243.159)
> >                           /|
> >                            | (echo 1>> /proc/sys/net/ipv4_forward )
> >                 Dom-0 eth1(10.10.1.1/24)(bcast 10.10.1.255)
> >                             |
> >                             | 
> >                             |   
> >                             |     Cluster-2 eth0(10.10.1.3/24) ,bcast
> > 10.10.1.255 ,
> >                             |       
> >                       Cluster-1 eth0(10.10.1.2/24) ,bcast 10.10.1.255
> >
> > ping from Cluster-1 to Cluster-2 to vice versa is working , but i am
> > not
> > able to ping from the Dom-0 eth1 to Cluster-1/Cluster-2 or  the other
> > way,..
> > tcpdump output says the xen domains are not able to give arp replies
> > for
> > requests as you can see below . for example
> >      
> > [root@Cluster-1 ~]# ping 10.10.1.1 ( hangs forever , 100%
> > packet lost on interrupting)
> > PING 10.10.1.1 (10.10.1.1) 56(84) bytes of data.
> >
> > [root@Aarya ~]# tcpdump -i eth1 |grep '10.10.1.2'
> > tcpdump: verbose output suppressed, use -v or -vv for full protocol
> > decode
> > listening on eth2, link-type EN10MB (Ethernet), capture size 96 bytes
> > 12:57:06.682653 arp who-has 10.10.1.2 tell 10.10.1.1
> > 12:57:08.682647 arp who-has 10.10.1.2 tell 10.10.1.1
> > 12:57:09.682647 arp who-has 10.10.1.2 tell 10.10.1.1
> > 12:57:10.682648 arp who-has 10.10.1.2 tell 10.10.1.1
> > 12:57:12.682647 arp who-has 10.10.1.2 tell 10.10.1.1
> > 12:57:13.682648 arp who-has 10.10.1.2 tell 10.10.1.1
> > 12:57:14.682659 arp who-has 10.10.1.2 tell 10.10.1.1
> >
> > My Dom-0 ifconfig output is like this
> > [root@Aarya ~]# ifconfig
> > eth0      Link encap:Ethernet  HWaddr 00:0E:0C:5E:AE:AB 
> >           inet addr:172.25.243.133  Bcast:172.25.243.159
> > Mask:255.255.255.224
> >           inet6 addr: fe80::20e:cff:fe5e:aeab/64 Scope:Link
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:265697 errors:5 dropped:0 overruns:0 frame:5
> >           TX packets:220098 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:101248 txqueuelen:1000
> >           RX bytes:362665597 (345.8 MiB)  TX bytes:33895510 (32.3 MiB)
> >
> > eth1      Link encap:Ethernet  HWaddr 00:C0:9F:47:1A:6B 
> >           inet addr:10.10.1.1  Bcast:10.10.1.255  Mask:255.255.255.0
> >           inet6 addr: fe80::2c0:9fff:fe47:1a6b/64 Scope:Link
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:316967 errors:10 dropped:0 overruns:0 frame:10
> >           TX packets:723 errors:4 dropped:0 overruns:0 carrier:4
> >           collisions:553 txqueuelen:1000
> >           RX bytes:289280232 (275.8 MiB)  TX bytes:48548 (47.4 KiB)
> >           Base address:0xece0 Memory:fe2e0000-fe300000
> >
> > lo        Link encap:Local Loopback 
> >           inet addr:127.0.0.1  Mask:255.0.0.0
> >           inet6 addr: ::1/128 Scope:Host
> >           UP LOOPBACK RUNNING  MTU:16436  Metric:1
> >           RX packets:18715 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:18715 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:5463365 (5.2 MiB)  TX bytes:5463365 (5.2 MiB)
> >
> > vif3.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF 
> >           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:488 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:113 errors:0 dropped:5 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:46202 (45.1 KiB)  TX bytes:9648 (9.4 KiB)
> >
> > vif4.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF 
> >           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:573 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:101 errors:0 dropped:5 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:54616 (53.3 KiB)  TX bytes:8444 (8.2 KiB)
> >
> > xen-br0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF 
> >           inet addr:172.25.243.133  Bcast:172.25.243.159
> > Mask:255.255.255.255
> >           inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:919 errors:0 dropped:0 overruns:0 frame:0
> >          TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:74613 (72.8 KiB)  TX bytes:1596 (1.5 KiB)
> >
> > Can anyone help as to why the domains are not giving arp replies or
> > how
> > best to set up my network
> >
> > TIA
> > Digz
> >
>
>
> Hi Digz,
>
> It seems that your vif's are attached to the wrong bridge. What's the
> output of:
>
> # brctl show
>
> in dom0?
>
> Since I don't see any xen-br1 in your setup I assume they're attached to
> xen-br0, which is not what you want.
>
> For the sake of simplicity you can just switch eth0 and eth1 in Dom0,
> ie:
>
> eth0 -> 10.10.1.1
> eth1 -> 172.25.243.133
>
> Then your vif's would attach to eth0 (in fact to xen-br0) without
> touching the scripts.
>
> Otherwise you would have to change the scripts to create xen-br1 and
> attach eth1 and your vif's to it.
>
> []s,
> Braulio Gergull
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users



**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
for the use of the addressee(s). If you are not the intended recipient, please 
notify the sender by e-mail and delete the original message. Further, you are 
not to copy, disclose, or distribute this e-mail or its contents to any other 
person and any such actions are unlawful. This e-mail may contain viruses. 
Infosys has taken every reasonable precaution to minimize this risk, but is not 
liable for any damage you may sustain as a result of any virus in this e-mail. 
You should carry out your own virus checks before opening the e-mail or 
attachment. Infosys reserves the right to monitor and review the content of all 
messages sent to or from this e-mail address. Messages sent to or from this 
e-mail address may be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***

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

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