My configuration broken after recent update

This forum is for admins who are looking to build or expand their OpenVPN setup.

Moderators: TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech

Forum rules
Please use the [oconf] BB tag for openvpn Configurations. See viewtopic.php?f=30&t=21589 for an example.
Post Reply
grzeg0rz
OpenVpn Newbie
Posts: 2
Joined: Mon May 10, 2021 5:34 pm

My configuration broken after recent update

Post by grzeg0rz » Mon May 10, 2021 5:47 pm

Hello fellow OpenVPN users!

I am running my VPN gateway and everything was working fine until yesterday. Yesterday I updated my unprivileged podman container where I run openvpn server and it won't start anymore because OpenVPN tries to adjust MTU of tun device.

In the past I was setting up tun device myself (including MTU) and then within container I was replacing `ip` command with empty script which was always returning 0. But yesterday I noticed MTU is set through different method, this is my log:

Code: Select all

TUN/TAP device tun0 opened
net_iface_mtu_set: mtu 1500 for tun0
sitnl_send: rtnl: generic error (-1): Operation not permitted
Linux can't set mtu (1500) on tun0
Exiting due to fatal error
OpenVPN from before November works fine.

Can somebody point me at direction what can I do to preserve my root-less setup? I was looking at -up argument but it says script specified within this argument is executed after interface is up.

TinCanTech
OpenVPN Protagonist
Posts: 11137
Joined: Fri Jun 03, 2016 1:17 pm

Re: My configuration broken after recent update

Post by TinCanTech » Wed May 12, 2021 8:44 pm

grzeg0rz wrote:
Mon May 10, 2021 5:47 pm
sitnl_send: rtnl: generic error (-1): Operation not permitted
SITNL is Simple Interface To Net Link.

I guess it is not compatible with your unprivileged podman container ..

Next time, test before you upgrade.

tedm
OpenVpn Newbie
Posts: 6
Joined: Sun May 16, 2021 4:30 pm

Re: My configuration broken after recent update

Post by tedm » Sun May 16, 2021 5:48 pm

The point of podman is to easily swap in and out different deployments so him switching back to his prior version is as easy as a couple of commands (assuming he backed up his pod) He IS testing.

Post Reply