Re: OpenWrt 19.07.6 service release
On 23/01/21 3:13 am, Philip Prindeville wrote: > You'll need to remove the dnsmasq package and select > CONFIG_PACKAGE_isc-dhcp-server-ipv4 (or -ipv6 which actually supports both > IPv4 and IPv6, but the UCI scripting for dynDNS for IPv6 as I said is > missing). That will bring in Bind and the related tools. Thanks for the detailed how-to. I would like to understand how to populate ipsets dynamically using bind, the way dnsmasq does with simple config like: list ipset '/domain.one/ipset1,ipset2' list ipset '/domain.two/ipset3,ipset1' If I can get it working with bind, I will be able to move to ISC DHCPD and BIND. Thanks in advance. Regards, Nishant ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Dissociate STA based on SNR
Hi, I was wondering if there is a way to dissociate STAs who say go below a minimum threshold SNR or signal level of say -65dBm in a multi-AP scenario? As we do not run our OpenWRT APs with a WLAN controller, which can automatically change channels or increase/decrease the txpower, would it be a good idea to kick a STA off if it has low signal, so that it can be forced to associate with another AP. Reason being, I have observed that there are a variety of STA cards which have their own algorithms built-in to consider the signal good enough or poor enough to try and find another AP with same SSID, which is beyond our control. Thus, STA hangs on to a poor SNR of say 17 but wouldn't switch to a better AP available affecting the user experience. As soon as I restart wifi on the AP, it goes to associate with another AP with better SNR. I do not have a lot of experience with WiFi, but yes, I do have installed around 25 OpenWRT ath9k based APs in offices and warehouses and this is what I have observed and am writing in to seek ideas and suggestions from more experienced people. Thanks in advance. Regards, Nishant ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Dissociate STA based on SNR
Hi Bastian,
On Monday 18 January 2016 08:16 PM, Bastian Bittorf wrote:
ubus call hostapd.$dev del_client '{ "addr" : "$mac", "reason" :
"assoc toomany", "ban_time" : 1 }'
Thanks for the pointers. It works for me.
What exactly is ban_time unit? I presume it's millisecond.
Where can I find more documentation about ubus call to different
processes? The page https://wiki.openwrt.org/doc/techref/ubus doesn't
mention the call that you have used :)
Regards,
Nishant
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] /usr/bin/ip missing in 15.05.1
Hi, I compiled 15.05.1 for x86, x86_64 and ar71xx (mikrotik RB951Ui) and found that mwan3 didn't work because it was looking for /usr/bin/ip. I have compiled ip-full into the image. I had to symlink /usr/sbin/ip to /usr/bin/ip in order for mwan3 to work. OpenVPN-openssl worked as expected and as able to add routes to the system. Regards, Nishant ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] /usr/bin/ip missing in 15.05.1
Hi, On Friday 22 January 2016 05:44 PM, Felix Fietkau wrote: Looks like you may have used the mwan3 package from the master branch in your 15.05 build. You need to use the for-15.05 branch from the packages feed. - Felix My feeds.conf contains following lines: src-git packages https://github.com/openwrt/packages.git src-git luci https://github.com/openwrt/luci.git src-git routing https://github.com/openwrt-routing/packages.git src-git telephony https://github.com/openwrt/telephony.git src-git management https://github.com/openwrt-management/packages.git src-git targets https://github.com/openwrt/targets.git On GitHub, no matter what branch I choose, I always get the same clone URL: e.g. at https://github.com/openwrt/packages/tree/for-15.05 the clone URL I get is https://github.com/openwrt/packages.git and at https://github.com/openwrt/packages/tree/master the clone URL is https://github.com/openwrt/packages.git Am I missing something? Regards, Nishant ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] /usr/bin/ip missing in 15.05.1
Hi, On Friday 22 January 2016 05:44 PM, Felix Fietkau wrote: Looks like you may have used the mwan3 package from the master branch in your 15.05 build. You need to use the for-15.05 branch from the packages feed. - Felix My feeds.conf contains following lines: src-git packages https://github.com/openwrt/packages.git src-git luci https://github.com/openwrt/luci.git src-git routing https://github.com/openwrt-routing/packages.git src-git telephony https://github.com/openwrt/telephony.git src-git management https://github.com/openwrt-management/packages.git src-git targets https://github.com/openwrt/targets.git On GitHub, no matter what branch I choose, I always get the same clone URL: e.g. at https://github.com/openwrt/packages/tree/for-15.05 the clone URL I get is https://github.com/openwrt/packages.git and at https://github.com/openwrt/packages/tree/master the clone URL is https://github.com/openwrt/packages.git Am I missing something? Regards, Nishant ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] /usr/bin/ip missing in 15.05.1
On Friday 22 January 2016 08:56 PM, Felix Fietkau wrote: Here's what feeds.conf.default in the 15.05 branch contains: src-git packages https://github.com/openwrt/packages.git;for-15.05 src-git luci https://github.com/openwrt/luci.git;for-15.05 src-git routing https://github.com/openwrt-routing/packages.git;for-15.05 src-git telephony https://github.com/openwrt/telephony.git;for-15.05 src-git management https://github.com/openwrt-management/packages.git;for-15.05 Thanks a lot Felix and Lars. It seems I was compiling bleeding edge packages all this while and was wondering why a lot of them didn't compile successfully on 15.05.1 while they did on 15.05. /me goes to re-build the images and packages. Regards, Nishant ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Firmware Upgrade - Mikrotik - ar71xx
Hi, I have around 50 boxes (ar71xx Mikrotik RB951Ui-2HnD) in the field, running AA or BB (custom compiled). I have checked through the documentation, but could not find any way to upgrade the firmware. Is there a way, that I could upgrade them to the newly compiled firmware remotely or only option I have is to recall the boxes back and re-flash them? Thanks in advance. Regards, Nishant ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Firmware Upgrade - Mikrotik - ar71xx
Hi Davey, Thanks for your response. I was away due to festive season so couldn't reply earlier. On Tuesday 20 October 2015 09:43 PM, David Hutchison wrote: I think sysupgrade now works with the rb951ui; however I haven't tested it. I wrote my own upgrade process before sysupgrade was available for the rb95x series: I of course scripted it. * HOWEVER IF SYSUPGRADE IS CONFIRMED WORKING WITH THE RB951Ui, USE THAT !!!* My way is not very well vetted; while I use I have a *very* custom rb951ui OpenWRT build. I can't emphasis that enough, test sysupgrade *FIRST!* Since my boxes are running AA or BB, so sysupgrade support in CC doesn't matter in this case. Thanks a lot for mentioning the steps which will help me create a script and test it on a local box. I will also give sysupgrade a try first. Mikrotik is hard to brick as I can always boot it with tftp :-) I will keep the list posted with my mileage. Thanks again. Regards, Nishant ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Need to check version of LUCI
Hi, You may clear your browser cookies and cache. Do rm -rf /tmp/luci* and then try. Regards, Nishant On 27 October 2015 09:26:15 GMT+05:30, nam228 wrote: >Hi all, > >I am using OpenWRT trunk version 47213 > svn://svn.openwrt.org/openwrt/trunk > >I installed luci by these commands: > trunk/script/feed update -a > trunk/script/feed install luci > >My question is: can i check version of luci ? or how can i downgrade it >. > >In my case , the luci web-page is not working well. >For example: when I edit the Network/Wifi it automatically log out to >the login page > >Thanks, >Nam. >___ >openwrt-devel mailing list >openwrt-devel@lists.openwrt.org >https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Plans for CC 15.05.1 or DD 16.xx release?
Hi, On Monday 11 January 2016 05:42 PM, John Crispin wrote: days. with a bit of luck 15.05.1 is ready early next week. How do I bump my local git cloned source to 15.05.1? A simple git pull in the source directory should be able to achieve that? Regards, Nishant ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] procd: service instance restart does not wait for old process to be closed before lanching the new one
On 8 February 2017 8:25:29 PM IST, "Alin Năstac" < >And isn't a bit too optimistic to assume all daemons will be stopped by >SIGTERM? Case in point a squid running on PCEngines APU. Even if I configure it to force close connections within 2-3 seconds, it still at times takes more time. Regards, Nishant -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Espressobin mvebu64
Hi, First of all, congratulations on re-merge of OpenWrt and LEDE. Now to the problem being faced. I am trying to build OpenWrt for Espressobin (http://espressobin.net) as described in their wiki at http://wiki.espressobin.net/tiki-index.php?page=Build+From+Source+-+OpenWrt It built fine with default options without installing any additional packages or enabling other software/kernel modules. On installing additional packages, it started to fail. So I did the following: ./script/feeds -a uninstall rm .config* make menuconfig -> select target make defconfig make -j1 V=s But still it fails while building the kernel. Below are the logs: = make -C /home/devuser/espressobin/openwrt-dd/build_dir/target-aarch64_cortex-a53+neon-vfpv4_musl-1.1.16/linux-mvebu64/linux-4.4.8 HOSTCFLAGS="-O2 -I/home/devuser/espressobin/openwrt-dd/staging_dir/host/include -I/home/devuser/espressobin/openwrt-dd/staging_dir/host/usr/include -Wall -Wmissing-prototypes -Wstrict-prototypes" CROSS_COMPILE="aarch64-openwrt-linux-musl-" ARCH="arm64" KBUILD_HAVE_NLS=no KBUILD_BUILD_USER="" KBUILD_BUILD_HOST="" CONFIG_SHELL="bash" V='' CC="aarch64-openwrt-linux-musl-gcc" modules make[5]: Entering directory '/home/devuser/espressobin/openwrt-kernel' CHK include/config/kernel.release CHK include/generated/uapi/linux/version.h CHK include/generated/utsrelease.h CHK include/generated/bounds.h CHK include/generated/timeconst.h CHK include/generated/asm-offsets.h CALLscripts/checksyscalls.sh usr/Makefile:64: *** multiple target patterns. Stop. Makefile:949: recipe for target 'usr' failed make[5]: *** [usr] Error 2 make[5]: Leaving directory '/home/devuser/espressobin/openwrt-kernel' Makefile:23: recipe for target '/home/devuser/espressobin/openwrt-dd/build_dir/target-aarch64_cortex-a53+neon-vfpv4_musl-1.1.16/linux-mvebu64/linux-4.4.8/.modules' failed make[4]: *** [/home/devuser/espressobin/openwrt-dd/build_dir/target-aarch64_cortex-a53+neon-vfpv4_musl-1.1.16/linux-mvebu64/linux-4.4.8/.modules] Error 2 make[4]: Leaving directory '/home/devuser/espressobin/openwrt-dd/target/linux/mvebu64' Makefile:13: recipe for target 'compile' failed make[3]: *** [compile] Error 2 make[3]: Leaving directory '/home/devuser/espressobin/openwrt-dd/target/linux' target/Makefile:21: recipe for target 'target/linux/compile' failed make[2]: *** [target/linux/compile] Error 2 make[2]: Leaving directory '/home/devuser/espressobin/openwrt-dd' target/Makefile:16: recipe for target '/home/devuser/espressobin/openwrt-dd/staging_dir/target-aarch64_cortex-a53+neon-vfpv4_musl-1.1.16/stamp/.target_compile' failed make[1]: *** [/home/devuser/espressobin/openwrt-dd/staging_dir/target-aarch64_cortex-a53+neon-vfpv4_musl-1.1.16/stamp/.target_compile] Error 2 make[1]: Leaving directory '/home/devuser/espressobin/openwrt-dd' /home/devuser/espressobin/openwrt-dd/include/toplevel.mk:192: recipe for target 'world' failed make: *** [world] Error 2 Any pointers on where it is going wrong would be really helpful. Thanks in advance. Regards, Nishant ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Fwd: GRUB / GRUB2 on current trunk?
Hi all, Posting on Devel list as it seems more like a devel query now. Regards, Nishant Original Message From: Nishant Sharma Sent: 3 September 2014 20:18:49 GMT+05:30 To: openwrt-us...@lists.openwrt.org Subject: GRUB / GRUB2 on current trunk? Hi, This is my first message to the list. Is there a way that I could compile old GRUB on SVN r42320 or install GRUB2 somehow on the target disk after copying the rootfs? The hardware is PCEngines APU with SSD. I am compiling it for x86_64 and there is no way that I can use grub-install command by chrooting into the new rootfs flashed on the target drive, as the GRUB2 utils are not available in the rootfs. The ext4 filesystem image generated by 'make' doesn't survive changes on a reboot. Which forces me to first copy rootfs to the target disk and then install the boot loader on it. The good old GRUB used to be so easy for x86. Any pointers would be of a great help. Thanks in advance. Regards, Nishant -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Barrier Breaker timeline?
On 8 September 2014 20:07:26 GMT+05:30, John Crispin wrote: > >On 08/09/2014 16:29, Nishant Sharma wrote: >> >> Hi John, >>> the test build is done and we fixed the 2 problems that came up. SDK >>> now >>> works properly. all the packages from all feeds build (apart from >>> old.packages which has a fallout of ~15 packages) currently we are >>> waiting on a ath9k regression fix that is being tested just now. >once >>> that is in the release branch i will restart the builders and >generate >>> BB-final. >> >> Great news. Shall we expect the x86 images created to retain changes >on reboot on BB-final? > >they don't do so now ? The last I tried on rc3 and trunk, they didn't. Hence a separate post too on the list. Wiki said the same. Will try again tomorrow and post the findings. Regards, Nishant -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Barrier Breaker timeline?
Hi, It is here on the wiki already posted by someone http://wiki.openwrt.org/toh/pcengines/apu Regards, Nishant On 8 September 2014 20:13:34 GMT+05:30, John Crispin wrote: >is this reported or documented anywhere ? > > > >On 08/09/2014 16:40, Nishant Sharma wrote: >> >> On 8 September 2014 20:07:26 GMT+05:30, John Crispin > wrote: >>> On 08/09/2014 16:29, Nishant Sharma wrote: >>>> Hi John, >>>>> the test build is done and we fixed the 2 problems that came up. >SDK >>>>> now >>>>> works properly. all the packages from all feeds build (apart from >>>>> old.packages which has a fallout of ~15 packages) currently we are >>>>> waiting on a ath9k regression fix that is being tested just now. >>> once >>>>> that is in the release branch i will restart the builders and >>> generate >>>>> BB-final. >>>> Great news. Shall we expect the x86 images created to retain >changes >>> on reboot on BB-final? >>> >>> they don't do so now ? >> The last I tried on rc3 and trunk, they didn't. Hence a separate post >too on the list. >> >> Wiki said the same. Will try again tomorrow and post the findings. >> >> Regards, >> Nishant >> -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Barrier Breaker timeline?
Hi John, On Monday 08 September 2014 08:13 PM, John Crispin wrote: > is this reported or documented anywhere ? > Compiled the Barrier Breaker (SVN 42452) and changes are "kept" on the reboot. I raised a false alarm. Thanks & regards, Nishant ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] kernel changes on recompilation?
Hello members, Although, I am compiling and using custom OpenWRT images since 8 months now, but I am still confused with this particular behaviour. I am using it primarily on x86 Alix & APU devices. Everytime I run a make and kernel gets recompiled, it changes the hex value appended to the kernel package name which makes a lot of packages or new modules compiled uninstallable on existing systems through opkg. What is the best practice for doing these kind of things or is there any workaround? Thanks in advance. Regards, Nishant ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] kernel changes on recompilation?
On 2 October 2014 04:45:38 GMT+05:30, Gui Iribarren wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA1 > >On 01/10/14 14:31, Baptiste Jonglez wrote: >> When you activate/deactivate packages in menuconfig, it may modify >> what gets compiled into the kernel, to add/remove support for the >> various subsystems needed by the packages you build. This will >> cause the kernel to be rebuilt with a different package number. >> >> If you just rebuild the image without changing anything in >> menuconfig, I think the kernel package will not be rebuilt. Not >> sure though, just try and see for yourself :) > >Hm.. i can contribute a datapoint: if you make a "dirclean", without >changing anything in the makeconfig or anything else >(say, "make dirclean ; make ; make dirclean; make") >you'll end up with two different kernel-hashes (after step 2 and 4) >so there's (in addition to selected-kernel-features and such) some >kind of build-date being taken into account for calculating the hash, >which gets lost when doing dirclean, somewhere inside build_dir i >suppose. I never did a clean or dir clean but yes I enabled a few packages and modules with new requirements. Which is fine by my own thinking. And just for adding e.g. batman-adv to existing devices in the field, it becomes a pain to reflash them due to kernel hash change. Any more pointers please? Regards, Nishant > >cheers! > >gui > >> >> Baptiste >> >> On Wed, Oct 01, 2014 at 03:43:20PM +0530, Nishant Sharma wrote: >>> Hello members, >>> >>> Although, I am compiling and using custom OpenWRT images since 8 >>> months now, but I am still confused with this particular >>> behaviour. I am using it primarily on x86 Alix & APU devices. >>> >>> Everytime I run a make and kernel gets recompiled, it changes >>> the hex value appended to the kernel package name which makes a >>> lot of packages or new modules compiled uninstallable on >>> existing systems through opkg. >>> >>> What is the best practice for doing these kind of things or is >>> there any workaround? >>> >>> Thanks in advance. >>> >>> Regards, Nishant ___ >>> openwrt-devel mailing list openwrt-devel@lists.openwrt.org >>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel >>> >>> >>> ___ openwrt-devel >>> mailing list openwrt-devel@lists.openwrt.org >>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel >-BEGIN PGP SIGNATURE- >Version: GnuPG v1.4.12 (GNU/Linux) > >iQIcBAEBAgAGBQJULIsaAAoJEIJqNBvBfxrIX9wQAI987g9ibT2DYo2LoTdGKjrt >1w6m8AHT5xAKLJRlbOLZ0eDeArtryOh+s+rZzOdSAd/++Yh/8cjx3KlX6rI0tqQY >cTW49Ghbm23VZaPhIq86y3pJOYN1VdYhk/ZYR4hTHER1lJwiJYl/Ikrhb4X7mhFv >m2NXwye+aIAruXlTo4MJ5hGYxxV5XgeAtwgtuaZDW8MtkxBIiNceSziOyaoU6mC0 >DBuslTnwNqZbkGoqRuZlkzJRjTtqKtG1CbkDRk9jWJmAhXCfEve5zqkI0wB5dwIi >c1F7/+a4SKW8iEQLEDELPEFqW/8rSO5QJL7O+d98LqO/b7kJiYuRfsAeMAdITMGD >TX4WPHyE47LSP5DdVolEOkX9YBwRMVFEiC594/unsHx7186k3h/84I0ZYtCs6WBo >106AuOzxcktnLycPPvR4Gj2pUbY0cGMeTgD+Z5+1sBAFDgKMwqUmVGy5NxCFQ39I >Va1z0ihqVey1+Bh3YJ86mJ6L02kdaEvc7+vpbtdJnXSRQGSjSK8wmvNjzCkvslJO >d3aQa39urJAgZ/flfk+SPvU1ZTr1ohjsmzcCwMq2KZFdr7wcBcQE2YZ1b77UhUcl >jdDqGaSUFbjy504UpQaGscjMwZctwT8IWcbePnBsutlNue0a5A1kVnhQoSgPeFCi >hxPIp54tbwYZ41YvJyPb >=HY70 >-END PGP SIGNATURE- >___ >openwrt-devel mailing list >openwrt-devel@lists.openwrt.org >https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Barrier Breaker 14.07 Final
A big thank and many congratulations! Cheers, Nishant On 2 October 2014 18:29:08 GMT+05:30, Steven Barth wrote: >The OpenWrt developers are proud to announce the final release >of OpenWrt Barrier Breaker. > > ___ __ > | |.-.-.-.| | | |..| |_ > | - || _ | -__| || | | || _|| _| > |___|| __|_|__|__||||__| || > |__| W I R E L E S S F R E E D O M > - > BARRIER BREAKER (14.07) > - > * 1/2 oz Galliano Pour all ingredients into > * 4 oz cold Coffeean irish coffee mug filled > * 1 1/2 oz Dark Rum with crushed ice. Stir. > * 2 tsp. Creme de Cacao > - > >http://downloads.openwrt.org/barrier_breaker/14.07/ > >Important changes since RC3 >* various ath9k related fixes >* a few board related fixes >* fixes for packages depdending on curl >* per feed download folders > >Important changes since RC2 >* NAT & firewall throughput improvements >* Security updates for OpenSSL & PolarSSL >* Minor fixes in DHCP & DHCPv6 handling >* Configuration support for GRE tunnels >* Various other fixes > >Important changes since RC1 >* fix a long standing ath9k deadlock bug >* all feeds are now built >* image builder now works and RC2 contains all board specific images >* various board/stability fixes > >** Highlights since Attitude Adjustment ** >Default configuration and images > >* Linux kernel updated to version 3.10 >* Procd: new preinit, init, hotplug and event system written in C >* Native IPv6-support > - RA & DHCPv6+PD client and server > - Local prefix allocation & source-restricted routes > (multihoming) >* Filesystem improvements > - Added support for sysupgrade on NAND-flash > - Added support for filesystem snapshot and rollback > - Rewritten mounting system in C for rootfs and block devices >* UCI configuration improvements > - Support for testing configuration and rollback to working > last working state > - Unified change trigger system to restart services on-demand > - Added a data validation layer >* Networking improvements > - Netifd now handles setup and configuration reload of > wireless interfaces > - Added reworked event support to allow obsoleting network > hotplug-scripts > - Added support for dynamic firewall rules and zones > - Added support for transparent multicast to unicast > translation for bridges > - Various other fixes and improvements > >Additional highlights selectable in the package feeds or SDK >* Extended IPv6-support > - Added DS-Lite support and improved 6to4, 6in4 and 6rd-support > - Experimental support for Lightweight 4over6, MAP-E and MAP-T > - Draft-support for self-managing home networks (HNCP) >* rpcd: new JSONRPC over HTTP-frontend for remote access to ubus >* mdns: new lightweight mdns daemon (work in progress) >* Initial support for the musl C standard library >* Support for QMI-based 3g/4g modems >* Support for DNSSEC validation >* Added architecture for package signing and SHA256 hashing >* ... and many more cool things > >Package feed reorganization >For quite a while already we are not very satisfied with the quality >of the packages-feed. To address this, we decided to do a fresh start >on GitHub. The new feed https://github.com/openwrt/packages should be >used from now on and package maintainers are asked to move their >packages there. For the final release we will still build the old >packages feed but it will be necessary to enable it manually in the >opkg package list to be usable. >Additionally we would like to give a big thank you to all of our >package >maintainers working on our various feeds. > >New build servers >We would like to express our gratitude to Imagination Technology for >funding the 2 build servers that we used for the release. > >Whats next ? >We aim at releasing Chaos Calmer (CC) before the end of the year. The >CC release will use 3.14 or a newer LTS kernel as baseline. > > >Have fun! > The OpenWrt developer team >___ >openwrt-devel mailing list >openwrt-devel@lists.openwrt.org >https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] 14.07 SDK - iostream.h not found
Hi, This is my first time using the SDK to build a perl module (JSON-XS) which is not available in OpenWRT 14.07. I am using OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2 on a Debian Jessie x86_64 host. This module was successfully built if I use BuildRoot and create everything from scratch, so there is no problem with package Makefile. The compilation fails as db47 needs iostream.h and is not found in the SDK. (output of "make" is below) Any pointers on how to resolve this would be of great help. Thanks in advance. Regards, Nishant nishant at lyle :: make package/perlbase-json-xs/compile V=s # # configuration written to .config # make[1]: Entering directory '/data/openwrt/hopmesh/sdk/ar71xx/OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2' make[2]: Entering directory '/data/openwrt/hopmesh/sdk/ar71xx/OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2/feeds/packages/libs/libxml2' make[2]: Leaving directory '/data/openwrt/hopmesh/sdk/ar71xx/OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2/feeds/packages/libs/libxml2' make[2]: Entering directory '/data/openwrt/hopmesh/sdk/ar71xx/OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2/feeds/packages/libs/db47' make -C /data/openwrt/hopmesh/sdk/ar71xx/OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2/build_dir/target-mips_34kc_uClibc-0.9.33.2/db-4.7.25.NC/build_unix DESTDIR="/data/openwrt/hopmesh/sdk/ar71xx/OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2/build_dir/target-mips_34kc_uClibc-0.9.33.2/db-4.7.25.NC/ipkg-install" all make[3]: Entering directory '/data/openwrt/hopmesh/sdk/ar71xx/OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2/build_dir/target-mips_34kc_uClibc-0.9.33.2/db-4.7.25.NC/build_unix' /bin/sh ./libtool --mode=compile ccache_cxx -c -I. -I../dist/.. -I/data/openwrt/hopmesh/sdk/ar71xx/OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2/staging_dir/target-mips_34kc_uClibc-0.9.33.2/usr/include -I/data/openwrt/hopmesh/sdk/ar71xx/OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2/staging_dir/target-mips_34kc_uClibc-0.9.33.2/include -I/data/openwrt/hopmesh/sdk/ar71xx/OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2/usr/include -I/data/openwrt/hopmesh/sdk/ar71xx/OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2/include -D_GNU_SOURCE -D_REENTRANT -Os -pipe -mno-branch-likely -mips32r2 -mtune=34kc -fno-caller-saves -fhonour-copts -Wno-error=unused-but-set-variable -msoft-float -mips16 -minterlink-mips16 -fpic ../dist/../cxx/cxx_db.cpp ccache_cxx -c -I. -I../dist/.. -I/data/openwrt/hopmesh/sdk/ar71xx/OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2/staging_dir/target-mips_34kc_uClibc-0.9.33.2/usr/include -I/data/openwrt/hopmesh/sdk/ar71xx/OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2/staging_dir/target-mips_34kc_uClibc-0.9.33.2/include -I/data/openwrt/hopmesh/sdk/ar71xx/OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2/usr/include -I/data/openwrt/hopmesh/sdk/ar71xx/OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2/include -D_GNU_SOURCE -D_REENTRANT -Os -pipe -mno-branch-likely -mips32r2 -mtune=34kc -fno-caller-saves -fhonour-copts -Wno-error=unused-but-set-variable -msoft-float -mips16 -minterlink-mips16 -fpic ../dist/../cxx/cxx_db.cpp -fPIC -DPIC -o .libs/cxx_db.o In file included from ../dist/../cxx/cxx_db.cpp:13:0: ./db_cxx.h:59:22: fatal error: iostream.h: No such file or directory #include ^ compilation terminated. Makefile:1845: recipe for target 'cxx_db.lo' failed make[3]: *** [cxx_db.lo] Error 1 make[3]: Leaving directory '/data/openwrt/hopmesh/sdk/ar71xx/OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2/build_dir/target-mips_34kc_uClibc-0.9.33.2/db-4.7.25.NC/build_unix' Makefile:96: recipe for target '/data/openwrt/hopmesh/sdk/ar71xx/OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2/build_dir/target-mips_34kc_uClibc-0.9.33.2/db-4.7.25.NC/.built' failed make[2]: *** [/data/openwrt/hopmesh/sdk/ar71xx/OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2/build_dir/target-mips_34kc_uClibc-0.9.33.2/db-4.7.25.NC/.built] Error 2 make[2]: Leaving directory '/data/openwrt/hopmesh/sdk/ar71xx/OpenWrt-SDK-ar71xx-for-linux-x86_64-gcc-4.8-linaro_uClibc-0.9.33.2/feeds/packages/libs/db47' package/Makefile:173: recipe for target 'package/feeds/packages/db47/compile' failed make[1]: *** [package/feeds/packages/db47/compile] Error 2 make[1]: Leaving directory '/data/openwrt/hopmesh/sdk/ar71xx/OpenWrt-SDK-ar71xx-for-
Re: [OpenWrt-Devel] New OpenWrt logo proposal [Was: Re: [RFC]new "corporate identity" for OpenWrt & static rendering]
Hi Petr, On 14/01/20 4:57 PM, Petr Štetiar wrote: > Petr Štetiar [2020-01-08 22:47:28]: > > 1. > https://forum.openwrt.org/t/help-pre-select-new-openwrt-project-logo-in-the-poll/52674 All of them are nice and I have voted for the one I liked. I have a thought here. As far as I see and use, OpenWrt doesn't stand just for wireless freedom, though that's the most popular use case. It is being used as a base for various functions related but not limited to meshing, routing, network security, IoT and anything or everything that one can imagine or implement with additional packages. It gives us such a "freedom" and helps us protect our "privacy". The logo "H" represents the versatility, but misses the wireless. Regards, Nishant ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Enabling Wi-Fi on First boot
On 06/07/21 7:56 pm, Henrique de Moraes Holschuh wrote: > So, to safely and responsibly enable wireless by default in a device (or > firmware) you're delivering to a third-party, you need that "per-unit > unique wireless password" per device thing most vendors are doing. > > [2] not really: openwrt sysugrade *does not help* in that there is no > way to add variable information to an already *finished* image file, to > be used on first-boot only, and which would *survive a factory reset*. > How about a first-boot script that enables the Wi-Fi if it is disabled and then sets the password (if not already set) using the first MAC address it finds on the device? Regards, Nishant ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Mikrotik RB951Ui-2HnD: Wireless config missing on new hardware
Hello, [Unable to post on forum (error 502 bad gateway), hence posting here.] It seems something has changed in the hardware. I have "Type: INTL" devices here. I have already tried the following firmwares: 1. custom compiled 19.07.0 2. openwrt 19.07.0 3. custom compiled 18.06.2 4. custom compiled 17.02.4 I have tried these firmware on multiple (5+) old and new devices. On newer hardware, wifi config only touches the /etc/config/wireless and there is no configuration inside. Below is the output on older hardware with 17.02.4, which has wifi working: ``` root@HBCC2DE061D01A:~# iw dev wlan0 info Interface wlan0 ifindex 6 wdev 0x1 addr cc:2d:e0:61:d0:25 type managed wiphy 0 txpower 20.00 dBm root@HBCC2DE061D01A:~# dmesg | grep ath [ 22.885162] ath: EEPROM regdomain: 0x0 [ 22.885182] ath: EEPROM indicates default country code should be used [ 22.885191] ath: doing EEPROM country->regdmn map search [ 22.885212] ath: country maps to regdmn code: 0x3a [ 22.885224] ath: Country alpha2 being used: US [ 22.885233] ath: Regpair used: 0x3a root@HBCC2DE061D01A:/sys/devices/platform# ls -1 ag71xx-mdio.1 ag71xx.0 ag71xx.1 alarmtimer ar934x-nfc ar934x_wmac ath79-gpio ath79-wdt ehci-platform leds-gpio regulatory.0 serial8250 serial8250.0 uevent ``` And below is the output on new hardware with 17.02.4: ``` root@OpenWrt:~# iw dev wlan0 info command failed: No such device (-19) root@OpenWrt:~# dmesg | grep ath root@OpenWrt:~# root@OpenWrt:/sys/devices/platform# ls -1 ag71xx-mdio.1 ag71xx.0 ag71xx.1 alarmtimer ar934x-nfc ath79-gpio ath79-wdt ehci-platform leds-gpio regulatory.0 serial8250 serial8250.0 uevent ``` Unloading or loading ath9k module adds following line to dmesg: ``` root@OpenWrt:~# dmesg | grep ath [ 1175.108742] ath9k: ath9k: Driver unloaded ``` The above behaviour is same with 19.07.0 on the new hardware. I do not see ar934x_wmac in /sys/devices/platform on new hardware, but it is present on older hardware. Does anyone has a clue about what could be going on? I have access to both the types of numerous devices, so I can provide further debugging information as and when required. Thanks in advance. Regards, Nishant ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 2/5] build: image: Add pad-to and pad-rootfs-squashfs helpers
Hi, Bumping this thread after years. On 01/04/19 11:03, Jo-Philipp Wich wrote: I would like to avoid adding generating padded images by default. I just came up with this simple script, which takes an existing image and pads it to full size: http://nbd.name/pad-image.pl With this, shipping padded images should be unnecessary. Ok, if that is preferred, it's fine with me. But we should probably add some note somewhere, that in order to test this images in QEMU (x86, armvirt, malta), the images should be padded with this script in order to provide usable images. Most other targets ship image artifacts which are usable ootb, requiring one extra step to pad the combined images is a waste of user resources every single time. It also causes recurring confusion among users wanting to use x86 builds since the need for padding is neither documented, nor obvious while a combined.img.gz makes it obvious that it is an image file which requires decompression. I really don't see the huge problem with conservatively padding the combined image artifacts to something like 32 or 48MB, it must not even be 256M or more. I build large squashfs images (16GB, 32GB) for x86_64 running on Xeon processors for high workload gateways running VPN, Squid, Snort etc. Till OpenWrt 19.07, I was able to build 32GB images on a machine with only 8GB of RAM and 8GB of swap. sysupgrade also worked fine on those images. But since 21.02, I am getting the *memory exhausted* error. Below is the build log snippet for 23.05.2: dd if=/home/devuser/auto-build/hopbox-os/hopbox-openwrt/build_dir/target-x86_64_musl/linux-x86_64/root.squashfs >> /home/devuser/auto-build/hopbox-os/hopbox-openwrt/build_dir/target-x86_64_musl/linux-x86_64/tmp/hopbox-arthur-23.05.2.1-x86-64-generic-squashfs-rootfs.img.gz 39891+1 records in 39891+1 records out 20424365 bytes (20 MB, 19 MiB) copied, 0.0445292 s, 459 MB/s dd if=/home/devuser/auto-build/hopbox-os/hopbox-openwrt/build_dir/target-x86_64_musl/linux-x86_64/tmp/hopbox-arthur-23.05.2.1-x86-64-generic-squashfs-rootfs.img.gz of=/home/devuser/auto-build/hopbox-os/hopbox-openwrt/build_dir/target-x86_64_musl/linux-x86_64/tmp/hopbox-arthur-23.05.2.1-x86-64-generic-squashfs-rootfs.img.gz.new bs=16642998272 conv=sync dd: memory exhausted by input buffer of size 16642998272 bytes (16 GiB) Here the block size is set to 16GiB to pad rootfs and there are not enough system resources available on the build host to be able honour that. I don't see any special case to handle x86/x86_64 in image-commands.mk Is there a way I can disable padding for x86_64? Thanks in advance. Regards, Nishant ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
How to disable Image Padding for large x86 images?
Hello, This is in reference to this patchset: https://patchwork.ozlabs.org/project/openwrt/patch/1553868440-26476-3-git-send-email-yn...@true.cz/ I am unable to find an option to disable padding to x86 images as it is taking a lot of time to build and flash the images of size 16 / 32 GB. Thanks in advance. Regards, Nishant ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: padding of large 16-32GB images [Was: Re: [PATCH 2/5] build: image: Add pad-to and pad-rootfs-squashfs helpers]
Hi Petr, On 01/04/24 15:58, Petr Štetiar wrote: dd: memory exhausted by input buffer of size 16642998272 bytes (16 GiB) can you check https://patchwork.ozlabs.org/project/openwrt/patch/20240401102511.495791-1-yn...@true.cz/ ? Thanks! Thanks a lot for the fix. I tested it by building a 16GB squashfs EFI image for x86_64 on a host with just 8GB of RAM and build was successful without any errors. But, it takes a lot of time (around 20 minutes) writing this image to the device, which I suspect is due to padding. Earlier, it used to take less than 2 minutes. Is it possible to get "CONFIG_TARGET_IMAGES_PAD" back or some other switch that can be flipped to disable padding for images? Regards, Nishant ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Applying arch specific patch to package from feeds
Hello, How can I apply a patch to a package from the feed, only when the architecture is say, ramips but not when it is x86_64 or mips. If I put the patch in package's patch directory, it gets applied unconditionally. Thanks in advance for the pointers. Regards, Nishant ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
