New to forum. Currently using a mofi4500

[Yipzy]

Thanks to both of you for that. Yipzy I checked that post but it's all for AT&T and mine is with Verizon. I still can't figure out why all the sudden it won't CA with the other bands B2, B5, B13 that it was before. I know the towers and the modem will do it because it was doing it before. Will the deprioritization make that happen?

Unlikely. Maybe the modem prefers B66 to CA with the second B66. You would have to disable B66 if you want it to CA with other bands if speeds are better or try to do multiple speed tests to see if B66 will CA with other bands. Your modem supports 3CA but according to the CA Combos list I linked, it won't CA another band when CA is active with B66+B66.

[BigMac79]

Unlikely. Maybe the modem prefers B66 to CA with the second B66. You would have to disable B66 if you want it to CA with other bands if speeds are better or try to do multiple speed tests to see if B66 will CA with other bands. Your modem supports 3CA but according to the CA Combos list I linked, it won't CA another band when CA is active with B66+B66.

OK so I've ran the code to include B2, B5 and B13 and left out B66. The CA is working as it's went from B2 to B2+B5 during the same 10 minute period. Maybe it just likes B66 now for some reason. The numbers aren't that different than with B66. Signal is a bit better but the other numbers are about the same. I'll see how this works and if it ever goes back to B13 as it was my best band by far.

E728F8D9-4085-4562-906F-C43260FFEE68.jpeg

[Yipzy]

OK so I've ran the code to include B2, B5 and B13 and left out B66. The CA is working as it's went from B2 to B2+B5 during the same 10 minute period. Maybe it just likes B66 now for some reason. The numbers aren't that different than with B66. Signal is a bit better but the other numbers are about the same. I'll see how this works and if it ever goes back to B13 as it was my best band by far.

Try to disable B66 and B5 but enable B2, B4, and B13.

[BigMac79]

Try to disable B66 and B5 but enable B2, B4, and B13.

I don’t know how to disable. Is it just not including it in the command? AT+QCFG="band",0,1002,1 (for B2+B13)

[Yipzy]

I don’t know how to disable. Is it just not including it in the command? AT+QCFG="band",0,1002,1 (for B2+B13)

Correct but add Band 4 which is 8 so

Code: Select all

AT+QCFG="band",0,100a,1

[Jwilliams54]

How do you change the ttl settings to stop throttling? I have a Verizon hotspot with 15gb as well. But that’s our only internet, we desperately need more, or some unlimited, unthrottled. Also looked into Unlimitedville, I’m desperate for help as we have 2 remote working adults and 2 virtual learning children’s at home right now. Thank you!!

[Yipzy]

How do you change the ttl settings to stop throttling? I have a Verizon hotspot with 15gb as well. But that’s our only internet, we desperately need more, or some unlimited, unthrottled. Also looked into Unlimitedville, I’m desperate for help as we have 2 remote working adults and 2 virtual learning children’s at home right now. Thank you!!

Do you have a router to connect the hotspot to via USB? Normally hotspots won't allow you to change that kind of settings.

[BigMac79]

Correct but add Band 4 which is 8 so

Code: Select all

AT+QCFG="band",0,100a,1

Forgot about B4! Ran it and noticed CA between B2, B5 & B13 for a minute then switched to just B2. But, speeds are ok. I'll check again in the morning during my normal "deprioritization" period and see if it helps. Wondering if a VPN on the WG3526 would help........

[Yipzy]

Wondering if a VPN on the WG3526 would help........

If you are deprioritized, VPN won't help. Changing to another tower nearby will if it's not congested like yours.

[BigMac79]

If you are deprioritized, VPN won't help. Changing to another tower nearby will if it's not congested like yours.

So I've ran speed tests and checked the modem several times today and especially during my normal deprioritization periods. Seems to be working great by removing B66 from the rotation. I've generally been on B13 and have speeds in the 25-40mbps down and 10-18mbps up. So, looks like this is working. Big thanks for all the guidance. Hopefully it will stay like this.

[Yipzy]

So I've ran speed tests and checked the modem several times today and especially during my normal deprioritization periods. Seems to be working great by removing B66 from the rotation. I've generally been on B13 and have speeds in the 25-40mbps down and 10-18mbps up. So, looks like this is working. Big thanks for all the guidance. Hopefully it will stay like this.

Good to hear. I just find that odd because B13 is Verizon's main band. Normally that band is more congested than others.

[BigMac79]

Good to hear. I just find that odd because B13 is Verizon's main band. Normally that band is more congested than others.

Even before I started messing with the settings ga it was my best performing band. Could be because I’m pretty rural here. Also, the signal for AT&T, Verizon and Sprint literally change from one house to the next. My neighbor behind me (1000 yards) has 4G AT&T and I can barely get a bar. The other direction my neighbors can’t get Verizon or AT&T but blaze on Sprjnt whereas I get 2 bars. Could be the B13 isn’t used by too many people here (if that’s how it works).

[Yipzy]

Could be the B13 isn’t used by too many people here (if that’s how it works).

That should be it. B13 travels farther so you get better signal as well.

[BigMac79]

So even with TTL set to 117 and the DNS settings (using cloudfare) I’m still “bleeding” through a bit of Hotspot data vs 100% device data. Is this normal or do I need to change something else?

Hotspot data showing about 1GB of increase every couple days vs. device data of about 3GB. I’m throttled to 600kbps so not using much now.

[Yipzy]

So even with TTL set to 117 and the DNS settings (using cloudfare) I’m still “bleeding” through a bit of Hotspot data vs 100% device data. Is this normal or do I need to change something else?

Hotspot data showing about 1GB of increase every couple days vs. device data of about 3GB. I’m throttled to 600kbps so not using much now.

It's not normal. I had TTL 65 on mine. Ping your router's ip and if it doesn't return 65. Increase to 66 or 67. Make sure you do for both ipv4 and ipv6.

[BigMac79]

It's not normal. I had TTL 65 on mine. Ping your router's ip and if it doesn't return 65. Increase to 66 or 67. Make sure you do for both ipv4 and ipv6.

I have Verizon does that change your recommendation?

I’ll have to figure out how to Ping the router. Yeah, totally new to this I know but I’m learning.

[BigMac79]

Figured out how to Ping from my MAC. Came back 64. Not sure why since I’ve changed TTL to 117 and router shows 117 for ipv4 and ipv6.

[BigMac79]

It's not normal. I had TTL 65 on mine. Ping your router's ip and if it doesn't return 65. Increase to 66 or 67. Make sure you do for both ipv4 and ipv6.

I tried changing the TTL and Custom Rules to 65, 66 and 67 and the ping comes back 64 every time. I rebooted after each change also. Any thoughts?

[Yipzy]

Figured out how to Ping from my MAC. Came back 64. Not sure why since I’ve changed TTL to 117 and router shows 117 for ipv4 and ipv6.

Then the settings aren't being applied. Try to restart the router.

[Yipzy]

I tried changing the TTL and Custom Rules to 65, 66 and 67 and the ping comes back 64 every time. I rebooted after each change also. Any thoughts?

Paste your settings here. Are you tethering with a hotspot/phone or using a modem inside the router?

[BigMac79]

Paste your settings here. Are you tethering with a hotspot/phone or using a modem inside the router?

Using WG3526P with EM12 modem and Verizon sim. Originally I was using TTL 117 and thought it was working.

Custom Rules:
#start TTL rules
iptables -t mangle -I POSTROUTING -o wwan0 -j TTL --ttl-set 67
iptables -t mangle -I PREROUTING -i wwan0 -j TTL --ttl-set 67
#ip6tables -t mangle -I POSTROUTING -o wwan0 -j HL --hl-set 67
#ip6tables -t mangle -I PREROUTING -i wwan0 -j HL --hl-set 67
#end TTL rules

DNS:
Custom DNS Server1: 1.1.1.1
Custom DNS Server2: 1.0.0.1
Custom DNS Server3: 2606:4700:4700::1111
Custom DNS Server4: 2606:4700:4700::1001

[Yipzy]

Using WG3526P with EM12 modem and Verizon sim. Originally I was using TTL 117 and thought it was working.

#ip6tables -t mangle -I POSTROUTING -o wwan0 -j HL --hl-set 67
#ip6tables -t mangle -I PREROUTING -i wwan0 -j HL --hl-set 67

Uncomment those 2 lines should fix your problem.

[BigMac79]

