On Mon, 24 Feb 2025 17:20:14 -0500 Jon LaBadie jon@labadie.us wrote:
On Mon, Feb 24, 2025 at 01:35:54PM -0800, Geoffrey Leach wrote:
I've been using Starlink configured for a single-band 5GHz Wi-Fi connection with success for some time. I decided to try the dual-band configuration, that is to create a Wi-Fi network operating at 2.4GHz, so as to replace the modem that has been connecting to a 2.4GHz printer.
The configuration appears have been successful, as I'm able to connect to the internet using the 2.4GHz band. However, I'm unable to connect to the printer.. (Ping fails)
Any suggestions as to what I've missed?
Might the printer need its configuration/settings changed to connect to the new network?
Here's the problem traceroute pvr traceroute to pvr (10.0.0.5), 30 hops max, 60 byte packets 1 _gateway (192.168.2.1) 20.167 ms 20.130 ms 20.122 ms 2 ....
(pvr is another box, configured for the same local net)
So, the route leaves the local net and wanders off into the ether..
So is there a local fix, or did I got what I asked for, just not what I wanted.
Jon LaBadie jon@labadie.us wrote:
Might the printer need its configuration/settings changed to connect to the new network?
Geoffrey Leach:
Here's the problem traceroute pvr traceroute to pvr (10.0.0.5), 30 hops max, 60 byte packets 1 _gateway (192.168.2.1) 20.167 ms 20.130 ms 20.122 ms 2 ....
(pvr is another box, configured for the same local net)
So, the route leaves the local net and wanders off into the ether..
So is there a local fix, or did I got what I asked for, just not what I wanted.
I'm presuming that previously all your local traffic went through your modem/router, with it just being a link to the Starlink device. And now you've removed that modem and just use the Starlink device by itself.
It could be that the Starlink device treats the 2.4 and 5 GHz networks as completely separate and won't communicate between them. Or it could be treating all traffic on its WiFi like that (guest or private networking).
It could also do what one of my dual-band routers did, and try to kick everything off the 2.4 GHz carrier onto the 5 GHz carrier (bandsteering). The trouble is various devices are 2.4 GHz-only and can't do that.
You could look for options like that (guest/private networking, bandsteering) on the Starlink device.
It's quite likely that all you have to do is change your LAN IP addresses to use the same private IP range as the Starlink device. Mixing 192.168.2.x and 10.0.0.y together without a suitable gateway *between* them is just not going to work.
You could go back to using your modem as your local access point. There are some advantages to using some separate kind of LAN hub outside of your ISP device.
* You can reboot the ISP device without killing all your LAN traffic. * You can probably get a better router than theirs, more configurable, able to handle more simultaneous connections, stronger WiFi, etc. * You can change ISPs without having to reconfigure your whole LAN around it (their supplied device might require a different local IP numbering scheme, they'll change your SSID, etc).
There are disadvantages, too. Such as NAT can be a pain for things like FTP, double-NAT can be even worse.
-
Geoffrey Leach -
Tim