Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Starlink problem with SG2440 22.05

    Scheduled Pinned Locked Moved General pfSense Questions
    38 Posts 6 Posters 4.5k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      Yup, sometimes a reinstall helps when nothing else does even though it makes no sense. Usually because there was some obscure setting we forgot about! Hard to see what that could be here though.

      Steve

      A 1 Reply Last reply Reply Quote 0
      • S
        serbus
        last edited by

        Hello!

        Wild guesses...

        When swapping routers with the same ip for testing, could there be arp issues?

        Can pfsense get a webpage the client cant? Diagnostics -> Command Prompt -> Execute shell command :

        curl -s https://www.pfsense.org
        
        curl -s https://www.netgate.com 
        

        John

        Lex parsimoniae

        1 Reply Last reply Reply Quote 0
        • A
          A.Bursell @stephenw10
          last edited by

          @stephenw10 said in Starlink problem with SG2440 22.05:

          Yup, sometimes a reinstall helps when nothing else does even though it makes no sense. Usually because there was some obscure setting we forgot about! Hard to see what that could be here though.

          Steve

          Thanks - I think I'm getting to that point now.

          @serbus said in Starlink problem with SG2440 22.05:

          Hello!

          Wild guesses...

          When swapping routers with the same ip for testing, could there be arp issues?

          Can pfsense get a webpage the client cant? Diagnostics -> Command Prompt -> Execute shell command :

          curl -s https://www.pfsense.org
          
          curl -s https://www.netgate.com 
          

          John

          The routers actually have different IPs - never really thought about that mattering. The pfSense is 192.168.2.1 and the Netgear is 10.0.0.1.

          I tried both of those commands and just saw a shell output command at the top with the same command. I tried it in Putty and again didn't see anything. Not sure what I was supposed to see?

          Adam

          1 Reply Last reply Reply Quote 0
          • A
            A.Bursell
            last edited by

            Went with the nuclear option and did a fresh install of pfSense 2.6 (can't go to 22.05 unless I get out of the local network). NO CHANGE. I didn't touch any settings except the time, and it is exactly the same. No errors during install, everything looks exactly like it should, but I have the exact same problem.

            What do I do now?

            Is it possible there is some type of hardware incompatibility? This is an SG2440 -- it just works and has worked on everything I've ever used it on for years. And it still works -- just not with my Starlink.

            Thoughts?

            Adam

            1 Reply Last reply Reply Quote 0
            • S
              serbus
              last edited by

              Hello!

              The curl command should show the html served up by the address. No output could mean a lookup error. Verify by using the -sv switch with curl.

              This thread talks about putting a switch between the starlink v2 ethernet adapter and the customer router to solve a similar (?) problem. Worth a try...

              John

              Lex parsimoniae

              A 2 Replies Last reply Reply Quote 0
              • A
                A.Bursell @serbus
                last edited by

                @serbus said in Starlink problem with SG2440 22.05:

                Hello!

                The curl command should show the html served up by the address. No output could mean a lookup error. Verify by using the -sv switch with curl.

                This thread talks about putting a switch between the starlink v2 ethernet adapter and the customer router to solve a similar (?) problem. Worth a try...

                John

                Well I don't even ... sure enough that thread sounds like exactly the same problem except with a Netgear router (ironiclly my Netgear router works fine), and I did a quick search and even saw the same thing with a Peplink router. There are probably more. I'm going to try the extra switch when I get back later. I don't know why or how it would work, or what the poitential consequences might be, if any, but it's for sure worth a shot.
                Thanks,
                Adam

                1 Reply Last reply Reply Quote 0
                • A
                  A.Bursell @serbus
                  last edited by

                  @serbus
                  I'm genuinely surprised, but sure enough- I put a simple unmanaged switch in-between the Starlink and pfSense and it instantly started working. Don't really understand it except that there must be some type of hardware issue with Starlink that conflicts with certain brands of routers? Suppose it could be software too but definitely a Starlink issue. My next stop will be trying to send info to their tech support and getting them to listen and understand. I don't like the idea of having an extra unnecessary switch installed there.

                  Thank you everyone for your help!
                  Adam

                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    Hmm, really weird. Hard to see how that could possibly affect some DNS queries only...

                    1 Reply Last reply Reply Quote 1
                    • S
                      serbus
                      last edited by

                      Hello!

                      For reference, here is a teardown of the starlink ethernet adapter. Maybe there is a workaround other than a switch.

                      John

                      Lex parsimoniae

                      1 Reply Last reply Reply Quote 1
                      • A
                        A.Bursell
                        last edited by A.Bursell

                        Update! I heard back from Starlink. They were nice enough to let me know I should only have one router in my network and sent instructions on how to change DNS addresses. 🤦 I reopened the ticket, explained again, and asked for it to be escalated to a higher tier support so it can be sent to hardware engineering. We will see.
                        Adam

                        1 Reply Last reply Reply Quote 1
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.