OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Archive »
  • 18.1 Legacy Series »
  • NAT, port aliases, redirect not working after upgrade
« previous next »
  • Print
Pages: 1 2 [3] 4 5 6

Author Topic: NAT, port aliases, redirect not working after upgrade  (Read 26399 times)

hirschferkel

  • Jr. Member
  • **
  • Posts: 92
  • Karma: 3
    • View Profile
Re: NAT, port aliases, redirect not working after upgrade
« Reply #30 on: January 31, 2018, 03:29:31 pm »
My forwarding rules are just > take all incoming connections on a range of ports to one destination and it's corresponding ports.
Host is defined as an Alias (but that's not the problem).
Port range is defined as another Alias.

But what I found is, that old imported rules can not be edited!
On the other hand I can edit a new rule, but this one will not be available with NAT port forwarding!

Something has gone quite wrong here...

At the moment it only works if I choose "pass" as an option, in a manual, single port forwarding. But I can't select new rules which are set to pass. I guess old rules loose their definition, as they can not be edited either. So in the end I cannot set a portrange to be passed... that's wired.
« Last Edit: February 07, 2018, 10:47:34 am by hirschferkel »
Logged

slackadelic

  • Full Member
  • ***
  • Posts: 124
  • Karma: 9
    • View Profile
Re: NAT, port aliases, redirect not working after upgrade
« Reply #31 on: January 31, 2018, 03:47:26 pm »
I believe this is a hold over from then first jump to the 17.x series.

There was a change in how the rule was defined and some other options that were added/removed from the tabs/pages.

I had a similar issue originally, but spoke with franco and he suggested I recreate the rules and get rid of old ones.  Once I did that, things were back to normal.
Logged

Evil_Sense

  • Full Member
  • ***
  • Posts: 112
  • Karma: 15
    • View Profile
Re: NAT, port aliases, redirect not working after upgrade
« Reply #32 on: January 31, 2018, 03:49:22 pm »
Quote from: hirschferkel on January 31, 2018, 03:29:31 pm
My forwarding rules are just > take all incoming connections on a range of ports to one destination and it's corresponding ports.
Host is defined as an Alias (but that's not the problem).
Port range is defined as another Alias.

But what I found is, that old imported rules can not be edited!
On the other hand I can edit a new rule, but this one will not be available with NAT port forwarding!

Something has gone quite wrong here...

At the moment it only works if I choose "pass" as an option, in a manual, single port forwarding. But I can't select new rules which are set to pass. I guess old rules loose their definition, as they can not be edited either. So in the end I cannot set a portrange to be passed... that's wired.
Is it possible that you configuered the old rules in the NAT > Port Forward menu? They should be editable there, they are only visible in the rules if you choosed "create new rule"
« Last Edit: January 31, 2018, 03:59:00 pm by Evil_Sense »
Logged

hirschferkel

  • Jr. Member
  • **
  • Posts: 92
  • Karma: 3
    • View Profile
Re: NAT, port aliases, redirect not working after upgrade
« Reply #33 on: January 31, 2018, 04:17:54 pm »
AFAIK you can create rules only in the section Firewall > Rules > choose Interface > edit rules.
I created the old rules there, and the new ones.

The old ones stay not editable.

The new rules will not be available in Firewall > NAT > Port forward > edit forwarding rule > Filter rule association
« Last Edit: January 31, 2018, 04:24:57 pm by hirschferkel »
Logged

franco

  • Administrator
  • Hero Member
  • *****
  • Posts: 13957
  • Karma: 1210
    • View Profile
Re: NAT, port aliases, redirect not working after upgrade
« Reply #34 on: January 31, 2018, 05:16:41 pm »
> The old ones stay not editable.
>
> The new rules will not be available in Firewall > NAT > Port forward > edit forwarding rule > Filter rule association

I think that's how the association always worked, no? Non-editable if auto-created via association or manually selectable if not.


Cheers,
Franco
Logged

marjohn56

  • Hero Member
  • *****
  • Posts: 1677
  • Karma: 171
    • View Profile
Re: NAT, port aliases, redirect not working after upgrade
« Reply #35 on: January 31, 2018, 05:36:39 pm »
18.1_1 working well. Nice one guys.👍
Logged
OPNsense 21.7 - Qotom Q355G4 - ISP - Community Fibre 1Gbps.

Team Rebellion Member - If we've helped you remember to applaud

hirschferkel

  • Jr. Member
  • **
  • Posts: 92
  • Karma: 3
    • View Profile
Re: NAT, port aliases, redirect not working after upgrade
« Reply #36 on: January 31, 2018, 05:41:41 pm »
Hi Franco,

you're right, I missed that.

So if I autocreate a port forwarding, it will not work!
If I setup a rule one manually, it will not be available for a new port forwarding. So it won't work, anyway at the moment?
Logged

franco

  • Administrator
  • Hero Member
  • *****
  • Posts: 13957
  • Karma: 1210
    • View Profile
Re: NAT, port aliases, redirect not working after upgrade
« Reply #37 on: January 31, 2018, 05:52:07 pm »
Ah ok, that sounds like a viable theory. The problem with the auto-created association rules is that they are not real rules so their edit button was removed to prevent further breakage. Ideally, they shouldn't exist in a state that an user should feel the need to edit, but may therefore be in a twilight state that the new alias system cannot cope with yet. We'll take a closer look.


Thank you,
Franco
Logged

dcol

  • Hero Member
  • *****
  • Posts: 586
  • Karma: 49
    • View Profile
Re: NAT, port aliases, redirect not working after upgrade
« Reply #38 on: February 01, 2018, 05:57:48 pm »
18.1 update also killed my NAT. Patch fixed it for me.
Logged

franco

  • Administrator
  • Hero Member
  • *****
  • Posts: 13957
  • Karma: 1210
    • View Profile
Re: NAT, port aliases, redirect not working after upgrade
« Reply #39 on: February 01, 2018, 06:33:28 pm »
18.1.1 has been prepared and is ready for release tomorrow morning.


Cheers,
Franco
Logged

Phobus

  • Newbie
  • *
  • Posts: 5
  • Karma: 0
    • View Profile
Re: NAT, port aliases, redirect not working after upgrade
« Reply #40 on: February 01, 2018, 07:04:10 pm »
Hopefully 18.1.1 will fix the Alias problem.
18.1 breaks a lot of things for me; All Aliases not working, NAT-Patch not working, IPS Rule Updates not working...
Logged

opnsense_user12123

  • Guest
Re: NAT, port aliases, redirect not working after upgrade
« Reply #41 on: February 01, 2018, 07:32:03 pm »
Quote from: Phobus on February 01, 2018, 07:04:10 pm
Hopefully 18.1.1 will fix the Alias problem.
18.1 breaks a lot of things for me; All Aliases not working, NAT-Patch not working, IPS Rule Updates not working...

i have the same problems. on 17.7.12 everything was working fine.
Even a full reinstall didn´t help!
Logged

elektroinside

  • Hero Member
  • *****
  • Posts: 574
  • Karma: 51
    • View Profile
Re: NAT, port aliases, redirect not working after upgrade
« Reply #42 on: February 01, 2018, 07:43:59 pm »
Quote from: Phobus on February 01, 2018, 07:04:10 pm
Hopefully 18.1.1 will fix the Alias problem.
18.1 breaks a lot of things for me; All Aliases not working, NAT-Patch not working, IPS Rule Updates not working...

Aliases are working for me, though i have a cron job to update them.

Btw, @Franco, using the 'Aliases Resolve Interval' from Firewall: Settings: Advanced is indeed broken.

IPS rules / updates have a patch which fixed the issue.
Logged
OPNsense v18 | HW: Gigabyte Z370N-WIFI, i3-8100, 8GB RAM, 60GB SSD, | Controllers: 82575GB-quad, 82574, I221, I219-V | PPPoE: RDS Romania | Down: 980Mbit/s | Up: 500Mbit/s

Team Rebellion Member

Evil_Sense

  • Full Member
  • ***
  • Posts: 112
  • Karma: 15
    • View Profile
Re: NAT, port aliases, redirect not working after upgrade
« Reply #43 on: February 01, 2018, 08:05:55 pm »
With the fix, port aliases are working, but GeoIP alias (still) isn't.
« Last Edit: February 01, 2018, 08:27:40 pm by Evil_Sense »
Logged

marjohn56

  • Hero Member
  • *****
  • Posts: 1677
  • Karma: 171
    • View Profile
Re: NAT, port aliases, redirect not working after upgrade
« Reply #44 on: February 01, 2018, 08:08:33 pm »
Quote from: Evil_Sense on February 01, 2018, 08:05:55 pm
With the fix, port aliases are working, but GeoIP alias isn't.

Gesendet von meinem ONEPLUS A5000 mit Tapatalk

It's all a bit strange. My geo aliases and all others are working fine... I must have done something wrong . ???
Logged
OPNsense 21.7 - Qotom Q355G4 - ISP - Community Fibre 1Gbps.

Team Rebellion Member - If we've helped you remember to applaud

  • Print
Pages: 1 2 [3] 4 5 6
« previous next »
  • OPNsense Forum »
  • Archive »
  • 18.1 Legacy Series »
  • NAT, port aliases, redirect not working after upgrade
 

OPNsense is an OSS project © Deciso B.V. 2015 - 2023 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2