similar to: re: Anyone else seen this one? (ping)

Displaying 20 results from an estimated 3000 matches similar to: "re: Anyone else seen this one? (ping)"

2007 May 04
0
RSVP RESV not seen
all: I"m just trying to create a simple rsvp session to familiarize myself with the protocol. I don''t ever get a rsvp RESV message only PATH AND PATH TEAR messages. There is a timeout but i''m not sure whats causing it exactly. Can anyone shed some light on why? All the configs and output are below. Please let me know if you need more information. Thanks. Jon Test
2005 Jan 30
1
x86_64 timer resolution in ping results
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
2009 Nov 06
0
High ping time from domU , normal time when tcpdump is running
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
2010 Oct 29
1
About ping latency in SR-IOV
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
2010 Oct 18
0
Ping time resolution
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
2011 Mar 08
2
CentOS 5.x 32bit VPS Ping Issue
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:
2007 Jun 25
1
Ping dom0 <-> domU result in "Destination host unreachable"
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
2009 Apr 26
1
1.6.1: "DNS error" but ping works
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
2005 Jun 02
2
Networking domU > Internet ping gives "destination host unreachable"
Hello @all, thanks for all the helpfull answers in this mailing list. They helped me compiling a new kernel 2.6.10.11 with Xen 2.0.6 (my first one), setting up a dom0 with RAID, LVM and loop devices for domU, integrating a second network as xen-br1 (I''m calling the /etc/xen/scripts/network script from within /etc/init.d/xend to bring up / down the second bridge.) and bootstrapping
2008 Sep 12
3
Strange Multi-homed Traceroute/Ping failure for some IPs on some routes
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
2009 Mar 31
1
dundi show peers - UNREACHABLE but I can ping it!
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
2010 Mar 17
0
Spooky networking issue: ping OK on container, stops on VM, restarts with arp -d
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
2004 Sep 22
0
ping failure on dual-home using -I without default route
My Linux workstation (Mandrake 10.1 kernel 2.6.8.1) is dual-homed to two ADSL Internet providers. Card eth0 (192.168.9.250) is the default route and leads to an SMC router (192.168.9.254). Card eth1 (192.168.1.250) leads to a Linksys router (192.168.1.1). I''m not doing any NAT or PPPoE in the workstation - the SMC and Linksys handle it all. If I remove all general default routes from
2004 Jan 07
11
Random ping jumps
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
2005 Apr 19
5
Strange pings.
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
2009 Jun 01
3
Within Subject ANOVA question
Dear R users, I have copied for following table from an article on "Using confidence intervals in within-subject designs": Subject 1sec 2sec 5sec 1 10 13 13 12.00 2 6 8 8 7.33 3 11 14 14 13.00 4 22 23 25 23.33 5 16 18 20 18.00 6 15 17 17 16.33 7 1 1 4 2.00 8 12 15 17 14.67 9 9 12 12 11.00 10 8 9 12 9.67 I rearranged the data this way:
2004 Sep 02
5
DNAT and ping
I have the following interfaces loc eth0 net0 eth1 net1 eth2 (net0 and net1 are the two ISP networks) policy loc net0 ACCEPT loc net1 ACCEPT net0 all DROP info proxyarp 209.189.103.204 eth0 eth1 no no params Pellucidar=192.168.124.232 rules DNAT net0 loc:$Pellucidar tcp 22,80,1950,50005 - 209.189.103.204 ACCEPT all all icmp
2007 Sep 13
0
change to ping
Has anyone else noticed with CentOS 5, that ping now starts at icmp_seq 1 instead of 0. It's clearly not a problem, just curious if anyone knows why it changed. Graham
2020 Jun 22
2
Voice broken during calls (again...)
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:
2012 Jun 07
1
network is only connected for a while when the domU is started
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