무선 UCI 설정은 / etc / config / wireless에 있습니다.

장치에 이더넷 포트가 있으면 기본적으로 무선이 꺼져 있습니다. disable 1 을 disable 0 으로 변경하여 / etc / config / wireless 에서 활성화 할 수 있습니다

일반적인 무선 설정 파일에는 채널, 드라이버 유형 및 txpower, 무선 장치 상단에 무선 네트워크를 정의하는 wifi 인터페이스 와 같은 일반적인 무선 속성을 지정하는 Wi-Fi 장치 가 적어도 하나 이상 포함되어 있습니다.

Wi-Fi 장치 는 시스템에 있는 실제 무선 장치를 나타냅니다. 이 세션에 있는 옵션은 채널 또는 안테나 선택과 같이이 무선 인터페이스의 모든 무선 네트워크에 공통된 속성을 설명합니다.

최소 Wi-Fi 장치 선언은 아래 예와 같습니다. 식별자 및 옵션은 칩셋 유형이나 드라이버에 따라 다를 수 있습니다.

config 'wifi-device' 'wl0'
	option 'type'    'broadcom'
	option 'channel' '6'

• wl0 은 무선 어댑터의 내부 식별자 입니다.
• broadcom은 칩셋 / 드라이버 유형을 지정합니다.
• 6 은 장치가 작동하는 무선 채널 입니다

장치 세션에 대해 가능한 옵션은 아래 표에 나열되어 있습니다. 모든 옵션이 모든 칩셋 / 드라이버 유형에 사용되는 것은 아니며, 자세한 내용은 주석을 참조하십시오.

완전한 무선 구성에는 하드웨어 상단에 무선 네트워크를 정의하기 위해 어댑터 당 최소 1 개의 wifi-iface 섹션이 포함됩니다. 일부 드라이버는 장치 당 여러 개의 무선 네트워크를 지원합니다.

• broadcom 코어 리비전이 9 보다 크거나 같으면 (참조 dmesg | grep corerev)
• mac80211

wifi-iface 선언에 대한 최소 예가 아래에 나와 있습니다.

config 'wifi-iface'
	option 'device'     'wl0'
	option 'network'    'lan'
	option 'mode'       'ap'
	option 'ssid'       'MyWifiAP'
	option 'encryption' 'psk2'
	option 'key'        'secret passphrase'

• wl0는 기본 무선 하드웨어의 식별자입니다.
• lan 은 wifi가 연결된 네트워크 인터페이스를 지정합니다.
• ap는 이 예제의 opetion 모드, 액세스 포인트 입니다.
• MyWifiAP는 브로드 캐스트 된 SSID입니다.
• psk2는 WPA2 PSK 무선 암호화 방법을 지정합니다.
• secret passphrase는 비밀 WPA 암호입니다

wifi-iface 세션 공통 옵션들은 아래와 같습니다.

WPA 모드 이외에도,encryption 옵션또한 그룹과 피어의 암호를 사용하는 것을 지정합니다. 암호를 오버라이드 하기 위해서,encryption의 값을 mode+cipher형식으로 지정해야 합니다. 가능한 조합에 대해서 아래의 표를 참조하세요.hwmode의 인터페이스를 ng 또는 na설정한다면, 그러면 CCMP 암호가 항상 목록에 추가 됩니다.

Listing of Access Point related options for WPA Enterprise.

Listing of Client related options for WPA Enterprise.

option auth 'auth=MSCHAPV2'

or

option auth 'auth=PAP'

Listing of Wi-Fi Protected Setup related options.

Minimal steps needed to get WPS running:

• Add option wps_pushbutton '1 ' to a config wifi-iface section that is configured for WPA2-PSK in /etc/config/wireless
• opkg update
• opkg remove wpad-mini
• opkg install wpad hostapd-utils
• reboot

After rebooting, instead of pushing the WPS button, you can manually initiate the WPS process (which is safer than using the button if it doubles as a reset button):

hostapd_cli wps_pbc

When using WPS-PIN:

• Add option wps_label '1 ' to a config wifi-iface section that is configured for WPA2-PSK in /etc/config/wireless
• opkg update
• opkg remove wpad-mini
• opkg install wpad hostapd-utils
• reboot

After rebooting, the WPS PIN needs to be given to hostapd each time a station tries to connect. The PIN may NOT be used multiple times, as an active attacker can recover half of it during each try. The “any” keyword can be replaced by the specific stations EUUID, as printed in hostapd log.

