NAT, port aliases, redirect not working after upgrade

Started by ssachse, January 30, 2018, 12:36:46 PM

Previous topic - Next topic
Configured mine the same way, submitted, pfTables shows it is populated.

February 13, 2018, 07:08:00 PM #76 Last Edit: February 13, 2018, 07:09:44 PM by Evil_Sense
Quote from: Dominian on February 13, 2018, 06:53:03 PM
Configured mine the same way, submitted, pfTables shows it is populated.
Hmm.. Seems it doesn't get populated if the name is the same as the value

Edit: Deleting aliases also doesn't remove the tables..

That KIND of makes sense.  I set the name to GeoIP and just selected switzterland.. I didn't even think about the naming just as yours is in the interface, my bad. 

Quote from: Dominian on February 13, 2018, 07:08:53 PM
That KIND of makes sense.  I set the name to GeoIP and just selected switzterland.. I didn't even think about the naming just as yours is in the interface, my bad.
Thanks for testing and pointing me in the right direction :)


Quote from: Dominian on February 13, 2018, 07:42:14 PM
Did you get it working now?
Yes, I changed the name and it's working perfectly fine :)

Also tested with other countries, it's true, if the name matches the value, nothing gets populated.

Now pfTables is showing some non existent tables, even after the refresh_aliases and reload command, but that doesn't bother me much ^^

Ok, mystery almost solved. Added a follow-up for this https://github.com/opnsense/core/issues/2199 to discuss what to clean up to prevent users running into it.


Thanks!
Franco