News:

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

+-+-

+-User

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

+-Site Stats

Members
Total Members: 15299
Latest: Psonic
New This Month: 2
New This Week: 2
New Today: 2
Stats
Total Posts: 125118
Total Topics: 15244
Most Online Today: 71
Most Online Ever: 7634
(January 21, 2020, 02:14:03 AM)
Users Online
Members: 1
Guests: 37
Total: 38

how to test pixels on the expansion card

Started by marci, January 12, 2022, 08:29:15 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

marci

I think I fixed the problem. I added a new static route specifically for the F16 and that seems to fix it.  Probably an obvious thing to do for someone more versed in networking but it took me a while to figure that out! Thx for helping me think through this!

Poporacer

#16
Quote from: marci on January 14, 2022, 07:20:59 AMI added a new static route specifically for the F16 and that seems to fix it.
Usually you add a route for the Subnet that you want to reach, not the specific device, can you show a screenshot or explain that route so we can verify? Also, on your FPP in the Network tab, enable routing between networks if you haven't done that already.
If to err is human, I am more human than most people.

k6ccc

Since you said you are very weak on networking, let's take the opportunity for a teachable moment...

Grumble, grumble, this forum would not let me imbed this image that I drew based on your description (after you edited post #8 and removed your network config...) so my numbers may not be correct.  Here is a link to my drawing...
http://www.newburghlights.org/images/Marci_network.png

By default your computer only knows about the 192.168.1.0/24 network (can also be written as 192.168.1.0 - 192.168.1.255 - also means it has a subnet mask of 255.255.255.0).  For ALL other IP addresses, it must go through a router somewhere.  Your computer has an address commonly called the default gateway.  This is the address that your computer will use as a gateway to get to all IP addresses that are NOT on your local network.  In other words, by default, your computer has no idea how to reach an IP address on the 192.168.2.0 network - other than to point the packet at it's default gateway.  By default, your router also knows nothing about your 192.168.2.0 (E1.31) network.  The router also has a default gateway that is normally supplied by your ISP.  So by default, anything that your router does not know about will be sent to the router's default gateway (normally your ISP).  A little detour here.  192.168.x.y addresses are in a range that are all private address space and NOT routable on the internet, so if you attempt to send to or from a 192.168.x.y address over the internet, either your router or at least your ISPs router will dump the packet.
You can manually set a route either in your computer so that it knows how to find the 192.168.2.0 network (by way of 192.168.1.111 in my drawing), or in your router.  Note that not all consumer grade routers allow that, or you may have change modes in the router to be able to do routing on the LAN side.  If you set a route statement in your computer, your computer will know that 192.168.2.112 is reachable by way of 192.168.1.111, so it will send the packet directly to 192.168.1.111.  If you set the route in the router, your computer will send the packet to your router, and the router with resend the packet to 192.168.1.111.
Once your packet arrives at the FPP instance, IF the FPP has been told that it is allowed to router packets between interfaces, it will know that it can resend the packet on it's other interface to get it to F16v3 on 192.168.2.112.

Did all that make sense?
Using LOR (mostly SuperStar) for all sequencing - using FPP only to drive P5 and P10 panels.
My show website:  http://newburghlights.org

Jim

marci

Thanks both of you for taking the time to educate me. I appreciate it! And my new static route doesn't seem to work all the time so that didn't fix the problem.

k6ccc, your drawing is correct. Good memory!

So, yes, I believe I get the basic idea of what you're saying. The show network (192.168.2.x) is blind to any device on the primary network (192.168.1.x) so I need a gateway (in either the computer on the primary network that wants to connect to the show network or the router) for any device on my primary network to see the F16 or FPP. I guess I'm having trouble establishing that gateway since I thought I had that in place with my static route in my router routing to traffic to the show network and the FPP (the gateway for the show network) is routing traffic to the F16. I seem to have it wrong though. So here's what I have at this point.

And, Poporacer, yes, I do have "enable routing between networks" checked.

FPP
eth0
Static IP: 192.168.2.111
Netmask: 255.255.255.0

wlan0
Static IP: 192.168.1.111
Netmask: 255.255.255.0
Gateway: 192.168.1.1

DNS server: 192.168.1.1

Tethering Mode: "if no connection"
Tethering Interface: wlan0
Tethering Technology: Hostapd
Tethering SSID: FPP

[checked] Enable routing between network interfaces


F16v3
Static IP: 192.168.2.112
Gateway: 192.168.2.111
Subnet mask: 255.255.255.0
DNS: 192.168.1.1


Router
Static Route 1 (For FPP):
Destination: 192.168.2.0/24
Next Hop: 192.168.1.111

Static Route 2 (for F16v3):
Destination: 192.168.1.0/24
Next Hop: 192.168.2.112

Poporacer

Quote from: marci on January 14, 2022, 01:33:56 PMAnd my new static route doesn't seem to work all the time so that didn't fix the problem.
How about posting a screenshot of your route settings and your network configuration pages? That will help tremendously.


Quote from: marci on January 14, 2022, 01:33:56 PMRouter
Static Route 1 (For FPP):
Destination: 192.168.2.0/24
Next Hop: 192.168.1.111
How about a screenshot of this? ^



Quote from: marci on January 14, 2022, 01:33:56 PMStatic Route 2 (for F16v3):
Destination: 192.168.1.0/24
Next Hop: 192.168.2.112
You need to delete this one, it will probably cause you all sorts of problems. You only need the one route.

If you want more information, you might want to look at the FPP Manual, it has some good resources.
https://falconchristmas.github.io/FPP_Manual(5.4).pdf#page=142
If to err is human, I am more human than most people.

k6ccc

Quote from: marci on January 14, 2022, 01:33:56 PMThe show network (192.168.2.x) is blind to any device on the primary network (192.168.1.x) so I need a gateway (in either the computer on the primary network that wants to connect to the show network or the router) for any device on my primary network to see the F16 or FPP.


The first part of your statement is backwards, but the second half has it right.

The devices on the show network (the F16v3 in this case) already have a gateway (the FPP instance) as a default gateway, so although they don't specifically know where the primary network is, they know how to get there - by way of the gateway.

The devices on the primary network need a route statement in either themselves, or the router that functions as the primary network default gateway in order to know that they can use the FPP instance as a gateway to get to the show network.

IP routing at this level is really pretty simple.  Your PC has a IP of 192.168.1.101 with a subnet mask of 255.255.255.0.  That means it's local network consists of 192.168.1.0 through 192.168.1.255 (.0 and .255 are not usable address in this context, but out of the scope of this discussion).  In order to communicate with any other device in that local network, the PC can simply address the packet to that IP and send it.  It will travel by way of the switch and if needed the WiFi access point, but it will NOT travel by way of the router.

By comparison, if the PC is trying to send a packet to any other IP address, it will send that packet by way of it's default gateway (the router in this case).  So for example if you try to reach my show website (http://newburghlights.org), your computer will do a DNS lookup (which is out of the scope of this discussion unless requested), and it will find that my show website is at 47.150.246.14.  Your PC has no clue where that address is, but it knows that it is not on the local network, so it sends the packet to the default gateway (your router).  Your router also has no clue where 47.150.246.14 is, but it also has a default gateway (a router at your ISP), and your router sends the packet to it's default gateway (your ISPs first router).  This is where routing gets more complex.  There will likely be several routers involved, but eventually your packet will reach a router that does know where 47.150.246.14 is located.  If you really want to see this, on your PC, open a command prompt and type " tracert newburghlights.org "  (without the quotation marks).

Now what we were doing by adding a route statement in your PC or local router is giving it a known route to the 192.168.2.0/24 network that does not depend on the default gateway.

BTW, that tracert command should look something like this:
C:\Users\jwalls>tracert newburghlights.org
Tracing route to newburghlights.org [47.150.246.14]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  172.16.13.254
  2    1 ms    <1 ms    <1 ms  047-044-002-089.biz.spectrum.com [<redacted>]
  3    2 ms    2 ms    8 ms  150.181.13.10
  4    3 ms    2 ms    2 ms  096-034-062-252.biz.spectrum.com [96.34.62.252]
  5    33 ms    2 ms    2 ms  bbr02atlnga-tge-0-0-0-1.atln.ga.charter.com [96.34.3.40]
  6    3 ms    3 ms    3 ms  bbr01ashbva-tge-0-1-0-1.ashb.va.charter.com [96.34.3.139]
  7    *        *        *    Request timed out.
  8    *        *        *    Request timed out.
  9    3 ms    3 ms    3 ms  4.16.30.130
 10    3 ms    3 ms    3 ms  ae1---0.scr01.lsan.ca.frontiernet.net [74.40.3.197]
 11    6 ms    7 ms    7 ms  be10---0.lcr21.lsan.ca.frontiernet.net [74.40.3.38]
 12    6 ms    5 ms    5 ms  172.102.111.123
 13    6 ms    7 ms    5 ms  47.150.246.14
Trace complete.


Each line is a router that the packet went through.  Line 1 is the local router here at work, and line 13 is my router at home (my show website is running on a server at home, but my router responds to the trace command from the internet).

Has your head exploded yet?
Using LOR (mostly SuperStar) for all sequencing - using FPP only to drive P5 and P10 panels.
My show website:  http://newburghlights.org

Jim

marci

Thanks for that explanation. So how does this apply to my situation? Seems like I need the right route statement on my router. Seems best to route at the router level rather than on the PC so any device on my primary network will find its way to either FPP or the F16 on the show network rather than just that one PC. Does that make sense?

So what's the correct route statement to do this on my router? What I have now obviously isn't right:
Destination: 192.168.2.0/24
Next Hop: 192.168.1.111

marci

On page 142 of the FPP manual where they show a network map of the devices for a one controller show it seems that my FPP and controller configuration matches that. If true, then it seems that I just need the right static route on my router. What should it be? My current static route has my destination as the show network (192.168.2.0/24) and the next hop as the FPP wlan0 IP (192.168.1.111).

marci

BTW, as I mentioned, when my computer on my primary network IS able to get to the F16 (randomly, it seems) I can ping the F16 and traceroute it.

Here is the result of the traceroute when it does connect. It first goes to the router gateway, then the router passed it to the FPP per the static route, then it just is an endless repeat loop of asterisks. So it doesn't seem to resolve, yet my PC on the primary network can still see it. Not sure why.
traceroute to 192.168.2.112 (192.168.2.112), 64 hops max, 52 byte packets
 1  192.168.1.1 (192.168.1.1)  1.503 ms  0.485 ms  0.393 ms
 2  192.168.1.111 (192.168.1.111)  6.272 ms  3.184 ms  2.991 ms
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
[keeps going forever]

Poporacer

Quote from: marci on January 14, 2022, 07:47:01 PMSo what's the correct route statement to do this on my router? What I have now obviously isn't right:
Like I said, let's see screenshots of your route and other network settings.


Quote from: marci on January 14, 2022, 08:33:14 PMthen it just is an endless repeat loop of asterisks. So it doesn't seem to resolve,
And did you still have that bad route I mentioned?

You have shotgunned your troubleshooting to a point that you probably have something not quite right and that is why it is important to actually SEE what you have configured.
If to err is human, I am more human than most people.

marci

Poporacer, this forum software doesn't allow the uploading of images. But here's what the screen looks like:

Route type: gateway
Destination network: 192.168.2.0/24
Next hop address: 192.168.1.111
Description: FPP
Distance (1-255): 1
Enable [checked]

jnealand

In the forum you must use the reply button and not the quick reply box.  In the reply option there is a place to upload images.  In a Windows PC you can type snip in the search box at the bottom left of a standard taskbar (i.e., not tailored), pick either the snipping tool or the snip and sketch option (better choice) and you can grab a screenshot of the part of the screen that you want to pass on.  I keep the snip and sketch option locked to my taskbar and I use it often when I see little nuggets of info come up on screen when browsing the forums or facebook,  also very usefull when shopping online.
Jim Nealand
Kennesaw, GA all Falcon controllers, all 12v Master Remote Multisync with Pi and BBB P10 and P5

marci

Hi Jim. I'm on a Mac. When I click on the "insert image" button in reply (quick reply or reply) I only see an option to enter a URL. No option to pick a file on my computer.

Poporacer

Quote from: marci on January 15, 2022, 09:43:08 AMHi Jim. I'm on a Mac. When I click on the "insert image" button in reply (quick reply or reply) I only see an option to enter a URL.
In a normal reply, not a Quick Reply, you have to upload the image first, then you can insert it.
You cannot see attachments on this board.
It will look a little funny but it works
You cannot see attachments on this board.
If to err is human, I am more human than most people.

marci

Got it. Here's the static route:
You cannot see attachments on this board.

Support FPP

+- Recent Topics

Upgraded to FPP V6.1.1 - Network Settings do not have "Interface Routing" option by Poporacer
October 01, 2022, 10:24:15 PM

FS Kulp K-8B Controller, Complete by poolprousa
October 01, 2022, 08:31:43 PM

60+ Ray Wu Cables, Pigtails, misc by jnealand
October 01, 2022, 08:57:49 AM

Sequence issues from Rasberry pi by Poporacer
October 01, 2022, 07:49:10 AM

New K4-PB wifi problems by fauxton
September 30, 2022, 07:19:15 PM

Projector video for just one video source by XmasInGalt
September 30, 2022, 03:54:30 PM

F16V4 port 5 Lights flicker by JonD
September 30, 2022, 01:55:34 PM

Smart receiver 2.01 on F16v3 not sending data by JonD
September 30, 2022, 12:51:45 PM

Micro-SD by JonD
September 30, 2022, 08:58:19 AM

Unable to get FPP working on RasPi-4 by k6ccc
September 30, 2022, 08:11:06 AM

Powered by EzPortal
Powered by SMFPacks Menu Editor Mod