Post has attachment
clang(1) added to OpenBSD base on amd64 and i386.

Not yet the main compiler, but gcc is looking nervous.

Post has attachment

Post has attachment
BSDNow 190: The Moore You Know.

Post has shared content
Forcing the password gropers through a smaller hole with OpenBSD's PF queues http://bsdly.blogspot.com/2017/04/forcing-password-gropers-through.html - one of my moments of creative procrastination while preparing for an upcoming tutorial session. Enjoy!

Post has attachment
FreeBSD Journal: March-April 2017.

Crossposting from the OpenBSD community.
-----

I've been meaning to try out the new switch(4) pseudo-device, but I can't seem to get it working using the information provided in the relevant manpages (ifconfig, switch, switchd, switchctl, hostname.if, etc).

I'm using a PC Engines APU 2C4. em0 is connected to the internet, em1 and em2 are connected to my home LAN.

Here are the contents of the relevant configuration files:

# cat /etc/hostname.switch0
add em1
add em2
addlocal vether0
description "LAN switch"
group lan
up

# cat /etc/hostname.em1
up

# cat /etc/hostname.em2
up

# cat /etc/hostname.vether0
192.168.1.1 255.255.255.0
description "LAN"
group lan
up

# cat /etc/switchd.conf
listen on 0.0.0.0 port 6633

pf.conf passes traffic on em1, em2 and vether0:
pass quick on { vether0 em1 em2 } keep state

switchd is running.

The problem is, I can't ping 192.168.1.1 from my LAN, nor do I have internet connectivity. A similar setup using bridge(4) works just fine.

Does anyone have any pointers or a working configuration that they're using?

Post has attachment

Post has attachment

Post has attachment
BSDNow 189: Codified Summer.

Post has attachment
Official release of OpenBSD 6.1
Wait while more posts are being loaded