Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - luhe

#1
Yes, it is working with 17.7.12_1-amd64.

Thanks,
Lukas
#2
Hello,

I updated the opnsense instance in my home network to version 18.1.8, but now my Port Forwards are broken.

An example for a broken rule is the following scenario:
I have a seperate network (VLAN). In this network, all HTTP and HTTPS requests should be redirected to a specific host.

The configuration is the following:

Interface: SHOUTBOX
Source: INVERT h_shoutbox
Source port range: any-any

Destination port range: HTTP

Redirect target IP: h_shoutbox
Redirect target port: HTTP

NAT reflection: Use system default
Filter rule association: Rule NAT


As seen abobe, this rule should redirect all HTTP requests on the SHOUTBOX interface.

However, when I enable this rule, the redirect is active on all interfaces - i.e. if I access any website on my LAN, I get redirected to the shoutbox host. This should NOT happen.

The following other settings are active:

Reflection for port forwards: checked
Reflection for 1:1: checked
Automatic outbound NAT for Reflection: checked

Automatic outbound NAT rule generation


Are there any changes in opnsense 18.1, which would explain this weird behaviour?

Thanks for your help,
Lukas
#3
Thanks for your quick response!
I re-enabled "Override DNS by ISP DNS servers" and can confirm that 0b38eff5f fixed the problems - DNS queries are now responding again.

Thank you for your great help,
Lukas
#4
Just wanted to note that I too was affected by this issues after upgrading to 17.7.
If there is anything else to help debuggiung/fixing it, feel free to ask me.
Workaround with overriding DNS servers helped.