RV: [Xen-users] Problem with bridge eth0. DomU access to Dom0 but doesn't access to Internet

["Diaz Corchero, Miguel Angel" <miguelangel.diaz@xxxxxxxxx>]

Rob, thanks for your answer I was worried with my bridge.

I have just had to disable spanning-tree and port-security on my cisco switch and now it's working successfully.

Regards
Miguel.


------------------------------------------------
Miguel A. Díaz Corchero
Unidad de Sistemas y Explotación
CETA-CIEMAT, Trujillo, Spain
miguelangel.diaz@xxxxxxxxx
------------------------------------------------



-----Mensaje original-----
De: Rob Aronson [mailto:riaronson@xxxxxxxxx]
Enviado el: lun 20/10/2008 5:47
Para: Diaz Corchero, Miguel Angel
Asunto: Re: [Xen-users] Problem with bridge eth0. DomU access to Dom0 but doesn't access to Internet

This is the third time I've heard about this type of failure. I have not
seen it first hand. The cases I heard of mentioned that it would work for
some time and then stop functioning without notice. I was trying to think of
things that could cause that, I was going to recommend doing some traces and
looking for problems with spanning tree.

On Sat, Oct 18, 2008 at 1:28 AM, Diaz Corchero, Miguel Angel <
miguelangel.diaz@xxxxxxxxx> wrote:

>  Hello.
>
> I have a problem with my bridge.
> My bridge eth0 is up, and if i do a ping from dom0 to domU it's successful.
> Too, if i do a ping from domU to dom0 it's successful, but i can't do a ping
> from domU to another machine into Lan.
>
> Thanks in advance.
>
>
> Below I have written the output of comands and SOs installed in Doms
>
>
> Dom0 is Centos5.2 x64 with Xen3.2
> DomU is Centos5.2 x64
> The brctl command returns this:
> bridge name     bridge id               STP enabled     interfaces
> eth0            8000.0014221e75c7       no              vif2.0
>                                                         peth0
> And ifconfig returns this:
> eth0      Link encap:Ethernet  HWaddr 00:14:22:1E:75:C7
>           inet addr:192.168.20.200  Bcast:192.168.20.255  Mask:
> 255.255.255.0
>           inet6 addr: fe80::214:22ff:fe1e:75c7/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:36794 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:3355 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:4916034 (4.6 MiB)  TX bytes:414648 (404.9 KiB)
>
> 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:219 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:219 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:22773 (22.2 KiB)  TX bytes:22773 (22.2 KiB)
>
> peth0     Link encap:Ethernet  HWaddr 00:14:22:1E:75:C7
>           inet6 addr: fe80::214:22ff:fe1e:75c7/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:157577 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:15352 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           RX bytes:16064251 (15.3 MiB)  TX bytes:1983064 (1.8 MiB)
>           Base address:0xecc0 Memory:fe6e0000-fe700000
>
> vif2.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:233 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:30458 errors:0 dropped:70 overruns:0 carrier:0
>           collisions:0 txqueuelen:32
>           RX bytes:11218 (10.9 KiB)  TX bytes:2067233 (1.9 MiB)
>
>
> And route command give me info below where 192.168.20.1 is the router.
>
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use
> Iface
> 192.168.20.0    *               255.255.255.0   U     0      0        0
> eth0
> 169.254.0.0     *               255.255.0.0     U     0      0        0
> eth0
> default         192.168.20.1    0.0.0.0         UG    0      0        0
> eth0
>
>
>
>
>
>  ---------------------------- Confidencialidad: Este mensaje y sus
> ficheros adjuntos se dirige exclusivamente a su destinatario y puede
> contener información privilegiada o confidencial. Si no es vd. el
> destinatario indicado, queda notificado de que la utilización, divulgación
> y/o copia sin autorización está prohibida en virtud de la legislación
> vigente. Si ha recibido este mensaje por error, le rogamos que nos lo
> comunique inmediatamente respondiendo al mensaje y proceda a su destrucción.
> Disclaimer: This message and its attached files is intended exclusively for
> its recipients and may contain confidential information. If you received
> this e-mail in error you are hereby notified that any dissemination, copy or
> disclosure of this communication is strictly prohibited and may be unlawful.
> In this case, please notify us by a reply and delete this email and its
> contents immediately. ----------------------------
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>



--
Rob Aronson
Storage, Virtualization and Orchestration Practice Manager, Novacoast
USA

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