Skip to content
This repository has been archived by the owner on Jul 4, 2023. It is now read-only.

openconnect's vpnc-script fails with sed error #18843

Closed
sorin-ionescu opened this issue Mar 30, 2013 · 5 comments
Closed

openconnect's vpnc-script fails with sed error #18843

sorin-ionescu opened this issue Mar 30, 2013 · 5 comments

Comments

@sorin-ionescu
Copy link
Contributor

vpnc-script in the openconnect formula is broken, and consequently, it fails to route through the tunnel. It wants GNU sed, and the script has to be patched for BSD sed.

sed: 1: "1p;/via/{N;p};/dev/{N;p ...": extra characters at the end of p command

Even with GNU sed installed, and every instance of sed replaced with gsed, it still fails to route through the tunnel. Instead, it prints the WAN and LAN IP addresses 13 times.

cc: @asparagui @robcast

@asparagui
Copy link
Contributor

k, i'm messing with 4.99 as we speak, one sec

@asparagui
Copy link
Contributor

pinged upstream, fwiw, the updated script in 4.99 doesn't touch sed so holding that patch for now

@sorin-ionescu
Copy link
Contributor Author

I broke it. It's my fault. I had a script called ip that prints my IP address in $PATH. The vpnc-script looks for a command called ip.

@sorin-ionescu
Copy link
Contributor Author

@asparagui How do you use openconnect? Have you created a LaunchAgent plist and a wrapper script to add routes you wish to tunnel?

for host in {foo,bar}.com; do sudo route add -host $host -interface tun0; done

@asparagui
Copy link
Contributor

i just update things randomly, glad there's not a problem 😸

@Homebrew Homebrew locked and limited conversation to collaborators Feb 16, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants