Dropping connection

Post by **Dubbzy** » Wed Jun 21, 2023 5:46 am

Hi all,

I've had an ongoing issue with my EM9191 since I purchased it. I got the NEXS2GO as well I believe, and have been plagued with slowdowns and disconnects.

Using the Quanta 5g modem Calyx provided me with my plan, I've had less issues from the NEXS2GO, but ultimately ended up using a GliNet Flint router. Since then, no problems.

I acquired a tablet plan from t-mobile, so I decided to use the EM9191 for my laptop. However, even connected directly to my Windows Lptop, it will just randomly disconnect. I have no idea what is causing this. Do I have a faulty unit? Shortly after I received the EM9191, the LEDs stopped functioning. No idea if that has any bearing on anything. I'll be glad to supply whatever log files might be necessary, just let me know how to procure them!

Post by **Didneywhorl** » Wed Jun 21, 2023 7:01 am

Is the modem itself rebooting, or is the connection to the cell network dropping, but modem still present?

The Modem Connection Logs should show this.

Post by **Dubbzy** » Sat Jun 24, 2023 10:27 pm

Didneywhorl wrote: Wed Jun 21, 2023 7:01 am Is the modem itself rebooting, or is the connection to the cell network dropping, but modem still present?

The Modem Connection Logs should show this.

I'm not entirely certain how I can access these via Windows, but from what I can tell, the modem is staying connected, but will not show a connection to a network.

On my PC, I have it plugged in, it shows the cellular connection full, but I have to go to my network list and tell it to "connect". I can have Windows manage this by having it auto connect as needed, though I still know when it drops because it takes a bit for that process to happen it seems.

I have tested with forgetting my other wireless network in the house, and there is no Ethernet connection. Yet still intermittently I will not be able to navigate further on a webpage and I will pull up the network options, and sure enough, there it is telling me to connect again. Bear in mind I still have my Calyx network Quanta hooked up to a GliNet Flint and that network will not be having any issues during this time.

Post by **Dubbzy** » Thu Jul 13, 2023 2:22 pm

Any ideas as to why the modem will just drop out?

Is there something I can run to gather logs to monitor it?

Post by **Didneywhorl** » Fri Jul 14, 2023 7:42 am

Unfortunately I don't think Windows logs cell connections.
Have you tried using a powered USB hub with it? The EM9191 is known to be power hungry, causing the actual voltage to drop below levels that trigger reboots. Most USB ports aren't well regulated as they aren't really made for heavy power use like these modems use.

Try a powered usb hub that outputs 5.0-5.25VDC. Under 5.0VDC works, but may drop too low under load.

Post by **Dubbzy** » Sun Jul 30, 2023 4:04 pm

Didneywhorl wrote: Fri Jul 14, 2023 7:42 am Unfortunately I don't think Windows logs cell connections.
Have you tried using a powered USB hub with it? The EM9191 is known to be power hungry, causing the actual voltage to drop below levels that trigger reboots. Most USB ports aren't well regulated as they aren't really made for heavy power use like these modems use.

Try a powered usb hub that outputs 5.0-5.25VDC. Under 5.0VDC works, but may drop too low under load.

Would keeping it plugged in via the optional micro USB help with the power load?

That's currently how I've had it: USB 3.0 cable going to powered USB on laptop, and micro USB going to power supply in outlet.

Post by **Didneywhorl** » Sun Jul 30, 2023 6:58 pm

It should but it didn't help in my tests. Seems to supply extra amps, but doesn't bolster the voltage level

Post by **Dubbzy** » Sun Jul 30, 2023 7:05 pm

What about using like an adapter to covert to USB-C from micro-b, then using a power delivery port on my laptop for a connection?

Or would I just be better served getting a powered adapter?

Would this work? or do you have a recommendation for something that would work?

Post by **Didneywhorl** » Mon Jul 31, 2023 8:09 am

You could try either, or both.

Just needs to provide a solid 5+ volts.

Post by **Dubbzy** » Mon Jul 31, 2023 10:18 am

So. A little after I first received the unit, the LED stopped working.

Is it possible that there is some sort of internal damage that is causing power supply issues?

Can I check the volts/amps being received via the command terminal somehow?

Post by **Dubbzy** » Mon Jul 31, 2023 11:34 am

