Hi,
fixed with http://luci.subsignal.org/trac/changeset/10286 - thanks for
your heads-up.
~ Jow
signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
Hi,
the data is cached upon the first call.
To force a resync, run network_flush_cache.
~ Jow
signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
Hi,
the string Saving config files is not occuring anywhere in the LuCI
source code. Seems it is emitted by a program that gets invoked when
configs get committed through libuci. Did you modify libuci or
luci.model.uci ?
~ Jow
signature.asc
Description: OpenPGP digital signature
Whats the result if you run
grep -r Saving config files /
?
signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Hi,
git send-email support is provided by a separate package on .deb distros:
apt-get install git-email
~ Jow
signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
Hi,
this chipset cannot support more than 7 clients in AP mode. Its a
limitation of the chip firmware.
~ Jow
signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
Hey Gui,
I think we can extract a few bits of entropy by using the MAC addresses,
should be easy to obtain them through getifaddrs().
~ Jow
signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
Thats due to the varnish cache, it strips all incoming cookies for
non-authenticated users.
~ Jow
signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
Hi.
Yes, I heard from other replies, that's good news, hope it will be
ready for prime time soon.
Still, it would be nice to have good unbloated language for rapid app
development in constrained environments, like most routers on which
OpenWRT runs. I made initial proof of concept web
Hi.
Profiles influence image generation and package selection but share all
a common kernel.
Subtargets are used if a different kernel is required.
~ Jow
signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
Hi,
can you extend the patch to update the corresponding strings in the *.po
files as well?
~ Jow
signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
Hi Russel,
I introduced that breakage yesterday and it applies to Kernel 3.13 as
well... I fixed my changed and pushed them, your patch was not
applicable because it modified the wrong patch file, the erroneous call
was introduced by 604-netfilter_conntrack_flush.patch
~ Jow
Hi Henning,
committed in r42139 and merged to BB in r42140 - thank you!
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Committed in r42151 - thank you!
~ jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Hi Liu Bo,
was there any particular reason why you couldn't use multiple -e
arguments? That should produce the very same results without using ;
jsonfilter -s '{a:b,e:{a:c}}' -e t=$['a'] -e y=$['e']['a']
export t='b'; export y='c';
~ Jow
___
Hi.
Try adding
option delay_root 10
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Hi,
yes there is a reason, the initial uci implementation was shell based
and section names are part of generated variable names which must not
contain dashes.
Simply replacing dashes with underscores is not possible either as this
would lead to ambiguous results.
~ Jow
So, it shouldn't be necessary with the C implementation?
Correct, but that cannot be changed without breaking support for legacy
APIs.
Simply replacing dashes with underscores is not possible either as this
would lead to ambiguous results.
Yes, I've got exactly this problem: the name of
Hi.
Dropbear should support sha2-based message authentication.
This patch will enable hmac-sha2-256 and hmac-sha2-512.
Whats the size increase due to that?
~ Jow
--- a/options.h
+++ b/options.h
@@ -128,8 +128,8 @@ much traffic. */
* which are not the
Hi.
The wan port is likely a dedicated, non-switch interface (e.g. eth1) on
this model. If you want to declare VLANs on it then simply create a new
interface using eth1.Y as manual physical ifname where Y denotes the
desired VLAN id.
~ Jow
___
Hi Gui,
this is not supposed to happen though - you can see the magic in
include/kernel-defaults.mk - define Kernel/Configure/Default
The hash is calculated like that:
grep '=[ym]' .../.config | sort | md5sum
Can you diff the Kernel build_dir/target-*/linux-*/linux-*/.config file
before and
Hi Michel,
On 02.10.2014 15:24, Michel Stam wrote:
During boot, a not found message is displayed for systems which do
not have uci 'network.globals.ula_prefix' defined in
/etc/config/network. The error message itself is not used and can
be ignored.
Signed-off-by: Michel Stam
Whats the meaning of this option?
The description text is awful and since I do not know what it is
supposed to do I cannot write a proper one.
Also a signed-off-by would be good.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
Hi,
thanks for the patch. however the description still looks grammatically
wrong: On which interface up should start the ddns script process.
Maybe it can be better written as Trigger DDNS update when this
interface is started
Ideas?
~ Jow
___
Hi Michel, John.
-for dev in $(ls /sys/class/ieee80211); do
+for dev in $(ls /sys/class/ieee80211 2/dev/null); do
what error do you see ? if you see an error we should try to fix that
rather than supressing it
I suppose the case when wifi detect is invoked but no phy exists on
the
Applied in r42757 - thanks!
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Applied in
http://nbd.name/gitweb.cgi?p=luci.git;a=commitdiff;h=08df45ab3592e5084eab77127b84be3add358500
- thanks!
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Hi Paul,
the trick is to add the OpenWrt source as package feed, this way you
gain access to libffi and any other core packages:
$ wget
https://downloads.openwrt.org/barrier_breaker/14.07/ar71xx/generic/OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2.tar.bz2
[...]
$ tar -xjf
Hi.
In principle I have no objections but we need to figure out a way on how
to deal with translation files. If stuff is split out of the LuCI repo
you have to take of that yourself.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
-by: Michel Stam m.s...@fugro.nl
Acked-by: Jo-Philipp Wich j...@openwrt.org
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Hi.
it does not work. this is my interface: [...]
Actually it should work just fine even without option netmask if you
specify the start as ipaddr:
# ipcalc.sh 192.168.0.1 16 192.168.8.1 252
IP=192.168.0.1
NETMASK=255.255.0.0
BROADCAST=192.168.255.255
NETWORK=192.168.0.0
PREFIX=16
Hi Christian,
should be fixed with 43017 - thanks for reporting.
Btw, there's two little problems with the prerm postinst defines in
the ddns-scripts Makefile:
First you should not indent the script code, otherwise the final script
file will have leading spaces on each line.
Second you must
Hi.
postinst and prerm are copied shell scripts
and executed on the box and not by make
thats the reason for #!/bin/sh required on the first line
so $$ not needed. right ?
Nope, not right - it is needed. Make is interpreting the stuff between
define .. endef - you need to escape $ in any
Try make package/iwinfo/{clean,compile}
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Hey,
11ng/11na is confusing for me, there is no something
like 11ng/11na outside OpenWrt world (or I'm not aware of :)), there is
11n on 5 ghz band and 11n on 2.4 ghz band so in my opinion band
selection is reasonable and means much more for end user.
Imo this notation is inconsistent within
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Honestly I don't care how it is done so far, I think it should be done
as best as possible and this is my concern.
We do care how its done so far - and mapping 11ng / 11na seems way
simpler to me than introducing an explicit band selection.
It
Applied in r30833 - thanks!
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This random related message is perfectly normal.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk9ZGLgACgkQdputYINPTPN9fgCgoBK7OFEJLwBfxpMpxxKXG8Fz
Hi,
new languages must be enabled by an administrator in the wiki.
I added japanese now, it should get offered as choice in the sidebar as
soon as you login.
HTH,
Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I now looked over the patch and have a couple of comments.
First of all, I added GPT support to the trunk kernel config a few days
ago, so it should be always there by now.
I don't like conditional compilation of kernel features triggered by a
* I could not find a working copy of pangocairo. Check config.log for
hints on why
As usual, dig through config.log
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
You need
include $(INCLUDE_DIR)/nls.mk
in your OpenWrt makefile. That will add the needed iconv search paths to
TARGET_CFLAGS.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
Yes, you need to patch out intltool related stuff.
Usually its enough to remove the po from SUBDIRS in the Makefile.am
and then declaring PKG_FIXUP:=autoreconf in the OpenWrt Makefile.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
-R is a linker option but unknown to gcc. Either (if you can) change
-R/usr/lib to -Wl,-rpath=/usr/lib or make sure that LD points to the
cross ld and not the cross gcc.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
While the existing perl code isn't the best either, yours is extremely
inefficient, you should rework it using native functions.
+ system(find $cache -follow -name $filename 2/dev/null 1
temp.dls);
perldoc -f open
+ my $lines = `cat temp.dls | wc -l`;
perldoc -f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, you can optimize out the temporary dl file.
diff -Naur a/scripts/download.pl b/scripts/download.pl
--- a/scripts/download.pl 2012-04-04 13:19:27.0 +0530
+++ b/scripts/download.pl 2012-04-04 13:20:34.0 +0530
@@ -9,6
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Philipp,
in principle I aggree but I've seen Perl distributions without
Digest::MD5 available by default, so shelling out to call md5sum
sounds ok to me.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It got line wrapped.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk9+DYgACgkQdputYINPTPPmbgCePy75NtkXFACVcCe01xA4Go7G
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
this one is fine...
Now we still have to wait fore gabor to review it :)
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
1. Following deny by default principle, change the default section
policy to DROP. The firewall package already add rules to allow all
lo traffic, there should be no impact to user.
NACK. If at all it should be reject, not drop - to at least
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://wiki.openwrt.org/doc/howto/generic.failsafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+Cy+EACgkQdputYINPTPMQkwCfXuYbhT1uSzxZ8rKTdip2NoG/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
thank your for your contribution.
There are a few issues, comments inline.
On 10.04.2012 21:56, Jiri Slachta wrote:
Signed-off-by: Jiri Slachta j...@slachta.eu
Index: feeds/packages/net/kamailio3/files/kamailio.init
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Applied in r31270, thanks.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+HbmsACgkQdputYINPTPMR2ACgkx7DPQ1Fl2z7NjyOCyc3Vm6G
--git a/net/mosquitto/Makefile b/net/mosquitto/Makefile
index 4ed8bc4..551f286 100644
--- a/net/mosquitto/Makefile
+++ b/net/mosquitto/Makefile
@@ -1,5 +1,5 @@
#
-# Copyright (C) 2011 OpenWrt.org
+# Copyright (C) 2011,2012 OpenWrt.org
# Copyright (C) 2010 Jo-Philipp Wich x...@subsignal.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Compiling anything is for developers. Whatever helps is a Good Thing;
nobody expects the holy grail.
Adding a version symbol the way it was proposed in the patch does not
help, it increases our maintenance burden and implies that changing the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
That sounds fine with me. The various guis will redirect / anyway.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
thanks - applied in r31374.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+Rg7oACgkQdputYINPTPOVWgCfSWxkBOqoh5vpYm/b9NSe4PZe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
No objections from anyone so added in r31375, thanks Michael.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
thanks for the udated patch, applied in r31376.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I committed a modified version of this patch in r31377 - thanks!
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
comments inline.
Index: utils/nut/patches/001-fix-missing-libmath-flags.patch
===
- --- utils/nut/patches/001-fix-missing-libmath-flags.patch(revision 0)
+++
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yes, its a known issue.
See https://dev.openwrt.org/ticket/11341 and
http://freetz.org/browser/trunk/make/libs/uclibcxx/patches/050-gcc47x-proper-two-phase-lookup.uclibcxx.patch
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi David,
I applied your patch series in r31569 - r31571, thank your for your
contribution.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So, finally please understand also, that there is a 99,48%-world
besides v6 which has to work as it is.
Finally, please understand that your IPv6 discussion in this thread is
pointless, off topic and and unproductive. It draws attention away from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
after reading the patche multiple times I still don't get the purpose.
Shouldn't $link already contain the last value when leaving the inner
while() loop? Why do you need yet another variable which is just a copy
of the existing one?
~ Jow
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am I missing something? I would think this useful, as it may have
been plugged into a different network.
Yes. This might work for units that have their wan at a dedicated
interface, but it will fail through bridges or switches which are
always up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
the errors you're experiencing are not your fault.
The appweb Makefile overrides the default Build/Prepare action which
prevents the Quilt make targets from getting executed.
This change will enable quilt patching as documented in the wiki:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK, this is rubbish because /etc/init.d/network doesn't run during in
failsafe?
No because the overlay is not mounted in failsafe, thats quite normal
and also seen on e.g. brcm47xx or ar71xx.
Tried mount_root when in failsafe?
~ Jow
-BEGIN
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
whats the current status of bcm63xx adsl modems (e.g. inside
d-link dsl-2741)?
Unchanged and unlikely to change in the future.
Anything news or success?
No news, no sucess.
~ Jow
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The failing part of the build:
Fixed with 8b9f1724276bf30408ffc0ddb695b179c4c4a200 / r32128
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hell Daniel,
I committed a modified and cleaned up variant of your patch to trunk in
https://dev.openwrt.org/changeset/32197 and removed the old pptp package
in https://dev.openwrt.org/changeset/32198.
~ Jow
-BEGIN PGP SIGNATURE-
Version:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
Shouldn't you also add CONFIG_ZLIB_DEFLATE to KCONFIG then?
~ Jow
- -BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Shouldn't you also add CONFIG_ZLIB_DEFLATE to KCONFIG then?
I meant CONFIG_ZLIB_INFLATE of course.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
patch applied in r32431 and further simplifications added in r32432.
Thank you!
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
On a small system with only 4MByte Flash dudders with openssl as dependency
is huge - libgcrypt is
sufficient.
Shouldn't you also add a configure switch which explicitly disables
openssl? Merely relying on it not being there will not work if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
$ GET http://patchwork.openwrt.org/patch/2155/mbox/ | git am
Applying: Update BIRD to version 1.3.7
error: patch failed: net/bird/Makefile:1
error: net/bird/Makefile: patch does not apply
Patch failed at 0001 Update BIRD to version 1.3.7
~ Jow
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
$ GET http://patchwork.openwrt.org/patch/2102/mbox/ | git am -p2
Applying: libssh2
error: patch failed: libs/libssh2/Makefile:8
error: libs/libssh2/Makefile: patch does not apply
Patch failed at 0001 libssh2
~ Jow
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ultimately, it may just be a bad idea to have a bridge's MAC address
change once established, at least as long as the bridge still contains an
underlying interface that owns the MAC address it's using.
That is nothing netifd or OpenWrt does, it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
what am I missing?
The fact that those units have no nvram.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
[snip]
+ while (dev) {
+ struct switch_dev *next = dev-next;
+ print_dev_summary(dev);
+ swlib_free(dev);
+ dev = dev-next;
This looks like a user-after-free.
Given that you allocate a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I copied commented your patch inline below.
- --- /dev/null 2012-07-05 10:42:19.287097043 +0200
+++ package/libsocketcan/Makefile 2012-07-05 18:35:26.763462631 +0200
@@ -0,0 +1,62 @@
+#
+# Copyright (C) 2006-2012 OpenWrt.org
That should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The LuCI patch will not properly work that way, OpenWrt Lua does not
handle numeric integer values 2^31 bit. A somewhat larger range can be
stored as float but the precision is not enough:
# lua -e 'print(string.format(%d,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
i commented the bit which sometimes fills the syslog with:
DHCP packet received on eth0.2 which has no address like it does
on my tp-link wr1043nd..
uci set dhcp.@dnsmasq[0].notinterface=eth0.2
uci commit dhcp
/etc/init.d/dnsmasq restart
~
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
Should I create patches for machtype.h and Kconfig, or should I
create a patch for 610-MIPS-openwrt-machines.patch?
Yes.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oops, I missed the or :)
I meant yes, you should amend 610-MIPS-openwrt-machines.patch .
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Use variant (a), a patch-patch. Don't worry, we're used to look at and
work with such things.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Applied in r33072 - thank you.
Next time please ensure that your patch applies with -p1, not -p0.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed in r33141 - thanks.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlAnpdgACgkQdputYINPTPOmcQCfZiObf1C4YfD/9n3ZLqVXsBF8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed in r33146 - thanks.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlAnploACgkQdputYINPTPOjcQCgl/kVVZ9jXXnOKpkg/TCbXnR0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Nguyễn Hồng Quân,
each request will make uhttpd fork off a new process with an isolated
process space. Every memory you modify within there will get discarded
once the process serving the request ends.
However you can use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Commited in r33186 - thanks.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlAqWZIACgkQdputYINPTPOI2wCfTvRN3sz+iIpE8ANyRZaNXzM4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed with minor whitespace changes in r33199 - thanks.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There isn't.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlAzUfcACgkQdputYINPTPNcQwCglRhv+KtZlZWtINUrsnRdGezX
YEIAnjoyOEq5jPaXy6S6vKBDGC/YiDd0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It looks like conffiles can only save files, not entire directories.
/etc/nginx is a directory. Should conffiles be fixed to work with
directories too?
It works fine with directories, see include/package-ipkg.mk, the code
below ifneq
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I see. The existing feeds/packages/net/nginx/Makefile already lists
the files under /etc/nginx that ship in the package in its
conffiles definition, but this doesn't result in a keep file in the
package because include/package-ipkg.mk will only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
this package is broken since a long time, simply deselect it.
It needs extensive changes to work with newer kernels / iptables.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Although with that we would be stuck at a certain kernel version.
Which is an absolute no-go for OpenWrt.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
The wireless does not works (no OpenWrt SSID show, the wireless LED
blinks).
Erm, it is normal that no SSID shows in station mode. You're client to
another network and you're supposed to set the SSID and crypto
settings to those of the target
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://wiki.openwrt.org/doc/recipes/routedap
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iEYEARECAAYFAlBgLcMACgkQdputYINPTPN+0QCeOerFEFz6RhsD9W7iw8G7vBIA
1 - 100 of 1241 matches
Mail list logo