Uncomment those 2 lines should fix your problem.

By "uncomment" you mean remove the '#' before it? If so, I did that, rebooted and still get a TTL64 when I ping it.

[Yipzy]

By "uncomment" you mean remove the '#' before it? If so, I did that, rebooted and still get a TTL64 when I ping it.

Yeah. Maybe your network interface wwan0 is incorrect. Go to Network -> Interfaces and see what does it say in the WAN1 plug box?

[BigMac79]

Yeah. Maybe your network interface wwan0 is incorrect. Go to Network -> Interfaces and see what does it say in the WAN1 plug box?

Here's what WAN1 has for IPv:
Protocol: MBIM
IPv4: 100.118.188.93/32
IPv6: 2600b0524d96:9702:e156:535f/128
IPv6-PD: 2600b0524d96:9702:e156:535f/64

[Yipzy]

Here's what WAN1 has for IPv:
Protocol: MBIM

It should be just a word right under WAN1 and the plug icon.

[BigMac79]

It should be just a word right under WAN1 and the plug icon.

Apologies, it says "wwan0"

[Yipzy]

Apologies, it says "wwan0"

Hm. That's the correct interface that goes with your settings. Not sure why the router is not applying them properly. Do you have TTL enabled? Try to uncheck it but make sure those 4 lines are in custom rules then apply and reboot.

[BigMac79]

Do you have TTL enabled? Try to uncheck it but make sure those 4 lines are in custom rules then apply and reboot.

I unchecked Enable TTL, hit save/apply, verified Custom Rules still good and then rebooted. Still ping as TTL 64
I rechecked enable TTL, hit save/apply, verified Custom Rules still good and then rebooted. Still ping as TTL 64

From my terminal after running ping:
icmp_seq=11 ttl=64 time=18.553 ms
icmp_seq=12 ttl=64 time=8.578 ms

[Yipzy]

I unchecked Enable TTL, hit save/apply, verified Custom Rules still good and then rebooted. Still ping as TTL 64
I rechecked enable TTL, hit save/apply, verified Custom Rules still good and then rebooted. Still ping as TTL 64

From my terminal after running ping:
icmp_seq=11 ttl=64 time=18.553 ms
icmp_seq=12 ttl=64 time=8.578 ms

So increasing the TTL to even 68, 69, 70 or 117 had no effect? Are you running GoldenOrb/ROOTer?

[BigMac79]

So increasing the TTL to even 68, 69, 70 or 117 had no effect? Are you running GoldenOrb/ROOTer?

Correct, no effect.

Yes. running GoldenOrb_2020-05-16

[Yipzy]

Yes. running GoldenOrb_2020-05-16

Do you see your custom rules via

Code: Select all

cat /etc/firewall.user

in terminal? If so, type

Code: Select all

/etc/init.d/firewall restart

Does it say "* Running script '/etc/firewall.user'" at the end of the process?

[BigMac79]

Do you see your custom rules via

Code: Select all

cat /etc/firewall.user

in terminal?

Would I see this in the AT-Command Execution (modem debug information) section? If so, I don't see anything in there with this information.

The "terminal" I referenced for my ping was the terminal on my Mac Book. I didn't see that code in there either.

[Yipzy]

Would I see this in the AT-Command Execution (modem debug information) section? If so, I don't see anything in there with this information.

The "terminal" I referenced for my ping was the terminal on my Mac Book. I didn't see that code in there either.

I'm not sure. I haven't been using LTE router for awhile so I can't check. I was talking about the terminal access from your router which you could access by type ssh root@your.router.ip via your MAC's terminal.

[BigMac79]

type ssh root@your.router.ip via your MAC's terminal.

When I type that in this is what appears in my terminal:

319BB77E-236B-40BE-A127-4ADE9D97F89E_4_5005_c.jpeg

And this is what shows when enter cat /etc/firewall.user

#start TTL rules
iptables -t mangle -I POSTROUTING -o wwan0 -j TTL --ttl-set 117
iptables -t mangle -I PREROUTING -i wwan0 -j TTL --ttl-set 117
ip6tables -t mangle -I POSTROUTING -o wwan0 -j HL --hl-set 117
ip6tables -t mangle -I PREROUTING -i wwan0 -j HL --hl-set 117
#end TTL rules

