From ca5c55acb366ff5f80af00737a8110673ccf252b Mon Sep 17 00:00:00 2001 From: Andrii Pientsov Date: Thu, 21 May 2020 09:08:42 +0300 Subject: Remove duplicates --- .../cell-radio-carrierswitch.default | 6 - .../cell-radio-carrierswitch.init | 26 - .../multitech/cell-radio-carrierswitch_1.0.bb | 25 - recipes-core/multitech/commissioning_1.0.1.bb | 42 - recipes-core/multitech/config/99_radio | 24 - recipes-core/multitech/config/chat_wrapper | 205 -- recipes-core/multitech/config/chat_wrapper.default | 20 - .../multitech/config/config-mths/default/bluetooth | 8 - .../multitech/config/config-mths/default/dnsmasq | 27 - .../multitech/config/config-mths/default/hostapd | 11 - .../multitech/config/config-mths/default/ntpd | 36 - .../multitech/config/config-mths/default/rs9113 | 14 - .../config/config-mths/default/usb-gadget | 6 - .../config/config-mths/dnsmasq.d/dhcp.conf | 12 - .../multitech/config/config-mths/hostapd.conf | 1996 -------------------- .../config/config-mths/ifplugd/ifplugd.action | 30 - .../multitech/config/config-mths/ifplugd/usb0.conf | 2 - .../multitech/config/config-mths/ifplugd/usb1.conf | 2 - .../config/config-mths/modprobe.d/cfg80211.conf | 7 - .../config/config-mths/modprobe.d/mts-io.conf | 1 - .../config/config-mths/network/interfaces.mths | 12 - recipes-core/multitech/config/config.init | 207 -- recipes-core/multitech/config/network/interfaces | 81 - recipes-core/multitech/config/ppp/chap-secrets | 3 - recipes-core/multitech/config/ppp/options | 27 - recipes-core/multitech/config/ppp/pap-secrets | 3 - .../multitech/config/ppp/peers/README.fwswitch | 76 - recipes-core/multitech/config/ppp/peers/cdma | 9 - recipes-core/multitech/config/ppp/peers/cdma_chat | 18 - recipes-core/multitech/config/ppp/peers/gsm | 11 - recipes-core/multitech/config/ppp/peers/gsm_chat | 47 - recipes-core/multitech/config/ppp/peers/l4e1 | 11 - recipes-core/multitech/config/ppp/peers/l4e1_chat | 43 - recipes-core/multitech/config/ppp/peers/l4n1 | 11 - recipes-core/multitech/config/ppp/peers/l4n1_chat | 1 - .../multitech/config/ppp/peers/l4n1_chat_non_vz | 67 - .../multitech/config/ppp/peers/l4n1_chat_vz | 44 - recipes-core/multitech/config/ppp/peers/lap3 | 11 - recipes-core/multitech/config/ppp/peers/lap3_chat | 43 - recipes-core/multitech/config/ppp/peers/leu1 | 11 - recipes-core/multitech/config/ppp/peers/leu1_chat | 43 - recipes-core/multitech/config/ppp/peers/lna3 | 11 - recipes-core/multitech/config/ppp/peers/lna3_chat | 1 - .../multitech/config/ppp/peers/lna3_chat_non_vz | 68 - .../multitech/config/ppp/peers/lna3_chat_vz | 44 - recipes-core/multitech/config/ppp/peers/lsp3 | 11 - recipes-core/multitech/config/ppp/peers/lsp3_chat | 19 - recipes-core/multitech/config/ppp/peers/lvw2 | 11 - recipes-core/multitech/config/ppp/peers/lvw2_chat | 27 - recipes-core/multitech/config_2.3.bb | 95 - .../multitech/reset-handler/reset-handler.default | 2 - .../multitech/reset-handler/reset-handler.init | 30 - .../multitech/reset-handler/reset-handler.sh | 74 - recipes-core/multitech/reset-handler_1.0.bb | 30 - recipes-core/multitech/upgrade-reboot_1.0.0.bb | 17 - 55 files changed, 3719 deletions(-) delete mode 100644 recipes-core/multitech/cell-radio-carrierswitch/cell-radio-carrierswitch.default delete mode 100644 recipes-core/multitech/cell-radio-carrierswitch/cell-radio-carrierswitch.init delete mode 100644 recipes-core/multitech/cell-radio-carrierswitch_1.0.bb delete mode 100644 recipes-core/multitech/commissioning_1.0.1.bb delete mode 100644 recipes-core/multitech/config/99_radio delete mode 100755 recipes-core/multitech/config/chat_wrapper delete mode 100644 recipes-core/multitech/config/chat_wrapper.default delete mode 100644 recipes-core/multitech/config/config-mths/default/bluetooth delete mode 100644 recipes-core/multitech/config/config-mths/default/dnsmasq delete mode 100644 recipes-core/multitech/config/config-mths/default/hostapd delete mode 100644 recipes-core/multitech/config/config-mths/default/ntpd delete mode 100644 recipes-core/multitech/config/config-mths/default/rs9113 delete mode 100644 recipes-core/multitech/config/config-mths/default/usb-gadget delete mode 100644 recipes-core/multitech/config/config-mths/dnsmasq.d/dhcp.conf delete mode 100644 recipes-core/multitech/config/config-mths/hostapd.conf delete mode 100755 recipes-core/multitech/config/config-mths/ifplugd/ifplugd.action delete mode 100644 recipes-core/multitech/config/config-mths/ifplugd/usb0.conf delete mode 100644 recipes-core/multitech/config/config-mths/ifplugd/usb1.conf delete mode 100644 recipes-core/multitech/config/config-mths/modprobe.d/cfg80211.conf delete mode 100644 recipes-core/multitech/config/config-mths/modprobe.d/mts-io.conf delete mode 100644 recipes-core/multitech/config/config-mths/network/interfaces.mths delete mode 100644 recipes-core/multitech/config/config.init delete mode 100644 recipes-core/multitech/config/network/interfaces delete mode 100644 recipes-core/multitech/config/ppp/chap-secrets delete mode 100644 recipes-core/multitech/config/ppp/options delete mode 100644 recipes-core/multitech/config/ppp/pap-secrets delete mode 100644 recipes-core/multitech/config/ppp/peers/README.fwswitch delete mode 100644 recipes-core/multitech/config/ppp/peers/cdma delete mode 100644 recipes-core/multitech/config/ppp/peers/cdma_chat delete mode 100644 recipes-core/multitech/config/ppp/peers/gsm delete mode 100644 recipes-core/multitech/config/ppp/peers/gsm_chat delete mode 100644 recipes-core/multitech/config/ppp/peers/l4e1 delete mode 100644 recipes-core/multitech/config/ppp/peers/l4e1_chat delete mode 100644 recipes-core/multitech/config/ppp/peers/l4n1 delete mode 120000 recipes-core/multitech/config/ppp/peers/l4n1_chat delete mode 100644 recipes-core/multitech/config/ppp/peers/l4n1_chat_non_vz delete mode 100644 recipes-core/multitech/config/ppp/peers/l4n1_chat_vz delete mode 100644 recipes-core/multitech/config/ppp/peers/lap3 delete mode 100644 recipes-core/multitech/config/ppp/peers/lap3_chat delete mode 100644 recipes-core/multitech/config/ppp/peers/leu1 delete mode 100644 recipes-core/multitech/config/ppp/peers/leu1_chat delete mode 100644 recipes-core/multitech/config/ppp/peers/lna3 delete mode 120000 recipes-core/multitech/config/ppp/peers/lna3_chat delete mode 100644 recipes-core/multitech/config/ppp/peers/lna3_chat_non_vz delete mode 100644 recipes-core/multitech/config/ppp/peers/lna3_chat_vz delete mode 100644 recipes-core/multitech/config/ppp/peers/lsp3 delete mode 100644 recipes-core/multitech/config/ppp/peers/lsp3_chat delete mode 100644 recipes-core/multitech/config/ppp/peers/lvw2 delete mode 100644 recipes-core/multitech/config/ppp/peers/lvw2_chat delete mode 100644 recipes-core/multitech/config_2.3.bb delete mode 100644 recipes-core/multitech/reset-handler/reset-handler.default delete mode 100644 recipes-core/multitech/reset-handler/reset-handler.init delete mode 100755 recipes-core/multitech/reset-handler/reset-handler.sh delete mode 100644 recipes-core/multitech/reset-handler_1.0.bb delete mode 100644 recipes-core/multitech/upgrade-reboot_1.0.0.bb (limited to 'recipes-core/multitech') diff --git a/recipes-core/multitech/cell-radio-carrierswitch/cell-radio-carrierswitch.default b/recipes-core/multitech/cell-radio-carrierswitch/cell-radio-carrierswitch.default deleted file mode 100644 index 7128721..0000000 --- a/recipes-core/multitech/cell-radio-carrierswitch/cell-radio-carrierswitch.default +++ /dev/null @@ -1,6 +0,0 @@ -# set to "no" to disable cell-radio-fwswitch on boot -ENABLED="yes" - -# The default timeout is 60 seconds. -# It depends on how long your radio takes to get ready. -# export TIMEOUT 60 diff --git a/recipes-core/multitech/cell-radio-carrierswitch/cell-radio-carrierswitch.init b/recipes-core/multitech/cell-radio-carrierswitch/cell-radio-carrierswitch.init deleted file mode 100644 index 6b8a640..0000000 --- a/recipes-core/multitech/cell-radio-carrierswitch/cell-radio-carrierswitch.init +++ /dev/null @@ -1,26 +0,0 @@ -#!/bin/sh - -# no firmware switch by default -ENABLED="no" - -[ -r /etc/default/cell-radio-carrierswitch ] && source /etc/default/cell-radio-carrierswitch -[ "$ENABLED" == "yes" ] || exit 0 - -# It may take a couple of boots to get the APN straightened out. -# mlinux-switch-apn is only effective for LNA3. It will only -# take action if it detects a different SIM from the one -# that is configured. It requires a RADIO that is active. -# The script is executed in the background to prevent holding up the -# boot. - -case $1 in - start) - (/usr/sbin/mlinux-switch-apn 2>&1 | logger -p daemon.notice) & - ;; - - *) - echo "Usage: $0 {start}" - exit 2 - ;; -esac - diff --git a/recipes-core/multitech/cell-radio-carrierswitch_1.0.bb b/recipes-core/multitech/cell-radio-carrierswitch_1.0.bb deleted file mode 100644 index 0220dba..0000000 --- a/recipes-core/multitech/cell-radio-carrierswitch_1.0.bb +++ /dev/null @@ -1,25 +0,0 @@ -DESCRIPTION = "Radio firmware switching functionality for dual image units (only LNA3 radios for now)" -SECTION = "base" -LICENSE = "MIT" -LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302" -PR = "r1" - -RDEPENDS_${PN} = "radio-query radio-cmd mlinux-scripts" - -inherit update-rc.d -INITSCRIPT_NAME = "cell-radio-carrierswitch" -INITSCRIPT_PARAMS = "start 63 5 ." - -SRC_URI = "\ - file://cell-radio-carrierswitch.default \ - file://cell-radio-carrierswitch.init \ -" - -do_install() { - install -d ${D}${sysconfdir}/init.d - install -m 0755 ${WORKDIR}/cell-radio-carrierswitch.init ${D}${sysconfdir}/init.d/cell-radio-carrierswitch - - install -d ${D}${sysconfdir}/default - install -m 0644 ${WORKDIR}/cell-radio-carrierswitch.default ${D}${sysconfdir}/default/cell-radio-carrierswitch -} - diff --git a/recipes-core/multitech/commissioning_1.0.1.bb b/recipes-core/multitech/commissioning_1.0.1.bb deleted file mode 100644 index 06e1904..0000000 --- a/recipes-core/multitech/commissioning_1.0.1.bb +++ /dev/null @@ -1,42 +0,0 @@ -inherit update-rc.d - -LICENSE = "MIT" -LIC_FILES_CHKSUM = "file://LICENSE;md5=593c81e8a2bd8b4c4e310d8792372b13" - -PACKAGE_ARCH = "${MACHINE_ARCH}" - -DEPENDS = "fcgi jsoncpp shadow" -RDEPENDS_${PN} += "jsoncpp lighttpd lighttpd-module-fastcgi lighttpd-module-openssl lighttpd-module-redirect bash" -RDEPENDS_${PN}-php-fpm += "php-fpm ${PN}" -PACKAGES =+ "${PN}-php-fpm" - -INITSCRIPT_PACKAGES = "${PN} ${PN}-php-fpm" -INITSCRIPT_NAME_${PN} = "commission " -INITSCRIPT_PARAMS_${PN} = "start 9 2 3 4 5 ." -INITSCRIPT_NAME_${PN}-php-fpm = "commission-php-fpm" -INITSCRIPT_PARAMS_${PN}-php-fpm = "start 9 2 3 4 5 ." - -PR = "r1" -SRCREV = "${PV}" - -FILES_${PN}-php-fpm = "/etc/init.d/commission-php-fpm" -FILES_${PN} += "/www/" - -SRC_URI = "git://git.multitech.net/commissioning;branch=master" - -S = "${WORKDIR}/git" -do_compile() { - oe_runmake all -} -do_install() { - - cp -a ${S}/${sysconfdir}/ ${D}/ - cp -a ${S}/www/ ${D}/ - cp -a ${S}/${prefix} ${D}/ - chmod 755 ${D}/etc/init.d/* - chmod 755 ${D}/${libexecdir}/commission/* - chown -R root:root ${D}/ - - oe_runmake install DESTDIR=${D} - chmod 755 ${D}/usr/bin/commissioning.fcgi -} diff --git a/recipes-core/multitech/config/99_radio b/recipes-core/multitech/config/99_radio deleted file mode 100644 index c2aa885..0000000 --- a/recipes-core/multitech/config/99_radio +++ /dev/null @@ -1,24 +0,0 @@ -# This configuration file lists filesystem objects that should get verified -# during startup and be created if missing. -# -# Every line must either be a comment starting with # -# or a definition of format: -# -# where the items are separated by whitespace ! -# -# : d|f|l : (d)irectory|(f)ile|(l)ink -# -# A linking example: -# l root root 0777 /var/test /tmp/testfile -# f root root 0644 /var/test none -# -# Understanding links: -# When populate-volatile is to verify/create a directory or file, it will first -# check it's existence. If a link is found to exist in the place of the target, -# the path of the target is replaced with the target the link points to. -# Thus, if a link is in the place to be verified, the object will be created -# in the place the link points to instead. -# This explains the order of "link before object" as in the example above, where -# a link will be created at /var/test pointing to /tmp/testfile and due to this -# link the file defined as /var/test will actually be created as /tmp/testfile. -d root dialout 2775 /run/radio none diff --git a/recipes-core/multitech/config/chat_wrapper b/recipes-core/multitech/config/chat_wrapper deleted file mode 100755 index f1fd30c..0000000 --- a/recipes-core/multitech/config/chat_wrapper +++ /dev/null @@ -1,205 +0,0 @@ -#!/bin/bash - -# Rules for chat scripts -# No comments allowed at the end of AT+CGDCONT in chat script -# The last AT+CGDCONT= must use the same context as the dialer. -# If desired, The AT+CGDCONT may be prefixed by #MT[[:space:]]+ -# Example: -#MT AT+CGDCONT="IPV6","data","192.168.2.1",0,1,"EXTRA" -# -# If you do not use a comment, the entire AT+CGDCONT command -# must be surrounded by apostrophes. This command will be executed -# twice, once in the chat wrapper, and a 2nd time in the chat -# itself. -# -# The space after "#MT" may be any number including tabs. -# If #MT AT+CGDCONT= is found, only the last one is chosen. -# Any uncommented AT+CGDCONT= is then ignored. -# If there are not #MT AT+CGDCONT= lines, then any line without -# a comment chararacter before AT+CGDONT= is accepted, but only the -# last one in the file. - -NAME=chat_wrapper -CONFIG=/etc/default/${NAME} -function finish -{ - ${LOG} "Launch:" "$@" - exec "$@" - # NOTREACHED -} - -[[ -f $CONFIG ]] || exit 1 - -. ${CONFIG} - -: ${REGWAITTIME:=300} -: ${FINALWAIT:=5} - -: ${LOG:="/usr/bin/logger -t ${NAME} -p daemon.notice"} - -${LOG} Timeout is $REGWAITTIME, execute "$@" -((i=$#)) -chatscript="${!i}" -${LOG} Parsing chat script "$chatscript" - -# CONTEXT is last context string in chat script -CONTEXT=$(egrep "^#MT[[:space:]]+(AT\+CGDCONT=.*)" ${chatscript} | tail -1) -if ((${#CONTEXT} == 0)) ; then - CONTEXT=$(egrep "^[^#]+AT\+CGDCONT=" ${chatscript} | tail -1) - [[ $CONTEXT =~ \'(AT\+CGDCONT=([0-9]+)[^$\']+) ]] -else - [[ $CONTEXT =~ (AT\+CGDCONT=([0-9]+).*)$ ]] -fi - -# CONTEXTNUM is the context number that is configured in the dialer. -CONTEXT="${BASH_REMATCH[1]}" -if ((${#CONTEXT} == 0)) ; then - ${LOG} No context specifiction in the chat script - finish "$@" - # NOTREACHED -fi -((CONTEXTNUM=${BASH_REMATCH[2]})) - - -${LOG} "Using Context ${CONTEXTNUM} based on chat script: ${CONTEXT}" - -# At this point if there is no context number, we can skip everything else. - -# Get Modem's context settings -MCONTEXT=$(/usr/bin/radio-cmd ${RADIOOPTION} -t10000 'AT+CGDCONT?' 2>&1 | tr -d '\r') -if [[ $MCONTEXT =~ [Ee][Rr][Rr][Oo][Rr] ]] ; then - RADIOOPTION="${RADIOOPTION2}" - MCONTEXT=$(/usr/bin/radio-cmd ${RADIOOPTION} -t10000 'AT+CGDCONT?' 2>&1 | tr -d '\r') -fi - -if ! [[ $MCONTEXT =~ \+CGDCONT:[[:space:]]+${CONTEXTNUM},\"([^\"]*)\",\"([^\"]*)\",\"([^\"]*)\",([0-9]+),([0-9]+)([^$'\n']*) ]] ; then - logger -s -p daemon.error "No valid context in modem. Is it ready?" - echo "$MCONTEXT" | logger -s -p daemon.error -fi - -MPDP="${BASH_REMATCH[1]}" -MAPN="${BASH_REMATCH[2]}" -MADDR="${BASH_REMATCH[3]}" -MDCOMP="${BASH_REMATCH[4]}" -MHCOMP="${BASH_REMATCH[5]}" -MFULLBOAT="${BASH_REMATCH[6]}" - -[[ $CONTEXT =~ AT\+CGDCONT=${CONTEXTNUM},\"([^\"]*)\",\"([^\"]*)\"(,\"([^\"]*)\"(,([0-9]+)(,([0-9]+)(,[^\']*))*)*)* ]] -PDP="${BASH_REMATCH[1]}" -APN="${BASH_REMATCH[2]}" -ADDR="${BASH_REMATCH[4]}" # Optional -DCOMP="${BASH_REMATCH[6]}" # Optional -HCOMP="${BASH_REMATCH[8]}" # Optional -FULLBOAT="${BASH_REMATCH[9]}" # Optional - -# On some modems there are more parameters than others. -if [[ $MFULLBOAT != $FULLBOAT ]] ; then - ${LOG} "Only the first five context parameters are considered. The rest will be ignored." - ${LOG} "modem: \"$MFULLBOAT\"" - ${LOG} "chat script: \"$FULLBOAT\"" -fi - -if ((${#DCOMP} == 0)) ; then - ((DCOMP=0)) # Default -fi -if ((${#HCOMP} == 0)) ; then - ((HCOMP=0)) # Default -fi - -# Only update context on a mismatch between chat and modem. -if [[ $MPDP != $PDP ]] || [[ $MAPN != $APN ]] || \ - [[ $MADDR != $ADDR ]] || ((MDCOMP != DCOMP)) || \ - ((MHCOMP != HCOMP)) ; then - ${LOG} "Modem context $MPDP,$MAPN,$MADDR,$MDCOMP,$MHCOMP does not match chat script" - ${LOG} "Chat script context $PDP,$APN,$ADDR,$DCOMP,$HCOMP does not match the modem" - if [[ $MPDP != $PDP ]] ; then - ${LOG} "PDP mismatch" - fi - if [[ $MAPN != $APN ]] ; then - ${LOG} "APN mismatch" - fi - if [[ $MADDR != $ADDR ]] ; then - ${LOG} "ADDR mismatch" - fi - if [[ $MDCOMP != $DCOMP ]] ; then - ${LOG} "DCOMP mismatch" - fi - if [[ $MHCOMP != $HCOMP ]] ; then - ${LOG} "HCOMP mismatch" - fi - if [[ $MFULLBOAT != $FULLBOAT ]] ; then - ${LOG} "Final parameter mismatches ignored" - ${LOG} "Parameter 6 and up on the modem:" - ${LOG} "\"${MFULLBOAT}\"" - ${LOG} "Parameter 6 and up on the chat script:" - ${LOG} "\"${FULLBOAT}\"" - fi - ${LOG} "$MCONTEXT" - ${LOG} "Dropping registration with carrier to set context" - # Need to deregister - /usr/bin/radio-cmd ${RADIOOPTION} -t10000 'AT+COPS=2' - # H5 radios do not like addresses that are empty with "" - if ((${#ADDR} == 0)) ; then - CMDSTR="AT+CGDCONT=${CONTEXTNUM},\"${PDP}\",\"${APN}\",,$DCOMP,${HCOMP}${FULLBOAT}" - else - CMDSTR="AT+CGDCONT=${CONTEXTNUM},\"${PDP}\",\"${APN}\",\"${ADDR}\",$DCOMP,${HCOMP}${FULLBOAT}" - fi - ${LOG} "Issued command /usr/bin/radio-cmd ${RADIOOPTION} -t10000 ..." - ${LOG} "... ${CMDSTR}" - - # If we fail to set the APN, sleep and try it again for up to 10 seconds. - result=1 - count=10 - while ((result != 0)) && ((count > 0)) ; do - ((count--)) || true - LOGMSG=$(/usr/bin/radio-cmd ${RADIOOPTION} -t10000 "${CMDSTR}" 2>&1) - result=$? - ${LOG} "Result ${result}, Got response ${LOGMSG}" - if [[ $LOGMSG =~ ERROR ]] ; then - result=1 - fi - sleep 1 - done - - # re-enable the modem to defaults. - /usr/bin/radio-cmd ${RADIOOPTION} -t10000 'AT+COPS=0' - sleep 1 - - # Some older modems will not re-register after the COPS - # command if you do not reset them using CFUN. - /usr/bin/radio-cmd ${RADIOOPTION} -t10000 'AT+CFUN=0' - /usr/bin/radio-cmd ${RADIOOPTION} -t10000 'AT+CFUN=1' - - # Abort PPP if the Context is not correct. We don't want - # to cause the carrier to disable the account by dialing - # out with a bad APN. - if ((result != 0)) ; then - ${LOG} "AT+CGDCONT failed, aborting" - exit $result - fi - sleep 1 - ${LOG} "New context is set. Wait up to $REGWAITTIME seconds to register" - # Wait for registration - uptime=$(cat /proc/uptime) - [[ $uptime =~ ^([^\.]*) ]] - t0=${BASH_REMATCH[1]} - while ! [[ $(/usr/bin/radio-query ${RADIOOPTION} --netreg) =~ ^REGISTERED$ ]] ; do - sleep 5 - uptime=$(cat /proc/uptime) - [[ $uptime =~ ^([^\.]*) ]] - t1=${BASH_REMATCH[1]} - if ((t1-t0 > REGWAITTIME)) ; then - ${LOG} "$((t1-t0)) seconds has expired" - exit 1 - fi - done - uptime=$(cat /proc/uptime) - [[ $uptime =~ ^([^\.]*) ]] - t1=${BASH_REMATCH[1]} - ${LOG} "Re-registered in $((t1-t0)) seconds -- wait ${FINALWAIT} more seconds" - sleep $FINALWAIT -else - ${LOG} "Context $CONTEXTNUM matches and nothing to do." -fi -finish "$@" -# NOTREACHED diff --git a/recipes-core/multitech/config/chat_wrapper.default b/recipes-core/multitech/config/chat_wrapper.default deleted file mode 100644 index a1b4e41..0000000 --- a/recipes-core/multitech/config/chat_wrapper.default +++ /dev/null @@ -1,20 +0,0 @@ -# The maximum time to wait for registration -# when changing the modem context parameters. -# This is ignored if the context is -# already set correctly in the modem. -REGWAITTIME=300 - -# The time to wait after registration -# when setting the context -# before attempting a PPP connection. -# This is ignored if the context is -# already set correctly in the modem. -FINALWAIT=5 - -# Option for radio-query, radio-cmd -# Used by /usr/libexec/ppp/chat_wrapper, -# mlinux-switch-apn, mlinux-switch-cell-fw -RADIOOPTION="-d /dev/modem_at1" - -# Device to use if RADIOOPTION fails: -RADIOOPTION2="-d /dev/modem_at0" diff --git a/recipes-core/multitech/config/config-mths/default/bluetooth b/recipes-core/multitech/config/config-mths/default/bluetooth deleted file mode 100644 index ec46cfd..0000000 --- a/recipes-core/multitech/config/config-mths/default/bluetooth +++ /dev/null @@ -1,8 +0,0 @@ -# Set to 1 to enable bluetooth daemon -BLUETOOTH_ENABLED=1 - -# Use the following to setup bluetooth usability -BLUETOOTHCTL_CMD="power on\ndiscoverable on\npairable on\n" - -#Compatilitity mode -#MOREOPTIONS="-C" diff --git a/recipes-core/multitech/config/config-mths/default/dnsmasq b/recipes-core/multitech/config/config-mths/default/dnsmasq deleted file mode 100644 index 129fda1..0000000 --- a/recipes-core/multitech/config/config-mths/default/dnsmasq +++ /dev/null @@ -1,27 +0,0 @@ -# MTHS dnsmasq -# and a hook to set up config files for MTHS -ENABLED="yes" - -# This configuration is for manufacturing test. -# Factory resets should not put back wifi defaults. -if [[ -f /var/config/.defaults2.tar.gz ]] ; then - rm /var/config/.defaults2.tar.gz -fi - -# Stop ntpd. ntpd default is in root. -sed -i 's/ENABLED="yes"/ENABLED="no"/' /etc/default/ntpd -# Use the ifplugd in /var/config -if ! [[ -L /etc/ifplugd ]] ; then - rm -rf /etc/ifplugd - ln -s /var/config/ifplugd /etc/ifplugd - # ifplugd is already started (and probably bombed) - # restart it. - /etc/init.d/ifplugd stop - /etc/init.d/ifplugd start -fi - -if ! [[ -L /etc/default/usb-gadget ]] && [[ -f /var/config/default/usb-gadget ]] ; then - rm -rf /etc/default/usb-gadget - ln -s /var/config/default/usb-gadget /etc/default/usb-gadget -fi - diff --git a/recipes-core/multitech/config/config-mths/default/hostapd b/recipes-core/multitech/config/config-mths/default/hostapd deleted file mode 100644 index 75c1c8a..0000000 --- a/recipes-core/multitech/config/config-mths/default/hostapd +++ /dev/null @@ -1,11 +0,0 @@ -# set to "yes" to start hostapd on boot -START_ON_BOOT="yes" -DEVICEID=$(cat /sys/devices/platform/mts-io/device-id) -SSID="hs-${DEVICEID}" -CONF=/etc/hostapd.conf - -PREUP="ifdown wifi1 - ifup wifi1 - sed -ri 's/^ssid=.*/ssid=hs-'${DEVICEID}/ ${CONF} - logger -s -t hostapd -p daemon.alert 'hostapd SSID line is '${SSID}" - diff --git a/recipes-core/multitech/config/config-mths/default/ntpd b/recipes-core/multitech/config/config-mths/default/ntpd deleted file mode 100644 index a0d3bcf..0000000 --- a/recipes-core/multitech/config/config-mths/default/ntpd +++ /dev/null @@ -1,36 +0,0 @@ -ENABLED="no" - - -CONFIGFILE=/etc/ntp.conf - -# The GPSD_* parameters in this file are ignored -# if the uBlox GPS is not present. - -# Require a GPS lock/fix before starting NTP -# This is needed if we are not using NTP servers. -# NTP will not work with the GPS if the GPS is not -# locked before starting. -# See /etc/default/gpsd for the states required. -GPSD_REQUIRED=0 - -# Number of seconds between testing for a GPS -# lock prior to calling ntpd. -GPSD_WAIT_TIME=120 - -# Since the HW Clock could be off by a second or -# so, our GPS might get marked as a false ticker -# if we do not set the system clock to the GPS -# first. The current correct way to do this -# according to the ntp doc is ntpd -gq -c conffile -# which must be done before ntpd is started. -# conffile should exclude the local clock, so it is -# ignored while doing the initial sync. -# ntpd -gq apparently does not work with the GPS -# when tested with the clock more than one day off -# and no ntpd. The gps shared memory is never polled. -# -# If there is a uBlox GPS present, the time is -# read from the GPS to initialize the system time -# before NTP is started. -SET_SYSTEM_CLOCK=1 - diff --git a/recipes-core/multitech/config/config-mths/default/rs9113 b/recipes-core/multitech/config/config-mths/default/rs9113 deleted file mode 100644 index 2594625..0000000 --- a/recipes-core/multitech/config/config-mths/default/rs9113 +++ /dev/null @@ -1,14 +0,0 @@ -RS9113_LOAD=1 -RSI_ANTENNA_DIVERSITY=0 -COEX_MODE=6 -WLAN_RF_PWR_MODE=0x00 -BT_RF_PWR_MODE=0x00 -BT_RF_TX_POWER_MODE=0 -BT_RF_RX_POWER_MODE=0 -SET_COUNTRY_CODE=0 -ANT_SEL_VAL=2 -ONBOARD_ANT_SEL=1 -SET_RETRY_COUNT=15 -SLEEPTIME=100000 -INTSLEEPTIME=100000 - diff --git a/recipes-core/multitech/config/config-mths/default/usb-gadget b/recipes-core/multitech/config/config-mths/default/usb-gadget deleted file mode 100644 index 944ef8a..0000000 --- a/recipes-core/multitech/config/config-mths/default/usb-gadget +++ /dev/null @@ -1,6 +0,0 @@ -# set to "no" to disable usb-gadget -ENABLED="yes" - -USB_MODE="networking" -MODULE_OPTIONS="" - diff --git a/recipes-core/multitech/config/config-mths/dnsmasq.d/dhcp.conf b/recipes-core/multitech/config/config-mths/dnsmasq.d/dhcp.conf deleted file mode 100644 index 47eb1c0..0000000 --- a/recipes-core/multitech/config/config-mths/dnsmasq.d/dhcp.conf +++ /dev/null @@ -1,12 +0,0 @@ -interface=wifi1 -dhcp-range=10.0.0.100,10.0.0.250,12h -dhcp-lease-max=200 -dhcp-leasefile=/var/config/dnsmasq_dhcp_wifi1.leases -dhcp-option=option:netmask,255.255.255.0 -dhcp-option=option:router,10.0.0.1 -dhcp-option=option:dns-server,10.0.0.1 -dhcp-authoritative -interface=usb0 -dhcp-range=192.168.3.100,192.168.3.250,12h -dhcp-option=option:router,192.168.3.1 -dhcp-option=option:dns-server,192.168.3.1 diff --git a/recipes-core/multitech/config/config-mths/hostapd.conf b/recipes-core/multitech/config/config-mths/hostapd.conf deleted file mode 100644 index 8acd72b..0000000 --- a/recipes-core/multitech/config/config-mths/hostapd.conf +++ /dev/null @@ -1,1996 +0,0 @@ -##### hostapd configuration file ############################################## -# Empty lines and lines starting with # are ignored - -# AP netdevice name (without 'ap' postfix, i.e., wlan0 uses wlan0ap for -# management frames with the Host AP driver); wlan0 with many nl80211 drivers -# Note: This attribute can be overridden by the values supplied with the '-i' -# command line parameter. -interface=wifi1 - -# In case of atheros and nl80211 driver interfaces, an additional -# configuration parameter, bridge, may be used to notify hostapd if the -# interface is included in a bridge. This parameter is not used with Host AP -# driver. If the bridge parameter is not set, the drivers will automatically -# figure out the bridge interface (assuming sysfs is enabled and mounted to -# /sys) and this parameter may not be needed. -# -# For nl80211, this parameter can be used to request the AP interface to be -# added to the bridge automatically (brctl may refuse to do this before hostapd -# has been started to change the interface mode). If needed, the bridge -# interface is also created. -#bridge=br0 - -# Driver interface type (hostap/wired/none/nl80211/bsd); -# default: hostap). nl80211 is used with all Linux mac80211 drivers. -# Use driver=none if building hostapd as a standalone RADIUS server that does -# not control any wireless/wired driver. -# driver=hostap - -# Driver interface parameters (mainly for development testing use) -# driver_params= - -# hostapd event logger configuration -# -# Two output method: syslog and stdout (only usable if not forking to -# background). -# -# Module bitfield (ORed bitfield of modules that will be logged; -1 = all -# modules): -# bit 0 (1) = IEEE 802.11 -# bit 1 (2) = IEEE 802.1X -# bit 2 (4) = RADIUS -# bit 3 (8) = WPA -# bit 4 (16) = driver interface -# bit 5 (32) = IAPP -# bit 6 (64) = MLME -# -# Levels (minimum value for logged events): -# 0 = verbose debugging -# 1 = debugging -# 2 = informational messages -# 3 = notification -# 4 = warning -# -logger_syslog=-1 -logger_syslog_level=2 -logger_stdout=-1 -logger_stdout_level=2 - -# Interface for separate control program. If this is specified, hostapd -# will create this directory and a UNIX domain socket for listening to requests -# from external programs (CLI/GUI, etc.) for status information and -# configuration. The socket file will be named based on the interface name, so -# multiple hostapd processes/interfaces can be run at the same time if more -# than one interface is used. -# /var/run/hostapd is the recommended directory for sockets and by default, -# hostapd_cli will use it when trying to connect with hostapd. -ctrl_interface=/var/run/hostapd - -# Access control for the control interface can be configured by setting the -# directory to allow only members of a group to use sockets. This way, it is -# possible to run hostapd as root (since it needs to change network -# configuration and open raw sockets) and still allow GUI/CLI components to be -# run as non-root users. However, since the control interface can be used to -# change the network configuration, this access needs to be protected in many -# cases. By default, hostapd is configured to use gid 0 (root). If you -# want to allow non-root users to use the contron interface, add a new group -# and change this value to match with that group. Add users that should have -# control interface access to this group. -# -# This variable can be a group name or gid. -#ctrl_interface_group=wheel -ctrl_interface_group=0 - - -##### IEEE 802.11 related configuration ####################################### - -# SSID to be used in IEEE 802.11 management frames -ssid=hs- -# Alternative formats for configuring SSID -# (double quoted string, hexdump, printf-escaped string) -#ssid2="test" -#ssid2=74657374 -#ssid2=P"hello\nthere" - -# UTF-8 SSID: Whether the SSID is to be interpreted using UTF-8 encoding -#utf8_ssid=1 - -# Country code (ISO/IEC 3166-1). Used to set regulatory domain. -# Set as needed to indicate country in which device is operating. -# This can limit available channels and transmit power. -country_code=US - -# Enable IEEE 802.11d. This advertises the country_code and the set of allowed -# channels and transmit power levels based on the regulatory limits. The -# country_code setting must be configured with the correct country for -# IEEE 802.11d functions. -# (default: 0 = disabled) -#ieee80211d=1 - -# Enable IEEE 802.11h. This enables radar detection and DFS support if -# available. DFS support is required on outdoor 5 GHz channels in most countries -# of the world. This can be used only with ieee80211d=1. -# (default: 0 = disabled) -#ieee80211h=1 - -# Add Power Constraint element to Beacon and Probe Response frames -# This config option adds Power Constraint element when applicable and Country -# element is added. Power Constraint element is required by Transmit Power -# Control. This can be used only with ieee80211d=1. -# Valid values are 0..255. -#local_pwr_constraint=3 - -# Set Spectrum Management subfield in the Capability Information field. -# This config option forces the Spectrum Management bit to be set. When this -# option is not set, the value of the Spectrum Management bit depends on whether -# DFS or TPC is required by regulatory authorities. This can be used only with -# ieee80211d=1 and local_pwr_constraint configured. -#spectrum_mgmt_required=1 - -# Operation mode (a = IEEE 802.11a (5 GHz), b = IEEE 802.11b (2.4 GHz), -# g = IEEE 802.11g (2.4 GHz), ad = IEEE 802.11ad (60 GHz); a/g options are used -# with IEEE 802.11n (HT), too, to specify band). For IEEE 802.11ac (VHT), this -# needs to be set to hw_mode=a. When using ACS (see channel parameter), a -# special value "any" can be used to indicate that any support band can be used. -# This special case is currently supported only with drivers with which -# offloaded ACS is used. -# Default: IEEE 802.11b -hw_mode=g - -# Channel number (IEEE 802.11) -# (default: 0, i.e., not set) -# Please note that some drivers do not use this value from hostapd and the -# channel will need to be configured separately with iwconfig. -# -# If CONFIG_ACS build option is enabled, the channel can be selected -# automatically at run time by setting channel=acs_survey or channel=0, both of -# which will enable the ACS survey based algorithm. -channel=10 - -# ACS tuning - Automatic Channel Selection -# See: http://wireless.kernel.org/en/users/Documentation/acs -# -# You can customize the ACS survey algorithm with following variables: -# -# acs_num_scans requirement is 1..100 - number of scans to be performed that -# are used to trigger survey data gathering of an underlying device driver. -# Scans are passive and typically take a little over 100ms (depending on the -# driver) on each available channel for given hw_mode. Increasing this value -# means sacrificing startup time and gathering more data wrt channel -# interference that may help choosing a better channel. This can also help fine -# tune the ACS scan time in case a driver has different scan dwell times. -# -# acs_chan_bias is a space-separated list of : pairs. It can be -# used to increase (or decrease) the likelihood of a specific channel to be -# selected by the ACS algorithm. The total interference factor for each channel -# gets multiplied by the specified bias value before finding the channel with -# the lowest value. In other words, values between 0.0 and 1.0 can be used to -# make a channel more likely to be picked while values larger than 1.0 make the -# specified channel less likely to be picked. This can be used, e.g., to prefer -# the commonly used 2.4 GHz band channels 1, 6, and 11 (which is the default -# behavior on 2.4 GHz band if no acs_chan_bias parameter is specified). -# -# Defaults: -#acs_num_scans=5 -#acs_chan_bias=1:0.8 6:0.8 11:0.8 - -# Channel list restriction. This option allows hostapd to select one of the -# provided channels when a channel should be automatically selected. -# Channel list can be provided as range using hyphen ('-') or individual -# channels can be specified by space (' ') separated values -# Default: all channels allowed in selected hw_mode -#chanlist=100 104 108 112 116 -#chanlist=1 6 11-13 - -# Beacon interval in kus (1.024 ms) (default: 100; range 15..65535) -beacon_int=100 - -# DTIM (delivery traffic information message) period (range 1..255): -# number of beacons between DTIMs (1 = every beacon includes DTIM element) -# (default: 2) -dtim_period=2 - -# Maximum number of stations allowed in station table. New stations will be -# rejected after the station table is full. IEEE 802.11 has a limit of 2007 -# different association IDs, so this number should not be larger than that. -# (default: 2007) -max_num_sta=255 - -# RTS/CTS threshold; -1 = disabled (default); range -1..65535 -# If this field is not included in hostapd.conf, hostapd will not control -# RTS threshold and 'iwconfig wlan# rts ' can be used to set it. -rts_threshold=-1 - -# Fragmentation threshold; -1 = disabled (default); range -1, 256..2346 -# If this field is not included in hostapd.conf, hostapd will not control -# fragmentation threshold and 'iwconfig wlan# frag ' can be used to set -# it. -fragm_threshold=-1 - -# Rate configuration -# Default is to enable all rates supported by the hardware. This configuration -# item allows this list be filtered so that only the listed rates will be left -# in the list. If the list is empty, all rates are used. This list can have -# entries that are not in the list of rates the hardware supports (such entries -# are ignored). The entries in this list are in 100 kbps, i.e., 11 Mbps = 110. -# If this item is present, at least one rate have to be matching with the rates -# hardware supports. -# default: use the most common supported rate setting for the selected -# hw_mode (i.e., this line can be removed from configuration file in most -# cases) -#supported_rates=10 20 55 110 60 90 120 180 240 360 480 540 - -# Basic rate set configuration -# List of rates (in 100 kbps) that are included in the basic rate set. -# If this item is not included, usually reasonable default set is used. -#basic_rates=10 20 -#basic_rates=10 20 55 110 -#basic_rates=60 120 240 - -# Short Preamble -# This parameter can be used to enable optional use of short preamble for -# frames sent at 2 Mbps, 5.5 Mbps, and 11 Mbps to improve network performance. -# This applies only to IEEE 802.11b-compatible networks and this should only be -# enabled if the local hardware supports use of short preamble. If any of the -# associated STAs do not support short preamble, use of short preamble will be -# disabled (and enabled when such STAs disassociate) dynamically. -# 0 = do not allow use of short preamble (default) -# 1 = allow use of short preamble -#preamble=1 - -# Station MAC address -based authentication -# Please note that this kind of access control requires a driver that uses -# hostapd to take care of management frame processing and as such, this can be -# used with driver=hostap or driver=nl80211, but not with driver=atheros. -# 0 = accept unless in deny list -# 1 = deny unless in accept list -# 2 = use external RADIUS server (accept/deny lists are searched first) -macaddr_acl=0 - -# Accept/deny lists are read from separate files (containing list of -# MAC addresses, one per line). Use absolute path name to make sure that the -# files can be read on SIGHUP configuration reloads. -#accept_mac_file=/etc/hostapd.accept -#deny_mac_file=/etc/hostapd.deny - -# IEEE 802.11 specifies two authentication algorithms. hostapd can be -# configured to allow both of these or only one. Open system authentication -# should be used with IEEE 802.1X. -# Bit fields of allowed authentication algorithms: -# bit 0 = Open System Authentication -# bit 1 = Shared Key Authentication (requires WEP) -auth_algs=3 - -# Send empty SSID in beacons and ignore probe request frames that do not -# specify full SSID, i.e., require stations to know SSID. -# default: disabled (0) -# 1 = send empty (length=0) SSID in beacon and ignore probe request for -# broadcast SSID -# 2 = clear SSID (ASCII 0), but keep the original length (this may be required -# with some clients that do not support empty SSID) and ignore probe -# requests for broadcast SSID -ignore_broadcast_ssid=0 - -# Do not reply to broadcast Probe Request frames from unassociated STA if there -# is no room for additional stations (max_num_sta). This can be used to -# discourage a STA from trying to associate with this AP if the association -# would be rejected due to maximum STA limit. -# Default: 0 (disabled) -#no_probe_resp_if_max_sta=0 - -# Additional vendor specific elements for Beacon and Probe Response frames -# This parameter can be used to add additional vendor specific element(s) into -# the end of the Beacon and Probe Response frames. The format for these -# element(s) is a hexdump of the raw information elements (id+len+payload for -# one or more elements) -#vendor_elements=dd0411223301 - -# Additional vendor specific elements for (Re)Association Response frames -# This parameter can be used to add additional vendor specific element(s) into -# the end of the (Re)Association Response frames. The format for these -# element(s) is a hexdump of the raw information elements (id+len+payload for -# one or more elements) -#assocresp_elements=dd0411223301 - -# TX queue parameters (EDCF / bursting) -# tx_queue__ -# queues: data0, data1, data2, data3, after_beacon, beacon -# (data0 is the highest priority queue) -# parameters: -# aifs: AIFS (default 2) -# cwmin: cwMin (1, 3, 7, 15, 31, 63, 127, 255, 511, 1023, 2047, 4095, 8191, -# 16383, 32767) -# cwmax: cwMax (same values as cwMin, cwMax >= cwMin) -# burst: maximum length (in milliseconds with precision of up to 0.1 ms) for -# bursting -# -# Default WMM parameters (IEEE 802.11 draft; 11-03-0504-03-000e): -# These parameters are used by the access point when transmitting frames -# to the clients. -# -# Low priority / AC_BK = background -#tx_queue_data3_aifs=7 -#tx_queue_data3_cwmin=15 -#tx_queue_data3_cwmax=1023 -#tx_queue_data3_burst=0 -# Note: for IEEE 802.11b mode: cWmin=31 cWmax=1023 burst=0 -# -# Normal priority / AC_BE = best effort -#tx_queue_data2_aifs=3 -#tx_queue_data2_cwmin=15 -#tx_queue_data2_cwmax=63 -#tx_queue_data2_burst=0 -# Note: for IEEE 802.11b mode: cWmin=31 cWmax=127 burst=0 -# -# High priority / AC_VI = video -#tx_queue_data1_aifs=1 -#tx_queue_data1_cwmin=7 -#tx_queue_data1_cwmax=15 -#tx_queue_data1_burst=3.0 -# Note: for IEEE 802.11b mode: cWmin=15 cWmax=31 burst=6.0 -# -# Highest priority / AC_VO = voice -#tx_queue_data0_aifs=1 -#tx_queue_data0_cwmin=3 -#tx_queue_data0_cwmax=7 -#tx_queue_data0_burst=1.5 -# Note: for IEEE 802.11b mode: cWmin=7 cWmax=15 burst=3.3 - -# 802.1D Tag (= UP) to AC mappings -# WMM specifies following mapping of data frames to different ACs. This mapping -# can be configured using Linux QoS/tc and sch_pktpri.o module. -# 802.1D Tag 802.1D Designation Access Category WMM Designation -# 1 BK AC_BK Background -# 2 - AC_BK Background -# 0 BE AC_BE Best Effort -# 3 EE AC_BE Best Effort -# 4 CL AC_VI Video -# 5 VI AC_VI Video -# 6 VO AC_VO Voice -# 7 NC AC_VO Voice -# Data frames with no priority information: AC_BE -# Management frames: AC_VO -# PS-Poll frames: AC_BE - -# Default WMM parameters (IEEE 802.11 draft; 11-03-0504-03-000e): -# for 802.11a or 802.11g networks -# These parameters are sent to WMM clients when they associate. -# The parameters will be used by WMM clients for frames transmitted to the -# access point. -# -# note - txop_limit is in units of 32microseconds -# note - acm is admission control mandatory flag. 0 = admission control not -# required, 1 = mandatory -# note - Here cwMin and cmMax are in exponent form. The actual cw value used -# will be (2^n)-1 where n is the value given here. The allowed range for these -# wmm_ac_??_{cwmin,cwmax} is 0..15 with cwmax >= cwmin. -# -wmm_enabled=1 -# -# WMM-PS Unscheduled Automatic Power Save Delivery [U-APSD] -# Enable this flag if U-APSD supported outside hostapd (eg., Firmware/driver) -#uapsd_advertisement_enabled=1 -# -# Low priority / AC_BK = background -wmm_ac_bk_cwmin=4 -wmm_ac_bk_cwmax=10 -wmm_ac_bk_aifs=7 -wmm_ac_bk_txop_limit=0 -wmm_ac_bk_acm=0 -# Note: for IEEE 802.11b mode: cWmin=5 cWmax=10 -# -# Normal priority / AC_BE = best effort -wmm_ac_be_aifs=3 -wmm_ac_be_cwmin=4 -wmm_ac_be_cwmax=10 -wmm_ac_be_txop_limit=0 -wmm_ac_be_acm=0 -# Note: for IEEE 802.11b mode: cWmin=5 cWmax=7 -# -# High priority / AC_VI = video -wmm_ac_vi_aifs=2 -wmm_ac_vi_cwmin=3 -wmm_ac_vi_cwmax=4 -wmm_ac_vi_txop_limit=94 -wmm_ac_vi_acm=0 -# Note: for IEEE 802.11b mode: cWmin=4 cWmax=5 txop_limit=188 -# -# Highest priority / AC_VO = voice -wmm_ac_vo_aifs=2 -wmm_ac_vo_cwmin=2 -wmm_ac_vo_cwmax=3 -wmm_ac_vo_txop_limit=47 -wmm_ac_vo_acm=0 -# Note: for IEEE 802.11b mode: cWmin=3 cWmax=4 burst=102 - -# Static WEP key configuration -# -# The key number to use when transmitting. -# It must be between 0 and 3, and the corresponding key must be set. -# default: not set -#wep_default_key=0 -# The WEP keys to use. -# A key may be a quoted string or unquoted hexadecimal digits. -# The key length should be 5, 13, or 16 characters, or 10, 26, or 32 -# digits, depending on whether 40-bit (64-bit), 104-bit (128-bit), or -# 128-bit (152-bit) WEP is used. -# Only the default key must be supplied; the others are optional. -# default: not set -#wep_key0=123456789a -#wep_key1="vwxyz" -#wep_key2=0102030405060708090a0b0c0d -#wep_key3=".2.4.6.8.0.23" - -# Station inactivity limit -# -# If a station does not send anything in ap_max_inactivity seconds, an -# empty data frame is sent to it in order to verify whether it is -# still in range. If this frame is not ACKed, the station will be -# disassociated and then deauthenticated. This feature is used to -# clear station table of old entries when the STAs move out of the -# range. -# -# The station can associate again with the AP if it is still in range; -# this inactivity poll is just used as a nicer way of verifying -# inactivity; i.e., client will not report broken connection because -# disassociation frame is not sent immediately without first polling -# the STA with a data frame. -# default: 300 (i.e., 5 minutes) -#ap_max_inactivity=300 -# -# The inactivity polling can be disabled to disconnect stations based on -# inactivity timeout so that idle stations are more likely to be disconnected -# even if they are still in range of the AP. This can be done by setting -# skip_inactivity_poll to 1 (default 0). -#skip_inactivity_poll=0 - -# Disassociate stations based on excessive transmission failures or other -# indications of connection loss. This depends on the driver capabilities and -# may not be available with all drivers. -#disassoc_low_ack=1 - -# Maximum allowed Listen Interval (how many Beacon periods STAs are allowed to -# remain asleep). Default: 65535 (no limit apart from field size) -#max_listen_interval=100 - -# WDS (4-address frame) mode with per-station virtual interfaces -# (only supported with driver=nl80211) -# This mode allows associated stations to use 4-address frames to allow layer 2 -# bridging to be used. -#wds_sta=1 - -# If bridge parameter is set, the WDS STA interface will be added to the same -# bridge by default. This can be overridden with the wds_bridge parameter to -# use a separate bridge. -#wds_bridge=wds-br0 - -# Start the AP with beaconing disabled by default. -#start_disabled=0 - -# Client isolation can be used to prevent low-level bridging of frames between -# associated stations in the BSS. By default, this bridging is allowed. -#ap_isolate=1 - -# BSS Load update period (in BUs) -# This field is used to enable and configure adding a BSS Load element into -# Beacon and Probe Response frames. -#bss_load_update_period=50 - -# Fixed BSS Load value for testing purposes -# This field can be used to configure hostapd to add a fixed BSS Load element -# into Beacon and Probe Response frames for testing purposes. The format is -# :: -#bss_load_test=12:80:20000 - -##### IEEE 802.11n related configuration ###################################### - -# ieee80211n: Whether IEEE 802.11n (HT) is enabled -# 0 = disabled (default) -# 1 = enabled -# Note: You will also need to enable WMM for full HT functionality. -# Note: hw_mode=g (2.4 GHz) and hw_mode=a (5 GHz) is used to specify the band. -#ieee80211n=1 - -# ht_capab: HT capabilities (list of flags) -# LDPC coding capability: [LDPC] = supported -# Supported channel width set: [HT40-] = both 20 MHz and 40 MHz with secondary -# channel below the primary channel; [HT40+] = both 20 MHz and 40 MHz -# with secondary channel above the primary channel -# (20 MHz only if neither is set) -# Note: There are limits on which channels can be used with HT40- and -# HT40+. Following table shows the channels that may be available for -# HT40- and HT40+ use per IEEE 802.11n Annex J: -# freq HT40- HT40+ -# 2.4 GHz 5-13 1-7 (1-9 in Europe/Japan) -# 5 GHz 40,48,56,64 36,44,52,60 -# (depending on the location, not all of these channels may be available -# for use) -# Please note that 40 MHz channels may switch their primary and secondary -# channels if needed or creation of 40 MHz channel maybe rejected based -# on overlapping BSSes. These changes are done automatically when hostapd -# is setting up the 40 MHz channel. -# Spatial Multiplexing (SM) Power Save: [SMPS-STATIC] or [SMPS-DYNAMIC] -# (SMPS disabled if neither is set) -# HT-greenfield: [GF] (disabled if not set) -# Short GI for 20 MHz: [SHORT-GI-20] (disabled if not set) -# Short GI for 40 MHz: [SHORT-GI-40] (disabled if not set) -# Tx STBC: [TX-STBC] (disabled if not set) -# Rx STBC: [RX-STBC1] (one spatial stream), [RX-STBC12] (one or two spatial -# streams), or [RX-STBC123] (one, two, or three spatial streams); Rx STBC -# disabled if none of these set -# HT-delayed Block Ack: [DELAYED-BA] (disabled if not set) -# Maximum A-MSDU length: [MAX-AMSDU-7935] for 7935 octets (3839 octets if not -# set) -# DSSS/CCK Mode in 40 MHz: [DSSS_CCK-40] = allowed (not allowed if not set) -# 40 MHz intolerant [40-INTOLERANT] (not advertised if not set) -# L-SIG TXOP protection support: [LSIG-TXOP-PROT] (disabled if not set) -#ht_capab=[HT40-][SHORT-GI-20][SHORT-GI-40] - -# Require stations to support HT PHY (reject association if they do not) -#require_ht=1 - -# If set non-zero, require stations to perform scans of overlapping -# channels to test for stations which would be affected by 40 MHz traffic. -# This parameter sets the interval in seconds between these scans. Setting this -# to non-zero allows 2.4 GHz band AP to move dynamically to a 40 MHz channel if -# no co-existence issues with neighboring devices are found. -#obss_interval=0 - -##### IEEE 802.11ac related configuration ##################################### - -# ieee80211ac: Whether IEEE 802.11ac (VHT) is enabled -# 0 = disabled (default) -# 1 = enabled -# Note: You will also need to enable WMM for full VHT functionality. -# Note: hw_mode=a is used to specify that 5 GHz band is used with VHT. -#ieee80211ac=1 - -# vht_capab: VHT capabilities (list of flags) -# -# vht_max_mpdu_len: [MAX-MPDU-7991] [MAX-MPDU-11454] -# Indicates maximum MPDU length -# 0 = 3895 octets (default) -# 1 = 7991 octets -# 2 = 11454 octets -# 3 = reserved -# -# supported_chan_width: [VHT160] [VHT160-80PLUS80] -# Indicates supported Channel widths -# 0 = 160 MHz & 80+80 channel widths are not supported (default) -# 1 = 160 MHz channel width is supported -# 2 = 160 MHz & 80+80 channel widths are supported -# 3 = reserved -# -# Rx LDPC coding capability: [RXLDPC] -# Indicates support for receiving LDPC coded pkts -# 0 = Not supported (default) -# 1 = Supported -# -# Short GI for 80 MHz: [SHORT-GI-80] -# Indicates short GI support for reception of packets transmitted with TXVECTOR -# params format equal to VHT and CBW = 80Mhz -# 0 = Not supported (default) -# 1 = Supported -# -# Short GI for 160 MHz: [SHORT-GI-160] -# Indicates short GI support for reception of packets transmitted with TXVECTOR -# params format equal to VHT and CBW = 160Mhz -# 0 = Not supported (default) -# 1 = Supported -# -# Tx STBC: [TX-STBC-2BY1] -# Indicates support for the transmission of at least 2x1 STBC -# 0 = Not supported (default) -# 1 = Supported -# -# Rx STBC: [RX-STBC-1] [RX-STBC-12] [RX-STBC-123] [RX-STBC-1234] -# Indicates support for the reception of PPDUs using STBC -# 0 = Not supported (default) -# 1 = support of one spatial stream -# 2 = support of one and two spatial streams -# 3 = support of one, two and three spatial streams -# 4 = support of one, two, three and four spatial streams -# 5,6,7 = reserved -# -# SU Beamformer Capable: [SU-BEAMFORMER] -# Indicates support for operation as a single user beamformer -# 0 = Not supported (default) -# 1 = Supported -# -# SU Beamformee Capable: [SU-BEAMFORMEE] -# Indicates support for operation as a single user beamformee -# 0 = Not supported (default) -# 1 = Supported -# -# Compressed Steering Number of Beamformer Antennas Supported: -# [BF-ANTENNA-2] [BF-ANTENNA-3] [BF-ANTENNA-4] -# Beamformee's capability indicating the maximum number of beamformer -# antennas the beamformee can support when sending compressed beamforming -# feedback -# If SU beamformer capable, set to maximum value minus 1 -# else reserved (default) -# -# Number of Sounding Dimensions: -# [SOUNDING-DIMENSION-2] [SOUNDING-DIMENSION-3] [SOUNDING-DIMENSION-4] -# Beamformer's capability indicating the maximum value of the NUM_STS parameter -# in the TXVECTOR of a VHT NDP -# If SU beamformer capable, set to maximum value minus 1 -# else reserved (default) -# -# MU Beamformer Capable: [MU-BEAMFORMER] -# Indicates support for operation as an MU beamformer -# 0 = Not supported or sent by Non-AP STA (default) -# 1 = Supported -# -# VHT TXOP PS: [VHT-TXOP-PS] -# Indicates whether or not the AP supports VHT TXOP Power Save Mode -# or whether or not the STA is in VHT TXOP Power Save mode -# 0 = VHT AP doesn't support VHT TXOP PS mode (OR) VHT STA not in VHT TXOP PS -# mode -# 1 = VHT AP supports VHT TXOP PS mode (OR) VHT STA is in VHT TXOP power save -# mode -# -# +HTC-VHT Capable: [HTC-VHT] -# Indicates whether or not the STA supports receiving a VHT variant HT Control -# field. -# 0 = Not supported (default) -# 1 = supported -# -# Maximum A-MPDU Length Exponent: [MAX-A-MPDU-LEN-EXP0]..[MAX-A-MPDU-LEN-EXP7] -# Indicates the maximum length of A-MPDU pre-EOF padding that the STA can recv -# This field is an integer in the range of 0 to 7. -# The length defined by this field is equal to -# 2 pow(13 + Maximum A-MPDU Length Exponent) -1 octets -# -# VHT Link Adaptation Capable: [VHT-LINK-ADAPT2] [VHT-LINK-ADAPT3] -# Indicates whether or not the STA supports link adaptation using VHT variant -# HT Control field -# If +HTC-VHTcapable is 1 -# 0 = (no feedback) if the STA does not provide VHT MFB (default) -# 1 = reserved -# 2 = (Unsolicited) if the STA provides only unsolicited VHT MFB -# 3 = (Both) if the STA can provide VHT MFB in response to VHT MRQ and if the -# STA provides unsolicited VHT MFB -# Reserved if +HTC-VHTcapable is 0 -# -# Rx Antenna Pattern Consistency: [RX-ANTENNA-PATTERN] -# Indicates the possibility of Rx antenna pattern change -# 0 = Rx antenna pattern might change during the lifetime of an association -# 1 = Rx antenna pattern does not change during the lifetime of an association -# -# Tx Antenna Pattern Consistency: [TX-ANTENNA-PATTERN] -# Indicates the possibility of Tx antenna pattern change -# 0 = Tx antenna pattern might change during the lifetime of an association -# 1 = Tx antenna pattern does not change during the lifetime of an association -#vht_capab=[SHORT-GI-80][HTC-VHT] -# -# Require stations to support VHT PHY (reject association if they do not) -#require_vht=1 - -# 0 = 20 or 40 MHz operating Channel width -# 1 = 80 MHz channel width -# 2 = 160 MHz channel width -# 3 = 80+80 MHz channel width -#vht_oper_chwidth=1 -# -# center freq = 5 GHz + (5 * index) -# So index 42 gives center freq 5.210 GHz -# which is channel 42 in 5G band -# -#vht_oper_centr_freq_seg0_idx=42 -# -# center freq = 5 GHz + (5 * index) -# So index 159 gives center freq 5.795 GHz -# which is channel 159 in 5G band -# -#vht_oper_centr_freq_seg1_idx=159 - -# Workaround to use station's nsts capability in (Re)Association Response frame -# This may be needed with some deployed devices as an interoperability -# workaround for beamforming if the AP's capability is greater than the -# station's capability. This is disabled by default and can be enabled by -# setting use_sta_nsts=1. -#use_sta_nsts=0 - -##### IEEE 802.1X-2004 related configuration ################################## - -# Require IEEE 802.1X authorization -#ieee8021x=1 - -# IEEE 802.1X/EAPOL version -# hostapd is implemented based on IEEE Std 802.1X-2004 which defines EAPOL -# version 2. However, there are many client implementations that do not handle -# the new version number correctly (they seem to drop the frames completely). -# In order to make hostapd interoperate with these clients, the version number -# can be set to the older version (1) with this configuration value. -#eapol_version=2 - -# Optional displayable message sent with EAP Request-Identity. The first \0 -# in this string will be converted to ASCII-0 (nul). This can be used to -# separate network info (comma separated list of attribute=value pairs); see, -# e.g., RFC 4284. -#eap_message=hello -#eap_message=hello\0networkid=netw,nasid=foo,portid=0,NAIRealms=example.com - -# WEP rekeying (disabled if key lengths are not set or are set to 0) -# Key lengths for default/broadcast and individual/unicast keys: -# 5 = 40-bit WEP (also known as 64-bit WEP with 40 secret bits) -# 13 = 104-bit WEP (also known as 128-bit WEP with 104 secret bits) -#wep_key_len_broadcast=5 -#wep_key_len_unicast=5 -# Rekeying period in seconds. 0 = do not rekey (i.e., set keys only once) -#wep_rekey_period=300 - -# EAPOL-Key index workaround (set bit7) for WinXP Supplicant (needed only if -# only broadcast keys are used) -eapol_key_index_workaround=0 - -# EAP reauthentication period in seconds (default: 3600 seconds; 0 = disable -# reauthentication). -#eap_reauth_period=3600 - -# Use PAE group address (01:80:c2:00:00:03) instead of individual target -# address when sending EAPOL frames with driver=wired. This is the most common -# mechanism used in wired authentication, but it also requires that the port -# is only used by one station. -#use_pae_group_addr=1 - -# EAP Re-authentication Protocol (ERP) authenticator (RFC 6696) -# -# Whether to initiate EAP authentication with EAP-Initiate/Re-auth-Start before -# EAP-Identity/Request -#erp_send_reauth_start=1 -# -# Domain name for EAP-Initiate/Re-auth-Start. Omitted from the message if not -# set (no local ER server). This is also used by the integrated EAP server if -# ERP is enabled (eap_server_erp=1). -#erp_domain=example.com - -##### Integrated EAP server ################################################### - -# Optionally, hostapd can be configured to use an integrated EAP server -# to process EAP authentication locally without need for an external RADIUS -# server. This functionality can be used both as a local authentication server -# for IEEE 802.1X/EAPOL and as a RADIUS server for other devices. - -# Use integrated EAP server instead of external RADIUS authentication -# server. This is also needed if hostapd is configured to act as a RADIUS -# authentication server. -eap_server=0 - -# Path for EAP server user database -# If SQLite support is included, this can be set to "sqlite:/path/to/sqlite.db" -# to use SQLite database instead of a text file. -#eap_user_file=/etc/hostapd.eap_user - -# CA certificate (PEM or DER file) for EAP-TLS/PEAP/TTLS -#ca_cert=/etc/hostapd.ca.pem - -# Server certificate (PEM or DER file) for EAP-TLS/PEAP/TTLS -#server_cert=/etc/hostapd.server.pem - -# Private key matching with the server certificate for EAP-TLS/PEAP/TTLS -# This may point to the same file as server_cert if both certificate and key -# are included in a single file. PKCS#12 (PFX) file (.p12/.pfx) can also be -# used by commenting out server_cert and specifying the PFX file as the -# private_key. -#private_key=/etc/hostapd.server.prv - -# Passphrase for private key -#private_key_passwd=secret passphrase - -# Server identity -# EAP methods that provide mechanism for authenticated server identity delivery -# use this value. If not set, "hostapd" is used as a default. -#server_id=server.example.com - -# Enable CRL verification. -# Note: hostapd does not yet support CRL downloading based on CDP. Thus, a -# valid CRL signed by the CA is required to be included in the ca_cert file. -# This can be done by using PEM format for CA certificate and CRL and -# concatenating these into one file. Whenever CRL changes, hostapd needs to be -# restarted to take the new CRL into use. -# 0 = do not verify CRLs (default) -# 1 = check the CRL of the user certificate -# 2 = check all CRLs in the certificate path -#check_crl=1 - -# TLS Session Lifetime in seconds -# This can be used to allow TLS sessions to be cached and resumed with an -# abbreviated handshake when using EAP-TLS/TTLS/PEAP. -# (default: 0 = session caching and resumption disabled) -#tls_session_lifetime=3600 - -# Cached OCSP stapling response (DER encoded) -# If set, this file is sent as a certificate status response by the EAP server -# if the EAP peer requests certificate status in the ClientHello message. -# This cache file can be updated, e.g., by running following command -# periodically to get an update from the OCSP responder: -# openssl ocsp \ -# -no_nonce \ -# -CAfile /etc/hostapd.ca.pem \ -# -issuer /etc/hostapd.ca.pem \ -# -cert /etc/hostapd.server.pem \ -# -url http://ocsp.example.com:8888/ \ -# -respout /tmp/ocsp-cache.der -#ocsp_stapling_response=/tmp/ocsp-cache.der - -# Cached OCSP stapling response list (DER encoded OCSPResponseList) -# This is similar to ocsp_stapling_response, but the extended version defined in -# RFC 6961 to allow multiple OCSP responses to be provided. -#ocsp_stapling_response_multi=/tmp/ocsp-multi-cache.der - -# dh_file: File path to DH/DSA parameters file (in PEM format) -# This is an optional configuration file for setting parameters for an -# ephemeral DH key exchange. In most cases, the default RSA authentication does -# not use this configuration. However, it is possible setup RSA to use -# ephemeral DH key exchange. In addition, ciphers with DSA keys always use -# ephemeral DH keys. This can be used to achieve forward secrecy. If the file -# is in DSA parameters format, it will be automatically converted into DH -# params. This parameter is required if anonymous EAP-FAST is used. -# You can generate DH parameters file with OpenSSL, e.g., -# "openssl dhparam -out /etc/hostapd.dh.pem 2048" -#dh_file=/etc/hostapd.dh.pem - -# OpenSSL cipher string -# -# This is an OpenSSL specific configuration option for configuring the default -# ciphers. If not set, "DEFAULT:!EXP:!LOW" is used as the default. -# See https://www.openssl.org/docs/apps/ciphers.html for OpenSSL documentation -# on cipher suite configuration. This is applicable only if hostapd is built to -# use OpenSSL. -#openssl_ciphers=DEFAULT:!EXP:!LOW - -# Fragment size for EAP methods -#fragment_size=1400 - -# Finite cyclic group for EAP-pwd. Number maps to group of domain parameters -# using the IANA repository for IKE (RFC 2409). -#pwd_group=19 - -# Configuration data for EAP-SIM database/authentication gateway interface. -# This is a text string in implementation specific format. The example -# implementation in eap_sim_db.c uses this as the UNIX domain socket name for -# the HLR/AuC gateway (e.g., hlr_auc_gw). In this case, the path uses "unix:" -# prefix. If hostapd is built with SQLite support (CONFIG_SQLITE=y in .config), -# database file can be described with an optional db= parameter. -#eap_sim_db=unix:/tmp/hlr_auc_gw.sock -#eap_sim_db=unix:/tmp/hlr_auc_gw.sock db=/tmp/hostapd.db - -# EAP-SIM DB request timeout -# This parameter sets the maximum time to wait for a database request response. -# The parameter value is in seconds. -#eap_sim_db_timeout=1 - -# Encryption key for EAP-FAST PAC-Opaque values. This key must be a secret, -# random value. It is configured as a 16-octet value in hex format. It can be -# generated, e.g., with the following command: -# od -tx1 -v -N16 /dev/random | colrm 1 8 | tr -d ' ' -#pac_opaque_encr_key=000102030405060708090a0b0c0d0e0f - -# EAP-FAST authority identity (A-ID) -# A-ID indicates the identity of the authority that issues PACs. The A-ID -# should be unique across all issuing servers. In theory, this is a variable -# length field, but due to some existing implementations requiring A-ID to be -# 16 octets in length, it is strongly recommended to use that length for the -# field to provid interoperability with deployed peer implementations. This -# field is configured in hex format. -#eap_fast_a_id=101112131415161718191a1b1c1d1e1f - -# EAP-FAST authority identifier information (A-ID-Info) -# This is a user-friendly name for the A-ID. For example, the enterprise name -# and server name in a human-readable format. This field is encoded as UTF-8. -#eap_fast_a_id_info=test server - -# Enable/disable different EAP-FAST provisioning modes: -#0 = provisioning disabled -#1 = only anonymous provisioning allowed -#2 = only authenticated provisioning allowed -#3 = both provisioning modes allowed (default) -#eap_fast_prov=3 - -# EAP-FAST PAC-Key lifetime in seconds (hard limit) -#pac_key_lifetime=604800 - -# EAP-FAST PAC-Key refresh time in seconds (soft limit on remaining hard -# limit). The server will generate a new PAC-Key when this number of seconds -# (or fewer) of the lifetime remains. -#pac_key_refresh_time=86400 - -# EAP-SIM and EAP-AKA protected success/failure indication using AT_RESULT_IND -# (default: 0 = disabled). -#eap_sim_aka_result_ind=1 - -# Trusted Network Connect (TNC) -# If enabled, TNC validation will be required before the peer is allowed to -# connect. Note: This is only used with EAP-TTLS and EAP-FAST. If any other -# EAP method is enabled, the peer will be allowed to connect without TNC. -#tnc=1 - -# EAP Re-authentication Protocol (ERP) - RFC 6696 -# -# Whether to enable ERP on the EAP server. -#eap_serve