Jump to content

Search the Community

Showing results for tags 'wan'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • The Latest from Starlink & SpaceX
    • News, Announcements & Blogs from Starlink
    • Status/Outages
  • STARLINK SUPPORT
    • Starlink Troubleshooting & Questions
    • Routers & Networking
    • Starlink Resources
  • USING STARLINK
    • General Starlink
    • Starlink Coverage
    • Starlink BETA Testing

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 2 results

  1. * re-submitted question (due to Forum technical difficulties in formatting turning all my text black thus rendering it unreadable; so I have resubmitted my new threat topic post) I suspect the "Order of Operations" here are important. I even saw a video online suggesting that prior to linking StarLink modem to a secondary 3rd Party Router one must allow the StarLink Modem to first obtain its own IP Address before linking an Ethernet wired connection to the 3rd Party Router (and long before toggling on Bypass Mode). I tried it both ways with different results, proving it had nothing to do with the 3rd Party Router involved but is indeed on StarLink's end, unlike what the useless low-level Help Desk general support workers regurgitating their text-book Manual from being slackers in Reading Comprehension or just from lack in English Language Reading Comprehension skills in general (yikes, I can't believe I have to pay for this type of customer service (I get better user support from FOSS/FLOSS community projects lol). Thus, this has nothing to do with "... how the 3rd Party Router is setup" that is just an excuse not to perform on the job to provide quality StarLink customer service. Proof: I have the same setup, yet when I changed the "order of operations" StarLink gave me different results within the app. This is a StarLink issue in that there is a failure for competent support technicians servicing customers as well as lacking Documentation to clearly say how to setup a 3rd Party Router from StarLink's side (I understand other factors will depend upon the 3rd Party Router, but again this is not the issue as the issue really is on StarLink's side despite their attempts to ignore it). The issue is clearly there is a proper "Order of Operations" before even toggling "on" Bypass Mode, and yet this is not within the in-app Documentation nor has been addressed by Customer Support through a Support Ticket because I keep ending up with non-English speaking low-level Help Desk Technicians that apparently only know how to memorize text-book replies without any Reading Comprehension skills whatsoever. Question remains, which these scenarios within the StarLink app suggest the correct order has been achieved, so to proceed onto the step of Bypass Mode? 1. before moving to the step of toggling "on" Bypass Mode, once wired up connections have been established, the app shows all devices even wired devices connected behind the 3rd Party Router. • example, StartLink app shows: - StarLink Modem - my iPhone - my 3rd Party Router that is connected to StarLink modem - my laptop connected on that 3rd Party Router OR 2. before moving to the step of toggling "on" Bypass Mode, once wired up connections have been established, the app shows only wired devices connected in front of the 3rd Party Router. • example, StartLink app shows: - StarLink Modem - my iPhone - my 3rd Party Router that is connected to StarLink modem OR 3. before moving to the step of toggling "on" Bypass Mode, once wired up connections have been established, the app shows NO wired devices connected relating to the 3rd Party Router. • example, StartLink app shows: - StarLink Modem - my iPhone OR 4. before moving to the step of toggling "on" Bypass Mode, once wired up connections have been established, the app shows NO connected devices at all — including failing to show my iPhone. • example, StartLink app shows: - StarLink Modem Which of these 4 scenarios is the ideal result prior to moving onto the next step of toggling "on" Bypass Mode? Clearly only 1 of these or some of these scenarios is the accurate sign of "good to go" before proceeding to toggle "on" the Bypass Mode for completing the process. Depending on the steps I take upon "resetting" the StarLink modem and the steps in certain order I do when connecting up the Ethernet cables, varying the method of Ordered Operations yields these 4 different scenarios based upon how I did it. I have gotten all 4 of these at least once during my time in trying to Troubleshoot as to why I cannot ping out to the Internet when set in Bypass Mode linked up from StarLink Gen3 to my 3rd Party Router on an Ethernet cat 6a wired connection. So, again, which scenario is the correct setup on the StarLink side? (as this is all shown from the StarLink app btw) This is NOT a 3rd Party issue this is a StarLink Gen3 issue; in that StarLink has failed to document the Order of Operations prior to placing the StarLink Gen3 modem into ByPass Mode. Please, help if you know any of these answers as I really need to get this done as I have wasted 4 days on it already with basically non-existing StarLink customer service user support. Thank you all in advance!
  2. My system was working fairly well before. Every so often, I would have to power off router for 20 minutes, but when it came back, it was fine. Powering off for 5 minutes didn't work. I'm pass through and I am getting the same problem with both Asus and D-Link routers. Routers are both pretty new. Problem router is being given a gateway IP address of 192.168.1.1 which is normally used for a LAN not a WAN. The router IP given using DHCP is in the 192.168.1.0/24 group; currently it is 192.168.1.138. I am currently on the ASUS which gives more information. The five left lights are all blue, and the WAN and LAN lights indicate good connections. Connecting to the router (right now I have the LAN set up at the 192.168.10.0/24 range - SUBNET = 255.255.255.0 - I have also tried 192.168.20.0/24, 192.168.0.0/24 and 192.168.1.0/24 - the last one gave real problems on the D-Link as it changed away and I had to reset the router) it states for the WAN status: Not Connected, but still lists the Gateway and Wan IP address as stated above. I expect to get a WAN gateway and IP address from the group allocated to Starlink (such as 65.181.0.0/22, or 65.181.4.0/22, or 65.181.8.0/23). Not in the 192.168.1.0/24 range, and I expect to be able to establish a route to say 1.1.1.1. Using traceroute, it stops after going to the router.
×
×
  • Create New...