00:09:22 After upgrading to 15.1 there's a message to run service local_unbound setup. Well... that deleted all my config. :( I use it internally for my local lan and I could rewrite it easily however I didn't expect to overwrite the old config. 00:22:55 pertho: Someone just posted a matrix of Intel support on the forums You might want to look there. 00:42:08 is there a list of invalid characters in network interface names? 00:45:53 kerneldove: ifconfig(8) man page: Name may not be longer than 15 characters. No other character restrictions listed. 00:47:01 even '`"? that's wild 01:01:47 is there anything wrong with renaming network interfaces to arbitrary strings? it would be to help me keep track of which is which. like ifconfig epair5 create; ifconfig epair5a name foo-bar 01:05:30 thermos: I suggest creating a dataset on the host and nullfs mounting it in the jail 01:06:09 Maybe you can unjail a dataset that was previously jailed, but I think they aren't meant to be unjailed 01:07:37 ifconfig em0 name eth0 01:07:41 no, no problem at all 01:23:03 ok cool ty! 01:26:19 kerneldove: i forget that bhyve adds the host to the description. does jails do not? 01:26:39 description: vnet0 host interface for Bastille jail dns0 01:26:44 bastille does 01:28:52 rtprio it does but i need to distinguish interfaces i give to jails. the handbook uses the 4th octet of its ipv4 ip, but not all of my jails have public ips. some only have private ips because they're 'behind' a nat jail that has the public ip and proxies for the other jails 01:28:57 what do you think about that? 01:52:27 but then it would still at least have a jail name, ya? 01:52:43 ya 01:52:57 so sounds like you're coming to my idea of using jail name as interface name? 01:53:07 but i still don't see the problem? 01:53:28 k if a jail doesn't have a public ip, what unit number to use for "epair"? 01:53:31 that's the problem 01:53:42 doesn't your jail manager assign one automatically? 01:53:48 in the handbook, last octet of its public ip is the {id} in jail config 01:53:56 i don't use a jail manager 01:54:17 i haven't found something like vm-bhyve but for jails 01:54:27 like bastille? 01:54:32 is it? 01:54:40 which i don't think is quite on par with vm-bhyve but does a lot of what i need 01:54:57 it does manage to pick non-conflicting epair names tho 01:55:07 what does it base them on? 01:56:57 it renames mine to ed0a_hostname 01:57:07 * automagically * 01:57:13 what's ed0? 01:57:25 er, e0a_ it's the epair 01:57:30 if you want to change a jail's hostname does it rename the if? 02:00:31 bastille rename dns0 dns1 02:00:46 did if change? 02:01:46 i'm sure it would, -a would restart it, which would presumably recreate the interface 02:02:04 ok well it's an interesting idea 02:02:16 i already base jail name on hostname, so if too woul dbe consistent with that 02:02:24 e0_ is an interesting convention too 02:03:07 i notice ed0a_hostname has no unit number at the end. is the 0 the unit number? 02:08:29 rtprio ? 07:42:19 kerneldove: this is how solved it to create my jails https://dpaste.com/EBXCQWSHJ 09:20:25 anybody running recent CURRENT *and* poudriere? 09:21:03 specifically, newer than e91e8ebefadcce9d57c8ff945ff70050cbbe1ce1 09:21:17 poudriere fails creating jails, with `jexec: jail_attach(6): Operation not permitted` 09:27:12 it seems to be specific to poudriere, normal jails can be created & attached to 09:50:26 nwe ty, which part should i refer to pls? it looks pretty much like the stock code in the handbook for setting up a vnet jail? 09:55:33 kerneldove: what are you trying to do? I skimmed history and its not clear 09:58:15 dch come up with a scheme for jail interfaces (epairs) that handles the case where the jail either/both 1. doesn't have a public ip address 2. has multiple epair interfaces. so the handbook code creates epairs for jails using the last octet of its ip address as the interface unit number, like epair{id} where id is the last octet. but that 09:58:15 convention doesn't handle case #1 or 2 09:59:51 fwiw i name jails based on their hostname, without anything following ".", so myjail.lan would be named myjail, so i was thinking maybe name interface {jailname}{unitnumber}, like myjail0, myjail1... 10:17:06 aah ok 10:18:33 so the script linked by nwe just shows you that you can create & rename the epairs afterwards to anything you like 10:19:14 e.g. `ifconfig epair12345 create` 10:21:08 or `ifconfig epair12345 create name kerneldove123` 10:21:43 note that this last one only renames the `a` end, so you still have `epair12345b` to rename afterwards 10:28:12 why would `ifconfig epair12345 create name kerneldove123` only rename the a end not the b end? 10:28:55 and where does the nwe script show renaming interface? i know the syntax but i'm not seeing it in the script 10:52:49 dch 10:53:39 kerneldove: they only alter the description. The renaming of only one end of the epair is arguably a bug 10:54:18 but by now, likely a bug that people depend on, so unless somebody comes up with a clever way to handle it, a bug we can't fix without breaking existing setups 10:55:36 man that's fkd up 10:55:46 and ya definitely a bug. sheesh that sux 10:56:40 so would you run ifconfig epair12345 name foobar \n ifconfig epair12345b foobarb? 10:56:51 yup 10:57:00 like why not just introduce fix in 16 and put in a migration note? 10:57:08 we can't keep cruft around indefinitely 10:58:31 probably it would cause more frustration and problems 10:58:47 e.g. everybody using a pfsense / opnsense or similar tool now needs a migration script 10:59:19 there's no easy way out of this\ 11:00:05 but that's what major versions are for, an opportunity to make breaking changes that improve the OS 11:00:37 i respect not having churn for churn sake, but fixing a clear bug is not that 11:01:09 put yourself in the position of an org with 50 firewalls that are all offline because we made that change 11:01:20 and now you need to send out 50 engineers to fix that 11:01:30 its easy to say "clear bug, fix it" 11:01:52 its a lot harder to find a solution that doesn't break existing setups 11:02:31 you're welcome to file a bug for it, and maybe somebody can find a clever way to allow renaming both ends of the epair 11:02:48 maybe there's space for another flag 11:03:52 anyone upgrading major version without reading migration doc and making appropriate changes deserves that. the OS and its users shouldn't suffer due to lazy sloppy ppl 11:04:03 there's never enough protection to protect them anyway, so no bother 11:04:41 a flag could be a good compromise 11:08:06 hmm.. found the link: https://forums.freebsd.org/threads/intel-gpu-support-matrix.102846/ but how do I bloody read it? Says all Alder Lake gpus are supported, but I can't get drm to enable on Intel Graphics (ADL-N) - Alder Lake-N 11:12:29 How do I know if it's an Xe2/Xe3 (Bxxx/Cxxx) card? Seems to not have a version like that 11:20:30 https://github.com/FreeBSDFoundation/proj-laptop/issues/111 not much info here 11:36:04 ah ha.. https://www.linux-hardware.org/?id=pci:8086-46d3 Supported in Linux 6.9 and newer.. 15.0-RELEASE is 6.6 isn't it? What does 15.1-RELEASE have? 11:38:05 Don't suppose 15.1 will get 6.12? 11:38:45 i'd open a bugzilla bug with the information you collected, it'd help get that in 11:38:53 there's a strong push to get solid laptop support 11:40:14 kerneldove: drm-612-kmod was added last month but I'm not sure if it made it into 15.1 11:43:34 anyone know offhand what OSVERSION of 15.1-RELEASE is? 11:46:09 that's awesome 11:46:35 freebsd is so good in so many ways, that's why we need to have the courage to fix serious bugs dch! 11:52:55 pertho: OSVERSION=1501000 11:54:43 pertho: in this gist is a script called gather.sh https://gist.github.com/dch/68dd6f8d44dd76c558908e71dc3e1f87#file-gather-sh most of that info will be useful (pciconf, dmesg, acpi) 11:56:52 if you got as far as running Xorg then include /var/log/Xorg.log too but I'm guessing you don't get that far 12:04:47 dch: will do.. it's my wife's tablet so will have to pop the FreeBSD USB stick on it to gather the info when I get a chance :) 12:05:24 but it looks like graphics/drm-612-kmod just might support it 12:08:38 I wish I could figure out the firmware error my AX201 is getting connecting via iwlwifi(4) to my new WiFi 7 AP. 12:08:49 Not sure if I need newer fw or something. 14:34:55 Hi. Is poudriere (ZFS) broken on main (9417b115a283)? It works if I revert to f4cd99131c70. 14:58:02 dch recently asked about problems with poudriere on newer CURRENT too, maybe the same problem 15:01:03 thanks. I am running git bisect atm. 15:02:18 "specifically, newer than e91e8ebefadcce9d57c8ff945ff70050cbbe1ce1" "poudriere fails creating jails, with `jexec: jail_attach(6): Operation not permitted`" 15:52:52 Result of git bisect: e03ed9daeb49fffa1d16b8d00240c65e92650d01 is the first bad commit 16:01:40 Indeed, reverting this resolves the issue. des@ already requested reverting this change. 16:03:27 zapata: what's your test case for it? 17:03:15 zapata: it has been reverted 18:37:12 Greetings. 18:37:42 Welcome CuriosCat 18:39:29 Thanks, dnp1 . 18:40:24 Seems I've been slacking. Still on 14.2-RELEASE. Doing an upgrade now. 18:50:03 OK, 14.4-RELEASE-p6. That's better. Any thoughts or opinions on 15.x? 18:52:52 it's great 18:59:35 Good enough for me. I know I'll have to rebuild pkgs, but that's not a biggie. 19:00:01 I think since the upgrade to 14.4 is my ipfw nat setup broken, have I missed any interface changes? 19:02:42 it works on the host itself but not for the attached jails 19:02:55 the ABI changed between 14.x and 15.x. Did you reinstall packages? 19:03:25 I have updated to 14.4 (from 14.3) 19:03:37 so no abi change, and ipfw is in base 19:06:22 strange is icmp works but no tcp or udp 19:07:50 That makes it sould like firewall blocking. 19:08:26 yes, but I would like to recive mails from mailhosters which still only support legacy ip 19:09:42 I have mimimiced my config. this is the current output of ipfw show: https://paste.debian.net/hidden/22b2d6b1 19:16:08 Am I missing something here? Saw what I thought was a kernel panic on-screen, but the host is still running? https://i.imgur.com/h15rPDu.png 19:16:32 (15.1 on an old Dell R720) 19:16:47 uptime? 19:18:58 spork_css: that's a new one to me 19:19:16 this is a kernel panic, right? 19:19:32 3:19PM up 18:32, 2 users, load averages: 0.03, 0.08, 0.08 19:24:34 spork_css: It has 'EFI RT fault'. I think it's not a real panic. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291193 19:27:02 odd, I can't really tell if this is bad or not from that. 19:27:19 serves me right trying EFI for the first time on real hardware. :) 19:29:53 oddly enough the DRAC log shows one DIMM hitting "correctable error threshold" a few days ago, and prior to that (when this host was running vmware) but no similar log at the time the fault was recorded. and having seen that DRAC message, I also had let this thing run memtest86+ for a few days last week, I think I got about 8 clean passes and 0 errors. ¯\_(ツ)_/¯ 19:30:29 I'm trying out https://sylve.io/ as a vmware replacment, fwiw. 19:31:42 spork_css: I'm interested in hearing how things go. I'd like to move off of truenas here 19:35:45 dnp1: I walked in the room this thing's in yesterday, saw the bright white text in a familar shape on the screen, and walked out, so I haven't done anything with it yet beyond the initial install. 19:36:23 It looks promising, but also I see the commits have really slowed down, so I'm not sure if it's going to be around long-term. These single-dev projects sometimes kind of fizzle out. 19:37:12 I did raise a bug already - the whole web UI locks up (client-side) over some JS framework errors when trying to create a new zpool. 19:44:14 i love vm-bhyve; i don't see the appeal of the clicky ui for this 19:45:22 I don't run any full-time virtualization anywhere, so that's just a whole giant chunk of arcane knowledge I don't have to fill my head with. 19:45:53 I was using esxi before - I just wanted a simple way to supply an ISO, do an install and go about things. 19:46:53 I did have to start using proxmox at one job and that's... interesting, but also incredibly simple to use in most ways. But of course that also has the whole "vmotion" type thing where you can failover an entire host. 19:48:00 clicky ui is handy when you need fast and quick and also good for newcomers, you can always learn the internals later 19:48:41 Even for home use where you might have a little lab (like I do), it's still cheaper for me to grab some older hardware x2 and put proxmox or something on there and be able to test failover scenarios and such, or even use for things that I want to always be up (like Home Assistant or Plex). 19:48:47 i don't think any clicking is going to be faster than editing a 10 line shell file and restarting the vm, but :shrug: 19:49:19 I like choices! 19:49:44 choices exist because not only is everyone different, theyre unique 19:49:49 human factors in computing 19:50:06 But I'd already be using vm-bhyve I guess if I could migrate a win10 VM from elsewhere into it in 10 minutes. :) 19:51:38 when I did a few bhyve things by hand I just found myself spending hours trying to figure out things like getting a graphical UI up, how to make grub work, why there's all these loader choices, it's (for me) total throwaway knowledge that I don't want (it pushes out the good stuff when you get older, you know). 19:52:30 free vmware was basically feed it an ISO image (for a new VM), give it some parameters, and off you go with whatever paid work you're doing. 19:53:34 if I was copying a windows VM, macos VM, whatever, that was very simple - copy my vmdks and other files to another esxi host, import, answer the question about "move or copy" (ie: give it a new MAC and UUID or not) and that was it. 19:53:47 And free ESXi is gone now? 19:53:59 I believe so, I was running 6.7. 19:54:18 i created myself an ai that reads man pages, the handbooks, and the ports/pkg database so when i get stuck i can ask and get an answer, it helps. 19:54:28 I seem to recall broadcom canned it 19:55:30 yeah, I think they nuked not just their free "customers" but many commercial users that couldn't justify six figures or whatever noped out and that's where proxmox got so extremely popular. 19:56:37 another nice coup for linux - meet the users where they are with a useful replacement. 19:57:09 spork_css: sometimes the firmware does dumb things, so now we trap efirt calls and render that somewhat harmless 19:57:17 no happiness in linux though 19:58:50 kevans: I was looking at this, and it seems like there's some kind of parameters that would let me do something about the error (I guess tell the OS to stay out of certain memory regions EFI is using?) but I'm not clear on how that works. https://reviews.freebsd.org/D51146 20:02:12 of note sylve, like proxmox, mixes jails and full VMs in one UI - not sure about "containers" since I hate them and haven't gotten that far. 20:14:23 another quick one on the EFI "crash"(?) - and this is all just trying to understand the conceptual junk here, but are there processes running on the CPUs that are NOT the FreeBSD kernel and all it's child processes? Is there a little EFI shell of some sort at another layer (I know nothing about EFI except I don't use it). 20:23:14 spork_css: firmware still provides some interfaces that we can call into, in uefi these are the 'runtime services' 20:23:31 basically, you tried to do something -> we called into runtime services -> they faulted 20:23:39 from the context, this was probably the result of trying to set the RTC 21:01:27 Is true? 21:01:36 3.12 is the new default python? 21:03:07 dnp1: It's been gone for a while. 21:04:32 Thanks for the feedback 21:06:37 I think the consumerish product is free though. 21:07:03 vmware workstation the vbox like product. Forget the name for the macOS version. 21:07:24 fusion