Issue - "Unable to connect" when connecting to WiFi (SOLVED)

TheSteelRider · Mar 16, 2021

Colorado Native said:
It's asking for it's host name, maybe you can setup a static IP entry in the USG so you can provide a hostname and possibly other requested values.

cmtaylor963 said:
I could see the MAC addresses in the Client List each time I tried to connect. I tried assigning a static IP, but that didn't work either. Most of my settings are stock as I only know enough to be dangerous.

Same here. I tried setting a static IP (in both my LAN and IoT networks). Same result.

Colorado Native · Mar 16, 2021

TheSteelRider said:
Same here. I tried setting a static IP (in both my LAN and IoT networks). Same result.

Did it result in a hostname being provided in the offer?

Otherwise, sorry I couldn't help resolve the issue. I'll be looking at this myself in June when and if my Infinite Blue MME shows up

TheSteelRider · Mar 16, 2021

Colorado Native said:
Did it result in a hostname being provided in the offer?

Otherwise, sorry I couldn't help resolve the issue. I'll be looking at this myself in June when and if my Infinite Blue MME shows up

I'm definitely not a DHCP/BOOTP expert, but I'm pretty sure the hostname is provided by the device in the Discover. I don't have any settings to override the provided hostname back to the client. On my LAN segment, the Offer provides a Domain Name, but on my IoT it does not, so that seems to say that doesn't matter.

I'll see if I can rig up something to use a different DHCP Server. Re-purposing my Netgear from an AP to a Router as a previous poster has suggested is a great idea, but is not desirable. I'd rather I think use one of my Pis and configure a quick DHCP server right quick (I already have Pi-Hole, so perhaps I'll make it be a DHCP server for one segment).

I think a scientific approach should be that I setup a new LAN segment, new SSID, and new DHCP server, and route the Mach E along that path. This way, I get a completely separate network that I can tcpdump off of for comparison. OR, Ford uses my tcpdumps from above and fixes it. OR they pay me a developer salary for my time thus far

Colorado Native · Mar 16, 2021

From your tcpdump we can see that the Mach-E does suggest a hostname, but also asks for it to be returned.

Code:

     Discover:
            Hostname Option 12, length 11: "mdm9650-tcu"
            Parameter-Request Option 55, length 11:
              Subnet-Mask, BR, Time-Zone, Domain-Name
              Domain-Name-Server, Hostname, Option 119, Netbios-Name-Server
              Netbios-Scope, Classless-Static-Route, Default-Gateway

   Offer:
           Server-ID Option 54, length 4: setup.ubnt.com
            Lease-Time Option 51, length 4: 86400
            Subnet-Mask Option 1, length 4: 255.255.0.0
            Domain-Name Option 15, length 22: "REDACTED"
            Domain-Name-Server Option 6, length 8: 10.13.0.253,10.13.0.254
            T119 Option 119, length 24: 225732709,1937007973,1819437412,1701971044,1684960003,1852142592
            Default-Gateway Option 3, length 4: setup.ubnt.com

This is reasonable, since the local DNS server has the final say about the hostname as it manages the resolving. I suggested the static IP change to allow you to provide a local hostname, hoping it would get sent back to the MME. I doubt this is the problem, so no big deal.

I like the Pi-Hole DHCP idea.

RonTCat · Mar 16, 2021

Colorado Native said:
From your tcpdump we can see that the Mach-E does suggest a hostname, but also asks for it to be returned.

Code:

Discover: Hostname Option 12, length 11: "mdm9650-tcu" Parameter-Request Option 55, length 11: Subnet-Mask, BR, Time-Zone, Domain-Name Domain-Name-Server, Hostname, Option 119, Netbios-Name-Server Netbios-Scope, Classless-Static-Route, Default-Gateway Offer: Server-ID Option 54, length 4: setup.ubnt.com Lease-Time Option 51, length 4: 86400 Subnet-Mask Option 1, length 4: 255.255.0.0 Domain-Name Option 15, length 22: "REDACTED" Domain-Name-Server Option 6, length 8: 10.13.0.253,10.13.0.254 T119 Option 119, length 24: 225732709,1937007973,1819437412,1701971044,1684960003,1852142592 Default-Gateway Option 3, length 4: setup.ubnt.com

This is reasonable, since the local DNS server has the final say about the hostname as it manages the resolving. I suggested the static IP change to allow you to provide a local hostname, hoping it would get sent back to the MME. I doubt this is the problem, so no big deal.

I like the Pi-Hole DHCP idea.

Should I post this on Stack Overflow, and get 9 "you so dumb" replies and one actual solution?

Finkerton · Mar 16, 2021

You could, but without knowing which dhcp client and version is in the car, it seems unlikely anyone would know why it would reject the offer.

Still, I've been wrong before, once or twice or three million times. Someone might have ideas based on some obscure bug they hit before. Might also be worth posting on the ubnt forums.

TheSteelRider · Mar 16, 2021

Finkerton said:
Might also be worth posting on the ubnt forums.

Great point! I'd like to get a dump of a working Discover / Offer though first so the question can be narrower, e.g. the diff of the two

americanflannel · Mar 30, 2021

Has anyone figured out a fix yet?
I am also having issues and of course I am running a whole Unifi setup as well.

cmtaylor963 · Apr 3, 2021

Ok, I have a Unifi USG and multiple Unifi APs, and had not been able to connect my Mach E to my wifi network. My DHCP range is set to 192.168.1.x. Today, I created a new network with a DHCP range of 10.0.1.x, and my car connected no problem!

For others with Unifi gear, what is your DHCP range?

TheSteelRider · Apr 3, 2021

cmtaylor963 said:
Ok, I have a Unifi USG and multiple Unifi APs, and had not been able to connect my Mach E to my wifi network. My DHCP range is set to 192.168.1.x. Today, I created a new network with a DHCP range of 10.0.1.x, and my car connected no problem!

For others with Unifi gear, what is your DHCP range?

I tried 10.13.255.255 and 172.16.0.255 and neither worked.

methorian · Apr 4, 2021

cmtaylor963 said:
Ok, I have a Unifi USG and multiple Unifi APs, and had not been able to connect my Mach E to my wifi network. My DHCP range is set to 192.168.1.x. Today, I created a new network with a DHCP range of 10.0.1.x, and my car connected no problem!

For others with Unifi gear, what is your DHCP range?

Mine's 192.168.50.1/24 for the network the Mach-E connected to without issue from Day 1 (Unifi UDM Pro as DHCP, Pi-Hole for DNS).

Ford Mustang Mach-E Issue - "Unable to connect" when connecting to WiFi (SOLVED) 1617545080131

Finkerton · Apr 5, 2021

methorian said:
Mine's 192.168.50.1/24 for the network the Mach-E connected to without issue from Day 1 (Unifi UDM Pro as DHCP, Pi-Hole for DNS).

The issue has seemed to be affecting those with USGs as the router, whereas those with the UDMs seem to be fine.

capt_jak_harkness · Apr 6, 2021

cmtaylor963 said:
Ok, I have a Unifi USG and multiple Unifi APs, and had not been able to connect my Mach E to my wifi network. My DHCP range is set to 192.168.1.x. Today, I created a new network with a DHCP range of 10.0.1.x, and my car connected no problem!

For others with Unifi gear, what is your DHCP range?

Has your MME continued to stay connected to your wifi with this fix?

cmtaylor963 · Apr 7, 2021

capt_jak_harkness said:
Has your MME continued to stay connected to your wifi with this fix?

Yes, but only when it's on the separate network. It won't connect to my main network no matter the IP range. I think there's another device on my main network that it doesn't like. DHCP is handled by my UniFi USG, and I don't have any other DHCP servers (that I know of.)

dml105 · Apr 12, 2021

OK, who wants to help me figure this out? Can't connect. Verizon FiOS router + a couple additional access points. WPA2 (AES+PSK) encoding. Shadowfax's MAC address is the one that ends in a2:03.

Here's the General log in my FiOS router:

Code:

Apr 13 02:28:21 2021named[13085]err<139>zone Fios_Quantum_Gateway/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 13 02:28:21 2021named[13085]err<139>zone localrp/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 13 02:28:21 2021named[13085]err<139>zone fios-router.home/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 13 02:28:21 2021named[13085]err<139>zone 1.168.192.in-addr.arpa/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 13 02:28:16 2021dhcpdinfo<158>192.168.1.204 is leased for 86400 seconds, renew in 0 seconds, rebind in 0 seconds
Apr 13 02:28:16 2021dhcpdinfo<158>DHCPACK on 192.168.1.204 to 78:55:cd:e5:a2:03 (mdm9650-tcu) via br-lan
Apr 13 02:28:16 2021dhcpdinfo<158>DHCPREQUEST for 192.168.1.204 from 78:55:cd:e5:a2:03 (mdm9650-tcu) via br-lan
Apr 13 02:28:16 2021named[13085]err<139>zone Fios_Quantum_Gateway/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 13 02:28:16 2021named[13085]err<139>zone localrp/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 13 02:28:16 2021named[13085]err<139>zone fios-router.home/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 13 02:28:16 2021named[13085]err<139>zone 1.168.192.in-addr.arpa/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.

And the Advanced log in my FiOS router:

Code:

imeEvent-TypeLog LevelDetails
Apr 13 02:22:24 2021bhr4err<11>DhcpServerLog: DeleteMacs=[sed '/hardware ethernet \(00:80:92:c5:e8:ad\);/d' /media/config/dhcpd/leases.tmp2 > /media/config/dhcpd/leases.tmp]
Apr 13 02:22:22 2021bhr4err<11>DhcpServerLog: DeleteMacs=[sed '/hardware ethernet \(00:80:92:c5:e8:ad\|78:55:cd:e5:a2:03\|b6:a4:bb:e8:e4:e0\);/d' /media/config/dhcpd/leases.tmp2 > /media/config/dhcpd/leases.tmp]
Apr 13 02:21:54 2021bhr4err<11>DhcpServerLog: DeleteMacs=[sed '/hardware ethernet \(00:80:92:c5:e8:ad\|6e:dc:61:37:7f:2a\);/d' /media/config/dhcpd/leases.tmp2 > /media/config/dhcpd/leases.tmp]
Apr 13 02:21:47 2021bhr4err<11>DhcpServerLog: DeleteMacs=[sed '/hardware ethernet \(00:80:92:c5:e8:ad\|78:55:cd:e5:a2:03\|80:ea:96:e6:b7:18\|d4:2c:0f:f7:54:76\|e2:37:bf:58:e3:70\);/d' /media/config/dhcpd/leases.tmp2 > /media/config/dhcpd/leases.tmp]

And here's the LAN DHCP log:

Code:

Apr 13 02:28:16 2021dhcpdinfo<158>192.168.1.204 is leased for 86400 seconds, renew in 0 seconds, rebind in 0 seconds
Apr 13 02:28:16 2021dhcpdinfo<158>DHCPACK on 192.168.1.204 to 78:55:cd:e5:a2:03 (mdm9650-tcu) via br-lan
Apr 13 02:28:16 2021dhcpdinfo<158>DHCPREQUEST for 192.168.1.204 from 78:55:cd:e5:a2:03 (mdm9650-tcu) via br-lan

Issue - "Unable to connect" when connecting to WiFi (SOLVED)

TheSteelRider

Well-Known Member

Colorado Native

Active Member

TheSteelRider

Well-Known Member

Colorado Native

Active Member

RonTCat

Well-Known Member

Finkerton

Well-Known Member

TheSteelRider

Well-Known Member

americanflannel

Well-Known Member

cmtaylor963

Well-Known Member

TheSteelRider

Well-Known Member

methorian

Well-Known Member

Finkerton

Well-Known Member

capt_jak_harkness

Well-Known Member

cmtaylor963

Well-Known Member

dml105

Well-Known Member

Similar threads