On Wed, Jan 10, 2024 at 12:21:12AM +0100, Jonas Bechtel wrote:
>
>
> Dear "misc" list attendees,
>
> maybe someone of you has an idea what happened.
>
> Ten years ago I installed OpenBSD 5.[?] which included setting up a
> small partition of 2 GB, including the full OS with kernel, programs,
I'm running OpenBSD on a Protectli box as a router/firewall. The disk is
an SSD. Every now and then I reboot it ("sudo shutdown -r now") just to
make sure it comes back up. Several times it hung on disk errors that
the auto 'fsck' can't fix. I was able to manually run 'fsck' and answer
its
Dear "misc" list attendees,
maybe someone of you has an idea what happened.
Ten years ago I installed OpenBSD 5.[?] which included setting up a
small partition of 2 GB, including the full OS with kernel, programs,
web-related data, etc.. Occasionally the partition was full so I had to
gzip
On Tue, Jan 09, 2024 at 07:27:47AM +0100, Otto Moerbeek wrote:
> resreved means that the port number is below 1024. The RPC system,
> (which is used to implement NFS) iuses portmapper to determine which
> service runs on which port. What problem are you trying to solve?
I'm not a fan of that
Thanks for taking a shot at this!
I fiddled with the few options this AP has related to the 5GHz mode, nothing
special, really (channel width, number, mode). Interestingly enough, the AP
says its Country is set to 'EU' (whatever that means) - can't grasp why it
would report 'US', though.
On Thu, Dec 21, 2023 at 09:23:42AM +0100, Stefan Sperling wrote:
> could you send me a pcap of 5GHz beacons from this AP?
Nothing in the beacon you sent off-list stands out.
I don't see a reason why things wouldn't work as they should.
The AP is set to country 'US' -- if this is incorrect then
> On Tue, Jan 09, 2024 at 10:13:56AM +0300, 4 wrote:
> No need to be so dramatic, the ports only change when the service is
> restarted, so there is no need for constant monitoring and/or script
> running. Either you run the script (a one-liner, by the way, see below)
> on the server upon
> On Tue, Jan 09, 2024 at 10:13:56AM +0300, 4 wrote:
> These kind of off-topic remarks won't help you getting answers,
> -Otto
"i'm only human after all
don't put your blame on me"
On Tue, Jan 09, 2024 at 06:24:36AM +0100, Uwe Werler wrote:
> Take a look at the example in man relayd.conf. You have to set the X-header
> like:
>
> match header set "X-Forwarded-For" \ value "$REMOTE_ADDR"
> match header set "X-Forwarded-By" \ value
>
On Tue, Jan 09, 2024 at 05:14:47AM +, Valdrin MUJA wrote:
> I've got a question about TSO and LRO:
>
> How does enabling TSO and/or LRO on the Ethernet cards of a network
> device that will serve as a router and firewall affect the forward
> traffic of users accessing the internet behind this
On Tue, Jan 09, 2024 at 10:13:56AM +0300, 4 wrote:
> >> i'm quoting the man page for mountd:
> >> The -n flag historically allowed clients to use non-reserved ports
> >> when
> >> communicating with mountd. In OpenBSD, a reserved port is always
> >> used.
> >> "reserved port".
On Tue, Jan 09, 2024 at 10:13:56AM +0300, 4 wrote:
> i'm trying to solve the problem of which port need to open on the pf. the
> variant of processing rpcinfo output with script and then putting a rules
> into an anchor is not very pretty. especially considering that this is not
> enough, and i
On Tue, Jan 09, 2024 at 10:13:56AM +0300, 4 wrote:
> >> i'm quoting the man page for mountd:
> >> The -n flag historically allowed clients to use non-reserved ports
> >> when
> >> communicating with mountd. In OpenBSD, a reserved port is always
> >> used.
> >> "reserved port".
>> i'm quoting the man page for mountd:
>> The -n flag historically allowed clients to use non-reserved ports when
>> communicating with mountd. In OpenBSD, a reserved port is always used.
>> "reserved port". "always".. however the port is different each time. how to
>> deal with this?
14 matches
Mail list logo
