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
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 the
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
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 the
-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
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
Instead of running portmap together with dnsmasq in the nobody group, portmap
should get it's
own group/user called rpc. This patch adds the group/user.
Signed-off-by: Peter Wagner tripo...@gmx.atdiff --git a/net/portmap/Makefile b/net/portmap/Makefile
index 70499aa..3e8ae80 100644
---
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 experience
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 my
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 package.
Good
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
Add sysupgrade support for cns3xxx
Signed-off-by: Tim Harvey thar...@gateworks.com
target/linux/cns3xxx/base-files/lib/cns3xxx.sh | 22 ++
target/linux/cns3xxx/base-files/lib/upgrade/platform.sh | 122
target/linux/cns3xxx/image/Makefile | 19
Allow unlocking MTD partitions that exist within a partial eraseblock
This allows sysupgrade for devices such as the Gateworks Avila/Cambria
product families based on the ixp4xx using the redboot bootloader with
combined FIS directory and RedBoot config partitions
Signed-off-by: Tim Harvey
Add sysupgrade support for ixp4xx platform
Signed-off-by: Tim Harvey thar...@gateworks.com
target/linux/ixp4xx/base-files/lib/ixp4xx.sh | 25 ++
target/linux/ixp4xx/base-files/lib/upgrade/platform.sh | 156 +
target/linux/ixp4xx/image/Makefile |
Add a new UART I/O type for slow busses such as the ixp4xx
Signed-off-by: Tim Harvey thar...@gateworks.com
target/linux/ixp4xx/patches-3.3/160-delayed_uart.patch | 121 +
1 file changed, 121 insertions(+)
Index: trunk/target/linux/ixp4xx/patches-3.3/160-delayed_uart.patch
Spread-spectrum clock adjust support
The ixp4xx can be driven from a 2% down spread-spectrum clock. Doing so
however will cause your UART timing and system clock timing to be 2% slow.
This patch adds a kernel built-time configuration to adjust those clocks
so that running on boards with a
---
I think upstream was trying to separate the check for include file in system
include dir vs check for include file in any dependent library's include
paths. Ideally their configure script could be instructed to use something
other than / as its idea of the root for system include dirs, but
17 matches
Mail list logo
