I am trying to understand the procedure and the failures, because they seem the same.
one issue I've already identified and solved is the issue with the test2 and on, there is a trial to open a new UDPsocket for receiving while the sending socket was not closed.
I am not sure if the binded address in the client of the STUN request- with ip & port change was supposed to be the same,
but of course it will not work.
In the pynat & pystun3 implementations it doesn't work this way, the same socket is being used.
I haven't figured out yet why one is working and the other doesn't, or what is the cause for different identification of the NAT type for the same home router I have in different times.
I am trying to understand the procedure and the failures, because they seem the same.
one issue I've already identified and solved is the issue with the test2 and on, there is a trial to open a new UDPsocket for receiving while the sending socket was not closed.
I am not sure if the binded address in the client of the STUN request- with ip & port change was supposed to be the same,
but of course it will not work.
In the pynat & pystun3 implementations it doesn't work this way, the same socket is being used.
I haven't figured out yet why one is working and the other doesn't, or what is the cause for different identification of the NAT type for the same home router I have in different times.