FPP 9.5-1 causing 192-168-8-1 for most WiFi IP

[Sawdust]

Help !!!
Feeling FPP9.5 is playing with WiFi drivers again.  I've lost most connections with FPP9.5-1 assigning IP address to 192.168.8.1.  Either DHCP or Static IP in FPP, after forced reboot they show 192.168.8.1  See below screenshot.

I'm running 2 networks and it is happening on both.  This is shutting down my FPP.
When old WiFi dongle drivers were dropped, I replaced all my dongles with new TP-Link Archer T3U AC1300.  I thought these were Linux supported, but I can't find the spec's to say they are...they are Windows 10/11 and Mac 10.9-10.14 supported.

Do I need to replace my dongles again - (My T3U's adapters ran the 2025 Halloween and Christmas shows without issues)
if yes - which ones are good.  Maybe a FPP 9.5 setting I'm doing wrong.
 - - Any help would be appreciated.
  Happy New Year

You cannot view this attachment.

[Sawdust]

hmmm...not dongles...PI4 (FPPM) is down too, and it has internal wifi.  Hardwired on 10-0-11-4

Also hardwire network is not shown on FPPG.  Should have 10-0-11-21

See FPPM & FPPG in below screen shot.

[allknowing2012]

This might be the known issue that is being worked on..
https://github.com/FalconChristmas/fpp/issues

[Sawdust]

Not sure this is the same as the known issue.  They just don't connect WiFi. Yes, I'm not connecting also, but the real issue here is assigning IP 192-168-8-1 to most adapters.  I thought 192-682-8-1 was computer hardwired direct to FPP.

[allknowing2012]

.8.1 is the tethered hotspot when it cant connect to your home wifi SSID.  USB tether is another IP. Are you able to get to master branch and try the fix posted yesterday - or is that not possible?

[Sawdust]

I have several FPP setups.  I can connect to about 1/2 via normal WiFi. 
I connect to a fault IP via ethernet hardwire and I sometimes can fix an IP to match the static address.  I then can use that IP to access the FPP.  I can access all the pages and play a sequence, but if I boot it goes back to 192.168.8.1.  I hear you on tethering, but at least 2 of the 8.1's setups have tether disabled.

xFinity just back up. . .went down for repairs earlier.  Could their router be an issue not setting ip or correct ip...

allknowing2012 thanks for the inputs.


Internet just tested true - Did an IP update and network restart.  Correct IP shown = reboot - YEAH! IP is still there.  Maybe it was xFinity and router not assigning IP correctly.

Will watch and test overnight to be sure.

[Sawdust]

It's Back...

Workaround.........
allknowing2012 . . . you pointing to tethering appears to have helped.  I disable tethering for those 192.168.8.1 IP's.  I then updated and restarted the network until the correct iP appeared for wlan0. Yeah, they now boot as static or DHCP as assigned.  So far, they're working, but I'll watch a couple days.  Yesterday they seem to have fixed themselves, but this morning they're broken again.  Maybe tethering is grabbing the IP assignment before my router has a chance.

[Sawdust]

SOLVED: I feel something in FPP v9.5.1 tethering is either slowing the wifi connection or the if-no-connection tethering setting is set to check (for connection) too soon in the boot process.

Repeatable: Settings and connections that have worked fine suddenly starting assign 192.168.8.1 to most all wlan0 on FPP v9.5-1.  Turning tethering to disable and doing several network connection updates, before the forced reboot, will reassign correct IP and will hold those IPs after reboot.

[Sawdust]

Fix is out  v9.5-1-1