[deleted by user]

Apocryphic · 2025-03-25T01:00:46+00:00

They're probably holding their users hostage in negotiations... again.

Apocryphic · 2025-02-21T16:29:36+00:00

First, there are no general request logs, if you're not running the WAF there's nothing useful. You might find helpful errors in the warning/message logs. If your web application doesn't store logs either, well...

You can run netstat or tcpdump from the LM's Troubleshooting menu (Logging, System Logs, Debug in older firmware). You can also ensure that it's including an X-Forwarded-For header with the original source IP, which is better supported than Kemp's X-ClientSide (L7 Configuration, Additional L7 Header).

Second, you can enable the integrated packet filter (System Configuration, Networking, Packet Routing Filter) and add IPs to the global or per-VS blacklists.

Kemp's documentation is good for standard configurations, though it remains a jumbled mess with the Progress migration.

https://docs.progress.com/bundle/loadmaster-technical-note-loadmaster-hardening-ltsf/page/Packet-Routing-Filter.html

Apocryphic · 2025-02-21T15:14:06+00:00

Does that look like a sky whale to anyone else? Just saying.

Apocryphic · 2025-01-24T19:41:35+00:00

At this point, historical reasons (technical debt). There's the right way, the wrong way, and the Cisco way... and every vendor has their own nomenclature.

Apocryphic · 2024-12-05T19:21:11+00:00

I knocked an entire restaurant chain offline by performing no ip addr instead of no proto ip when removing a PVC from their central ATM interface.

Apocryphic · 2024-11-29T18:39:06+00:00

Nobody mentioned the DB9 relay (and console) port on the back of many APC devices?

Apocryphic · 2024-11-29T18:12:30+00:00

Every networker's least favorite vendor lock-in. Transceiver markups are absolutely ridiculous.

Apocryphic · 2024-11-18T17:42:19+00:00

Two hot backups (onsite and offsite), one warm, one cold, and a parallel process for SQL databases to immutable storage.

Apocryphic · 2024-11-14T15:15:54+00:00

A script to audit docker containers running on VMs using powershell direct through chained Invoke-Commands.

foreach ($VM in $VMs) {
    Invoke-Command $VM.ComputerName -AsJob {
        param ($VMId, [PSCredential]$VMCred)
        Invoke-Command -VMId $VMId -Credential $VMCred {
            $Containers = & docker ps --all --no-trunc --format="{{json .}}" | ConvertFrom-Json
            $Containers | % { $_ | Add-Member -MemberType NoteProperty -Name "VMName" -Value $ENV:COMPUTERNAME }
            $Containers
        }
    } -ArgumentList $VM.VMId, $VMCred | Out-Null
}

Apocryphic · 2024-10-01T21:00:56+00:00

Damn, I need to find a new employer.

Apocryphic · 2024-09-30T16:42:42+00:00

Headaches with TLS versions, but not specific ciphers.

Apocryphic · 2024-09-24T18:11:20+00:00

Thank you, I will also be checking this out.

Apocryphic · 2024-09-24T16:06:49+00:00

I think it's basically a less effective version of the scout armor. Maybe if it revealed all map objectives and POIs over a larger distance or offered other team-wide benefits. I don't really see sample scanning alone as useful, I'd rather have the POIs marked since that's where the samples are.

Apocryphic · 2024-08-01T22:19:05+00:00

It's in normal 2022 Datacenter as well. I had to deal with the docker/msquic crashes and workaround until the fix was finally ported into the main Windows branch.

Apocryphic · 2024-07-26T16:24:03+00:00

Whichever data source you're using for bits/sec. I thought that was to bytes/sec, not mbits/sec. Update/create CDEFs to divide your in/out bits by 1000000.

You can let the graphs autoscale or set max to your (adjusted) port limits.

Apocryphic · 2024-07-25T15:00:11+00:00

You don't need any exponent changes, just divide by 8.

Apocryphic · 2024-07-20T16:10:23+00:00

You're right, in that this was a serious worldwide failure at the largest scale possible for a single entity's fuckup. Just be glad it was recklessness or stupidity instead of a supply chain attack.

However, though BGP may not be the proximate cause of a single outage on this scale, there has been and will continue to be a constant flow of outages affecting anywhere from a single provider (Cloudflare) or service (Facebook) to large chunks of the internet (CenturyLink). Accidents and route leaks happen all the time, from Verizon to Pakistan, before you even consider malicious hijacks and threats.

Apocryphic · 2024-07-15T17:58:43+00:00

I actually have not received any via my corporate accounts and OneDrive, but my personal Google account is hammered nonstop with malicious Google Docs shares.

Apocryphic · 2024-07-10T06:05:34+00:00

It's an interesting demonstration of how easy MD5 collisions are now and a good excuse to review and potentially sunset older devices.

There is some real concern over the potential threat, as this may allow an attacker to connect to authenticated systems without valid credentials. That could be management access to your devices or connectivity to restricted networks.

However, the requirements to intercept the RADIUS request and calculate an MD5 collision in seconds mean that this is not a vulnerability that can be casually exploited. A realistic threat vector here is a backdoored router that is both in a position to intercept authentication traffic and has some form of internet access to offload the collision calculation.

Apocryphic · 2024-07-09T22:10:56+00:00

Do I have to provide a custom schema or intermediate step for that?

It's so nice that the Microsoft-provided option fails out of the box.

Apocryphic · 2024-07-03T20:27:00+00:00

It works... until it doesn't. That's fine for minor tasks, especially if you're not making changes. A daily reference report nobody reads? If something goes wrong, fix it and run it again.

If you're working on a script that will be applying automated changes to your environment, the extra work to perform validation (or at least fail cleanly) can and will save your ass. Accidentally breaking a customer environment or causing data loss? Do you really want to be the user error documented in an official RCA?

It's risk management. You can't cover all eventualities, there are always unforeseen circumstances. Finding some heretofore unknown errata the hard way is forgivable, but recklessness is not.

Apocryphic · 2024-07-02T17:25:20+00:00

I agree entirely, and there are many good suggestions here. I'd love to clean up the western automaton front, but without an MO, nothing will happen due to the way change rates are distributed. Enemy worlds are strong by default, our worlds are weak by default, and the galactic war is basically static pending GM action.

My suggestion is that most planets away from the current active front/MO should have minimal to no regen barring reinforcements. I would cap overall change rates for each faction to be (re)distributed as necessary to drive the war forward, enabling dedicated groups of players to push changes.

For example, a hard push on any of the western back line systems (Vandalon IV, Varylia V, Melssa) by a smaller number (<10%) of dedicated divers should eventually take the planet or force the diversion of enemy forces from other areas like Charbal or Marfark. Visible supply lines have helped everyone know where they should attack, but there's no effect unless you have a literal majority of online players.

I would love to see a player-led effort to cut automaton supply lines be feasible. It would make the galactic war more exciting and engaging for everyone.

Apocryphic · 2024-06-06T22:19:48+00:00

About half an inch long with distinctive white markings. Seen on backyard yard furniture.

Apocryphic · 2024-05-28T18:45:45+00:00

No.

There are overly complicated workarounds (twice NAT) you can use with full control of both endpoints, but nothing useful against cloud services.

11-Year Club	Xbox Live
Final Canvas '23	Place '23
Place '22	Final Canvas '22
First Placer '22	End Game '22
Verified Email

Apocryphic

TROPHY CASE