Communication is ok. Problem was with pcap filtering based on port
number. Only the first fragment of the packet have this information.
All others have port fields empty. More information in tcpdump man
page in IP Fragmentation section.
In new packet capture the request for 87 OIDs is replied with
On 06/03/18 23:36, Eliezer Croitoru wrote:
> Is this SNMP value present in the cache-manager pages?
> If so it would be pretty simple to write a script that will extract the
> relevant data via http.
>
OID *.1.5.2.2 is the mgr:client_list table data, excluding the TCP_*
code breakdown for respon
: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf
Of Amos Jeffries
Sent: Friday, March 2, 2018 15:38
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Squid SNMP remote monitoring and IP fragmentation
On 03/03/18 01:28, Peter Viskup wrote:
> We do monitor
On 03/03/18 01:28, Peter Viskup wrote:
> We do monitor our Squid's via SNMP with Zabbix and use the template
> available on Zabbix share portal [1].
> Retrieval of values is not reliable. Seems to be related to IP fragmentation.
>
> The complete answer should be 4325B long.
>
> ~# snmpwalk -m /us
We do monitor our Squid's via SNMP with Zabbix and use the template
available on Zabbix share portal [1].
Retrieval of values is not reliable. Seems to be related to IP fragmentation.
The complete answer should be 4325B long.
~# snmpwalk -m /usr/share/squid3/mib.txt -v2c -CE
.1.3.6.1.4.1.3495.1.5