Didneywhorl wrote: Wed Jun 21, 2023 7:01 am Is the modem itself rebooting, or is the connection to the cell network dropping, but modem still present?

The Modem Connection Logs should show this.

Alright. I checked Windows Event Viewer when it disconnected the internet again. I've attached the line items around the time it happened. Hoping this sheds some light, I'm not entirely certain what I am looking at here.

I also have the NEXS2GO from you guys. Essentially the same thing would happen with it, I would just have random dropouts.

If I connected that back up, does it supply enough power? Would the NEXS2GO support a powered USB hub to help facilitate proper power delivery?

Will it provide better logs to be able to know what is going on? Really tempted to get the Invisagig, though this equipment was already the same cost and just not working properly.

Post by **Didneywhorl** » Mon Jul 31, 2023 5:39 pm

Show me a picture of the NEXS2GO router label (black out the MAC addr numbers and barcodes)

Post by **Dubbzy** » Mon Jul 31, 2023 5:45 pm

Here you go

Post by **Didneywhorl** » Tue Aug 01, 2023 8:46 am

Yep, that one should have plenty of USB voltage output.

Get a USB volt tester from amazon and you can see the output: https://amzn.to/3qeGo1k

Post by **Dubbzy** » Wed Aug 02, 2023 10:23 am

Preliminary testing seems like this has resolved being connected straight to my PC.

Will the NEXS2GO recognize the passthrough from this hub?

Do you think that this is what was causing my issues on the NEXS2GO as well?

Post by **Didneywhorl** » Wed Aug 02, 2023 2:26 pm

It should see it fine on the hub, as all USB kind of works like a hub, called a 'bus'.

Depends on if the modem is actually power cycling under load. You have to also ensure there are not goofy watchdongs turned on in the firmware (two potential places), but it should show up in the modem logging/connection logging.

Post by **Dubbzy** » Thu Aug 03, 2023 3:02 am

NEXS2GO will not recognize the modem when it is behind the hub.

I'm attaching different log files from the NEXS2GO.

What I did was flashed it to the latest firmware, WiFiX-NEXS2GO-GO2023-01-12, then hooked up the modem. First through the hub, no dice.

Direct to NEXS2GO, internet seems to be working, until it just stops. Persists beyond a restart of equipment.

I don't know what is causing the issue here.

Post by **Didneywhorl** » Thu Aug 03, 2023 9:04 am

If plugging it in directly works, but not through the hub, you may have a faulty hub.

I use one similar to this : https://amzn.to/3rVjQDe

The logs show this part that jumps out at me:

Thu Aug 3 02:49:20 2023 daemon.notice netifd: Interface 'CLAT1' is setting up now
Thu Aug 3 02:49:20 2023 user.notice URL-DEBUG: hotplug (iface): action='ifup-failed' interface='CLAT1'
Thu Aug 3 02:49:23 2023 user.info mwan3track[13087]: Check (httping) failed for target "1.1.1.1" on interface wan1 (wwan0). Current score: 7
Thu Aug 3 02:49:24 2023 daemon.notice netifd: Interface 'CLAT1' is now down
Thu Aug 3 02:49:24 2023 daemon.notice netifd: Interface 'CLAT1' is setting up now
Thu Aug 3 02:49:24 2023 user.notice URL-DEBUG: hotplug (iface): action='ifup-failed' interface='CLAT1'
Thu Aug 3 02:49:27 2023 daemon.notice netifd: Interface 'CLAT1' is now down
Thu Aug 3 02:49:27 2023 daemon.notice netifd: Interface 'CLAT1' is setting up now
Thu Aug 3 02:49:27 2023 user.notice URL-DEBUG: hotplug (iface): action='ifup-failed' interface='CLAT1'
Thu Aug 3 02:49:28 2023 user.info mwan3track[13087]: Check (httping) failed for target "1.0.0.1" on interface wan1 (wwan0). Current score: 7
Thu Aug 3 02:49:30 2023 daemon.notice netifd: Interface 'CLAT1' is now down
Thu Aug 3 02:49:30 2023 daemon.notice netifd: Interface 'CLAT1' is setting up now
Thu Aug 3 02:49:30 2023 user.notice URL-DEBUG: hotplug (iface): action='ifup-failed' interface='CLAT1'
Thu Aug 3 02:49:33 2023 daemon.notice netifd: Interface 'CLAT1' is now down
Thu Aug 3 02:49:33 2023 daemon.notice netifd: Interface 'CLAT1' is setting up now
Thu Aug 3 02:49:33 2023 user.notice URL-DEBUG: hotplug (iface): action='ifup-failed' interface='CLAT1'
Thu Aug 3 02:49:33 2023 user.info mwan3track[13087]: Check (httping) failed for target "8.8.8.8" on interface wan1 (wwan0). Current score: 7
Thu Aug 3 02:49:36 2023 daemon.notice netifd: Interface 'CLAT1' is now down
Thu Aug 3 02:49:36 2023 daemon.notice netifd: Interface 'CLAT1' is setting up now
Thu Aug 3 02:49:36 2023 user.notice URL-DEBUG: hotplug (iface): action='ifup-failed' interface='CLAT1'
Thu Aug 3 02:49:38 2023 user.info mwan3track[13087]: Check (httping) failed for target "8.8.4.4" on interface wan1 (wwan0). Current score: 7
Thu Aug 3 02:49:39 2023 daemon.notice netifd: Interface 'CLAT1' is now down
Thu Aug 3 02:49:39 2023 daemon.notice netifd: Interface 'CLAT1' is setting up now
Thu Aug 3 02:49:39 2023 user.notice URL-DEBUG: hotplug (iface): action='ifup-failed' interface='CLAT1'
Thu Aug 3 02:49:43 2023 daemon.notice netifd: Interface 'CLAT1' is now down
Thu Aug 3 02:49:43 2023 daemon.notice netifd: Interface 'CLAT1' is setting up now
Thu Aug 3 02:49:43 2023 user.notice URL-DEBUG: hotplug (iface): action='ifup-failed' interface='CLAT1'
Thu Aug 3 02:49:46 2023 daemon.notice netifd: Interface 'CLAT1' is now down
Thu Aug 3 02:49:46 2023 daemon.notice netifd: Interface 'CLAT1' is setting up now
Thu Aug 3 02:49:46 2023 user.notice URL-DEBUG: hotplug (iface): action='ifup-failed' interface='CLAT1'
Thu Aug 3 02:49:48 2023 user.info mwan3track[13087]: Check (httping) failed for target "1.1.1.1" on interface wan1 (wwan0). Current score: 6
Thu Aug 3 02:49:49 2023 daemon.notice netifd: Interface 'CLAT1' is now down
Thu Aug 3 02:49:49 2023 daemon.notice netifd: Interface 'CLAT1' is setting up now
Thu Aug 3 02:49:49 2023 user.notice URL-DEBUG: hotplug (iface): action='ifup-failed' interface='CLAT1'
Thu Aug 3 02:49:52 2023 daemon.notice netifd: Interface 'CLAT1' is now down
Thu Aug 3 02:49:52 2023 daemon.notice netifd: Interface 'CLAT1' is setting up now
Thu Aug 3 02:49:52 2023 user.notice URL-DEBUG: hotplug (iface): action='ifup-failed' interface='CLAT1'
Thu Aug 3 02:49:53 2023 user.info mwan3track[13087]: Check (httping) failed for target "1.0.0.1" on interface wan1 (wwan0). Current score: 6

The CLAT(and XLAT server) interface is how tmobile transports IPV4 traffic over IPV6.

I'm not 100% sure if this is a problem, but based on your other logs I see no problems. I just see logs for a modem that is connected.

Based on the logs, your modem is not dropping out or shutting off. Based on what you've said, and seeing those logs posted, you are just losing the data connection. When you say rebooting fixes it for a little bit, that 100% points to losing data connection with the carrier, not losing your modem. Completely different issue and troubleshooting methods.

The CLAT errors above seem to show up pretty much immediately after the last entry in your modem log. How long does the modem typically pass data for before it stops?

Post by **Dubbzy** » Thu Aug 03, 2023 9:17 am

The hub works with my pc without issue.

I had no problem with maintaining a data connection with it connected to my PC once introducing the hub. I tested this by downloading a fairly large file overnight, which it was able to complete without any issue.

As I want to be able to use this product in other ways, I decided to try and reintroduce the NEXS2GO back into the mix. However, just as before, I am only able to maintain a connection for short periods of time. Everything points to things working, and even during the time of the errors I am able to perform Google searches, but other websites will fail. So it's not a total connection loss, just what seems like some sort of DNS issue or something

Post by **Didneywhorl** » Thu Aug 03, 2023 9:27 am

Yeah, that sounds like the NEXS2GO firmware may need a fresh install again.

Try this version: https://random-sharing.b-cdn.net/WiFiX- ... 03-20A.zip

Do not save settings or use a configuration backup, as they can re-introduce issues. Flash 3x in a row (old troubleshooting "trick")

Post by **Dubbzy** » Thu Aug 03, 2023 10:52 am

That's the way I had done it.

Took it back to factory and navigated to flash the new firmware, then flashed 2 more times.

I'll do it once more to see if it might help, but this is the same issue I have been having since day 1

Post by **Didneywhorl** » Thu Aug 03, 2023 11:07 am

Let us know if anything changes with that firmware.

You may also want to try eliminating IPV6 for that build, making the APN connect as IP(IPV4) only.

Post by **Dubbzy** » Thu Aug 03, 2023 12:24 pm

This is a Calyx T-Mobile hotspot plan. I believe it only has a ipv6 option, though the router can translate that over to ipv4 somehow.

I have tried to make the APN IPV4 only, but then it will not connect.

Post by **Dubbzy** » Thu Aug 03, 2023 1:32 pm

Also,

Thu Aug 3 13:21:24 2023 user.notice nft-qos-monitor: ACTION=update, MACADDR=7e:0a:11:c4:6f:c1, IPADDR=192.168.1.159, HOSTNAME=Pixel-6-Pro
Thu Aug 3 13:21:24 2023 user.notice nft-qos-dynamic: ACTION=update, MACADDR=7e:0a:11:c4:6f:c1, IPADDR=192.168.1.159, HOSTNAME=Pixel-6-Pro
Thu Aug 3 13:21:25 2023 daemon.info dnsmasq-dhcp[9923]: DHCPREQUEST(br-lan) 192.168.1.210 84:a9:38:da:6a:eb
Thu Aug 3 13:21:25 2023 daemon.info dnsmasq-dhcp[9923]: DHCPACK(br-lan) 192.168.1.210 84:a9:38:da:6a:eb Legion
Thu Aug 3 13:21:26 2023 user.notice nft-qos-monitor: ACTION=add, MACADDR=84:a9:38:da:6a:eb, IPADDR=192.168.1.210, HOSTNAME=Legion
Thu Aug 3 13:21:26 2023 user.notice nft-qos-dynamic: ACTION=add, MACADDR=84:a9:38:da:6a:eb, IPADDR=192.168.1.210, HOSTNAME=Legion
Thu Aug 3 13:21:27 2023 daemon.notice netifd: Interface 'CLAT1' is now down
Thu Aug 3 13:21:27 2023 daemon.notice netifd: Interface 'CLAT1' is setting up now
Thu Aug 3 13:21:27 2023 user.notice URL-DEBUG: hotplug (iface): action='ifup-failed' interface='CLAT1'
Thu Aug 3 13:21:30 2023 daemon.notice netifd: Interface 'CLAT1' is now down
Thu Aug 3 13:21:30 2023 daemon.notice netifd: Interface 'CLAT1' is setting up now
Thu Aug 3 13:21:30 2023 user.notice URL-DEBUG: hotplug (iface): action='ifup-failed' interface='CLAT1'
Thu Aug 3 13:21:33 2023 daemon.notice netifd: Interface 'CLAT1' is now down
Thu Aug 3 13:21:33 2023 daemon.notice netifd: Interface 'CLAT1' is setting up now
Thu Aug 3 13:21:33 2023 user.notice URL-DEBUG: hotplug (iface): action='ifup-failed' interface='CLAT1'
Thu Aug 3 13:21:34 2023 daemon.err uhttpd[5104]: luci: accepted login on / for root from 192.168.1.210
Thu Aug 3 13:21:36 2023 daemon.notice netifd: Interface 'CLAT1' is now down
Thu Aug 3 13:21:36 2023 daemon.notice netifd: Interface 'CLAT1' is setting up now
Thu Aug 3 13:21:37 2023 user.notice URL-DEBUG: hotplug (iface): action='ifup-failed' interface='CLAT1'
Thu Aug 3 13:21:40 2023 daemon.notice netifd: Interface 'CLAT1' is now down
Thu Aug 3 13:21:40 2023 daemon.notice netifd: Interface 'CLAT1' is setting up now
Thu Aug 3 13:21:40 2023 user.notice URL-DEBUG: hotplug (iface): action='ifup-failed' interface='CLAT1'
Thu Aug 3 13:21:43 2023 daemon.notice netifd: Interface 'CLAT1' is now down
Thu Aug 3 13:21:43 2023 daemon.notice netifd: Interface 'CLAT1' is setting up now
Thu Aug 3 13:21:43 2023 user.notice URL-DEBUG: hotplug (iface): action='ifup-failed' interface='CLAT1'
Thu Aug 3 13:21:46 2023 daemon.notice netifd: Interface 'CLAT1' is now down
Thu Aug 3 13:21:46 2023 daemon.notice netifd: Interface 'CLAT1' is setting up now
Thu Aug 3 13:21:46 2023 user.notice URL-DEBUG: hotplug (iface): action='ifup-failed' interface='CLAT1'
Thu Aug 3 13:21:49 2023 daemon.notice netifd: Interface 'CLAT1' is now down
Thu Aug 3 13:21:49 2023 daemon.notice netifd: Interface 'CLAT1' is setting up now
Thu Aug 3 13:21:49 2023 user.notice URL-DEBUG: hotplug (iface): action='ifup-failed' interface='CLAT1'

The same thing appears to be happening. I'm not sure what else is going on or how to move forward with this

Post by **Didneywhorl** » Thu Aug 03, 2023 4:56 pm

I'm going to post on the firmware forums about it, and see what they say for this. I'll let you know.

Post by **Didneywhorl** » Thu Aug 03, 2023 5:51 pm

Navigate to the page: Network->Interfaces and edit the LAN. On the Advanced Settings tab and delete the IPv6 IPs from the Custom DNS Servers.

Reboot.

Post by **Dubbzy** » Fri Aug 04, 2023 12:38 pm

Didneywhorl wrote: Thu Aug 03, 2023 5:51 pm Navigate to the page: Network->Interfaces and edit the LAN. On the Advanced Settings tab and delete the IPv6 IPs from the Custom DNS Servers.

Reboot.

I'll give it to go and do some testing!

Post by **Dubbzy** » Fri Aug 04, 2023 1:37 pm

I performed this step, and things were working, then the modem was disconnected by something internally.

I rebooted, still not showing anything for the modem.

My PC recognizes the modem with the same cable being used for the NEXS2GO, connects to my PC and works without issue.

I've attached all the logs I could find. This is disheartening.

Post by **Dubbzy** » Tue Aug 15, 2023 8:07 am

Dubbzy wrote: Fri Aug 04, 2023 1:37 pm I performed this step, and things were working, then the modem was disconnected by something internally.

I rebooted, still not showing anything for the modem.

My PC recognizes the modem with the same cable being used for the NEXS2GO, connects to my PC and works without issue.

I've attached all the logs I could find. This is disheartening.

Just a quick bump, have you had a chance to review these logs?

Post by **Didneywhorl** » Fri Aug 18, 2023 8:05 am

I'll make a custom firmware update for you. It has to be something either related to the firmware acting a fool, or somehow the power output on the usb port just isn't kicking like it should.

Nothing in the logs is jumping out at me, except the Connection logging. It's got the modem coming and going with connections to the internet, but the System log is oddly clear of modem info.

If you can't get it going on the new firmware, I'll swap one of mine out with you for free.

Give me a day or two to get the firmware image compiled.

Post by **Dubbzy** » Fri Aug 18, 2023 8:19 am

Awesome! Thank you for the continued support!

Post by **Didneywhorl** » Tue Aug 22, 2023 10:45 am

I've got some issues with my build system. Should have fixed and done today.

Post by **Didneywhorl** » Thu Aug 24, 2023 11:17 pm

Took forever to fix my machine, but here is the first I could get done: https://thewirelesshaven.com/help-page-nexs2go/

NOTE: It is 100% untested. You can always recover, but I have to say I haven't tested it and will not be able to for about a week or so. Much going on right now.

Post by **Dubbzy** » Thu Sep 21, 2023 7:37 pm

Didneywhorl wrote: Thu Aug 24, 2023 11:17 pm Took forever to fix my machine, but here is the first I could get done: https://thewirelesshaven.com/help-page-nexs2go/

NOTE: It is 100% untested. You can always recover, but I have to say I haven't tested it and will not be able to for about a week or so. Much going on right now.

No worries, same here.

I am thinking there is actually something wrong with the modem itself. It had been working flawlessly once I introduced the powered USB hub to the mix, but it has started disconnecting and reconnecting itself again, which it is doing not from a service level, but straight from the USB driver level.

Oddly enough, it only seems to happen if I am actually trying to use it. If I leave my Ethernet/wifi connected, then I will never see it disconnect. But as soon as I rely solely on the cellular connection, it starts disconnecting.

Not sure how I would go about fixing that.

I'm ordering one of those USB devices that monitors the output of power it's connected to, but I've not noticed issues with anything else, just the modem. I've made sure it's the only thing even plugged into the hub.

Post by **Didneywhorl** » Sun Sep 24, 2023 4:01 pm

Are you also working with the BPI3 mini?

Post by **Dubbzy** » Sun Sep 24, 2023 4:24 pm

Didneywhorl wrote: Sun Sep 24, 2023 4:01 pm Are you also working with the BPI3 mini?

I have whatever is in the prebuilt modem you guys sent me.

My order #xxxxx [Mod edit for privacy]

Post by **Didneywhorl** » Mon Sep 25, 2023 8:28 am

Dubbzy wrote: Sun Sep 24, 2023 4:24 pm
Didneywhorl wrote: Sun Sep 24, 2023 4:01 pm Are you also working with the BPI3 mini?
I have whatever is in the prebuilt modem you guys sent me.

My order #xxxxx

Not what I meant

There is a user on another forum for a SBC, like the raspberry pi, that has a similar username as yours. I checked though, different username

Post by **Dubbzy** » Mon Sep 25, 2023 8:31 am

Didneywhorl wrote: Mon Sep 25, 2023 8:28 am
Dubbzy wrote: Sun Sep 24, 2023 4:24 pm
Didneywhorl wrote: Sun Sep 24, 2023 4:01 pm Are you also working with the BPI3 mini?
I have whatever is in the prebuilt modem you guys sent me.

My order #xxxxx
Not what I meant There is a user on another forum for a SBC, like the raspberry pi, that has a similar username as yours. I checked though, different username

Oh gotcha. No, I've never had the pleasure of using anything like a raspberry pi. I looked into one a few years back when I was reading about the PiHole, but never went further than that.

Post by **Dubbzy** » Wed Oct 25, 2023 1:58 pm

Dubbzy wrote: Thu Sep 21, 2023 7:37 pm
Didneywhorl wrote: Thu Aug 24, 2023 11:17 pm Took forever to fix my machine, but here is the first I could get done: https://thewirelesshaven.com/help-page-nexs2go/

NOTE: It is 100% untested. You can always recover, but I have to say I haven't tested it and will not be able to for about a week or so. Much going on right now.

No worries, same here.

I am thinking there is actually something wrong with the modem itself. It had been working flawlessly once I introduced the powered USB hub to the mix, but it has started disconnecting and reconnecting itself again, which it is doing not from a service level, but straight from the USB driver level.

Oddly enough, it only seems to happen if I am actually trying to use it. If I leave my Ethernet/wifi connected, then I will never see it disconnect. But as soon as I rely solely on the cellular connection, it starts disconnecting.

Not sure how I would go about fixing that.

I'm ordering one of those USB devices that monitors the output of power it's connected to, but I've not noticed issues with anything else, just the modem. I've made sure it's the only thing even plugged into the hub.

So output power is still good. No fluctuations or issues, but modem apparently still is rebooting itself. It's hard to say exactly when it happens since LEDs for power stopped working shortly after I received it.

Not sure where to go from here other than just taking a loss on these and looking for another product.

Post by **Didneywhorl** » Wed Oct 25, 2023 3:39 pm

Shoot me an email at sales@thewirelesshaven.com about it. I might have something to swap you up to.