• 0 Posts
  • 20 Comments
Joined 10 months ago
cake
Cake day: January 16th, 2024

help-circle

  • Yeah I’d check for fragmentation, particularly coming from whatever was on the opposite end of this tunnel. This looks like librespeed (which is super simple to run in a container, ‘adolfintel/speedtest‘, if interested…I run some at work and it’s very useful) so I’m assuming it was running on the server at the other end of the wireguard tunnel?

    That latency and jitter are also absurd tho. Op should run a bufferbloat test on both sides. Though I don’t always trust those results from librespeed.



  • As a network guy…open up your favorite web-managed application and open the developer console. Inspect the transactions you see and compare it to the applications REST API reference, and you’ll likely find a lot of commonality (and maybe some undocumented endpoints!).

    Backend made the API and everything that is performed by it. Front end is doing the GUI based off the response and promoting for input.










  • But…why?

    Project Calico is designed for segmenting network traffic between kubernetes workloads.

    Right tool for the job.

    Also if you are a Fortinet shop, supposedly you can manage rules with FortiManager. I haven’t tried that yet but it looks really cool.



  • JasonDJ@lemmy.ziptoProgrammer Humor@lemmy.mlFirewall
    link
    fedilink
    arrow-up
    5
    ·
    edit-2
    9 months ago

    Oof I did a firmware upgrade on my main external firewall.

    The upgrade went fine but when we added an ISP a month or so prior, I forgot to redistribute the ISPs routes. While all my ISPs were technically working, and the firewall came back up, nothing below it could get to the internet, so it was good as down.

    Cue the 1.5 hour drive into the office…

    Had that drive to think about what went wrong. Got into the main lobby, sat down, joined the wifi, and fixed it in 3 minutes.

    Didn’t even get to my desk or the datacenter.


  • I had and loved my minidisc player back in the earlie naughties. The remote was great, but there was no standardization and it became a single point of failure. If and when it broke, you’d have to get the specific control for your MD player.

    It kind of lived on in spirit with in-line volume/call controls for wired headsets on the 4-conductor 2.5mm jack. Those were cool, and standardized.

    We could have a return to that, with USB-C, but I don’t think it’d see much more than a niche adoption. Smartwatches and fitness trackers do it just as well, and once you know the layout, you can skip/pause without looking. Plus most cordless headphones/earbuds have integrated controls as well. Streaming at home you have voice controls, streaming in the car they are on the steering wheel or stereo.

    The wired in-line remote is really only even applicable to the already niche community of users who refuse to adopt wireless. Considering most of those people are strict audiophiles, only something that has a quality integrated DAC would appeal to them. Thats a pretty specific product for a pretty small market. Not saying it wouldn’t be feasible, but it’d certainly not be cheap and simple.

    Tactile feedback is great though. I’m totally with you there…not many watches have physical buttons that you can locate and activate completely unaided by vision.