Hi,
Two packages provide the proto l2tp netifd protocol: xl2tpd [1] in the
new packages feed, and l2tpv3tun [2] in oldpackages.
The config are totally different, the problem is really a name clash.
What is the recommended way to deal with name clashes in netifd protocols,
without breaking
Finally you do it succeed?
2014-07-19 15:54 GMT+08:00 OpenWrt openwrt-devel@lists.openwrt.org:
#16348: ramips(HLKRM04) can't scan wifi ap. showed an error
--+-
Reporter: astankvai@… | Owner:
Type: defect |
From: Christian Schoenebeck christian.schoeneb...@gmail.com
Date: Sat, 19 Jul 2014 11:14:01 +0200
Subject: ca-certificates: create symbolic link for certificate hashes
Implementing add-cert.sh functionality discribed at
http://wiki.openwrt.org/doc/howto/wget-ssl-certs into Makefile
otherwise you
Hi Baptiste,
thanks for the report.
I renamed the xl2tpd netifd protocol to l2tpv2 and kept the l2tpv3 as
l2tp as documented in the wiki.
Cheers,
Steven
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
The installation process on nand-based boards using ubi
like the BTHOMEHUBV2B makes use of a ramdisk image, so it
makes sense to generate this by default.
Signed-off-by: Ben Mulvihill ben.mulvih...@gmail.com
---
--- a/target/linux/lantiq/xway/target.mk2014-07-19 14:59:39.691201637
+0200
Some of the packages, apache with DSO, clamav with memory performance
options are easier to work with in the native compile arrangement.
Is see the http://wiki.openwrt.org/doc/howto/obtain.firmware.sdk but
that seems to be specific to one architecture.
I'm working with the Raspberry BCM2708
John,
any update on this issue? i strongly believe that the hard-coded
wndr4300 string somewhere in the source is the culprit of the problem
since the wndr3700v4 board_detection is identified as wndr4300 thus the
sysupgrade works for 4300 but not for 3700v4.
Regards,
-paul
On Tue, 2014-06-24 at
From: Christian Schoenebeck christian.schoeneb...@gmail.com
Date: Sat, 19 Jul 2014 21:31:04 +0200
Subject: [PATCH][packages] tinyproxy: no SysLog and no logging as non root user
1.) No SysLog possible because keyword misspelled
In tinyproxy.conf and tinyproxy.config the parameter is correct
Commit 40842 reverted the fix for tagged+untagged VLANs on AR8327:
https://dev.openwrt.org/changeset/40777
https://dev.openwrt.org/changeset/40842
According to jow, some people experienced some issues on older devices. Can
anyone tell me what were those issues?
Anyway, that patch modified some
Hi,
do a cat /tmp/sysinfo/* on the unit please ...
John
On 19/07/2014 20:52, Paul Blazejowski wrote:
John,
any update on this issue? i strongly believe that the hard-coded
wndr4300 string somewhere in the source is the culprit of the
problem since the wndr3700v4 board_detection
Hi,
On Fri, Jul 18, 2014 at 04:08:02PM -0700, David Lang wrote:
Yes, there will be some attacks that get through and start from the
inside, but there are far fewer that get into my network than to get
into the network of everyone I share an ISP with.
I also don't want these random
David == David Lang da...@lang.hm writes:
David go do a tcpdump of your WAN interface some time, look at all
David the attacks that are going on there (especially with an ISP
David that's not blocking it for you)
Bear in mind, scanning an IPv6 network is a self-inflicted
denial-of-service
12 matches
Mail list logo
