News:

LATEST RELEASE:  FPP 5.5 - Download from here - https://github.com/FalconChristmas/fpp/releases/tag/5.5

+-+-

+-User

Welcome, Guest.
Please login or register.
 
 
 
Forgot your password?

+-Site Stats

Members
Total Members: 15231
Latest: Manuelpereyra78
New This Month: 20
New This Week: 4
New Today: 2
Stats
Total Posts: 124534
Total Topics: 15147
Most Online Today: 58
Most Online Ever: 7634
(January 21, 2020, 02:14:03 AM)
Users Online
Members: 3
Guests: 35
Total: 38

Bridging networks so show network can access internet

Started by townshendlights, June 25, 2022, 06:49:57 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Poporacer

Quote from: k6ccc on June 28, 2022, 05:19:22 PMAs I understood it, he is using the built in WiFi in the Pi to connect to his normal home network, and the wired interface and then D-Link Access Point as a separate WiFi network to communicate from the FPP instance to the ESPixel devices
I agree, that is what I understand, but the question is why?

Quote from: k6ccc on June 28, 2022, 05:19:22 PMKeeping the E1.31 traffic on a separate network is not a bad plan. 
I somewhat agree, but that can normally be accomplished by simply using a switch... But sending E1.31 data over Wi-Fi is usually not a good plan.

Quote from: k6ccc on June 28, 2022, 05:19:22 PMPersonally all my E1.31 traffic is on a completely separate network - although in my case it is all wired.
Which is a good plan!
If to err is human, I am more human than most people.

k6ccc

Quote from: Poporacer on June 28, 2022, 05:24:15 PMBut sending E1.31 data over Wi-Fi is usually not a good plan.
Unless you are trying to send to devices that are WiFi only - like ESPixelSticks (what he is trying to do as I understood it).
Using LOR (mostly SuperStar) for all sequencing - using FPP only to drive P5 and P10 panels.
My show website:  http://newburghlights.org

Jim

Poporacer

Quote from: k6ccc on June 28, 2022, 05:41:49 PMUnless you are trying to send to devices that are WiFi only - like ESPixelSticks
Version 4 of the Firmware supports FPP MultiSync. But if not using the Multisync, it doesn't take too many of these devices before you start to notice lag or other issues... Pixel Data over Wi-Fi isn't a good plan unless it is an extremely small show.
If to err is human, I am more human than most people.

townshendlights

Quote from: Poporacer on June 28, 2022, 05:24:15 PM
Quote from: k6ccc on June 28, 2022, 05:19:22 PMAs I understood it, he is using the built in WiFi in the Pi to connect to his normal home network, and the wired interface and then D-Link Access Point as a separate WiFi network to communicate from the FPP instance to the ESPixel devices
I agree, that is what I understand, but the question is why?
 I'm going to answer these the best I can.
I really appreciate everyone's input. :)
I don't want to have show data on my home network as my home network has massive data use and I didn't want the show to be effected. 


Quote from: k6ccc on June 28, 2022, 05:19:22 PMKeeping the E1.31 traffic on a separate network is not a bad plan.
I somewhat agree, but that can normally be accomplished by simply using a switch... But sending E1.31 data over Wi-Fi is usually not a good plan.
I have very good success with a WIFI show. I don't have any lag or issues as I'm using DDP.

Quote from: k6ccc on June 28, 2022, 05:19:22 PMPersonally all my E1.31 traffic is on a completely separate network - although in my case it is all wired. Which is a good plan!

I didn't want to run a wired network as it just doesn't suit my property to run cables everywhere.

The only reason I wanted the FPP to have internet connection is so people watching the show can use falcon remote to choose songs etc, otherwise the show works great on its own network.


bloojoop

Thank you for the diagram as that helps a lot.   Yes this is a slightly different and more complex setup than most and not specifically accounted for in the manual.  Anyway, I'll do my best to describe what you need here: 
on the raspberry pi, the wlan0 interface will connect to your home network (only one radio on the rpi so if connecting to existing network, it cannot operate as a access point).  The wlan0 would need to be on teh 192.168.1.0 network as you described but the eth0 needs to be on the show network of 192.168.0.0 NOT 192.168.100.0 as you listed it in your diagram and as other have pointed out. Try these settings: 
rpi
wlan0 - home network
192.168.1.100
255.255.255.0
192.168.1.1
eth0
192.168.0.100
255.255.255.0
<blank>
routing between interfaces enabled.
Also set DNS to either your router of 192.168.1.1 or public dns such as 8.8.8.8

The static route on your home router needs to direct the show network of 192.168.0.0 to the rpi at 192.168.1.100. so the GW on the route statement should be 192.168.1.100 not 192.168.1.1 as you described in in your drawing. something like : 
route 192.168.0.0 mask 255.255.255.0 gw 192.168.1.100... 
This will send the traffic for 192.168.0.<x> to the pi where it can send it to the show AP.  
Now all your show controllers need to have an ip address on the .0 network like you mentioned but their gateways need to be the eth0 ip address of the ip like : 
192.168.0.20
255.255.255.0
192.168.0.100 
if you can set the dns on the remote controllers, set them to your home router or public dns just like you would for the pi.  

you basically will have two networks routed by the pi in this setup.  If you need more help, you can swing by the xlights zoom room and the helpers can get you setup if needed. 
--Ron A.

townshendlights

@bloojoop 
Thank you so much, however I think I've not quite got something right.
I've attached a revised diagram with the settings I've changed to match what you put in your post.
You cannot see attachments on this board.

bloojoop

so what is NOT working that you expect to work... Originally you wanted FPP to be able to communicate out to the internet.  Is that not working?  On the dns tab, hit the ping button next to 8.8.8.8 and see that responds.  If so then it is getting to the internet.  Can you communicate with the d1 based controllers from your laptop?    Are you available to join the xlights zoom room, we should be able to help in real time and get this figured out if needed.  Or is all of that working and just remote falcon not working?  now that you have a standard network configuration (wired separate show network, but with a AP in the mix).  We can look at it piece by piece and see where it is not working. 
--Ron A.

Support FPP

+- Recent Topics

PiCap abnormal conditions: Disabling my IP address by bloojoop
Today at 01:36:17 PM

FPP CANT REACH CONTROLLER THROUGH ETHERNET IP ADDRESS by k6ccc
Today at 12:33:42 PM

Testing RGB's by ecbrum
Today at 12:09:32 PM

Beagle Board x36 networking issues. by rayster
Today at 11:40:19 AM

Touchscreen by Poporacer
Today at 10:46:45 AM

BBB Display by TracyDockter
Today at 07:13:26 AM

Customizable Virtual Matrix to Drive Video Screens by CaptainMurdoch
August 18, 2022, 02:38:11 PM

Pi Top on sale by CaptainMurdoch
August 18, 2022, 11:49:33 AM

FPP 6.0 Released! by Poporacer
August 17, 2022, 05:17:25 PM

Just putting this out for research? by Poporacer
August 17, 2022, 10:53:09 AM

Powered by EzPortal
Powered by SMFPacks Menu Editor Mod