Re: trackpad reversed scrolling broken on -current

2019-03-25 Thread lists+misc
On Mon, Mar 25, 2019 at 10:53:08PM +0100, Ulf Brosziewski wrote: > You can make that permanent with an entry in wsconsctl.conf. However, > please note that the "param" field is for debugging and development, > there are no guarantees about its future. Thanks yet again, Ulf. For long term plans,

trackpad reversed scrolling broken on -current

2019-03-25 Thread lists+misc
Hello all - On the latest snap of -current, my reversed trackpad scrolling seems to have broken. My xorg.conf is as follows: Section "InputClass" Identifier "ws pointer" MatchIsPointer "true" Option "AccelerationProfile" "2" Option "AccelerationNumerator" "5" Option

Re: vultr

2019-01-07 Thread lists+misc
On Mon, Jan 07, 2019 at 08:44:03AM -0500, Nick Holland wrote: > Use their install ONLY to put your own bsd.rd in root (everyone seems to > obsess over loading an ISO. Who cares? Just use a -current bsd.rd!), > boot off that, reinstall exactly as you want it. The Vultr console > works great on

Re: syspatch, relink and kernel version/date

2018-12-20 Thread lists+misc
I can't confirm, but I think I noticed this on a box that was using the MP kernel even though it was an SP machine. On Thu, Dec 20, 2018 at 12:14:14PM +0200, Kapetanakis Giannis wrote: > Hi, > > I'm a bit confused about syspatch and kernel updates. One of machines after > latest syspatch (009)

6.2 starts nsd before slaacd binds ipv6 address

2017-10-09 Thread lists+misc
Hello all - I don't feel this warrants a bug report, but nevertheless feel that this behavior is inconsistent with the way dhclient works. I have a vultr server running nsd/OpenBSD 6.2, and I suspect that the move to slaacd from kernel code in 6.1 is what has broken my nsd config (it fails to

Re: af-to ipv6 -> ipv4 server

2017-10-04 Thread lists+misc
On Wed, Oct 04, 2017 at 11:50:10PM +, lists+m...@ggp2.com wrote: > It looks like I'm being delegated a /64 from Comcast no matter what I > ask for. Actually... I spoke too soon. After digging around some more, it appears that Comcast appears to have some sort of caching going on. If I spoof

Re: af-to ipv6 -> ipv4 server

2017-10-04 Thread lists+misc
It looks like I'm being delegated a /64 from Comcast no matter what I ask for. Here's the relevant portion of my dhcpcd.conf: interface re1 ipv6rs ia_na 0 ia_pd 1/::/60 vlan10/1/64 vlan1001/2/64 I've also tried ia_pd 1/::/56 my original config line before testing was: ia_pd 1 vlan10/0

Re: af-to ipv6 -> ipv4 server

2017-10-04 Thread lists+misc
On Wed, Oct 04, 2017 at 07:54:45PM +0200, Jeremie Courreges-Anglas wrote: > I'm reading contradicting stuff on the net, some posts say that comcast > will hand you more than a /64... if you ask for more, say a /60. Maybe > this is worth trying? I'll give that a shot when I get home. It may have

Re: af-to ipv6 -> ipv4 server

2017-10-04 Thread lists+misc
> No, that makes sense. Thanks! > SLAAC requires /64 interfaces. Does your ISP *only* give a /64? Many > will give a larger block using DHCPv6-PD (e.g. following Broadband > Forum TR-187). Unfortunately, (my tests seem to confirm) Comcast only gives me a single /64. I'm moving to a new ISP

af-to ipv6 -> ipv4 server

2017-10-03 Thread lists+misc
Hello all! I'm new to ipv6, and was hoping that someone could check my understanding of the af-to option. My ISP has given me a /64 block - say 1234:1234:1234:5d6f:/64 I have a subnet of servers that are ipv4-only, and want to use the af-to option to provide some of these servers with ipv6