It turns out the problem was with the file vpnc-script and the function
fix_ip_get_output(). There appears to be a conflict with the package
iproute2mac, which I had installed. After uninstalling iproute2mac (which
provides for an “ip” command on macOS), OpenConnect works as expected with no
sed error.
So, unless/until this is fixed in OpenConnect, Mac users experiencing this
issue may consider the workaround of uninstalling iproute2mac.
J. LaSelva
> On Sep 5, 2018, at 1:05 PM, J. LaSelva <justin.lase...@utexas.edu> wrote:
>
> Hello,
>
> I’m running OpenConnect 7.08 installed via Homebrew on macOS 10.13.6 and am
> having a problem connecting to my institution’s VPN. Specifically,
> OpenConnect will prompt for authentication and accept it, but will never
> instantiate the proper routes upon connecting. Instead, I get an error:
>
>> sed: 1: "1p;/via/{N;p};/dev/{N;p ...": extra characters at the end of p
>> command
>
> Here is my connection sequence:
>
>> Got CONNECT response: HTTP/1.1 200 OK
>> CSTP connected. DPD 30, Keepalive 20
>> Connected as x.x.x.x, using SSL
>> Established DTLS connection (using GnuTLS). Ciphersuite
>> (DTLS0.9)-(DHE-RSA-4294967237)-(AES-256-CBC)-(SHA1).
>> sed: 1: "1p;/via/{N;p};/dev/{N;p ...": extra characters at the end of p
>> command
>> Usage: ip route list
>> ip route get ADDRESS
>> ip route { add | del } ROUTE
>> ROUTE := PREFIX [ nexthop NH ]
>> Usage: ip route list
>> ip route get ADDRESS
>> ip route { add | del } ROUTE
>> ROUTE := PREFIX [ nexthop NH ]
>> Executing: /usr/bin/sudo /sbin/ifconfig utun1 up
>>
>> Executing: /usr/bin/sudo /sbin/ifconfig utun1 mtu 1322
>>
>> Usage: ip addr show [ dev STRING ]
>> ip addr { add | del } PREFIX dev STRING
>> Usage: ip route list
>> ip route get ADDRESS
>> ip route { add | del } ROUTE
>> ROUTE := PREFIX [ nexthop NH ]
>> Usage: ip route list
>> ip route get ADDRESS
>> ip route { add | del } ROUTE
>>
>> […]
>
> I’ve found this reference <
> http://lists.infradead.org/pipermail/openconnect-devel/2013-March/001019.html
> > to the same error but the user who reported it 5 years ago declared it a
> configuration issue. I don’t have any custom “ip” script in my $PATH, so I
> suspect my issue is unrelated.
>
> Any help you can provide is appreciated. Thanks.
>
> J. LaSelva
_______________________________________________
openconnect-devel mailing list
openconnect-devel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/openconnect-devel
