Initial experiences from a new Mach-E owner

[timbop]

Good news. I finally got my Mach-E connected to my Wi-Fi.

My suspicion was correct. It was the DHCP server that the Mach-E didn't like. It appears as though there is an incompatibility between the Sync 4 software and the DHCP software that is running on the Synology NAS (Synology uses Dnsmasq for its DHCP server).

I disabled the DHCP server on my NAS and configured the DHCP server on my Ubiquity EdgeRouter X. Once I did that the Mach-E connected right away.

While I was troubleshooting the issue last night, I discovered in the Synology DHCP server's log files that it was assigning an address to the car (i.e. an ACK was being sent), but for some reason the Mach-E just wasn't accepting it.

Now I just need to figure out how to let Ford know about the incompatibility. Not that it matters to me anymore. I'll just keep using the DHCP server on my router, but it would be great if Ford could fix it so that nobody else runs into the same issue.

Well, that is good news - so your only remaining issue is with wireless android auto?

I am sure it was frustrating, but unfortunately those are some of the hazards of being an early adopter. The good news is that people will be gawking and asking you about the car for a long time.

Sponsored

 

[SashaLondon]

Good news. I finally got my Mach-E connected to my Wi-Fi.

My suspicion was correct. It was the DHCP server that the Mach-E didn't like. It appears as though there is an incompatibility between the Sync 4 software and the DHCP software that is running on the Synology NAS (Synology uses Dnsmasq for its DHCP server).

I disabled the DHCP server on my NAS and configured the DHCP server on my Ubiquity EdgeRouter X. Once I did that the Mach-E connected right away.

While I was troubleshooting the issue last night, I discovered in the Synology DHCP server's log files that it was assigning an address to the car (i.e. an ACK was being sent), but for some reason the Mach-E just wasn't accepting it.

Now I just need to figure out how to let Ford know about the incompatibility. Not that it matters to me anymore. I'll just keep using the DHCP server on my router, but it would be great if Ford could fix it so that nobody else runs into the same issue.

Thanks I have an edge router so will watch out for this when I get the car

 

[ChasingCoral]

Good news. I finally got my Mach-E connected to my Wi-Fi.

My suspicion was correct. It was the DHCP server that the Mach-E didn't like. It appears as though there is an incompatibility between the Sync 4 software and the DHCP software that is running on the Synology NAS (Synology uses Dnsmasq for its DHCP server).

I disabled the DHCP server on my NAS and configured the DHCP server on my Ubiquity EdgeRouter X. Once I did that the Mach-E connected right away.

While I was troubleshooting the issue last night, I discovered in the Synology DHCP server's log files that it was assigning an address to the car (i.e. an ACK was being sent), but for some reason the Mach-E just wasn't accepting it.

Now I just need to figure out how to let Ford know about the incompatibility. Not that it matters to me anymore. I'll just keep using the DHCP server on my router, but it would be great if Ford could fix it so that nobody else runs into the same issue.

Excellent news!
earlier there was discussion of MAC addresses. @hybrid2bev shows how to find them in this post
https://www.macheforum.com/site/threads/my-mach-e-day-1-impressions.2993/post-95148

 

[Tsand4]

I think you need andriod 11 or above to utilise andriod auto.

FWIW, I have had no wireless Android Auto connection issues and I am running Android 10 on a Samsung Galaxy S10.

 

[CP-Mach-E]

FWIW, I have had no wireless Android Auto connection issues and I am running Android 10 on a Samsung Galaxy S10.

Yep. The issue seems to be limited to version 11.

 

[Tsand4]

Good news. I finally got my Mach-E connected to my Wi-Fi.

My suspicion was correct. It was the DHCP server that the Mach-E didn't like. It appears as though there is an incompatibility between the Sync 4 software and the DHCP software that is running on the Synology NAS (Synology uses Dnsmasq for its DHCP server).

I disabled the DHCP server on my NAS and configured the DHCP server on my Ubiquity EdgeRouter X. Once I did that the Mach-E connected right away.

While I was troubleshooting the issue last night, I discovered in the Synology DHCP server's log files that it was assigning an address to the car (i.e. an ACK was being sent), but for some reason the Mach-E just wasn't accepting it.

Now I just need to figure out how to let Ford know about the incompatibility. Not that it matters to me anymore. I'll just keep using the DHCP server on my router, but it would be great if Ford could fix it so that nobody else runs into the same issue.

You may have just written a tech service bulletin for Ford! You could offer up your services as a tech consultant or just ask for a little swag like one of those Mach-E jackets that were seen on "the tour".
Glad they got issues worked out for you, now go enjoy the ride!

 

[CP-Mach-E]

Thanks I have an edge router so will watch out for this when I get the car

Just in case you misread my post, the EdgeRouter was the one that worked, so you should be good.

 

