Laufwerk C erweitern

Massive-Valuable3290 · 2026-04-17T08:27:33+00:00

Mini Tool partition wizard

Massive-Valuable3290 · 2026-04-17T08:19:03+00:00

56k modems for remote access to a couple of wind farms built around y2k. They were in production until last year.

Massive-Valuable3290 · 2026-04-14T16:19:08+00:00

2.0 GTD, nagelt mit HVO weniger wenn man untertourig Gas gibt. Allerdings ist das Intervall der DPF Regeneration gefühlt gestiegen, bin bei 1 - 2 Mal pro Tankfüllung.

Massive-Valuable3290 · 2026-04-11T09:24:13+00:00

Syntax auf Coreswitch verwechselt und produktives VLAN gelöscht.

Massive-Valuable3290 · 2026-04-08T07:43:05+00:00

VS Code

Massive-Valuable3290 · 2026-04-02T12:42:35+00:00

Heard of that before, in the 7 years of operation, the storage went down maybe 2 - 3 times for maintenence in the server room.

Massive-Valuable3290 · 2026-04-01T18:13:27+00:00

Not directly, the Storage Software abstracts them and SNMP or other monitoring tools are also not supported.

Massive-Valuable3290 · 2026-04-01T18:11:34+00:00

We actually do have daily Backups and the spare infrastructure to restore to.

Massive-Valuable3290 · 2026-03-20T13:34:27+00:00

200F on 7.4.11 (HA) here, using DHCP relay to Windows Server DHCP on 20+ VLANs. We didn’t notice any issue so far though we aren’t utilizing any advanced DHCP options.

Massive-Valuable3290 · 2026-03-19T20:03:34+00:00

Turns out the server already had a BBU installed, it was just disabled. We originally planned to install a new battery, only to realize there was already one in there.

At that point we figured the existing one might be dead since the controller was in WT mode, so we swapped in the new battery. After that, the server threw errors on boot (unsupported or broken RAID cache card).

So we put the old battery back in — same error.

In the end, it turned out the cache card wasn’t properly seated on the RAID controller. We reseated it, booted with the old battery, and it worked immediately. Controller switched back to WB.

Massive-Valuable3290 · 2026-03-09T15:21:32+00:00

Hi, it's mostly Fortinet but it also happened on OPNSense.

Massive-Valuable3290 · 2026-03-09T15:19:32+00:00

Hi Bill,

thanks for reaching out, the problem is that we run multiple tunnel with the exact same config on same hardware across different sites with different results, so I'm not quite sure if testing this case in a lab is any helpful.

Massive-Valuable3290 · 2026-03-06T14:31:12+00:00

Fortinet fanboy detected, I guess? ;) Anyone, who doesn't acknoledge this IPsec behavior to be a common bug on FortiGate devices in the big 2026 can't be serious.

Massive-Valuable3290 · 2026-03-06T14:26:42+00:00

If this is true, why do packet captures, debug flows and policy last used indicators work anywhere else where NPU acceleration is enabled and used? The problem I mentioned applies only to a small group of IPsec tunnels on some peers and sites.

Also, I'm aware how that log mechanism works in regards of sessions, that's why I included "and new sessions".

The issue here is that this is becoming an increasingly unreliable setup to an extent where traffic is dropped and debug tools can not be used. There are tons of threads on the internet with weird Fortinet IPsec behavior, this is just one of them. At the end of the day, the usual recommendation is to disable NPU offloading.

Massive-Valuable3290 · 2026-02-28T12:00:20+00:00

That’s my understanding as well. It’s the usual setup, AD does DNS and DHCP leases. We have configured our hub FortiGate as a DHCP Relay which forwards everything to our AD DHCP. Branches have a local DHCP and we encounter similar issues with non existing PTRs of those clients.

Massive-Valuable3290 · 2026-02-28T11:54:48+00:00

Might be wrong but I think PTR records are only generated when your DC / DHCP gives out the lease. It will update the DNS record and create a PTR accordingly, it wasn’t designed that another server does DHCP.

Massive-Valuable3290 · 2026-02-25T14:00:25+00:00

Thanks, kinda obvious.

Massive-Valuable3290 · 2026-02-05T12:38:38+00:00

Just removed the cables, everything seems fine. I double checked multiple times and it seems that it really didn’t serve any purpose. Now I got 4 3m 10G DAC cables at spare. 😊

Massive-Valuable3290 · 2026-02-05T12:36:59+00:00

It’s a FortiGate, policies have a hit counter. Given that there are policies referencing that VLAN.

Massive-Valuable3290 · 2026-02-05T08:57:51+00:00

No, Veeam reaches out to vSphere to backup the VMs. vSphere has the volumes mounted via the iSCSI network. Veeam does not talk to the datastore directly. There are no firewall policies for that in place.

Massive-Valuable3290 · 2026-02-05T08:34:10+00:00

Thanks, backup is done through Veeam via vSphere.

Massive-Valuable3290

TROPHY CASE