KDE Connect - connection across routers
KDE Connect - connection across routers
I have two routers in my network, one master router and another supplementary one that extends the main one using a LAN cable.
My desktop and laptop are always connected to the main router, but my phone sometimes connects to the other, due to me moving about the house. I keep having to manually connect back to the main router when I need to use KDE connect. I don't want to 'Forget' the second router as it is the only one that covers certain parts of my house, such as the kitchen.
Is there a way around this? I had earlier connected the second router to the main one without a cable (wireless extender) and KDE Connect worked well in that config. I'm sure I'll need to provide some more info about my router setups, but I'm not sure what is needed, I can give more context in response to queries.
For one thing, you need to bridge your 2nd router and disable its DHCP server, effectively making it an Access Point.
If that's not enough to address your issue, you could also try setting the Wifi SSID and password the same, provided its set to use different channels than your main router, although this can make it a pain to force a device to switch from one router to another. (my second router also has a separate SSID partially because the one for the kids' devices and living-room TV shuts off for bed-time).
End of the day, unless you have commercial routers/APs or Mesh routers that are setup to inerroperate on the same SSID while using an Ethernet backhaul, there's going to be quirks and compromises.
8Or if OP really can't do that (that's by far the best solution), KDE Connect also lets you hardcode some IPs it'll try to connect to. Given the computer is on the main network, using the IP of the computer directly would make it work fine behind the second router.
But ideally, they really should be the same network.
3Just disabling the dhcp server did the trick, thanks!
2
So you have two separate LAN networks. Look into that second router if it can be made to work as access point. That would solve your problem.
6Why can't you just use a switch and an access point?
Why do you have 2 routers.
5Because I had a spare router lying around
2
Can't you just reconfigure your second router to act as WiFi repeater or get WiFi repeaters? The latter obviously involves additional cost
2Maybe it's your channel structure?
2You could restructure your network, but it's probably not necessary. My phone is always behind NAT on the secondary router's wi-fi. I got it working by:
- Reserving a static IP address for my phone in the secondary router's DHCP server.
- Forwarding that router's incoming ports 1714-1764 to the phone's IP address.
- Allowing outgoing traffic from that router's network to ports 1714-1764 on my workstation's IP address (on the primary network).
- Adding a device (my workstation) by IP address in my phone's KDE Connect app.
2Try removing your PC from KDE connect and redo the pairing through the second router.
I use tailscale to connect to my home network and that worked for me, KDE connect can now work both locally and through tailscale.
1