Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| toh:netgear:lbr20 [2024/11/20 16:38] – [Specific Configuration & Gotchas] grammer, spelling, and new information regarding A06 01.008 (the latest modem firmware) s2s2 | toh:netgear:lbr20 [2024/11/24 20:34] – [OEM easy installation] tiny change to formatting/layout s2s2 | ||
|---|---|---|---|
| Line 31: | Line 31: | ||
| * You will get a warning that the version you are trying to flash is older. Just click ' | * You will get a warning that the version you are trying to flash is older. Just click ' | ||
| * Settings in the NVRAM (the settings for the Netgear/ | * Settings in the NVRAM (the settings for the Netgear/ | ||
| - | | + | * If you flash back to Netgear/ |
| - | * > This is convenient, because if you have a little difficulty with Openwrt or need to test something out, the N/V firmware will still have your previous settings. | + | |
| ==== OEM installation using the TFTP method ==== | ==== OEM installation using the TFTP method ==== | ||
| Line 67: | Line 67: | ||
| * **Qfirehose Quectel Modem Upgrade-Flashing Procedure**: | * **Qfirehose Quectel Modem Upgrade-Flashing Procedure**: | ||
| * [083.292]: Upgrade module successfully.</ | * [083.292]: Upgrade module successfully.</ | ||
| - | * Using the command | + | * The modem (not the entire router) will reboot 10 seconds later, and reconnect to the cell provider. |
| - | * The latest A06 01.008 modem firmware, does not display a 01.008 revision code after the ...A06M4G. | + | * Using '' |
| - | * The ''/ | + | * The latest A06 01.008 modem firmware, does not display a 01.008 revision code after the ...A06M4G |
| + | * The Netgear-provided A05 firmware, also does not display a revision code after the A05M4G response. | ||
| + | * The ''/ | ||
| ==== QMI / wwan0 / 4G LTE Monitoring Script ==== | ==== QMI / wwan0 / 4G LTE Monitoring Script ==== | ||
| Here is a wan_watchdog.sh script that tests the connection, and if it receives no response from several well-known DNS providers, it will: | Here is a wan_watchdog.sh script that tests the connection, and if it receives no response from several well-known DNS providers, it will: | ||
| Line 84: | Line 86: | ||
| < | < | ||
| #!/bin/sh | #!/bin/sh | ||
| + | |||
| TRIES=" | TRIES=" | ||
| - | while [[ " | + | while [[ " |
| do | do | ||
| echo $TRIES | echo $TRIES | ||
| echo " | echo " | ||
| - | # ONE failure will not fail fping. All of them failing, will. | + | # ONE site failure will not fail fping. All of them failing, will. |
| if fping --alive 1.1.1.1 9.9.9.9 8.8.8.8 2001: | if fping --alive 1.1.1.1 9.9.9.9 8.8.8.8 2001: | ||
| - | # if fping --alive blablahblah | grep -q . # this will intentionally make the script fail, when we are testing | + | # if fping --alive blablahblah | grep -q . # this will intentionally make the script fail, when we are testing. |
| then | then | ||
| - | echo " | + | echo " |
| exit 0 | exit 0 | ||
| fi | fi | ||
| Line 100: | Line 103: | ||
| done | done | ||
| - | echo "PING FAILED | + | echo "PING FAILED |
| - | # Tell the modem to turn off without actually disconnecting the tty serial communication interface: | + | # There are a variety of ways to restart the Quectel/4G interface. |
| - | echo AT+CFUN=0 | socat - / | + | # The original script used hub-ctrl to turn-off, then turn-on, the USB hub. |
| - | sleep 5 | + | # However, devices like the Orbi LBR20 with a EM18-xx 4G chip, don't use a |
| - | # tell the modem to turn on | + | # USB bus. Older devices like the GL-X750, do (through a mini-pci-e slot). |
| - | echo AT+CFUN=1 | socat - / | + | # Restart hub: (GL-X750/ |
| - | sleep 5 | + | # hub-ctrl -b 001 -d 002 -P 2 -p 0 |
| - | # restart the network interface | + | # More general use: EG18xx EC25xx etc: |
| - | ifup qmippp # this is where you change ' | + | ifup qmippp # restarts the interface |
| - | date >> / | + | sleep 15 # give the modem time to reconnect |
| + | # Alternative method (older modem firmware, ymmv) | ||
| + | # Tell the modem to turn off without actually disconnecting the tty serial | ||
| + | # communication interface: | ||
| + | # echo AT+CFUN=0 | socat - / | ||
| + | # sleep 3 | ||
| + | # Tell the modem to turn on | ||
| + | # echo AT+CFUN=1 | socat - / | ||
| + | # sleep 7 | ||
| + | echo " | ||
| + | date >> / | ||
| + | # sleep 2 # pause before bringing the hub back up | ||
| + | # hub-ctrl -b 001 -d 002 -P 2 -p 1 | ||
| + | # Test if the previous steps worked. If yes, exit. If no, reboot. | ||
| + | # The following network restart may work for you, but usually the modem itself is crashed and so the LBR20 requires | ||
| + | # if fping --alive 1.1.1.1 9.9.9.9 8.8.8.8 2001: | ||
| + | # then | ||
| + | # echo " | ||
| + | # echo " | ||
| + | # exit 0 | ||
| + | # fi | ||
| + | # echo " | ||
| + | # sleep 5 | ||
| + | # | ||
| + | # sleep 25 | ||
| + | if fping --alive 1.1.1.1 9.9.9.9 8.8.8.8 2001: | ||
| + | then | ||
| + | echo " | ||
| + | echo " | ||
| + | exit 0 | ||
| + | fi | ||
| + | echo " | ||
| + | echo " | ||
| + | sleep 5 | ||
| + | reboot | ||
| </ | </ | ||
| ==== Network interfaces ==== | ==== Network interfaces ==== | ||