Wireless Joint

Cameleer wrote: Wed Aug 04, 2021 9:05 am Thank you hazerjast for your awesome work and info! I have my LBR20 running the newest Voxel. I'm running T-mobile Magent Max with working magic on the orbi and using the wifi from the orbi. Even with your great instructions I still can't get my TTL working correctly. Still having some leakage. From a command prompt using orbi wifi when I ping DNS 8.8.8.8 I come back with TTL=110. I have tried various mixed rules of TTL 64 and 65 still nothing. When I check the above TTL rules step 11 in telnet I get back Ipv4 = 65, but nothing on the IPv6. The IPv6 script shows the routing just no IPv6=65 at the end.

Does anyone have any ideas about what to try next?

I have an old archer c7 router with golden orb on it setting here unused. Would It be easier/safer to use the wifi from the C7 and set the TTL on it?

Setting this up for my mother in law so would really like to just use the orbi 100% and have one less router to deal with .

Thanks

gscheb wrote: Thu Aug 05, 2021 8:45 am Hello, Been using one of these for AT&T. With original orbi firmware. Being AT&T have no use for TTL settings. But would like to create a group of bands. Do I have to switch to this voxel to do that?

Sam023432 wrote: Thu Aug 05, 2021 2:14 pm i know its not recommended but i had the same issue the only way i got it to work was to put the ip6 scrip code in with the ip4 code and it worked like a charm so far but either way his guide was a blessing so no complaints here ttl 64 hl64 on reboot (set at 64 seems to be the one for verizon) i cant thank hazarjast enough note...... made the actual code part one long line per command

root@LBR20:~# cat /mnt/circle/overlay/opt/scripts/firewall*
# IPv4 TTL mod
iptables -t mangle -C POSTROUTING -o wwan0 -j TTL --ttl-set 64 > /dev/null 2>&1 || \iptables -t mangle -I POSTROUTING 1 -o wwan0 -j TTL --ttl-set 64

ip6tables -t mangle -C POSTROUTING -o wwan0 -j HL --hl-set 64 > /dev/null 2>&1 || \ip6tabl[/b]es -t mangle -A POSTROUTING -o wwan0 -j HL --hl-set 64

(in the script code is one long line per command delete space between\ ip in red so \ip)

i get 118 when i ping google as well not really sure what to do there but still this is much better then having to change manually evey time so thank you hazarjast i really appreciate your how to guide maybe when you get some time you can q us in on changing the dns also : ) : )

root@LBR20:~# cat /opt/scripts/firewall-start.sh
# IPv4 TTL mod
iptables -t mangle -C POSTROUTING -o wwan0 -j TTL --ttl-set 65 > /dev/null 2>&1 || \
iptables -t mangle -I POSTROUTING 1 -o wwan0 -j TTL --ttl-set 65

# IPv6 TTL mod (prevents leaks not covered by IPv4 rules)
ip6tables -t mangle -C POSTROUTING -o wwan0 -j HL --hl-set 65 > /dev/null 2>&1 || \
ip6tables -t mangle -I POSTROUTING 1 -o wwan0 -j HL --hl-set 65

root@LBR20:~#

gilbreen wrote: Mon Aug 09, 2021 7:00 pm Magic allows the Orbi to appear as whatever device you told your carrier you were using for their service. Some carriers will remove your plan if you are not connecting with the device you said you were using.

Sam023432 wrote: Thu Aug 12, 2021 4:36 pm you wouldnt happen to have a link to the software or how to go about this with the orbi not having usb and all ?????????

BillA wrote: Fri Aug 13, 2021 3:45 am There's typo in "\ip6tabl[/b]es" should be "\ip6tables".
Here are the correct commands enclosed in code.

Code: Select all

iptables -t mangle -C POSTROUTING -o wwan0 -j TTL --ttl-set 64 > /dev/null 2>&1 || \iptables -t mangle -I POSTROUTING 1 -o wwan0 -j TTL --ttl-set 64
ip6tables -t mangle -C POSTROUTING -o wwan0 -j HL --hl-set 64 > /dev/null 2>&1 || \ip6tables -t mangle -A POSTROUTING -o wwan0 -j HL --hl-set 64

tal7901 wrote: Sat Aug 14, 2021 11:05 pm Has anyone experienced a speed drop using AT&T? I'm on the $20 Ipad tablet plan using latest Voxel and magic and usually get 75-135 download on speed test but tonight only 25-30. Currently it's connected to band 14 but usually connects to band 66. I've tried rebooting several times hoping to connect to ban 66 to see if that's he problem but no luck. Also has anyone successfully been able to band lock with AT&T and if so how lol! thanks

