I tested the list with a few addresses.
Both suricata and URL filter worked well.
2 Likes
Updatet the latest change for WLAN this morning (74→75 if I remember correct). Entering the password “Eins&Zwei=3” still leads to WLAN not coming up. This is the log:
Feb 6 11:36:55 ipfire hostapd: blue0: interface state ENABLED->DISABLED
Feb 6 11:36:55 ipfire hostapd: blue0: AP-DISABLED
Feb 6 11:36:55 ipfire hostapd: blue0: CTRL-EVENT-TERMINATING
Feb 6 11:36:55 ipfire hostapd: nl80211: deinit ifname=blue0 disabled_11b_rates=0
Feb 6 11:36:57 ipfire kernel: BLKLST_DSHIELD IN=red0 OUT= MAC=00:0d:b9:3f:f6:69:00:01:5c:80:0a:46:08:00 SRC=147.185.132.48 DST=82.136.105.63 LEN=44 TOS=0x00 PREC=0x00 TTL=251 ID=54321 PROTO=TCP SPT=56115 DPT=3389 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 6 11:36:57 ipfire ntpd[2990]: Deleting 7 blue0, [192.168.5.11]:123, stats: received=0, sent=0, dropped=0, active_time=19 secs
Feb 6 11:36:57 ipfire hostapd: Line 36: invalid WPA passphrase length 0 (expected 8..63)
Feb 6 11:36:57 ipfire hostapd: WPA-PSK enabled, but PSK or passphrase is not configured.
Feb 6 11:36:57 ipfire hostapd: 2 errors found in configuration file ‘/etc/hostapd.conf’
Feb 6 11:36:57 ipfire hostapd: Failed to set up interface with /etc/hostapd.conf
Feb 6 11:36:57 ipfire hostapd: Failed to initialize interface
I restarted ipfire, cleaed browser cache and restartet the browser, but this did not help
Just to be sure this is really the right update: Pakfire says about installed addons: hostapd-f747ae0-73
No that is not correct. It is not the hostapd addon that you have to re-install it is the CU200 that you have to update.
Change the entry in the /opt/pakfire/db/core/mine file from 200 to 199 and then go back to the pakfire page and refresh the lists and you will see that there is an update from 199 to 200 available. That will give you the latest updated version of CU200 Testing.
The update process for a Testing version is described in the documentation at
https://www.ipfire.org/docs/configuration/ipfire/pakfire/testing#update-testing
EDIT:
You will also see the version number of hostapd go from 72 to 73 but that is not a change to the hostapd binary but the update to the initscript for hostapd, where some of the changes have been made.
EDIT2:
I have just updated my IPFire Prime to the latest CU200 Testing
IPFire 2.29 (x86_64) - Core-Update 200 Development Build: master/ff0daa16
and ran it with Eins&Zwei=3
and it worked correctly and I was able to connect with my laptop client.
EDIT3:
Also just tested it with the remaining characters that previously were still getting filtered.
The following characters can all now also be used successfully
&"$()*]^`{}~
If a single quotation mark ' is used in the password, then after pressing Save on the WUI page the full password will be saved in to the hostapd.conf file and the settings file but on the WUI page you will only see the password up to the character before the ' character.
So it looks like the perl code for the WUI page is treating the ' character as defining the end of the string.
So a ' can be successfully used for connection but on the WUI page you will not see the whole password you defined.
2 Likes
Thanks. I’ll do that as soon as possible and report afterwards
Bingo. Up and running now. Of course I will have to do mor tests with my different clients, which are on another WLAN-Router at the moment. That will take some more time, but things look good.
1 Like