similar to: Bug#679533: Traffic forwarding issue between Xen domU/dom0 and ovs

retitle Traffic forwarding issue between Xen domU/dom0 thanks This week again this bug occurred again so we are trying to create some kind of reproduce algorithm. First we've created two virtual machines named koekiemonster.bofh.hq.mendix.net and netappsim.bofh.hq.mendix.net. We've added 29 vifs to koekiemonster.bofh.hq.mendix.net. During this tests we've always had a ping

Kevin, Would you mind taking a look at #679533 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679533) and give some feedback about how similar this issue is to your report in #631102 here? There was a hint 631102 might be similar, but from the text in this bug report it's not clear to me if this is about the same issue. Maybe you could comment on it. First results of a big shoot-out

Hi all, I have been testing network throughput and latency and I was wondering if my measurements are as expected. For the test, I used Fedora 17 for both host and guest, using kernel 3.5.2-3.fc17.86_64. Pinging an external server on the LAN from the host, using a gigabit interface, the results are: # ping -c 10 172.16.1.1 PING 172.16.1.1 (172.16.1.1) 56(84) bytes of data. 64 bytes from

Hi all, I have been testing network throughput and latency and I was wondering if my measurements are as expected. For the test, I used Fedora 17 for both host and guest, using kernel 3.5.2-3.fc17.86_64. Pinging an external server on the LAN from the host, using a gigabit interface, the results are: # ping -c 10 172.16.1.1 PING 172.16.1.1 (172.16.1.1) 56(84) bytes of data. 64 bytes from

hi all , i use ubuntu 12.04 with xcp , all config run very well except vlan i use xe network-create and xe vlan-create to build vlan 3000 then startup a vm in this network, xapi0 fakebridge and vif1.0 all looks well, use ovs-vsctl list port i can see xapi0 and vif1.0 have beed taged with 3000 but i can not access the internent~~~ somebody can help me with this? thanks.

A huge thank you to mario from the ''openvswitch on Xen 4.1'' post. I was having some trouble with using openvswitch with Xen 4.1 (I''m currently migrating from 4.0.1) until I saw his post and noticed that the xl.conf needed the full path to the networking script. Made this change and all is good now. Thank you. I would like to contribute what I have for using

Hello everyone. After all the problems I had demoting my DC and managed it to work again, it was working for only a week. Now i am getting this messages on the log: [2014/07/22 16:13:11.745783, 0] .../source4/librpc/rpc/dcerpc_util.c:681(dcerpc_pipe_auth_recv) Failed to bind to uuid e3514235-4b06-11d1-ab04-00c04fc2dcd2 for e3514235-4b06-11d1-ab04-00c04fc2dcd2 at

HI, I''m having trouble with a debian etch HVM domU inside a dom0 domu >From domU, I try to ping gateway, but response time change if tcpdump is writing to standard output. Ping without tcpdump running has a 4 ms time. While tcpdump is writing in stdout, in another terminal: # ping -n -c20 10.12.6.1 PING 10.12.6.1 (10.12.6.1) 56(84) bytes of data. 64 bytes from 10.12.6.1: icmp_seq=1

Am 22.06.2020 um 17:41 schrieb Marek Greško: Hi > try pinging your sip peer ip address following way: > > ping -n -M do -s 1300 -i 0.1 -c 100 ${ipaddress} > > Post several lines and the statistics. root at bpi:/etc/asterisk# ping -n -M do -s 1300 -i 0.1 -c 100 tel.t-online.de PING tel.t-online.de (217.0.128.133) 1300(1328) bytes of data. 1308 bytes from 217.0.128.133:

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-2 Severity: grave File: xen Justification: renders package unusable Debian Squeeze Dom0, up to date. Networking is handled by OS scripts, such that br0 and br1 are bridge interfaces. Without warning, the DomU (Ubuntu 10.04 LTS) loses inbound connectivity. It tends to happen after several hours. It doesn't seem to be affected by throughput

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

Hello, I''m using Linux kernel 2.6.x and tc (from iproute2 package). I''m trying to use HTB or HFSC scheduler in order to limite the rate of outgoing packets and also in order to minimiez delay for RTP stream. But I didn''t suceed in having this 2 QoS services working. I use Iptables in order to classify packets. Here is my HFSC conf. In fact the pings that i send from

I'm not *entirely* sure but this began happening at about the time I installed the latest kernel updates for CentOS 5.1 (kernel-2.6.18-53.1.6.el5.i686.rpm from January 24). Shortly before that I changed the encryption on my wireless router and switched from ndiswrapper back to the standard bcm43xx driver, but I'm pretty sure the network was OK before that update for the simple reason that

Hi, There seems to be a problem with the timer resolution on x86_64. This is clear in ping results - I don't know if it's just a ping problem or if it manifests elsewhere as well. It does also affect mtr and traceroute times. I guess it's more a kernel issue than a CentOS problem, but is anyone else seeing the same? Ping results have a resolution of 10ms - so a ping <10ms

Hello Thilo, What did you find superior with CBQ-wondershaper over HTB-wondershaper? We have not been using wondershaper specifically but our simple tests so far seem to show that htb is much easier to configure for a given target shape (i.,e accurate) compared to CBQ. Torsten -----Original Message----- From: Thilo Schulz [mailto:arny@ats.s.bawue.de] Sent: Saturday, June 14, 2003 8:55 AM To:

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

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

faced this exact same problem a few times on more than one servers and it was 1) dialplan issue which was not hanging up the zap channels correctly 2) using more than 8 spans on a server. Asterisk can't handle more than 96 zap channels on T1s. FXO/FXS combinations can vary the number of spans but if you know what I mean by spans, in production don't use more than 6 spans. On 2010-03-17

Hi, running Asterisk 1.6.2.0 and have started to see in messages: [Jan 14 05:43:43] NOTICE[29231] chan_sip.c: Peer '100' is now Lagged. (4007ms / 3000ms) [Jan 14 05:43:53] NOTICE[29231] chan_sip.c: Peer '100' is now Reachable. (9ms / 3000ms) [Jan 14 05:44:02] NOTICE[29231] chan_sip.c: Peer '100' is now Lagged. (5008ms / 3000ms) [Jan 14 05:44:12] NOTICE[29231] chan_sip.c:

I'm currently running tinc-pre6 on 2 nodes in a larger network. My Laptop (Lassulus), lan ip: 192.168.2.100, tinc-ip: 10.243.0.2 My Server (alphalabs), lan ip: 192.168.2.103, tinc-ip: 10.243.1.10 internet vserver (slowpoke), no lan ip, tinc-ip: 10.243.232.121 Everything works fine until both nodes are in the same LAN. The first 2-3 minutes everything is fine. Pings between the machines go