am888 wrote: Thu Aug 19, 2021 9:59 am VOXEL FIRMWARE
--------------
Is there any sort of cron with voxel? (NM - found cron - will see if I can get it to stick)
Will it try and auto-update the firmware if I don't use any sort of DNS block?

One thing I thought would be neat - though outside of my ability - would be being able to send an SMS to the router to reboot or feedback data usage... I assume this would be possible.

Thanks

As an LOL someone at netgear put their auto-update of QoS @ 0420

Meh - can't get it to hold crontab - it mounts the crontab from a different section of ROM than the circle overlay so it continually rewrites it. Any ideas??
----------------------------

UPDATE:
1. created /mnt/circle/overlay/etc/rc.local
2. contents of rc.local

Code: Select all

# Put your custom commands here that should be executed once
# the system init finished. By default this file does nothing.

#Crontab located at /mnt/circle/overlay/etc/crontabs/root
cat /etc/crontabs/root > /tmp/etc/crontabs/root

exit 0

3. Created /mnt/circle/overlay/etc/crontabs/root (rw/r/r perms) <------- This is your new crontab (for editing/persists)

my root/cron file contents:

Code: Select all

20 04 * * * /TM/QoSControl auto_update
50 03 * * * /usr/share/armor/bdupd_start_schedule.sh
00 02 * * 1,4 /sbin/reboot

I need my router to reboot a couple times a week since I'm not always there.
Voila - I have a working crontab that persists on reboot.

am888 wrote: Thu Aug 19, 2021 9:59 am VOXEL FIRMWARE
--------------
Is there any sort of cron with voxel? (NM - found cron - will see if I can get it to stick)
Will it try and auto-update the firmware if I don't use any sort of DNS block?

One thing I thought would be neat - though outside of my ability - would be being able to send an SMS to the router to reboot or feedback data usage... I assume this would be possible.

Thanks

As an LOL someone at netgear put their auto-update of QoS @ 0420

Meh - can't get it to hold crontab - it mounts the crontab from a different section of ROM than the circle overlay so it continually rewrites it. Any ideas??
----------------------------

UPDATE:
1. created /mnt/circle/overlay/etc/rc.local
2. contents of rc.local

Code: Select all

# Put your custom commands here that should be executed once
# the system init finished. By default this file does nothing.

#Crontab located at /mnt/circle/overlay/etc/crontabs/root
cat /etc/crontabs/root > /tmp/etc/crontabs/root

exit 0

3. Created /mnt/circle/overlay/etc/crontabs/root (rw/r/r perms) <------- This is your new crontab (for editing/persists)

my root/cron file contents:

Code: Select all

20 04 * * * /TM/QoSControl auto_update
50 03 * * * /usr/share/armor/bdupd_start_schedule.sh
00 02 * * 1,4 /sbin/reboot

I need my router to reboot a couple times a week since I'm not always there.
Voila - I have a working crontab that persists on reboot.

1. SSH into your LBR20 using Putty.
2. Issue the following commands:

   Code: Select all

   mkdir -p /mnt/circle/overlay/opt/scripts
   touch /mnt/circle/overlay/opt/scripts/firewall-start.sh
   chmod 755 /mnt/circle/overlay/opt/scripts/firewall-start.sh
   

3. Now we will populate the firewall script file we created. To do this, we will use the text editor 'vi'. Let's start by opening the IPv4 firewall script in vi:

   Code: Select all

   vi /mnt/circle/overlay/opt/scripts/firewall-start.sh
   

4. Once the file is open in vi, you have to press the "I" (as in "igloo") key on your keyboard to enter "Insert" mode.
5. Then, select the following text from the code box and copy it to your clipboard ("Ctrl+C"):

   Code: Select all

   # IPv4 TTL mod
   iptables -t mangle -C POSTROUTING -o wwan0 -j TTL --ttl-set 65 > /dev/null 2>&1 || \
   iptables -t mangle -I POSTROUTING 1 -o wwan0 -j TTL --ttl-set 65
   # IPv6 TTL mod (prevents leaks not covered by IPv4 rules)
   ip6tables -t mangle -C POSTROUTING -o wwan0 -j HL --hl-set 65 > /dev/null 2>&1 || \
   ip6tables -t mangle -I POSTROUTING 1 -o wwan0 -j HL --hl-set 65
   

