Escort Radar Forum  

Go Back   Escort Radar Forum > Windshield Radar Detectors > RedLine 360c

Notices

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old November 15th, 2021
gtgf gtgf is offline
Junior Member
 
Join Date: Nov 2021
Posts: 4
Default WiFi Issues on Redline 360c

Hi everyone,

Like a lot of you I have been trying to get my redline 360c to work with my car's hotspot.

I recently got a T-Mobile SyncUp Drive since I have read that others have gotten it to work on that device. The device is strictly 2.4 B/G/N so the radio is fully compatible. Well the redline connects and shows up as connected but all I get is the white MPH box with the -- and Communication Error when I try to update Database or Firmware.

I know my redline is fine because it works great on my home's wifi.
Being a bit of a tech nerd I started to investigate what the issue might be so I started using other devices like my phone's hotspot which is also on T-Mobile and I get the same behavior as the SyncUP.

So I took it inside and connected it back to my home network and started both DNS and packet tracing the R360c.

The Redline talks to these three domains:
http://device.drivealert.io/
http://live2.escortassist.net/
http://url.drivealert.io/

When running a traceroute on my home network I see the following:
traceroute to live2.escortassist.net (3.93.75.177), 64 hops max, 52 byte packets
1 rt-ac66u (10.0.0.1) 2.663 ms 1.055 ms 0.981 ms
2 * * *
3 100.41.26.74 (100.41.26.74) 70.505 ms
100.41.26.76 (100.41.26.76) 67.706 ms
100.41.26.74 (100.41.26.74) 4.202 ms
4 0.csi1.grcynygc-mse01-bb-su1.alter.net (140.222.3.206) 11.203 ms 14.162 ms
0.csi1.whplnywp-mse01-bb-su1.alter.net (140.222.3.212) 134.554 ms
5 * * *
6 * * *
7 0.ae15.gw14.iad8.alter.net (140.222.226.31) 12.127 ms
0.ae16.gw14.iad8.alter.net (140.222.226.37) 8.966 ms
0.ae15.gw14.iad8.alter.net (140.222.226.31) 10.559 ms
8 &#10.170.148.204.in-addr.arpa (204.148.170.66) 10.904 ms 14.977 ms 10.146 ms

When running it on my phone's hotspot or SyncUp I get the following:
traceroute to live2.escortassist.net (3.93.75.177), 64 hops max, 52 byte packets
1 192.168.51.128 (192.168.51.128) 18.104 ms 8.942 ms 7.839 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *

From this I gather that T-mobile is blocking or dropping the communication to the R360c as the packets don't ever leave the Hotspot.

To further prove that it is definitely T-Mobile blocking stuff, I ran my phone's hotspot and connected my computer to it but also had my computer share its wifi network while on a VPN. This put the wifi I was sharing with the R360c behind a vpn. When the R360c connected to the wifi behind the VPN it worked fine.

Since the VPN created a tunnel it bypasses whatever issue or block T-mobile has with the R360c.

This may have something to do with T-Mobile being a IPv6 network, my network at home is still IPv4, I will investigate further. As well as try other provider's hotspot.

I don't know if this helps anyone, hopefully cedar so they can fix it. There has to be a reason why the R360c traffic goes nowhere on a T-Mobile hotspot and it might also be the same reason it goes no where in other car's hotspot.

If you would like to test the packet hops on your hotspot you can just run this command on a linux or mac computer as well as an android phone traceroute live2.escortassist.net for windows replace traceroute with tracert
Reply With Quote
  #2  
Old November 15th, 2021
mtime mtime is offline
Senior Member
 
Join Date: Jun 2015
Posts: 369
Default

I have been running T-Mobile reliably on my M360c, then R360c, now MaxCam360 using my iPhone hotspot for a long time without an issue.
You've indicated that you can't get data service from either your iPhone hotspot or your data only T-Mobile hotspot.
How long have you had your Redline and have you ever had a successful connection?
Reply With Quote
  #3  
Old November 17th, 2021
gtgf gtgf is offline
Junior Member
 
Join Date: Nov 2021
Posts: 4
Default

I actually just got the redline 360c about a couple weeks ago, it has never worked for me on any of my Tmobile devices, at least not as it should. I don't have an iphone, I have an android, Galaxy S21 Ultra.

I did find a solution, it is a little involved but not difficult by any means. Although once it is set up, it is basically set it and forget it.

I hypothesize the issue lies in the use of ipv6 networks, when using an ipv6 to access escort's servers the traffic data goes nowhere but when using an ipv4 network I have no issues.

To get around ipv6 entirely what I ended up doing was getting a gl-inet usb powered mini router, recommend either the mango or shadow if you have a 2.4 hotspot, these run around $30 or the slate if you have 5GHz only in your car, this one is around $60.

The next step get a VPN, I already had a wireguard VPN server running on my home network, but you can definitely use OpenVPN or a VPN service like Nord or Private Internet Access both also worked for me.

Connect the mini router using WISP to your car's hotspot and then configure the VPN service on the mini router and boom magic your radar should connect without issues to Escort's servers since there is no ipv6 network standing in your way since you are now using a vpn tunnel to bypass it completely.

The router is usb powered and turns on and off with the car and once configured it auto connects to your car's hotspot and connects to the VPN all on its own. It takes about 2 minutes give or take to connect but it's completely hands off.

I configured the router to only route the R360c's traffic through the VPN. This way the rest of my devices are not slowed down by the vpn. On vpn average bandwidth on those mini routers is 10 Mbps up and down which is more than enough for the R360c but horrible for a dashcam or most other devices.

This is basically a workaround, the real solution would be for Escort to update their servers to allow ipv6 networks to communicate with their servers natively using ipv6 address, I think that would solve almost everyone's connectivity issues.

Since you say it works for you out of curiosity would you mind going to this site and letting me know if you are running ipv6 on T-mobile where you are: https://test-ipv6.com/

Last edited by gtgf; November 17th, 2021 at 09:40 PM.
Reply With Quote
  #4  
Old November 17th, 2021
mtime mtime is offline
Senior Member
 
Join Date: Jun 2015
Posts: 369
Default

Going to the site you listed with my iPhone on cellular only (T-Mobile), the results were 10/10 for IPv6.
I'm glad you figured out a workaround. I'm not sure the issue is IPv6, but you're certainly technically more experienced than me.
Why my iPhone works but your android doesn't is unclear. With iPhone, you have to switch to compatibility mode to force a 2.4gb connection (which the RL360c requires). Is there something similar with Android?
The other issue posted on the forum(s) is the Escort RD's have difficulty with complex network names and passwords. You might try limiting names and passwords to single names and pm's of 8 or less characters.
Also, what make/model is your vehicle. Escorts and GM's (On-Star) never liked each other. Same for a few other makes.

Last edited by mtime; November 17th, 2021 at 07:45 PM.
Reply With Quote
  #5  
Old November 17th, 2021
gtgf gtgf is offline
Junior Member
 
Join Date: Nov 2021
Posts: 4
Default

I make my SSIDs and passwords super short and simple so I am sure it is not that, not even spaces. I am using a T-mobile Syncup Drive Hotspot connected to the OBD2 port since my car does not have built in WiFi.

Androids have the ability to pick 2.4 and 5Ghz as well as encryption type, my phone connects fine and is able to provide data to legacy 2.4 devices.

Now I'll be honest the whole IPv6 is a hypothesis, I could be entirely wrong. It's just when I run a traceroute to the url the radar keeps trying to reach (live2.escortassist.net) over an IPv4 networks I tend to get a response. When I try it on an ipv6 network, which I have at work, and on my phone, or hotspot, I get nada just immediate timeouts. This is what led me to believe it may have something to do with that.

Maybe T-mobile blocks certain kinds of traffic only in certain areas since my friends with iPhones have the same experience as me.

Now I can confidently say that if you set up a mini routers with a VPN even if you use Onstar, BMW, or any built in car WiFi it should work since you are going to be bypassing whatever block is going on.

Tried it on a friend's 2020 Suburban with onstar and a 2019 BMW M3 using the built in wifi, once the mini router was paired it connected and provided Escort Live data to the r360c with no issues. I attached a picture as proof, ignore the low voltage.
Attached Images
 

Last edited by gtgf; November 17th, 2021 at 09:57 PM.
Reply With Quote
  #6  
Old November 18th, 2021
mtime mtime is offline
Senior Member
 
Join Date: Jun 2015
Posts: 369
Default

The On Star users and/or car hotspot owners that have had connection problems should be happy to read your solution.
It's still curious to me why your phone hotspot won't give you a successful connection. Clearly by having a white PSL box (with dashes) means you're connected to your phone hotspot but as you experience, that does not mean you're getting an internet pass through. Have you experimented with lowering the security settings...just thinking?
Reply With Quote
  #7  
Old November 18th, 2021
gtgf gtgf is offline
Junior Member
 
