-
Notifications
You must be signed in to change notification settings - Fork 24
Not working with v1 (maybe) #54
Comments
hi @zhum , Hum... seems like a network issue. Do you mind running this in debug mode? Also, you don't need to set the |
Here is the output (repeated several times):
|
Here is tcpdump of console
May be last |
Could you also |
Here it is:
|
Ok, so we confirmm that the packet is well-formed, and it's sent to the right peer. I guess the legacy device takes longer to reply? Try increasing the |
Tried this, didn't help... Seems very strange, may be my legacy device has some peculiarity, but how can we detect it? |
can you run run |
Here is the log: It seems strange, that answer for a request was received very fast, but in case ruby code there was no answer at all... |
@zhum can you try the EDIT: Also forgot to ask: what's your environment, i.e. OS, ruby version, etc. |
Did not help :( I use Centos 7.8.2003, ruby 2.7 (via |
I'm out of ideas for remote troubleshooting 😞 I think I'd I'd require remote access to figure out what's going on, as that's a weird network behaviour: the request packet goes, but the response never arrives... Do you know how to work with wireshark? Could you inspect all UDP, SNMP traffic during your script run, to see if things are workingn as expected network-wise? Maybe compare it with the |
I can get you the remote ssh access, if you provide an open ssh key to me (serg at parallel.ru), also I can get you sudo access for tcpdump and wireshark. |
privilege connectionless interactions, as agents might send PDUs from destinations other than the ones the request was sent to. Fixes #54.
@zhum I've found out what was going on. It was two things:
Thank you again for the collaboration. |
Wow! Yes, it works with these notes. Thank you! |
I'm trying to get some values from proprietary service, supporting only V1. It works fine with console program:
While simple ruby program fails with timeout:
How can I debug this?
The text was updated successfully, but these errors were encountered: