Cannot Connect to F48V4-NS Through Rasberry Pi

[wutinthehail]

Hello all.  I am new to this and just learning to set up my first system and I am struggling right out of the box.  I am having trouble connecting to my Falcon controller through my Rasberry Pi.  These are my settings:

Rasberry Pi

FPP Ver 6.3
Wlan:  Static
           IP:  10.1.10.211
           Subnetmask:  255.255.255.0
           Gateway: 10.1.10.1
           IP Forwarding:  Forwarding (assuming this is the equivalent of "enable routing through network interfaces" an older version of FPP)
Eth0:  Static
          IP Address:  10.1.11.200
          Netmask:  255.255.255.0
          Gateway:  Blank
           IP Forwarding:  Forwarding (assuming this is the equivalent of "enable routing through network interfaces" an older version of FPP)

DNS Server 1:  10.1.10.1
DNS Server 2:  10.1.10.1
Outputs: E31/Artnet/DDP/Kinet enable output checked, Source interface = eth0, Multithreaded checked, Output counts =0

I can connect to my Pi wirelessly via a browser, with no problem.

Falcon F48V4-NS Ver1.01
          IP:  10.1.11.6
          Gateway:  10.1.11.200
          Subnetmask:  255.255.255.0
          DNS:  10.1.10.1

I am connecting the two via eth5e patch cable via the eth output of the Pi and the network in input on the F48V4 however I can't connect to the controller via a web browser pointed at 10.1.11.6.

Any help is appreciated.  Thank you!

[Poporacer]

Your settings look correct, you don't need the IP forwarding on the eth0 interface and you should set one of your DNS addresses to an internet based address like 8.8.8.8 but I don't think that would cause your problem. Can you try a different cable? What happens if you use a command prompt and Ping 10.1.11.200?

[wutinthehail]

Your settings look correct, you don't need the IP forwarding on the eth0 interface and you should set one of your DNS addresses to an internet based address like 8.8.8.8 but I don't think that would cause your problem. Can you try a different cable? What happens if you use a command prompt and Ping 10.1.11.200?

Thank you for your quick reply!  I changed things as suggested; turning off IP forwarding on the eth0 interface, changing one of the DNS to 8.8.8.8, and tried a different, known good, eth cable but still no luck. Oh yes.  I get a timeout when trying to ping 10.1.11.6 and 10.1.11.200

[jnealand]

All of my units also have the channel output set to point to the the Falcons IP.  You did not mention that.  And I do have the ip forwarding checked as I have no recollection of ever being told that was not required.

[Poporacer]

I get a timeout when trying to ping 10.1.11.6 and 10.1.11.200

Getting a timeout to 10.1.11.200 is concerning. What does a tracert 10.1.11.200 show? Maybe your router has some sort of firewall that is blocking the communication?

[wutinthehail]

I get a timeout when trying to ping 10.1.11.6 and 10.1.11.200

Getting a timeout to 10.1.11.200 is concerning. What does a tracert 10.1.11.200 show? Maybe your router has some sort of firewall that is blocking the communication?

This is what I get down to 30 hops

Tracing route to 10.1.11.200 over a maximum of 30 hops

  1    5 ms    4 ms    3 ms  10.1.10.1
  2    *        *        *    Request timed out.
  3    *        *        *    Request timed out.
  4    *        *        *    Request timed out.
  5    *        *        *    Request timed out.
  6    *        *        *    Request timed out.
  7    *        *        *    Request timed out.

[wutinthehail]

All of my units also have the channel output set to point to the the Falcons IP.  You did not mention that.  And I do have the ip forwarding checked as I have no recollection of ever being told that was not required.

Hello, and thank you for your response!  I don't have a channel output pointing to the Flacon's IP because of all the setup videos/documentation I saw, they never called for it.  

[k6ccc]

If your computer is on the 10.1.10.x subnet, it has no way of knowing that there is a route to 10.1.11.x unless you manually tell it that there is a route via the Pi.  You can add a route statement in the computer with 10.1.11.0 as a destination and 10.1.10.211 (the Pi address) as the gateway.  The exact syntax of the route statement depends on the operating system you are using.

[wutinthehail]

If your computer is on the 10.1.10.x subnet, it has no way of knowing that there is a route to 10.1.11.x unless you manually tell it that there is a route via the Pi.  You can add a route statement in the computer with 10.1.11.0 as a destination and 10.1.10.211 (the Pi address) as the gateway.  The exact syntax of the route statement depends on the operating system you are using.

I am not 100% sure I know what you mean.  During setup I opened an admin command prompt and typed the following:

route add 10.1.11.0 mask 255.255.255.0 10.1.10.211 -p

10.1.10.211 is my Pi Wlan ip

[k6ccc]

Assuming recent Windows, that route command looks right.  Open a command prompt on your computer and type these two command, and copy / paste the results here:
ipconfig /all
route print

Yes, those will give more information than is needed, but the right stuff will be there.

[wutinthehail]

Assuming recent Windows, that route command looks right.  Open a command prompt on your computer and type these two command, and copy / paste the results here:
ipconfig /all
route print

Yes, those will give more information than is needed, but the right stuff will be there.

Thank you for your help!!

ipconfig /all

Wireless LAN adapter Wi-Fi:

  Connection-specific DNS Suffix  . : hsd1.in.comcast.net
  Description . . . . . . . . . . . : Realtek RTL8822CE 802.11ac PCIe Adapter
  Physical Address. . . . . . . . . : A4-97-B1-EB-F5-A7
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes
  IPv6 Address. . . . . . . . . . . : 2603:300f:d03:7a00::b581(Preferred)
  Lease Obtained. . . . . . . . . . : Thursday, January 26, 2023 10:50:29 AM
  Lease Expires . . . . . . . . . . : Saturday, January 28, 2023 10:47:11 PM
  IPv6 Address. . . . . . . . . . . : 2603:300f:d03:7a00:6414:1024:6373:c3d0(Preferred)
  Temporary IPv6 Address. . . . . . : 2603:300f:d03:7a00:a05c:65c:7107:4f3e(Preferred)
  Link-local IPv6 Address . . . . . : fe80::30fd:42f0:7505:478%16(Preferred)
  IPv4 Address. . . . . . . . . . . : 10.1.10.225(Preferred)
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Lease Obtained. . . . . . . . . . : Thursday, January 26, 2023 10:50:26 AM
  Lease Expires . . . . . . . . . . : Thursday, February 2, 2023 1:40:15 PM
  Default Gateway . . . . . . . . . : fe80::5e7d:7dff:fefa:121f%16
                                      10.1.10.1
  DHCP Server . . . . . . . . . . . : 10.1.10.1
  DHCPv6 IAID . . . . . . . . . . . : 161781681
  DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-27-B2-12-AA-64-C9-01-F0-CE-82
  DNS Servers . . . . . . . . . . . : 2001:558:feed::1
                                      2001:558:feed::2
                                      75.75.75.75
                                      75.75.76.76
  NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Bluetooth Network Connection:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
  Physical Address. . . . . . . . . : A4-97-B1-EB-F5-A8
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes

route print

===========================================================================
Interface List
18...64 c9 01 f0 ce 82 ......Realtek PCIe GbE Family Controller
  7...00 ff 61 1a 3f 82 ......ExpressVPN TAP Adapter
  3...00 ff 0d 9d 23 cd ......TAP-Windows Adapter V9
15...a6 97 b1 eb f5 a7 ......Microsoft Wi-Fi Direct Virtual Adapter
12...e6 97 b1 eb f5 a7 ......Microsoft Wi-Fi Direct Virtual Adapter #2
16...a4 97 b1 eb f5 a7 ......Realtek RTL8822CE 802.11ac PCIe Adapter
17...a4 97 b1 eb f5 a8 ......Bluetooth Device (Personal Area Network)
  1...........................Software Loopback Interface 1
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway      Interface  Metric
          0.0.0.0          0.0.0.0        10.1.10.1      10.1.10.225    35
        10.1.10.0    255.255.255.0        On-link      10.1.10.225    291
      10.1.10.225  255.255.255.255        On-link      10.1.10.225    291
      10.1.10.255  255.255.255.255        On-link      10.1.10.225    291
        127.0.0.0        255.0.0.0        On-link        127.0.0.1    331
        127.0.0.1  255.255.255.255        On-link        127.0.0.1    331
  127.255.255.255  255.255.255.255        On-link        127.0.0.1    331
        224.0.0.0        240.0.0.0        On-link        127.0.0.1    331
        224.0.0.0        240.0.0.0        On-link      10.1.10.225    291
  255.255.255.255  255.255.255.255        On-link        127.0.0.1    331
  255.255.255.255  255.255.255.255        On-link      10.1.10.225    291
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
        10.1.11.0    255.255.255.0    100.1.10.211      1
===========================================================================

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination      Gateway
16    291 ::/0                    fe80::5e7d:7dff:fefa:121f
  1    331 ::1/128                  On-link
16    291 2603:300f:d03:7a00::/64  On-link
16    291 2603:300f:d03:7a00::b581/128
                                    On-link
16    291 2603:300f:d03:7a00:6414:1024:6373:c3d0/128
                                    On-link
16    291 2603:300f:d03:7a00:a05c:65c:7107:4f3e/128
                                    On-link
16    291 fe80::/64                On-link
16    291 fe80::30fd:42f0:7505:478/128
                                    On-link
  1    331 ff00::/8                On-link
16    291 ff00::/8                On-link
===========================================================================
Persistent Routes:
  None

[k6ccc]

     10.1.11.0    255.255.255.0    100.1.10.211      1

You typoed the gateway address.  Should be 10.1.10.211

[wutinthehail]

    10.1.11.0    255.255.255.0    100.1.10.211      1

You typoed the gateway address.  Should be 10.1.10.211

Thank you very much!!  Now another newb question...how do I fix it? 

[Poporacer]

Thank you very much!!  No another newb question...how do I fix it?

route delete 10.1.11.0

Then
route add 10.1.11.0 mask 255.255.255.0 10.1.10.211 -p

[k6ccc]

Guess I'm glad that I asked for the route print command...
Happy to be able to help.