Author Topic: 21.7 GUI issue (Read 4346 times)

Mantis314 · « **on:** August 14, 2021, 06:51:24 am »

I have an IPsec tunnel between two OPNsense firewalls.
I upgraded both of them today to 21.7.
If I go to VPN/IPsec/Tunnel Settings, both local and remote subnets are /24.
If I then click on the edit icon (Pencil), the next page shows both subnets as /32.
Please see attached snips.
I didn't notice this when I edited the description field and crashed my tunnel upon saving the configuration.
It was easy to fix, once I spotted the problem.
Subsequent testing shows that it does this every time, and it behaves the same way at both ends.
This looks like a bug to me.
If it's intentional, I'm not a fan.

Mantis314

kosta · « **Reply #1 on:** August 14, 2021, 03:21:45 pm »

Where it says 32 in your config, mine is 24.
Actually, first one is LAN subnet, which has an empty address field, and 32 preselected. I could of course put the network manually, like you did, but save it as 24.
Remote network is of course custom (Network), with /24 subnet.

franco · « **Reply #2 on:** August 14, 2021, 03:22:44 pm »

Quote from: Mantis314 on August 14, 2021, 06:51:24 am

If it's intentional, I'm not a fan.

You're not a fan of updating to 21.7.1 either?

Cheers,
Franco

Mantis314 · « **Reply #3 on:** August 14, 2021, 05:08:31 pm »

Kosta, The issue is that going in to edit one field, in my case the description, should not automatically change other unrelated fields.
When I saved my description changes, both subnets changed from /24 to /32 which broke my config.
Now that I know to watch for that it shouldn't be a problem for a while. But if I change something 6 months from now, I will likely have forgotten again.

Mantis314

Mantis314 · « **Reply #4 on:** August 14, 2021, 05:24:19 pm »

Franco,
I'm not a fan of some of the "Improvements" that show up after updating various products, Windows comes to mind here.
Bugs, on the other hand are just part of the process.

After all the whole reason for updates and patches is to replace documented issues with undocumented ones.

Mantis314

franco · « **Reply #5 on:** August 14, 2021, 08:31:52 pm »

I simply meant to say https://github.com/opnsense/changelog/blob/613960454b7da72e18f282211f7cbd5f1bf844b7/community/21.7/21.7.1#L36 which is https://github.com/opnsense/core/issues/5129 which is https://github.com/opnsense/core/commit/0680b5ccc8d so you can just install on 21.7 with:

# opnsense-patch 0680b5ccc8d

Cheers,
Franco

Mantis314 · « **Reply #6 on:** August 15, 2021, 03:48:15 am »

Franco,

I ran the check for updates on Friday, and it gave me 21.7
I noticed the problem the next day, Saturday morning and posted right away.
I misinterpreted your reply to mean that you didn't care for 21.7.1
Now that I read you second reply and followed the links you provided, I see that it is fixed in 21.7.1
I just rechecked for updates and was provided 21.7.1 which does indeed correct the issue.

Thanks for that!

Mantis314

Greelan · « **Reply #7 on:** August 15, 2021, 04:24:30 am »

Franco likes to be cryptic…

franco · « **Reply #8 on:** August 15, 2021, 09:00:42 am »

All I am trying to say is that issues should go to GitHub and reports should be checked against the latest available version if possible.

Cheers,
Franco