Actions
Bug #8493
closedAssigned OpenVPN interface does not send traffic via right route until reboot
Status:
Not a Bug
Priority:
Very Low
Assignee:
-
Category:
Routing
Target version:
-
Start date:
05/03/2018
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:
Description
In case of using several OpenVPN instances, e.g. Client (has its own default route) and Server on pfsense, assigned OpenVPN server interface does not send traffic via right route until device reboot (in some cases until pf restart).
I can see states and input traffic (10.0.10.0/24) on appropriate interface (OPT1) but does not see one output interface (LAN 10.0.11.0/24). Instead that I observe this traffic on WAN (default route) interface.
OPT1 icmp 10.0.10.2:1 -> 10.0.11.1:1 0:0 2 / 2 120 B / 120 B
Before reboot
OPT1
IP 10.0.10.2 > 10.0.11.1: ICMP echo request, id 1, seq 157, length 40 IP 10.0.10.2 > 10.0.11.1: ICMP echo request, id 1, seq 158, length 40
WAN
IP 10.0.11.1 > 10.0.10.2: ICMP echo reply, id 1, seq 157, length 40 IP 10.0.11.1 > 10.0.10.2: ICMP echo reply, id 1, seq 158, length 40
After reboot:
OPT1 and LAN
IP 10.0.10.2 > 10.0.11.1: ICMP echo request, id 1, seq 137, length 40 IP 10.0.11.1 > 10.0.10.2: ICMP echo reply, id 1, seq 137, length 40 IP 10.0.10.2 > 10.0.11.1: ICMP echo request, id 1, seq 138, length 40 IP 10.0.11.1 > 10.0.10.2: ICMP echo reply, id 1, seq 138, length 40
The issue affects Intel and ARM
Files
Actions