RicochetStarlink

@Kermit67 Firstly, 100.79.x.x is definitely a public IP address range. Secondly, I can't image that SonicWall has any preference for or aversion to a specific IP address range (other than 169.254.x.x which is "special" in a whole other way). I am pretty certain that your SonicWall is not "rejecting" the 100.79.x.x address. Thirdly, while I can't say for sure what is keeping the SonicWall from connecting to Starlink, there is one Starlink-specific detail that may have some bearing here. Starlink assigns IP addresses using something called CGNAT (Carrier-Grade Network Address Translation). I won't attempt to explain the details of CGNAT -- not sure I can, LOL -- but suffice it to say that your Starlink connection may not be the only connection using your IP Address. You might be sharing it with other users. Maybe the SonicWall sees all this and says, "No thanks! Not playing!" ??? FWIW, this is a total guess on my part. I'm grabbing at straws here. Not having experience with SonicWall, I just looked them up. SonicWall is an enterprise-grade firewall -- a real boss piece of equipment. There are sooo many things that can be done with these commercial-grade firewalls, it's impossible to say wha the issue might be. Do you control the configuration of your SonicWall? If so, you might need to reach out to SonicWall support for assistance with this. If the configuration is controlled by a corporate IT department, I'd suggest reaching out to them. If you do reach out for assistance elsewhere, be sure to mention Starlink's use of CGNAT. FWIW, when I go to the Starlink Support Web site and search on "NAT". I see the following HTH...

@Huxta Starlink Forum has had a lot of folks asking about extended the length of the antenna cable for their Starlink. Would you be so kind as to share links to the videos that covered constructing this cable? Thanks!

@Karen S. from Texas, Thank you for posting your experience. It does seem that there have been a LOT of reports about Routers dying inexplicably in the midst of an update... from many Starlink users in many locations around the globe, but especially in the US. I have no information on what is going on or why, but I can certainly say that it is concerning to me.

Yes. We have. All of us... and there's no fixing it. That's just the way it is... TL; DR; Internet speed tests (e.g., Ookla Speed Test) are generally pretty accurate. They measure the maximum bandwidth available at a given moment. However, the actual speed that you observe with a particular transfer operation is only partially dependent on the available bandwidth. In fact, the transfer speed is affected by an enormous number of factors. The capacity of the server that is transmitting the data The speed of the Internet connection that that server uses The distance that the data is traveling on the Internet Network congestion in... The server itself The server's Internet connection The Internet in general Your Internet connection Anything else affecting performance on either end of the connection... or in the middle All this translates down to two basic things Actual transfer speed will NEVER be as high as measured transfer speed. Sometimes it will be a small percentage. That's just the way it is. Actual transfer speed at a given moment during a specific transfer activity will be different than the transfer speed experienced on a previous or subsequent moment during the exact same transfer activity. ...which leads to the answer to your original question. > "In fact, I'm just looking to have a real bandwidth that is roughly consistent with what I observe with their measurement tool. > Have any of you noticed such a phenomenon?" Yes. We have. All of us... and there's no fixing it. That's just the way it is...

Sort of. Internet users are assigned an IP address by their ISP (i.e., Starlink). The IP address assigned to you will be based on the location of your ISP's point of presence (PoP). For land-based ISPs, this is generally nearby your location. For Starlink, it depends on the location of the ground station where the satellite connects to forward your traffic. So, for instance, I live in West Tennessee, but my IP Starlink IP Address is generally located in Dallas because the Dallas PoP is where most of the satellite passing over my location are connecting to deliver my traffic. In countries outside the US, I have heard reports that a user's assigned IP address may actually be in a neighboring country becuase that is the location of the nearest Starlink PoP. The only way to control the IP Address seen by the places you connect (including your employer) is to use a VPN service and connect to one of their VPN servers in the location that you wish to appear. However, there are two BIG caveats here. Firstly, your employer's network may or may not tolerate a VPN connection at all. VPN's can be problematic for certain kinds of traffic and/or certain providers. For example, banking applications are notorious for shutting you out if you are on a VPN. No, I'm not sure how they know... Secondly, International Laws have something to say about you working abroad as well. If you work abroad for more than 30 days, you and your employer are legally required to notify both the US government (IRS) and the local government where you are working and to remit the correct payroll taxes to both the the US government and to the nation where you are working. Violation of these laws fall under the tax code and carry very stiff penalties. For this reason, many employers do NOT allow employees to work abroad, especially if the employer does not have other employees in the country where you would be working. Long story short, consult an attorney to understand the risks involved before you decide to move to Borneo to work from home for your current employer using a VPN to mask your location. You might be opening a big hornet's nest.

