Hi guys I’ve looked everywhere for the last 4 hours trying to solve this problem and am stumped. I have a raspberry pi running fpp connected to a falcon f48.
My network settings on fpp are wlan0 connected to my router with a static ip of 192.168.1.25 / netmask 255.255.255.0 / gateway 192.168.1.1
When I setup the eth0 I have a static ip of 192.168.25.1 / netmask 255.255.255.0 and gateway blank
I have my dns set to 192.168.1.1 and secondary to 8.8.8.8
On my router I have a static route setup to go from 192.168.1.25 to 192.168.25.0
When I attempt to login to my falcon controller it fails but after about a minute on the screen the version of my controller will show up in the url box and nothing else.
Any help would be appreciated.
Parkerson89 wrote:Hi guys I’ve looked everywhere for the last 4 hours trying to solve this problem and am stumped. I have a raspberry pi running fpp connected to a falcon f48.My network settings on fpp are wlan0 connected to my router with a static ip of 192.168.1.25 / netmask 255.255.255.0 / gateway 192.168.1.1
When I setup the eth0 I have a static ip of 192.168.25.1 / netmask 255.255.255.0 and gateway blank
I have my dns set to 192.168.1.1 and secondary to 8.8.8.8On my router I have a static route setup to go from 192.168.1.25 to 192.168.25.0
When I attempt to login to my falcon controller it fails but after about a minute on the screen the version of my controller will show up in the url box and nothing else.
Any help would be appreciated.
I’m not a network expert but the next to the last digit in the IP is called the subnet. Everything has to be on the same subnet. So you either need to choose 0 or 25 for the subnet. Also everywhere the gateway needs to be whatever you choose for your router IP address. Also I do t know anything about Falcon controllers.
Sent from my iPhone using Tapatalk
maybe you didnt add the route correctly?
you can change your netmask to 255.255.0.0 i think will work
Try adding the route on your computer and see if that works.
I can probably help you with this.
Your network is 192.168.1.0 and your netmask is 255.255.255.0 which is the same as 192.168.1.0/24. That's just two different ways of representing the information. Your router/gateway for that subnet is 192.168.1.1 by the way you described it. Your broadcast address for this network is 192.168.1.255. So, you can't 'assign' 192.168.1.0 or 192.168.1.255 to any devices, those are both reserved.
Now, your pi wlan0 is assigned 192.168.1.25 with what appears to be the correct configuration. Your eth0 appears to be in a different network and that's fine. However, that comes with a few constraints. If you really want to use the eth0 interface but are routing through the wlan0 interface, then on your router (192.168.1.1), you'll need to add a static route that points to 192.168.25.0/24 and the next hop is 192.168.1.25. I am assuming your wlan0 is statically assigned. If not, you run the potential of this breaking each time you reboot your pi. Now, I don't know off the top of my head if the pi will route the traffic or not. Some devices need additional configuration to route traffic between two local interfaces...
Make that static route change and see if that helps get to where you're trying to go...and good luck!