6. Now paste the text from your clipboard into the Putty window by right-clicking with your mouse anywhere inside it. You should see the text appear in vi.
7. Hit 'Enter' to add a new line, then press "Esc" (escape key) on your keyboard which will take you out of "Insert" mode. Save and exit vi by typing the following followed by "Enter" on your keyboard:

   Code: Select all

   :wq
   

   (":" = enter vi command mode, "w" = write changes to the file, "q" = quit vi)
8. Check your work by issuing the following command:

   Code: Select all

   cat /mnt/circle/overlay/opt/scripts/firewall-start.sh
   

   The output should show all the iptables commands you've added from the code box above in the previous steps. If it does not, go back into the file and check for mistakes (maybe you didn't paste before saving, maybe you forgot "w" when existing vi and the text was not saved, etc.).
9. Issue the following command to restart the LBR20 to check that your scripts execute properly on startup:

   Code: Select all

   reboot
   

10. Once the unit has rebooted and some minutes have passed to be sure all services have started, issue the following two commands to check that your iptables rules are active:

    Code: Select all

    iptables -t mangle -L
    ip6tables -t mangle -L
    

    The last line of output from each command should show a POSTROUTING rule with a value of "65". If not, then something went wrong and your iptables rules are not active. Check that the 'firewall-start.sh' script file exists where you created it the previous steps above and that it is populated with the necessary iptables text in the code box from previous steps. Also, be sure that you did not miss the "chmod 755" command when creating the file as this makes it executable. Fix any errors you encounter, then reboot and execute the above iptables commands again to re-check.

am888 wrote: Mon Aug 23, 2021 6:03 pm Hazarjast - have you found /rom/sbin/wlandebug.sh

It's a pretty interesting file. It's literally every setting in the router.

am888 wrote: Tue Aug 24, 2021 3:50 pm I forked a keep-alive script for the Orbi and added it to my cron. Working good so far.
(sorry took this post down ealier cause i ran into some issues)

Will reboot router on failure.

https://github.com/HiDef888/openwrt-lte-keep-alive

