Re: Are there any OpenBSD Kernel/Architecture Books?
Den tis 21 dec. 2021 kl 02:14 skrev Thomas Windisch : > What resources would be a good primer on the OpenBSD kernel and general > architecture and give me a good understanding of the internals? > > FreeBSD has this: > > https://docs-legacy.freebsd.org/doc/13.0-RELEASE/usr/local/share/doc/freebsd/en_US.ISO8859-1/books/arch-handbook/book.html > > I understand that in OpenBSD there is the mantra that source code is > documentation. But as a beginner I'm afraid that I do need something > explicit that would allow me read the source code in an effective manner. For general kernel code, The Design and Implementation of the 4.4BSD Operating System, and for network/driver code, Stevens TCP/IP Illustrated Volume 2 is a really good choice. Even if it doesn't match 100%, when you "get" those books and how code is/was written, it will be far easier to get into the OpenBSD codebase. -- May the most significant bit of your life be positive.
Are there any OpenBSD Kernel/Architecture Books?
What resources would be a good primer on the OpenBSD kernel and general architecture and give me a good understanding of the internals? FreeBSD has this: https://docs-legacy.freebsd.org/doc/13.0-RELEASE/usr/local/share/doc/freebsd/en_US.ISO8859-1/books/arch-handbook/book.html I understand that in OpenBSD there is the mantra that source code is documentation. But as a beginner I'm afraid that I do need something explicit that would allow me read the source code in an effective manner.
Re: NAT fails to work from internal to external network
> pass out on egress from trunk:network to any nat-to egress > pass out on egress Looks like you (incorrectly) assumed that first matching rule wins? On 12/20/21 15:05, Ben Raskin -X (braskin - HIGH TECH GENESIS INC at Cisco) wrote: Hello, Misc; I'm attempting to configure a firewall using pf and have been having some troubles with NAT. The following is my config set skip on lo block all pass in on trunk from trunk:network to trunk:network pass out on egress from trunk:network to any nat-to egress pass out on egress Where trunk interface group is the internal interface. I am able to ping hosts on my intetrnal network from an arbitrary host on said network, however, I'm not able to ping some other host say 1.1.1.1. I've set sysctl variables for both ipv4 and ipv6 forwarding however nat stil doesn't work. Can anyone point me in the right direction, and show me where I went wrong? Thank you in advance. Ben Raskin
NAT fails to work from internal to external network
Hello, Misc; I'm attempting to configure a firewall using pf and have been having some troubles with NAT. The following is my config set skip on lo block all pass in on trunk from trunk:network to trunk:network pass out on egress from trunk:network to any nat-to egress pass out on egress Where trunk interface group is the internal interface. I am able to ping hosts on my intetrnal network from an arbitrary host on said network, however, I'm not able to ping some other host say 1.1.1.1. I've set sysctl variables for both ipv4 and ipv6 forwarding however nat stil doesn't work. Can anyone point me in the right direction, and show me where I went wrong? Thank you in advance. Ben Raskin
Re: I got a new ???em??? card. pf uses old ???self???
On Mon, Dec 20, 2021 at 05:38:45AM -0600, Luke Small wrote: > I reserved a new address for the new I350-T2 card and replaced unbound.conf > and all uses of it in /etc. > > ???tcpdump -aetvvipflog0??? still returns the old reserved address! > > What do I do? Post a more comprehensive bug report.
I got a new “em” card. pf uses old “self”
I reserved a new address for the new I350-T2 card and replaced unbound.conf and all uses of it in /etc. “tcpdump -aetvvipflog0” still returns the old reserved address! What do I do? -- -Luke
Got a new “em” card. pf uses old “self”
I reserved a new address for the new I350-T2 card and replaced unbound.conf and all uses of it in /etc. “tcpdump -aetvvipflog0” still returns the old reserved address! What do I do? -- -Luke
Re: Who is responding to my audio volume keys?
On Mon, Dec 20, 2021 at 09:59:29AM +0100, Richard Ulmer wrote: > Hi Alexandre, Hi Christian, > thanks for you responses! In the meantime Ralf Horstmann had also > contacted me and helped me find a workaround. > > Alexandre Ratchov wrote: > > Keyboard volume keys control volume of first audio device. > > We probably have different definitions of 'first audio device', but even > if I put 'rcctl set sndiod flags -f rsnd/1' into /etc/hotplug/attach and > 'rcctl set sndiod flags -f rsnd/0' into /etc/hotplug/detach, so that > only one audio device is configured at a time, the volume keys only work > for the internal device. > Sorry, I was refering to the first instance of the audio(4) driver, a.k.a the "audio0 at ..." in dmesg output. The volume keys are handled entierly inside the kernel with direct calls from the wskbd driver to audio driver, so the logic is completely out of the scope of sndiod or any program.