[Accord07]

Good news. I finally got my Mach-E connected to my Wi-Fi.

My suspicion was correct. It was the DHCP server that the Mach-E didn't like. It appears as though there is an incompatibility between the Sync 4 software and the DHCP software that is running on the Synology NAS (Synology uses Dnsmasq for its DHCP server).

I disabled the DHCP server on my NAS and configured the DHCP server on my Ubiquity EdgeRouter X. Once I did that the Mach-E connected right away.

While I was troubleshooting the issue last night, I discovered in the Synology DHCP server's log files that it was assigning an address to the car (i.e. an ACK was being sent), but for some reason the Mach-E just wasn't accepting it.

Now I just need to figure out how to let Ford know about the incompatibility. Not that it matters to me anymore. I'll just keep using the DHCP server on my router, but it would be great if Ford could fix it so that nobody else runs into the same issue.

Great job!

 

[CP-Mach-E]

...so your only remaining issue is with wireless android auto?

Yes, and now that my Wi-Fi is working, I can actually get the OTA update when it is available.

 

[RonTCat]

Good news. I finally got my Mach-E connected to my Wi-Fi.

My suspicion was correct. It was the DHCP server that the Mach-E didn't like. It appears as though there is an incompatibility between the Sync 4 software and the DHCP software that is running on the Synology NAS (Synology uses Dnsmasq for its DHCP server).

I disabled the DHCP server on my NAS and configured the DHCP server on my Ubiquity EdgeRouter X. Once I did that the Mach-E connected right away.

While I was troubleshooting the issue last night, I discovered in the Synology DHCP server's log files that it was assigning an address to the car (i.e. an ACK was being sent), but for some reason the Mach-E just wasn't accepting it.

Now I just need to figure out how to let Ford know about the incompatibility. Not that it matters to me anymore. I'll just keep using the DHCP server on my router, but it would be great if Ford could fix it so that nobody else runs into the same issue.

You could likely get dnsmasq to work if you customize it's config on the Synology. dnsmasq is a simple forwarder, and likely won't work with the default config. You would likely have to directly specify your ISP nameserver, and config the resolvr and hosts files.

This will be easy once we hit "the year of Linux on the desktop". In 2121. LOL.

 

[SkyWalker]

Good news. I finally got my Mach-E connected to my Wi-Fi.

My suspicion was correct. It was the DHCP server that the Mach-E didn't like. It appears as though there is an incompatibility between the Sync 4 software and the DHCP software that is running on the Synology NAS (Synology uses Dnsmasq for its DHCP server).

I disabled the DHCP server on my NAS and configured the DHCP server on my Ubiquity EdgeRouter X. Once I did that the Mach-E connected right away.

While I was troubleshooting the issue last night, I discovered in the Synology DHCP server's log files that it was assigning an address to the car (i.e. an ACK was being sent), but for some reason the Mach-E just wasn't accepting it.

Now I just need to figure out how to let Ford know about the incompatibility. Not that it matters to me anymore. I'll just keep using the DHCP server on my router, but it would be great if Ford could fix it so that nobody else runs into the same issue.

Thanks for investigating. I run Synology setup at my house although I let the Synology router do all the networking and not the NAS devices. Very helpful reminder that I do weird things on my network.

 

[timbop]

You could likely get dnsmasq to work if you customize it's config on the Synology. dnsmasq is a simple forwarder, and likely won't work with the default config. You would likely have to directly specify your ISP nameserver, and config the resolvr and hosts files.

This will be easy once we hit "the year of Linux on the desktop". In 2121. LOL.

Hey, in my house there are 2 ubuntu laptops, 2 winblows laptops, and an iMac. So, linux/unix is the dominant platform -clearly winblows is dying as a platform

 

[JamieGeek]

Hey, in my house there are 2 ubuntu laptops, 2 winblows laptops, and an iMac. So, linux/unix is the dominant platform -clearly winblows is dying as a platform

At least 4 Windows boxes here....its not dead yet

Ok yeah I have a few Raspberry Pi's running as well so some Linux.

 

[GoGoGadgetMachE]

Good news. I finally got my Mach-E connected to my Wi-Fi.

My suspicion was correct. It was the DHCP server that the Mach-E didn't like. It appears as though there is an incompatibility between the Sync 4 software and the DHCP software that is running on the Synology NAS (Synology uses Dnsmasq for its DHCP server).

Hmm. I use a Pi-Hole for DHCP which is forked dnsmasq. This is concerning. We will see what happens when I get my car in 3-4 years.

 

[timbop]

Hmm. I use a Pi-Hole for DHCP which is forked dnsmasq. This is concerning. We will see what happens when I get my car in 3-4 years.

I guess you'll just have to shut your Pi-Hole, then. ?

Sponsored