{"id":5691,"date":"2023-10-06T14:28:32","date_gmt":"2023-10-06T22:28:32","guid":{"rendered":"https:\/\/wonghoi.humgar.com\/blog\/?p=5691"},"modified":"2024-05-11T23:31:30","modified_gmt":"2024-05-12T07:31:30","slug":"quirks-of-softether-vpn-server-that-came-with-dd-wrt","status":"publish","type":"post","link":"https:\/\/wonghoi.humgar.com\/blog\/2023\/10\/06\/quirks-of-softether-vpn-server-that-came-with-dd-wrt\/","title":{"rendered":"Quirks of SoftEther VPN Server that came with DD-WRT"},"content":{"rendered":"\n

DD-WRT came with SoftEther VPN and it looked pretty scary because it shows no user interface and a box for you to enter a config file! <\/p>\n\n\n\n

Turns out SoftEther VPN’s Remote Admin interface is basically a tool that takes all user settings, generate a config file and upload it to the server behind the scenes!<\/p>\n\n\n\n

Concepts to know<\/h2>\n\n\n\n

vpn_server.config<\/code> is the core file the defines the server. <\/p>\n\n\n\n

SoftEther VPN Server Manager<\/strong> (The remote admin program) is basically a tool to generate the config text string from the UI and pass it to the server’s memory (not file yet until the server stops and flushes its config state out)<\/p>\n\n\n\n

Default location of the config file<\/h2>\n\n\n\n

SoftEther by default reads and writes the vpn_server.config<\/code> file which controls everything in a JFFS folder. So you are better off identifying it by doing a path search because they move around from version to version of dd-wrt:<\/p>\n\n\n\n

find \/jffs -name vpn_server.config<\/code><\/pre>\n\n\n\n
\"\"<\/figure>\n\n\n\n
So for my case the core file path is<\/p>\n\n\n\n
\/jffs\/var\/softethervpn\/vpn_server.config<\/code><\/pre>\n\n\n\n
Config file’s file access\/update mechanism<\/h2>\n\n\n\n
SoftEther’s explicitly stated that their config file (vpn_server.config<\/code>) handling mechanism does not flush the current state in use to the file until the server stops. So it has the following behavioral implications:<\/p>\n\n\n\n