Bug 206653 - [script] security/openconnect lacks starting script
Summary: [script] security/openconnect lacks starting script
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Ryan Steinmetz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-26 20:06 UTC by c.kworr
Modified: 2018-02-05 09:26 UTC (History)
3 users (show)

See Also:
bugzilla: maintainer-feedback? (zi)


Attachments
openconnect starting script (1.85 KB, text/plain)
2016-01-26 20:06 UTC, c.kworr
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description c.kworr 2016-01-26 20:06:36 UTC
Created attachment 166161 [details]
openconnect starting script

Hi. I created a simple starting script for OpenConnect.

PS: OpenConnect doesn't destroy `tun` iface on closing in nor reuses present `tun` interfaces. Restarting it a few time you will have a number of `tun` ifaces with only the last one used.
Comment 1 dwmw2 2016-08-31 13:16:48 UTC
(In reply to c.kworr from comment #0)
>  PS: OpenConnect doesn't destroy `tun` iface on closing in nor reuses present
> `tun` interfaces. Restarting it a few time you will have a number of `tun` 
> ifaces with only the last one used.

Hm... I thought we fixed all that. I have a vague memory of a set of patches to fix up the tun handling with net.link.tun.devfs_cloning=0, when (IIRC) it became the default.

I also remember the existence of crashes, such as the one in bug 204853.

I'd dearly love for someone who actually knows about the FreeBSD tun driver to take ownership of this...
Comment 2 w.schwarzenfeld freebsd_triage 2018-02-03 02:09:06 UTC
Is this still relevant?
Comment 3 Volodymyr Kostyrko 2018-02-05 09:26:06 UTC
Not for me, quit using it long time ago.