similar to: domU network packets get lost on the way to dom0

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 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

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

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.

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

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

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

Hello, I use a script network-multi vlan and network-bridge-vlan for multiple VLANs in domu. Several domu uses the bridge vlanbr30. Need to dom0 as was in this vlan''e. How? I tried to put a bridge interface ip, but with him until the rest domu in vlanbr30 not get through. How to understand the need to create a virtual interface (vifx.y) and add it to the bridge vlanbr30. How?

> > Just to be doubly clear, do you mean that the name is compared at the > > time the rule is submitted, or at the time it is evaluated? > > It''s the latter. See ip_packet_match in net/ipv4/netfilter/ip_tables.c > for example. Wild -- that''s not what I''d have guessed. I suppose it allows you to insert rules for interfaces that don''t

Hi All, I am trying to create the following configuration: dom0 |---eth2 Masquerading interface to OUTSIDE | |---eth0 LAN:10.0.1.1/24 | |---eth1 WLAN:10.0.2.1/24 | |---xenbr0 DMZ:10.0.3.1/24 | |-- vifX.0 -- eth0 domU:10.0.3.2 I would like to do it this way because I will not be using xen all the time on this machine. I created a network-virtual script which

I am using nat for guest domU with dhcp running on dom0. on creating the domU xend-debug.log reports: Can''t open /etc/dhcp3/dhcpd.conf: Permission denied and dhcp fails. The vif0.X is created and the dhcp.conf is modified according to the randomly generated mac address and the address of vifx.0. I think the problem lies in the vif-nat script in synchronization during dhcpd.conf

Hello! I use kernel-xen.x86_64 2.6.20-2931.fc7 virt-manager.x86_64 0.4.0-2.fc7 xen-libs.x86_64 3.1.0-2.fc7 xen.x86_64 3.1.0-2.fc7 with FC7. I want bridged networking for my virtual machines, so I create fully virtualized DomUs with virt-manager and add eth0 (bridged, as ethernet device). When I

An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20120322/a53547cf/attachment.htm>

On 4/18/06, David Goodlad <dgoodlad@gmail.com> wrote: > Hi all > > I can''t seem to get networking to function at all in hvm/vmx guests. > I''ve tried both winxp and linux guests, and neither can get any > traffic through their network devices. The device _is_ detected as a > pcnet32 card, which is fine, but I see 0 packets going through, even > at the

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,

Already reported.... http://bugs.centos.org/view.php?id=2516 >Subject: RE: [CentOS-virt] xenbr0 isn't created anymore >To: <centos-virt at centos.org> >Message-ID: > <E2BB8074E5500C42984D980D4BD78EF9022A704E at MFG-NYC-EXCH2.mfg.prv> >Content-Type: text/plain; charset="us-ascii" > >Kai Schaetzl wrote: >> >> Somehow I managed