Hello,
again I fell in this problem, I must solve this now, so if someone has a
better idea than trying to reproduce the OpenVPN protocol begin and see if
there is any answer, I will have to figure out how to send the OpenVPN
protocol by UDP manually.
I would like to see if there is a simpler man
I use my own build to build this [1].
The OpenVPN project should have long ago separate between a some
components for ease of use:
1. OpenVPN
2. OpenVPN Windows Service Wrapper
3. OpenVPN TAP driver
4. OpenVPN Windows Installer
5. Easy-RSA
This would have enable users to build specific component
I tried to build openvpn on Windows from its source code and encountered a
few problems:
1. Incorrect defines at autodefs/defs.h, line 51-52:
#define PRODUCT_TAP_DEVICE_DESCRIPTION TAP-Win32 Adapter V9
#define PRODUCT_TAP_PROVIDER TAP-Win32 Provider V9
They are supposed to be:
#define PRODUCT_
Peter Stuge writes:
>> >> I am running a multihomed host where 'local ' must be
>> >> specified for proper operation.
>> >
>> > Could you add a route and use nobind? Unless you have one openvpn
>> > on each IP that should work.
>>
>> I would really like to avoid the NAT hackery.
>
> I didn't mea
Enrico Scholz wrote:
> >> I am running a multihomed host where 'local ' must be
> >> specified for proper operation.
> >
> > Could you add a route and use nobind? Unless you have one openvpn
> > on each IP that should work.
>
> I would really like to avoid the NAT hackery.
I didn't mean to sugges
Hi,
I just updated the requirements specification for the "community site".
It's available here:
http://users.utu.fi/sjsepp/openvpn/Community_site_requirements.mm.html
The specification was moulded to fit the Volere requirements
specification which I'm pretty familiar with. In this rush I could
Peter Stuge writes:
>> I am running a multihomed host where 'local ' must be
>> specified for proper operation.
>
> Could you add a route and use nobind? Unless you have one openvpn on
> each IP that should work.
I would really like to avoid the NAT hackery.
>> On ungraceful reconnects, the ne
Hi all,
Both today's and Tuesday's IRC meetings will be held at the
#openvpn-discussion channel, not #openvpn as stated previously. I'll be
monitoring the #openvpn channel and directing people to the right channel.
--
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc
irc freenode net:
David Sommerseth wrote:
> On 08/01/10 09:40, Samuli Seppänen wrote:
> > These are very valid concerns... even if all else goes smoothly, there's
> > probably lots of "noise" on the #openvpn channel. Any objections against
> > moving the meeting(s) to #openvpn-discussion?
>
> Right now, I'm not sure
