Snmp response - bad udp length
by Itzme345 from LinuxQuestions.org on (#506CN)
Hi,
I am running the snmp agent on a custom board. And am using the MIB browser tool on my PC to query the snmp data from the agent.
I have certain parameters of OCTET STRING type that have sizes greater than 128 bytes.
The MTU size is the default 1500.
However, it seems that when I query the snmp data, the parameters of size greater than 128 bytes are not displayed. I mean, when querying for these parameters, there is no response and the snmp request just shows timeout.
So , I checked the data transfer using wireshark. It shows that the data bytes are received properly with the correct data. However it shows error in wireshark with the Expert Info showing bad udp length > ip payload length. It shows sizes of around 736 bytes.
The odd thing was that, this was working fine up until today. I have not changed any configurations on either end.
It is the first time that such an issue is showing up.
What could this mean? How do I resolve this?,
I am running the snmp agent on a custom board. And am using the MIB browser tool on my PC to query the snmp data from the agent.
I have certain parameters of OCTET STRING type that have sizes greater than 128 bytes.
The MTU size is the default 1500.
However, it seems that when I query the snmp data, the parameters of size greater than 128 bytes are not displayed. I mean, when querying for these parameters, there is no response and the snmp request just shows timeout.
So , I checked the data transfer using wireshark. It shows that the data bytes are received properly with the correct data. However it shows error in wireshark with the Expert Info showing bad udp length > ip payload length. It shows sizes of around 736 bytes.
The odd thing was that, this was working fine up until today. I have not changed any configurations on either end.
It is the first time that such an issue is showing up.
What could this mean? How do I resolve this?,