10:05:59 <ivy> markmcb: that pkg-version issue will be fixed in the next pkg release, in the mean time we decided to also remove FreeBSD-ftpd (not freebsd-ftpd) entirely, since it was already slated for 15.0 and just wasn't done yet
10:21:40 <polarian> Does anyone have IPv6 working on wireguard
10:21:43 <polarian> for some reason I can't get it to work
10:21:50 <polarian> IPv4 works just fine, IPv6 works on my phone too
10:21:55 <polarian> so I know its not a router side issue
10:22:01 <polarian> pf isn't dropping the packet
10:22:07 <polarian> wg-quick routes seem to be correct
10:22:15 <polarian> yet no IPv6 packets will pass
10:37:49 <polarian> The host interface is IPv4 only, but this doesn't matter over a wireguard tunnel
10:39:17 <polarian> wtf it just started working without me even touching it
10:40:27 <polarian> oh wait it is firefox which is the issue
10:40:59 <nimaje> I would have asked for  netstat -r -W -n  and  ifconfig  output to debug the issue, but as it is solved…
10:44:30 <polarian> welp this is buggy asf, restarted wireguard and now it doesn't work again
10:45:48 <polarian> nimaje: sure sorry about that, I should have pastebinned that too
10:46:14 <polarian> it doesn't seem like firefox detects IPv6 though :/
10:49:13 <polarian> alright so, checking wg0 the IPv6 packets are passing out, but there is no response passing back in
10:49:19 <polarian> the response is being dropped for some reason
10:51:01 <polarian> nimaje: https://bpa.st/XRKPU here, stripped the public addresses out
10:51:42 <polarian> it literally just randomly worked for a few seconds and now isn't again
10:52:29 <polarian> oh wait it was because I was over ssh, thats why "it worked" xD
10:52:54 <polarian> it never worked basically I mixed up my terminals :P
11:00:40 <nimaje> can you look at the other side how it handles the packages? as you said they go out but no response is comming
11:06:20 <polarian> alright sure
11:06:27 <polarian> thats a good suggestion actually
11:21:34 <polarian> nimaje: no IPv6 packets hit the other side
11:22:32 <polarian> so I can assume my laptop must be dropping them then
11:22:58 <polarian> I see IPv6 packets from my phone going via the tunnel
11:23:13 <polarian> working just fine, but freebsd? nahj
14:55:22 <markmcb> ivy: that's great! thanks for closing the loop
16:25:21 <rtprio> ivy: hrm i ended up having to blast usr/local and /var/db/pkg and rebuilding everything
16:25:26 <rtprio> not sure what i was expecting
17:26:33 <polarian> ignore my IPv6 shit
17:26:35 <polarian> I found the issue :)
17:28:36 <nimaje> what was it? faulty firewall?
18:01:54 <dsmith> polarian, Yes, what was it?
18:18:09 <polarian> dsmith: making me say now are we? :P
18:18:26 * polarian is an idiot and assigned the same IPv6 to my phone 
18:18:35 <polarian> its classic bad documentation of your network
18:18:48 <polarian> the documented IPv6 address for my phone differed than the actual one in the config
18:19:17 <polarian> reason? I reinstalled android a lot on my phone in the last year, with DivestOS going EOL, then CalyxOS having trouble (and EOL for 6 months) and now on LineageOS :P
19:33:53 <CrtxReavr> polarian, the "documented IP" is likely a temporary (privacy extension IP) and the "actual" is probably an EUI-64 SLAAC IP.
19:36:38 <polarian> CrtxReavr: dunno what you are talking about
19:36:52 <polarian> the IP I had written down as allocated in my docs for my network differed from the one in the config
19:36:59 <polarian> in other words, I hadn't updated the docs
19:37:11 <polarian> which meant when I manually assigned the next "free" IPv6
19:37:27 <CrtxReavr> Okay - sorry for misinterpreting.
19:43:26 <CrtxReavr> rtprio, hope you remembered to change your shell back to something !under /usr/local.  >=]
19:49:30 <rtprio> the big thing was grub2 and curl
19:49:39 <rtprio> but then ports were so broken i had to start over
19:50:18 <CrtxReavr> Been there.
19:50:33 <CrtxReavr> Been a long time, fortunatly, but I've been there.
19:51:41 <CrtxReavr> Not letting things other than ports & pkg install things to $LOCAL_BASE goes a long way to help with that.
19:52:26 <CrtxReavr> I normally maintain a /usr/opt/ prefix for things I write, maintain, or compile by hand.
20:39:46 <ivy> kind of sad that freebsd pollutes /usr/local so badly people can't actually use it for its intended use.  i build my ports under /pkg instead
20:41:04 <rtprio> build them, or use them under /pkg ?
20:41:14 <nxjoseph> i don't think it's a pollution
20:41:24 <ivy> rtprio: i mean i build them with LOCALBASE=/pkg
20:41:52 <kevans_> how we do things work these days, now that we have user.localbase?
20:41:56 <kevans_> s/we/well/
20:42:45 <ivy> kevans_: i had to fix ~5 ports out of a few hundred, other than that it seems to work well.  i think it actually broke make -C release more than anything in ports :-)
20:43:18 <ivy> you will want my recent fix to /etc/defaults/rc.conf if you want to try it, otherwise the ldconfig path doesn't get set properly
20:44:57 <kevans_> hmm
20:45:25 <kevans_> things like syslog.conf are also a little bit of a challenge
20:46:02 <kevans_> you almost need some of these to be generated at build time to get it 'just right', rather than complicating everything with some form of variable substitution at runtime
20:47:25 <rtprio> ivy: do you use /usr/local for? ports rather than pkg? builds that aren't either pkg or ports? nothing?
20:48:01 <ivy> rtprio: things which are local to the system.  system-specific shell scripts, for example
20:48:44 <rtprio> that reminds me of the netbsd/pkg+pkgsrc pattern
20:50:06 <ivy> yeah, netbsd did this correctly
21:09:13 * CrtxReavr misses when you could just use portmaster to build/install/upgrade ports, and didn't have to phutz with poudriere.
21:11:39 <kevans_> dsynth?
21:11:43 <kevans_> or synth?
21:11:57 <rtprio> CrtxReavr: why can't you?
21:12:26 <CrtxReavr> There's always some that won't build.  It's very inconsistent these days.
21:12:26 <ivy> rtprio: practically a lot of stuff breaks with portmaster nowadays.  for example if you have freebsd-gcc installed, you can't build any llvm or rust ports
21:12:48 <kevans_> there's been a somewhat concerted effort to require clean environments for building ports
21:13:12 <CrtxReavr> Nothing in ports shoudl be build with gcc anymore.
21:14:04 <kevans_> that's a nice idea in theory
21:14:15 <ivy> CrtxReavr: freebsd-gcc is for building the base system
21:14:25 <CrtxReavr> How long did we wait to get gcc out of base?
21:14:26 <ivy> since we support doing that, freebsd developers need freebsd-gcc installed to test it
21:21:29 <impulse> What shell do you guys use? I'm coming from 20 years of using bash in linux.
21:21:44 <V_PauAmma_V> (t)csh
21:22:13 <ivy> impulse: zsh
21:22:29 <ivy> but if you like bash, you can just keep using bash, it works fine in freebsd
21:23:38 <impulse> yea, i'm trying to decide if i should keep using bash or try something with a BSD license to get the full BSD experience
21:24:00 <impulse> does tcsh use libedit these days?
21:25:42 <dsmith> The only thing that trips me up moving from bash to fbsd sh is lack of M-.  But I found a vi-mode command that is almost the same "_"
21:26:18 <dsmith> "vi-history-word"
21:26:19 <impulse> dsmith: you use plain sh?
21:26:34 <dsmith> On fbsd, yes.
21:26:46 <dsmith> For about 2 weeks now...
21:26:55 <ivy> sh is not too bad as an interactive shell since it got line editing and history search, i no longer feel an urge to change root's shell to csh
21:27:14 <dsmith> Used to use fbsd years (20?) ago.  Probaby used bash on it then
21:27:27 <V_PauAmma_V> impulse, "ldd /bin/tcsh" says it doesn't.
21:27:51 <impulse> oh but "ldd /bin/sh" does
21:27:53 <impulse> interesting
21:28:09 <CrtxReavr> Older bash versions supported a static-build option. . . I used to toss it in /bin/.
21:28:14 <ivy> impulse: i think line editing in tcsh predates the existence of libedit, which was written specifically to add line editing to NetBSD base tools
21:28:58 <impulse> ivy: yea looks like. i would probably prefer to use libedit though so i can have one configuration between all cli's
21:29:28 <impulse> dsmith: should be able to add M-. to your libedit configuration
21:29:34 <CrtxReavr> Changing root's shell to something not in your / volume is great. . . until something goes sideways and you can't mount /usr for instance.
21:29:37 <impulse> without switching to vi mode
21:30:44 <impulse> hmm no libedit on zsh either
21:31:10 <CrtxReavr> I remember db talking about having a sysadmin who refused to install vi becuase they thought it was too much of a resource hog.
21:31:22 <impulse> CrtxReavr: do you use sh as root then? or do you immediately invoke another shell when you log in?
21:31:51 <impulse> CrtxReavr: was that in an embedded environment?
21:32:07 <ivy> CrtxReavr: seems reasonable.  ed(1) (the standard text editor) only requires 1 line, vi(1) can use up to 80 lines.  that's 80x more lines!
21:32:23 <CrtxReavr> impulse, no. . . just old.
21:33:10 <CrtxReavr> impulse, I typically just leave root's shell as the csh default. . . and I alsomost every need to use it, 'cause I set my own shell as bash and 'sudo -s' keeps most of my environment, so. . . win-win.
21:33:45 <ivy> root's shell is /bin/sh by default now (since 13?)
21:33:46 <impulse> on my system, root's shell seems to be sh
21:34:11 <dsmith> impulse, Yes, I have `bind "^[." vi-history-word` in my ~/.editrc
21:34:47 <CrtxReavr> I notice it's set to sh on this VPS I IRC from. . . and I don't remember if I set that or if it changed somewhere.
21:35:15 <CrtxReavr> This is an old VPS. . . it was prolly installed as 5.x or 6.x
21:36:18 <CrtxReavr> Huh. . . must have changed to /bin/sh in a merge I didn't pay much attention too.
21:46:53 <impulse> oh. libedit doesn't have yank-last-arg. i guess it's not really a dropin replacement for readline
22:32:03 <dsmith> Yeah, the vi-history-word is not exactly the same. Adds an extra space.  Close enough for my muscle memory