It doesn't really matter I don't think. The OpenVPN config file is the same no
matter where you use it.
-brian
On 8/8/2012 10:50 AM, Sampsa Laine wrote:
I can run it from both an OS X box or Linux?
Which is easier to configure?
Sampsa
On 8 Aug 2012, at 16:55, Brian Hechinger wrote:
I should have some time today. Let me take a quick look at it and see. I can simulate your
setup so I can test it here before passing it off to you
-brian
On 8/8/2012 9:19 AM, Sampsa Laine wrote:
Brian,
When would be a good time to set up this OpenVPN thing for you?
Let me know.
Sampsa
On 6 Aug 2012, at 23:43, Sampsa Laine wrote:
I'm game - never set it up on a Linux box before, though
On 6 Aug 2012, at 23:13, Brian Hechinger wrote:
A possible option would be to setup an OpenVPN tunnel somewhere to go through. Maybe not
pretty, but it'll work.
If you want to try that email me off list and we can set it up on my colo box.
-brian
On Aug 6, 2012, at 16:00, Sampsa Laine <sampsa at mac.com> wrote:
On 6 Aug 2012, at 20:07, Johnny Billquist wrote:
Ah well, I could go on... Suffice to say that it's not because I'm opposed to the
features that a TCP connection, or DNS resolution would give, but I prioritize something
that I feel confident is working to features. And doing a proper solution with all these
aspects is more work than I have cared to put into it. The bridge program is a hack.
As Paul mention, pthreads would probably be a good start if you want to do something more
intelligent. You need to start thinking asynchronously.
My desire for this is basically because my ISP is NAT'd to hell - I have no way of
getting UDP packets back to my network, as the ISP gives me a non-routable address.
Why go with this ISP? Well it's about 3x faster than the DSL I can get in the sticks
over a 3G signal, with unlimited bandwidth and usage.
But sucks for HECnet..
Sampsa