[–] 4 points 2 months ago (2 children)

Weird, I learned rhotic was pretty much standard dialect around the time North America was colonized ... wouldn't that mean it's the other way around in reality? (Honest no rage-bait question). I was taught and repeatedly read over the years that modern British dialect sounded more American then, and only changed with more inter-colonization from surrounding countries?

  • source
  • parent
  • context
  • [–] [S] 3 points 5 months ago

    Good to hear mikrotik fans here ... if there wasn't an abundance of Cisco equipment at my work I would be buying these for personal use instead, but these just wont die :P

    This will be for less capable persons needing a wifi hotspot for access to CIDR restricted services on our side. Keeping it stupid simple like a GL.iNet GL-MT3000 for clients if they perform well.

  • source
  • parent
  • context
  •  

    Looking for feedback on Wireguard capable wifi routers that keep a persistent link from the router to an endpoint. A lot of what I see advertised as "Wireguard Supported" sets up a server and not a client.

    The GL.iNET routers seem to do it, anyone with experience with these? https://docs.gl-inet.com/router/en/4/interface_guide/wireguard_client/

    Bonus for being able to push a wireguard client config to the device via API/cli.

    [–] 7 points 6 months ago

    M365 chat also fetches a copy of whatever secured file links you send to each other. Goes without saying, but never use Microsoft products if you value security.

  • source
  • [–] 13 points 6 months ago* (2 children)

    Ask a local ISP like us. We store our old servers and send them to be recycled annually. If I had an enthusiast walk up to our offices asking for a donation, we wouldn't hesitate. Can't speak for competitors, but it's worth a shot.

  • source
  • [–] [S] 1 point 6 months ago*

    The major one is botnets through compromised IPTV devices using these networks. We have a pretty small set of users ~4k but some cannot get service without satellite so they use these networks. We can't distinguish if these are compromised devices from our competitors (or in our problem case, a mobile user from 5 states away brute-forcing services). The ARIN data is very inconsistent and most of them don't add the local region.

    I guess we'll have to refactor with geo-location. Just wondering if there was an easier way out :P

  • source
  • parent
  • context
  •  

    cross-posted from: https://lemmy.world/post/46304716

    We’re currently implementing additional security controls for our hosting platform, and one of the biggest challenges we’re encountering involves customers connecting over mobile networks. As users move between towers or regions they are frequently assigned different IP addresses within very short timeframes, which complicates IP-based allow-listing.

    Is there a reliable way to obtain and maintain up-to-date CIDR ranges for major mobile providers such as AT&T, Verizon, and T-Mobile?

    For reference, we currently use this from Starlink that provides a public feed of their IP space.

     

    cross-posted from: https://lemmy.world/post/46304716

    We’re currently implementing additional security controls for our hosting platform, and one of the biggest challenges we’re encountering involves customers connecting over mobile networks. As users move between towers or regions they are frequently assigned different IP addresses within very short timeframes, which complicates IP-based allow-listing.

    Is there a reliable way to obtain and maintain up-to-date CIDR ranges for major mobile providers such as AT&T, Verizon, and T-Mobile?

    For reference, we currently use this from Starlink that provides a public feed of their IP space.

     

    We’re currently implementing additional security controls for our hosting platform, and one of the biggest challenges we’re encountering involves customers connecting over mobile networks. As users move between towers or regions they are frequently assigned different IP addresses within very short timeframes, which complicates IP-based allow-listing.

    Is there a reliable way to obtain and maintain up-to-date CIDR ranges for major mobile providers such as AT&T, Verizon, and T-Mobile?

    For reference, we currently use this from Starlink that provides a public feed of their IP space.

    view more: next ›