Fordpass always connecting via cellular and not wifi

[bub]

See if pfsense shows two devices pop up (two new MAC addresses) when you turn on WiFi in your truck. If they both get IP addresses and you can ping them you're in good shape. If one of them just sits there sending DHCP DISCOVER over and over again...you have the problem.

I have two mac addresses in my DHCP lease table from my truck with the hostname "SYNC".
With the truck turned on I can see one of them in my access point management portal.
But neither of the DHCP lease addresses ping.

The trucks wifi page, if you hit the question mark on the ssid. It justs one of the leases. So it seems to be getting a lease. But either its not working, or the truck is just not responding to pings.

I'm not totally convinced the wifi is working properly.
I'm curious if you can point me to where you discovered these wifi problems?

Sponsored

 

[bub]

Ah. Search works.
https://www.f150lightningforum.com/forum/threads/sync-not-connecting-to-home-wifi.1095/#post-175623

Also, it seems even though my Domain settings in pfsense DHCP is blank. It defaults to the global pfsense domain. So i am serving up a domain via DHCP.

I think i'll try making a guest vlan for this truck with bland dhcp settings and see how that goes.

 

[tls]

Ah. Search works.
https://www.f150lightningforum.com/forum/threads/sync-not-connecting-to-home-wifi.1095/#post-175623

Also, it seems even though my Domain settings in pfsense DHCP is blank. It defaults to the global pfsense domain. So i am serving up a domain via DHCP.

I think i'll try making a guest vlan for this truck with bland dhcp settings and see how that goes.

Yeah - there's that thread, and a few others in Mach-E forums. I'd observed something similar running packet captures but I hadn't pinned it down to the domain name yet.

What I saw was one of the two client devices in the truck repeatedly receiving perfectly good DHCP OFFER messages and just immediately sending another DISCOVER. If you really dig around you'll find that QNX has its own 100% from-scratch DHCP client and there are other reports of this behavior when it gets options it doesn't like (the standard says it has to ignore them - but who needs standards - and anyway it is *asking for* the domain name option - this is why not to reinvent the wheel - but I digress).

I was pretty sure once things started working, both addresses were pingable. Also that only one client was sending hostname SYNC while the other was... something different. But I just checked and my truck, which is definitely online by WiFi as there's no cell coverage where it's parked, is now showing only one lease on my DHCP server, with client name SYNC, and I cannot ping it from the router. I wonder if they made changes since last winter when I first looked at this? I know they gave some very curious explanations of what they recently did to address the Home Integration System problems that almost sounded like they might have reworked the external connectivity architecture of the truck so things were now gatewaying through each other... Hmmm.

Sponsored