[BigMac79]

If so, type

Code: Select all

/etc/init.d/firewall restart

Does it say "* Running script '/etc/firewall.user'" at the end of the process?

This is what is shows when I run this.
root@WiFiX:~# /etc/init.d/firewall restart
Warning: Section @zone[1] (wan) cannot resolve device of network 'wwan'
* Flushing IPv4 filter table
* Flushing IPv4 nat table
* Flushing IPv4 mangle table
* Flushing IPv6 filter table
* Flushing IPv6 mangle table
* Flushing conntrack table ...
* Populating IPv4 filter table
* Rule 'Allow-DHCP-Renew'
* Rule 'Allow-Ping'
* Rule 'Allow-IGMP'
* Rule 'Allow-IPSec-ESP'
* Rule 'Allow-ISAKMP'
* Forward 'lan' -> 'wan'
* Forward 'lan' -> 'VPN'
* Forward 'lan' -> 'VPNS'
* Zone 'lan'
* Zone 'wan'
* Zone 'VPN'
* Zone 'VPNS'
* Populating IPv4 nat table
* Zone 'lan'
* Zone 'wan'
* Zone 'VPN'
* Zone 'VPNS'
* Populating IPv4 mangle table
* Zone 'lan'
* Zone 'wan'
* Zone 'VPN'
* Zone 'VPNS'
* Populating IPv6 filter table
* Rule 'Allow-DHCPv6'
* Rule 'Allow-MLD'
* Rule 'Allow-ICMPv6-Input'
* Rule 'Allow-ICMPv6-Forward'
* Rule 'Allow-IPSec-ESP'
* Rule 'Allow-ISAKMP'
* Forward 'lan' -> 'wan'
* Forward 'lan' -> 'VPN'
* Forward 'lan' -> 'VPNS'
* Zone 'lan'
* Zone 'wan'
* Zone 'VPN'
* Zone 'VPNS'
* Populating IPv6 mangle table
* Zone 'lan'
* Zone 'wan'
* Zone 'VPN'
* Zone 'VPNS'
* Set tcp_ecn to off
* Set tcp_syncookies to on
* Set tcp_window_scaling to on
* Running script '/etc/firewall.user'
Bad argument `POSTROUTING'
Try `iptables -h' or 'iptables --help' for more information.
Bad argument `PREROUTING'
Try `iptables -h' or 'iptables --help' for more information.
Bad argument `POSTROUTING'
Try `ip6tables -h' or 'ip6tables --help' for more information.
Bad argument `PREROUTING'
Try `ip6tables -h' or 'ip6tables --help' for more information.
! Failed with exit code 2

[Yipzy]

And this is what shows when enter cat /etc/firewall.user

#start TTL rules
iptables -t mangle -I POSTROUTING -o wwan0 -j TTL --ttl-set 117
iptables -t mangle -I PREROUTING -i wwan0 -j TTL --ttl-set 117
ip6tables -t mangle -I POSTROUTING -o wwan0 -j HL --hl-set 117
ip6tables -t mangle -I PREROUTING -i wwan0 -j HL --hl-set 117
#end TTL rules

What about the other command? Does it run /etc/firewall.user through it? When you set TTL 117, you shouldn't be getting TTL 64 as a response though.

EDIT: Your firewall isn't working properly applying your custom rules that's why TTL is not set. Try to flash to a previous version of WiFiX or curren if possible via https://wirelessjoint.com/viewtopic.php?f=12&t=5 and redo the settings. If you don't need the extra custom settings from WiFiX. Use the firmware from https://ofmodemsandmen.com/firmware.html

Bad argument `POSTROUTING'
Try `iptables -h' or 'iptables --help' for more information.
Bad argument `PREROUTING'
Try `iptables -h' or 'iptables --help' for more information.
Bad argument `POSTROUTING'
Try `ip6tables -h' or 'ip6tables --help' for more information.
Bad argument `PREROUTING'
Try `ip6tables -h' or 'ip6tables --help' for more information.
! Failed with exit code 2

[BigMac79]

What about the other command? Does it run /etc/firewall.user through it?

When I run this from the current session in the terminal I get this response:

root@WiFiX:~# /etc/firewall.user
-ash: /etc/firewall.user: Permission denied

[Yipzy]

