Sean Meighan
Software => Xlights Setup => Topic started by: Santacarl on January 02, 2020, 11:20:20 PM
-
Hey All,
Can someone remind me what the "FPP Proxy" column in the setup tab should point to? I can't remember if it is the FPP IP itself or the router IP that the column is referring to.... Thanks...
-
https://nutcracker123.com/forum/index.php?topic=6530.0
-
https://nutcracker123.com/forum/index.php?topic=6530.0
Thanks for the response. I had already read that and still wasn't clear.... I don't speak 'network' and references like "FPP instance that has the ip address configured." go right over my head....never heard of an "FPP instance" so that confused me even more..... :-[
-
An FPP instance is an installed FPP
-
An FPP instance is an installed FPP
Thanks Jim.... So if I'm understanding that means to put the IP address of the FPP itself in that column? Sorry to be so anal retentive but I'm a literalist who doesn't handle concepts well until I see the 'steps' on how to there.....
-
I think it's meant to connect to other FPPs (like remotes) or Falcon controllers through the Pi (main one) that your network connects to. If you only have the one pi....you don't need to add anything in the proxy. If you have Falcon controller you can add the ip address of those.
-
The wifi address of fpp. (You already have the controller address in the main portion of the setup info)
-
The wifi address of fpp. (You already have the controller address in the main portion of the setup info)
Yeah.....I was posed to post that very thing....the controller address is already in the "Port" column of the "Setup" tab since I'm using unicast..so I was about to ask why it would be needed in the "FPP Proxy" column too.....
I'm guilty of sometimes just trying different things until I get it to work without fully understanding the 'why' part of how it work..that comes back to bite me sometimes... ::)
-
I'm still confused on this proxy thing.....
My Show Network is on 192.168.1.xx
I connect to my Pi (Master) wifi from my home network 10.0.0.xx
Without anything in the Proxy Settings I can not reach the setup pages of my Pi (Remote) or none of the Falcon controllers through my home network. Correct?
Putting the ip addresses of my Remote and controllers in the proxy setting I can now reach the their setup pages through my home network even though they're only connected to the show network.
Am I thinking about this wrong?
-
Sounds like you understand it .. it was a feature added so users dont have to mess with adding routing info to get from their home network into a show network.
So
Home Browser/etc -> proxy thru Pi on wifi -> Out Pi on ethernet -> show network/all your controllers.
-
Putting the ip addresses of my Remote and controllers in the proxy setting
So, how do you put both he remote AND controllers in the proxy setting? Sorry....as I mentioned above I'm extremely literal.....
-
This is the way mine looks.....
-
This is the way mine looks.....
Just so I can get a clear picture what do the .22/.39/.29/.155 IP's go with?
-
This is the way mine looks.....
Just so I can get a clear picture what do the .22/.39/.29/.155 IP's go with?
.22 is a pi in remote mode for my matrix
.39 & .29 are Falcon controllers
.155 is a pi in standalone mode for my Tune in sign.
-
This is the way mine looks.....
Just so I can get a clear picture what do the .22/.39/.29/.155 IP's go with?
.22 is a pi in remote mode for my matrix
.39 & .29 are Falcon controllers
.155 is a pi in standalone mode for my Tune in sign.
Thanks for the clarification Rudy..... That screenshot is from an FPP? It just dawned on me that I was initially trying to figure out how to set the proxy in XL...Well....I AM confused now! Haha... ???
-
It is on the FPP....then in Xlights you can click the controller in the setup section and add the proxy address toward the bottom of the window. For me, it's like 10.0.0.137/proxy/192.168.1.39
-
Really if you don't know what it is you don't need it. What problem are you trying to solve? You only set the proxy if you have a controller that cannot be reached without going through another IP address as a middle man. If that's not the problem you are trying to solve then leave it alone.
-
Really if you don't know what it is you don't need it. What problem are you trying to solve? You only set the proxy if you have a controller that cannot be reached without going through another IP address as a middle man. If that's not the problem you are trying to solve then leave it alone.
Thanks for the explanation Gil. I started thinking about this while pondering situation where I have a few controllers I can't 'see' on my home network.
I use a stand alone network for my display. It uses 192.168.2.xxx addresses. My home network uses 192.168.0.xxx addresses.
Oddly enough if I take the cat 5 cable out of my show network/router and plug it into the home network/router I CAN 'see' all my Falcon Controllers but I CAN NOT 'see' my San Devices (E682's). I like accessing the show controllers with my home network computer because it's much easier to make changes than with my show network which I access with my phone.
So...if in XL I enter the IP for the FPP in the FPP proxy column where I use the E682 ports does that the FPP the 'middle man' you're referring to that will allow me to access the E682's with my home network?
-
I would just test it. You know I used to have a separate show network but it became a problem after I added security cameras and wanted the same computer to see the cameras on the home network and the controllers on the show network. Bill Porter convinced me I didn't really need a show network and I collapsed it down to a single network for the whole house and everything works great. You won't find many that have more traffic on their home network so if it works for me it should work for everyone.
-
I would just test it. You know I used to have a separate show network but it became a problem after I added security cameras and wanted the same computer to see the cameras on the home network and the controllers on the show network. Bill Porter convinced me I didn't really need a show network and I collapsed it down to a single network for the whole house and everything works great. You won't find many that have more traffic on their home network so if it works for me it should work for everyone.
Thanks again....I guess I must have a anemic router/modem. If I run a sequence on the home network it knocks other devices off or won't allow them to log on....and those that do stay on often experience data issues.... So I went the route of show network instead of risking buying another modem/router for the home network that MIGHT also not handle the show and home combination.
As to just try it....I can do that but I hoping to understand if that's the purpose of that column or if it just happens to work in my situation.
-
Its how you have things wired up that determines the answer. Does the E682 plug into the network port on the FPP? or all they connected via a switch? To use FPP as a proxy usually means you are connecting to the FPP over its wireless connection and then it forwards the data to the controller that is physically connected to its wired port. That's what makes it a proxy. You know it's like if Jill will only talk to Bill and Gil wants to say something to Jill then Gil has to tell Bill who in turn will tell Jill what Gil had to say...lol.
-
Its how you have things wired up that determines the answer. Does the E682 plug into the network port on the FPP? or all they connected via a switch? To use FPP as a proxy usually means you are connecting to the FPP over its wireless connection and then it forwards the data to the controller that is physically connected to its wired port. That's what makes it a proxy. You know it's like if Jill will only talk to Bill and Gil wants to say something to Jill then Gil has to tell Bill who in turn will tell Jill what Gil had to say...lol.
Gil better be careful! Haha....
The #682's plug in to a switch. I don't use the wireless on the FPP (Cat 5 to the router). I just use the wireless on the show modem/router to access the FPP and controllers...but even if I hook 1 E682 directly to the home network's router I can't access it through the home network 192.168.0.xxx protocol...I have to put the E682 into a mode where it's IP is 169.254.74.73 (I think that's it's default) in order to get to the E682s UI.
On the show network I can easily access the E682 UI with my phone (Phone>Wifi modem/router>Switch>E682)..easy peasy....
-
Well you probably have the E682 set to a certain subnet so when you move it things aren't going to just work.
-
Well you probably have the E682 set to a certain subnet so when you move it things aren't going to just work.
Yeah...probably.... Network stuff baffles me....subnets are a total mystery as to how to tinker with them.....
-
Unless you do something fancy devices on a network only can talk to each other if the first 3 numbers match. So if its set to 192.168.1.x in the device its not going to work when you plug it into 192.168.0.x. That's about as simple as it gets.
-
Unless you do something fancy devices on a network only can talk to each other if the first 3 numbers match. So if its set to 192.168.1.x in the device its not going to work when you plug it into 192.168.0.x. That's about as simple as it gets.
Yeah I figured out that 3rd set of numbers as being the reason....Just haven't figured out why I can see the Falcons on my home network that are set to a different 3rd number set yet can't see the E682's.... I mean the Falcons are set, by me, since I'm using unicast (no DHCP) and so are the E682's to run on my show network yet I CAN see the Falcons but not the E682's on the home network.....The Falcons and E682's have the same number in that third set....It makes my punkin head hurt thinking about it....Haha
-
Well without seeing any setup pages we can only imagine.
-
Well without seeing any setup pages we can only imagine.
Here's 1 of each....in case you're curious....maybe there's something there I don't see or more likely understand... ;)
-
Well I don't see how you are getting to the Falcon on the 192.168.0.x subnet. Are you sure the Falcon doesn't also have a wireless interface?
-
Well I don't see how you are getting to the Falcon on the 192.168.0.x subnet. Are you sure the Falcon doesn't also have a wireless interface?
I can get to all the Falcons on the 192.168.0.x subnet so if I'm getting there through wireless they set themselves up because I didn't.....
The 192.168.0.x subnet is on my home network modem/router so I can't turn it off as the cat5 goes from that home modem/router to the Falcon.
I've never even peeked at the wireless on the Falcon. How would I check if it's set up/working on the Falcon?
-
I don't know I checked the latest Falcon manual and it says wireless is not active yet. Not sure if that's outdated or not. Is yours a V3? I'm afraid you've hit my limit of network knowledge. Only way I'd think you could get to the Falcon is some kind of routing table entry.
-
I don't know I checked the latest Falcon manual and it says wireless is not active yet. Not sure if that's outdated or not. Is yours a V3? I'm afraid you've hit my limit of network knowledge. Only way I'd think you could get to the Falcon is some kind of routing table entry.
Yup....all F16v3's.... Well...I do have a work around at least. I can default the E682's and get to them that way....it's just a pain when they are out in the yard to have to go out and use the program button to default them to something I can reach with my 'puter.
Thanks for trying....I appreciate your effort.
-
Santacarl,
I also have E682s in my display and used the FPP Proxy (along with 2 BBBs) to add all of my devices to the Master Pi. Oddly enough, while I can get to either of the BBBs running FPP, when I try to "proxy in" to any of the E682s, I get a partial web page popping up, but I can't change a single item in there. I tried accessing via a tablet and with my home PC and it works the same for both.
A little frustrating because I have to do what you do - disconnect everything, bring in the E682 in it's box, hit the Prog button and go back to default value, access via the web browser (after connecting the E682 to my home network), change any items, set the IP address back to the value it was for the show/display, unplug, and put it back outside and reconnect everything. >:( Now, while I don't have to change things often, things like this make me want to switch over to Falcon controllers and ditch my E682s. Nothing against the guys that make FPP and included the Proxy, and nothing against San Devices, but I'd like to know why I can't access my controller it through a proxy?
-
The SanDevices t don't actually implement HTTP protocol properly and the Proxy stuff in the Apache web server that we use requires the other side to actually implement HTTP.
If you use Wireshark or similar to trace the connection from your browser to the SanDevice when connected locally, you will see that the response does not contain ANY HTTP headers. There is no response code, no content-length header, not content-type, nothing. To get it to work would require a new firmware for the Sandevices thing that actually returns proper HTTP.
-
I am so glad we have many smart people here to answer questions. :)
I had no idea that the Sandevices controllers lacked that HTTP capability. I've enjoyed my E682s, and they have been quite reliable, but unless some things change, I might see myself trying to switch out from those to Falcon controllers. Granted, I don't have a huge show, but once things are up and in place, it's a huge PITA to try to alter any settings. :-\