@Kermit67 There's a lot going on here. First off, sorry to hear you had to replace your SL Kit due to a power problem. I always recommend using a UPS (battery backup) between your power outlet and your SL Kit. It's not worth the risk to go without it and you can get one for $45 at Walmart... Secondly, its interesting that the Sonicwall router was once using 192.168.100.100 as it's external address (on the SL side) and now your PC is getting a 100.79.x.x address. Sounds like the old router might not have been in bypass mode. Not sure that this matters. Anyway, I wonder if it's possible that your Sonicwall router might have had the old IP address (192.168.100.100) manually assigned instead of taking it from DHCP on the Starlink Router. That could definitely cause these symptoms. Thirdly, it remotely possible that the power problem that took out the old SL Kit might have done some damage to the Sonicwall Router's WAN port. A high voltage coming into the SL router could have resulted in a high voltage on the Ethernet cable to the Sonicwall causing damage to the port on the Sonicwall. However, I don't think this is the right answer because the Sonicwall can ping the new SL router at 192.168.100.1. Not sure what else to offer here. Hate to hear you're having trouble. Thanks!

Is the Starlink WiFi router allowing devices to connect wirelessly? Have you connected a hard-wired device (e.g., laptop, desktop) to the Ethernet Adapter to see if that works? Is your Linksys Velop router configured to connect to the WAN using DHCP?

The Ethernet Adapter is (reportedly) a 1Gbit Ethernet port. Cat 5E or Cat6 Ethernet cable should be fine. Yes, this is correct. A Wireless Access Point (WAP) should work, but it will need a different SSID (WiFi network name) than your main Starlink router. I would recommend one of Ubiquiti's AP "disks" (see https://ui.com/). Installing a router in the shed will introduce a layer of overhead that is likely unnecessary.

The Starlink Mobile app is only available for iOS (Apple) and Android™ devices. There is not Starlink App for Windows, macOS or Linux. You can, however, point the browser on your WIndows 10 laptop to https://192.168.100.1/ to get to the router's browser interface. The browser-based app has the key functions available through the mobile app.

@JMS "...DHCP scope range..."???

@wntrhwk Were you able to resolve this issue?

Contact SL Support. Sounds like you may have a DOA router.

Not sure what to tell you here. An inverter and a UPS should have similar power protection properties, if I understand correctly. For the record, I’ve heard a lot of reports about DOA Starlink routers in the last couple of months. As for using a POE injector foe the Dishy (antenna), some folks are doing that, but it voids your warranty and you still need to get the Ethernet signal off the antenna to a 3rd-party router. I bypass my Starlink Router using the Ethernet Adapter ($25 in the Starlink store online). The SL router can be put in bypass mode and you can then connect a 3rd-party router. Of course, that still requires a working SL router. probably best to reach out to SL support using a ticket or email to AStarlinkResolutions@spacex.com.

Is this what you are looking for? https://ts2.space/en/how-to-become-starlink-reseller/

The only possibility might be a VPN service.

@Skirat There are a lot of "gray areas" with those kinds of definitions in the Starlink T&C. If you need clarification or assistance, you should reach out to Starlink Support.

@MarkFisher702 No, you really cannot use the same SSID on the SL and the Orbi. There's a whole bunch of technical reasons why this probably will not work.

@Rick919 If you ASUS router is set up to accept an IP address from a DHCP server on the WAN side, then it should work. To do this, you need your Starlink Kit and the Starlink Ethernet Adapter. In short here's the procedure. Plug the Ethernet Adapter inline between the Starlink Dishy and the Starlink Router. Connect your ASUS router's WAN port to the Starlink Ethernet Adapter. Your ASUS router should work at this point. If you aren't going to use the Starlink Router, use the mobile app to put it in bypass mode. As for your DSL line, unless your ASUS router is capable of Dual WAN -- and most are NOT -- your DSL will be sitting around doing nothing.

@ESD If you can get your hands on a working Starlink router, it should plug and play. 3rd Party routers require a working Starlink router and an Ethernet Adapter. The Starlink Router can be in bypass mode, but it must be working...

If the antenna has an unobstructed view of the sky, outages should be negligible. The 30Mbps speed could be a result of limitations on the LAN and/or WiFi networks that have nothing to do with Starlink.

@jackel61 To my knowledge, there is nothing you can do short of turning on Location services on your devices. Even that might not work in all cases. This occurs because Starlink satellites connect to a ground station to get your traffic onto the Internet. Those ground stations which are few and far between are responsible for assigning your IP address and the IP address blocks they use are all for the locale of the ground station. There is no way to override this IP address assignment or to influence it to use an IP address that geo-locates to your location. I have had this conversation with Starlink Support and, unless something has changed radically, it's just not possible to change.

@Michel That sounds like it might be a viable solution. I'd say give it a try. What do you have to lose since you already have the gear? On the other hand, I have never used the powerline adapters. So, I can't say whether this will work... or how well...

Yes.

FWIW, I have the same problem and Starlink has told me there is nothing to be done. It affects EVERYTHING... Channel selection and advertising on my Smart TVs, location on most web sites. The answer to your question: Nothing. The satellites you are connecting to are connecting to Starlink's ground station in Los Angeles. Your IP Address is assigned by the ground station. This is all automated in the management of the Starlink network. Starlink Support, to date, has not been able to provide any way to override your IP Address. You should contact the owners of those "certain things" that "don't work properly" and ask them what can be done.Sorry I don't have a different answer.

@Danusa The Starlink Support page you referenced above seems pretty clear. It gives a list of countries where mobile data is available and there are no African countries listed. For more information, I suggest reaching out to Starlink Support at StarlinkResolutions@spacex.com.