Skip to main content

Starlink Issues

Comments

7 comments

  • Official comment
    Bill Moffitt

    OK - here's the situation. Our folks have years of experience dealing mostly with folks who are not IP networking savvy, who don't know what an IP subnet is, and think a router is just a WAP. So we have customers who set stuff up, cause IP address conflicts on their network, and tell us our products caused it. It makes us a little grumpy.

    The Starlink router is a router, with all that implies. Connecting a second router to the Starlink router means that you have to configure it appropriately, in accordance with Starlink's clear instructions and warnings, and accept responsibility for “double NAT” and any other associated dangers. From what I have seen, they are pretty clear about this and recommend generally that you not do it unless you know what you're doing. 

    The way all Ayrstone AyrMesh products are configured is by having them check in to AyrMesh.com and get the configuration from your account there - this is the “initialization” step. You connect the Ayrstone product to the router, let it check in, it shows up on AyrMesh.com (if you have followed the instructions) and it is configured - that way you don't have to go through the hassles of having a separate app just for Ayrstone or having to find the device's IP address on your router and logging into it. If your Hub or Receiver does not show up automatically in your account you can easily add them using the MAC addresses that the instructions tell you to write down in the first step. AyrMesh.com uses public IP addresses to automatically assign devices to AyrMesh.com accounts; because Starlink moves public IP addresses from router to router very quickly, it's not unusual for devices to fail to be automatically assigned to a customer account; many have to be added manually.

    There's are entire sections of the Starlink subreddit about the problems with using different devices with Starlink. Because Starlink's support is not great, I assume everyone reads that subreddit, but that's probably not true. I'm going to try to set up some FAQs specifically for Starlink installations, because, quite honestly, Starlink as a product/service has been terrific for our customers and has enabled a lot of rural folks to have a good, fast Internet connection, and AyrMesh allows them to spread it out over a very large area. So we like Starlink, despite its shortcomings - it generally works well enough if you use it within its limitations and don't try to get too fancy with it. I'd say the same advice goes for AyrMesh - it's a very simple “layer 2” system for spreading your network across a large area, not intended as a commercial WiFi system with myriad bells and whistles, but rather a simple solution for farms, ranches, and rural homes and businesses.

  • jpstyle

    I am having the same problem even purchase additional hubs thinking one my be defective and still having the same problem . the suggestion was that it may be bad cables which needed to be cat 5 so I purchase new cat 5 cable and we are able to see that they are connected and Susan at support that has been great also see that they connect and like you I am able to connect my phone or Ipad bud it has no internet. I know that it has something to do with starlink but we need a solution I have spend thousand of dollar to get the system up and running. I must also add that my system work great for over a year with no problem  **we need help! 

    0
  • Jerry McCollum

    Unfortunately, I'm getting what I consider to be conflicting “advice” from technical support that makes no sense for Starlink connections.

    "Ok I thought you were trying to set up a second router for some reason. I advised you previously to initialize the Receiver to the Starlink adapter. Then take it out and hook it up with a single cable.
     The Hub should be plugged into the Starlink adapter and stay plugged in except for when you are initializing the Receiver. 
     If you are setting up a second Router to use with the Receiver you need to plug it into the LAN port on the power supply Receivers power supply and setup in access point model from the Receiver."

    Several things appear disconcerting about this advice.

    #1 
    Previous advice from technical support said this (with no mention of Starlink):

    “The Receiver needs to be initiated to your main router. Take the power supply and the Receiver and the short cables it came with up to your main router and plug the LAN port on power supply into the back of your router and the PoE to WAN port on your Receiver. Plug it in and leave it 10-15 minutes to initiate it. Once it is initiated you can take it out and place it where you want it in line of sight of your Hub. Give it 10-15 minutes to check in and then you can setup the TP Link to it.”

    #2 
    Starlink power supply LAN port uses a single ethernet cable to feed my main AX3000 router. I do not understand the use of the term “adapter” other than to indicate this LAN port.

    #3
     If I'm now being advised to initialize the Ayrmesh Receiver with ONLY the ethernet LAN port from the Starlink dish power supply, what's the qualitative difference between that initialization and doing the same thing from the Starlink-fed AX3000 router?

    #4
    “The Hub should be plugged into the Starlink adapter and stay plugged in except for when you are initializing the Receiver.”

    If I am leaving the Aymesh Hub  plugged into the Starlink LAN port, then I am bypassing my main AX3000 router entirely. So this means I have no main router connected to my main computer. Am I missing something here? Where is my main computer supposed to get its internet connection?

    This would be funny if it weren't so nonsensical. 😊😎

    Any advice from actual, experienced and knowledgeable users is welcome.
     

    0
  • Jerry McCollum

    I'm giving myself 2 weeks to resolve this issue before requesting a Return Authorization from Ayrmesh and getting a refund. Ayrmesh needs competent technicians and support staff. 😊

     

    0
  • Jerry McCollum

    Thank you for your response, Bill. I appreciate the amount of design work and prioritization that has been put into the Ayrmesh system. I believe I expected too much. What I have since tested and installed to replace the Ayrmesh hub and receiver for my 100 yard, line-of-sight installation is a paired set of Ubiquiti Nanostation LOCOM5 P2P units. My speed test comparisons for this purpose were much more satisfactory than the Ayrmesh Hub & Receiver.

    Naturally, I have lost entirely the range of the hub 2x2 for spreading out an omni-directional WIFI, but I have gained the necessary speed and bandwidth required for this farm's main point-to-point need.

    I will soon be returning the Ayrmesh units and correspond with your company for a return authorization.

    If this farm was in a more advanced stage of broad, farm-wide WIFI needs, Ayrmesh would be a more viable and suitable option.


     

    0
  • Glenn Whitley

    i have had Starlink connected to my Hub2T for a year then something happened to the hub and i received a replacement. i thought that it was the Starlink cable at first so i replaced it with a new one and no signal to the Hub2T. i ordered a replacement adapter from Starlink since that is the only other cable between the Starlink and the Hub2t. still not able to get the Hub2T to check in. this is with all new cables and a new Hub2T. i tried to manually input the MAC address but it does not seem to retain it.

    Any help will be greatly appreciated!!

    0
  • Bill Moffitt

    Please remember that this forum is a place to discuss common issues with AyrMesh; if you're having a problem with your specific installation, support@ayrstone.com is a far more expeditious route to take.

    0

Please sign in to leave a comment.

Powered by Zendesk