17:50 <johnjaye> o0x1eef: by the way, i had a question about setting up a "virtual lab" like you were mentioning

17:50 <johnjaye> if you want to say test a firewall you need a host A and a host B say both running freebsd to talk to each other. is that something you can do with jails? or do you need qemu and bhyve?

17:57 <adam12> johnjaye: Could probably do it wiht jails + vnet.

17:58 <johnjaye> ok. this seems like a common sense thing to want to do but.

17:58 <adam12> Then every jail gets it's own network stack.

17:58 <johnjaye> i've not gotten good enough to really set it up exactly

17:58 <johnjaye> like surely the idea of having 2 VMs to test networking is not a new idea

17:58 <johnjaye> so i figure i must be missing something

18:02 <adam12> johnjaye: There's software that does this for you, but it's beefy. Like GNS3

18:02 <adam12> And EVE-NG

18:03 <adam12> But you can probably get away with a Linux network namespace if you wanted. I use them sometimes when I am testing.

18:04 <johnjaye> sure. but i mean the equivalent of working in my garage

18:04 <johnjaye> ok. i'll look that up

19:00 <o0x1eef> I use a setup similar to what adam12 described :) All my jails are "thick" jails that have their own network stack (vnet) and then you can use /etc/pf.conf like you would on the host. So you could add host A and host B to each other's allowlist, and block anything else. I have one bhyve VM that's running Linux for ollama and that's basically a must to be able to get the most juice out of my gfx card.

19:00 <o0x1eef> No CUDA support on native freebsd.

19:01 <o0x1eef> On Linux I'm using nftables. It made me realize why I don't like Linux :D Too complicated.

19:01 <adam12> Getting vnet as a default in FreeBSD was one of the best recent changes they made.

19:01 <o0x1eef> +1

19:03 <o0x1eef> Here is my config: https://gist.github.com/0x1eef/421f940a3cabcc6af706603fde0d6398 - if you need any help getting setup feel free to reach out, either here, #freebsd, or by DM