similar to: RE: [PATCH] Re: network-bridge scriptbreaks networkconnectivity

https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=84 ------- Additional Comments From tv@debian.org 2003-12-26 18:12 ------- Just wanted to note that http://lists.netfilter.org/pipermail/netfilter-devel/2003-September/012316.html http://lists.netfilter.org/pipermail/netfilter-devel/2003-September/012305.html talk about the same subject, that the same bug triggers an ugly crash

Package: xen-utils-common Version: 3.2.0-2 Hello We used the script "network-bridge" on our Xen servers based on "etch" (xen-utils-common 3.0.3-0-2) to setup bridge configuration. This script created a bridge "xenbr0", renamed "eth0" to "peth0", renamed "veth0" to "eth0" and added "peth0" and "vif0.0" to

Package: xen-utils-3.0 Version: 3.0.2+hg9656-1 Severity: normal My setup is a basic one. No changes to the /etc/xen/* files. Network in a domU works perfectly fine. But, after shutdowning a domU, I can see the following lines in /var/log/debug: May 6 10:31:45 vaio logger: /etc/xen/scripts/vif-bridge: offline XENBUS_PATH=backend/vif/18/0 May 6 10:31:46 vaio logger: /etc/xen/scripts/vif-bridge:

Hi, I''ve a working xen 3.0.2 booting a gentoo linux on Dom0. I have setup a Windows XP in a DomU OK with no problems except the network!! My problem is that I wanted to give a working network interface on the DomU and the best I could. making the windows detect an network adapter, was putting: vif = [''type=ioemu''] I also tryied: vif = [''type=ioemu,

Hi, I am experiencing a strange network problem. It looks like some packets get lost on the way from frontend network device in domU to the backend vifx.x in dom0. But first my configuration: - Xen 3.4.0 from the gentoo ebuild and the pvops dom0 kernel from jeremy/xen.git - The system has two physical network interfaces called gblan (Gigabit Ethernet) and felan (Fast Ethernet) - Two network

Has anyone managed to combine bridged network model and SNAT? I have a machine that just ssh''s into other boxes and updates via rsync a copy of their filesystems. I figured I could stage a xen VM for this server with a private IP address and do SNAT and "routing" via the dom0 box, but I get a wierd "Performing cross-bridge DNAT requires IP forwarding to be enabled"

Hi All, I have a weird issue I''m not sure how to solve.  I''ve got Xen 3.2.1 working under RHEL 5.2 x86_64 just fine.  I fired off a CentOS 5.2 PV install and everything went smoothly... except that when I fire up the PV, the tap0 for bridging isn''t being created.  This results in the CentOS 5.2 domU''s bridged eth0 only being able to ping the RHEL5

http://bugzilla.netfilter.org/show_bug.cgi?id=751 Summary: IPv6 bridging bug Product: iptables Version: unspecified Platform: x86_64 OS/Version: Gentoo Status: NEW Severity: normal Priority: P3 Component: ip6tables AssignedTo: netfilter-buglog at lists.netfilter.org ReportedBy: david at

Hi, in the official XenNetworking ( http://wiki.xensource.com/xenwiki/XenNetworking ) i didn''t find reported how the NAT configuration works with xen. Does anybody know how the vifX.Y (10.X.X.128), gateway of any domU ethX (10.X.X.1) talk with the real ethX of the dom0? Thanks Enrico _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Package: xen-utils-common Version: 4.1.2-3 Severity: normal When configurating a duplicate custom vifname for interfaces in the Xen dom0 that are added to a bridge (which is obviously a configuration error), the hotplug scripts fail silently to rename the new vifX.0 to the custom vifname, if it's already existing. The result of this, is that the domU will start normally, but no network

Hi, I'm having trouble applying ebtables-brnf-3_vs_2.4.22.diff to 2.4.22-1.2166.nptl. Applying the patch did not go well. Can anyone help me with this? TIA. Andy Here is the output: [root@specwall linux-2.4.22-1.2166.nptl]# patch -p1 < ../ebtables-brnf-3_vs_2.4.22.diff patching file net/bridge/br_private.h Reversed (or previously applied) patch detected! Assume -R? [n] n Apply anyway?

Hello guys I have the following problem with xen 3.0.1 compiled from sources on Debian Sarge, kernel 2.6.12.6 which can be easily reproduced at least on my installation: after I log in to domU console or via ssh and run "shutdown" I get deadlocked network interface with error message: unregister_netdevice: waiting for vifX.0 to become free. Usage count = n After this happen I

Package: xen-utils-common Version: 3.0.3-0-2 Severity: normal I cannot find a use the network-nat and vif-nat provided in the general case, where I'd like to NAT between vifx.0 and ethx interfaces. I have setup the following in /etc/xen/xend-config.sxp : ## Use the following if network traffic is routed with NAT, as an alternative # to the settings for bridged networking given above.

Hi! As noted by Chris Rankin on a mail to netfilter-devel and to the linux-kernel mailing list (subject: 2.6.12: connection tracking broken?), there is a problem with the connection tracking of iptables when one of the interfaces is a bridge. On my tests here I have setup a connection between two machines using a real interface (eth0) and then the same setup using a bridge interface (br0) to

Package: xen-utils-4.17 Version: 4.17.1+2-gb773c48e36-1 Severity: important Dear Maintainers, On one of our domUs we discovered that the network interface names were wrongly assigned since recreating the domU after an upgrade to bookworm. If over 10 network interfaces are configured the mapping (dom0) vifX.10 <-> eth10 (domU) does not apply anymore. Instead the interfaces on dom0 are

Dear Professor I have read your questions in the website on Doubly non-central F-distribution. I am looking for source code for evaluating this function now. I have matlab code but it's only accurate up to the 4th decimal point. Dataplot is more accurate, but it is not user friendly as you only can evaluate one function at a time. So I would like to know do you have found any R code for

Hi, I've been testing the Debian packages ahead of the Debian 7 release (which is very imminent) I believe this is a serious bug[1] in the package, as it appears that HVM networking is broken, or at the very least, requires some undocumented configuration step Specifically: - I can start the HVM domU without any vif - if I attach a vif, the domU will not start Looking at

# HG changeset patch # User Ian Campbell <ian.campbell at citrix.com> # Date 1341941699 -3600 # Node ID efb7fee3573b68e895de0341dd67df83cb68acc6 # Parent ca5c306052791edf6d96da3f80aecd750b86a5e4 hotplug: vif: fail if a duplicate vifname is used. This is based on a patch from Hans van Kranenburg in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658305. Quoting that bug report: When

Hi, this is propably bridge related and not really a xen problem, but it might help someone: Some of our domUs are not able to arp. Arp -n show (incomplete), and doing a tcpdump shows, that on the dom0''s eth0 the arp request goes out, the response comes in, but on the vifX.0 interface the arp response is gone. dom0# tcpdump -ni eth0 arp who-has 10.32.2.51 tell 10.32.7.70 arp reply

I have found this problem while trying to see the active rules on IPTABLES: [root@worf root]# iptables --list /lib/modules/2.4.7-10/kernel/net/ipv4/netfilter/ip_tables.o: init_module: Device or resource busy Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.7-10/kernel/net/ipv4/netfilter/ip_tables.o: insmod