When I run this from the current session in the terminal I get this response:

root@WiFiX:~# /etc/firewall.user
-ash: /etc/firewall.user: Permission denied

That's just a path to the file. You need to issue a command before it to let it know what you want to do with it. Like cat to paste file content.

[BigMac79]

That's just a path to the file. You need to issue a command before it to let it know what you want to do with it. Like cat to paste file content.

When I run it I get this in return. Exactly as is written in WiFix.
# This file is interpreted as shell script.
# Put your custom iptables rules here, they will
# be executed with each firewall (re-)start.

# Internal uci firewall chains are flushed and recreated on reload, so
# put custom rules into the root chains e.g. INPUT or FORWARD or into the
# special user chains, e.g. input_wan_rule or postrouting_lan_rule.
#start TTL rules
iptables -t mangle -I POSTROUTING -o wwan0 -j TTL --ttl-set 117
iptables -t mangle -I PREROUTING -i wwan0 -j TTL --ttl-set 117
ip6tables -t mangle -I POSTROUTING -o wwan0 -j HL --hl-set 117
ip6tables -t mangle -I PREROUTING -i wwan0 -j HL --hl-set 117
#end TTL rules

[Yipzy]

When I run it I get this in return. Exactly as is written in WiFix.
# This file is interpreted as shell script.
# Put your custom iptables rules here, they will
# be executed with each firewall (re-)start.

# Internal uci firewall chains are flushed and recreated on reload, so
# put custom rules into the root chains e.g. INPUT or FORWARD or into the
# special user chains, e.g. input_wan_rule or postrouting_lan_rule.
#start TTL rules
iptables -t mangle -I POSTROUTING -o wwan0 -j TTL --ttl-set 117
iptables -t mangle -I PREROUTING -i wwan0 -j TTL --ttl-set 117
ip6tables -t mangle -I POSTROUTING -o wwan0 -j HL --hl-set 117
ip6tables -t mangle -I PREROUTING -i wwan0 -j HL --hl-set 117
#end TTL rules

Check my previous post. Your custom settings aren't being applied because iptables isn't configured properly. Best is to reflash or flash to a previous version of firmware than current and restore your backed up settings. When you run the second command line, it gives out errors at the end regarding your custom settings.

[BigMac79]

Check my previous post. Your custom settings aren't being applied because iptables isn't configured properly. Best is to reflash or flash to a previous version of firmware than current and restore your backed up settings. When you run the second command line, it gives out errors at the end regarding your custom settings.

Thanks for the help! I will try to find the version before the one I have and see if I can flash to it. I've only had to do this once when I set it up so it's not something I'm thrilled about. But if it works that's all that matters.

Just for my learning, you can not just retype in the custom settings for the iptables with the correct configuration? I was the one that typed in the one's that are shown in the Custom Rules section.

[Yipzy]

Just for my learning, you can not just retype in the custom settings for the iptables with the correct configuration? I was the one that typed in the one's that are shown in the Custom Rules section.

Your custom settings are right. It's the iptables applying the settings. If you are feeling adventurous, look up how to fix it with the those error lines.

[BigMac79]

You custom settings are right. It's the iptables applying the settings. If you are feeling adventurous, look up how to fix it with the those error lines.

OK. So found different iptables rules in another post I've been following for a Visible sim https://wirelessjoint.com/viewtopic.php?p=11873#p11873. I noticed there was a slight change in the custom rules so I redid it and this is what I now get when I run the codes in the terminal. No error messages but still pings 64 after a reboot.

#start TTL rules7
iptables -t mangle -I POSTROUTING -o wwan0 -j TTL --ttl-set 117
iptables -t mangle -I PREROUTING -i wwan0 -j TTL --ttl-set 117
ip6tables -t mangle -A POSTROUTING -o wwan0 -j HL --hl-set 117
ip6tables -t mangle -I PREROUTING -i wwan0 -j HL --hl-set 117
#end TTL rules

