Messages

I have the exact same isue

There is no "Client Install Packages" entry under "VPN: OpenVPN: Client Export" after configuring VPN Server

  OPNsense 19.7.6-amd64
  FreeBSD 11.2-RELEASE-p14-HBSD
  OpenSSL 1.0.2t 10 Sep 2019

This installation is some years old and has always been updated. Maybe we lost some features on this way?

Thanks
Jan

[OR]

I have difficulties getting a setup with 2 WAN Gateways on OPNsense 19.7.6 to work properly. My intention was to implement a failover/loadbalance setup.

The problems began after adding the new Gateway (DSLGW) in addition to the existing Gateway (WANGW). Before that, everything worked fine for years

The current situation is:

• When both Gateways are enabled, and the new DSLGW is the active default gateway, my clients can connect to the internet.
• When I disable DSLGW, the old WANGW becomes active, but connection to the internet is lost.
  
• I also have NAT rules set up to proxy https traffic from the internet to a servers in my DMZ. This traffic is coming in via the WANGW.
  This now only works if the new DSLGW is inactive
  

So I now have a setup where either the inbound (NATted) traffic via WANGW OR the outbound internet traffic via DSLGW passes through my firewall, but not both.

Now I am now a bit lost as to where to start troubleshooting:

• I cannot see blocked packets in the Logs
• I already tried to work through the documentation on Gateways an MultiWAN
• I cannot find details on some settings like "reply-to"
• I tested tons of small changes to settings all with no positive effect
• I tried to reduce the setup as much as possible (no gateway monitoring)

Any hints please?

Thanks
Jan

Regarding the apinger, there is a workaround as per this post:
  https://forum.opnsense.org/index.php?topic=5196.msg21689#msg21689
which is to edit the WAN Gateway settings (System: Gateways: All) without changing anything.
It works for me on 17.1.8

Whether or not this remedies the DHCP Gateway problem, I cannot say, as I did not test it.
Maybe someone with more insight into OPNSense can see the connection between the two symptoms?

Do you guys have a default gateway set in System: Gateway: Status?

I do have an Entry in System: Gateways: Status called "WANGW" with a status of "pending"

And on this page in the upper left, there is the red "stopped" sign for the apinger Service

I do see the same symptoms after upgrading to 17.1.7 (I skipped 17.1.6):

- The default gateway is no longer sent to the DHCP clients
- the apinger service does not start

The respective field for the gw is empty, but it was so before the upgrade, so the indeed the mechanics changed. Setting it explicitly remedied the problem. I would expect that this should happen to quite a lot of users.

(Regarding the apinger, I did not yet check any details, it does not seem to impact me at  the moment.)