[opensuse] wlan not visible in YaST firewall configuration
Recently did a fresh install of Leap 42.2 on my laptop. Most of the time I only use ethernet with the wi-fi switch disabled, but wi-fi also works fine using Network Manager when I activate it. In YaST Firewall Configuration, under Interfaces, I only see eth0 configured in the External Zone. I'd have expected to see the wi-fi as a separate entry (I'm sure that's how it was in the past under previous OS versions). I've tried activating the wi-fi connection and going back into the Firewall Configuration, and I've tried rebooting with wi-fi activated, but nothing else ever appears there, and there's no facility to add an entry. I began thinking that maybe 'eth0' is just a misleading collective name for any connection, but in my sistemd journal entries I see the line "using default zone 'ext' for interface wlan0". I only know about the basics of firewall configuration in YaST and not how to configure it otherwise. Can I be sure that this is set up correctly, and why is a separate wlan0 entry not visible? gumb -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-02-24 18:20, gumb wrote:
I only know about the basics of firewall configuration in YaST and not how to configure it otherwise. Can I be sure that this is set up correctly, and why is a separate wlan0 entry not visible?
It is just a text file: /etc/sysconfig/SuSEfirewall2 that can be edited as root. I have this entry: FW_DEV_EXT="eth0 ppp0 wlan0"
but in my sistemd journal entries I see the line "using default zone 'ext' for interface wlan0".
Well, maybe it is automatic. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
On 24/02/17 18:42, Carlos E. R. wrote:
I have this entry:
FW_DEV_EXT="eth0 ppp0 wlan0"
My own only shows: FW_DEV_EXT="eth0" and I see no further reference to wlan0. So where is the journal getting this from? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-02-24 18:49, gumb wrote:
On 24/02/17 18:42, Carlos E. R. wrote:
I have this entry:
FW_DEV_EXT="eth0 ppp0 wlan0"
My own only shows:
FW_DEV_EXT="eth0"
and I see no further reference to wlan0. So where is the journal getting this from?
I don't know, but you can change the entry with any editor (as root). I have it that way since years. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
On 24/02/17 18:58, Carlos E. R. wrote:
On 2017-02-24 18:49, gumb wrote:
On 24/02/17 18:42, Carlos E. R. wrote:
I have this entry:
FW_DEV_EXT="eth0 ppp0 wlan0"
My own only shows:
FW_DEV_EXT="eth0"
and I see no further reference to wlan0. So where is the journal getting this from?
I don't know, but you can change the entry with any editor (as root). I have it that way since years.
Well I added it manually so the line now reads: FW_DEV_EXT="eth0 wlan0" When I now go into the YaST Firewall Configuration, I see eth0 as before, and a new entry listed as 'Custom', and showing as 'Unknown Interface wlan0'. I find that bizarre. The Journal knows about the interface and has assigned it the default external zone, whilst YaST on the other hand is trying to tell me the interface is unknown. openSUSE reporting has gone all Sean Spicer on me. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-02-26 06:20, gumb wrote:
On 24/02/17 18:58, Carlos E. R. wrote:
Well I added it manually so the line now reads:
FW_DEV_EXT="eth0 wlan0"
When I now go into the YaST Firewall Configuration, I see eth0 as before, and a new entry listed as 'Custom', and showing as 'Unknown Interface wlan0'.
I find that bizarre. The Journal knows about the interface and has assigned it the default external zone, whilst YaST on the other hand is trying to tell me the interface is unknown.
openSUSE reporting has gone all Sean Spicer on me.
Well, if the logs say that it is external, that is what matters. Try this: # Define additional firewall zones # # The built-in zones INT, EXT and DMZ must not be listed here. Names # of additional zones must only contain lowercase ascii characters. # To define rules for the additional zone, take the approriate # variable for a built-in zone and substitute INT/EXT/DMZ with the # name of the additional zone. # # Example: # FW_ZONES="wlan" # FW_DEV_wlan="wlan0" # FW_SERVICES_wlan_TCP="80" # FW_ALLOW_FW_BROADCAST_wlan="yes" # FW_ZONES="wlan" If that doesn't do the trick (not unknown) try wlan0. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
participants (2)
-
Carlos E. R. -
gumb