Question

We have Problems establishing tunnels if the PSK contains special characters like "§".

It occours only if the PSK is enterd via the GUI.

I did a Workaround: I manipulate /etc/config/ipsec file with an editor and the tunnel esteblishes.

I guess there is a problem converting strings with special characters to hex if enterd in GUI.

Comments

Is the device you are creating a tunnel to is another RUT?

What changes do you perform in the config file?

---

- The remote host is a Fortinet Fortigate 101E. We have many RUT230 and 240 with older Firmware connecting to it as a Dialup VPN. The RUT 241 was the first device that can´t create a tunnel. Logs in the Fortigate showed a PSK mismatch.

- The Secret entered in the GUI was stored in HEX in the config file /etc/config/ipsec.

option secret          '0xFFFF123FFF'

i changed it to:

option secret          'ThisIsAnExampleforAPSKString'

I did an IPsec restart and the Tunnel established immediately.

---

I assume your other devices have legacy design firmware with versions starting RUT2XX_R_00.01.14.x and it does not occur on RUT2_R_00.07.xx firmwares? 

Have you tested any other special characters or is it just "§"?

---

-  Yes the other Devices have legacy design firmware: RUT2XX_R_00.01.14.4

- I did not update RUT230 & RUT240 to the new design firmware yet. So i can´t say if it occurs on RUT2_R_00.07.xx. At the moment i am a little afraid, the VPN will not establish after update.

- this are the special characters in the PSK:        §}_{>;&%$+<?}#~,

---

I was not able to establish a tunnel using "§" as well. The issue is forwarded to the development team to investigate.

Thank you for the information you have provided.

---

Hello,

Out of all these symbols §}_{>;&%$+<?}#~, the issue is reproducible only with §.

Solution is currently scheduled for 7.4 firmware, which will not happen anytime soon.

In the mean time, the suggestion is to remain on the legacy WebUI firmware or simply avoid the use of §.

Best regards,

Answer 1

Hello,

I would like you to attach a troubleshoot file to your question. It would help to analyze the issue and provide a solution. Please, replicate the issue, then access router's WebUI, go to System -> Administration > Troubleshoot section and download troubleshoot file from there.

Files are private and visible only to Teltonika Moderators.

Best regards,