Easy to install, just run script in /mnt/circle/overlay/opt/scripts (is what i'd recommend)

Originally had it drop modem and restart on fail - but that was a disaster. Erased many of my settings and so on, so I just went with a simple reboot on x3 fails. Call it as often as you like in cron...

shinesmart wrote: Tue Aug 24, 2021 8:17 pm I’ve put together this guide to help anyone wishing to Cell Lock to a specific cell. Please use at your own risk and know the pros and cons of cell locking before jumping in.

Netgear Orbi LBR20 Cell Locking
Author: shinesmart

Login using PuTTy:
192.168.1.1
UN: root
PW: your admin password

To query the Serving Cell:
echo -ne "AT+QENG=\"servingcell\"\r\n" | microcom -X -t 1000 /dev/ttyUSB2

You will get a response like this:
AT+QENG="servingcell"
+QENG: "servingcell","NOCONN","LTE","FDD",311,480,1B29020,245,66636,66,5,5,6F00,-92,-11,-58,11,-,-,-

In this example, the PCID is 245 and the EARCFN is 66636, which is for the Serving Cell you are currently connected to.

Now, to lock to this cell, run this command replacing the EARCFN and PCID with the values from above:
echo -ne "AT+QNWLOCK=\"common/4g\",1,EARCFN,PCID\r\n" | microcom -X -t 1000 /dev/ttyUSB2

Example: echo -ne "AT+QNWLOCK=\"common/4g\",1,66636,245\r\n" | microcom -X -t 1000 /dev/ttyUSB2

You will get a response like this:
AT+QNWLOCK="common/4g",1,66636,245
OK

Alternatively, you can query the Neighbouring Cell, then use the same lock command once you have its respective EARCFN and PCID:

To query the Neighbouring Cell:
echo -ne "AT+QENG=\"neighbourcell\"\r\n" | microcom -X -t 1000 /dev/ttyUSB2

To lock the Neighbouring Cell:
echo -ne "AT+QNWLOCK=\"common/4g\",1,EARCFN,PCID\r\n" | microcom -X -t 1000 /dev/ttyUSB2


* Note: Cell locking does not persist on this device, so these steps will need to be performed following each reboot.

Please feel free to proof check this guide.

echo -ne "AT+QNWLOCK=\"common/4g\",1,66636,245\r\n" | microcom -X -t 1000 /dev/ttyUSB2

hazarjast wrote: Wed Aug 25, 2021 3:45 pm It is funny you had posted this today because I just finished working on the first version of a script that directly relates to cell locking and checking for connectivity in case the cell stops passing internet traffic for whatever reason (malfunction, maintenance, etc.). For simplicity I threw it up with the CJ scripts on GitHub. Feel free to use if it seems helpful to you but realize I'm still 'beta' testing it

https://github.com/hazarjast/circle_jer ... ailsafe.sh

The workflow of the script is thus: on execution it runs the following in an infinite loop at the set $INVERVAL:

- Pings hosts defined in $ALLDEST until one succeeds ($CONNECTED=1).
- If Internet connectivity is confirmed, the script checks if a cell is locked.
- If a cell is locked, nothing is done and the script sleeps until the next $INTERVAL has passed.
- If internet connectivity is present and no cell is locked it will lock to the cell values defined in $LOCKCELL.
- Once a cell is locked it will check for internet connectivity again.
- If original test for internet connectivity fails or check after cell lock fails, the script will remove the cell lock.
- The script waits the length of $INVERAL then performs all of the above again (checking connectivity, locking to a cell if not already locked, etc.).

gilbreen wrote: Thu Aug 26, 2021 1:03 am hazerjast,

Another awesome addition. Thanks! Where do you recommend that this script be placed in order for it to run each time on bootup of the Orbi?

mkdir -p /mnt/circle/overlay/etc
cp -p /etc/rc.local /mnt/circle/overlay/etc

# Put your custom commands here that should be executed once
# the system init finished. By default this file does nothing.

/opt/scripts/cell_lock_failsafe.sh &

exit 0

hazarjast wrote: Thu Aug 26, 2021 9:22 am I would store it on the overlay filesystem under '/mnt/circle/overlay/opt/scripts' where the 'firewall-start.sh' script is located. That way it can easily be called from '/opt/scripts' after restart.

If you have not already created an overlay filesystem copy of 'rc.local' you will need to do that first so we can add our own scripts to run on startup:

Code: Select all

mkdir -p /mnt/circle/overlay/etc
cp -p /etc/rc.local /mnt/circle/overlay/etc

Then, just add a line to the custom '/mnt/circle/overlay/etc/rc.local' to have it call the script in background ('&'):

Code: Select all

# Put your custom commands here that should be executed once
# the system init finished. By default this file does nothing.

/opt/scripts/cell_lock_failsafe.sh &

exit 0

I updated the script on GitHub to add a two minute sleep since most folks will probably want to run this on startup the same as yourself. This allows the modem time to connect normally before the first run of the main 'while' loop so that no cell unlocking/locking commands are issued to it while it's trying to initiate the carrier connection. It might not necessarily harm anything without the sleep command but I've added it just for insurance. If you test without the sleep command and find the modem still connects fine on restart then feel free to remove it.

gilbreen wrote: Thu Aug 26, 2021 9:37 am hazarjast,

Does one also need to add a line to the rc.local file to call the firewall-start.sh or does it start on its own? Just trying to understand better.

hazarjast wrote: Sun Aug 15, 2021 10:38 pm No, you can band lock on any firmware but be aware it may not be reboot persistent unless you add it to a startup script. I prefer cell locking myself which is covered in the OP, other posts in this forum cover Quectel band index creation and locking. I believe I may have linked to them in one of my earlier replies to this thread and there should be an Excel/Google Sheets document floating around which helps with the index calculations (they are in hexadecimal).

gscheb wrote: Sun Aug 29, 2021 12:27 am gscheb wrote: ↑
Thu Aug 05, 2021 9:45 am
Hello, Been using one of these for AT&T. With original orbi firmware. Being AT&T have no use for TTL settings. But would like to create a group of bands. Do I have to switch to this voxel to do that?



Having issues using putty telnet on this. Seen a post where you got to enable telnet on the LBR20. But when I go to do that there is no enable telnet box to check.
LBR20
Router Firmware Version
V2.6.5.2

am888 wrote: Sun Aug 29, 2021 8:21 pm From what I understand, they removed the telnet option from later firmware versions. You'll be doing yourself a big favor to use voxel or circle_jerk to 'unlock' your routers potential & communicate with the modem directly. Your second worst option (besides leaving it as is) is probably to flash back to original netgear firmare, but your modem will likely erase all your setting everytime it reboots (so you gotta start all over). Just switch to circlejerk or voxel and save yourself a lot of headaches.

gscheb wrote: Sun Aug 29, 2021 9:27 pm Have used rooter in the past. Want to use this instead since have had some issues with AT&T on rooter for some reason.
Haven't modified one of these LBR20 before.
Thought that the Circle_Jerk was something running on Voxel. All I want to do is block out band 30 on AT&T. Keeps connecting as my primary band and making my upload speeds terrible. What is by best path for this and can I get some assistance maybe?
Have read the whole post from start to finish. Think you need some knowledge on it to understand this thread.
Also don't plan on using WiFi from the device just as a modem. Have another router plugged into it as a access point.

hazarjast wrote: Mon Aug 30, 2021 8:56 am Your most user-friendly path forward is to downgrade your firmware to Netgear 2.5.2.20 (first link below), then flash Voxel (second link below):
https://www.downloads.netgear.com/files ... 5.2.20.zip
https://voxel-firmware.com/Downloads/Vo ... 5SF-HW.zip

If you want to run on the latest Netgear firmware then your option is to use Circle_Jerk or at least the telnet-enable2 exe or Python script from it to enable telnet as Netgear has removed 'Enable telnet' option from 'debug.htm' on the newer firmware releases. Some folks prefer this option to keep on the latest Netgear firmware but given Netgear takes so long to patch security vulnerabilities etc. I prefer running Voxel myself (and I'll be the first to admit CJ install is typically a lot more effort for the uninitiated than simply downgrading and flashing Voxel).

gscheb wrote: Mon Aug 30, 2021 9:26 am Thanks for the advice. Have a couple of questions.
1. If someone decides Voxel isn't for them is it easy enough to go back to Netgear Firmware?
2. Once you get Voxel loaded do you communicate to the modem thru telnet?
3. Once band 30 is locked out will it stay thru reboots of the device?

MattB29 wrote: Fri Sep 03, 2021 6:53 am Would someone that has a Orbi LBR20 do a IMEI check at Cricket https://www.cricketwireless.com/cell-ph ... your-phone to see if it is compatible? If not likely AT&T is also going to turn these off come Feb. 2022 as being 3G devices.

Keaton85 wrote: Sun Sep 05, 2021 9:50 pm Edit: figured it out

Does Voxel firmware have auto-update patch already applied?

Largition wrote: Thu Sep 09, 2021 1:59 am Has this been a Windows only experience thus far? A non-chromebook laptop on the cheap seems essential here.

am888 wrote: Thu Aug 19, 2021 9:59 am

mkdir -p /mnt/circle/overlay/etc/
cp -p /etc/rc.local /mnt/circle/overlay/etc

# Put your custom commands here that should be executed once
# the system init finished. By default this file does nothing.

#Crontab located at /mnt/circle/overlay/etc/crontabs/root
cat /etc/crontabs/root > /tmp/etc/crontabs/root

exit 0

mkdir -p /mnt/circle/overlay/etc/crontabs/
vim /mnt/circle/overlay/etc/crontabs/root (since I'm root it automatically had 644 permissions.)
paste:
*/15 * * * * /mnt/circle/overlay/opt/scripts/internet-keep-alive.sh (This sets it to 15 minutes, right?)

am888 wrote: Wed Sep 15, 2021 9:52 am Sorry Crasoum,

I've been out sick. Did it work for you??
I would check logs to verify it's making a connection and, if so, you're good.

-am

ajipro wrote: Thu Sep 16, 2021 8:16 pm1; How do I see what bands I'm currently on?

echo -ne "AT+QCAINFO?\r\n" | microcom -X -t 1000 /dev/ttyUSB2

ajipro wrote: Thu Sep 16, 2021 8:16 pm2: What's the telnet command for changing the bands?

dhare72 wrote: Fri Sep 24, 2021 11:21 am Can anyone post a video tutorial on accessing ORBI LRB20 shell using a Mac (terminal)?

ssh -l root 192.168.1.1

echo -ne "AT+QNWLOCK=\"common/4g\",0\r\n" | microcom -X -t 1000 /dev/ttyUSB2

IronBorg wrote: Mon Sep 27, 2021 1:28 pm Hello and thank you for the awesome firmware. I'm currently running V9.2.5.2.25SF-HW and have successfully connected to the router using SSH. Can someone please help me with enabling bridge mode please?

little-endian wrote: Tue Sep 28, 2021 9:11 am

Code: Select all

echo -ne "AT+QCAINFO?\r\n" | microcom -X -t 1000 /dev/ttyUSB2

...

I also have a few points on my own to all of you:

Somehow, the cell lock behaviour is quite strange in my case. When I lock it to one only, I partly still end up with CA enabled (as far as I can tell):

root@LBR20:~# echo -ne "AT+QNWLOCK=\"common/4g\",1,1600,292\r\n" | microcom -X -t 1000 /dev/ttyUSB2
root@LBR20:~#
root@LBR20:~#
root@LBR20:~# echo -ne "AT+QCAINFO?\r\n" | microcom -X -t 1000 /dev/ttyUSB2
AT+QCAINFO?
+QCAINFO: "pcc",1600,75,"LTE BAND 3",1,264,-99,-20,-60,12
+QCAINFO: "scc",6200,50,"LTE BAND 20",1,38,-91,-18,-62,-5,DL

Furthermore, at some point, the LBR20 decided to only use Band 1, even after rebooting or entering the command

Code: Select all

echo -ne "AT+QNWLOCK=\"common/4g\",0\r\n" | microcom -X -t 1000 /dev/ttyUSB2

Not only should the cell locking be persistent after a reboot, nor should it have any effect at latest after entering the command above, should it?

The only way to restore the usual B3+B7+B20 combination however for me was to perform a factory reset, hardly convenient for any testing or tuning.

Independently of that - has anyone managed to route the guest wifi over a VPN with "kill switch" functionality yet? My goal is to run the OpenVPN client according to the readme provided by the Voxel firmware, however only for traffic passing the guest SSID and nothing else. If anyone happens to have some working iptables or ebtables or whatnot script, I would greatly appreciate any help, thanks.

am888 wrote: Wed Sep 29, 2021 9:14 pm There is no bridge mode, for all practical purposes, on the LBR20.

Klockwork77 wrote: Mon Oct 04, 2021 11:25 am Is there an error log somewhere after getting error sending AT commands?

hazarjast wrote: Tue Oct 05, 2021 1:38 pm Is there a specific command you are trying to issue to the modem which is resulting in "ERROR" being returned? If you are able to post the exact command and/or a screenshot we may be able to tell you whether the command exists for this particular Quectel modem and whether it is syntactically sound.

cat /dev/ttyUSB2` echo -e "AT +EMGR=1,7,\"012345678911121\"\r\n" > /dev/ttyUSB2`

Klockwork77 wrote: Tue Oct 05, 2021 6:07 pm I'm trying to send AT command using what you posted through ssh.

Code: Select all

cat /dev/ttyUSB2` echo -e "AT +EMGR=1,7,\"012345678911121\"\r\n" > /dev/ttyUSB2`

You can ignore the proton email I sent you about this topic if you reply here.

hazarjast wrote: Tue Oct 05, 2021 1:07 pm 'AT+QCAINFO?' can give you band info but it is specifically used for showing info about carrier aggregation status. I think mostly Netgear and folks interactively querying the modem are using 'AT+QENG="servingcell" to check the currently connected cell and its associated band info.

echo -ne "AT+QENG=\"servingcell\"\r\n" | microcom -X -t 1000 /dev/ttyUSB2

hazarjast wrote: Tue Oct 05, 2021 1:07 pmAs mentioned in the previous point 'AT+QCAINFO' will give you the last reported carrier aggregation status of the modem, which is not necessarily the same as the current connected cell and band info (i.e. 'AT+QENG="servingcell"').

hazarjast wrote: Tue Oct 05, 2021 1:07 pmCell locking is definitely not reboot persistent so either there is a specific bug with B1 locking in the Quectel firmware you are on, or (more likely) the firmware algorithm, which is mostly based on preferring the strongest signal available, has preferred B1 even after the lock was removed.

hazarjast wrote: Tue Oct 05, 2021 1:07 pmHowever, if you put the time in and are able to successfully configure the LBR20 for split-tunnel VPN routing, I'm certain more than a few other LBR20 owners would be indebted to you for posting your configuration detail/tutorial for the same

das1996 wrote: Fri Oct 22, 2021 6:28 pm I've been out of touch for a while. Glad to see more progress made.

Question; there is no option in the GUI to disable wifi. Is it possible to do so through console? Negative side effects?

das1996 wrote: Thu Nov 18, 2021 7:15 pm @hazarjast How do i send you a private message?

das1996 wrote: Thu Nov 18, 2021 7:15 pm @hazarjast How do i send you a private message?

Didneywhorl wrote: Sun Nov 21, 2021 1:25 pm I wonder if this would help in general with IP tables TTL/HL rules used on openWRT