Hi Tiago,
well ... as I said before .. I wouldn't set your eth0 mac address (on
dom0 ) to the broadcast one ...
Before setting the one on peth0, write it down and set eth0 (of your
Dom0, not the DomU's) to it.
That can be done easily on the init scripts (sorry, I use debian, so the
network scripts are completely different) :)
But the peth0 and xenbr0 mac addresses should be fe:ff:ff:ff:ff:ff =)
[]'s
Theo Diem
On Mon, 2006-10-30 at 12:37 -0300, Tiago Cruz wrote:
> Hello Theo, many thanks for your help! ;)
>
> On Mon, 2006-10-30 at 13:59 +0100, Theo Cabrerizo Diem wrote:
>
> > I got that message when my xenbr0/peth0 (yes, the real eth0, renamed by
> > xend scripts) interfaces (or whatever bridge name you are using) have a
> > MAC address configured in it.
>
> Well, I don't know exactly what's happen but I've configured only my
> eth0 on boot time, and put this on my rc.local:
>
> ip link set peth0 down
> ip link set peth0 mac fe:ff:ff:ff:ff:ff
> ip link set peth0 up
>
> ip link set xenbr0 down
> ip link set xenbr0 mac fe:ff:ff:ff:ff:ff
> ip link set xenbr0 up
>
> ip link set eth0 down
> ip link set eth0 mac fe:ff:ff:ff:ff:ff arp off
> ip link set eth0 up
>
>
> Now, after boot my machine don't crash any more, but the bridge stay
> without IP/MAC:
>
> xenbr0 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:159 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:14472 (14.1 KiB) TX bytes:0 (0.0 b)
>
> [root@xen ~]# brctl show
> bridge name bridge id STP enabled interfaces
> xenbr0 8000.feffffffffff no peth0
> vif0.0
>
> Anyway, look that is all working now :)
> Many thanks!
>
> - Tiago Cruz
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home