Quick Question about Factory Default Settings

Home Forums Conduit: AEP Model Quick Question about Factory Default Settings

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #29779
    William Laing
    Participant

    MTCDT-LVW2-247A Firmware 1.7.4

    Good Day –

    I searched the Knowledge Base and Forum but cannot find the factory default settings for this Conduit.

    I’m guessing that the default/out-of-the-box configuration for Wi-Fi ap and client are both disabled – is that correct?

    Thanks!
    William

    #29780
    Jeff Hatch
    Keymaster

    Hello William,

    You are correct, Wi-Fi Access Point and Wi-Fi Client are both disabled when the device is set to Factory Settings.

    Jeff

    #29782
    William Laing
    Participant

    Thank you, Jeff – appreciate it!

    Have a great day.

    William

    #29783
    William Laing
    Participant

    One more question, Jeff –

    Do you know if there’s a way to initiate a scan of available Wi-Fi networks that the Wi-FI client (WAN) could use?

    We are using the REST API and have tried various combinations of enabling/disabling the Wi-Fi client, resetting Wi-Fi, etc., but nothing seems to initiate a scan. We keep getting empty arrays for wifi/networks and wifi/client/savedNetworks.

    Thanks,
    William

    #29784
    Jeff Hatch
    Keymaster

    Hello William,

    There is not a WiFi scan request through the API. The values you see in the GET requests you are doing are generated dynamically by a separate thread in the API. Theoretically, the data should be updated when a valid scan can be done (see next paragraph).

    The WiFi on Conduit has a limitation that it cannot do a scan while the WiFi client is connected.

    There is a script called wifiscan that exists on the Conduit that can be used as a reference for doing a wifi scan. As you will see in that script, it checks to see if the client is connected first before it tries to do a scan.

    Hope that helps.

    Jeff

    #29785
    William Laing
    Participant

    Hi Jeff –

    Does the wifiscan script exist on firmware 1.7.4?

    The only names I see are:

    sudo find / -name ‘*wifiscan*’ -print

    /var/lib/opkg/info/jswifiscan.control
    /var/lib/opkg/info/jswifiscan.list
    /usr/bin/jswifiscan

    And jswifiscan appears to be a binary executable.

    Using REST API, we have tried clearing the savedNetworks, disabling the wifi client, and then re-enabling the wifi client – to ensure no connections. But we still don’t see any networks. My phone sees about a dozen wifi networks here in the office next to the Conduit.

    The client will enter their SSID. We’d like to parse the scanned networks to extract that network and get the rest of the information we need to add it into savedNetworks.

    Any help appreciated.

    Thanks,
    William

    #29786
    Jeff Hatch
    Keymaster

    Hello William,

    That script may not exist on 1.7.4. I know it exists in 5.0.0.

    #!/bin/sh

    DEBUG=1

    if ((DEBUG)) ; then
    LOGDBG=”/usr/bin/logger -s -t WIFI”
    else
    LOGDBG=”echo”
    fi

    function scan() {
    # Ensure WLAN is up

    if [ ! -d /sys/class/net/wlan0 ]; then
    ${LOGDBG} “Wifi client is not run”
    fi
    WLAN0_STATE=$(ifconfig wlan0 |grep UP|awk ‘{print $1}’)
    if [ $WLAN0_STATE != “UP” ];then
    ifconfig wlan0 up
    ${LOGDBG} “wlan0 is not up. bringing up”
    fi
    WLAN0_STATE=$(ifconfig wlan0 |grep UP|awk ‘{print $1}’)
    if [ $WLAN0_STATE != “UP” ] ;then
    ${LOGDBG} “wlan0 has not been up. Scan is not possible”
    exit 0
    fi
    ALLOW_SCAN=”true”
    #
    # Scanning hangs on connected rs9113 chip
    #
    RS9113_DETECTED=$(/usr/bin/lsusb | grep -o 1618:9113)
    if [[ -n “$RS9113_DETECTED” ]]; then
    CURRENT_SSID=$(iw dev wlan0 link | grep ‘SSID:’ | awk ‘{print $2}’)
    if [[ -n “$CURRENT_SSID” ]]; then
    ${LOGDBG} “WiFi is connected to an access point. Scan is not possible.”
    ALLOW_SCAN=”false”
    fi
    fi

    if [[ “$ALLOW_SCAN” == “false” ]]; then
    exit 0
    fi

    ${LOGDBG} “Start scanning”
    # Scan
    #workaround rs9113 driver issue.
    #if wifi client has connection to AP scanning doesnt stop never.
    mts-timeout -t 15 -s 2 iw wlan0 scan
    }

    scan

    #29797
    William Laing
    Participant

    Thank you, Jeff – we appreciate the help.

    Best,
    William

Viewing 8 posts - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.