Changes between Initial Version and Version 2 of Ticket #47554


Ignore:
Timestamp:
Jun 3, 2015, 7:48:00 PM (9 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

Replying to 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?

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #47554

    • Property Keywords openconnect utun removed
    • Property Cc ryandesign@… added
  • Ticket #47554 – Description

    initial v2  
    11Installed latest openconnect 7.05 from ports onto MacOS 10.8.2.
    22Starting OpenConnect results in error messge:
     3{{{
    34Failed to open tun device: Invalid argument
     5}}}
    46
    57.. but i did not want to install/use the 'tun' interface, but instead MacOS standard utun interface as supported by openconnect since 7.0