Messages

1

General Discussion / Re: 3CX Phone System and OPNSense

« on: March 11, 2024, 09:10:47 pm »

This NAT outbound VOIP configuration doesn't require port forwarding?

I had a similar situation and the answer is most likely this:

In Firewall: NAT: Outbound set the mode to "Hybrid outbound NAT rule generation (automatically generated rules are applied after manual rules)"

Then add a rule:

Disabled: (unchecked)
Do not NAT: (unchecked)
Interface: WAN
TCP/IP Version: IPv4 (unless you are using IPv6 on your LAN)
Protocol: Any
Source invert: (unchecked)
Source address: The local LAN address of your 3CX server
Source port: Any
Destination invert: (unchecked)
Destination address: Any
Destination port: Any
Translation / target: interface address
Log: (unchecked unless you prefer logging)
Translation / port: (leave blank)
Static-port: (CHECKED - THIS IS THE MOST IMPORTANT SETTING!!!!!)
Pool Options: Default
Set local tag: (leave blank)
Match local tag: (leave blank)
No XMLRPC Sync: (unchecked)
Description: 3CX (or whatever you like)

Enabling the static-port option is the key to getting it to work.  Strangely, that is the only setting on the page for which no help is available.

There is one other thing, if you have a dynamic DNS host hame for your server (or a host name other than that used with OPNesnse), go to System: Settings: Administration and put it in the Alternate Hostnames field.

2

22.1 Legacy Series / Wireguard with two WAN

« on: March 06, 2023, 06:41:30 am »

I have OPNsense version: 22.1.8_1-amd64
I setup WireGuard on the OPNSense box with tho WAN and I am able to connect and access the LAN side hosts, etc. However, it only works with the WAN which is currently the default gateway. If that WAN is down, then OPNSense switches the default gateway (gateway switching is enabled) and WireGuard peers can utilize the 2nd WAN to connect. However, as long as WAN1 is "up", peers cannot connect to WAN2. Well, actually the peers appear to be able to connect to WAN2 but traffic isn't properly received (a few bytes are received but no network services such as ping, ssh, etc. work).

Can anyone point me in the right direction of how to setup WireGuard on OPNSense such that peers can connect to either WAN interface?

3

Hardware and Performance / Re: traffic between untagged vlan and a tagged vlan basically dies

« on: September 07, 2022, 08:55:22 am »

Don't run tagged and untagged traffic over the same interface.

WHY NOT??

4

22.1 Legacy Series / OPNsense updates

« on: July 28, 2022, 06:31:06 am »

I need some advice on OPNsense updates.
I plan to use OPNsense as a replacement for a real production router.
I hesitate to apply updates due to the risk of bugs that could affect OPNsense functionality.
What is the best strategy for applying updates to a production OPNsense router?