RE: net.inet.udp.blackhole issue
- From: "Yony Yossef" <yonyossef.lists@xxxxxxxxx>
- Date: Tue, 30 Dec 2008 14:17:29 +0200
I'm facing lots of UDP "Connection refused" errors while runningbut I'm not
multistream iperf test. Analyzing it with wireshark showed several
"ICMP Port Unreachable" problems.
I've overriden it with "sysctl net.inet.udp.blackhole=1",
sure this is the correct thing to do, I feel like I've sweeped thetest, it can
problem under the carpet.
PS - I see similar failures with TCP bidirectional iperf
also be overriden by "sysctl net.inet.tcp.blackhole=1".
My question is - can it be a NIC problem? If so, how can a driver
problem cause an iperf UDP socket to be in a "non listening state"?
This is fairly unlikely to be a NIC problem, although
anything is possible in software. I'm not familiar with
iperf, but generally speaking ICMP port unreachable is a
result of packets arriving at a closed socket;
net.inet.udp.blackhole suppresses that ICMP:
if (badport_bandlim(BANDLIM_ICMP_UNREACH) < 0)
*ip = save_ip;
ip->ip_len += iphlen;
icmp_error(m, ICMP_UNREACH, ICMP_UNREACH_PORT, 0, 0);
I think I'd suspect an application bug/feature, in which
socket gets closed and opened during execution and once in a
while a datagram is delivered in that window. Perhaps
packets are being delivered with a non-trivial delay causing
them to arrive after the application has timed out waiting for it?
Robert N M Watson
University of Cambridge
I'm talking about a simple multistream UDP iperf test.
One stream always works fine. More than one UDP stream has a chance of
failing because of this problem.
Wireshark analysis shows no such delay and no packet loss nor corruption,
for what I've seen and understood.
On the other hand, same test on a 1Gig NIC (I'm using a 10Gig) doesn't
suffer from this issue without the blackhole assistance.
freebsd-net@xxxxxxxxxxx mailing list
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"
- Prev by Date: Re: +ipsec_common_input: no key association found for SA
- Next by Date: Re: +ipsec_common_input: no key association found for SA
- Previous by thread: Re: net.inet.udp.blackhole issue
- Next by thread: Account Update