00:21:23 lw: https://botsin.space/@lexknowssystems/111791073584612720 00:21:24 Title: Lex knows systems: "" - botsin.space 00:49:09 _xor: what kind of doorbell camera is it? 00:49:23 sorry was scrolled far up for some reason 02:37:14 if a daemon starts up and creates a socket file, should it also delete the file when terminating? or is there another way to cleanly shut down sockets? 02:39:51 mason: yo, were you the one with the jail(8) segfault? 02:40:12 kevans: Yeah, parsing a bad config. 02:40:50 bad 02:41:24 mason: full name or just "mason" for attribution? 02:41:47 Mason Loring Bliss, although I only whined about it. 02:41:56 This is much different from fixing. 02:42:57 kevans: Abuse and scorn for not doing the legwork and submitting a patch might be more appropriate. 02:45:48 Sir, this is a Wendy's. 02:45:57 heh 03:25:58 mason: finding bugs is easy, actually reporting them deserves recognition imo 03:26:15 good repro is gold 03:29:01 Next thing to figure out (or implement if it doesn't exist) is to figure out jail numbers that's fixed on jail start but dynamic at rest. Which is to say, rather than having $ep = in my /etc/jail.conf.d/foo.conf I have $ep = $magicnumber for purposes of epair allocation. 03:29:28 like numbered taps for bhyves? 03:29:45 Possible? I haven't used Bhyve for more than "oh yeah, that seems to work" yet. 03:30:57 alepzi: Example /etc/jail.conf config: https://bpa.st/G7BA and then in /etc/jail.conf.d/foo.conf: https://bpa.st/4YMA 03:30:58 Title: View paste G7BA 03:32:43 So I'd like to have a magic number rather than hardcoding $ep in the config, with the notion that I could then ship the jail dataset (and reconstitute the config from properties) and not have to figure out a system-specific number. 03:34:54 Hm, I bet I can just use the jail ID. 03:35:51 Got to figure out when the jail ID is first known. 05:42:40 mason: https://cgit.freebsd.org/src/commit/?id=768149ff156e7d34a035853030bf946ca94cb461 05:42:42 Title: src - FreeBSD source tree 09:58:27 parv: missed you on the lagg thing from yesterday. I have been running lagg with NIC and wifi since 11 or 12 on my laptop. always worked great. same subnet of course. 10:23:04 my router has been crashing, always during the night. To debug it I left a couple of tail -Fs running from my laptop. The problem is, the FreeBSD running laptop crashes too... 10:26:12 pstef_: no dumps? 10:26:40 surprisingly, no. Probably I don't know how to turn them on 10:26:51 _xor: relevant to your interests https://lists.freebsd.org/archives/freebsd-ports/2024-January/005181.html 10:26:52 Title: Call for help: moving manpages to share/man 10:32:25 how can I see where a certain port is defining it's dependenciens ? 10:33:34 last1: dependencies should always be in Makefile 10:34:04 that I knew, but this one I Have no clue where it's coming from 10:34:18 somehow my nginx port is depending on libcrypto.so.12 which is openssl 3 10:34:30 which I don't have and don't want to install 10:35:02 nginx-1.24.0_14,3 depends on file: /usr/local/lib/libcrypto.so.12 - not found 10:35:16 is that defined somewhere else ? 10:37:45 that comes from security/openssl, if you don't want the nginx package to use that, then select base openssl when configuring it 10:38:07 hmm, or does nginx not have an option for this? 10:38:53 last1: try setting DEFAULT_VERSIONS+=ssl=base in make.conf and rebuilding it 10:39:13 (if you use poudriere, make sure to set that in poudriere's make.conf) 10:40:36 Seems I fixed my lagg setup on my laptop. I had some weird setup mistakes in /etc/rc.conf which somehow worked fine on 13.2 and before. But actually should have given issues back then too... 10:40:43 that did it 10:43:06 weust: what was the issue? 10:48:45 meena: for some reason in the past I had SYNCDHCP included on my ifconfig_wlan0 line, while having DHCP on the ifconfig_lagg0 line. 10:49:08 That meant that the default router was using wlan0 instead of lagg0 10:49:26 oooohhhh 10:50:14 and I had the MAC address to em0 set to the MAC address of em0 instead of iwm0. but in my dhcpd config I had a commented out line for the iwm0 MAC, and one for the m0 MAC. 10:50:18 em0* 10:50:55 No idea when or why I did that. the laptop is from mid 2018 so somewhere in the past 5 years I must have messed with it for some reason 10:51:23 Since I copied that setup over to the RPi4 I am now changeing that setup to reflect the laptop 13:43:08 Hello. I have installed FreeBSD 14. During boot it seems to be trying to mount da0 but "Medium not present". Could it be trying to mount the disk I installed from? 13:44:07 or ... maybe not trying to mount but looking for it 13:47:02 msamsing: like this? "cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed"? that's just reporting that it can't identify the disc in the drive because there isn't one, it's not trying to mount it 13:52:03 lw: Yes. Like that. Is it possible to fix it so it is not looking for da0? 13:52:34 you may be able to forcibly hide it with hints somehow, but... why? 13:59:29 lw: I was just wondering why it is looking for something that isn't there - and is not supposed to be there 14:00:24 how would it know it's not present until it looks? ... this is just a normal part of querying available devices on startup, every OS does this 14:00:46 it's not trying to do anything with it, it just wants some basic information about the device 14:13:03 lw: Ok. Good to know it's not a problem 14:19:24 am i reading the -CURRENT makefile right? that i can not just build man pages, in a /usr/src of current? 14:20:33 * meena tries 14:20:58 i see that i can do a mandoc -Tlint 14:47:46 kevans: Neat. Thanks for helping fix it! 15:27:36 nginx-devel from ports, with lua enabled: [alert] failed to load the 'resty.core' module (https://github.com/openresty/lua-resty-core); ensure you are using an OpenResty release from https://openresty.org/en/download.html (reason: /usr/local/share/lua/5.1/resty/core/base.lua:24: ngx_http_lua_module 0.10.25 required) 15:27:38 Title: OpenResty - Download 15:27:38 any ideas? 15:27:54 13-stable, nginx 1.25.3, openresty 1.21.4, lua-resty-core 0.1.27, luajit-openresty 2.1.20230911_2 15:40:10 Onepamopa, have you tried the nginx port to see if the same issue occurs? Do you need 1.25.x? 15:40:35 I'm installing it from port www/nginx-devel 15:40:44 And yes, I do. 15:42:07 Have you tried using the latest openresty module? Might be a compatibility thing... 15:42:23 installed all I mentioned from ports ... same thing 15:42:56 maybe the ports in mention haven't been updated recently by the respective maintainers, idk 15:44:45 Well the error message seems to say it is looking for a later version of the ngx_http_lua_module than what you have... 15:47:00 isn't ngx_http_lua_module built when "lua" is selected in port's make config ? 15:47:10 cause I've installed everything I could think of - no change 15:49:59 I think it probably comes from the openresty port... but I'm not 100% sure. 15:50:26 does phabricator email you automatically if you're the author on something that's committed? i got some mails from it about commits with my name on and i'm not certain why 15:51:32 solved by: /usr/local/share/lua/5.1/resty/core/base.lua ==> or ngx.config.ngx_lua_version ~= 10025  --> or ngx.config.ngx_lua_version ~= 10026 16:22:52 kqueue(2): "EV_CLEAR: After the event is retrieved by the user, its state is reset." - what does this mean? what state? 16:34:01 it also says, for EV_TIMER, "On return, fflags contains the events which triggered the filter." - does that mean fflags will contain NOTE_ABSTIME if it's an absolute timer? 16:34:04 lw: it's probably intentionally vague because the state it clears is different based on the hint, but see conditionals that check for EV_CLEAR, here is one example: https://github.com/freebsd/freebsd-src/blob/main/sys/kern/kern_event.c#L1026-L1029. 16:34:05 Title: freebsd-src/sys/kern/kern_event.c at main · freebsd/freebsd-src · GitHub 16:37:29 dstolfa: hmm. i'm curious specifically about the behaviour for EVFILT_SIGNAL because it says EV_CLEAR is set, but i don't see anything related to EVFILT_SIGNAL there... 16:40:17 lw: https://github.com/freebsd/freebsd-src/blob/768149ff156e7d34a035853030bf946ca94cb461/sys/kern/kern_sig.c#L4308-L4319 this is where the data gets populated, and this is what it means by EV_CLEAR being set: https://github.com/freebsd/freebsd-src/blob/768149ff156e7d34a035853030bf946ca94cb461/sys/kern/kern_sig.c#L4283-L4294 16:40:19 Title: freebsd-src/sys/kern/kern_sig.c at 768149ff156e7d34a035853030bf946ca94cb461 · freebsd/freebsd-src · GitHub 16:41:20 dstolfa: but what does EV_CLEAR actually do there? what changes about the event? 16:50:45 lw: in every knote that has it set, it will clear out the data and fflags. this usually means that it won't signal the event over and over again. for EVFILT_SIGNAL, this means that you can build your signal handling event loop in the "obvious" way 16:52:11 however, again, depending on the event type and various other things, it could mean something else which is why it's probably documented as vaguely as it is. i'm looking through the man pages to see if there's a good example of what it does, but i can't really find one that explicitly shows it 16:52:24 there's a lot of implicit stuff that makes sense if you know how it works, but could be confusing otherwise 16:55:53 hmm. 16:57:39 dstolfa: so the way i'd expect EVFILT_SIGNAL to work is i get one event per signal delivered to my process... but i don't want it to clear out fflags because what if another signal arrives before i can rearm the event? 16:57:44 has anyone used these instructions: https://wiki.freebsd.org/PkgBase to upgrade a jail/bastille to current? for testing purposes? 16:57:45 Title: PkgBase - FreeBSD Wiki 16:58:47 dstolfa: it's not clear to me if i reset fflags and re-arm the event, will it deliver the 'missing' signals then? 17:00:19 (this is at least how Solaris event ports worked, from what i remember... you set up your signal with sigaction() to tell it to deliver to the event port, then you just get one event per signal) 17:00:47 ofc freebsd is not solaris but this seems like the obvious way to implement it 17:04:16 lw: it's been a while since i looked at kqueue internals but i'm pretty sure you get all the signals, you just don't get the same signal multiple times when EV_CLEAR is set (but you would if it wasn't). that's the idea that the man page talks about when it comes to wanting to get notified about state transitions. there are a few examples on how you might implement a signal handling event loop in base, 17:04:22 see camdd or pmcstat 17:04:52 i'll have a look, thanks. this is basically described "edge-triggered" behaviour, right? whereas kevent is normally level-triggered 17:04:59 (might be easier if the manpage just said that...) 17:05:38 actually wait, is EV_CLEAR really just the "make this event edge-triggered" flag? 17:06:32 if so i am going to just add EV_CLEAR to all my kevents because i hate level-triggered behaviour 17:09:17 lw: depends on how you think of edge-triggered i guess. in this case, it would only trigger when the signal is delivered, but not when it's handled (for obvious reasons) 17:09:28 right 17:09:52 so like, a signal is delivered, then i call kevent() another 20 times, i don't get any more notifications, until i turn the event back on 17:10:19 wait, no. until another signal is delivered. 17:10:27 (otherwise that would be EV_ONESHOT which is different) 17:10:41 ... i might write a test program to understand how this works then submit a diff to the manpage 17:11:47 EV_CLEAR sounds like what we want for threaded programs though where you get an event, dispatch it to a thread pool, and might end up calling kevent() again before the handler has had a chance to read() or whatever 17:12:24 lw: better docs are always welcome :). might be helpful to even include an example that clears up stuff that you've run into so even if it's confusing in the text, there's at least code that demonstrates the interesting bits of behaviour someone might care about 17:12:38 am i going nuts or is there NO limit to how many "clones" of a nic you can make? 17:12:47 voy4g3r2: what do you mean by clones 17:13:03 i have the physical re0 and i want to have one for jails (VNET) and one for bhyve 17:13:19 errr, you probably don't want that 17:13:21 it looks right now, when i try to "connect" the bhyve to re0 it is "busy" and it keeps mentioning clone the interface 17:13:27 haha 17:13:35 could explain why it does not work 17:13:36 create a bridge, put re0 in the bridge, create an epair for the jail, put that in the bridge, create a tap for the bhyve, put that in the bridge 17:14:00 a tap is NOT a bridge? or am i just overthinking the terms 17:14:06 correct, a tap is not a bridge 17:14:24 a tap has exactly two endpoints, one is the kernel device, the other end is whichever program has the tap device opened 17:14:35 and if i want to have -CURRENT builld i CAN NOT put it in a jail.. think jail 17:14:42 an epair also has two endpoints, but both of them are kernel devices, so you can put one end in a VNET jail 17:14:49 yes, do not use tap for jail, use epair 17:15:36 okay.. and i need to use bhyve for -CURRENT? 17:15:40 voy4g3r2: it's a bit long (sorry) but here's a real-life example: https://www.le-fay.org/tmp/30d/RPXZZo.txt - tap0 is a bhyve vm, all those epairs are jails, ix1 is the external interface, and bridge0 is the one bridge to rule them all 17:15:52 if you want to run -current on 14.0 (or whatever) then yes you need bhyve 17:16:52 okay.. i am at point hwere bhyve has a freebsd-current image just the network is NOT working 17:17:04 and if i use that txt (thank you and nice on tolkein reference) i should get network 17:17:23 this is the rc.conf for that setup which is actually much simpler: https://www.le-fay.org/tmp/30d/6Vle6n.txt 17:17:27 and now i get why some of these tutorials i am reading, say have a multiple nic card in your machine :) 17:17:40 notice the two instances of 'auto_linklocal' which are important, ipv6 will break without that 17:18:10 wow, very clean and easy to follow.. i think you have been doing this quite a while 17:18:19 i am not cool enough to have ipv6 17:18:31 i tried to setup on home network and it was just acting up.. 17:18:43 voy4g3r2: this machine has an onboard re(4) (unused) and an Intel X540-AT2 with two ports (ix0 and ix1) 17:19:09 that was going to be next question is ix your nic card 17:19:16 s/card//g 17:19:20 yes, ix1 is plugged into the switch 17:20:10 lets see what i can break for being the bull in china shop 17:20:14 thank you for the guidance 17:20:27 i waant to get this man page pull request over to current because seems like "wasted" effort to do on 14.0 17:20:46 and i probably annoyed some people with all the udpates to the pull request.. i got some awesome help to break up the files into smaller commits 17:22:06 voy4g3r2: fwiw, rather than trying to do this with ifconfig, i suggest editing rc.conf based on what i pasted above, reboot, and see if it works. (take a back of rc.conf first in case it doesn't.) the main thing to be aware of is for a bridge, you have to put your IP addresses on the bridge instead of on the existing member interface 17:22:15 s/a back/a backup/ 17:23:04 so for a single bhyve vm you want something like: cloned_interfaces="bridge0 tap0"; ifconfig_tap0="link0 up"; ifconfig_bridge0="inet 10.1.1.1/24 addm tap0 addm ix1 up" except replace ix1 with your actual nic 17:23:33 and replace 10.1.1.1/24 with your actual IP address 17:23:49 the reason you set link0 is on tap is so it stays up even when bhyve exits, otherwise by default it will go down 17:27:23 ah 17:27:39 i was noticing an entry when bhyve instance was up 17:27:47 then when i turned it off to do "work" it went away 17:27:56 but i also was not going down the path you were 17:30:26 so everytime you add a new bhyve.. you update your rc.conf to then add more taps/clones depending on what youa re using? 17:30:51 yes 17:31:11 vm-bhyve can actually do this automatically but i found that annoying, i prefer to do it by hand 17:31:23 don't like random scripts messing with my interfaces 17:31:31 yeah, that would make sense 17:31:43 i was watching garyhtech youtube and he was using BVCP.. 17:31:51 i don't know that 17:32:10 so trying that.. but adding a nichttps://bhyve.npulse.net/ 17:32:12 Title: BVCP: FreeBSD Bhyve Project 17:32:31 i really need to NOT have ifconfig_re0="DHCP" 17:32:52 it makes setting up bhyve a lot easier but it falls when it comes to this NIC stuff 17:33:02 i don't know how to run DHCP on a bridge and also add members to it, maybe someone else does... 17:33:28 i have been delaying the transition.. DHCP should not be on a server.. clients yes, servers no 17:33:34 it goes on the list of fixing today 17:35:24 thank you for the example lw 17:48:26 lw, does sublime-music really require python >=3.10 ? 17:48:36 jbo: yes, the setup.py is full of lies 17:48:49 sorry, i know this makes it really annoying to build. i went through the same thing. 17:49:00 yeah, that's why I haven't committed this yet 17:49:01 lw, how did you poudriere-testport this? 17:49:10 jbo: i use python 3.11 17:49:18 it appears to ask for dependencies with flavor 3.10 that do not exist or something 17:49:20 I hate this. 17:49:21 so DEFAULT_VERSIONS 17:49:25 hmm really? 17:49:58 https://pastebin.com/CC4NhJ4Z 17:49:59 Title: # poudriere testport -p main -j 132Ramd64 -o audio/py-sublime-music[00:00:00] - Pastebin.com 17:50:15 uh that's weird 17:50:31 jbo: does it work if you set DEFAULT_VERSIONS+=python=3.10 ? 17:50:49 that's AFAIK not how ports are supposed to behave so I didn't test that :p 17:51:17 i would have thought it would automatically build some 3.10 packages if you had 3.9 as default but i guess not 17:51:29 are you sure that RUN_DEPENDS is sound? 17:51:33 this also applies to something else i want to port soon that requires 3.11 so it would be nice to solve it... 17:51:51 ===> py310-sublime-music-0.12.0 depends on package: py310-gobject3>0 - not found 17:51:57 ===> py310-sublime-music-0.12.0 depends on package: /packages/All/py310-gobject3-3.42.2.pkg - not found 17:52:07 hang on, let me git am and test again 17:52:31 I attempted this three times last week and luckily always got some customer crap to take care of instead :p 17:52:34 but also want to get the PR done... 17:54:09 RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}gobject3>0:devel/py-gobject3@${PY_FLAVOR} \ 17:54:27 i mean, this seems right 17:54:41 let's ask #freebsd-ports 17:55:09 I'm gonna let you handle this one, ok? once it passed poudriere-testport I'll take over again 17:55:21 please do make sure that it works without "hacks" such as DEFAULT_VERSIONS 17:55:44 ok, it's not a "hack", that's just how i build my ports because i want a newer python. i will testport it a blank make.conf though 17:56:13 so poudriere-testport on a 13.2-RELEASE jail worked for you out-of-the-box with the latest patch of the PR? 17:57:02 you're 100% sure that you don't have a /usr/local/etc/poudriere.d/make.conf (or make.conf per-jail) that does funky things? 17:57:14 jbo: on -current. but with my local make.conf (which includes python 3.11) which i didn't realise it would be an issue, so i will fix that. i did not deliberately "hack" this to make it build... 17:57:42 err - I didn't mean to insinuate something or blame you - trying to find solutions so we can get this moving :p 17:57:55 apologies if my wording was... suboptimal 17:59:03 god i wish testporting was less of a fucking pain in the ass (not a rant at you, just in general) 17:59:16 trying to maintain a development branch of ports and get poudriere to actually use it is far more annoying than it should be 17:59:40 huh? poudriere-testport is like the least pain-in-the-ass I have ever experienced working on any system that had something to do with "integrating" upstream software 17:59:54 just register multiple ports 18:00:21 that would be easier if poudriere ports -B actually worked to switch branches (unless that got fixed...) 18:00:32 nah, just use METHOD=null 18:00:35 right now i have to commit to my dev branch, then push it somewhere, then pull that in the poudriere checkout... 18:00:46 that way you can just handle the ports repo manually 18:00:50 nah 18:00:51 it's like 5 commits just to testport a one-line change 18:00:55 s/commits/commands 18:04:39 hehe.. without fail. typos are evil! 18:09:18 fun fact, poudriere supports supplying it a patch, but not for git 18:10:23 https://github.com/freebsd/poudriere/issues/1057 18:10:25 Title: poudriere jail -P doesn't work with -u · Issue #1057 · freebsd/poudriere · GitHub 18:10:25 1057 – this is a junk PR https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=1057 18:12:51 jbo: there are zero (0) ports which require python 3.10 or later and have RUN_DEPENDS other than audio/sublime-music. so... i don't know. maybe this isn't meant to work? 18:13:10 there are 3 ports which require 3.10+ and have BUILD_DEPENDS, but it's the RUN_DEPENDS which are the problem here 18:13:26 lw, is python 3.10 supported on 13.2 (and 14.0)? 18:13:30 meena, might now. I'm not a python guy. 18:13:34 s/now/know 18:14:03 jbo: i don't know, i can test that but it's definitely supported on 15.0 and it still doesn't work for me 18:14:16 :D 18:14:28 so for example i did # poudriere testport -p sublimemusic -j main textproc/py-TatSu 18:14:35 it would be nice to bump the default python… 18:14:36 and it's off building lang/python311 like you'd expect 18:14:53 but py-TatSu only has BUILD_DEPENDS 18:15:44 jbo: i will ask python@ 18:16:25 lw, alright! wanna assign the PR to yourself for the time being? :D 18:17:12 jbo: i don't think i have the magic bugzilla flag to let me assign bugs to people 18:17:18 this is restricted to committers iirc 18:17:36 are you mad at me if I assign it back to you? 18:17:44 that's fine, i will comment when i solve this 18:17:53 sounds good :) 18:20:43 lw, mediaelch still waiting for approval from mentors btw 18:21:16 jbo: makes no darn sense that a Qt app is easier to port than a Python app 18:21:37 well, that is one of the reasons I try to stay away from python where reasonable :p 18:22:48 I'm sure python@ will be able to shed some light on your particular issue - I just don't have enough python knowledge to help more directly 18:23:10 I just see that it's my duty to make sure that it builds under reasonable configurations and it doesn't seem to :D 18:23:41 i didn't realise sublime was python when i first looked at it but it's literally the only navidrome client that exists that isn't written in electron 18:23:49 (well maybe not literally the only one but the only useful one) 18:24:01 electron... probably the only thing worse than python :p 18:24:25 lw, I can mostly recommend emby 18:24:36 (although you are probably more interested in jellyfin) 18:26:32 i already use jellyfin but it's really bad at reading music tags for some reason, half my music ends up under 'unknown artist' 18:26:51 i could probably fix that with mediaelch but tagging 1TB of music in mediaelch would take years 18:28:28 jbo: interestingly now that you assigned it to me i can edit the assignee, so i will give it you back once i solve this 18:35:09 works for me 18:37:29 lw, I have to admit that my "listen to music" experience is not as great with emby 18:37:43 lw, I usually make sure that the audio files I import are already pre-tagged 18:39:13 jbo: all my music is 100% correctly tagged (i am really anal about this) but jellyfin still doesn't like it :-( 18:39:52 i'm using musickube on an nfs share for now which actually works quite well, i'm not sure if i'll end up actually using sublime 18:40:04 but even if not i'll keep maintaining it, nice to have more music apps 18:40:12 sorry, musikcube, not musickube 18:40:27 as a maintainer of a port you're somewhat expected to actually maintain the port - just saying ;) 18:40:37 > but even if not i'll keep maintaining it, nice to have more music apps 18:40:58 i've already submitted upstream patches to it, i think that counts as maintaining it :-) 18:41:14 it counts as maintaining if you _keep_ maintaining it ;) 18:42:02 i mean i just said i would do that. i already submitted an update to py-pychromecast and tested it with sublime even though it's not even in ports yet 18:43:04 good - that's nice/appreciated 19:18:43 jbo: can you please re-paste your paste with the sublime error? pastebin.com says it's expired 19:20:50 lw, not really. that ship has sailed :p 19:20:56 lw, would have to get back to that machine tomorrow 19:21:07 ah nm then 19:53:13 lw: sorry to bother again, i am looking throguh your output and i am curious, why are is an 'a' added to the ifconfig but when i looked at cloned_interfaces there is no 'a'? 19:54:33 i see the bridge0 uses the a version.. just not sure i understand the cloned_interfaces line 19:55:17 random question, is there a specific reason the emacs port doesnt have nativecomp enabled by default? i usually compile with that option but dont feel like starting to build ports on this machine 19:56:22 cedb, default options questions are usually best directed to the package maintainer (i.e. by e-mailing them) 19:56:29 cedb, also: https://forums.freebsd.org/threads/ports-huh-what-are-the-advantages-and-do-they-outweigh-the-disadvantages.91969/#post-639550 19:56:30 Title: Ports huh? What are the advantages and do they outweigh the disadvantages? | The FreeBSD Forums 19:56:38 voy4g3r2: epair is magical, when you clone one it creates both 'a' and 'b' automagically 19:56:42 voy4g3r2: i put the 'a' interface in the bridge and the 'b' version in /etc/jail.conf, but it doesn't matter, you could do it the other way around, both ends of the interface are identical 19:57:44 jbo: right sorry 19:57:57 ah that explains my next question on the epair2 it was the only one with both :) 19:58:17 you have a running jail most likely 19:58:39 voy4g3r2: the jail that normally has epair2b is not currently running 19:58:40 cedb, no need to apologize for anything 19:58:44 lw: and the ip address you are using as bridge, that is your "main" one 19:58:51 the .16 19:58:52 voy4g3r2: yes 19:59:14 got it, my freaking cheap router was offriding my ip address, got that fixed.. i guess the next thing is to just reboot 19:59:14 wait, no 19:59:17 and see what happens 19:59:34 this system's addresses are 10.1.6.13 and 2001:8b0:aab5:106::12 20:00:09 that was my typo.. i mean 13 not 16 20:00:18 i have way too many lines between these two files 20:00:25 i am old and had to print out to trace it all 20:01:19 well lets see what happens, thanks for confirmation 20:13:45 wow i got them, sweet! 21:00:20 err bvcp just use my bridge!! stop making your own@