On Mon, Aug 12, 2024 at 3:31 PM Peter Fraser wrote:
> I support a charity and I look after a OpenBSD firewall.
>
> The firewall supports asterisk, nsd, unbound, dhcpd.
>
> Everything was working properly.
>
>
>
> Then they did some rewiring, and the behaviour of the system is now very
> strange.
I support a charity and I look after a OpenBSD firewall.
The firewall supports asterisk, nsd, unbound, dhcpd.
Everything was working properly.
Then they did some rewiring, and the behaviour of the system is now very
strange.
When the system starts up, everything behaved properly, their phones r
On Wed, Aug 07, 2024 at 01:50:39AM +0200, David Uhden Collado wrote:
> > The rationale is that the installer is not able to make a reasonable
> > guess about
> > how you plan to use the system. It knows the minimum required filesystem
> > sizes, and if you have a moderate amount of extra disk it
On Sun Aug 11, 2024 at 01:52:22AM GMT, Kevin Williams wrote:
> When I try to configure the wallpaper by right-clicking on the desktop,
> Plasma goes to a blank screen with only the mouse visible.
I think your plasmashell crashed. Checkout for core files and report backtraces:
$ egdb /usr/local/bin
Hi all,
I am failing at a basic routing.
I have included this rule in my pf.conf:
pass out quick proto udp from any to any port 51820 route-to 192.168.1.254
I thought this would be force egress traffic with destination port 51820 to use
192.168.1.254 as a gateway, instead of the default gatew
We had another set of issues, this time with OpenBSD 7.5, fully patched
Same weird logging about nd6_ns_input: NS packet from non-neighbor
Again with an extra few bits (16-31) in the logged source link-local
address - we've discovered those bits are actually the ifindex of the
receiving interf
On Aug 11 21:44:52, oli...@gfuzz.de wrote:
> How do you guys trim your SSDs?
> Or shall I ask "do you trim your SSDs at all"?
>
> Does OpenBSD have similar functionality like
> https://man.netbsd.org/blkdiscard.8 ?
>
> I recently rented a phys. machine and installed OpenBSD on it[1], smartctl
> a
Nick Holland wrote:
If you really want to arrange the deck chairs on the Titanic, get a drive
a lot bigger than you need (say...250G for a firewall), allocate 20GB of
that for your FW at the front of the disk. In a year, replace that first
20G partition with a new one, in the next 20G of the dis
I would recommend to allocate up to 90% of your SSD in fdisk,
ignore the remaining 10% and don't worry about it again. The
10% should give the SSD firmware sufficient free space for
wear leveling.
Regards
Harri
9 matches
Mail list logo
