FPP VS eero home network Static IP challenges

[R6Taz]

Hi Folks,

I just switched my home network to eero routers and am having a hell of a time trying to set a static IP on my FPP that I use on a RaspPi to run my Hinks controlers as a PROXIE server..   I understand there are challenges with FFP and I.P. addresses but it is way above my knowledge level..  I heard disabling USB tethering my stop the conflict etc .. I cannot change my home netowrk settings as i have way too many devices connected and run an office from home.. can anybody point me in the right direction? Thanks Oh my eero network is 192.168.7.

[JonD]

Welcome to the forum.  The 192.168.7.x network range will conflict with some tethering options.  Not really an FPP thing, and more of a network problem in general.  It would be best to not use IP ranges in conflict, but understand you not wanting to change all of your IPs.  You could have other issues down the line, as tethering is a common and handy feature with many devices. 

The follwing IP ranges are best to avoid.
192.168.0.x (common)
192.168.1.x (common)
192.168.6.x (tether)
192.168.7.x (tether)
192.168.8.x (tether)
192.168.100.x (cable modems)
192.168.254.x (common ISP modems)

If your home network is using the 192.168.7.x network range you may need to turn tethering off.  Otherwise that network would be local to FPP device, and data will not route correctly to your home network.  It should not hurt anything to turn tethering off, other than it may be a little harder to setup the FPP after a fresh installation.

https://falconchristmas.github.io/FPP_Manual.pdf   Page 22

Note: If your home router has an IP address with a subnet of 192.168.6.xxx,
192.168.7.xxx or 192.168.8.xxx then your FPP will likely have problems communicating
in these environments. Those subnets are the default subnets used by Windows, Mac
and Linux for USB tethering and could cause conflicts. You should change your home
network to a different subnet to avoid problems.

[AAH]

Changing from the common 255.255.255.0 netmask to 255.255.0.0 may help with your issues as that can allow communications across different IP ranges. ie with 255.255.255.0 netmasks on the relevant devices you can communicate between 192.168.0.x and 192.168.1.x or anywhere in the 192.168.x.x range.

[JonD]

Changing from the common 255.255.255.0 netmask to 255.255.0.0 may help

Expanding the local range can help in some situations, but not sure that would help with this one.  

The tether would have a triple 255 subnet with a new image install, and you would have a conflict at boot up.  Might be possible to change, but don't think it can be done from the GUI, and if possible would be an advance configuration.  Most likely way more work that just disabling the tether, but interested in learning more if you have done this.