I solved the problem by copying the entire rule block right after
the old one and commenting out the old one.
New:
pass in on egress inet proto tcp to (egress) port $mail_ports \
keep state (max-src-conn 20, \
max-src-conn-rate 35/300, overload \
flush global) \
rd
On 2024-05-21, Maksim Rodin wrote:
> I solved the problem by copying the entire rule block right after
> the old one and commenting out the old one.
>
> New:
> pass in on egress inet proto tcp to (egress) port $mail_ports \
> keep state (max-src-conn 20, \
> max-src-conn-rate 35/300, o
On 5/20/24 09:37, Jan Stary wrote:
On May 20 13:22:26, mikyde...@yahoo.fr wrote:
Hello,
I have two use cases and problems with fsck.
1) When my openbsd boots after an outage, the system asks me to fsck /, /usr,
/var or /home manually.
So I do
fsck /dev/sd0a
And then I'm asked questions and I
On 2024-05-21, Nick Holland wrote:
> On 5/20/24 09:37, Jan Stary wrote:
>> On May 20 13:22:26, mikyde...@yahoo.fr wrote:
>>> Hello,
>>>
>>> I have two use cases and problems with fsck.
>>>
>>> 1) When my openbsd boots after an outage, the system asks me to fsck /,
>>> /usr, /var or /home manual
Hi
On 21/05/2024 04:01, jrmu wrote:
> Here is my configuration:
> Inside hypervisor:
> hypervisor$ cat /etc/hostname.em1
> inet 104.167.241.211 0xffc0
> inet6 2602:fccf:400:41:: 48
Why are you using 48 as mask here and not 64?
Here is a suggestion in term of routing.
From your configura
Greetings,
> > Here is my configuration:
>
> > Inside hypervisor:
>
> > hypervisor$ cat /etc/hostname.em1
> > inet 104.167.241.211 0xffc0
> > inet6 2602:fccf:400:41:: 48
>
> Why are you using 48 as mask here and not 64?
I don't have control over the hypervisor's gateway, that is provided b
As indicated here:
https://social.treehouse.systems/@AsahiLinux/112449204541186432
The system firmware that comes with macOS Sonoma 14.5 triggers a bug
in the m1n1 bootloader that is used to boot OpenBSD on these machines.
The bug will prevent OpenBSD from booting on some machines after the
mac
On 2024-05-21, jrmu wrote:
>
> --qhuug7BO2jqFJSbi
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> Greetings,
>
>> > Here is my configuration:
>>=20
>> > Inside hypervisor:
>>=20
>> > hypervisor$ cat /etc/hostname.em1
>> >
.
On 21/05/2024 22:04, jrmu wrote:
Greetings,
Here is my configuration:
Inside hypervisor:
hypervisor$ cat /etc/hostname.em1
inet 104.167.241.211 0xffc0
inet6 2602:fccf:400:41:: 48
Why are you using 48 as mask here and not 64?
I don't have control over the hypervisor's gateway, th
Greetings,
> > I also don't control the entire /48.
> >
> > Here is the information I was given:
> >
> > My IPv6 Address Subnet: 2602:fccf:400:41::/64
> > Hypervisor' IPv6 Gateway: 2602:fccf:400::1
> >
> > I was only given a /64.
>
> So you should use a /64 prefix length not the /48 which you hav
Hello!
This was the first thing I checked.
But I think there was a deadly combo of two factors:
1) the continuation character
2) The nuance described in man pf.conf:
"Care should be taken when
commenting out multi-line text: the comment is effective until the end of
the entire block."
After contin
On 2024/05/21 20:30, jrmu wrote:
> Greetings,
>
> > > I also don't control the entire /48.
> > >
> > > Here is the information I was given:
> > >
> > > My IPv6 Address Subnet: 2602:fccf:400:41::/64
> > > Hypervisor' IPv6 Gateway: 2602:fccf:400::1
> > >
> > > I was only given a /64.
> >
> > So you
12 matches
Mail list logo
