similar to: Ubuntu 8.04 Hardy Heron bridged networking xen connectivity loss

Running Samba mostly on Redhat 5 with version 3.5.4-0.83 Also failed on Debian 3.5.6 and Solaris with a 3.5 version. Logging details here are from Redhat case. We have a similar problem on all Unix/Linux systems using ADS as the backend authentication for samba shares on Unix/Linux. It was working before today and we didn't change anything. Today, any time we try smbclient or a Windows drive

Is this possible? Here is my situation, due to extrenuous circumstances I have one office(192.168.9.0) going through a NAT to another office (192.168.6.0 - which yet again goes through another NAT to the outside world). For the moment, there is no way to change this network config for various reasons. We're stuck like this for at least another 2 weeks. Previously, we didn't have any

Hi Michael: Sorry to brother. But I''ve been suffered this issue quite a long time. My test environment is 2.6.32.36 + xen 4.0.1 + bnx2, 2.3. Also cpu idle is disabled in grub. Grub info: title Red Hat Enterprise Linux Server (2.6.32.36xen) kernel /xen-4.0.1.gz iommu=off x2apic=off console=com1,vga com1=115200,8n1 noreboot cpuidle=0 cpufreq=none

Hello again, folks! I''m getting one strange problem with FC5 running on XEN 3.0.3 x64... The MRTG point to my machine with XEN running one absurd volume of output data sent (normal is around 6 MB/s) and when XEN is working we get 80 MB/s until my DRAC is alive... after this, the machine crash, DRAC stop do reply, swith stop do work together... Anyone knows whats happening now? ;)

Hi, If one sets xend to use network-bridge and there are no bridges already present then it seems that xend will clone eth0 to peth0, create xenbr0 and add peth0 and vif0.0 as ports on that bridge. If on the other hand xenbr0 is created in /etc/network/interfaces then xend will not do any of that peth0 stuff, nor will it add vif0.0 to xenbr0, yet (barring some changes in iptables rules) things

Before starting xend (xen 3.0) these are my correct network interfaces: eth0 Link encap:Ethernet HWaddr 00:14:5E:0A:53:04 inet addr:192.168.1.51 Bcast:192.168.1.255 Mask:255.255.255.0 eth1 Link encap:Ethernet HWaddr 00:14:5E:0A:53:05 inet addr:192.168.1.52 Bcast:192.168.1.255 Mask:255.255.255.0 lo Link encap:Local Loopback inet

Hello, my server has massive problems with my NIC. I got: "Detected Tx Unit Hang". At the moment I use 2.6.31 from Jeremy, does anyone know if it''s fixed in 2.6.32 or newer tree? Regards, Stefan Kuhne _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I come across some problem when using xen-4.1.1-rc1-pre from xen-4.1-testing tree and 2.6.32.36xen linux kernel from git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git. when I use ''xend restart'' , it hangs when kernel dmesg printing ''Bridge firewalling registered'' and the console show below messages: localhost# xend restart Nothing to flush. Cannot

xenconsole fix. reference of tty->count in xencons_close() is racy. It must be protected by tty_sem semaphore like con_close() in drivers/char/vt.c -- yamahata _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hello, Just did a fresh install of xen-4.0 and using the 2.6.31.13 dom0 kernel. I have 6 linux debian guests running, and on my host console i am getting these errors rolling pretty constantly. "Attempting to checksum a non-TCP/UDP packet, dropping a protocol 1 packet" I tried doing the ethtool -K eth0 tx off and same thing on peth0, using bridged mode for network config. Any tips?

Hello, Just did a fresh install of xen-4.0 and using the 2.6.31.13 dom0 kernel. I have 6 linux debian guests running, and on my host console i am getting these errors rolling pretty constantly. "Attempting to checksum a non-TCP/UDP packet, dropping a protocol 1 packet" I tried doing the ethtool -K eth0 tx off and same thing on peth0, using bridged mode for network config. Any tips?

Hello to all, I''ve got some guests that are really beginning to become bandwidth hogs. Some of them are file mirrors, some of them are just simple ftp backup servers. I''d like to try ebtables with my public bridges to try and tame things a bit, and was wondering if anyone has some snippets or scripts they would like to share. I''m new to ebtables, and am finding it a

Hi, Creating a new domain is a lot easier in opensuse 11. I follow the instruction on the website and build a virtual machine which uses opensuse 11 as well (I installed it from iso image). Everything works fine except the network. I cannot access the Internet from DomU. Here is some information. P.S. the DomU id is 1. "brctl show" in Dom 0: bridge name bridge id STP

During my attempts to get the latest bridge networking model working on my system, I often invoked ''network-bridge stop'' with total failure. Attached is an updated version that works. -Andrew signed-off-by: Andrew Theurer <habanero@us.ibm.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

It seems that with their specific Xen packages, Debian likes to go against the norm, and rather than calling the Xen bridging device something sensible like "xenbr0", they rename the main physical ethernet device "eth0" to "peth0" and create "eth0" as the Xen bridge (as far as I can tell, anyways). Anyone know where exactly they do this so I can reverse it?

When starting xend i see the following errors on the console. I''m running CentOS 5 as the operating system with kernel 2.6.32.18 from 4.0.1''s `make prep-kernels` Below is a log, the things i''m concerned with is the XENBUS errors and the deprecated iptables stuff. Any ideas whats going on here? ---------------------------------------------------- Bridge

*Hello,* I have installed Xen as Hypervisor with OpenSUSE running in Dom0. I want to use ovswitch (ovs) instead of the bridges that Xen created. In order to do so, I installed ovs in dom0 just like for the plain Linux. Xen has replaced eth0 with peth0, and has created a bridge named eth0. And eth0 is connected peth0 interface , vif2.0 interface (VM), and everything is working fine. Now I delete

Hi Everyone, In order to prevent DomU from entering promiscuous mode, is it just a matter of adding these 2 rules when the vif is created? # Accept packets leaving the bridge going to the domU only if # the destination IP for that packet matches an authorized IPv4 # address for that domU. iptables -A FORWARD -m physdev --physdev-out vif1.0 \ --destination 216.146.46.43 -j ACCEPT

Hi, I''ve installed xen 3.0.3 from packages (xen-linux-system) on a debian etch, and i''ve configured it with network-bridge script in the default way (netdev=eth0, bridge=xenbr0, etc...) which is ok for me. the problem I have: I cannot ping any outer machine from dom0 (nor any outer machine can ping me). It gives me a "Destination Host Unreachable" message that

Hi all, it''s happening a strange thing: After I boot the xen dom0 network is unavailable: I have to unload the network modules and load it again ( rmmod / modprobe) and execute a service network restart) This is strange, what do you suggest me to check? Thanks Marco Strullato _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com