Carlos E. R. wrote:
Yes there is "a similar trick" - firewalld hasn't changed the basics of firewalling, only how it is managed.
Your definition above seems to translate to:
"accept smtp from 192.168.1.15" (for instance).
Ok, and where in the GUI do you write that? :-) Another rich rule?
That is left as an exercise for the reader. I don't use firewalld myself, I speak iptables.
There will be some straight forward way of defining that with/in firewalld too.
I don't see it in the GUI.
Given that it is such a simple rule "accept this traffic from that machine", I'm sure you just need to look closer.
An incoming connection can take any of those 13 addresses. Don't think "normally", think also bad actors.
Well, if you explain to us what you wish to permit, from where to where, I'm sure we can find a solution. Although, with (regularly?) changing addresses, any services (e.g. smtp) would need to listen on all addresses. You can fix the lower half (using EUI64), but not the upper. Anyway, isn't it all a bit moot? You said you have cancelled your participation in the beta-test programme. -- Per Jessen, Zürich (10.6°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes