FPP IP Forwarding

[clampman]

I know this topic has been beat to death, but I had a question.  I'm using the FPP v7.3.1 firmware on a Raspberry Pi3B. I have setup using the videos I've found on Youtube.  I am using wlan0 to connect to my router, and the eth0 to connect the controller.(Falcon F16V3)  Of course, I'm trying to connect to the controller wirelessly from my laptop.  For IP Forwarding, I have set the eth0 interface to "Forwarding" and I'm not sure what I should use for wlan0.  Should it also be "Forwarding" or "Masquerading/NAT"?

Thanks for the help.  

[JonD]

I just use the proxy feature.  FPP\Status-Control\ProxySettings.  Enter the IP of the controller, and then click on the link to manage it.  In xlights, enter the controller as the actual ip, and then enter the FPP wifi ip into the proxy settings.  You don't need forwarding at all in most cases.

[clampman]

I'll give that a try when I get home from work.  Thanks!!

[JonD]

IP forwarding settings are not backed up.  They will typically survive an upgrade, but will not restore to a fresh install.  The proxy settings should restore from backup if ever needed.  If it works, could make future upgrades less of a hassle for you.

[nick]

For this to work for me, I have wlan0 setup for forwarding and IP Forwarding for eth0 is off. wlan0 gets a 192.168.1.X address, and eth0 and my controllers are all on the 192.168.2.0 subnet. I then setup persistent static routes on my laptop or desktop computer to go through 192.168.1.X to reach any address on the 192.168.2.0 subnet.

[Poporacer]

For IP Forwarding, I have set the eth0 interface to "Forwarding" and I'm not sure what I should use for wlan0.  Should it also be "Forwarding" or "Masquerading/NAT"?

You want the wlan0 to have the forwarding, not the eth0. Masquerading/NAT will allow the downstream device to have access to the internet as well, this isn't much use for the F16 but either one will work just fine.