From owner-freebsd-net@freebsd.org Tue Jan 5 09:39:30 2021 Return-Path: Delivered-To: freebsd-net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E35C04DEC51 for ; Tue, 5 Jan 2021 09:39:30 +0000 (UTC) (envelope-from vit@otcnet.ru) Received: from mail.otcnet.ru (mail.otcnet.ru [194.190.78.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4D96sF5k1Fz3k7C for ; Tue, 5 Jan 2021 09:39:29 +0000 (UTC) (envelope-from vit@otcnet.ru) Received: from VitComp.local (unknown [95.179.10.25]) by mail.otcnet.ru (Postfix) with ESMTPSA id 0FF259A6C2 for ; Tue, 5 Jan 2021 12:39:22 +0300 (MSK) Subject: Re: 'dropped due to full socket buffers' by SNMP To: freebsd-net@freebsd.org References: <388da9a7-7b89-89b2-54eb-17d0e818c924@otcnet.ru> <4e41c1d2-19bc-0345-0b03-526e4cb785c7@otcnet.ru> <6c780827-e764-8053-356b-a921e0892c15@grosbein.net> <7e51a6be-aea1-51c6-c0bd-10d00c19d5d3@grosbein.net> From: Victor Gamov Message-ID: <888c8e91-c8f2-ad4b-9fcf-64c09432f2d5@otcnet.ru> Date: Tue, 5 Jan 2021 12:39:03 +0300 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: <7e51a6be-aea1-51c6-c0bd-10d00c19d5d3@grosbein.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: ru Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4D96sF5k1Fz3k7C X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of vit@otcnet.ru designates 194.190.78.3 as permitted sender) smtp.mailfrom=vit@otcnet.ru X-Spamd-Result: default: False [-3.20 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[194.190.78.3:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+a:mail.otcnet.ru]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-net@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[194.190.78.3:from:127.0.2.255]; DMARC_NA(0.00)[otcnet.ru]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:50822, ipnet:194.190.78.0/24, country:RU]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-net]; RECEIVED_SPAMHAUS_PBL(0.00)[95.179.10.25:received] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jan 2021 09:39:30 -0000 Hi Eugene! Thanks for your responces. And Happy New Year for everyone! On 01.01.2021 03:19, Eugene Grosbein wrote: > 30.12.2020 23:08, Victor Gamov wrote: > >> As I understand hw.ix.flow_control=3 to allow flow-control for negotiation. >> Real PAUSE setting will be set during negotiation. > > At the moment of congestion. As I understand PAUSE feature negotiated during auto-negotiation process. If flow-control disabled on one side (switch for example) then other side (host) will not to use this feature too. Is it right? >> So where I can find active flow-control setting for host interface? > > Can't check for ix just now, but for em(4) there is sysctl dev.em.0.fc. > It should be similar for ix. I have hw.ix.flow_control=3 (what does is it means ?) and dev.ix.0.fc=3 (and what does is it means?) >>> maybe increase kern.ipc.maxsockbuf and then net.inet.udp.recvspace. >> Eugene, at first message you suppose Host-A (sender) "outgoing link for that UDP packets is congested" >> because this host shows non-zero "dropped due to full socket buffers". >> So is net.inet.udp.recvspace increasing on Host-B (mainly receiver) will be affected for this congestion? > > Can't tell in details without going deep into your setup :-) > You can try it yourself and verify quickly. > >> Or I need to try to increase both kern.ipc.maxsockbuf and net.inet.udp.recvspace on both hosts? > > Tune one that drops UDP. > >> Also how I can check current sockbuf usage? > > netstat -xn Unfortunately it never shoes counters about UDP multicast traffic. I'll increase kern.ipc.maxsockbuf and net.inet.udp.recvspace at next week and write about results. Back to my original question: is it possible to monitor `netstat -n -p udp -f inet -s` counters by SNMP? -- CU, Victor Gamov