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))