AW: Problems using xen 3.1 | bridged network

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Geofrey,

i compare our "ifconfig" results to your ones. I think everything is fine (have a look at the attachment). I tried the redhat package of xen and this works fine. A "lsmod" shows me that the needed bridge module is loaded. Maybe i forgot something? 
After starting the network-bridge script i got a message on console like "bridge firewalling registered" .... mmh, it can't be the iptables skript because this is offload ...

thx for you help
chris

-----Ursprüngliche Nachricht-----
Von: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] Im Auftrag von Geofrey Rainey
Gesendet: Donnerstag, 13. Dezember 2007 20:11
An: General Red Hat Linux discussion list
Betreff: RE: Problems using xen 3.1 | bridged network

Hi,

As you can see from the text file I have 2 ethernet bridges, now this
part is a little
Tricky. I think each bridge bridges the two physical ethernet devices 0
and 1 
(peth0, peth1), to the virtual ethernet devices (vifxx), which then send
the packets
To the appropriate device within the Xen configuration (eth0, eth1), and
on these devices
The IP addresses are bound.

What is the output of ifconfig for you?
 
Regards,
Geofrey Rainey
	
Systems Engineer
TVNZ Interactive Operations
D. +64 9 916 7178
M. +64 21 563 106


-----Original Message-----
From: redhat-list-bounces@xxxxxxxxxx
[mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Hartung,
Christopher
Sent: Friday, 14 December 2007 3:45 a.m.
To: General Red Hat Linux discussion list
Subject: Problems using xen 3.1 | bridged network

Hi @all,

i compiled xen 3.1 from source on my rh 5 box. Mostly everything works
fine but i've a little problem with our bridged network. If i startup
xend it'll startup the script network-bridge in background which will
map the bridge network and configure it. After this script is finished
my network doesn't work anymore (no tcp/ip connection from or to this
server). So in /var/log/messages i see messages like: "Interface
eth0.IPv4 no longer relevant for mDNS" and so on. Iptables is disabled. 

Do i've to configure an ip address for the xenbr0 if oder where is my
problem?

Thx for your answers

so long
chris


--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=subscribe
https://www.redhat.com/mailman/listinfo/redhat-list
==========================================================
For more information on the Television New Zealand Group, visit us
online at tvnz.co.nz 
==========================================================
CAUTION:  This e-mail and any attachment(s) contain information that
is intended to be read only by the named recipient(s).  This information
is not to be used or stored by any other person and/or organisation.
eth0      Link encap:Ethernet  Hardware Adresse 00:1A:64:25:DC:24  
          inet Adresse:10.100.0.132  Bcast:10.100.0.255  Maske:255.255.255.0
          inet6 Adresse: fe80::21a:64ff:fe25:dc24/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0 
          RX bytes:1028 (1.0 KiB)  TX bytes:7614 (7.4 KiB)

lo        Link encap:Lokale Schleife  
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:70 errors:0 dropped:0 overruns:0 frame:0
          TX packets:70 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0 
          RX bytes:18252 (17.8 KiB)  TX bytes:18252 (17.8 KiB)

peth0     Link encap:Ethernet  Hardware Adresse FE:FF:FF:FF:FF:FF  
          inet6 Adresse: fe80::fcff:ffff:feff:ffff/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:3 errors:0 dropped:0 overruns:0 frame:0
          TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000 
          RX bytes:900 (900.0 b)  TX bytes:9296 (9.0 KiB)
          Interrupt:21 Speicher:ce000000-ce011100 

vif0.0    Link encap:Ethernet  Hardware Adresse FE:FF:FF:FF:FF:FF  
          inet6 Adresse: fe80::fcff:ffff:feff:ffff/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:29 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0 
          RX bytes:7614 (7.4 KiB)  TX bytes:1098 (1.0 KiB)

xenbr0    Link encap:Ethernet  Hardware Adresse FE:FF:FF:FF:FF:FF  
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:32 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0 
          RX bytes:8054 (7.8 KiB)  TX bytes:0 (0.0 b)

-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

[Index of Archives]     [CentOS]     [Kernel Development]     [PAM]     [Fedora Users]     [Red Hat Development]     [Big List of Linux Books]     [Linux Admin]     [Gimp]     [Asterisk PBX]     [Yosemite News]     [Red Hat Crash Utility]


  Powered by Linux