00:54:05 gitlogs: 04:35:47 Is there a way to get the console to go blank after being idle for some time? blanktime="300" and saver="daemon" don't seem to work these days. 04:54:33 hyperreal, See "man vidcontrol" and look for the screen saver timeout settings there. 04:55:57 I am not using the vt console myself at the moment, systems are either headless or have X running, so don't know this works from personal experience. 06:33:55 rwp thanks 08:13:09 Greetings 10:00:00 And salutations 13:14:44 hi everyone, I'm having a weird problem with FreeBSD 14.0-RELEASE-p6 on arm64. I'm trying something simple: create a gre tunnel. the interface comes up and I can ping the local private end of the tunnel, however I cannot ping the other end (private ip). what is weird is that even in the physical interface I cannot not see any gre packet when trying 13:14:44 to ping the other end. From the other end (openbsd machine) I ping my freebsd private IP and I can see the gre packets in the physical interface but there are no echo-replies sent back. I enabled net.inet.ip.forwarding=1, but Im not sure if something else is missing. Openbsd has net.inet.gre.allow=1 but I didnt find anything like that for freebsd. 13:37:51 jmon: sounds like your firewall might be blocking it 13:46:40 jmnbtslsQE: the freebsd machine is not running any firewall. and the problem is that internally I dont see the traffic from gre0  going through the physical interfaxe 13:51:35 OK, i ask because if the interfaces are configured correctly, typically that means that a firwall is blocking the outgoing gre. can you paste the intrerface config for your physical interface and gre interface on both machines? 13:52:16 or just the outgoing machine i guess since that's where your issue is now 13:54:49 maybe a route issue ? try netstat -rn4 (assuming IPv4); also make sure the gre interface is actually up. 14:05:36 agreed. it's either firewall, interface config, or routing. if he's seeing the packets on the interface it should be up 14:10:00 this is the freebsd box: https://clbin.com/AaDl1 and this is the openbsd: https://clbin.com/VyCPg 14:18:47 so you ping 10.255.255.2 from the freebsd machine and no packets are entering your genet0 interface? 14:19:39 exactly, while on the openbsd machine they do when I ping 10.255.255.1 14:22:26 hmm, maybe my assumption is wrong then, because i see no issue with the config on that machine. i guess you are certain that you have no firewall running 14:24:52 oh sorry 14:25:34 so, I dont have ipfw, ipfs, pf or anything similar running 14:25:42 GRE + NAT is the issue i think 14:27:10 strange that you're not getting any errors when you ping 14:27:34 actually when I ping I get ping: sendto: Network is down 14:28:02 yeah, the GRE interface will require that your local tunnel addr be an actual local address 14:28:24 one thing that bothers me is the list of flags on gre0; shouldn't the interface be in RUNNING state ? (IFF_RUNNING) 14:29:05 can you ping 46.23.91.142 from 78.18.50.37 ? 14:29:06 oh 14:29:07 I think it is not running because of the NAT problem 14:29:11 yeah 14:29:20 yes, I can ping the public end of the tunnel 14:29:22 78.18.50.37 isn't a local IP 14:29:23 i don't think GRE is possible in this case. i can't say i've ever tried this 14:29:32 that is the local public IP 14:30:06 jmnbtslsQE: should I change for an ip in the 192.168.0/24 network 14:30:23 i think your remote gre interface won't accept it because it has the "wrong" address 14:30:58 I can reconfigure the other end to use an ip in that range too 14:31:20 i'm sorry you're right 14:31:22 yes try that 14:31:38 let me give it a try 14:32:08 actually no i don't think that will work 14:33:20 yeah i'm just confusing myself 14:33:27 it will work fine 14:34:07 it's easy for me to confuse gre with other things i guess. 14:34:30 nope, no luck 14:34:44 I still get no traffic in the genet0 and I cannot ping the other end 14:35:36 even with local side of the tunnel set to your local IP? 14:36:53 yeah https://clbin.com/3PZBW 14:37:21 hmm no you don't need to change the "inet" address. you need to change the local "tunnel" one to your local 192.168.0.10 14:37:33 oh 14:37:35 the term it's a little confusing 14:37:38 is* 14:37:39 one sec 14:39:23 jmnbtslsQE++ 14:39:28 jmnbtslsQE: it is alive!!! 14:39:50 great. 14:40:28 thanks so much for your help! TIL the complications of GRE + NAT :D 14:41:12 and now that is configured properly the interface is running: gre0: flags=1008051 metric 0 mtu 1476 14:42:01 sure. good to know, i didn't notice that 15:18:28 is there a way I could configure how much pg-up pg-dwn move the buffer? It drives me crazy that it's only half a "page" 15:23:10 in which buffer? 15:32:52 sorry I accidentaly sent that here as well as somewhere else 16:40:36 after upgrading a jail to 14.1 and doing a pkg upgrade -f inside the jail I get "ld-elf.so.1: Shared object "libpcre2-8.so.0" not found, required by "nginx"" and some more for another program. What might be missing? 16:44:18 the host is 14.1 as well? did you try pkg-static upgrade? 16:53:14 yes. I think I found the error. ldconfig was not taking into account /usr/local/lib because of directory permission, it was group writable, I changed it to 750. 17:40:37 does the freebsd pf not support match directive? 17:54:52 seems like yes? https://man.freebsd.org/cgi/man.cgi?pf.conf(5) 17:58:30 thx 19:41:47 hrm 20:10:21 sorry for just asking... do you know which package provides /usr/include/security/pam_misc.h on freebsd? i do not know much about freebsd but want to test some code there... 20:11:54 I don't see pam_misc.h 20:11:59 do you mean pam_mod_misc.h ? 20:12:17 on linux it is called pam_misc.h 20:12:25 let me try 20:12:27 if so thats part of the base system, and not packages 20:12:44 on linux it is part of the package pam 20:13:07 on alpine part of the package linux-pam-dev 20:13:12 okay? 20:13:18 freebsd isn't linux 20:13:21 you see a file openpam.h maybe? 20:13:27 yes 20:13:29 i know... :) 20:13:32 okay... 20:13:46 which also isn't in a package 20:13:46 i want to compile this: https://git.xw3.org/xw3/checkpw 20:14:02 yeah, freebsd is very different... ;) 20:14:37 i wrote that program some time ago and wonder if it would compile on other OS's too since PAM ist stadartized 20:17:17 well, try it 20:17:38 you will probably have to ifdef a couple of #include's 20:18:10 yeah, i think you're right... i am trying 20:18:19 https://0x0.st/XYEO.h this is pam_mod_misc.h on freebsd 14.1 20:18:26 if that helps you identify it being similar 20:18:42 yes! 20:18:47 it compiles now 20:19:00 argh, no 20:19:35 stdio.h on freebsd is different... and produces an error. 20:19:49 thank you all! i think i am on the right way... 20:19:52 :) 20:21:02 👍 20:24:12 seems i have to learn more about freebsd this winter... ;) 20:24:53 i task i have on my todo since more then 25 years 20:50:13 https://termbin.com/6dqke 20:50:18 Dealing with some fuckery today. 20:58:26 we're all dealing with some fuckery, in a manner of speaking 21:03:11 Trying to figure out what the best location for files is $PREFIX/libexec vs $PREFIX/share. I've looked at some ports for examples but there doesn't seem to be any consistency. 21:03:14 I have a set of shell scripts. One is the "main" executable, then there are a bunch of 'libraries' (all of which are shell). I also have documentation, resources (example config files, example scripts, templates, etc.). 21:03:35 what's the recommended location for each type of file? 21:05:19 poudriere seems to put it's libraries in /usr/local/share while git for example puts them in libexec 21:11:24 Looks like /usr/local/share/ ( architecture-independent files) is the correct location 21:13:29 ideally you'll find answers in man hier, but i don't know how specific it gets 21:14:27 Yeah, I'm looking at that, but I can't tell where the best place is for non-executable sh libraries go 21:19:28 the one project that comes to mind is bastille, and they put them in /usr/local/share 22:49:23 Hi!, I'm about to move disks from an ubuntu VM (running on HyperV) to a FreeBSD 14.1 VM. In Ubuntu, to avoid changing mount points, one must mount them using UUID instead of /dev/xxx. Is it safe to mount using /dev/da0p1 (as an example) in FreeBSD? 23:31:15 oh geez. how the hell can I establish a connection to Express VPN if I want to use openvpn and stunnel? ChatGPT told me that if the ISP's firewall rules block openvpn's attempts to connect to express vpn, I should use stunnel. But then, no matter how many suggestions ChatGPT gave me, I failed to connect to Express VPN using the openvpn/stunnel combination. I am so frustrated. What have I been 23:31:17 doing wrong? 23:41:31 TLS Error: TLS handshake failed 23:41:33 why? 23:51:46 i haven't used stunnel, but i don't know how that would help. your ISP is filtering based on ports, right? but either way, openvpn is already inside TLS, i think 23:52:57 does expressvpn have an option to connect on port 443? 23:53:07 over TCP 23:54:44 you mean, chatgpt gave me a garbage suggestion? 23:55:07 and stunnel is useless in this scenario?