hi Freek, is there any difference between explicit list of interfaces and 'any'? Because now I have: FW_DEV_EXT="enp0s25 wlp3s0" and I need to restart firewall after WiFi connection. m. On nedeľa, 10. apríla 2016 22:33:57 CEST Freek de Kruijf wrote:
Op zondag 10 april 2016 22:16:36 schreef Michal Hlavac:
Hi,
I have some open ports in OpenSuSE firewall (kdeconnect, NFS client, SMFP device discovery). With wired connection everything works, but with WiFi doesn't. I realized that there is no zone attached to wlp3s0 wireless interface. So I created file /etc/sysconfig/network/ifcfg-wlp3s0 with content:
BOOTPROTO='dhcp' STARTMODE='auto'
After that (and firewall restart) everything started to work. I can see wlp3s0 interface attached to external zone (yast2 firewall).
But when I restart computer, then login to KDE session, connect to WiFi, it doesn't work (e.g. I can't connect to android phone via kdeconnect). I have to restart firewall to make it work.
thanks, m.
You have to put your external interfaces in /etc/sysconfig/SuSEfirewall2 in FW_DEV_EXT, but putting "any" in it is sufficient.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org