On Mon, 23 Mar 2015, Janne Cederberg wrote:
I was thinking the same thing David mentioned, namely, that
determining channel change criterion is probably not trivial. Are you
guys familiar with Cisco Meraki?
Thinking about the problem a bit more.
First off, I don't believe that this can be com
For me a shell script is doing the job. Calling parameter is the target.
I use a separate configuration directory beside building directory.
I copy the correct files for the target into the files directory
and the correct .config into building directory
and then call make. All inside the script.
Hi a Quan,
I think you should try to modify "openwrt/Makefile"
Add your own script for target devices.
After that when compiling run "make target=XX" or something like that.
Nam.
On 24/03/2015 00:10, Nguyễn Hồng Quân wrote:
Hello all
If I want to build customized OpenWrt, I need to place al
If it's done on a per AP basis, and only happens when nobody is connected, it
probably doesn't have much effect. This will work when there aren't a lot of
users so the various APs go completely idle on a regular basis.
If a client tries to connect right after it has gone idle, they will just en
Oh, sorry Bastian I forgot to comment on your suggestion earlier!
Question: how does that "constant" restarting affect network QoS/throughput?
-Janne
2015-03-23 23:17 GMT+02:00 Bastian Bittorf :
> * Janne Cederberg [23.03.2015 22:13]:
>> So there's the auto mode in OpenWrt but that only consider
On Tue, Mar 24, 2015 at 12:01 PM, David Lang wrote:
> Is there any open implementation of this? opencapwap shows no updates in
> their wiki since 2012 and no files at all on their sourceforge page.
>
> I admit to being a bit skeptical about such approaches. They sound good in
> theory, and work f
Is there any open implementation of this? opencapwap shows no updates in their
wiki since 2012 and no files at all on their sourceforge page.
I admit to being a bit skeptical about such approaches. They sound good in
theory, and work fairly well when there aren't that many users, but I've never
Isn't CAPWAP designed for this?
xxiao
On 03/23/2015 07:42 PM, openwrt-devel-requ...@lists.openwrt.org wrote:
Re: Multiple OpenWrt devices collectively managed?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/c
* Janne Cederberg [23.03.2015 22:13]:
> So there's the auto mode in OpenWrt but that only considers the state
> of the wifi spectrum at the ifup of the wifi adapter, correct? So if
> things drastically change later, the AP would stay on the same channel
> and not switch.
what we do in our custom
Citeren Janne Cederberg :
Cool, this sparked a conversation :)
Yes, the background of the question was not a mesh network but a
network where all APs could be connected to the same switch for
example and from there to a DHCP server. A controller would control
which channels the APs operate on to
There were a few issues with the existing code to detect the model string:
* Always using the string starting with byte 56 would cut off the W of WNDR when
the ID starts with 29763654+16+128 instead of 29763654+16+64
* The string contained garbage after the zero byte instead of cutting it off
a
Cool, this sparked a conversation :)
Yes, the background of the question was not a mesh network but a
network where all APs could be connected to the same switch for
example and from there to a DHCP server. A controller would control
which channels the APs operate on to minimize interference a) fro
This changes the x86 image generation to match x86_64, using the PARTUUID for
the rootfs instead of explicitly configuring the device.
It unbreaks KVM with VirtIO, which uses /dev/vda2 instead of /dev/sda2.
Tested in QEMU/KVM with VirtIO, VirtualBox and VMware.
Signed-off-by: Matthias Schiffer
Otherwise the root device won't be found in 1/16 of the generated images
(whenever the signature starts with a zero digit).
Signed-off-by: Matthias Schiffer
---
target/linux/x86_64/image/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/x86_64/image/Makefi
On Mon, 23 Mar 2015, Bastian Bittorf wrote:
* David Lang [23.03.2015 20:19]:
question is around having something to automatically assign channels
amoung the different APs to minimize interference between the APs and
between the APs and other things in the area.
we just use hostapd & athXk &
* David Lang [23.03.2015 20:19]:
> question is around having something to automatically assign channels
> amoung the different APs to minimize interference between the APs and
> between the APs and other things in the area.
we just use hostapd & athXk & acs-survey/channel=auto...why dont you?
by
There is tool for that in buildroot... run ./scripts/env or look wiki for
more info. It's for having multiple device profiles in one buildroot.
Sami Olmari
On Mar 23, 2015 6:11 PM, "Nguyễn Hồng Quân" wrote:
>>
>> Hello all
>>
>> If I want to build customized OpenWrt, I need to place all custom
On Mon, 23 Mar 2015, Jean-Michel Pouré - GOOZE wrote:
you would be horrified to look under the covers of most linux based
appliances,
a lot of them are running a stock redhat/centos install with very
little
customization outside of the userspace app that they run. Gaping
security holes
in such a
> you would be horrified to look under the covers of most linux based
> appliances,
> a lot of them are running a stock redhat/centos install with very
> little
> customization outside of the userspace app that they run. Gaping
> security holes
> in such appliances are common.
Yes, I agree with
Le lundi 23 mars 2015 à 16:09 +0100, Bastian Bittorf a écrit :
> echo >>.config 'CONFIG_PACKAGE_luci=y'
> make defconfig # (this solves the dependencies)
> make
You spotted the right solution, this results in a nice configuration. I
feel that I am now able to automate daily compilation. OpenWRT
On Mon, 23 Mar 2015, Jean-Michel Pouré - GOOZE wrote:
Le lundi 23 mars 2015 à 16:21 +0100, Jonas Gorski a écrit :
This is currently not easily possible with OpenWrt, as it contains
several "out-of-tree" kernel modules, which aren't part of the kernel
sources and thus can't be statically linked
On Sun, 22 Mar 2015, Outback Dingo wrote:
On Sun, Mar 22, 2015 at 10:33 AM, valent.turko...@gmail.com <
valent.turko...@gmail.com> wrote:
On 21 March 2015 at 15:49, Janne Cederberg
wrote:
Greetings all!
Been searching around and found for example OpenWISP but thought I'd
ask the list as well
Allow using wpa_supplicant instead of authsae when joining mesh
networks with encryption. authsae is still prefered if installed.
Signed-off-by: Daniel Golle
---
.../mac80211/files/lib/netifd/wireless/mac80211.sh | 18 +++---
1 file changed, 11 insertions(+), 7 deletions(-)
diff
These new variants include support for mesh mode and SAE crypto.
They always depend on openssl as EC operations are not provided by
the internal crypto implementation.
Signed-off-by: Daniel Golle
---
package/network/services/hostapd/Config.in | 7 +++--
package/network/services/hostapd/Makefile
Le lundi 23 mars 2015 à 16:21 +0100, Jonas Gorski a écrit :
> This is currently not easily possible with OpenWrt, as it contains
> several "out-of-tree" kernel modules, which aren't part of the kernel
> sources and thus can't be statically linked into the kernel. For
> example all wifi drivers are
Le lundi 23 mars 2015 à 16:09 +0100, Bastian Bittorf a écrit :
> echo >>.config 'CONFIG_PACKAGE_luci=y'
> make defconfig # (this solves the dependencies)
> make
Thanks. I probably want to go this way for a better automation.
Kind regards,
Gnutella
___
Hello all
If I want to build customized OpenWrt, I need to place all custom file in
files/ folder.
The problem is that a set of custom files can only be applied to 1 device,
i.e /etc/config/wireless file for TP Link router can not be used for D-Link.
Is there any way that I can use a script to mo
Helpful to disable when debugging lldpd crashes (when working on it).
When privilege separation is on, some crashes are stack-traced to
some privilege separation code.
Signed-off-by: Alexandru Ardelean
---
package/network/services/lldpd/Config.in | 5 ++
package/network/services/lldpd
On Mon, Mar 23, 2015 at 5:28 PM, Stijn Tintel wrote:
> On 23-03-15 12:31, Alexandru Ardelean wrote:
> > Helpful to disable when debugging lldpd crashes (when working on it).
> > When priviledge separation is on, some crashes are stack-traced to
> > some priviledge separation code.
> Nitpicking, b
On 23-03-15 12:31, Alexandru Ardelean wrote:
> Helpful to disable when debugging lldpd crashes (when working on it).
> When priviledge separation is on, some crashes are stack-traced to
> some priviledge separation code.
Nitpicking, but the correct spelling is "privilege".
> Signed-off-by: Alexandr
On Mon, Mar 23, 2015 at 10:48 AM, wengbj wrote:
> ralink i2c driver is not working on MT7621 platform. Porting a new drivers
> from MTK's source code.
>
> Signed-off-by: wengbj
Please always sign off with your full real name.
Jonas
___
openwrt-devel
On Mon, Mar 23, 2015 at 3:51 PM, Jean-Michel Pouré - GOOZE
wrote:
> Dear all,
>
> I would like to discuss the ability to compile a minimal kernel with all
> needed modules compiled staticly. This is for custom projects. I know
> static kernels are not for mass-release as it would confuse users.
>
* Arjen de Korte [23.03.2015 16:06]:
> >So I need to activate compilation with:
> >echo >>.config 'CONFIG_PACKAGE_luci=y'
>
> No, you have to run 'make menuconfig' and select the luci package in
> there. In many cases, other packages are needed when you select a
> package. This is exactly what m
Citeren Jean-Michel Pouré - GOOZE :
Le lundi 23 mars 2015 à 15:18 +0100, Arjen de Korte a écrit :
No, you have to run 'make menuconfig' and select the luci package in
there. In many cases, other packages are needed when you select a
package. This is exactly what menuconfig automates (so making
Dear all,
I would like to discuss the ability to compile a minimal kernel with all
needed modules compiled staticly. This is for custom projects. I know
static kernels are not for mass-release as it would confuse users.
Is there a way to achieve something similar to:
make localyesconfig
turns mo
Hi.
> Thanks, I got it now. So I should run make oldconfig when compiling
> automatically everyday?
The best approach is the following:
- Initially use menuconfig and select stuff as you like
- Extract the delta compared to the defualt configuration with
scripts/diffconfig.sh:
$ ./scripts/
Le lundi 23 mars 2015 à 15:18 +0100, Arjen de Korte a écrit :
> No, you have to run 'make menuconfig' and select the luci package in
> there. In many cases, other packages are needed when you select a
> package. This is exactly what menuconfig automates (so making
> changes
> by hand in the g
Citeren Jean-Michel Pouré - GOOZE :
Le lundi 23 mars 2015 à 21:21 +0800, Yousong Zhou a écrit :
"./scripts/feeds install pkgname" will make those packages
visible/available/selectable in menuconfig (creating links in
package/feeds/feedsname/) as the prior update action only fetches them
down as
Le lundi 23 mars 2015 à 21:21 +0800, Yousong Zhou a écrit :
> "./scripts/feeds install pkgname" will make those packages
> visible/available/selectable in menuconfig (creating links in
> package/feeds/feedsname/) as the prior update action only fetches them
> down as is.
Thanks!
So I need to acti
On 23 March 2015 at 21:07, Jean-Michel Pouré - GOOZE wrote:
>> but it works and you can tweak it individually via 'make menuconfig'.
>> what we do here, is e.g.:
>> echo >.config 'CONFIG_TARGET_ar71xx_generic_TLWR1043=y'
>
> Thanks. Due to ignorance, I could not figure it out.
>
> So my script be
Hi all,
I was wondering if some of you guys know about any "automated hotspot
testing tool"?
The thing is:
I have a bunch of hotspots running a crafted OpenWRT firmware that I
compile myself.
Prior each firmware release I manually do a lot of tests like:
- try to get an IP addre
> but it works and you can tweak it individually via 'make menuconfig'.
> what we do here, is e.g.:
> echo >.config 'CONFIG_TARGET_ar71xx_generic_TLWR1043=y'
Thanks. Due to ignorance, I could not figure it out.
So my script becomes:
git clone git://git.openwrt.org/openwrt.git openwrt-ar71xx
cd
On 23 March 2015 at 20:07, Jean-Michel Pouré - GOOZE wrote:
>> I read buildroot WIKI page:
>> http://wiki.openwrt.org/doc/howto/build
>
> I am getting confused about the build system.
>
> I am comparing .config generated by buildroot (today's GIT) with
> https://downloads.openwrt.org/snapshots/tru
* Jean-Michel Pouré - GOOZE [23.03.2015 13:30]:
> Obviously, I need a default .config file before using buildroot.
> Where is it stored and published?
just type 'make defconfig'.
this is maybe not the config you have found somewhere,
but it works and you can tweak it individually via 'make menuc
> I read buildroot WIKI page:
> http://wiki.openwrt.org/doc/howto/build
I am getting confused about the build system.
I am comparing .config generated by buildroot (today's GIT) with
https://downloads.openwrt.org/snapshots/trunk/ar71xx/generic/config
and this is not the same file.
Obviously, I
On 23 March 2015 at 17:49, Jean-Michel Pouré - GOOZE wrote:
>> /target/linux/ar71xx/image/Makefile
>
> I read buildroot WIKI page:
> http://wiki.openwrt.org/doc/howto/build
>
> Pardon my ignorance, I am new to OpenWRT.
>
> If I select target TP-Link TL-WR841ND in target of make-menuconfig
> this t
Helpful to disable when debugging lldpd crashes (when working on it).
When priviledge separation is on, some crashes are stack-traced to
some priviledge separation code.
Signed-off-by: Alexandru Ardelean
---
package/network/services/lldpd/Config.in | 5 ++
package/network/services/lld
From: Alexandru Ardelean
Helpful to disable when debugging lldpd crashes (when working on it).
When priviledge separation is on, some crashes are stack-traced to
some priviledge separation code.
Signed-off-by: Alexandru Ardelean
---
package/network/services/lldpd/Config.in | 5 ++
p
* Jean-Michel Pouré - GOOZE [23.03.2015 11:28]:
> Will it select automatically this .config file:
> target/linux/ar71xx/config-3.18
yes. the number is taken from 'include/kernel-version.mk'
bye, bastian
___
openwrt-devel mailing list
openwrt-devel@list
> /target/linux/ar71xx/image/Makefile
I read buildroot WIKI page:
http://wiki.openwrt.org/doc/howto/build
Pardon my ignorance, I am new to OpenWRT.
If I select target TP-Link TL-WR841ND in target of make-menuconfig
this triggers /target/linux/ar71xx/image/Makefile
Will it select automatically t
ralink i2c driver is not working on MT7621 platform. Porting a new drivers from
MTK's source code.
Signed-off-by: wengbj
---
.../0111-i2c-MIPS-add-mt7621-I2C-driver.patch | 335
1 file changed, 335 insertions(+)
create mode 100755
target/linux/ramips/patches-3.18/01
51 matches
Mail list logo
