Messages

[I can't change IPSec configuration on the other end of the tunnel.]

I have configured site-to-site IPSec from my LAN to specific remote IP on the other end of IPSec tunnel.
From LAN network everything works fine.

I also have OpenVPN clients (road warrior setup) on separate subnet. That OpenVPN subnet (tunnel network) can not access remote IP on the IPSec directly. I can't change IPSec configuration on the other end of the tunnel.

My idea was to try to configure Outbound NAT somehow in order to access remote IP from OpenVPN clients.

I add FW rule in OpenVPN "interface" to allow traffic from OpenVPN subnet to remote IP.
I also add remote IP in OpenVPN server config as "IPv4 Local Network" (/32).

I also add Outbound NAT rule (manual generation) with following parameters:

• Interface : LAN (also tried OpenVPN and IPSec interfaces
• Source address : OpenVPN subnet (tunnel network)
• Destination address : Remote IP address
• Translation/target : LAN address (also tried Interface address)

... but I can't find setup that works. I would like to try to "cheat" IPSec tunnel to allow OpenVPN clients subnet to have access to remote IP, without changing IPSec configuration (I can't change other side of IPSec).

Looking in Firewall log, all attempts to access remote IP from OpenVPN subnet goes to WAN interface.

Any idea ? Is it possible at all ?

[System/Access/Servers]

Thanks for reply :).

So, I don't need to add server in System/Access/Servers in this case ?
I just need to add freeradius plugin and configure it in Services/FreeRADIUS (including users and clients-WAPs) ?

• Any firewall rules needed ?
• What IP address to put on my clients ? Is OpnSense listening for radius messages on all its interfaces ?

Is it possible to use OpnSense Freeradius plugin for external Wireless Access Points WPA Enterprise authentication ?

[[intr{swi4: clock (0)}]]

OpnSense is installed on SuperMicro SuperServer 5018D-FN8T with Xeon D-1518 CPU.
Everything works fine, but even in idle, [intr{swi4: clock (0)}] shows WCPU abt 10.0% all the time.

Code Select Expand


PID USERNAME PRI NICE SIZE  RES    STATE   C    TIME      WCPU     COMMAND
11   root    155 ki31 0   128K   CPU0    0 330.2H    100.00%  [idle{idle: cpu0}]
12   root    -60  - 0   1328K  WAIT    5 35.3H      10.57%  [intr{swi4: clock (0)}]


Same config on chinese Mini PC based on Celeron J1900 shows WCPU for same process less then 1%.

Is it normal ? Load average showing on Dashboard is about 0.5 (8 cores CPU).