|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] can't connect to dhcp after bridging
Okay, your ifconfig and brctl output looks fine...something else is going on,
and I'm short on ideas right now...
>>> Emanuele Ianni 11/05/10 7:44 PM >>>
Can you be more specific? How do I check it? My ifconfig is
eth0 Link encap:Ethernet HWaddr 00:13:77:BC:E5:67
inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::213:77ff:febc:e567/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:21108 errors:0 dropped:0 overruns:0 frame:0
TX packets:14977 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:27331120 (26.0 MiB) TX bytes:1245843 (1.1 MiB)
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:3126 errors:0 dropped:0 overruns:0 frame:0
TX packets:3126 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6578733 (6.2 MiB) TX bytes:6578733 (6.2 MiB)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:21079 errors:0 dropped:0 overruns:0 frame:0
TX packets:15072 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:27325244 (26.0 MiB) TX bytes:1263008 (1.2 MiB)
Interrupt:253 Base address:0xe000
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:14977 errors:0 dropped:0 overruns:0 frame:0
TX packets:21108 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1245843 (1.1 MiB) TX bytes:27331120 (26.0 MiB)
virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:51 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:9034 (8.8 KiB)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:267 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:38818 (37.9 KiB) TX bytes:0 (0.0 b)
And brctl show gives:
[root@localhost ~]# brctl show
bridge name bridge id STP enabled interfaces
virbr0 8000.000000000000 yes
xenbr0 8000.feffffffffff no peth0
vif0.0
2010/11/5 Nick Couchman
> When you configure the bridge, you need to make sure that the DHCP
> client is running on the bridge interface, not on the physical
> interface. Xend will actually make this change for you automatically if
> you allow it. In your case, the DHCP client, IP address, and all of the
> routes need to be on eth0 and not peth0. Also, of course, check the
> obvious things, like brctl show to make sure that peth0 is a member of
> the eth0 bridge.
>
> -Nick
>
> On Fri, 2010-11-05 at 11:08 +0100, Emanuele Ianni wrote:
> > Hi! I'm sorry if this sounds like a really stupid question but I
> > started today for the first time using Xen. I'm using it on a fresh
> > installation of Debian Lenny.
> > I followed this tutorial
> > http://www.howtoforge.com/virtualization-with-xen-on-debian-lenny-amd64but
> > the 686 version, non the amd64.
> >
> > The problem is that after enabling the bridge it can't seem able to
> > find my router dhcp server. Is there something I'm missing? On
> > ifconfig I have eth0, peth0 and lo.
> >
> > --
> > Distinti Saluti
> > Emanuele Ianni
> >
> > Le informazioni e gli allegati contenuti in questa e-mail sono
> > considerati confidenziali e possono essere riservati. Qualora non
> > foste il destinatario, siete pregati di distruggere questo messaggio e
> > notificarmi il problema immediatamente. In ogni caso, non dovrete
> > spedire a terze parti questa e-mail. Vi ricordo che la diffusione,
> > l'utilizzo e/o la conservazione dei dati ricevuti per errore
> > costituiscono violazione alle disposizioni del D.L. n. 196/2003
> > denominato "Codice in materia di protezione dei dati personali"
> >
> > The information in this e.mail and in any attachements is confidential
> > and may be privileged. If you are not the intended recipient, please
> > destroy this message and notify the sender immediately. You should not
> > retain, copy or use this e.mail for any purpose, nor disclose all or
> > any part of its contents to any other person according to the Italian
> > Legislative Decree n. 196/2003.
>
>
>
> --------
> This e-mail may contain confidential and privileged material for the sole
> use of the intended recipient. If this email is not intended for you, or
> you are not responsible for the delivery of this message to the intended
> recipient, please note that this message may contain SEAKR Engineering
> (SEAKR) Privileged/Proprietary Information. In such a case, you are
> strictly prohibited from downloading, photocopying, distributing or
> otherwise using this message, its contents or attachments in any way. If
> you have received this message in error, please notify us immediately by
> replying to this e-mail and delete the message from your mailbox.
> Information contained in this message that does not relate to the business
> of SEAKR is neither endorsed by nor attributable to SEAKR.
>
--
Distinti Saluti
Emanuele Ianni
Le informazioni e gli allegati contenuti in questa e-mail sono considerati
confidenziali e possono essere riservati. Qualora non foste il destinatario,
siete pregati di distruggere questo messaggio e notificarmi il problema
immediatamente. In ogni caso, non dovrete spedire a terze parti questa
e-mail. Vi ricordo che la diffusione, l'utilizzo e/o la conservazione dei
dati ricevuti per errore costituiscono violazione alle disposizioni del D.L.
n. 196/2003 denominato "Codice in materia di protezione dei dati personali"
The information in this e.mail and in any attachements is confidential and
may be privileged. If you are not the intended recipient, please destroy
this message and notify the sender immediately. You should not retain, copy
or use this e.mail for any purpose, nor disclose all or any part of its
contents to any other person according to the Italian Legislative Decree n.
196/2003.
--------
This e-mail may contain confidential and privileged material for the sole use
of the intended recipient. If this email is not intended for you, or you are
not responsible for the delivery of this message to the intended recipient,
please note that this message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information. In such a case, you are strictly
prohibited from downloading, photocopying, distributing or otherwise using this
message, its contents or attachments in any way. If you have received this
message in error, please notify us immediately by replying to this e-mail and
delete the message from your mailbox. Information contained in this message
that does not relate to the business of SEAKR is neither endorsed by nor
attributable to SEAKR.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |