Frequent packet loss in router MR100 4G LTE with Airtel 4G sim card
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi,
I bought the MR100 wireless router 2 months back, from the day I purchased this I'm keep seeing the packet loss issues but haven't got any fix or help on this.
However when I purchased it, I could see rare packet loss but after a week or two, I could see frequent packet loss.
C:\Users\veg>ping -n 100 google.com Pinging google.com [216.58.196.174] with 32 bytes of data:
Reply from 216.58.196.174: bytes=32 time=459ms TTL=55
Reply from 216.58.196.174: bytes=32 time=842ms TTL=55
Reply from 216.58.196.174: bytes=32 time=214ms TTL=55
Reply from 216.58.196.174: bytes=32 time=61ms TTL=55
Reply from 216.58.196.174: bytes=32 time=149ms TTL=55
Reply from 216.58.196.174: bytes=32 time=93ms TTL=55
Reply from 216.58.196.174: bytes=32 time=332ms TTL=55
Reply from 216.58.196.174: bytes=32 time=195ms TTL=55
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.58.196.174: bytes=32 time=58ms TTL=55
Reply from 216.58.196.174: bytes=32 time=41ms TTL=55
Reply from 216.58.196.174: bytes=32 time=53ms TTL=55
Reply from 216.58.196.174: bytes=32 time=45ms TTL=55
Reply from 216.58.196.174: bytes=32 time=46ms TTL=55
Reply from 216.58.196.174: bytes=32 time=50ms TTL=55
Reply from 216.58.196.174: bytes=32 time=54ms TTL=55
Reply from 216.58.196.174: bytes=32 time=52ms TTL=55
Reply from 216.58.196.174: bytes=32 time=46ms TTL=55
Reply from 216.58.196.174: bytes=32 time=66ms TTL=55
Reply from 216.58.196.174: bytes=32 time=53ms TTL=55
Reply from 216.58.196.174: bytes=32 time=53ms TTL=55
Reply from 216.58.196.174: bytes=32 time=42ms TTL=55
Reply from 216.58.196.174: bytes=32 time=53ms TTL=55
Reply from 216.58.196.174: bytes=32 time=50ms TTL=55
Reply from 216.58.196.174: bytes=32 time=53ms TTL=55
Request timed out.
Request timed out.
Request timed out.
Reply from 216.58.196.174: bytes=32 time=61ms TTL=55
Reply from 216.58.196.174: bytes=32 time=76ms TTL=55
Reply from 216.58.196.174: bytes=32 time=56ms TTL=55
Reply from 216.58.196.174: bytes=32 time=45ms TTL=55
Thought that could be network coverage issues and purchased the 4G lte antenna. With the antenna connection speed got increased but packet loss issue still persists.
https://www.amazon.in/Kaevion-KVA660E-Antenna-TP-Link-Router/dp/B09DZ3FV74/ref=sr_1_11_sspa?keywords=4g+lte+antenna&qid=1658732810&sprefix=4g+lte+an%2Caps%2C275&sr=8-11-spons&psc=1&spLa=ZW5jcnlwdGVkUXVhbGlmaWVyPUFWNFRUVENZMVM5WTQmZW5jcnlwdGVkSWQ9QTAxNTM0ODRMVEJMUEhEOTdWWlAmZW5jcnlwdGVkQWRJZD1BMDExNzU4NU9JSUxPUTI1VlM4TCZ3aWRnZXROYW1lPXNwX210ZiZhY3Rpb249Y2xpY2tSZWRpcmVjdCZkb05vdExvZ0NsaWNrPXRydWU=
The same sim card I have kept in my mobile and used as hotspot to my laptop, haven't seen any packet loss over there.
Hope to get help soon.
Thanks,
venkatesh
Hi, I am using the Airtel LTE 4G simcard, I could see regular disconnections of network and I could see 'connecting' status under network Basic -> Internet -> Internet status.
As you said, I have locked the Band to 8, still I could see frequent disconnections. My mobile works great on Band 8, network speed will be slow down sometimes but never had faced time out issues as such until unless if complete signal goes off, which rarely happens in my area.
Since I'm working in remote area where there is no broadband connection, I have chosen this MR100 router which has 4G LTE simcard facility. However I'm facing this network drop issues during 'Teams meeting calls'. Download speed looks fine, but due to the packet drop issues, I'm facing huge call drop in meetings, and downloads gets cancelled when packet drop occurs so I need to restart the download which downloads from starting eventually I'm loosing huge amount of Data.
And I have never tested this router with Wired connection which I don't have at my place.
Please find the attached documents.
Looks like many user with this product having same issues, please help me fixing this issue.