They also encourage you to provide info on yourself (create an account, provide birthday) to even use the screen on the seat back…

  • object [Object]@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    23
    arrow-down
    2
    ·
    4 months ago

    Wireguard vpn+pihole and you won’t need to watch those ads. Set it up to use an ntp port, and you won’t have to sign in to use the wifi.

    • Hol
      link
      fedilink
      English
      arrow-up
      8
      ·
      4 months ago

      Hold up, using the ntp port to skip WiFi sign in is a game changer. Any way to do that with Tailscale on iOS?

      • object [Object]@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        3
        ·
        4 months ago

        I have no idea how to do that on tailscale as I use pivpn on a vps. It works on Norwegian airlines and SAS, but I assume other systems might block traffic differently.

        • Hol
          link
          fedilink
          English
          arrow-up
          3
          ·
          4 months ago

          Definitely worth a bit of research to see if it’s feasible (or potentially just set up wireguard for those cases). Thanks!

    • bitwolf@lemmy.one
      link
      fedilink
      English
      arrow-up
      6
      ·
      4 months ago

      The airplane captive portals generally don’t work if you use a different DNS.

      I’ve always had to defer to “automatic” DNS and let DHCP give me the DNS address in order to access the wifi

      • linearchaos@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        4 months ago

        It is possible to use VPN over DNS. Some mad lads back in the '90s made a DNS server that would forward TCP packets over name service text records. The captive portals usually still let DNS pass. But it’s not like you’re going to be able to use any high bandwidth applications that way.

      • object [Object]@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        5
        ·
        edit-2
        4 months ago

        I just set up the server to listen on port 123/udp(ntp). You can also try port 53 although that isn’t always reliable.

        You should be able to change the port in the wireguard config file, restart the service, and allow traffic trough ufw.

        • wolfpack86@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          edit-2
          3 months ago

          Thanks, I saw you mention SAS. I fly with them often, I might try this out. (Usually log in and then flip on the VPN)

      • object [Object]@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        1
        ·
        4 months ago

        If you call security trough obscurity a security measure, then it’s really safe. Bots scanning for wireguard servers won’t find yours because they’ll be looking for the default port. In general wireguard will only respond to wireguard traffic, so a bot trying to exploit an ntp server will see silence as wireguard will not respond to actual ntp traffic.