Bug in Default gateway selection

[Fabiano1]

Under the System menu, Routing, Gateways tab, Default gateway section.
The right config is:

In the fields:
Default gateway IPv4, and
Default gateway IPv6
set both = None. Save.
The message says:
"The gateway configuration has been changed.
The changes must be applied for them to take effect."
Click the Apply Changes button.
The globe icon still shows that the default gateway is WANGW. The same is shown in the dashboard.

The system continues working fine until a reboot, or until powering on the second server configured as backup (CARP/pfsync). After that, only LAN continues working, no internet access anymore (because WAN has no gateway).
I have found this after changing from 2.3.4 to 2.6.0. It seems like an obvious question, but the fact of not stopping the internet access imediatly, it took me a lot of time to find out where the problem was. Two points here:
1 - it could have a better message after changing the default gateway field;
2 - it could apply the change immediatly, or print a message alerting the user about what will happen.
Everyone agrees with me that this is a bug?

Note: If you select Automatic, the globe icon is displayed in the same way as None. I haven't tested with Automatic option selected, to know if it works or not.

[bingo600]

@Fabiano1

Why would you want to have no default gateway, at all ?

I have been bitten by automatic .... If wan ever goes down it would set "one of the other" as def-gw , and i seem to remember it wouldn't switch back when wan comes up.
I had to reboot, until i discovered the "automatic" was NOT what i wanted.

Bug or not .... Please answer why you would want to run a pfSense wo. a def-gw

/Bingo

[Fabiano1]

@bingo600

I don't want. It was an error selecting None. But until discover this was the error... it was possible to discover too that the behaviour is not to apply the choice imediatly, so the difficulty in finding the root cause.

[stephenw10]

Mmm, that does seem unexpected. Though the globe icon indicates which gateway is default and it still showed which was correct.
I assume it was not shown after rebooting?

[Fabiano1]

@stephenw10
Exactly.

[stephenw10]

Did it log an error when setting the gateway to none? Something that might indicate it was unable to remove the default route?

[Fabiano1]

@stephenw10
No, I couldn't find any error in the logs. I found this only (under Status menu -> System Logs -> System -> Gateways):

Jun 22 14:27:33 dpinger 44595 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr <WAN gateway IP> bind_addr <WAN IP> identifier "WANGW "
Jun 22 14:27:33 dpinger 44759 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr <LAN gateway IP> bind_addr <LAN IP> identifier "LANGW "

[stephenw10]

Hmm, that's just dpinger restarting, which is expected when you make any gateway change.

[Fabiano1]

@stephenw10
Coming back to the two points I have suggested in the first topic:
1 - it could have a better message after changing the default gateway field;
2 - it could apply the change immediatly, or print a message alerting the user about what will happen.
Could be submitted a suggestion for improvement? (so it can be fixed, or it could have at least a message informing...).

[stephenw10]

You can open a bug report or feature request: https://redmine.pfsense.org/

[Fabiano1]

@stephenw10
https://redmine.pfsense.org/issues/14634

Thank you!

[Kyouko]

@Fabiano1 I have had similar behavior. However, CARP was still involved, which was also the reason for the problem.
But from the description it sounds very similar.
Therefore here is the link to the issue: https://redmine.pfsense.org/issues/14171