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

[methorian]

Cool! Thanks.

So, there may still be a value to the Mach E's wifi hotspot. Whether it's worth buying or not is another matter -- maybe just on months with planned road trips.

The hyphen working may send me back to the drawing board to see why I haven't been able to connect Marlin to our home WiFi.

It would certainly seem like there's quite a few issues at play with folks inability to connect to their home Wifi networks, so the hyphen thing may work for you and is still worth trying once Marlin is back home!

Sponsored

 

[methorian]

I have the same equipment and can't connect yet. Have tried 2.4 vs 5, single access point, no hyphens, and still no luck.

What encryption are you using? Any other settings I should look for?

I'm using the following settings on this network:

I have 2 APs - both newer Wifi 6 units. One Flex and one in-wall. Mach-E connects fine to both my 2.4Ghz and 5Ghz network. I do not have any special routing on these networks, it's my plain "private" network (versus my IoT network that's blocked off from my main network).

 

[eltonlin]

If one wanted to use the phone hotspot, you could always plug in the phone via USB to access CarPlay, correct?

 

[TheSteelRider]

I have the same equipment and can't connect yet. Have tried 2.4 vs 5, single access point, no hyphens, and still no luck.

What encryption are you using? Any other settings I should look for?

Hmm. Same here. I have a USG gateway and the AC-LR APs. But, I also have a spare Netgear router that I tried. No dice.

From debugging so far, the car *is* able to associate with the access points (and the Netgear), and then it requests a DHCP address, is given a DHCP address, then rinses and repeats.

I setup a tcpdump at my gateway listening on it's LAN port, and it sure looks like the Mach E doesn't like the DHCP offer that is getting returned. I have connected about 40 wireless devices on my network, never an issue (not to mention the many guests).

admin@Gateway:~$ sudo tcpdump -vv -i eth1 ether host 78:55:CD:E4:XX:YY
tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size 262144 bytes

16:15:24.172125 78:55:cd:e4:XX:YY (oui Unknown) > Broadcast Null Supervisory, Receiver not Ready, rcv seq 64, Flags [Poll], length 46
16:16:07.898369 78:55:cd:e4:XX:YY (oui Unknown) > Broadcast Null Unnumbered, xid, Flags [Response], length 46: 01 00
16:16:07.941498 EAPOL key (3) v1, len 117
16:16:07.956410 EAPOL key (3) v1, len 95
16:16:10.273100 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 78:55:cd:e4:XX:YY (oui Unknown), length 300, xid 0x24c30e0e, secs 2, Flags [none] (0x0000)
          Client-Ethernet-Address 78:55:cd:e4:XX:YY (oui Unknown)
          Vendor-rfc1048 Extensions
            Magic Cookie 0x63825363
            DHCP-Message Option 53, length 1: Discover
            Lease-Time Option 51, length 4: 4294967295
            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
            Client-ID Option 61, length 3: hardware-type 116, 63:75
16:16:10.280334 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 356)
    setup.ubnt.com.bootps > 10.13.40.20.bootpc: [udp sum ok] BOOTP/DHCP, Reply, length 328, xid 0x24c30e0e, secs 2, Flags [none] (0x0000)
          Your-IP 10.13.40.20
          Client-Ethernet-Address 78:55:cd:e4:XX:YY (oui Unknown)
          Vendor-rfc1048 Extensions
            Magic Cookie 0x63825363
            DHCP-Message Option 53, length 1: 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
16:16:13.291451 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 78:55:cd:e4:XX:YY (oui Unknown), length 300, xid 0x24c30e0e, secs 5, Flags [none] (0x0000)
          Client-Ethernet-Address 78:55:cd:e4:XX:YY (oui Unknown)
          Vendor-rfc1048 Extensions
            Magic Cookie 0x63825363
            DHCP-Message Option 53, length 1: Discover
            Lease-Time Option 51, length 4: 4294967295
            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
            Client-ID Option 61, length 3: hardware-type 116, 63:75
16:16:13.292614 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 356)
    setup.ubnt.com.bootps > 10.13.40.20.bootpc: [udp sum ok] BOOTP/DHCP, Reply, length 328, xid 0x24c30e0e, secs 5, Flags [none] (0x0000)
          Your-IP 10.13.40.20
          Client-Ethernet-Address 78:55:cd:e4:XX:YY (oui Unknown)
          Vendor-rfc1048 Extensions
            Magic Cookie 0x63825363
            DHCP-Message Option 53, length 1: 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

 

[Finkerton]

I have the same issue. Also Ubiquity APs. Separate 2.4/5GHz SSIDs. No funny options, setup basically the same as the picture above, but it refuses to connect.

 

[Finkerton]

For anyone that has this successfully working with Ubiquiti APs, could you also share your Site and Network settings? I don't have any fancy DHCP options enabled, although I do have IGMP snooping and UPnP. But as it seems to be a DHCP issue rather than a wifi one it would be helpful to see those settings as well in addition to the wifi ones in the pics above. TIA.

 

[TheSteelRider]

For anyone that has this successfully working with Ubiquiti APs, could you also share your Site and Network settings? I don't have any fancy DHCP options enabled, although I do have IGMP snooping and UPnP. But as it seems to be a DHCP issue rather than a wifi one it would be helpful to see those settings as well in addition to the wifi ones in the pics above. TIA.

My other thought was to create a dedicated new SSID off a single AP, then SSH into that AP and do a tcpdump from there. I guess there is a possibility that somewhere along my network something is happening that a tcpdump at the router / gateway won't catch. I'll chew on this and perhaps try it if/when I get a Round Tuit.

 

[TheSteelRider]

My other thought was to create a dedicated new SSID off a single AP, then SSH into that AP and do a tcpdump from there. I guess there is a possibility that somewhere along my network something is happening that a tcpdump at the router / gateway won't catch. I'll chew on this and perhaps try it if/when I get a Round Tuit.

Ok, I did that and it doesn't yield anything new. Car does a DHCP request, gets a DHCP offer, then does nothing.

For grins, I created a new subnet (in case it did not like 10. addresses). No dice, did not work either.

 

[Colorado Native]

Ok, I did that and it doesn't yield anything new. Car does a DHCP request, gets a DHCP offer, then does nothing.

Maybe the router is setting one or more DHCP options - like naming an NTP server - and the MME is confused by them.

Another thought - the MME might not like the DNS server your DHCP offer is providing. Maybe try tweaking the router to offer a public DNS server... Like 8.8.8.8.

I don't have a MME to check, but does it allow you to set a static IP address and set your own DNS server (thereby bypassing DHCP completely?)

 

[Colorado Native]

Ah - just noticed that you provided a dump of the DHCP request and resulting offer.

The DHCP server is not providing everything the MME is asking for - which is fine - but maybe the MME requires the time zone or the host name.

Gotta say that I'm perplexed the tcpdump Is providing a domain name instead of an IP address in this line:
Default-Gateway Option 3, length 4: setup.ubnt.com
... and not in this line:
Domain-Name-Server Option 6, length 8: 10.13.0.253,10.13.0.254
Never known tcpdump to do reverse lookups - always thought it provided unvarnished data.

 

[Colorado Native]

I also have a spare Netgear router that I tried. No dice.

Did you use the Netgear device as a router or as an access point? In other words, did you let the Netgear device manage the WiFi as it's own subnet so it could use the built-in Netgear DHCP server to respond to the MME?

 

[Finkerton]

I wonder if we could either get the thread marked as unsolved or start a new thread for Ubiquiti users. Some known Ford reps lurk on the forum and possibly with it marked as solved they aren't paying any attention to the issues we're having.

 

[methorian]

For anyone that has this successfully working with Ubiquiti APs, could you also share your Site and Network settings? I don't have any fancy DHCP options enabled, although I do have IGMP snooping and UPnP. But as it seems to be a DHCP issue rather than a wifi one it would be helpful to see those settings as well in addition to the wifi ones in the pics above. TIA.

Here's my site and network settings, Mach-E connects fine to my AP's.

Using a Dream Machine Pro on 1.9.0. Network is at 6.1.61.

DNS points to my Pi-Hole.

 

[TheSteelRider]

Did you use the Netgear device as a router or as an access point? In other words, did you let the Netgear device manage the WiFi as it's own subnet so it could use the built-in Netgear DHCP server to respond to the MME?

As an access point.

Yes it is looking like a DNS issue to me so I may try that or other experiments. Currently I have my USG setup as the DNS server as you can see in my packet trace.

 

[cmtaylor963]

As an access point.

Yes it is looking like a DNS issue to me so I may try that or other experiments. Currently I have my USG setup as the DNS server as you can see in my packet trace.

I have my USG set up as my DNS server and have not been able to connect my MachE. No hyphens in my SSID, and I tried separating the SSIDs between 2.4 & 5 GHz with no luck. I haven't had time to do much troubleshooting, so I added a spare AirportExpress router to create a separate network for my car in the meantime.

Sponsored