Re: UPDATE/FIX: net/ocserv

2021-02-13 Thread Stuart Henderson
On 2021/02/12 17:51, Marc West wrote: > On 2021-02-11 21:32:08, Stuart Henderson wrote: > > thanks, i've adapted it to -current and then merged that (with the > > 1.1.1 update) back to 6.8-stable. > > Thanks for the MFC. On OPENBSD_6_8, patch-src_config_c and > patch-src_main_c are still present a

Re: UPDATE/FIX: net/ocserv

2021-02-12 Thread Marc West
On 2021-02-11 21:32:08, Stuart Henderson wrote: > thanks, i've adapted it to -current and then merged that (with the > 1.1.1 update) back to 6.8-stable. Thanks for the MFC. On OPENBSD_6_8, patch-src_config_c and patch-src_main_c are still present after a fresh checkout from a couple different mirr

Re: UPDATE/FIX: net/ocserv

2021-02-12 Thread Stuart Henderson
On 2021/02/12 00:21, Jake Stennett wrote: > thanks for the -current adaptation, I'm trying to write a patch to use cloned > interfaces without having to use MAKEDEV, I have the tun interfaces created, > but they won't go active unless I open /dev/tunN, I've looked through the > ifconfig code but

Re: UPDATE/FIX: net/ocserv

2021-02-11 Thread Jake Stennett
help. any chance you can point me in the right direction? From: Stuart Henderson Sent: Thursday, February 11, 2021 1:32 PM To: Jake Stennett Cc: ports@openbsd.org Subject: Re: UPDATE/FIX: net/ocserv On 2021/02/11 18:44, Jake Stennett wrote: > ran into this: &g

Re: UPDATE/FIX: net/ocserv

2021-02-11 Thread Stuart Henderson
On 2021/02/11 18:44, Jake Stennett wrote: > ran into this: > after 4 users connected, a 5th was unable to connect even after running > MAKEDEV to add more tun devices > > figured out this: > devname wasn't returning the tun name for /dev/tun4+. > > here is a patch to update the current version i

UPDATE/FIX: net/ocserv

2021-02-11 Thread Jake Stennett
ran into this: after 4 users connected, a 5th was unable to connect even after running MAKEDEV to add more tun devices figured out this: devname wasn't returning the tun name for /dev/tun4+. here is a patch to update the current version in ports to avoid this problem, this has been tested again