Force Local IP address not sending data to controllers

[johnty]

I have my controllers on a LAN connected to a second NIC card in my Windows 10 machine with an IPV4 address of 192.168.1.100.  With a browser I can see all of my controller's status pages so I know that my PC is talking to them.  In my Settings I have Force Local IP checked and the above IP address is selected.  When I play a fully rendered sequence in 2019.67 (64bit) and click on Output to Lights, nothing happens.

In regression testing, I find that 2019.31 works correctly.  Version 2019.32 does not nor does any newer release.  FSEQ Version is V2 in .31, V2 ZSTD in .67.  Nothing else is checked in Settings except for Save and Backup.

Could you investigate?  Let me know if you need more info.

[keithsw1111]

Go back to v1 files.

[johnty]

Go back to v1 files.

That doesn't fix the problem.  I tried all four FSEQ Version settings with no luck.

[dkulp]

Do you have "FPP Proxy" settings set for any controller?   That seems to be the only change between .31 and .32 that would have an impact on output.

[johnty]

Do you have "FPP Proxy" settings set for any controller?   That seems to be the only change between .31 and .32 that would have an impact on output.

That was the problem.  Deleting the proxy IP does let data flow to the controllers.  But does that have to be an either/or situation?  I've been running FPP in Bridge mode to test sequences from xLights but there's a problem with seeing controllers via proxy in FPP (Falcon F16V3 pages don't show correctly).  After I get some controller settings fixed and tested from my PC I'll move the LAN back to my Pi but all of the FPP Proxy settings in Setup will have to be re-added.  Is a mod possible to xLights to have the FPP Proxy IPs present and still have data going to a Local Ethernet card?

[dkulp]

The page display problem was fixed in FPP 3.5.4 I believe.

[johnty]

The page display problem was fixed in FPP 3.5.4 I believe.

The F16V3 status page now displays correctly in FPP 3.5.5 but the E131/Artnet and String Ports pages do not.  I'm creating a post of the FPP forum since this problem is off-topic.  Still, it is not a trivial exercise to move between the Pi and the PC to debug things.  A FPP Proxy option in the xLlights Setup Bulk Edit option would be nice if an IP address in that field is going to prevent data output to the NIC.

[dkulp]

It doesn't prevent anything, it just changes where the data goes.   If the proxy is set, it sends the data directly to the FPP instance which will then send it onto the F16V3.   Without the FPP proxy set, the data would go directly to the controller.     However, that means the FPP instance needs to be running in bridge mode.  Not remote or standalone.   

[johnty]

It doesn't prevent anything, it just changes where the data goes.   

Now I understand.  I thought data would go to both the proxy port and local NIC card but I guess there are configurations where that might cause problems.  I was running FPP in Bridge mode and it worked except for the F16V3 detail pages which appears to be fixed with a Falcon firmware update.

Until I can get that working, changing the network from the Pi to the PC requires deleting or adding dozens of FPP Proxy IP addresses one line at a time.  A Bulk Edit for that Setup field in xLights would be most beneficial.

Thanks for your help!