root@WiFiX:~# /etc/init.d/firewall restart
Warning: Section @zone[1] (wan) cannot resolve device of network 'wwan'
* Flushing IPv4 filter table
* Flushing IPv4 nat table
* Flushing IPv4 mangle table
* Flushing IPv6 filter table
* Flushing IPv6 mangle table
* Flushing conntrack table ...
* Populating IPv4 filter table
* Rule 'Allow-DHCP-Renew'
* Rule 'Allow-Ping'
* Rule 'Allow-IGMP'
* Rule 'Allow-IPSec-ESP'
* Rule 'Allow-ISAKMP'
* Forward 'lan' -> 'wan'
* Forward 'lan' -> 'VPN'
* Forward 'lan' -> 'VPNS'
* Zone 'lan'
* Zone 'wan'
* Zone 'VPN'
* Zone 'VPNS'
* Populating IPv4 nat table
* Zone 'lan'
* Zone 'wan'
* Zone 'VPN'
* Zone 'VPNS'
* Populating IPv4 mangle table
* Zone 'lan'
* Zone 'wan'
* Zone 'VPN'
* Zone 'VPNS'
* Populating IPv6 filter table
* Rule 'Allow-DHCPv6'
* Rule 'Allow-MLD'
* Rule 'Allow-ICMPv6-Input'
* Rule 'Allow-ICMPv6-Forward'
* Rule 'Allow-IPSec-ESP'
* Rule 'Allow-ISAKMP'
* Forward 'lan' -> 'wan'
* Forward 'lan' -> 'VPN'
* Forward 'lan' -> 'VPNS'
* Zone 'lan'
* Zone 'wan'
* Zone 'VPN'
* Zone 'VPNS'
* Populating IPv6 mangle table
* Zone 'lan'
* Zone 'wan'
* Zone 'VPN'
* Zone 'VPNS'
* Set tcp_ecn to off
* Set tcp_syncookies to on
* Set tcp_window_scaling to on
* Running script '/etc/firewall.user'

Do you still think I need to reflash with another version given there are no errors?

[Yipzy]

Do you still think I need to reflash with another version given there are no errors?

Has the TTL respond with different number other than 64 after reboot?

[BigMac79]

Has the TTL respond with different number other than 64 after reboot?

No. Still 64. I can re-run through the different TTL settings and try to uncheck the enable ttl like we did before. But if that doesn't work then it's a reflash I'm guessing.

[Yipzy]

I would imagine so if others didn't have problem with it. It's also the reason you are leaking hotspot data.

[BigMac79]

I would imagine so if others didn't have problem with it. It's also the reason you are leaking hotspot data.

OK. So here's the update so that maybe it can help someone else. I did not have to reflash. What I did have to do was some trial and error with my custom rules thanks to some posts on this site and the FB site. These custom rules below now have me pinging ttl 117 with no errors in my iptables/ip6tables when I run <root@WiFiX:~# /etc/init.d/firewall restart> like I was getting before.

Most importantly I've also completely stopped leaking hotspot data since I inserted the new custom rules and had no impact to performance. Thanks for all the help and guidance and others on the sites who have unknowingly contributed. Here's the custom rules:

#start TTL rules
iptables -t mangle -I POSTROUTING -j TTL --ttl-set 117
iptables -t mangle -I PREROUTING -j TTL --ttl-set 117
ip6tables -t mangle -A POSTROUTING -o wwan0 -j HL --hl-set 117
ip6tables -t mangle -I PREROUTING -i wwan0 -j HL --hl-set 117
#end TTL rules

Note: Running WG3526P, EM12G modem on Verizon.

[Yipzy]

Most importantly I've also completely stopped leaking hotspot data since I inserted the new custom rules and had no impact to performance. Thanks for all the help and guidance and others on the sites who have unknowingly contributed. Here's the custom rules:

That's awesome! Thanks for the update.

[gscheb]

Benn able to do this in the past with my Verizon phone sim in a Quectel EP06. But for some reason couldn't get this to work on a EM12G. Don't know why, odd Especially since bigmac79 got it to work.

[BigMac79]

Benn able to do this in the past with my Verizon phone sim in a Quectel EP06. But for some reason couldn't get this to work on a EM12G. Don't know why, odd Especially since bigmac79 got it to work.

It was a lot of help and trial and error. Happy to share my settings if it helps you any.

[Dr-BroadBand]

Need Antennas!!
There is hope, See the following YouTube

https://youtu.be/xzqkoPL9t9A
https://youtu.be/73jEQgihpso
https://youtu.be/kFsYem_7eZg