Untangle v15.1 Access Rule - Destined Local Missing

[sky-knight]

Build: 15.1.0.20200826T124051.636f288233-1buster

/admin/index.do#config/network/advanced/access_rules

Trying to make a new rule, click add condition, and destined local isn't in the list. My rules that used it still have it, but I can't make new ones?

What happened?

[jcoffin]

Access rules never had destined local. Since access rules are for the box itself, destined local is redundant.

[sky-knight]

My existing rules that say Destined Local say otherwise... though what you say does make sense, so I should update my brain to assume there's an implied Destination Local flag on all Access Rules.

[Jim.Alles]

My existing rules that say Destined Local say otherwise

screen shot or it didn't happen. teehee.
At least you aren't talking to yourself!

[sky-knight]

Wish granted... and while we're on the topic can we get a forum package that's made in the last decade? Because I can simply copy / paste screen grabs on other forums, having to take the time to upload them to my web server is a pain in the rear.



I can edit those rules, and the destined local flag appears as expected. But I can't add it to new rules, and if this is "normal" fine... but... it's invisible, and confusing... and not the same as literally every other place in untangle that uses this matcher.

[Jim.Alles]

Wish granted... and while we're on the topic can we get a forum package that's made in the last decade? Because I can simply copy / paste screen grabs on other forums, having to take the time to upload them to my web server is a pain in the rear.

I second that, for sure. I have taken to running Firefox on Windows 10 just for the forums.

but... it's invisible, and confusing... and not the same as literally every other place in untangle that uses this matcher.

huh. I can't get to it, and don't have any. I wonder if that is an artifact from import/export, but then again, why would you?
Things that make you go HUH.

[sky-knight]

This install has been around since 10.0, upgraded all the way. Things are... strange sometimes. And I forget what changes went with what. It's all a murky ball of muck in what pretends is my memory.

*Edit* Correction the install hasn't lived that long, but the configuration has.

[jcoffin]

Now I'm curious when it was removed.

Edit: It was removed in 13.0.

[sky-knight]

Yeah... and the stupid part is I've reported this before.

https://forums.untangle.com/feedback...ned-local.html

Stupid brain...

[Jim.Alles]

Brains are good at this, I think. It is one of those little details that really does mean something — so it re-surfaces even after making the painful decision to ignore stuff that is outside of our control.

While I think the reasoning for removing it in the logic is sound, we most certainly need a blurb in the wiki page at minimum, and there should be mention on the config screen as well. It could go a long way in clearing up the confusion of the purpose and function of access rules for those who don't have a solid understanding of the underlying iptables in the first place.

(Oh, wait nftables now? A search doesn't turn up anything in changelogs for that migration).

That would include 99% of the people on the planet. I know I am glad that NGFW handles it for me.

Thanks, Untangle!