It seems to be an network reception issue. If you are using an Android phone, can you try to download the app LTE discovery (or something similar) to find out with bands you were on? and the strength of it?
As well, can you do the normal speed test during the day and night to see if there was a difference? At night the signal reception could be worse because there were more partitions with closed door and windows.
Regarding the add-on 25GB, which plan were you on? Was it an “old” LTE plan where you can get speed of more than 100MBs? or was it a new one with a speed cap?
Hi
Been using Koodo for over 12 years.
Phone seems to run fine for most things except the for tethering/VPN/RDP
In the last 2 months its gone from usable, to completely un-usable.
I have read of issues with VPN over LTE due to the way data is sent in parallel over multiple channels
Nothing physically has changed in my day to day usage and locations. IE On Friday I attempted to connect up at home, then multiple times on the way into Toronto (someone else was driving), and then at 2 different location, all with the same results.
Running a S21ultra with the latest OS updates (Samsung's flavor of Android)
I haven’t checked speed in a while as it been doing what I need.. ie.. Remote desktop used very little data at about 150-200 Kbps for basic text functionality.
I seem to remember the speed was in the 60 Mbps range before; so could of been on a old LTE plan before getting the 25GB add on (Only reason I got it was it was cheap and having the massive extra headroom for just in case :-)
I ran a speed test just now and hitting 281/17 Mbps and then again 324/6 (New LTE?) - Just blew gig of cellular testing :-(
Switch from LTE to WCDMA/GSM (showing up as 4G) and speed test hitting 9/2 Mbps, On 4G VPN connects up without any issues every time; but RDP still very very spotty (was able to connect once in about 10 time)
Generally my issue is more with VPN and general network through Tethering. Pretty sure its something to do with the 25G plan addon
Any thoughts on the possibly of Koodo switching me back to older cellular LTE?
Thanks
Paul
Update
Done some more testing..
At this point in time, I’m pretty sure my issues is MTU related (Maybe Windows update related?)
The MTU of the VPN connection isn’t accurate, and is actually smaller.
Steps to fix
Connect up to Hotspot, and then bring up VPN
Run CMD prompt as Administrator
Check MTU settings
netsh interface ipv4 show subinterfaces
MTU MSS Bytes In Bytes Out Interface
------ --------------- --------- --------- -------------
1500 1 5583429 2002832 Wi-Fi
1400 1 23681 79493 VPN-Primary
VPN-Primary is 1400 max packet size
Perform ping tests (below) to figure out max MTU
Noted 1326 packet size is sweet spot where pings are replied to successfully.
Tweaked MTU for VPN-Primary connection
netsh interface ipv4 set subinterface "VPN-Primary" MTU=1326 store=persistent
Verify change caught.
netsh interface ipv4 show subinterfaces
MTU MSS Bytes In Bytes Out Interface
------ --------------- --------- --------- -------------
1500 1 8203902 4478076 Wi-Fi
1326 1 525672 526952 VPN-Primary
Connect up VPN - WORKS!
I’ll perform some testing in the different locations I work. I think there may of been some other issues with the Koodo/Telus network previously (as I wasn’t able to ping standard internet addresses as google.com) when was testing,
Hope this helps someone else out
Paul
-==-=--==--=-=Ping to get valid max Packet size
C:\>ping -f -l 1500 -n 1 192.168.2.30
Pinging 192.168.2.30 with 1500 bytes of data:
Packet needs to be fragmented but DF set.
Ping statistics for 192.168.2.30:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
C:\>ping -f -l 1400 -n 1 192.168.2.30
Pinging 192.168.2.30 with 1400 bytes of data:
Packet needs to be fragmented but DF set.
Ping statistics for 192.168.2.30:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
C:\>ping -f -l 1350 -n 1 192.168.2.30
Pinging 192.168.2.30 with 1350 bytes of data:
Request timed out.
Ping statistics for 192.168.2.30:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
C:\>ping -f -l 1340 -n 1 192.168.2.30
Pinging 192.168.2.30 with 1340 bytes of data:
-Request timed out.
Ping statistics for 192.168.2.30:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
C:\>ping -f -l 1330 -n 1 192.168.2.30
Pinging 192.168.2.30 with 1330 bytes of data:
Request timed out.
Ping statistics for 192.168.2.30:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
C:\>ping -f -l 1320 -n 1 192.168.2.30
Pinging 192.168.2.30 with 1320 bytes of data:
Reply from 192.168.2.30: bytes=1320 time=55ms TTL=127
Ping statistics for 192.168.2.30:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 55ms, Maximum = 55ms, Average = 55ms
C:\>ping -f -l 1325 -n 1 192.168.2.30
Pinging 192.168.2.30 with 1325 bytes of data:
Reply from 192.168.2.30: bytes=1325 time=51ms TTL=127
Ping statistics for 192.168.2.30:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 51ms, Average = 51ms
C:\>ping -f -l 1326 -n 1 192.168.2.30
Pinging 192.168.2.30 with 1326 bytes of data:
Reply from 192.168.2.30: bytes=1326 time=52ms TTL=127
Ping statistics for 192.168.2.30:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 52ms, Maximum = 52ms, Average = 52ms
C:\>ping -f -l 1327 -n 1 192.168.2.30
Pinging 192.168.2.30 with 1327 bytes of data:
Request timed out.
Ping statistics for 192.168.2.30:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
C:\>ping -f -l 1326 -n 1 192.168.2.30
Pinging 192.168.2.30 with 1326 bytes of data:
Reply from 192.168.2.30: bytes=1326 time=50ms TTL=127
Ping statistics for 192.168.2.30:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 50ms, Average = 50ms
Update - Solution didn’t last - Issue came back :-(
So above MTU solution was just a fluke.
Called into Koodo 1st level support and went through the standard trouble shooting steps (reboot, reset network settings) without any luck.
Bumped up to level 2 support.
While waiting for 2nd level, repeated and new additional testing, swapping cell phones, sim cards and carriers. Problem followed Koodo service (the sim card) ruling out phone.
2nd level support quickly got back to me. After some additional testing, made some network changes on Koodo’s side and it worked
Believe it was a issue with some sort of Koodo network protection (but don’t quote me as I wasn’t paying to much attention)
So if your having issues with Tethering and VPN, use the Koodo online service to request a tech support call back
P.