Jean-Jacques Sarton

plungin_stun segment violation

Tested with gcc 10.2 and gcc 7.4, work well with both.

I had made tests with the correct setting at this time this what not okay. I have corrected my mistake and now the test what successful. Thanks. By the way the beta version produce further warnings, see attached file. Instead of using sprintf() yo may use snprintf(). The declaration of ident produce also warning, sing that what nice in old time.

I have run siproxd on an other system, which has no NAT helper and this worked. This don't solve my problem but the reason is more or less found.

No NAT helper is involved on the system with Linphone. On the Server NAS the modules are loaded but the rules are only for docker instances and shall not interfere with siproxd. For the tunnel there are also no iptables rules containing problematic thinks.

I know, but via->port[5-1] will short the string if the port number is greater as 9999. The code may be eliminated and will only be effective if there is an error in the code or the called function above. Am 07.02.21 um 19:59 schrieb Thomas Ries: No. snprintf does include the terminating \0, also if the size limit is triggered. The limit is /including/ the terminating \0 (-> 6 = 5 digits + terminating \0). compile warning https://sourceforge.net/p/siproxd/discussion/203640/thread/e783812b9f/?limit=25#372f...

What is with line 159 should it not been: via->port[PORTSTRING_SIZE-1] ='\0'; or via->port[5] ='\0';

What is with line 159 should it not been: via->port[PORTSTRING_SIZE-1] ='\0';