On Thursday, May 24, 2012 05:53:51 Pedro Nuno Costa Rodrigues wrote:
I really must done a job and i really need some light in this issue.
I'm having a good openwrt+batman-adv experience and i'm enjoying a lot.
It seems there is a bug... i must wait a new release, thats right?
No release is
No release is necessary. The OpenWrt stable maintainer(s) need to backport
that fix to stable or you do it yourself or you use trunk.
Hello,
this conversation come out to be very interesting to me. I finally
realize why Ninux Pisa uses OpenWRT trunk and not a stable realease.
Marek may I ask
Yes we use TRUNK in ninux pisa for that bug of backfire and also because
of Ethernet driver crash on backfire that seems not affect the new
kernel in trunk ( but to be sure we have to do some more testing )
On 05/24/12 10:20, ZioPRoTo (Saverio Proto) wrote:
No release is necessary. The OpenWrt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Your username looks wrong. It is supposed to be the 32 byte md5 sum
representing your user id, you can find it in your tunnelbroker.net
profile page. tb4... for sure does *not* look like an md5 hash.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG
On Wed, 2012-05-23 at 20:26 +0200, John Crispin wrote:
On 23/05/12 20:07, John Crispin wrote:
i think we should change this to not use xtu bits unless explicitly set
can you try with this patch applied ?
Success.
That patch didn't work. The -i is necessary. It's also a critical param,
On 24/05/12 13:41, Conor O'Gorman wrote:
On Wed, 2012-05-23 at 20:26 +0200, John Crispin wrote:
On 23/05/12 20:07, John Crispin wrote:
i think we should change this to not use xtu bits unless explicitly set
can you try with this patch applied ?
Success.
awesome :-) I will cook up
On Thu, 2012-05-24 at 13:43 +0200, John Crispin wrote:
On 24/05/12 13:41, Conor O'Gorman wrote:
That patch didn't work. The -i is necessary. It's also a critical param,
as the first setting seems to stick till reboot. Which is annoying, as
all subsequent tests are pointless.
Anyway,
On Thu, 2012-05-24 at 13:45 +0100, Conor O'Gorman wrote:
The default a2p (adsl2+) is perhaps too strict? The 'a' option
includes all 'a' variations:
annex_a=04_01_04_00_00_01_00_00
annex_at1=01_00_00_00_00_00_00_00
annex_alite=00_01_00_00_00_00_00_00
annex_admt=04_00_00_00_00_00_00_00
Hello??I successfully get ipv6 address using 6to4 method following openwrt
wiki. http://wiki.openwrt.org/doc/howto/ipv6
By the way,I've never heard of cerowrt.What's the major different towards
openwrt?
-- Original --
From: Rich
On Thursday, May 24, 2012 16:20:47 ZioPRoTo (Saverio Proto) wrote:
Marek may I ask if the matter is just this bug with the start/stop
scripts not working correctly at boot, or if there are more issues in
using the batman-adv package with the backfire branch ?
The problem arises only if you
This adds a new boolean option, fqdn, to the config dnsmasq section of
/etc/config/dhcp. The default is off. When set on, it enables the dhcp-fqdn
option to dnsmasq. dhcp-fqdn causes dnsmasq's DNS server to not resolve
unqualifed local hostnames. The domain option is required when using fqdn.
When dnsmasq is configured with a domain option in the config dnsmasq
section of /etc/config/dhcp, it causes a search line to be added to
/etc/resolv.conf naming the domain specified. For situations where this is
undesirable, this can now be bypassed with the search_domain boolean option.
The
Since r31182, dnsmasq is configured by a configuration file at
/var/etc/dnsmasq.conf generated by dnsmasq's start script from its UCI
configuration. It is no longer configured by command-line arguments. dnsmasq
is started by telling it (via the -C option) to use /var/etc/dnsmasq.conf as
its
Hi,
We wanted to let the OpenWrt community know that version 2.2.0 of the CyaSSL
embedded SSL library has been released and is now available for download from
the yaSSL website. CyaSSL currently supports the OpenWrt project. This
release contains bug fixes and feature enhancements, some of
Very well, I'll drop this. I missed the conf-file=/etc/dnsmasq.conf at
the top of /var/etc/dnsmasq.conf.
I'm still proposing the other four dnsmasq patches I sent to the list
in a series earlier today.
___
openwrt-devel mailing list
The attached patch bumps iptables up to 1.4.13 and adds in support for -m
rpfilter (reverse path filtering for both IPv4 and IPv6) implemented since
kernel 3.3
This update breaks compatibility with the 2.4 series, if anyone wishes to
fix it, feel free.
Tested and working on my WNDR3800 - if
The following patch enables ECDSA support in OpenSSL in order to allow
OpenSSH to also make use of it as it is now the primary (preferred) mode of
authentication for OpenSSH
Signed-off-by: Oliver Smith oli...@8.c.9.b.0.7.4.0.1.0.0.2.ip6.arpaIndex: package/openssl/Makefile
The following patch enables generation of ecdsa keys in OpenSSH at init.
Signed-off-by: Oliver Smith oli...@8.c.9.b.0.7.4.0.1.0.0.2.ip6.arpaIndex: feeds/packages/net/openssh/files/sshd.init
===
---
Hello.
Could you please say the feeds that you use in the trunk build. I mean
the feeds located in /trunk/feeds.conf.default?
I already tryed to build, but i'm not getting it right...
Or it gives me error in the build, or i can make the build, but don't
work the batman-adv...
Thank's!!
Shadow passwords were enabled by default in r28936, but most of the benefit
was not realized because the shadow file was allowed to be world-readable.
This change sets /etc/shadow's mode to 0600 in the base-files package, and
ensures that its permissions are not clobbered when building an image.
On the off chance that the root filesystem's /tmp is used directly as a
temporary directory instead of having a tmpfs mounted over it, it should have
the sticky bit set.
Signed-off-by: Mark Mentovai m...@moxienet.com
---
Index: include/image.mk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
first, dont worry its *not* about asking how to unbrick ;) This is
well documented in the wiki and working fine with serial and tftp..
I rather want to understand, what went wrong (or if it's maybe a
problem that others might run into and avoid
Everything is there http://eigenlab.org/~gioacchino/openwrt/
you will find feed.conf and .config inside the meta folder
On 05/24/12 22:41, Pedro Nuno Costa Rodrigues wrote:
Hello.
Could you please say the feeds that you use in the trunk build. I mean
the feeds located in
Changes in this patch:
* bumps to version 2012.04.01
* adds md5sum
* creates a menu so it will look better in make menuconfig
* adds /etc/fw_env.config to conffile
* adds /etc/config/ubootenv to conffile
* refresh patches
* removes init script because we should be using uci-defaults
Petr Štetiar wrote:
is anyone using nfsroot on ramips/rt305x platform? I couldn't get it working
without this patch[1]. So my questions are, is nfsroot working for someone on
this platform? If not, is it this patch ok (or it's a total nonsense)? Is
there a better solution? Thanks for any
On Fri, 2012-05-25 at 00:08 +0200, Michael Markstaller wrote:
[0.00] Kernel command line: board=TL-WR1043ND console=ttyS0,115200
rootfstype=squashfs,jffs2 noinitrd
[0.10] MIPS: machine is Generic AR71XX/AR724X/AR913X based board
It appears that the kernel cannot correctly
26 matches
Mail list logo