Messages

1

General Discussion / Scheduled NAT using local tags problem

« on: December 16, 2019, 07:36:55 am »

I wish to have a Port Forward to be active only for a specific time range, unfortunately this is not possible in OpnSense, but it does offer time Schedules on regular Firewall Rules.

So my thought was to setup a Firewall rule on the VLAN to "local tag" the traffic I am interested in.  This works and I can see the tag applied when viewing the Live View log.

Second step is to create the Port Forward on WAN and have it match the "local tag" set by the rule above from the VLAN.  However this does not work.

It seems that the processing order of NAT then afterwards Firewall Rules applies globally across all interfaces, eg:

VLAN & WAN
1)   NAT
2)   Firewall Rules

Which means the idea of tagging via a rule then using it to match on the Port Forward is not going to work.

I was expecting it to apply locally across each Interface, eg:

VLAN
1)   NAT
2)   Firewall Rules  <-- rule sets local tag
WAN
3)   NAT  <-- port forward matches local tag
4)   Firewall Rules


Can anyone clarify this or have any suggestion on how this could be made to work?

2

19.7 Legacy Series / Re: How to redirect all traffic for a specific port?

« on: December 16, 2019, 12:58:43 am »

I figured it out now, it was something stupid - on the Port Forward rule I had the wrong Interface selected.

3

19.7 Legacy Series / Re: How to redirect all traffic for a specific port?

« on: December 15, 2019, 11:38:25 pm »

Thanks for your thoughts, however 1-to-1 NAT would not achieve this as it maps source and destination IP addresses only.  We are wanting redirection to work on any Destination IP for a specific port 3000 only.

4

19.7 Legacy Series / How to redirect all traffic for a specific port?

« on: December 15, 2019, 12:31:34 am »

Running OpnSense 19.7.4

How can I configure OpnSense so all LAN traffic going to a specific destination port is redirected to a target IP on the LAN?

So if we have LAN IP 192.168.1.10 accessing an external IP address on port 3000, we want it redirected to target LAN IP 192.168.1.20:3000

I have tried configuring Outbound NAT but can't get this working and it seems this is broken in 19.7.x.  Can someone run me through the configuration steps in case I am doing something stupid?

5

General Discussion / Re: Multi WAN DNS issue

« on: November 09, 2018, 01:00:46 pm »

I had the same problem with DNS not working when failed over to the backup WAN connection.  I fixed it by;

1. Goto Services -> Unbound DNS -> General
2. Tick option "Enable Forwarding Mode" and Save.