similar to: Bridging on the blink with greater than 2 xen domains

Hi, I've been trying to get a couple of routers up after h/w failure. The border router is an OpenBSD firewall running NAT between the Internet and a DMZ like subnet, and in that a Linux antivirus server is running NAT to the LAN. When the client does a DNS query it reaches to the f/w where dns is running and is returned into the A/V server but never hits the 0.254 interface. (Shown by

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

On Sat, 18 Jul 2015 22:37:30 -0700 Gordon Messmer wrote: > On 07/18/2015 10:12 PM, Frank Cox wrote: > > Interesting. But since it's still exactly the same, it's still not > > working; it still fails in exactly the same way too. > > Yes, but that means you need to start with the standard troubleshooting > stuff. Do you have link? Is the Ethernet cable working?

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u1 Severity: important A few minutes after starting a domU, network access is no longer possible from and to it. This does not always happen and is not easily reproducible, but seems to occur in all newly started domUs from some point in time on. However, also restarting the dom0 does not necessarily prevent the problem. At the moment when

Using a default xen3.0.1 setup for dom0(rhel4 distro) and domUs (gentoo, rhel4, centos4.2 distros, ttylinux) with the domUs all having dhcp turned on, is there an easy way to tell from within the dom0 what ip addresses were assigned to the domUs after bootup? Toby Ford USi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Anyone ?|Another try and now with the info asked 4. |nl1cat wrote: | Hello.. | I have a somewhat "funny" setup. | I use the dosemulator Dosemu for running a dos based packetradio nodeprogram | called Xrouter. | I setup dosemu to use my eth1 (lan) nic and i bring up a device called dsn0. | (this is all running on Slackware 9.1 without X) | insmod /etc/dosemu/dosnet.o | sleep 2 | ifconfig

I just did a fresh install of centos 5.0 from cd, followed by yum update which installed 399 packages. No failures or errors that I can see. I have three nics in the box, but am only setting up one at the moment. The box can ping others in my network, but if I try ssh, telnet, ftp, etc I get this: [root at cm network-scripts]# ftp watchdog ftp: connect: No route to host ftp> [root at cm

Am 19.07.2015 um 08:13 schrieb Frank Cox: > On Sat, 18 Jul 2015 22:37:30 -0700 > Gordon Messmer wrote: [ ... ] > Do you see > any traffic if you run "tcpdump -nn -i eth1"? > > I see no traffic on eth1 with that command until I log into another session and type "ping google.com". Then I get this output: > > [root at audio ~]# tcpdump -nn -i eth1 >

On Wed, 2015-09-16 at 01:52 +0200, Arne Klein wrote: > [...] > At the moment when the network in the domU completely stops working, > there is the error message > [2178752.854380] vif vif-33-0 vif33.0: Guest Rx stalled > visible in dmesg in the dom0. This will therefore be a kernel issue not a hypervisor one. It sounds like a backend one given the issue is with both new and

what is weird is that i have not changed it for about 2 years, only apt update, upgrade. no other change, ipv4 and ipv6 address working correctly. now there is this bug, that i have not changed anything and suddenly, DLZ generates an unknown not connected , working, live ip4 and ip6. and all because it tried an nslookup p3x-dc.patrikx3.com that was the correct for over 2 years. the only thing that

Hi ALL, Here is a weird problem comfusing me for a long time. i''v installed xen 4.0.1 with linux kernel 3.1.0-rc9+ Everything works fine except i cannot ping to the gateway in a PVM domU. i''v installed bridge-utils and brctl show like this bridge name bridge id STP enabled interfaces eth0 8000.00219b480d56 no

I''m trying to shape traffic on a Devil-Linux box. This note was originally sent to their maillist, because the LARTC list appears to have been down for the past few days. My mailbox was just flooded with a half dozen or so confirmation requests in response to my repeated attempts to subscribe to this list. ---------- Forwarded message ---------- From: drew einhorn

On Sat, 18 Jul 2015 21:34:27 -0700 Gordon Messmer wrote: > Does the system work correctly if you don't run those "ip route" commands? It's exactly the same. And what I mean by exactly the same is EXACTLY the same. I rebooted the system which should clear out my route commands and whatnot, and discovered that everything (route -n and ip route show and whatnot) are exactly

Date: Wed, 27 Jun 2018 20:45:44 -0400 From: Jonathan Billings <billings at negate.org> > On Wed, Jun 27, 2018 at 05:14:06PM -0400, mark wrote: > >> I do see one option of "defgw macaddr" - is that supposed to be a MAC >> external to the server, or can I use the MAC of eth1 (or whatever the >> stupid, unrememberable name is)? > > As mentioned earlier,

Hi all, I''m running some tests with netem and I noticed some strange behaviour that looks like a bug: I''m pinging another machine and adding delay with netem. When I tell netem to give me a 10ms delay, it works fine. The problem is that when I ask for a 11ms delay, it gives me 20ms! It happens for any value between 11ms an 20ms, and it repeats for values over 20ms, now

Hi I used the command "ip -6 addr add 2001:DB8:CAFE:1111::12/64 dev eth0" to add ipv6 address and can see it in ifconfig but can't ping it Why? Thank you # ping6 2001:db8:cafe:1111::12 PING 2001:db8:cafe:1111::12(2001:db8:cafe:1111::12) 56 data bytes >From ::1 icmp_seq=1 Destination unreachable: Address unreachable >From ::1 icmp_seq=2 Destination unreachable: Address

Hi, Greg, Eddie, I found that in SR-IOV + HVM environment, ping latency depends on ping interval. The NIC is Intel 82576 (1000Mbps), server uses xen-4.0.1, domain-0 is kernel-2.6.32 and HVM is kernel-2.6.31. The server and client are connected through a 1000Mbps switch. The data is as following: # ping -i 1 192.168.0.21 PING 192.168.0.21 (192.168.0.21) 56(84) bytes of data. 64 bytes from

Hi folks, I read quite some posts about "Destination host unreachable" problems before, but none could help me to solve my issue. So here we go: This is what I am using: SUSE Linux Enterprise Desktop 10 SP1 - Current with all updates Network configuration of my dom0: foobar:~ # ip a 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd

Hi all, My setup is Debian testing dom0/domUs with a 2.6.32 pvops kernel from Debian unstable. Hypervisor is 3.4.2 from Debian testing. I use network- and vif- route with a default route in domU pointing to the nic because multiple IPs with bridge would trigger port shutdown on the switch (only one mac-address allowed per port). A subnet is routed to the dom0, which then knows which addresses the

Hao Yu Commercial Scale Out IBM T.J. Watson Research Center 1101 Kitchawan Rd/Route 134, Rm 36-019 Yorktown Heights, NY 10598-0218 914-945-1854, Email: yuh@us.ibm.com ----- Forwarded by Hao Yu/Watson/IBM on 10/31/2006 09:52 AM ----- Jimi