-
Notifications
You must be signed in to change notification settings - Fork 72
0.1.1 doesn't seem to add anything at all #13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi Dan, thanks for your feedback!
Also, please try this version. (I basically just made sure it compiled correctly and I added more debugging output where I suspect it could crash). |
if [[ $(which macosvpn) == "" ]]; then
# by flipping the version here, on 0.1.0 it works
sudo bash -c "curl -L https://github.com/halo/macosvpn/releases/download/0.1.1/macosvpn > /usr/local/bin/macosvpn"
# sudo bash -c "curl -L https://github.com/halo/macosvpn/releases/download/0.1.0/macosvpn > /usr/local/bin/macosvpn"
sudo chmod +x /usr/local/bin/macosvpn
fi
sudo macosvpn create --cisco name --endpoint my.endpoint.is.an.ip.address --username $vpn_username --password $vpn_password --groupname MYGROUPNAME --shared-secret $vpn_shared_secret I'll hopefully be able to spend a bit of time debugging later today. |
|
Ok, so far, the same thing happens to me. But then I ran it again and I got one log message further. Then it failed again 3 times, then it worked as normal and created the VPN as intended, then it kept failing again. I really dislike random errors :/ |
For what it's worth, I do see this warning log, but I even see that when it's working. So I don't suppose it's related. |
huh. Yeah, I just ran it 10 times in a row and 1 time it worked |
Maybe we need to convert it to Swift ;) I saw you're into that. I do wish I could speak it fluently. Either way, one of the recent code changes must have introduced it. I guess I'll have to go through it step by tep. Other than that, I recently upgraded Yosemite to |
If I run without
Don't know if that helps... Is there a way to pass in arguments when running from Xcode? Some breakpoints would be helpful. I've never touched an Objective-C command-line app before 😄 |
I have another macbook on |
I'm running |
See, that is how I originally intended the whole thing to work. That's how it was in the beginning. But at some point processes got prevented from elevating themselves. So I had to start using sudo.
Ah, I haven't even thought about that. You'd have to hack around somewhere in |
@halo This seems like a possibly bad build. I'm on OS X v10.10.5 and reproduce this issue with the GitHub pre-release binary; however, I cannot reproduce it with a local build of master (either Debug or Release build). Using the GH Release Binary:
Local build of ced57c1:
|
@steve-jansen Thank you for explaining how to run this as root and how to add arguments :) Now I have a reliable way to crash Xcode haha. Seriously, every time I run that, it gives me the beachball somewhere in the So, I just went through all changes recently made and I believe I solved it. Turns out, @Dan2552 Would you mind giving master a try? Simply create one Cisco VPN with group name and one without. And anyone who does that, needs to do it 10 times, because the crash only occurred randomly, and at random places :) |
(Because I had the problem locally and don't have it anymore, I went ahead and released 0.1.3 from latest master.) |
not having luck on my work computer running Yosemite. When I'm able to, I'll test on my home laptop again and do a bit of debugging with what Steve suggested. |
Ok, I think I found the issue. If the group is set, these Arrays need to have the size 9, otherwise 7. It works fine in each use case provided that rule is respected. I'm not sure how to initialize a |
Figured it out. |
Sorry to be the messenger... Doesn't look like everything is fixed; still failed but worked after running it a few times. |
Ok, this is getting ridiculous :) I experience the same thing now with the released executable (compiled for production). |
I just created dozens of services without problems. Both L2TP and Cisco, with and without group. 😮 I now uploaded the very executable I used just one minute ago for this into the 0.1.4 release. It was not compiled using "Archive", but it's simply the product of the debug "Command + b" building process. Would you mind trying that one? |
Yes! It works every time! |
Thank you indeed. I can sleep well again ;) |
@halo didn't we see a situation previously where the official archive build didn't work as expected, but, a debug build did? EDIT |
Yes, I was just going to point to the same post :) I'll try to keep an eye on it in upcoming releases. I'm wondering if Travis could catch this. Not sure if network services can be added there. Could be. |
Just to confirm: I'm working on integration specs which just call the macosvpn executable to test the actual functionality on Travis. The @steve-jansen So you were absolutely right. |
I turned off "Code Optimization" for the |
* Updated for Xcode 8 Still using Swift 2.3 though * Travis: Use XCode 8 * Sierra compatibility halo#21 I took the chance and converted VPNServiceCreator to Swift * Version bump 0.2.1 -> 0.3.0 halo#21 * Updated changelog halo#21 * bundle update halo#21 * Extracted CFArray enumeration halo#21 * XCode project update halo#21 * PPP keychain items didn't change name, only cisco did Closes halo#23 * Prevented an Xcode warning halo#21 * Unified exit codes in enumerator * Updated Xcode project halo#21 * Added Sierra to README * Trying to cleanup double-XAUTH interpolation halo#23 This appears to work on Sierra now. Reportedly on El Capitan as well * Version bump 0.3.0 -> 0.3.1 * Making bundler on Travis happy * Updated download links on README * Added exit codes to CHANGELOG for 0.3.1 * Ruby on Travis 2.2.4 -> 2.2.5 Some gems depend on it * Xcode automated Swift upgrade * Do not activate code optimization, it will break functionality See halo#13 * Upgraded PrettyColors vendor library halo#30 * Updated CocoaLumberjack halo#30 * Fixed a compiler warning halo#30 * Explicitly unwrap all interpolated optional strings * Updated changelog halo#30 * Added disconnect on switch/logout flags halo#33 * Added disconnect on switch/logout to help halo#33 * How about not breaking code halo#33 * Added specs halo#33 * Version bump 0.3.1 -> 0.3.2 halo#33 * Making rubocop happy halo#33 I know I cheated ;) * Pulled upstream DDOSLogger halo#35 * Updated Xcode 8.3 -> 9.0 * Fixed compiler warnings Simply by updating the upstream classes * Version bump 0.3.2 -> 0.3.3 * Travis tests Xcode 8+9 * Added changelog for 0.3.3 * Clarified macOS version requirement in README [skip ci] * CI: Try only xcode 9 * Added delete subcommand halo#36 * Bundle update Github noted a security vulnerability in rubocop: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8418 * Target ruby 2.4 in tests * Rubocop --auto-correct * Relax ruby version in Gemfile for Travis * Use default Travis ruby version * Rubocop happiness * Compare same datatypes only halo#37 This breaks on compiling on El Capitan * Travis runs Xcode 8 as well halo#37
It provides warnings fine if you miss out settings:
Warning: You did not provide a group name for service <abc>
The text was updated successfully, but these errors were encountered: