• Whooping_Seal@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 day ago

    I’m not surprised by the corporate network, it’s pretty common for those types of networks to severely block inter-device LAN communication. There are two solutions however, for one, KDEconnect has initial Bluetooth support. I think it only support Plasma and Android as of now, and could be documented better, but it does avoid the LAN access problems. The other solution is using a VPN, the easiest off the shelf solution being Tailscale, but I feel this is only worth it if you have multiple use cases for it (I use it for faster Syncthing transfers, Moonlight / Sunshine game streaming. And KDEconnect)

    I really wish KDEConnect “just worked”, similar to how Apple’s devices connect to one another, but I guess this is the price you pay sometimes for an open source cross platform solution.

    • rumba@lemmy.zip
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 day ago

      My home and corporate networks are both set up with igmp snooping.

      Problem with using tailscale is that if I’m at work, both my desktop and phone would have to be tailscaled home to connect which is not ideal.

      When I’m at home I need my phone to connect to my home desktop, when I’m at work I need my phone to connect to my work desktop.

      If they supported a list of static IP addresses that would work

      If they allowed DNS names as the targets that would work.

      If they could add IGMP multicast to their search capabilities that would work. IGMP is the option to be allowed to forward across networks.

      Bluetooth could work

      They could use MQTT or NTFY

      It’s probably about a billion ways to skin this. They basically just need some form of communication without knowing the exact target or being able to specify the target dynamically. I give it a shot every year or so get it to connect a couple of times and then eventually give up.