On 12-12-17 11:48 AM, Joachim Schlipper wrote:
>
> I don't remember at what stage the .tgz was but I'm sure I have improved
> the scripts meanwhile. Since I see you're interrested, I'm going to fuddle
> my current files together into a new tgz.
Awesome. Thanks!
> The current implementation is t
Thank you very much.
I don't remember at what stage the .tgz was but I'm sure I have improved
the scripts meanwhile. Since I see you're interrested, I'm going to fuddle
my current files together into a new tgz.
The current implementation is thought in this way: when the (virtual)
interface
is bro
Nice work on netifdizing OpenVPN! I'm really looking forward to
patching all of your scripts from
http://pariah-angels.de/openwrt/openvpn-interface.tgz into my AA-rc1
installation I have here. Any chance you might want to publish an AA
ipk for it? :-)
I wonder what your thoughts are on the appl
On 10/04/2012 05:48 PM, Joachim Schlipper wrote:
> The openvpn-devel package won't disappear once the 2.3 version of
> OpenVPN is released, or does it?
I don't see any reason to continue this once 2.3 is out.
There are currently features in OpenVPN-trunk which are essential to
some users. Once 2.3
Am 04.10.2012 16:40, schrieb Mirko Vogt:
> On 10/04/2012 02:25 PM, Joachim Schlipper wrote:
>> Am 04.10.2012 14:05, schrieb Jo-Philipp Wich:
>>> If I am not mistaken then openvpn-devel is supposed to use the very
>>> same files as openvpn. Afair its files/ folder is symlinked to the
>>> openvpn pac
On 10/04/2012 02:25 PM, Joachim Schlipper wrote:
> Am 04.10.2012 14:05, schrieb Jo-Philipp Wich:
>> If I am not mistaken then openvpn-devel is supposed to use the very
>> same files as openvpn. Afair its files/ folder is symlinked to the
>> openvpn package.
>
> Good to read, that indeed eliminates
Hi,
On Thu, Oct 04, 2012 at 01:44:00PM +0200, Joachim Schlipper wrote:
> IPv6 works just fine with my setup, at least in my "simple" setup:
Cool :-)
[..]
> All of this works like a charm, so I'd say there's no problem with
> routing IPv6.
> But I'd be grateful to have someone with more experienc
Hi jow,
Am 04.10.2012 14:05, schrieb Jo-Philipp Wich:
> Hi.
>
> If I am not mistaken then openvpn-devel is supposed to use the very
> same files as openvpn. Afair its files/ folder is symlinked to the
> openvpn package.
Good to read, that indeed eliminates my concerns about maintaining
different
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
> what to do then with the openvpn-devel package, should it include a
> copy of all scripts which are also in the openvpn package? That
> would mean that patches would have to be applied to both packages,
> no?
If I am not mistaken then openvpn-d
Hi Jow,
Am 04.10.2012 13:11, schrieb Jo-Philipp Wich:
> Hi Joachim,
>
> integrating the netifd support into the main OpenVPN package is just
> fine, it does not prevent the traditional way of using OpenVPN from
> working therefore I see no reason to not integrate it there.
what to do then with t
Hi Gert,
IPv6 works just fine with my setup, at least in my "simple" setup:
I have a VirtualBox VM with OpenWRT running on my internet server, that
gets a (6to4) IPv6 address from HEnet (sadly my server provider doesn't
yet seem to know anything about IPv6) including a /48 subnet and runs an
Open
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Joachim,
integrating the netifd support into the main OpenVPN package is just
fine, it does not prevent the traditional way of using OpenVPN from
working therefore I see no reason to not integrate it there.
One main reason why your work isn't inte
Hi,
On Thu, Oct 04, 2012 at 11:29:49AM +0200, Joachim Schlipper wrote:
> as I didn't get reply in the forum (well, except for that spambot who
> kindly wrote on the thread), I dare to post my question again here.
>
> I'm quite eager to contribute my work on the OpenVPN netifd integration
> into t
On 10/04/2012 11:29 AM, Joachim Schlipper wrote:
> Hi,
Hi,
> I've thought about these possibilities:
> 1. Integrate stuff into existing package ('openvpn')
> 2. Create a new package (i.e. openvpn-netifd) and place all stuff there
> 3. Create a new package (i.e. openvpn-netifd) with just Makefile
Hi,
as I didn't get reply in the forum (well, except for that spambot who
kindly wrote on the thread), I dare to post my question again here.
I'm quite eager to contribute my work on the OpenVPN netifd integration
into the repository, but don't know which way to go.
I've thought about these poss
15 matches
Mail list logo