Unable to set Gateway since update, results in no DNS reachable

[joshr45]

I have starlink, my untangle box was working before the 16.3.2 update, i was able to set my gateway to the 192.168.100.1 so that the app on my phone could communicate with the starlink dish, now after the update it killed my internet, so i reinstalled because it said it failed.

i tried putting my settings back to what i had and it lost DNS connectivity again, so now im forced to not have data during a Beta test of the dish.

since sending emails to the support email doesn't get anywhere because i don't have "Live support" with my home subscription which to me is ridiculous, its a paid subscription i should be able to talk to someone, this is further cementing my future decisions on not renewing and just switching to PFsense

Let me be extremely clear i had to stay up for several hours reinstalling, only to find out that i now needed to be connected to the internet to setup my local device, not being able to setup the interface first so i could connect to the internet or select from 1 of the 4 ethernet ports my server has, i had no choice but to move the connections around so that i could connect to the internet to setup this now garbage software that i paid for, was and am still beyond pissed that an update broke my setup and now i have no data coming to the starlink app

beyond the garbage no assistance from the "help desk" has anyone else found a solution to this?

[sky-knight]

Starlink has nothing to do with this... Untangle has nothing to do with this... and I really think the upgrade had nothing to do with this. And no, you didn't need to reinstall, what you needed to do was troubleshoot the problem.

I've been on these forums for a long time, and issues like this almost always boil down to a configuration that never should have worked, but for some reason did. So now we're in the place of not working, wondering what do we need to do to get back to working? Swapping to PFSense doesn't solve the problem because you need to fix exactly the same problem with that product. You don't know how to configure a router to work with your ISP... that's fundamental.

Support can't really help you... heck, I can't really help you either! But, as I'm the closest thing to a patron saint of lost causes around, here we go! And, to make matters worse my time here will likely be rejected because all too often people are too wrapped up in the pain of the mess they're in, and assume I'm belittling them or something. That's not happening here, I see where you are, and I'm attempting to pull you out of it.

I will start by affirming your experience with the "new and improved" first boot wizard that rather stupidly forces you to have a working Internet connection to complete, when the device you're configuring is supposed to be the one providing it. This new process creates the nightmare catch 22 situation you've experienced, I've experienced it myself, yes it's utterly stupid, and yes I've complained about it too. Perhaps after a few hundred more of us Untangle will grow a brain and revert this insanity!

However, I can tell you this... if you close the browser during the first boot wizard, it terminates it. By launching the admin console again you'll get a login prompt. This login prompt will have a username of admin, and a password of passwd. None of your modules will work correctly and it'll complain about reports not being there even though it is... but you're in the admin UI, and finally with the full power of config -> networking free to configure your unit to get it online!

So focus on that for now. Sadly, Starlink uses carrier grade NAT. This means you're stuck with some private address on Untangle. BUT it should be handing out addresses via DHCP, if it's not you need to figure out why your connection isn't doing that. Once it is, Untangle should be fine with external configured for DHCP, and internal configured for whatever private network you want to use inside your home.

[joshr45]

the Starlink modem/dish does hand out its IP to untangle, it gets it very easily and i don't have a problem connecting to the internet, the problem is the gateway it has to be set to 192.168.100.1 for the starlink app to get data on the local network, this worked in the previous version no problem and now it doesn't

[sky-knight]

the Starlink modem/dish does hand out its IP to untangle, it gets it very easily and i don't have a problem connecting to the internet, the problem is the gateway it has to be set to 192.168.100.1 for the starlink app to get data on the local network, this worked in the previous version no problem and now it doesn't

What do you mean by that? Because the gateway needs to be whatever DHCP says it should be so the Internet works. Unless the starlink modem is running on 192.168.100.1 so you can control it? Cable modems do that too... and you can simply stuff that address into your browser for it to pop up.

[joshr45]

starlink has its own specific app, theres no advanced settings to tell the app to talk to the dhcp gateway address, theres no login for the starlink dish/modem, normally you would have the starlink router plugged in and there wouldn't be a problem, my starlink install is far enough away that a single router/wifi combo wouldn't work so thats why i have it running through an untangle box and then into my network.

so like i said, even if my setup was "incorrect" it worked, everything functioned on my network regardless, now i am unable to manually set the Gateway override so that the app can actually tell that im online with starlink and give me data from the satellite, doing so causes a failure to reach any DNS servers.

[jcoffin]

Please contact support and specify that you are on 16.3.2 and are using Starlink. We did some changes specifically to support Starlink so if there is an issue, development will be interested. Please include your UID.