search for: pinging

i am hoping this attachment gets through. It deals with bug in ping that made it very difficult to set up a system with two gateways. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20091009/ddfc8176/attachment-0004.html> -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi all, I've recently switched to the latest rt kernel available from http://people.centos.org/hughesjr/kernel-rt And one of the two problems I'm having with this new kernel is that the logs have been flooded with nagios alerts which indicate high percentage (50-60) of packet loss when pinging localhost. The problem shows up several hours after the system reboot. Any ideas on what might be wrong and how to fix this on a running system? Are there any current plans to integrate MRG Realtime into CentOS project? Thank you, Sasha

At Rusty's suggestion, I tested vhost base performance with ping. Results below, and seem to be what you'd expect. I'm working on TSO support, expect results shortly. latency with ping (lower is better): native: [root at virtlab17 ~]# ping -c 1000000 -f -q 21.1.50.4 PING 21.1.50.4 (21.1.50.4) 56(84) bytes of data. --- 21.1.50.4 ping statistics --- 1000000 packets transmitted,

At Rusty's suggestion, I tested vhost base performance with ping. Results below, and seem to be what you'd expect. I'm working on TSO support, expect results shortly. latency with ping (lower is better): native: [root at virtlab17 ~]# ping -c 1000000 -f -q 21.1.50.4 PING 21.1.50.4 (21.1.50.4) 56(84) bytes of data. --- 21.1.50.4 ping statistics --- 1000000 packets transmitted,

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

Hello! I have two problems. One is, that I cannot ping a DomU from Dom0 (or any other host in my local network) and the second one is, that I cannot ping the same site (eg. www.suse.com) from two DomU''s at the same time. I have a fresh installation of openSuse 11.0 with Kernel 2.6.25.20-0.1-xen and my box has two physical ethernet cards. As far as I have investigated, eth0 is the one

I have a simple perl script that every few hours pings the handful of machines on my LAN. Lately I've sometimes been getting ping of 192.168.0.1 succeeded ping of 192.168.0.7 succeeded ping of 192.168.0.5 FAILED ping of 192.168.0.6 succeeded ping of 192.168.0.9 succeeded This machine in question has been running Centos faithfully for about six years and no recent changes to it have been

http://pastebin.com/raw.php?i=rykHdvBh bix.hu and www.yahoo.com are "pingable" test sites. 127.0.0.1 could not be pinged [firewall drops all icmp] i have a "oneliner" that echoes if theres "internet connection or no". $ ping -W 1 -c 2 bix.hu &gt;&amp; /dev/null &amp;&amp; ping -W 1 -c 2 www.yahoo.com &gt;&amp; /dev/null &amp;&amp;

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

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

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

For a same configuration in which the default policy is drop and only one connection is accepted in rules, continuous pinging to devices will stop squarely in 4.0.15 as soon as a very basic firewall is enabled whereas in 4.4.26.1, pinging will still continue after the firewall is enabled. All tests are done with proper reboot of the unit3 where the firewall is applied: unit1 <---> eth4 unit3 eth1 <--->...

...rnel. >> ping <windows-ip> PING 192.168.1.2 (192.168.1.2): 56 data bytes--- ping: sendto: Host is down ping: sendto: Host is down 192.168.1.2 ping statistics ---6 packets transmitted, 0 packets received, 100% packet loss >> ping <freebsd-ip> (from the windows machine). Pinging 192.168.1.3 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. If theres anymore input I can offer, let me know! At this point I'll do just about anything to get this working. Thanks again! Alex <ateslik@aol.com>

hi, how to write a scripts which launches 10 pings to different destinations at execution of single shell scripts please help me any ideas regards, Gopinath

Hi all, One of the net-ping users reported that the Net::Ping::External library was returning false positives on Vista. Basically, it does a ''ping -n1 host'' and checks for certain error strings. The problem is that the error strings it checks for are in English. The user in question is using a cmd.exe that''s entirely in Swedish (I think). Is there any way I can

We're being ping-flooded by the Nachi worm, which probes subnets for systems to attack by sending 92-byte ping packets. Unfortunately, IPFW doesn't seem to have the ability to filter packets by length. Assuming that I stick with IPFW, what's the best way to stem the tide? --Brett Glass

...fix . : IP Address. . . . . . . . . . . . : 10.54.7.16 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 10.54.7.1 cant ping anything on the 10.54.0 subnet, nor does that subnet show up ip using a port scanner... C:\>ping 10.54.0.2 Pinging 10.54.0.2 with 32 bytes of data: Request timed out. Request timed out. C:\>ping 10.54.7.2 Pinging 10.54.7.2 with 32 bytes of data: Reply from 10.54.7.2: bytes=32 time<1ms TTL=64 Reply from 10.54.7.2: bytes=32 time<1ms TTL=64 Any ideas why this is happening? I dont have a firewall on th...

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