hostapd_cli wps_pin any $PIN

/etc/config/wireless example fie required for better understanding like below

root@XYZ:~# cat /etc/config/wireless
...
config wifi-iface
	option device 'radio0'
	option mode 'ap'
	option ssid 'My-WiFi-Home'
	option network 'lan'
	option encryption 'psk2'
	option key 'WiFipassword'
	option ieee80211w '0'
	option wps_pushbutton '1'
root@XYZ:~#

Wireless interfaces are brought up and down with the wifi command. To (re)start the wireless after a configuration change, use wifi, to disable the wireless, run wifi down. In case your platform carries multiple wireless devices it is possible to start or run down each of them individually by making the wifi command be followed by the device name as a second parameter. Note: The wifi command has an optional first parameter that defaults to up , i.e. start the device. To make the second parameter indeed a second parameter it is mandatory to give a first parameter which can be anything except down. E.g. to start the interface wlan2 issue: wifi up wlan2; to stop that interface: wifi down wlan2. If the platform has also e.g. wlan0 and wlan1 these will not be touched by stopping or starting wlan2 selectively.

To rebuild the configuration file, e.g. after installing a new wireless driver, remove the existing wireless configuration (if any) and use the wifi config command:

rm -f /etc/config/wireless
wifi config

The default max channel width of 20MHz supports a max speed of 150Mbps. Increasing this to 40MHz will increase the maximum theoretical speed to 300Mbps. The catch is that in areas with a lot of wifi traffic (and Bluetooth etc. which share the same radio frequencies), 40MHz may decrease your overall speed. Devices should detect interference when using 40MHz, and drop back to 20MHz. Edit htmode options in the file /etc/config/wireless and restart the wifi AP to test various channel widths. Note that option htmode should be set to either HT40+ (for channels 1-7) or HT40- (for channels 5-11) or simply HT40.

In many countries, operating WiFi devices on some or all channels in the 5GHz band requires radar detection and DFS (explanation). If you define a channel in your wireless config that requires DFS according to your country regulations, the 5GHz radio device won’t start up unless the firmware image is able to provide DFS support (i.e. it is both included and enabled). More technical details of the Linux implementation can be found here. DFS works as follows in Linux: The driver detects radar pulses and reports this to nl80211 where the information is processed. If a series of pulses matches one of the defined radar patterns, this will be reported to the user space application (e.g. hostapd) which in turn reacts by switching to another channel.

The following configuration selects channel 104 which needs DFS support as implicitly stated with country code DE:

config wifi-device  radio0
	option type     mac80211
	option channel  104
	option hwmode	11a
	option path	'pci0000:00/0000:00:00.0'
	option htmode	HT20
	option country 'DE'

config wifi-iface
	option device   radio0
	option network  lan
	option mode     ap
	option ssid     lede
	option encryption none

You can check the country (regulatory domain) your WiFi card thinks it must conform to with

iw reg get

If in doubt, double check your hostapd-phy.conf to make sure it contains the following values, and that your country code is set:

country_code=DE
ieee80211n=1
ieee80211d=1
ieee80211h=1
hw_mode=a

If radar detection is working, DFS channels will show up like this (here for Belgium, iw phy1 info output trimmed):

Frequencies:
* 5220 MHz [44] (17.0 dBm)
* 5240 MHz [48] (17.0 dBm)
* 5260 MHz [52] (20.0 dBm) (radar detection)
DFS state: usable (for 2155257 sec)
DFS CAC time: 60000 ms
* 5280 MHz [56] (20.0 dBm) (radar detection)
DFS state: usable (for 2155257 sec)
DFS CAC time: 60000 ms

logread -f

If you select a channel that requires DFS in your country and enable HT40, this may result in the DFS start_dfs_cac() failed error (visible with logread):

Configuration file: /var/run/hostapd-phy1.conf
wlan1: interface state UNINITIALIZED->COUNTRY_UPDATE
wlan1: interface state COUNTRY_UPDATE->HT_SCAN
wlan1: interface state HT_SCAN->DFS
wlan1: DFS-CAC-START freq=5680 chan=136 sec_chan=-1, width=0, seg0=0, seg1=0, cac_time=60s
DFS start_dfs_cac() failed, -1
Interface initialization failed
wlan1: interface state DFS->DISABLED
wlan1: AP-DISABLED
hostapd_free_hapd_data: Interface wlan1 wasn't started

Changing your configuration to HT20 should resolve this.