Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 1 Feb 2005 13:28:27 +0000
From:      Chris <chrcoluk@gmail.com>
To:        freebsd4@fadesa.es
Cc:        freebsd-stable@freebsd.org
Subject:   Re: 50% of packets lost only on local interfaces
Message-ID:  <3aaaa3a0502010528760c3a11@mail.gmail.com>
In-Reply-To: <41FE7524.7E907BE@fadesa.es>
References:  <41FE7524.7E907BE@fadesa.es>

next in thread | previous in thread | raw e-mail | index | archive | help
Have tested on 3 boxes.

5.3-STABLE compiled Jan 5th

--- 127.0.0.1 ping statistics ---
61 packets transmitted, 61 packets received, 0% packet loss
round-trip min/avg/max/stddev =3D 0.062/0.073/0.146/0.013 ms

5.3-STABLE amd64 build compiled Jan 29th

--- 127.0.0.1 ping statistics ---
60 packets transmitted, 60 packets received, 0% packet loss
round-trip min/avg/max/stddev =3D 0.024/0.030/0.048/0.005 ms

5.3-Release-P5

--- 127.0.0.1 ping statistics ---
60 packets transmitted, 60 packets received, 0% packet loss
round-trip min/avg/max/stddev =3D 0.057/0.089/0.167/0.017 ms

On Mon, 31 Jan 2005 19:12:52 +0100, Jos=E9 M. Fandi=F1o <freebsd4@fadesa.es=
> wrote:
> Hello,
>=20
> It sounds weird but tcp/ip traffic directed to _local_ interfaces,
> and only _local_ interfaces, always cause 50% of packets lost. Of
> course there isn't packet filters activated.
>=20
> I'm running -stable (the last update was this past weekend)
>=20
> There is another report like this:
> http://www.FreeBSD.org/cgi/query-pr.cgi?pr=3Dkern/72022
> but the suggested solution doesn't works in my case.
>=20
> ping to local interfaces get replies for 50% of the packets:
>=20
> > ping -c 512 127.0.0.1
> [snip]
> --- 127.0.0.1 ping statistics ---
> 512 packets transmitted, 257 packets received, 49% packet loss
> round-trip min/avg/max/stddev =3D 0.046/0.049/0.077/0.004 ms
>=20
> > ping -c 512 10.20.30.2
> [snip]
> --- 10.20.30.2 ping statistics ---
> 512 packets transmitted, 254 packets received, 50% packet loss
> round-trip min/avg/max/stddev =3D 0.017/0.049/0.071/0.004 ms
>=20
> Also running tcpdump on localhost shows as the kernel stop from
> responding to packets without an apparent motive.
>=20
> > tcpdump -n -i lo0
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decod=
e
> listening on lo0, link-type NULL (BSD loopback), capture size 96 bytes
> [snip]
> 17:58:15.516451 IP 127.0.0.1 > 127.0.0.1: icmp 64: echo request seq 76
> 17:58:15.516476 IP 127.0.0.1 > 127.0.0.1: icmp 64: echo reply seq 76
> 17:58:16.517321 IP 127.0.0.1 > 127.0.0.1: icmp 64: echo request seq 77
> 17:58:16.517347 IP 127.0.0.1 > 127.0.0.1: icmp 64: echo reply seq 77
> 17:58:17.518158 IP 127.0.0.1 > 127.0.0.1: icmp 64: echo request seq 78
> 17:58:18.519042 IP 127.0.0.1 > 127.0.0.1: icmp 64: echo request seq 79
> 17:58:19.519853 IP 127.0.0.1 > 127.0.0.1: icmp 64: echo request seq 80
> 17:58:20.520698 IP 127.0.0.1 > 127.0.0.1: icmp 64: echo request seq 81
> 17:58:21.521548 IP 127.0.0.1 > 127.0.0.1: icmp 64: echo request seq 82
> 17:58:22.522392 IP 127.0.0.1 > 127.0.0.1: icmp 64: echo request seq 83
>=20
> more tests, to the lan router:
>=20
> > ping -c 500 10.20.30.6
> [snip]
> --- 10.20.30.6 ping statistics ---
> 500 packets transmitted, 500 packets received, 0% packet loss
> round-trip min/avg/max/stddev =3D 1.565/2.015/40.189/2.385 ms
>=20
> from the lan router:
>=20
> Router#ping
> Protocol [ip]:
> Target IP address: 10.20.30.2
> Repeat count [5]: 500
> Datagram size [100]:
> Timeout in seconds [2]:
> Extended commands [n]:
> Sweep range of sizes [n]:
> Type escape sequence to abort.
> Sending 500, 100-byte ICMP Echos to 10.20.30.2, timeout is 2 seconds:
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> !!!!!!!!!!
> Success rate is 99 percent (498/500), round-trip min/avg/max =3D 1/2/12 m=
s
>=20
> I don't find any explanation for this, but I'd like to know if there is
> any solution?
>=20
> Thank you.
>=20
> I put the whole test (dmesg, make.conf, etc)in this URL so you can see
> all numbers.
> http://195.55.55.164/tests/FreeBSD/report.txt
>=20
> --
> -----BEGIN GEEK CODE BLOCK-----
> Version: 3.1
> GCS/IT d- s+:+() a- C+++ UBL+++$ P+ L+++ E--- W++ N+ o++ K- w---
> O+ M+ V- PS+ PE+ Y++ PGP+>+++ t+ 5 X+$ R- tv-- b+++ DI D++>+++
> G++ e- h+(++) !r !z
> ------END GEEK CODE BLOCK------
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3aaaa3a0502010528760c3a11>