192.0.2.5 to any
At some point when the IP lease is renewed, the ISP has assigned an
address from another block e.g. 203.0.113.21/24. I would now think that
the block rules created by antispoof are obsolete as they are not
updated with the new address, but why should it still work without
interface name in parentheses?
ilter rule of:
Is it not even simpler to just specify the filter rule as block without
all, they seem to expand identical?
‐‐‐ Original Message ‐‐‐
On Thursday, July 16, 2020 9:33 AM, Stefan Sperling wrote:
> Nevermind, I have found the problem.
BTW some time ago I watched your EuroBSDcon 2017 talk on device driver
development. I found this introduction very clear and interesting.
on on whether hiding the ESSID is
ridiculous or not, I'm just testing different things, so I know which
features work and which don't.
pens, as I can't guarantee that none of the
devices within wireless range are malicious.
On Wednesday, June 24, 2020 10:58 PM, Aaron Mason
> Auto filesystem repair is bad juju.
Indeed, but an unbootable network appliance thousands of miles away,
is much much worse.
very small change compared to
have read only filesystems. Anyone who knows OpenBSD, will be able to
manage the firewall without special instructions.
to a MITM
attack, but I'm no expert.
ost -t gateway.local
Host gateway.local not found: 3(NXDOMAIN)
What could I be doing wrong?
the boot process at the exact time 'reorder_kernel' is running,
the system will break because of a corrupt kernel and repair is not
Is there a way to avoid 'reorder_kernel' during the boot process and
run it manually instead?
Thanks in advance.
routers without UPS, tell if
filesystem corruption is going to be a problem after power outages, or
if there are any officially supported ways to make the system resilient
enough to not break after a power outage?
I'm using an mSATA disk with MLC flash in the router.
Thanks in advance.
Mail list logo