Wouldn't it be cool...!

What if you could set up a pf rule to: overload an ip address into a table if they tried to access the wrong port on an address and overload flush global immediately into a blocklist ( max-src-states 0)! or with max-src-conn-rate 2/60 when sshd behaves in such a manner as to confirm that a

Re: Cannot access internet with virtual switch

On Fri, Apr 6, 2018 at 4:40 PM, Aham Brahmasmi wrote: > Hello misc, > > Problem > A physical server with a switch (add em0 up) cannot access the internet. > However, the same host with a bridge (add em0 up) can access the > internet. > > Steps > $ ifconfig > em0:

[Arduino Library] Does WifiDriverInit() is missing in some package ?

Hello all, I would like to share my issue with the compilation of the sketch provided by arduino.cc concerning the Wifi Whield. After few try and some unrefferenced reference (IPAddress, WiFiDrv)... as expected i edited the MAkefile: LIBRARIES=SPI WiFi IPAddress WiFiDrv Question: as i still

Cannot access internet with virtual switch

Hello misc, Problem A physical server with a switch (add em0 up) cannot access the internet. However, the same host with a bridge (add em0 up) can access the internet. Steps $ ifconfig em0: flags=8843 mtu 1500 lladdr 22:22:22:22:22:22 index

OpenBSD-based network switch with >16 GigE ports.

Hello, I'm looking to buy a new switch for house network. Ideally I'd like to setup everything here on OpenBSD, but I'm not lucky to find any OpenBSD-based switch. I need just GigE ports, at least 18-20. Preferably fanless. 1-2U shallow depth into small rack. I know all those Marvells,

Re: Documenting library promises.

Ingo Schwarze wrote: > Hi Kristaps, > > Kristaps Dzonsons BSD.LV wrote on Sat, Apr 07, 2018 at 01:37:32AM +0700: > > > The only reason I suggest a standalone section is that it's easier > > to standardise across manpages. > > For that goal, using ".Ss Pledge promises" > at

Re: OpenBSD VMM VMs Crash

On Fri, Apr 06, 2018 at 06:55:05PM +0200, Aaron Marcher wrote: > Ohai, > > for me OpenBSD VMM VMs crash after some (undefined) time while logging the > following on the host: > vcpu_run_loop: vm 3 / vcpu 0 run ioctl failed: Invalid argument > Apart from that VMM works es expected. > > Regards, >

Re: OpenBSD VMM VMs Crash

On Fri, Apr 06, 2018 at 06:55:05PM +0200, Aaron Marcher wrote: > Ohai, > > for me OpenBSD VMM VMs crash after some (undefined) time while logging the > following on the host: > vcpu_run_loop: vm 3 / vcpu 0 run ioctl failed: Invalid argument > Apart from that VMM works es expected. > > Regards, >

Re: Documenting library promises.

Hi Kristaps, Kristaps Dzonsons BSD.LV wrote on Sat, Apr 07, 2018 at 01:37:32AM +0700: > The only reason I suggest a standalone section is that it's easier > to standardise across manpages. For that goal, using ".Ss Pledge promises" at the end of the DESCRIPTION might work. For now, such

OpenBSD VMM VMs Crash

Ohai, for me OpenBSD VMM VMs crash after some (undefined) time while logging the following on the host: vcpu_run_loop: vm 3 / vcpu 0 run ioctl failed: Invalid argument Apart from that VMM works es expected. Regards, Aaron -- Web: https://drkhsh.at/ or http://drkhsh5rv6pnahas.onion/ Gopher:

Re: Documenting library promises.

Kristaps Dzonsons wrote: > The only reason I suggest a standalone section is that it's easier to > standardise across manpages. I do not see a way to do this in libc. So standardise isn't really required. You are talking about doing this in a port library, not a base library.

Re: Documenting library promises.

>> .Sh SANDBOXING >> On >> .Ox , >> the >> .Fn khttp_parse >> function requires the >> .Qq stdio proc >> promises to >> .Xr pledge 2 . > > As long as it is only a single sentence, that could easily go right > after the description of the individual function in the DESCRIPTION, > or alternatively

Re: Documenting library promises.

> .Sh SANDBOXING And please stop using that word. It has been misused so many times, by now it is misleads. pledge is not a sandbox (whatever the hell a sandbox is)

Re: Documenting library promises.

Hi Kristaps, Kristaps Dzonsons BSD.LV wrote on Fri, Apr 06, 2018 at 09:57:09PM +0700: > Short: what do you recommend for documenting an external library's > pledge(2) requirements? That is an interesting question indeed. I never considered it before, so i will think about it in some detail.

Documenting library promises.

Hi folks, Short: what do you recommend for documenting an external library's pledge(2) requirements? Longer: https://bsd.network/@florian/99802355448571943 The question raised in this... um... toot?... is which promises are required by an external library call, in this case khttp_parse(3) in

is gif(4) not backward compatible between 6.3 and 6.2?

Hi, I am in need of setting up an IPV4 tunnel over IPv6 in gif between a 6.3-current and a 6.2 router.  Only I'm not able to establish the tunnel.  In revision 1.109 of /sys/net/if_gif.c there went a change that changed the next header (protocol) to IPPROTO_GRE (protocol 47?) and that's what I'm

Issues with relayd

Hi misc@ I am running relayd as a reverse TLS proxy on OpenBSD 6.3 release with the GENERIC kernel. I have noticed two issues that happen: (1) netstat reports that the Recv-q for the ip protocol steadily climbs and never goes back to 0 unless I restart relayd and (2) I am getting a lot of

Re: Compilations errors with plan9port on 2018/04/05 snapshot

On 04/05, Philip Guenther wrote: > On Thu, Apr 5, 2018 at 9:50 PM, Philip Guenther wrote: > > > On Thu, Apr 5, 2018 at 7:53 PM, Patrick Marchand > > wrote: > > > >> Output of compiling plan9port on amd64 with the april 5 snaphot > >> > > ... > > >

Re: iwi(4) fatal firmware error

On Thu, Apr 5, 2018 at 3:37 AM, Stefan Sperling wrote: > > Is this a purely cosmetic issue or does it actually prevent your > wifi connection from working? > > These looks like potentially harmless errors which happen during > association. > Does the driver recover from these

The modesetting driver uses acceleration or not?

Hello, In the modesetting video driver man page states that it is a non-accelerated driver, but you have a option to set the acceleration method. If it is non-accelerated driver why can you set the acceleration? Thanks.