similar to: High ping time from domU , normal time when tcpdump is running

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

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

Anyone else seen this one? > > ping -n {remote host} > { 6 second delay } > 64 bytes from 216.168.105.33: icmp_seq=0 ttl=255 time=6sec > 64 bytes from 216.168.105.33: icmp_seq=1 ttl=255 time=5sec > 64 bytes from 216.168.105.33: icmp_seq=2 ttl=255 time=4sec > 64 bytes from 216.168.105.33: icmp_seq=3 ttl=255 time=3sec > 64 bytes from 216.168.105.33: icmp_seq=4

Hi! We have encountered a rather weird problem on a machine that we use for our network latency check (smokeping with fping). For an hour (or so) after boot it reports the ping time with a microsecond accuracy (ad it should). Then the millisecond accuracy starts. We have yet to identify the cause and the logs currently do not show anything. Please find an example of a good and a bad result

Try to ping from client to server with its hostname. Sounds like dns problem. ping server Then try to ping its ip address. Then try to add server address to host file. Ex 192.168.8.30 server.example.com[1] server Best M On May 26, 2016 12:02, "Nico Speelman" <nico at speelmanrobben.nl[2]> wrote: Hello, I've been trying to add a new server to my Samba 4 Active directory, but

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 just got an inexpensive VPS too have an outside server to play/test with. I am pinging it every 5 minutes and graphing with MRTG on another CentOS box. This works fine to all servers but the VPS. The first ping to the VPS is always crud and following ones are fine. [root at ns1 scripts]# ping X PING X 56(84) bytes of data. 64 bytes from X: icmp_seq=1 ttl=55 time=773 ms 64 bytes from X:

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. The configuration script is at the bottom. My configuration looks similar to this: imq0 | 1:1 (12mbit) | 1:2 (10mbit) | 3:0 | 3:1 (256kbit) / \ 3:2 3:3 icmp (rest) both 3:2 and 3:3 have rate 1kbit ceil 256kbit Icmp bucklet have priority 1 (better), "rest" bucklet have prio 2 (worse) I tested the script with heavy download

Dear all, If I do cause offence by posting OT here I apologise in advance, I am however desperate for help and after posting on other forums without any ideas I know many networking experts will see this here and hope they can enlighten me. I will gladly donate some PayPal money to the person who can help. I have a leased line on 83.111.160.6 (/30 subnet, gw is 83.111.160.5), and they

With 1.6.1 svn: [2009-04-26 15:01:00] NOTICE[1844]: chan_sip.c:9927 sip_reg_timeout: -- Registration for '17470121145 at proxy01.sipphone.com' timed out, trying again (Attempt #30) [2009-04-26 15:01:00] WARNING[1844]: acl.c:376 ast_get_ip_or_srv: Unable to lookup 'proxy01.sipphone.com' [2009-04-26 15:01:00] WARNING[1844]: chan_sip.c:10037 transmit_register: Probably a DNS

Hello, I''ve got this problem. There is an linux server with 2.4.24 kernel and pinging from him to internet (or from lan) ping randomly jumps up: 64 bytes from fortas.ktu.lt (193.219.160.131): icmp_seq=387 ttl=59 time=30.0 ms 64 bytes from fortas.ktu.lt (193.219.160.131): icmp_seq=388 ttl=59 time=32.6 ms 64 bytes from fortas.ktu.lt (193.219.160.131): icmp_seq=389 ttl=59 time=34.9 ms

Hi guys!! This is something that have always bother me, hope you can help me... :) I've 8 server connected using IAX / DUNDi, it works just fine. However, sometimes when some of our links goes down the server takes forever to appear back as OK at DUNDi's list and people can't call the other Box. It's happening right now: CLI> dundi show peers 00:14:22:16:54:c5 200.X.X.6

I am managing two Xen containers which are exhibiting a spooky behavior. There are intermittent network failures that affect only the VM''s, and not dom0. This exhibits itself as problems with nfs locks, snmp, and even icmp ping. The arp tables look normal on both the dom0 and the guest. However, it is definitely arp related. Causing arp traffic of any sort results the problem curing

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:

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

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

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:

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