Starlink

[BrierPatch]

What happens if you are using the "plain vanilla" Starlink router, but have a mix of network devices-- some with an assigned IP, and some using DHCP?

On bootup, everything works fine on my system. Locally plus also remote access from an off-site location. But after a while, remote access stops working. When that stops working, my wired LAN seems fouled up as well. I'm using the Starlink router, ethernet adapter, then into a network switch that connects to various things. No 3rd party router.

Some of my cameras/camera devices want a fixed IP. But if that is buggering the Starlink lan I will have to figure out a workaround. ???

What were you using before starlink to setup static IP's with. Is it possible that any of your static IP's are conflicting with the SL router IP. One of my disappointments with the SL router was you can't manage or even really see the network. I have a mix of static and DHCP on my network as well. It was much easier to just let SL be my internet connection(WAN) and keep my existing mesh network exactly like it has been, no re-configuring or anything. It's been working great. I bypassed my SL, but could run it's wifi also, but I had no need to, and prefer not having competing wifi's.

 

[plowhog]

What were you using before starlink to setup static IP's with. Is it possible that any of your static IP's are conflicting with the SL router IP. One of my disappointments with the SL router was you can't manage or even really see the network.

I used HughesNet prior to Starlink. That worked OK but was very slow.

I found numerous reports (Reddit) about Starlink DHCP sometimes doing inexplicable things-- leading to network lockup. I'm guessing that is happening to me. But I don't know why my wired network works perfectly after a fresh boot, stays perfect for a day or so, but then the wired network crashes.

Seems I am at a fork in the road- a) change my network devices using fixed IP's to dynamic IP, or b) bypass the SL router.

Maybe one other option is to alter my fixed IP's to be outside the range that SL uses for DHCP. Does anyone know what range that is? I've searched but can't find it ...

 

[RedNeckGeek]

My 3rd gen StarLink router issues IPs in the 192.168.1.xxx range. My wired network uses the 192.168.10.xxx range to avoid conflicts. I haven't disabled anything on the StarLink router, and it seems to be working fine.

 

[plowhog]

My wired network uses the 192.168.10.xxx range to avoid conflicts.

Do you have any devices with fixed IP's in your network?

I thought just my cameras were fixed IP. Then I remembered I have two nanostation M5's doing wireless transmission to my barn. This are fixed IP also.

 

[ponytug]

I used HughesNet prior to Starlink. That worked OK but was very slow.

I found numerous reports (Reddit) about Starlink DHCP sometimes doing inexplicable things-- leading to network lockup. I'm guessing that is happening to me. But I don't know why my wired network works perfectly after a fresh boot, stays perfect for a day or so, but then the wired network crashes.

Seems I am at a fork in the road- a) change my network devices using fixed IP's to dynamic IP, or b) bypass the SL router.

Maybe one other option is to alter my fixed IP's to be outside the range that SL uses for DHCP. Does anyone know what range that is? I've searched but can't find it ...

I would either add a subnet with a second router for your static IP devices, or just go with DHCP and dynamic IP address from Starlink.

The 24 hour time period is strongly suggestive of the issue being an addressing issue, specifically an expired DHCP lease (that typically run for 24 hours).

To the best of my knowledge, there is no data on what range the Starlink router uses, just that it has only has a 127 address table of addresses that it does hand out. I looked as well. You might watch the dynamic addresses and see if you see a pattern.

All the best,

Peter

 

[RedNeckGeek]

Do you have any devices with fixed IP's in your network?

At one time I did, but haven't used static IPs for a long time now. IIRC, I was running a web server I wanted to be accessible by the public, and had to use port forwarding to set that up, which involved establishing a static IP for the web server.

 

[plowhog]

had to use port forwarding to set that up, which involved establishing a static IP for the web server.

That is/was one reason for me having devices with static IP's. But since HughesNet and Starlink both use carrier grade NAT, wanting to do port forwarding is no longer an issue as there is no public facing IP.

My other reason is convenience. When I want to make a minor adjustment to a security camera, I know, by IP, how to get to that exact camera to make the adjustment. But if I adopt a naming scheme for the cameras I think that will work just as well.

I'm soon to eliminate all fixed IP's and we will see how that works.

 

[GSVette]

Just got my email notification from Starlink after a 1 1/2 year wait.

Cant wait to get it installed and cancel my horrible HughesNet service. Looking forward to uninterrupted video streaming. Will operate in parallel for a bit to make sure it’s reliable enough.

 

[rekees4300]

Just got my email notification from Starlink after a 1 1/2 year wait.

Cant wait to get it installed and cancel my horrible HughesNet service. Looking forward to uninterrupted video streaming. Will operate in parallel for a bit to make sure it’s reliable enough.

Patience is a virtue ... congrats

 

[plowhog]

cancel my horrible HughesNet service.

Grab a large mug of your favorite beverage before making the call.

I canceled just now. Took 48 minutes on the phone. By the end I had told them I had already moved into a nursing home, would die soon, been blinded by disease, and didn't know what might happen to my property where the dish and equipment is.

Those subterfuges were in response to:
- we really don't want to lose you as a customer
- don't you really want to keep it?
- could you use it as backup internet?
- could the service move with you?
- what kind of service do you have at your new location?
- could your family still use it at the old location?
- wouldn't a new buyer of your property like to already have high speed internet up and running? (high speed, lol)

I kept being put on numerous "two minute" holds. I began to suspect they could listen in during the holds, even though I could not hear them. Finally, at 45 mins, while on hold, I said: "have you been logging everything on this call? because I think we need to report it ...."

Somehow it was all fixed up within 3 minutes of those utterances ....

Fortunately I had unplugged the modem about 10 days ago. So they saw a cessation of usage on their end.