Guens

Thanks Kent for your help. I tried your script and the second session always fails too : ``` [] S2 error on iteration 0: timed out while connecting to remote...

I follow your advice with wireshark. When it's OK with ```python s2 = easysnmp.Session(hostname="10.224.113.113", **snmp_opts) print(s2.get(oid)) s1 = easysnmp.Session(hostname="10.224.115.121", **snmp_opts) print(s1.get(oid)) ``` Hers is the wireshark capture ``` $ tshark...

Single sessions s1 or s2 contains only the following packets : ``` $ tshark -r s1.pcapng 1 0.000000000 188.3.3.204 → 10.224.115.121 SNMP 106 get-request 2 0.001558097 10.224.115.121 → 188.3.3.204 SNMP...

Good shot Ken ! Problem occurs when two devices have the same EngineID. Let's look at this example : ```python oid = [".1.3.6.1.6.3.10.2.1.1.0", ] # SNMP-FRAMEWORK-MIB::snmpEngineID.0 s1 = easysnmp.Session(hostname="10.224.115.121", **snmp_opts)...

These 2 devices are 2 different hosts. They both have exactly the same software and configuration. They only differ with their network addresses, of course. I tried to restart one...

I agree with you : EasySNMP shouldn't care if two different devices have the same Engine ID. IMHO 2 "entities", with 2 different IP addresses, should be seen as 2...

> @Guens thanks for providing the sample code. I'll have to give it a try here sometime soon. In the meantime time can you downgrade EasySNMP to version 2.5 for...

@kamakazikamikaze your understanding is correct :-) I expect data returned, whatever `retry_no_such` value. I have tried your latest branch `test`, with this code : ```python import easysnmp try: easysnmp.snmp_walk(oids=".1.3.6.1.4.1.30512.2.12.1.5", hostname="10.174.202.133",...

@kamakazikamikaze you are right, the walk ask for a `get-next-request` after `.1.3.6.1.4.1.30512.2.12.1.5.16` and a `noSuchName` is returned :  CLI `snmpwalk` has the same exchanged packets, except it does not...

@carlkid1499 No problem : ```console $ ./python3.9 -