public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: Michael Tremer <michael.tremer@ipfire.org>
Cc: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: Problem with push routes when updating a CU196 openvpn to CU197
Date: Sat, 30 Aug 2025 12:10:11 +0200	[thread overview]
Message-ID: <57cad6ea-c25a-4153-9b90-122c26c883c3@ipfire.org> (raw)
In-Reply-To: <F80B752E-A3F0-4109-9AAF-C4BFDEA7C689@ipfire.org>

Hi Michael,

On 29/08/2025 23:51, Michael Tremer wrote:
> Hello,
> 
> This was probably introduced in this commit:
> 
>    https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=460942d7ed28ebf8c7727faa6321b63ee1c56964
> 
> It is supposed to read the routes_push file and write it to /var/ipfire/ovpn/settings.
> 
> This should happen whenever the CGI script is being called and does not even require that any configuration is being rewritten.
> 
> Can you confirm that nothing is in ROUTES_PUSH?

Yes, I can confirm that entry in the settings file is empty.

Regards,

Adolf.

> 
> Best,
> -Michael
> 
>> On 29 Aug 2025, at 19:50, Adolf Belka <adolf.belka@ipfire.org> wrote:
>>
>> Hi All,
>>
>> On 29/08/2025 19:05, Adolf Belka wrote:
>>> Hi All,
>>> I normally have not had any routes to be pushed specified on my openvpn connections. While investigating some other things I did some setups with routes specified in the CU196 server advanced settings. These were stored in the routes_push file and defined in the server.conf file.
>>> When I did an update to CU197 I found that the routes were specified in the routes_push file but no longer in the server.conf file. They were also not in the ROUTES_PUSH entry in the settings file.
>>> I then went into the Advanced Settings page on the CU197 and the routes were in the push routes entry box but separated by a blank line.
>>> I then pressed the Save Advanced Settings button and now the routes were in the server.conf and settings files and were in the advanced settings page without any blank lines between them.
>>> So something is not being fully completed when doing an update from a CU196 server with push routes specified and it requires the advanced settings to be saved to get everything updated as it should be.
>>> I suspect that a similar thing might happen if a CU196 backup with push routes is restored into a CU197 system but I haven't tested this yet. I will feedback what I find when I do that.
>>
>> I can confirm that the same thing happens when a CU196 backup with push routes specified does the same thing as described above and requires the Save Advanced Settings button to be pressed to put everything in the right files.
>>
>> Regards,
>>
>> Adolf.
>>
>>> Should I create a bug report for this?
>>> Regards,
>>> Adolf.
>>
>>
> 



  reply	other threads:[~2025-08-30 10:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-29 17:05 Adolf Belka
2025-08-29 18:50 ` Adolf Belka
2025-08-29 21:51   ` Michael Tremer
2025-08-30 10:10     ` Adolf Belka [this message]
2025-08-30 10:28       ` Adolf Belka
2025-08-30 10:56         ` Adolf Belka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57cad6ea-c25a-4153-9b90-122c26c883c3@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    --cc=michael.tremer@ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox