Project

General

Profile

Actions
Copy link

Bug #16670

open

Routing broken after upgrade 24.11 → 25.07.1: OpenVPN gateway and subnet routed via lo0

Added by Sami Siltala 1 day ago. Updated 1 day ago.

Status:
Incomplete
Priority:
Normal
Assignee:
-
Category:
Routing
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Release Notes:
Default
Affected Plus Version:
Affected Architecture:
6100

Description

Hi

I recently noticed that after upgrading pfSense from version 24.11 to the newer 25.07.1, the firewall log started showing blocked messages: "lo0 Default deny rule IPv4 (1000000104)".
I have a LAN 192.168.0.0/24 and an OpenVPN site-to-site network 192.168.255.0/24. This worked in version 24.11 and I have not made any changes, but now I am unable to ping the destination network, and the remote side cannot access the local network either.

Has something happened in the update that could explain why this no longer works?

I recreated a post: https://forum.netgate.com/topic/200007/firewall-log-lo0-blocked-traffic

Routing tables
Internet:
Destination        Gateway            Flags         Netif Expire
20.1.0.1           link#10            UHS             lo0  <--- this is supposed to be ovpns2
20.1.0.2           link#28            UH           ovpns2
192.168.255.0/24   20.1.0.1           UGS             lo0  <--- this is supposed to be ovpns2
Actions
Copy link
 #1

Updated by Jim Pingle 1 day ago

  • Status changed from New to Incomplete

This is most likely a configuration issue but there is not enough information here to go on, and this platform is not for diagnostics or discussion. Keep the discussion on the forum, and if a specific reproducible issue can be identified, this can be reopened with more complete information.

The first steps should be upgrading to the current release (25.11.1) and if the problem still occurs, post more detail about your OpenVPN configuration on the forum thread.

Actions
Copy link
 #2

Updated by Sami Siltala 1 day ago

Jim Pingle wrote in #note-1:

This is most likely a configuration issue but there is not enough information here to go on, and this platform is not for diagnostics or discussion. Keep the discussion on the forum, and if a specific reproducible issue can be identified, this can be reopened with more complete information.

The first steps should be upgrading to the current release (25.11.1) and if the problem still occurs, post more detail about your OpenVPN configuration on the forum thread.

I updated to version 25.11.1, but there was no change.

Actions
Copy link

Also available in: Atom PDF