search for: icmp_seq

Hello all, I would like to connect two IPv4-only networks through global IPv6-only network with tinc. Could anyone tell me how to configure tinc.conf and the other config files? Thanks in advance, Ichiro Tinc: Discussion list about the tinc VPN daemon Archive: http://mail.nl.linux.org/lists/ Tinc site: http://tinc.nl.linux.org/

Our users are experiencing some unacceptable delay when trying to have a conversation. The delay is so noticeable that they keep stepping on each others words and resort to calling the customers via cell phone. Here is the setup SDSL Connection (PPPoA) Speedtouch 610 SDSL Modem 3Com 2224PWR Plus Switch (phones on separate VLAN) 8 Cisco 796 Phones All connecting to a remote Asterisk Server. We

...the eth0 in domU could not get an IP address. i post the output here: 133.133.133.40 is the IP address of gateway 133.133.134.171 is the IP address of the PVM domU [root@localhost ~]# ping 133.133.133.40 PING 133.133.133.40 (133.133.133.40) 56(84) bytes of data. 64 bytes from 133.133.133.40: icmp_seq=1 ttl=64 time=0.824 ms 64 bytes from 133.133.133.40: icmp_seq=2 ttl=64 time=0.491 ms 64 bytes from 133.133.133.40: icmp_seq=3 ttl=64 time=0.495 ms 64 bytes from 133.133.133.40: icmp_seq=4 ttl=64 time=0.437 ms 64 bytes from 133.133.133.40: icmp_seq=5 ttl=64 time=0.459 ms 64 bytes from 133.133.133.40...

...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 ttl=64 time=0.448 ms 64 bytes from 10.12.6.1: icmp_seq=2 ttl=64 time=0.421 ms 64 bytes from 10.12.6.1: icmp_seq=3 ttl=64 time=0.405 ms 64 bytes from 10.12.6.1: icmp_seq=4 ttl=64 time=0.418 ms 64 bytes from 10.12.6.1: icmp_seq=5 ttl=64 time=0.423 ms 64 bytes from 10.12.6.1: icmp_seq=6 ttl=64 time=...

...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: icmp_seq=1 ttl=57 time=18.0 ms 1308 bytes from 217.0.128.133: icmp_seq=2 ttl=57 time=17.9 ms 1308 bytes from 217.0.128.133: icmp_seq=3 ttl=57 time=18.0 ms 1308 bytes from 217.0.128.133: icmp_seq=4 ttl=57 time=18.0 ms 1308 bytes from 217.0.128.133: icmp_seq=5 ttl=57 time=18.1 ms 1308 bytes from 217.0.128.133...

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 64 bytes from fortas.ktu.lt (193.219.160.131): icmp_seq=390 ttl=59 time=198 ms 64 bytes from fortas.ktu.lt (193.219...

...ather some statistics then we kill the download. then we sh -x wshaper.htb stop to shut down the malfunctioning shaper. Here''s the output from the ping: $ ping 67.0.192.10 PING 67.0.192.10 (67.0.192.10) 56(84) bytes of data. Link is idle, normal ping times. 64 bytes from 67.0.192.10: icmp_seq=0 ttl=254 time=48.5 ms 64 bytes from 67.0.192.10: icmp_seq=1 ttl=254 time=48.4 ms 64 bytes from 67.0.192.10: icmp_seq=2 ttl=254 time=48.4 ms 64 bytes from 67.0.192.10: icmp_seq=3 ttl=254 time=48.4 ms 64 bytes from 67.0.192.10: icmp_seq=4 ttl=254 time= 48.5 ms 64 bytes from 67.0.192.10: icmp_seq=5 t...

Am 22.06.2020 um 17:01 schrieb Telium Technical Support: > I don't know if there was a prior email with more details, but.... > > Latency is as important as speed. Have you checked latency between your device and pop? What about QoS at your location, and does your ITSP support/respect QoS? That's a very good idea... Could you suggest me how can I check it? The Gateway is a

...i send from this box should be the most highly priorised packet, but there are delayed when i add load on the link (with a scp upload). What is strange is that the delay of thoses ping is not constant: Does someone have an idea about this issue? Thx for any help romary 64 bytes from 10.10.0.10: icmp_seq=1 ttl=63 time=10.4 ms 64 bytes from 10.10.0.10: icmp_seq=2 ttl=63 time=52.8 ms 64 bytes from 10.10.0.10: icmp_seq=3 ttl=63 time=40.4 ms 64 bytes from 10.10.0.10: icmp_seq=4 ttl=63 time=90.1 ms 64 bytes from 10.10.0.10: icmp_seq=5 ttl=63 time=77.6 ms 64 bytes from 10.10.0.10: icmp_seq=6 ttl=63 time=...

...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 rounding up to 30ms. Here is an example: # ping x.x.x.x PING x.x.x.x (x.x.x.x) 56(84) bytes of data. 64 bytes from x.x.x.x: icmp_seq=1 ttl=64 time=0.197 ms 64 bytes from x.x.x.x: icmp_seq=2 ttl=64 time=0.100 ms 64 bytes from x.x.x.x: icmp_seq=3 ttl=64 time=0.081 ms 64 bytes from x.x.x.x: icmp_seq=4 ttl=64 time=0.099 ms # tc qdisc add dev eth0 root netem delay 10ms # ping x.x.x.x PING x.x.x.x (x.x.x.x) 56(84) bytes of data. 64 b...

...HWtype HWaddress Flags Mask Iface 10.20.10.125 ether 00:19:B9:D7:FB:4B C eth0 10.20.10.199 ether 00:07:E9:82:60:33 C eth0 PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data. >From 10.20.10.125: icmp_seq=1 Redirect Host(New nexthop: 10.20.10.1) 64 bytes from 4.2.2.2: icmp_seq=1 ttl=56 time=37.1 ms >From 10.20.10.125: icmp_seq=2 Redirect Host(New nexthop: 10.20.10.1) 64 bytes from 4.2.2.2: icmp_seq=2 ttl=56 time=32.3 ms 64 bytes from 4.2.2.2: icmp_seq=3 ttl=56 time=30.8 ms 64 bytes from 4.2.2.2:...

...k OK (if perhaps a little bursty) once I manage to get connected (often by ssh'ng to the destination by IP address rather than by name). I can ping computers on the wired LAN on the other side of the router: PING 192.168.0.100 (192.168.0.100) 56(84) bytes of data. 64 bytes from 192.168.0.100: icmp_seq=1 ttl=64 time=0.094 ms 64 bytes from 192.168.0.100: icmp_seq=2 ttl=64 time=0.084 ms 64 bytes from 192.168.0.100: icmp_seq=3 ttl=64 time=0.082 ms 64 bytes from 192.168.0.100: icmp_seq=4 ttl=64 time=0.084 ms 64 bytes from 192.168.0.100: icmp_seq=5 ttl=64 time=0.085 ms 64 bytes from 192.168.0.100: icm...

https://bugzilla.netfilter.org/show_bug.cgi?id=1127 Bug ID: 1127 Summary: running nft command creates lag for forwarded packets Product: nftables Version: unspecified Hardware: x86_64 OS: Gentoo Status: NEW Severity: major Priority: P5 Component: nft Assignee: pablo at

...;10ms shows as 0.000ms... --- On an Opteron machine running CentOS-3.4 --- # uname -a Linux omega.xxx 2.4.21-27.0.2.ELsmp #1 SMP Wed Jan 19 11:28:26 CST 2005 x86_64 x86_64 x86_64 GNU/Linux # ping 192.168.1.200 PING 192.168.1.200 (192.168.1.200) 56(84) bytes of data. 64 bytes from 192.168.1.200: icmp_seq=0 ttl=64 time=0.000 ms 64 bytes from 192.168.1.200: icmp_seq=1 ttl=64 time=0.000 ms 64 bytes from 192.168.1.200: icmp_seq=2 ttl=64 time=0.000 ms 64 bytes from 192.168.1.200: icmp_seq=3 ttl=64 time=0.000 ms 64 bytes from 192.168.1.200: icmp_seq=4 ttl=64 time=0.000 ms --- 192.168.1.200 ping statisti...

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 unreachable >From ::1 icmp_seq=3 Destination unreachable: Address unreachable >From ::1 icmp_seq=5 Destination unreachable: Address unreachable >From ::1 icmp_seq=6 Destination unreachab...

Hiya, I''m trying to track down some throughput latency that our customer seems to be attributing to our product, I can''t see what he''s talking about, but I want to try and get some deeper granularity than I might get with something like smokeping, and maybe even see if its down to something tunable on our end. I''ve been looking for some examples on how

...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 192.168.0.21: icmp_seq=1 ttl=64 time=0.117 ms 64 bytes from 192.168.0.21: icmp_seq=2 ttl=64 time=0.100 ms 64 bytes from 192.168.0.21: icmp_seq=3 ttl=64 time=0.102 ms 64 bytes from 192.168.0.21: icmp_seq=4 ttl=64 time=0.100 ms 64 bytes from 192.168.0.21: icmp_seq=5 ttl=64 time=0.105 ms --- 192.168.0.21 ping statistics --...

...7285/64 scope link valid_lft forever preferred_lft forever 3: sit0: <NOARP> mtu 1480 qdisc noop link/sit 0.0.0.0 brd 0.0.0.0 sles10mini:~ # Ping dom1 from localhost: foobar:~ # ping 192.168.130.171 PING 192.168.130.171 (192.168.130.171) 56(84) bytes of data. From 192.168.130.170: icmp_seq=1 Destination Host Unreachable From 192.168.130.170 icmp_seq=1 Destination Host Unreachable From 192.168.130.170 icmp_seq=2 Destination Host Unreachable From 192.168.130.170 icmp_seq=3 Destination Host Unreachable --- 192.168.130.171 ping statistics --- 5 packets transmitted, 0 received, +4 errors...

...uld be > 2000 without traffic shaper. I regard this already for quite an accomplishment, though it is not good enough yet for a gamer. I need stable pings, and the pings now are around 60 and 150. To demonstrate what I mean I give you the ping output: 64 bytes from 2int.de (217.160.128.207): icmp_seq=347 ttl=56 time=128 ms 64 bytes from 2int.de (217.160.128.207): icmp_seq=348 ttl=56 time=136 ms 64 bytes from 2int.de (217.160.128.207): icmp_seq=349 ttl=56 time=133 ms 64 bytes from 2int.de (217.160.128.207): icmp_seq=350 ttl=56 time=143 ms 64 bytes from 2int.de (217.160.128.207): icmp_seq=351 ttl...

...an_sip.c: Peer '100' is now Reachable. (8ms / 3000ms) [Jan 14 07:20:37] NOTICE[29231] chan_sip.c: Peer '100' is now Lagged. (4007ms / 3000ms) If I run a constant ping to that peer all looks fine: PING 192.168.1.110 (192.168.1.110) 56(84) bytes of data. 64 bytes from 192.168.1.110: icmp_seq=1 ttl=60 time=0.509 ms 64 bytes from 192.168.1.110: icmp_seq=2 ttl=60 time=0.496 ms 64 bytes from 192.168.1.110: icmp_seq=3 ttl=60 time=0.486 ms 64 bytes from 192.168.1.110: icmp_seq=4 ttl=60 time=0.500 ms 64 bytes from 192.168.1.110: icmp_seq=5 ttl=60 time=0.497 ms 64 bytes from 192.168.1.110: icm...