This things going to be the death of me! Chasing an IT Wizard

[ausnz]

Hi there. In short I'm 3 days in and still cant figure where i have gone wrong. I am trying to have my PI 4 wifi from my computer and ethernet to my Beagle Bone Black controller (with hanson 123 48 output controller). I have followed the steps i believe required but in x lights i can upload data to my PI playlist on xlights using fpp connect but not fpp connect xlights to the beagle bone. If i ethernet to the beagle i can put the playlist in there and it will play from the pi schedule or if i manually hit play in the pi ip address.
I have setup my network as follows: my home router gateway is 192.168.1.1 I have set a static route in my router as network host 192.168.200.0 mask 255.255.0.0 and gateway 192.168.1.68. For just static address the pi and beagle in Asus router (PI 192.168.200.1) and Beagle (192.168.200.2) and left gateway as default. i have command prompt as administrator -p add 192.168.200.0 mask 255.255.0.0 192.168.1.68
I have put in the Pi itself ETh0 IP 192.168.200.1 mask 255.255.0.0 and left the gateway empty, Wlan0 I have IP 192.168.1.68 mask 255.255.0.0 and gateway 192.168.1.1 . The Beagle Bone Black.

I have no idea where I have gone wrong from the Falcon instructions ( using v6.2) I have enabled port forwarding but am also unsure of exactly how i should have the controllers configured in x lights and if perhaps that is where my issue lies.

Just to recap - I can play my playlist remotely from my computer and put new songs on the PI. Cannot play new songs that I have put on however unless i plug an ethernet lead into the beagle and upload same song. I have no local access to the beagle so cant see anything in there unless i ethernet to it. I can access the Pi no problem via the 192.168.200.1 IP.

Any help would be greatly appreciated

 

[Katekate]

sounds like your pi is not setup to route traffic to the beaglebone

 

[tooms]

Your netmask's are a bit out, if using a mask of 255.255.0.0, 192.168.1.x and 192.168.200.x are in the same network.

Maybe try shortening the mask's to 255.255.255.0

Using 255.255.0.0 as your mask is making your 192.168 subnet start and finish at 192.168.0.1 - 192.168.255.255

 

[DarkwinX]

Just confirming - do you have everything on the same network or do you have 2 networks - one for your home devices and one for your lights which is connected to the Asus router?

If there's two what is your general home network IP Range?

If there's only one you don't really need to setup static routes between devices.

 

[ausnz]

Your netmask's are a bit out, if using a mask of 255.255.0.0, 192.168.1.x and 192.168.200.x are in the same network.

Maybe try shortening the mask's to 255.255.255.0

Using 255.255.0.0 as your mask is making your 192.168 subnet start and finish at 192.168.0.1 - 192.168.255.255

Thanks Tooms, i’ll change that all out and see how it reacts, i see what your saying there.

 

[Skymaster]

Pop into the zoom room if you do get stuck, in there some of us can help take a look at the exact config and see where it may be "not quite right"

 

[BAZMick]

192.168.1.68. For just static address the pi and beagle in Asus router (PI 192.168.200.1) and Beagle (192.168.200.2)

You need to set the proxy setting in xlights for the beagle bone to 192.168.1.68 and then on the pi under the Status tab go to proxy settings and add the beagle bone 192.168.200.2

Edit, you also need to check the 'Enable Routing between network interfaces' box in Status/Interface Routing tabs on the pi

 

[Pavle]

'Enable Routing between network interfaces' box in Status/Interface Routing tabs on the pi

This has been changed in FPP 6.x IP FORWARDING and you need to set it to forward.
You shouldn't need to setup proxy at all as far as my config went.



You will however need to activate advance user interface level to access the IP forwarding option

 

[Skymaster]

Routing / IP Forwarding vs Proxy is all dependent on whether you'd able to set up a static route back from your home network towards your show network. This can be hardware dependent if trying on the home router, or can be done on the console of a Windows/Mac/Linux workstation if only that machine needs access.

• Proxy does NOT require that configuration, and will do the double-hop for you with the FPP software, and no configuration required on your controllers OR your home network, only FPP needs to know about the controllers. xLights will also need to be told about the proxy.
• IP Forwarding requires configuration on FPP (to enable the Operating system level functions), and then configuration on the controller (FPP as default gateway) and on your home network (route to reach the show network) in order for it to operate.

IP forwarding is "native networking" at layer 3, whereas proxy is layer 7 application-specific routing. Both have their advantages and disadvantages.

Looking at the above initial configuration done by @ausnz, it appears that the layer 3 IP routing path is being taken.

The suggestion by @tooms of fixing the netmask in both the Pi (on both interfaces) and the Beaglebone, as well as the static route is the most pertinent here - right now devices will think they are on the same network when they are not.