Join Date: Nov 2021
Posts: 4
Default

I am confident it is not related to the SSID, Password, or encryption/security. I used WP2-Personal since WPA3 is not supported by the radar and WPA is as good as having your password in clear text on a post it note but the behavior was the same regardless of complexity or simplicity of the SSID or Password.

I can assure you the issue is most definitely network related, if you go online and look up T-mobile home internet and ipv6 there are tons of forums of users complaining on how T-mobile filters network traffic and block all kinds of ports, and I am sure other cellular networks do the same.

Now the US is a big place they may not filter the same kind of traffic where you are as they do where I am. We are not pinging the same towers or being routed from the same servers. Which could explain why it works for you and not for me.

The VPN tunnel bypasses whatever filtering and configuration T-mobile is running on their network and acts as an extension of my home network where I know the radar's traffic is not blocked. I am also using port 443 to run my vpn which is https and cannot be blocked since that port is the port the internet runs on and unblock-able by any ISP no matter how restrictive. Plus you get that safety net that T-mobile is not able to spy on your network traffic and sell your personal data to the highest bidder.

Last edited by gtgf; November 18th, 2021 at 11:34 PM.
Reply With Quote
  #8  
Old December 2nd, 2021
elarson6772 elarson6772 is offline
Junior Member
 
Join Date: Sep 2020
Posts: 24
Default

Quote:
Originally Posted by gtgf View Post
I actually just got the redline 360c about a couple weeks ago, it has never worked for me on any of my Tmobile devices, at least not as it should. I don't have an iphone, I have an android, Galaxy S21 Ultra.

I did find a solution, it is a little involved but not difficult by any means. Although once it is set up, it is basically set it and forget it.

I hypothesize the issue lies in the use of ipv6 networks, when using an ipv6 to access escort's servers the traffic data goes nowhere but when using an ipv4 network I have no issues.

To get around ipv6 entirely what I ended up doing was getting a gl-inet usb powered mini router, recommend either the mango or shadow if you have a 2.4 hotspot, these run around $30 or the slate if you have 5GHz only in your car, this one is around $60.

The next step get a VPN, I already had a wireguard VPN server running on my home network, but you can definitely use OpenVPN or a VPN service like Nord or Private Internet Access both also worked for me.

Connect the mini router using WISP to your car's hotspot and then configure the VPN service on the mini router and boom magic your radar should connect without issues to Escort's servers since there is no ipv6 network standing in your way since you are now using a vpn tunnel to bypass it completely.

The router is usb powered and turns on and off with the car and once configured it auto connects to your car's hotspot and connects to the VPN all on its own. It takes about 2 minutes give or take to connect but it's completely hands off.

I configured the router to only route the R360c's traffic through the VPN. This way the rest of my devices are not slowed down by the vpn. On vpn average bandwidth on those mini routers is 10 Mbps up and down which is more than enough for the R360c but horrible for a dashcam or most other devices.

This is basically a workaround, the real solution would be for Escort to update their servers to allow ipv6 networks to communicate with their servers natively using ipv6 address, I think that would solve almost everyone's connectivity issues.

Since you say it works for you out of curiosity would you mind going to this site and letting me know if you are running ipv6 on T-mobile where you are: https://test-ipv6.com/
Man, I was with you on this one, ordered the mini router you suggested and then got to the VPN setup step and got blown away. Makes no sense to me at all. Making a config file to upload and the other jazz involved seems very complicated for a noob. Any suggestion on some way to learn how to do that step?
Reply With Quote
  #9  
Old December 8th, 2021
flylow7f39 flylow7f39 is offline
Moderator
 
Join Date: Nov 2010
Posts: 4,006
Default

Links to sales and or services are not allowed in Escort's product support forum.

I have unapproved a couple posts for review by the forum administrator and other forum moderators. The posts were not deleted and will be back if the forum administrator decides they are OK.

Thanks for understanding!
__________________
__________________________________________________ ______________________________________
Moderators here are not Escort employees.

If you need immediate help give Escort Radar customer service a call right after they open at 1-800-543-1608, option 2, available from 9am-5:30pm Eastern Time Mon-Fri. Wait for the pause following the message and use the option for a call back.

Last edited by flylow7f39; December 8th, 2021 at 08:27 PM.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 05:18 AM.


Powered by vBulletin® Version 3.8.1
Copyright ©2000 - 2022, Jelsoft Enterprises Ltd.
Copyright 2018 Escort Inc.