Wireless Joint

EM12-G modem in a WG3526 using a Verizon unlimited plan running GoldenOrb. This has been working for the last 9 months (besides minor interruptions and reboots). Now, it says I am connected but I have no internet. I've removed the APN, rebooted and replaced the APN several times and same result. I ...

I've searched the forums and haven't been able to find anything that would address this specific issue. I have a WG3526 with E-12G on a Verizon unlimited card. I have no issues utilizing only 'unlimited data' with all my devices (phones, TV, laptops, etc.) and utilize 0mb of Hotspot data.

However ...

gscheb wrote: Wed Sep 16, 2020 1:56 pm 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.

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 ...

Yipzy wrote: Tue Sep 08, 2020 4:36 pm 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.

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 ...

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 ...

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 ...

Yipzy wrote: Tue Sep 08, 2020 3:20 pm 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

If so, type /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 ...

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 ...

Do you see your custom rules via 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 ...

Yipzy wrote: Tue Sep 08, 2020 1:48 pm 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

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 ...

Yipzy wrote: Tue Sep 08, 2020 10:48 am It should be just a word right under WAN1 and the plug icon.

Apologies, it says "wwan0"

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: 2600:100d:b052:1ec8:4d96:9702:e156:535f/128
IPv6-PD: 2600:100d:b052:1ec8:4d96:9702:e156 ...

Yipzy wrote: Mon Sep 07, 2020 10:36 pm 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.

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 ...

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 ...

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.

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 ...

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 ...

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 ...

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 ...

Correct but add Band 4 which is 8 so 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 ...

Yipzy wrote: Tue Sep 01, 2020 8:02 pm 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)

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 ...

Check my post here for CA Combos on EM12-G. https://wirelessjoint.com/viewtopic.php?f=15&t=840&p=10594#p10594

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 ...

gscheb wrote: Tue Sep 01, 2020 5:11 pm I know in the past if my primary band is band 2 (15 mhz) CA with band 12 (5mhz). Speeds are allot faster if that scenario is switched around. That is what I am talking about.

I know how to select the bands I want but how do you tell it to pick one before the other (a primary and a CA one)?

Your settings are fine. This is the classic deprioritization. You can't really do anything except changing provider or force it to connect to another uncongested tower nearby if your modem supports it. You could manually band lock one by one band to see which band will let you have full speed but ...

Your tower is likely congested. You should have your normal speeds after off-peak hours no? You could just test each band when you see slow down in speeds and if all bands provide the same result then you are being deprioritized and not cause by band locking any particular band. It's doing CA with ...

Yipzy wrote: Tue Sep 01, 2020 2:45 pm It's aggregating with another 15 Mhz so it shouldn't be only when it's not doing the CA so he just needs to test each band individually.

How do I go about testing each band individually? is it using the AT+QCFG="band",0,<band #>,1 and just insert each band individually?

Did you try AT+QCFG="band",0,2000001e0bb1e39df,1 ?

Every since I've ran this the modem will only lock onto Band 66 for some reason. Before as you could see in previous post it was constantly switching to 13, 2, 5 or 66. I seem to be getting deprioritized (it's not all the time that I'm ...

Has anyone had any luck with the Verizon post paid? I don't want to get stuck in a two year contract if it will not work.

I have $65 Do More Unlimited post paid Verizon plan. Using a WP3526 with EM-12 modem. The phone SIM has worked fine for me after some tweaking of the settings. I’m now into ...

Thanks again! So now just trying to understand the code (for my knowledge on how it works).
20000000000000000 = band 66
1000 = Band 13
2 = Band 2
10 = Band 5

So you literally combine them to get to the band you want

1000 + 2 = 1002 for Bands 13 and 2
1000 + 10 = 1010 for Bands 13 and 5 ...

I didn't try it by replacing the <0x0> with the <1>. Just did that and it accepted it. Thank you! This is all new to me so trying to figure it out. Really appreciate the quick response. Now to figure out how to aggregate 13 and 66 my best two bands and avoid 5 and 2.

I think this https://wirelessjoint.com/viewtopic.php?f=16&t=943 is what you are looking for. When you type the first command I posted, it will respond with the default configuration. You then just need to type second command and replace the middle number 1002 with the long string with omitted 0x ...

Problem solved thanks to FB Wireless Joint. Resolution: Change TTL to 117 -> Reboot -> Delete APN (leave it blank) -> Reboot -> Add back in APN -> Reboot = Connected. Strange but worked.

Then, relocate working router and spend 30 minutes trying to figure out that you have to repeat the process ...

Hello All. I'm very new to this and have no technical experience. With that disclaimer out the way this is what I have.

New WG3526P with WiFix/Goldenorb firmware, Quectel EM12-G modem, mini PCie to M.2 adapter and pigtails. I've installed in the modem (not external slot on router though I've tried ...

Search found 39 matches