[MacPorts] #47554: openconnect compiled without UTUN support

[MacPorts]

#47554: openconnect compiled without UTUN support
--------------------------+--------------------------------
  Reporter:  tte@…        |      Owner:  macports-tickets@…
      Type:  defect       |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:  2.3.3
Resolution:               |   Keywords:
      Port:  openconnect  |
--------------------------+--------------------------------
Changes (by ryandesign@…):

 * cc: ryandesign@… (added)


Old description:

> Installed latest openconnect 7.05 from ports onto MacOS 10.8.2.
> Starting OpenConnect results in error messge:
> Failed to open tun device: Invalid argument
>
> .. but i did not want to install/use the 'tun' interface, but instead
> MacOS standard utun interface as supported by openconnect since 7.0
>
> When i downloaded openconnect from http://www.infradead.org/openconnect/
> and tried to compile myself, ./configure complained about IF_UTUN... not
> to compile, so the config file created did not include UTUN support. I
> did manually changed it and it compiled fine and worked fine. I do
> suspect that the port binary of openconnect might have had the same
> problem in compilation. I did not try to investigate why that compile
> problem exist (autoconfigure scripts are too complex).
>
> ALso note that the vpnc script that was installed by port openconnect
> seems to be quite outdated, aka: the package should be compiled with the
> latest downloaded from git.

New description:

 Installed latest openconnect 7.05 from ports onto MacOS 10.8.2.
 Starting OpenConnect results in error messge:
 {{{
 Failed to open tun device: Invalid argument
 }}}

 .. but i did not want to install/use the 'tun' interface, but instead
 MacOS standard utun interface as supported by openconnect since 7.0

 When i downloaded openconnect from http://www.infradead.org/openconnect/
 and tried to compile myself, ./configure complained about IF_UTUN... not
 to compile, so the config file created did not include UTUN support. I did
 manually changed it and it compiled fine and worked fine. I do suspect
 that the port binary of openconnect might have had the same problem in
 compilation. I did not try to investigate why that compile problem exist
 (autoconfigure scripts are too complex).

 ALso note that the vpnc script that was installed by port openconnect
 seems to be quite outdated, aka: the package should be compiled with the
 latest downloaded from git.

--

Comment:

 Replying to [ticket:47554 tte@…]:
 > Installed latest openconnect 7.05 from ports onto MacOS 10.8.2.
 > Starting OpenConnect results in error messge:
 > {{{
 > Failed to open tun device: Invalid argument
 > }}}
 >
 > .. but i did not want to install/use the 'tun' interface, but instead
 MacOS standard utun interface as supported by openconnect since 7.0
 >
 > When i downloaded openconnect from http://www.infradead.org/openconnect/
 and tried to compile myself, ./configure complained about IF_UTUN... not
 to compile, so the config file created did not include UTUN support. I did
 manually changed it and it compiled fine and worked fine. I do suspect
 that the port binary of openconnect might have had the same problem in
 compilation. I did not try to investigate why that compile problem exist
 (autoconfigure scripts are too complex).

 openconnect was updated to 7.06 in r137056 (#47945). Did that help?

 > ALso note that the vpnc script that was installed by port openconnect
 seems to be quite outdated, aka: the package should be compiled with the
 latest downloaded from git.

 Note that openconnect does not install a vpnc script, but it does depend
 on another port that does. openconnect switched from using the vpnc port
 to using the vpnc-scripts port in r137024 (#47180). Did that help?

-- 
Ticket URL: <https://trac.macports.org/ticket/47554#comment:2>
MacPorts <https://www.macports.org/>
Ports system for OS X