Am Montag, 24. November 2014, 13:19:14 schrieb Roger Luedecke:
On Mon, 2014-11-24 at 21:07 +0100, Mathias Homann wrote:
Am Montag, 24. November 2014, 11:55:28 schrieb Roger Luedecke:
On Mon, 2014-11-24 at 15:55 +0100, Mathias Homann wrote:
Hi,
Request for discussion: Should we offer firewalld as alternative for SuSEfirewall2?
I think we should...
reasoning:
mobile users (laptops) who use NetworkManager / Wicked for managing their ip connectivity "in userspace" would want to be able to have multiple wifi setups that end up being in different zones.
I'm going to try to package the latest firewalld from fedora for openSUSE, and test it with 13.2.
Progress report will follow in due time.
cheers MH
I think I fail to see what the problem with our current firewall is?
Then please explain to me how to do this:
I want to use NetworkManager (or wicked). I want to have one WiFi definition for my Wifi at home. I want to have the wireless interface to be in the internal network when that configuration is active. I also want to have another WiFi definition called "Work", and when that one is active I want the WiFi to be in the work zone. I also want to have any further WiFi definitions that might crop up occasionally (airport, starbucks, you name it) to be in the "public" zone by default.
Frankly, I want the "Zone" field in network manager to be useful. With SuSEFirewall2 it isn't.
Cheers MH
I couldn't since I failed to see what the problem with our current firewall was.
The problem is that SuSEFirewall2 can't have the same interface in different zones depending on which wireless you connect to. The problem also is that SCPM is not working with systemd, so it can't be used to switch configurations on boot based on which WiFi you're *going* to connect to. Did I make myself clear? Cheers MH -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org