Hi guys,
I wonder if
The wireless interface doesn't not support AP mode regardless of Debian or FreeBSD:
However in Debian I was able to create the access point with these rules:
On FreeBSD Unfortunately it does not initialize the interface:
Perhaps the key is the "driver" line, however I haven't found any suitable label that I can use.
Or simply you can't trick FreeBSD as I did with Debian.
Thanks...
I wonder if
hostapd has the same behavior on Debian and FreeBSD (15), or if the latter is stricter in applying the rules.The wireless interface doesn't not support AP mode regardless of Debian or FreeBSD:
Code:
drivercaps=581c001<STA,SHSLOT,SHPREAMBLE,MONITOR,WPA1,WPA2,WME>
cryptocaps=b<WEP,TKIP,AES_CCM>However in Debian I was able to create the access point with these rules:
Code:
### Wireless network name ###
interface=wlan0
#driver=nl80211
country_code=US
ssid=$ESSID-NAME
hw_mode=g
channel=1
wpa=2
wpa_passphrase=$PASSPHRASE
## Key management algorithms ##
wpa_key_mgmt=WPA-PSK
## Set cipher suites (encryption algorithms) ##
## TKIP = Temporal Key Integrity Protocol
## CCMP = AES in Counter mode with CBC-MAC
wpa_pairwise=TKIP
rsn_pairwise=CCMP
## Shared Key Authentication ##
auth_algs=1
## Accept all MAC address ###
macaddr_acl=0On FreeBSD Unfortunately it does not initialize the interface:
Code:
service hostapd forcestart
Password:
Starting hostapd.
bsd_set_if_media: SIOCSIFMEDIA Device not configured
bsd_init: failed to set operation mode
bsd driver initialization failed.
wlan0: interface state UNINITIALIZED->DISABLED
wlan0: AP-DISABLED
wlan0: CTRL-EVENT-TERMINATING
hostapd_free_hapd_data: Interface wlan0 wasn't startedPerhaps the key is the "driver" line, however I haven't found any suitable label that I can use.
Or simply you can't trick FreeBSD as I did with Debian.
Thanks...
Last edited: