Messages

From earlier posts, I was used to constructive help on this forum. Not to people just slapping each other with RTFM or STFU.
And then making fun about it with each other.
This kind of condescending communication is not constructive at all.

I tried to form some sense of your little unkind words. But I just did not understand. Because like I kept saying, it was different to what I was used to, and I didnt know if something went wrong during an update or something changed.
 
And something did change.
As I went over all the options in making a new rule in destination nat.
I found that the 3 options under: 'option firewall rule' are new (to me at least).
manual, pass, register rule.

All my rules seem to be manual, and that's why they both need to be updated. Unlike before, when I only updated in one location.
And this is why it behaved differently than I was used to.
The manual confirms that its new.
https://docs.opnsense.org/manual/nat.html#destination-nat-port-forward

Thanks.

I played around a bit and the port forward only works when enabled in both rules AND destination NAT. If either one is disabled, it will not work.
If I delete one of them. Either in rules or destination NAT, the port forward also does not work anymore.
Same goes for changing a rule or creating a new one. I will have to change or create them in both locations before they work.

Now I have been port forwarding for a long time in OPNsense.
And this used to be all done from 1 location. Not 2.

I know there were changes to this recently. Sp either something is wrong here. Or this might be the change?!
But it seems very illogical to have it in 2 locations, so my guess is something is wrong here.

Thanks!

I have been reading a bit more on this. And I see there are quite some people asking about this. Yet I didnt really find an answer that explains me why the port forwarding is now handled in 2 separate locations. It seems confusing to me as it used to be in one location.
Also I cant find if this is by design or something just went wrong here during migrations/updates.
I am going to experiment a bit with making new rules and seeing how they end up in the destination nat.

Thanks!

Hi all.


I run: OPNsense 26.7.5-amd64. This router has been running in this config for years now.
Yesterday I needed to enable some already long ago configured forwarded ports.
So I clicked on enable port under: Firewall / Rules. But somehow I was not getting through.
I checked a bit further and found the same rules under NAT / Destination NAT.
And only after I enabled them there too, the port was actually opened. The 2 dont seem to work together.

This is something new to me, as I did this same thing under rules a few months ago, and it just worked.
Is this a new thing? Or is something not correct.

I did do the 4/5 step migration wizard thingy of downloading the settings. Uploading them. And then the cleaning up last step.

Thanks!

I have been looking into this. Giving ALL access does not seem like my preference.  :)
So I found the place to change the dnsmasq.
I also found how it supposedly should be entered

server=/myserver.com/#
address=/.myserver.com/100.101.102.103

I just dont seem to find how to translate this to my situation.

My iprange for the vpn tunnel is 10.1.3.1/24
How would I write this in?

Thanks!

Its that easy, eh! I will try that.
Thanks!

Hi all.


I searched but could'nt really find the answer.
So i set up the wireguard instance and made my peers. This was all quite straight forward with the opnsense guide.
But i also use a dns server on a pi with pihole. For my normal ip range on the opnsense router this works fine.

But I noticed the vpn is not using the pihole.
Probably as in the tutorial the dns is set to the first of the vpn ip range.

Can i just change this? Or what is the  way to make the vpn ip range also use the pihole dns server?

Thanks!

Just one more thing to add.
So I already changed some port forwards to the new interface I made for the pppoe connection. Which also worked fine.

But after deleting the new interface and pointing the pppoe to WAN, I noticed those port forwards where pointing to nothing.
I thought changing them back to WAN and WAN address would be enough. But they still didnt work.
Then I noticed the rules for those port forwards I changed, where also gone.
I didnt immediately see a way to quickly make a new rule for them. So I just cloned those port forwards and deleted the original ones.
This automatically made new rules.

Thanks!

Thanks for the confirmation. I assigned it to WAN and deleted the extra interface. At first it didnt work. Internet would not start.
I put it back to how it did work with the extra interface. Then I noticed the new interface was disabled by default. Only after manually enabling it internet would work.
So I tried again assigning it to WAN and deleting the extra created interface. And then disabling / re-enabling WAN. After that the pppoe worked like normal on WAN.

Thanks!

Hi all!


We recently got a new home internet provider. So we went from a simple dhcp on WAN. To a PPPOE connection.
I followed this tutorial: https://docs.opnsense.org/manual/how-tos/pppoe_isp_setup.html
But we have no VLAN, and the tutorial is a bit focussed on it. So I was a bit confused. Everything works fine. No problem. Speed is very close to promised and no heavy cpu draw. i3-7100.

But I am just wondering if this is the way it should be set up, with the new interface;ONE next to WAN and LAN.
Or if I should have just assigned WAN to the new PPPOE device.
Cause I had to change my port forwards to point to ONE as well now.

Thanks!

Ah yes, I meant the user certificate. as it also expired. I use otp.

I made new certificates.. Not noticing the authority was also expired. ;)
So I did everything twice. I guess I wont forget anymore now.

My VPN works like before again.
Thanks!

So I got home.
SSLVPN Server Certificate has indeed epired.
It was only valid for a year. User certificate is also almost expired.

I set it up myself, I guess a year ago, using a guide.
I am still learning about what I actually did and how it affects everything. I never did this before.

As I read, there is no simple renewal option. I just have to remake the certificate. And the user.
Is that right?

I am sorry I dont have more info at the moment. I am on holiday. Thats the whole reason I was using the vpn ;)

And does anyone happen to know the standard expiration date? I thought it was 10 years?

Hi all.


I have been using openvpn for quite some time now without problems. Since last Thursday though, i get this error on all clients.
Peer certificate verification failure.
Nothing changed on server. Maybe client got updated?
Was there some change in certification rules or so? Can it be expired?
Anyone have an idea?

Thanks!

Well to start with just a few IP would be fine.

But I cant seem to let it show anything else than wan or lan. Not specified to IP.