17-07-2017 11:23 PM
I recently purchased a VW with their Car-Net subscription, which requires Internet connectivity. To set it up, I had the car connected to my home Wi-Fi and it worked fine. Based on recomendations from other Car-Net users, I then purchased a Huawei E8372h-153 wingle and an EE 4G data sim. I want to use EE because it provides the best data coverage where I live.
To cut a long story short, I cannot get Car-Net to work on the EE 4G connection, most likely due to a DNS issue. I created a test set up which allows me to capture the packets to and from the head unit. That setup also allows me to change the DNS server addresses which are sent to the head unit as part of the DHCP options. So, I captured a trace using OpenDNS DNS servers and a trace with the default EE DNS servers. The head unit queries both IPv6 AAAA and IPv4 A records for er-mib2std-ca0d-mbbservices.audi-connect.de. The OpenDNS AAAA response simply returns a CNAME vw-eu-mib2std-mbbservices04.audi-connect.de. The EE AAAA response returns the same CNAME but also an IP address "64:ff9b::8fa4:a807".
From what I can determine, this IP address "64:ff9b::8fa4:a807" is in no way associated with audi-connect.de, just perform the query yourself here http://www.ipvoid.com/aaaa-ipv6-lookup/ and here https://mxtoolbox.com/IPv6.aspx.
Unfortunately I'm stuck now because I cannot manually configure IP settings on the car's head unit and the wingle does not allow me to modify any of the DHCP options. I tried the same with an O2 sim and it works fine, but I would really like to use the EE data network.
Is this in any way related to the fact that EE are rolling out IPv6 on their network? Is there a fix?
18-07-2017 07:07 AM
This is not a answer to your questioin, but I am unable to get VPN going because EE networks is screwed and does not work properly.
I think people who just want to browse the internet be happy with EE network, rest or the onese with specialist projects will be dissapointed ....
18-07-2017 10:31 AM
Yes, I have opened up a communication channel with VW too. In the meantime, I'm just interested to find out why the EE DNS servers are returning an (invalid) IPv6 address in the first place? (It clearly confuses my car, even though the car should probably just ignore the returned information and continue on IPv4.)
19-07-2017 10:43 PM
I've not sorted this one yet, but it does seem to be related to the IPv6 rollout. For hosts that are IPv4 only, the EE DNS server synthesises an IPv6 response. So, the returned address "64:ff9b::8fa4:a807" is in fact an IPv6 representation of the IPv4 address "18.104.22.168", associated with host er-mib2std-ca0d-mbbservices.audi-connect.de.
If the wingle and head-unit would be IPv6 capable then I guess that would be fine, i.e. it would be a way for EE IPv6 network clients to communicate with an IPv4 host (using DNS64 and NAT64 services provided by EE).
In my case, I know that the wingle isn't IPv6 and I can see it gets allocated an IPv4 WAN address, which is good. My suspicion is that the head-unit wants to use IPv6 to communicate because it receives an IPv6 DNS response, but there is no 'path' for it to do so (wingle LAN is IPv4 only, so the head-unit wouldn't even be allocated an IPv6 address). Unfortunately, the head-unit then doesn't fall back to IPv4. However, that's just my hypothesis! I don't even know whether the head unit is in fact IPv6 ready... All I know is that the IPv6 DNS response causes the Car-Net connection to fail 😞
23-07-2017 07:33 PM
Spoke to a helpful lady in customer services and she provided me with the 'orangeinternet' apn details for IPv4 use. However, that apn must use the same DNS server(s) because an AAAA query for a host which only exists as IPv4 on the Internet still results in a response with an IPv6 'pseudo' address (for use by the EE Internet gateway).
I think it is good that EE are embracing IPv6, even though in my case it results in a VW Car-Net connectivity issue. However, at this point in time, I would point the finger at the head-unit rather than EE, as the root cause for the connectivity issue.
As a workaround I now use an O2 SIM, which works fine. I will provide further updates if I make any progress with Volkswagen. It would be good if I could 'pause' my pre-loaded 12GB EE SIM (2GB/month for 6 months), but I presume that is not possible?
25-07-2017 04:29 PM
can you please share complete settings for the orangeinternet' APN?
Does the APN work in their 4G network?
25-07-2017 07:07 PM
I was advised to use the following details:
The wingle connected to the EE 4G network with these details (and I got an IPv4 WAN address as before), but DNS response was the same so it wasn't a solution for me.
by max1486 16 hours ago
by Maisie2 Saturday