TURNKEYGNU / LINUX
English

Forum archive

OpenVPN 18.1 - Issues with setting static IP/connections on DHCP

Support
I'm having some issues with the 18.1 ISO release: When attempting to set a static IP on a new install via confconsole I receive "Unexpected config line post-up iptables restore /etc/iptables.up.rules" - upon exiting and re-entering the console/IP settings the default gateway is absent, they only way for the appliance to be usable is to set DHCP and reboot. (wether I chose to update during the install process makes no difference.)

Also when using DHCP the appliance appears not accept to connections on 1194 on its assigned DHCP address.

I have compared the IPtables configuration from a clean 17.1 install and both look the same, minus a webmin entry. Please let me know if you need further logs and want me to do further testing.

Regards,

Replies (3)

The same thing happened to me

Reply 1
Remove the line "post-up iptables restore /etc/iptables.up.rules" from /etc/network/interfaces.
To load the iptables rules, create a file named iptables-start.service in /usr/lib/systemd/system/ Paste this text:
#########################################3
[Unit]
Description=Start Iptables
After=network.target
StartLimitIntervalSec=0
[Service]
Type=simple
Restart=always
RestartSec=1
User=root
ExecStart=/usr/sbin/iptables-restore /etc/iptables.up.rules
[Install]
WantedBy=multi-user.target
################################################################
Enable it with systemctl enable iptables-start.service
Start de service with systemctl start iptables-start.service

Client connection error

Reply 2
Another problem I had was that I couldn't get the computers to connect to the OpenVPN server.
I solved it by adding these two lines to server.conf

cipher AES-256-CBC
auth SHA256

The Windows client log file didn't provide much information. I saw the error in the logs of Linux machines that were trying to connect to the OpenVPN server.

Thanks for the bug report & thanks for your workaround Juan

Reply 3

Thanks for the bug report & thanks for your workaround Juan.

Apologies for such a slow response. I'm currently tied up working on the new v19. I had hoped that it would have been long been released but alas I'm still battling few gnarly bugs... :(

Regardless, I'll circle back to this ASAP.