Hello Jiri,
Am 14.01.2013 12:05, schrieb Jiri Slachta:
> why don't you send a patch to mailing list according to
> SubmittingPatches guide (
> https://dev.openwrt.org/wiki/SubmittingPatches )? You do not need to
> have write access, and this practice is quite good - everyone can test
> your packag
Sorry, I had a typo. correct link is:
http://www.schlipper.net/OpenWRT/openvpn-interface.tgz
Joachim
Am 14.01.2013 11:01, schrieb Christoph Thielecke:
> Hello,
>
>> I have created a bundle with the required files (quite a lot, because of
>> many up- down- connect- and disconnect- scripts) here:
>
I would like to add a new package that enables the use of openvpn
connections as netifd interfaces.
Each openvpn instance is then treated as a virtual network interface
which simplifies the usage, especially
with firewalling, re-configuration of network interfaces (ifdown ifup
sequences) etc.
I ha
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
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 s
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
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
ted with IPv6
recently. I'm willing to make it perfect, so I'm eager to learn.
Joachim
Am 04.10.2012 12:50, schrieb Gert Doering:
> 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 t
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
Hi,
Am 11.09.2012 13:53, schrieb Gert Doering:
> Indeed, it's that simple. I have just sent a patch upstream to change
> this in the openvpn git sources, as all "non-busybox" Linux versions
> accept that syntax as well - so we don't need to maintain an OpenWRT
> specific patch here.
That's grea
Hi,
this little patch does the trick. Busybox ifconfig just just doesn't
want the 'inet6' parameter, the rest is the same.
Joachim
diff -Naur old/src/openvpn/tun.c new/src/openvpn/tun.c
--- old/src/openvpn/tun.c 2012-09-11 11:02:41.0 +0200
+++ new/src/openvpn/tun.c 2012-09-11
Hello Philip,
I'm following your efforts with great interest, because I'm running OpenWRT in
a VirtualBox VM on a remote Windows (x86) machine and would also like to be
able to sysupgrade.
Unfortunately the project is on hold for the next 2 or 3 months because I have
other issues that require m
Sorry, my fault.
I feel a bit sheepish about it, because in fact I did make sure to update the
feeds before I tested it again.
But as it turns out I executed the scripts/feeds update in the wrong build
root, so it didn't affect my test build.
Trying to be more careful next time...
Joachim
On 1
Hi,
trying to build the zoneinfo package leads to an error because the required
file tzdata2011n.tar.gz can't be downloaded neither from
http://source.icu-project.org/repos/icu/data/trunk/tzdata/mirror/tzdata2011n.tar.gz
nor from the openwrt mirrors.
I've found the file with google somewhere els
Hi Lukas,
as far as I can see, you have three options of how to overwrite package
config files:
First, you can just create a "files" folder in your buildroot folder.
Every file you place there
will be copied over automatically right before building the image and
after all packages
have been built
Ah, now I get it. I guess I was thinking too complicated to realize that
it's that simple.
Thanks a lot!
Joachim
On 05/06/2011 01:42 PM, Jo-Philipp Wich wrote:
> With topdir I mean the directory where you run "make" in,
> feeds.conf.default and LICENSE are located there.
>
> As I also wrote initi
Sorry Jow, I didn't misunderstood what you meant with buildroot topdir.
I guess now you mean a "files" folder that is not in my package dir, but
somewhere in the build_dir folder (or any descendant), right?
Now I'm searching for the folder or any example that uses it, but I can't
find one. Could yo
gt; I agree that user files should take precedence over canned release files
> (actually, I thought this was the case?).
>
> -Philip
>
>
> On 5/5/11 10:24 AM, Joachim Schlipper wrote:
>> Hi Jow,
>>
>> thanks for the quick reply.
>> The problem is that if I j
Hi Jow,
thanks for the quick reply.
The problem is that if I just copy my own configuration file to
/etc/config/openvpn, it will be overwritten by the one from the
openvpn-package. So my config is lost.
Joachim
On 05/05/2011 06:16 PM, Jo-Philipp Wich wrote:
> Hi.
>
> Any mechanism that relies on
x27;s own - and since there is nothing to compile, it will
exit with an error.
define Build/Compile
true
endef
define Package/joachim-setup-openvpn/common
TITLE:=OpenVPN
SECTION:=net
CATEGORY:=Joachim's Packages
MAINTAINER:=Joachim Schlipper
endef
#
### set
ails
because of some openjade error (as it happened in my case).
This is my first contribution to the list, so please tell me if
something's wrong or if I could do smth better next time :-)
Signed-off-by: Joachim Schlipper
Index: libs/libusb/pa
21 matches
Mail list logo