Re: [OpenWrt-Devel] abc7ed2c ath79: add support for D-Link DIR-859 A1

[Weedy]

Is there any reason this would should fail or brick a 859L A3?
On the D-Link site they don't separate A1 or A3 so I should be fine?

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Mac address randomization on rsPro ath79

[Weedy]

On Sun, 28 Oct 2018 at 03:09, matt merhar  wrote:
>
> ‐‐‐ Original Message ‐‐‐
> On Sunday, October 28, 2018 12:40 AM, Weedy  wrote:
>
> > On Sat, 27 Oct 2018 at 22:46, matt merhar mattmer...@protonmail.com wrote:
> >
> > > Hi,
> >
> > Hello, I replied to you on IRC but like 2 days later :V
>
> Yeah, I figured it would be better to get the reply on the ML anyhow, as it 
> might help others.
>
> > > Due to the switch to using devicetree in ath79, it became necessary to
> > > populate the MAC addresses via userland during first boot. This is done
> > > using target/linux/ath79/base-files/etc/board.d/02_network,
> > > specifically:
> > >
> > > ubnt,routerstation|\\
> > > ubnt,routerstation-pro)
> > > wan_mac=$(fconfig -s -r -d $(find_mtd_part "RedBoot 
> > > config") -n ar7100_esa)
> > > lan_mac=$(macaddr_add "$wan_mac" 1)
> > >
> > >
> > > This said, I can think of a few potential reasons for your
> > > /etc/config/network to lack the 'macaddr' option for lan/wan interfaces:
> > > 1.) Rather than modify the UCI network config generated at first boot,
> > > the config was instead overwritten with those from an ar71xx install
> > > (uploading via scp, .tar.gz via LuCI, cat >, etc.)
> >
> > I use $topdir/flies/
>
> This is probably causing the issue. If you're building a pre-made
> $topdir/files/etc/config/network into the image, I don't believe it will
> overwrite that existing /etc/config/network file on first boot. If you
> want to continue doing things this way then you'll need to add the
> 'macaddr' options to your $topdir config, or alternatively try using the
> patch I provided. I suppose you could also add something like an init
> script to update the config file (e.g. with "uci set") on boot instead.

When I upgraded my tplink4300 the wifi code added another block to my
$topdir customized config for the 2.4ghz radio, the pci path had
changed. Shouldn't the boot code check for unset macaddr and uci
commit like the wifi code does?

> If you check /etc/board.json it should still contain the autogenerated
> config similar to:
>
> ...
> "network": {
> "wan": {
> "ifname": "eth0",
> "protocol": "dhcp",
> "macaddr": "00:15:6d:aa:bb:cc"
> },
> "lan": {
> "ifname": "eth1.1",
> "protocol": "static",
> "macaddr": "00:15:6d:aa:bb:cd"
> }
> },
> ...
>
> ...as long as you're not pre-populating that file in $topdir/files as
> well. If the MACs there are correct then things are working as intended.

This is all fine and my macs are also 00:15:6d:aa:bb:cc, so I just
copied them over to my $topdir/.
From my end the problem is solved, thanks for your time.

> > > 2.) Using sysupgrade -F and preserving the old config while migrating
> > > from ar71xx -> ath79
> > > 2.) Building your own image and deselecting the 'fconfig' utility which
> > > is necessary to read the base MAC address from the RedBoot config
> > > partition
> >
> > Now this is interesting because I use defconfig. I don't mind adding
> > fconfig to my scripts, but then why isn't defconfig picking that up?
> >
> > buildImage () {
> > make V=99 defconfig && \
> > nice -n 7 make V=1 -j4 || exit 1
> > }
> > cat configs/rsPRO-home-repeater.config > .config
> >
> > buildImage
> > scp 
> > bin/targets/ath79/generic/openwrt-ath79-generic-ubnt_routerstation-pro-squashfs-sysupgrade.bin
> >
> >
> > r...@repeater.lan:/tmp/
> >
> > $ cat configs/rsPRO-home-repeater.config
> > CONFIG_TARGET_ath79=y
> > CONFIG_TARGET_ath79_generic=y
> > CONFIG_TARGET_ath79_generic_DEVICE_ubnt_routerstation-pro=y
> > CONFIG_PACKAGE_wpad=y
> > CONFIG_PACKAGE_wpad-mini=n
> > CONFIG_ATH_USER_REGD=y
> > CONFIG_PACKAGE_ATH_DFS=y
> > CONFIG_PACKAGE_ATH_DYNACK=y
> > CONFIG_PACKAGE_kmod-ath9k=y
> > CONFIG_ATH9K_SUPPORT_PCOEM=y
> > CONFIG_ATH9K_UBNTHSR=n
>
> I tested this (to the point of running "make defconfig" anyways) and the
> following *are* properly selected in .config using the contents of your
> configs/rsPRO-home-repeater.config:
>
> CONFIG_DEFAULT_fconfig=y
> CONFIG_PACKAGE_fconfig=y
>
> It lives at /usr/sbin/fconfig on the router.

I didn't bother to check this, I was assuming that lacking this util
caused my random macs.
You are right it's there.

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Mac address randomization on rsPro ath79

[Weedy]

On Sat, 27 Oct 2018 at 22:46, matt merhar  wrote:
>
> Hi,
Hello, I replied to you on IRC but like 2 days later :V

> Due to the switch to using devicetree in ath79, it became necessary to
> populate the MAC addresses via userland during first boot. This is done
> using target/linux/ath79/base-files/etc/board.d/02_network,
> specifically:
>
> ubnt,routerstation|\
> ubnt,routerstation-pro)
> wan_mac=$(fconfig -s -r -d $(find_mtd_part "RedBoot config") 
> -n ar7100_esa)
> lan_mac=$(macaddr_add "$wan_mac" 1)
>
> This said, I can think of a few potential reasons for your
> /etc/config/network to lack the 'macaddr' option for lan/wan interfaces:
>
> 1.) Rather than modify the UCI network config generated at first boot,
> the config was instead overwritten with those from an ar71xx install
> (uploading via scp, .tar.gz via LuCI, cat >, etc.)
I use $topdir/flies/

> 2.) Using sysupgrade -F and preserving the old config while migrating
> from ar71xx -> ath79
> 2.) Building your own image and deselecting the 'fconfig' utility which
> is necessary to read the base MAC address from the RedBoot config
> partition
Now this is interesting because I use defconfig. I don't mind adding
fconfig to my scripts, but then why isn't defconfig picking that up?

buildImage () {
make V=99 defconfig && \
nice -n 7 make V=1 -j4 || exit 1
}
cat configs/rsPRO-home-repeater.config > .config
buildImage
scp 
bin/targets/ath79/generic/openwrt-ath79-generic-ubnt_routerstation-pro-squashfs-sysupgrade.bin
r...@repeater.lan:/tmp/

$ cat configs/rsPRO-home-repeater.config
CONFIG_TARGET_ath79=y
CONFIG_TARGET_ath79_generic=y
CONFIG_TARGET_ath79_generic_DEVICE_ubnt_routerstation-pro=y
CONFIG_PACKAGE_wpad=y
CONFIG_PACKAGE_wpad-mini=n
CONFIG_ATH_USER_REGD=y
CONFIG_PACKAGE_ATH_DFS=y
CONFIG_PACKAGE_ATH_DYNACK=y
CONFIG_PACKAGE_kmod-ath9k=y
CONFIG_ATH9K_SUPPORT_PCOEM=y
CONFIG_ATH9K_UBNTHSR=n

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Mac address randomization on rsPro ath79

[Weedy]

I'm currently having some fun on master and noticed every reboot gives
me random mac addresses. Never happened on ar71xx.

 LAN configuration
config interface lan
option ifname   eth1
option type bridge
option protodhcp
option hostname 'repeater'
option ipv6 0

config interface lanAlias
option ifname   br-lan
option protostatic
option ipaddr   192.168.69.1
option netmask  255.255.255.0

config interface lanEmerg
option ifname   eth0
option protostatic
option ipaddr   192.168.42.1
option netmask  255.255.255.0

root@repeater:~# ifconfig
br-lanLink encap:Ethernet  HWaddr 1E:3C:CB:9D:D7:D7
  inet addr:192.168.69.1  Bcast:192.168.69.255  Mask:255.255.255.0
...

eth0  Link encap:Ethernet  HWaddr F6:1A:54:6F:68:23
  inet addr:192.168.42.1  Bcast:192.168.42.255  Mask:255.255.255.0
...
  Interrupt:4

eth1  Link encap:Ethernet  HWaddr 1E:3C:CB:9D:D7:D7
...
  Interrupt:5

root@repeater:~# ifconfig
br-lanLink encap:Ethernet  HWaddr 2A:F7:8A:0F:2A:65
  inet addr:192.168.69.1  Bcast:192.168.69.255  Mask:255.255.255.0
...
eth0  Link encap:Ethernet  HWaddr 2A:CE:6B:79:1E:B8
  inet addr:192.168.42.1  Bcast:192.168.42.255  Mask:255.255.255.0
...
  Interrupt:4

eth1  Link encap:Ethernet  HWaddr 2A:F7:8A:0F:2A:65
...
  Interrupt:5

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] ath79: RouterStation Pro build failure

[Weedy]

I have build system that adds a couple packages (qos-scripts, munin,
iptables modules, etc) to the default list and builds images for my
systems.

For the purposes of the bug report the differences are:

echo 'CONFIG_TARGET_ath79=y
CONFIG_TARGET_ath79_generic=y
CONFIG_TARGET_ath79_generic_DEVICE_tplink_tl-wdr4300=y
CONFIG_PACKAGE_wpad=y
CONFIG_PACKAGE_wpad-mini=n
' > .config
make defconfig

vs.

echo 'CONFIG_TARGET_ath79=y
CONFIG_TARGET_ath79_generic=y
CONFIG_TARGET_ath79_generic_DEVICE_ubnt_routerstation-pro=y
CONFIG_PACKAGE_wpad=y
CONFIG_PACKAGE_wpad-mini=n
' > .config
make defconfig

I've been on ar71xx a LONG long time and my tl-wdr4300 has been on
ath79 at least a month maybe 2. Today I decided to flip my RSpro over
to ath79 and it puked all over hostapd-wpad-full-internal. Then I did
a make distclean and a puked again so here I am.
Honestly I didn't expect RSpro to rebuild anything vs. tl-wdr4300 but
it insists and somethings dies. Even after erroring out if I swap out
RSpro for tl-wdr4300 in the .config it will rebuild wpad again but
everything works and I get a firmware file at the end.

Thank you for your time.


make[3]: Leaving directory
'/home/weedy/projects/openwrt-lede/package/network/services/dropbear'
time: package/network/services/dropbear/compile#0.13#0.01#0.14
make[3]: Entering directory
'/home/weedy/projects/openwrt-lede/package/libs/gettext'
make[3]: Leaving directory
'/home/weedy/projects/openwrt-lede/package/libs/gettext'
time: package/libs/gettext/compile#0.12#0.03#0.14
make[3]: Entering directory
'/home/weedy/projects/openwrt-lede/package/libs/libiconv'
make[3]: Leaving directory
'/home/weedy/projects/openwrt-lede/package/libs/libiconv'
time: package/libs/libiconv/compile#0.12#0.03#0.14
make[3]: Entering directory
'/home/weedy/projects/openwrt-lede/package/libs/libtool'
make[3]: Leaving directory
'/home/weedy/projects/openwrt-lede/package/libs/libtool'
time: package/libs/libtool/compile#0.11#0.02#0.12
make[3]: Entering directory
'/home/weedy/projects/openwrt-lede/package/libs/wolfssl'
make[3]: Leaving directory
'/home/weedy/projects/openwrt-lede/package/libs/wolfssl'
time: package/libs/wolfssl/compile#0.12#0.02#0.13
make[3]: Entering directory
'/home/weedy/projects/openwrt-lede/package/network/services/hostapd'
rm -f 
/home/weedy/projects/openwrt-lede/build_dir/target-mips_24kc_musl/hostapd-wpad-full-internal/hostapd-2018-05-21-62566bc2/.built
touch 
/home/weedy/projects/openwrt-lede/build_dir/target-mips_24kc_musl/hostapd-wpad-full-internal/hostapd-2018-05-21-62566bc2/.built_check
echo ` 
CFLAGS="-I/home/weedy/projects/openwrt-lede/staging_dir/target-mips_24kc_musl/usr/include/libnl-tiny
-I/home/weedy/projects/openwrt-lede/build_dir/target-mips_24kc_musl/hostapd-wpad-full-internal/hostapd-2018-05-21-62566bc2/src/crypto
-I/home/weedy/projects/openwrt-lede/staging_dir/target-mips_24kc_musl/usr/include
-I/home/weedy/projects/openwrt-lede/staging_dir/target-mips_24kc_musl/include
-I/home/weedy/projects/openwrt-lede/staging_dir/toolchain-mips_24kc_gcc-7.3.0_musl/usr/include
-I/home/weedy/projects/openwrt-lede/staging_dir/toolchain-mips_24kc_gcc-7.3.0_musl/include/fortify
-I/home/weedy/projects/openwrt-lede/staging_dir/toolchain-mips_24kc_gcc-7.3.0_musl/include
-DCONFIG_LIBNL20 -D_GNU_SOURCE -DCONFIG_MSG_MIN_PRIORITY=3 -Os -pipe
-mno-branch-likely -mips32r2 -mtune=24kc -fno-caller-saves -fno-plt
-fhonour-copts -Wno-error=unused-but-set-variable
-Wno-error=unused-result -msoft-float -mips16 -minterlink-mips16
-iremap/home/weedy/projects/openwrt-lede/build_dir/target-mips_24kc_musl/hostapd-wpad-full-internal/hostapd-2018-05-21-62566bc2:hostapd-2018-05-21-62566bc2
-Wformat -Werror=format-security -fstack-protector -D_FORTIFY_SOURCE=1
-Wl,-z,now -Wl,-z,relro -ffunction-sections -fdata-sections -flto"
make  -C 
/home/weedy/projects/openwrt-lede/build_dir/target-mips_24kc_musl/hostapd-wpad-full-internal/hostapd-2018-05-21-62566bc2/hostapd
AR="mips-openwrt-linux-musl-gcc-ar" AS="mips-openwrt-linux-musl-gcc -c
-Os -pipe -mno-branch-likely -mips32r2 -mtune=24kc -fno-caller-saves
-fno-plt -fhonour-copts -Wno-error=unused-but-set-variable
-Wno-error=unused-result -msoft-float
-iremap/home/weedy/projects/openwrt-lede/build_dir/target-mips_24kc_musl/hostapd-wpad-full-internal/hostapd-2018-05-21-62566bc2:hostapd-2018-05-21-62566bc2
-Wformat -Werror=format-security -fstack-protector -D_FORTIFY_SOURCE=1
-Wl,-z,now -Wl,-z,relro -ffunction-sections -fdata-sections -flto"
LD=mips-openwrt-linux-musl-ld NM="mips-openwrt-linux-musl-gcc-nm"
CC="mips-openwrt-linux-musl-gcc" GCC="mips-openwrt-linux-musl-gcc"
CXX="mips-openwrt-linux-musl-g++"
RANLIB="mips-openwrt-linux-musl-gcc-ranlib"
STRIP=mips-openwrt-linux-musl-strip
OBJCOPY=mips-openwrt-linux-musl-objcopy
OBJDUMP=mips-openwrt-linux-musl-objdump
SIZE=mips-openwrt-linux-musl-size CONFIG_ACS= CONFIG_DRIVER_NL80211=
CONFIG_IEEE80211N= CONFIG_IEEE80211AC= CONFIG_DRIVER_W

Re: [OpenWrt-Devel] [LEDE-DEV] [PATCH 00/15] Metadata generator refactoring, cleanup and PROVIDES improvements

[Weedy]

On 2018-01-14 08:12 AM, Jo-Philipp Wich wrote:
> Hi Weedy,
> 
> can you provide some more context lines to see which package those broken 
> depends belong to?
> 
> Thanks,
> Jo
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> 

menu "LuCI"

menu "3. Applications"
config PACKAGE_luci-app-acme
tristate "luci-app-acme.. ACME
package - LuCI interface"
default y if DEFAULT_luci-app-acme
default m if ALL
select PACKAGE_libc
select PACKAGE_librt if USE_GLIBC
***depends on
depends on PACKAGE_lua
select PACKAGE_libpthread if USE_GLIBC
select PACKAGE_acme
select PACKAGE_libssp if SSP_SUPPORT
help
 Control the ACME Letsencrypt certificate interface
 Toke Høiland-Jørgensen <t...@toke.dk>

config PACKAGE_luci-app-sqm
tristate "luci-app-sqm SQM
Scripts - LuCI interface"
default y if DEFAULT_luci-app-sqm
default m if ALL
select PACKAGE_libc
***depends on
select PACKAGE_librt if USE_GLIBC
depends on PACKAGE_lua
depends on !LINUX_3_18
select PACKAGE_libssp if SSP_SUPPORT
select PACKAGE_libpthread if USE_GLIBC
select PACKAGE_sqm-scripts
help
 Luci interface for the SQM scripts queue management
configuration package.
 Toke Høiland-Jørgensen <t...@toke.dk>

endmenu
endmenu
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [LEDE-DEV] [PATCH 00/15] Metadata generator refactoring, cleanup and PROVIDES improvements

[Weedy]

On 14 January 2018 at 06:21, Weedy <weedy2...@gmail.com> wrote:
> On 8 January 2018 at 14:02, Matthias Schiffer
> <mschif...@universe-factory.net> wrote:
>> I've pushed an updated branch fixing the mistake Jo pointed out and some
>> other stylistic improvements to the metadata2 branch of my staging tree [3].
>>
>>
>>> [1] https://github.com/openwrt/packages/pull/5370
>>> [2] https://github.com/openwrt-routing/packages/pull/345
>>
>> [3]
>> https://git.lede-project.org/?p=openwrt/staging/neoraider.git;a=shortlog;h=refs/heads/metadata2
>
>
> So the base repo works:
> $ make
> Checking 'working-make'... ok.
> Checking 'case-sensitive-fs'... ok.
> Checking 'proper-umask'... ok.
> Checking 'gcc'... ok.
> Checking 'working-gcc'... ok.
> Checking 'g++'... ok.
> Checking 'working-g++'... ok.
> Checking 'ncurses'... ok.
> Checking 'zlib'... ok.
> Checking 'perl-thread-queue'... ok.
> Checking 'tar'... ok.
> Checking 'find'... ok.
> Checking 'bash'... ok.
> Checking 'patch'... ok.
> Checking 'diff'... ok.
> Checking 'cp'... ok.
> Checking 'seq'... ok.
> Checking 'awk'... ok.
> Checking 'grep'... ok.
> Checking 'getopt'... ok.
> Checking 'stat'... ok.
> Checking 'unzip'... ok.
> Checking 'bzip2'... ok.
> Checking 'wget'... ok.
> Checking 'perl'... ok.
> Checking 'python'... ok.
> Checking 'git'... ok.
> Checking 'file'... ok.
> Checking 'ldconfig-stub'... ok.
> Collecting package info: done
> Collecting target info: done
> WARNING: Makefile 'package/utils/busybox/Makefile' has a dependency on
> 'libpam', which does not exist
> WARNING: Makefile 'package/utils/busybox/Makefile' has a build
> dependency on 'libpam', which does not exist
> WARNING: Makefile 'package/network/utils/curl/Makefile' has a
> dependency on 'libgnutls', which does not exist
> WARNING: Makefile 'package/network/utils/curl/Makefile' has a
> dependency on 'libopenldap', which does not exist
> WARNING: Makefile 'package/network/utils/curl/Makefile' has a
> dependency on 'libidn', which does not exist
> WARNING: Makefile 'package/network/utils/curl/Makefile' has a
> dependency on 'libssh2', which does not exist
> WARNING: Makefile 'package/boot/kexec-tools/Makefile' has a dependency
> on 'liblzma', which does not exist
> WARNING: Makefile 'package/kernel/linux/Makefile' has a dependency on
> 'kmod-usb-musb-tusb6010', which does not exist
> WARNING: Makefile 'package/network/services/lldpd/Makefile' has a
> dependency on 'libnetsnmp', which does not exist
> make[2]: Entering directory '/home/weedy/projects/openwrt-lede/scripts/config'
> conf.c: In function 'check_stdin':
> conf.c:78:3: warning: format not a string literal and no format
> arguments [-Wformat-security]
>printf(_("aborted!\n\n"));
>^~
> conf.c:79:3: warning: format not a string literal and no format
> arguments [-Wformat-security]
>printf(_("Console input/output is redirected. "));
>^~
> conf.c:80:3: warning: format not a string literal and no format
> arguments [-Wformat-security]
>printf(_("Run 'make oldconfig' to update configuration.\n\n"));
>^~
> conf.c: In function 'conf_askvalue':
> conf.c:90:3: warning: format not a string literal and no format
> arguments [-Wformat-security]
>printf(_("(NEW) "));
>^~
> conf.c: In function 'conf_choice':
> conf.c:291:5: warning: format not a string literal and no format
> arguments [-Wformat-security]
>  printf(_(" (NEW)"));
>  ^~
> conf.c: In function 'check_conf':
> conf.c:439:6: warning: format not a string literal and no format
> arguments [-Wformat-security]
>   printf(_("*\n* Restart config...\n*\n"));
>   ^~
> conf.c: In function 'main':
> conf.c:620:6: warning: format not a string literal and no format
> arguments [-Wformat-security]
>   _("\n*** The configuration requires explicit update.\n\n"));
>   ^
> conf.c:674:4: warning: format not a string literal and no format
> arguments [-Wformat-security]
> fprintf(stderr, _("\n*** Error during writing of the 
> configuration.\n\n"));
> ^~~
> conf.c:678:4: warning: format not a string literal and no format
> arguments [-Wformat-security]
> fprintf(stderr, _("\n*** Error during update of the configuration.\n\n"));
> ^~~
> conf.c:689:4: warning: format not a string literal and no format
> arguments [-Wformat-security]
> fprintf(stderr, _("\n*** Error during writing of the 
> configuration.\n\n"));
> ^~~
> make[2]: Leaving directory '/home/weedy/projects/openwrt-lede/scripts/config'
> make[2]: Entering

Re: [OpenWrt-Devel] [LEDE-DEV] [PATCH 00/15] Metadata generator refactoring, cleanup and PROVIDES improvements

[Weedy]

On 8 January 2018 at 14:02, Matthias Schiffer
<mschif...@universe-factory.net> wrote:
> I've pushed an updated branch fixing the mistake Jo pointed out and some
> other stylistic improvements to the metadata2 branch of my staging tree [3].
>
>
>> [1] https://github.com/openwrt/packages/pull/5370
>> [2] https://github.com/openwrt-routing/packages/pull/345
>
> [3]
> https://git.lede-project.org/?p=openwrt/staging/neoraider.git;a=shortlog;h=refs/heads/metadata2


So the base repo works:
$ make
Checking 'working-make'... ok.
Checking 'case-sensitive-fs'... ok.
Checking 'proper-umask'... ok.
Checking 'gcc'... ok.
Checking 'working-gcc'... ok.
Checking 'g++'... ok.
Checking 'working-g++'... ok.
Checking 'ncurses'... ok.
Checking 'zlib'... ok.
Checking 'perl-thread-queue'... ok.
Checking 'tar'... ok.
Checking 'find'... ok.
Checking 'bash'... ok.
Checking 'patch'... ok.
Checking 'diff'... ok.
Checking 'cp'... ok.
Checking 'seq'... ok.
Checking 'awk'... ok.
Checking 'grep'... ok.
Checking 'getopt'... ok.
Checking 'stat'... ok.
Checking 'unzip'... ok.
Checking 'bzip2'... ok.
Checking 'wget'... ok.
Checking 'perl'... ok.
Checking 'python'... ok.
Checking 'git'... ok.
Checking 'file'... ok.
Checking 'ldconfig-stub'... ok.
Collecting package info: done
Collecting target info: done
WARNING: Makefile 'package/utils/busybox/Makefile' has a dependency on
'libpam', which does not exist
WARNING: Makefile 'package/utils/busybox/Makefile' has a build
dependency on 'libpam', which does not exist
WARNING: Makefile 'package/network/utils/curl/Makefile' has a
dependency on 'libgnutls', which does not exist
WARNING: Makefile 'package/network/utils/curl/Makefile' has a
dependency on 'libopenldap', which does not exist
WARNING: Makefile 'package/network/utils/curl/Makefile' has a
dependency on 'libidn', which does not exist
WARNING: Makefile 'package/network/utils/curl/Makefile' has a
dependency on 'libssh2', which does not exist
WARNING: Makefile 'package/boot/kexec-tools/Makefile' has a dependency
on 'liblzma', which does not exist
WARNING: Makefile 'package/kernel/linux/Makefile' has a dependency on
'kmod-usb-musb-tusb6010', which does not exist
WARNING: Makefile 'package/network/services/lldpd/Makefile' has a
dependency on 'libnetsnmp', which does not exist
make[2]: Entering directory '/home/weedy/projects/openwrt-lede/scripts/config'
conf.c: In function 'check_stdin':
conf.c:78:3: warning: format not a string literal and no format
arguments [-Wformat-security]
   printf(_("aborted!\n\n"));
   ^~
conf.c:79:3: warning: format not a string literal and no format
arguments [-Wformat-security]
   printf(_("Console input/output is redirected. "));
   ^~
conf.c:80:3: warning: format not a string literal and no format
arguments [-Wformat-security]
   printf(_("Run 'make oldconfig' to update configuration.\n\n"));
   ^~
conf.c: In function 'conf_askvalue':
conf.c:90:3: warning: format not a string literal and no format
arguments [-Wformat-security]
   printf(_("(NEW) "));
   ^~
conf.c: In function 'conf_choice':
conf.c:291:5: warning: format not a string literal and no format
arguments [-Wformat-security]
 printf(_(" (NEW)"));
 ^~
conf.c: In function 'check_conf':
conf.c:439:6: warning: format not a string literal and no format
arguments [-Wformat-security]
  printf(_("*\n* Restart config...\n*\n"));
  ^~
conf.c: In function 'main':
conf.c:620:6: warning: format not a string literal and no format
arguments [-Wformat-security]
  _("\n*** The configuration requires explicit update.\n\n"));
  ^
conf.c:674:4: warning: format not a string literal and no format
arguments [-Wformat-security]
fprintf(stderr, _("\n*** Error during writing of the configuration.\n\n"));
^~~
conf.c:678:4: warning: format not a string literal and no format
arguments [-Wformat-security]
fprintf(stderr, _("\n*** Error during update of the configuration.\n\n"));
^~~
conf.c:689:4: warning: format not a string literal and no format
arguments [-Wformat-security]
    fprintf(stderr, _("\n*** Error during writing of the configuration.\n\n"));
^~~
make[2]: Leaving directory '/home/weedy/projects/openwrt-lede/scripts/config'
make[2]: Entering directory '/home/weedy/projects/openwrt-lede'
make[3]: Entering directory '/home/weedy/projects/openwrt-lede/scripts/config'
make[3]: Leaving directory '/home/weedy/projects/openwrt-lede/scripts/config'
make[3]: Entering directory '/home/weedy/projects/openwrt-lede'
make[3]: Leaving directory '/home/weedy/projects/openwrt-lede'
WARNING: Makefile 'package/utils/busybox/Makefile' has a dependency on
'libpam', which does not exist
WARNING: Makefile 'package/utils/busybox/Makefile' has a build
dependency on 'libpam', which does not exist
WARNING: Makefile 'package/network/utils/curl/Makefile' has a
dependency on 'libgnutls', w

Re: [OpenWrt-Devel] WiFi client mode leaves router inaccessible if upstream network goes down

[Weedy]

On 3 February 2017 at 19:17, Nick Malyon  wrote:
> If anyone has a workaround that would be great — currently I managed to get 
> back in range of a network to make it accessible again, and now I run from 
> batteries and delete the wifi client configuration every night before the 
> jungle power goes out.


Do you have access to a PC? I would be interested in seeing the
wireless config file. specifically if the AP or STA section is listed
first.

I have a script I use to keep my repeated online in case of bullshit.
I can probably modify it to help you out if I get your config. Are you
using the template off the wiki with relayd and interface wwan etc?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [LEDE-DEV] MT7620A WiFi issue - with a twist!

[Weedy]

On 1 February 2017 at 15:29, Jamie Stuart  wrote:
> Hello LEDE / OpenWRT devs,
>
> I am requesting your help. First a little background…
...
> This a known issue with the chipset and seems to have been round for years.
> We are currently building on LEDE trunk and still the issue persists.
>
> We are not driver developers, so my question is whether anyone with
> knowledge can help and provide a proper fix for this issue?


You will probably have the most luck posting a bounty on the linux
wifi mailing list.

Your root problem is picking a platform that basically uses a client
mode tested driver in AP mode and then hanging a million clients off
of it. I'm honestly surprised it didn't fall over sooner.

May I suggest when it comes time to refresh the hardware you guys pick
something with NGFF or mini-pcie slots for ALL radios.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [RFD] Future - suggestion for the teleconference

[Weedy]

On 3 Jul 2016 07:03, "Luke McKee"  wrote:
>
> Suggestion for the teleconference:
>
> Talkshoe.com
>
> Talkshoe is free. It has a web client too with a chat log when the
> conference call starts.

Google hangouts?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH 02/05] [tools] findutils glibc >= 2.23 compat

[Weedy]

On 25 Apr 2016 1:33 pm, "Jo-Philipp Wich"  wrote:
>
> Hi,
>
> this should be handled already, configure uses AC_HEADER_MAJOR and
> mountlist.c does:
>
> #ifdef MAJOR_IN_SYSMACROS
> #include 
> #define HAVE_MAJOR
> ...
>
> did you patched findutils proactively or was there an actual build issue?

I patched everything in response to failures. If it's already in there then
I dunno why it's not getting enabled.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH 05/05] [tools] squashfs4 glibc >= 2.23 compat

[Weedy]

With the update to glibc 2.23, sys/types.h doesn't inherit
sys/sysmacros.h anymore. We need to include it manually.

Signed-off-by: Weedy <weedy2...@gmail.com>

--- /dev/null   2016-04-18 05:53:30.273258717 -0400
+++ tools/squashfs4/patches/125-glibc-2.23-sysmacros.patch  2016-04-24
16:22:30.271759670 -0400
@@ -0,0 +1,20 @@
+--- a/squashfs-tools/mksquashfs.c  2016-04-24 16:10:19.230996009 -0400
 b/squashfs-tools/mksquashfs.c  2016-04-24 16:10:54.671356457 -0400
+@@ -33,6 +33,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include 
+ #include 
+ #include 
+--- a/squashfs-tools/unsquashfs.c  2016-04-24 16:14:24.310155265 -0400
 b/squashfs-tools/unsquashfs.c  2016-04-24 16:14:46.560381562 -0400
+@@ -30,6 +30,7 @@
+ #include "xattr.h"
+
+ #include 
++#include 
+
+ struct cache *fragment_cache, *data_cache;
+ struct queue *to_reader, *to_deflate, *to_writer, *from_writer;
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH 04/05] [tools] squashfs glibc >= 2.23 compat

[Weedy]

With the update to glibc 2.23, sys/types.h doesn't inherit
sys/sysmacros.h anymore. We need to include it manually.

Signed-off-by: Weedy <weedy2...@gmail.com>

--- /dev/null   2016-04-18 05:53:30.273258717 -0400
+++ tools/squashfs/patches/125-glibc-2.23-sysmacros.patch   2016-04-24
16:16:39.524863687 -0400
@@ -0,0 +1,20 @@
+--- a/squashfs-tools/mksquashfs.c  2016-04-24 16:10:19.230996009 -0400
 b/squashfs-tools/mksquashfs.c  2016-04-24 16:10:54.671356457 -0400
+@@ -30,6 +30,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include 
+ #include 
+ #include 
+--- a/squashfs-tools/unsquashfs.c  2016-04-24 16:14:24.310155265 -0400
 b/squashfs-tools/unsquashfs.c  2016-04-24 16:14:46.560381562 -0400
+@@ -25,6 +25,7 @@
+ #define FALSE 0
+ #include 
+ #include 
++#include 
+ #include 
+ #include 
+ #include 
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH 01/05] [tools] e2fsprogs glibc >= 2.23 compat

[Weedy]

With the update to glibc 2.23, sys/types.h doesn't inherit
sys/sysmacros.h anymore. We need to include it manually.

Signed-off-by: Weedy <weedy2...@gmail.com>


--- /dev/null   2016-04-18 05:53:30.273258717 -0400
+++ tools/e2fsprogs/patches/125-glibc-2.23-sysmacros.patch  2016-04-24
14:58:32.704376584 -0400
@@ -0,0 +1,20 @@
+--- a/lib/blkid/devname.c.bak  2016-04-24 14:55:25.665819444 -0400
 b/lib/blkid/devname.c  2016-04-24 14:55:45.589354153 -0400
+@@ -25,6 +25,7 @@
+ #include 
+ #if HAVE_SYS_TYPES_H
+ #include 
++#include 
+ #endif
+ #include 
+ #if HAVE_SYS_STAT_H
+--- a/lib/ext2fs/ext2fs.h.bak  2016-04-24 14:56:14.822982962 -0400
 b/lib/ext2fs/ext2fs.h  2016-04-24 14:56:31.613152667 -0400
+@@ -49,6 +49,7 @@
+
+ #ifdef HAVE_SYS_TYPES_H
+ #include 
++#include 
+ #endif
+
+ #include 
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH 01/??] [tools] make-ext4fs glibc >= 2.23 compat

[Weedy]

On 25 Apr 2016 09:09, "Jo-Philipp Wich"  wrote:
>
> Hi!
>
> Thanks for the patch, I fixed the include issue directly in Git, so this
> patch can be dropped and make-ext4fs should be updated in tools/ to a
> newer version instead.
>
> ~ Jo

Have you fixed all the packages that need this?

Make-ext4fs, e2fsprogs, mtd-utils, findutils, and both the squashfs
packages.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH 01/??] [tools] make-ext4fs glibc >= 2.23 compat

[Weedy]

With the update to glibc 2.23, sys/types.h doesn't inherit
sys/sysmacros.h anymore. We need to include it manually.


--- /dev/null   2016-04-18 05:53:30.273258717 -0400
+++ tools/make-ext4fs/patches/125-glibc-2.23-sysmacros.patch2016-04-24
14:50:33.932873523 -0400
@@ -0,0 +1,10 @@
+--- a/ext4_utils.h 2016-04-24 14:47:50.207888150 -0400
 b/ext4_utils.h 2016-04-24 14:48:11.761438966 -0400
+@@ -30,6 +30,7 @@
+ #include 
+
+ #include 
++#include 
+ #include 
+ #include 
+ #include 


This is a test for my mail client.
Please tell me if I need to change anything.
I have patched the rest of the host packages this update broke.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] undefined reference while building

[Weedy]

On 24 Apr 2016 1:09 pm, "Hauke Mehrtens" <ha...@hauke-m.de> wrote:
>
> > Never mind. After a few more test and fresh git clones it seems I have
> > a more general build failure. Basically any host utill with makedev,
> > major or minor in it is dying. I don't understand why.
> >
> > Is this a gcc 5.x thing? I updated my system recently.
>
> ..
>
> > '/home/weedy/projects/openwrt/build_dir/host/mtd-utils-1.5.2'
> >   CHK include/version.h
> >   LD  mkfs.jffs2
> > mkfs.jffs2.c:944: error: undefined reference to 'major'
> > mkfs.jffs2.c:944: error: undefined reference to 'minor'
> > mkfs.jffs2.c:1263: error: undefined reference to 'minor'
> > mkfs.jffs2.c:1263: error: undefined reference to 'major'
> > mkfs.jffs2.c:1273: error: undefined reference to 'minor'
> > mkfs.jffs2.c:1273: error: undefined reference to 'major'
> > mkfs.jffs2.c:503: error: undefined reference to 'makedev'
> > mkfs.jffs2.c:467: error: undefined reference to 'makedev'
> > mkfs.jffs2.c:510: error: undefined reference to 'makedev'
> > collect2: error: ld returned 1 exit status
> > common.mk:80: recipe for target
>
>
> Hi,
>
> what Linux distribution are you using? What libc are you using?
>
> makedev and co. are some more specific functions, but they should be
> provided by your libc:
> http://man7.org/linux/man-pages/man3/major.3.html
>
> Hauke

Gentoo, glibc 2.23
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] undefined reference while building

[Weedy]

On Sun, Apr 24, 2016 at 3:23 AM, Weedy <weedy2...@gmail.com> wrote:
> I "cat >" a few things into .config and then call defconfig.
> bmon, curl, iperf, etc, little things. I don't even add filesystems.
> My target is CONFIG_TARGET_ar71xx_generic_TLWDR4300.
>
> If I start a clean build with -j1 for a few minutes I can switch the
> -janything later and I'm fine.
> But -j anything right off a distclean breaks.
>
> $ make -j3 V=s
> make[1]: Entering directory '/home/weedy/projects/openwrt'
> make[2]: Entering directory '/home/weedy/projects/openwrt'
> make[2]: Entering directory '/home/weedy/projects/openwrt'
> + mkdir -p 
> /home/weedy/projects/openwrt/staging_dir/target-mips_34kc_musl-1.1.14
> + cd /home/weedy/projects/openwrt/staging_dir/target-mips_34kc_musl-1.1.14
> + mkdir -p bin lib include stamp
> + mkdir -p /home/weedy/projects/openwrt/staging_dir/host
> mkdir -p 
> /home/weedy/projects/openwrt/build_dir/target-mips_34kc_musl-1.1.14/stamp
> + cd /home/weedy/projects/openwrt/staging_dir/host
> + mkdir -p bin lib include stamp
> touch 
> /home/weedy/projects/openwrt/staging_dir/target-mips_34kc_musl-1.1.14/.prepared
> mkdir -p /home/weedy/projects/openwrt/build_dir/host/stamp
> /home/weedy/projects/openwrt/staging_dir/host/include/sys
> install -m0644 /home/weedy/projects/openwrt/tools/include/*.h
> /home/weedy/projects/openwrt/staging_dir/host/include/
> install -m0644 /home/weedy/projects/openwrt/tools/include/sys/*.h
> /home/weedy/projects/openwrt/staging_dir/host/include/sys/
> ln -sf lib /home/weedy/projects/openwrt/staging_dir/host/lib64
> touch /home/weedy/projects/openwrt/staging_dir/host/.prepared
> make[3]: Entering directory '/home/weedy/projects/openwrt/tools/flock'
> rm -rf 
> /home/weedy/projects/openwrt/staging_dir/target-mips_34kc_musl-1.1.14/root-ar71xx
> make[2]: Leaving directory '/home/weedy/projects/openwrt'
> make[3]: Leaving directory '/home/weedy/projects/openwrt/tools/flock'
> make[3]: Entering directory '/home/weedy/projects/openwrt/tools/flock'
> make[3]: Leaving directory '/home/weedy/projects/openwrt/tools/flock'
> make[3]: Entering directory '/home/weedy/projects/openwrt/tools/tar'
> make[3]: Leaving directory '/home/weedy/projects/openwrt/tools/tar'
> make[3]: Entering directory '/home/weedy/projects/openwrt/tools/tar'
> make[3]: Leaving directory '/home/weedy/projects/openwrt/tools/tar'
> make[3]: Entering directory '/home/weedy/projects/openwrt/tools/sstrip'
> make[3]: Entering directory '/home/weedy/projects/openwrt/tools/expat'
> make[3]: Entering directory '/home/weedy/projects/openwrt/tools/patch'
> make[3]: Leaving directory '/home/weedy/projects/openwrt/tools/sstrip'
> make[3]: Entering directory '/home/weedy/projects/openwrt/tools/make-ext4fs'
> make[3]: Leaving directory '/home/weedy/projects/openwrt/tools/patch'
> make[3]: Leaving directory '/home/weedy/projects/openwrt/tools/expat'
> make[3]: Entering directory '/home/weedy/projects/openwrt/tools/patch-image'
> make[3]: Entering directory 
> '/home/weedy/projects/openwrt/tools/firmware-utils'
> make -C /home/weedy/projects/openwrt/build_dir/host/make-ext4fs-2015-12-02
> make_ext4fs STATIC=1
> make[4]: Entering directory
> '/home/weedy/projects/openwrt/build_dir/host/make-ext4fs-2015-12-02'
> cc -o make_ext4fs allocate.o canned_fs_config.o contents.o crc16.o
> ext4fixup.o ext4_sb.o ext4_utils.o extent.o indirect.o
> make_ext4fs_main.o make_ext4fs.o sha1.o uuid.o wipe.o
> libsparse/libsparse.a -Wl,-Bstatic -lz -Wl,-Bdynamic
> contents.o:contents.c:function make_special: error: undefined
> reference to 'major'
> contents.o:contents.c:function make_special: error: undefined
> reference to 'minor'
> collect2: error: ld returned 1 exit status
> Makefile:30: recipe for target 'make_ext4fs' failed
> make[4]: *** [make_ext4fs] Error 1
> make[4]: Leaving directory
> '/home/weedy/projects/openwrt/build_dir/host/make-ext4fs-2015-12-02'
> Makefile:40: recipe for target
> '/home/weedy/projects/openwrt/build_dir/host/make-ext4fs-2015-12-02/.built'
> failed
> make[3]: *** 
> [/home/weedy/projects/openwrt/build_dir/host/make-ext4fs-2015-12-02/.built]
> Error 2
> make[3]: Leaving directory '/home/weedy/projects/openwrt/tools/make-ext4fs'
> tools/Makefile:134: recipe for target 'tools/make-ext4fs/compile' failed
> make[2]: *** [tools/make-ext4fs/compile] Error 2
> make[2]: *** Waiting for unfinished jobs
> make[3]: Leaving directory '/home/weedy/projects/openwrt/tools/patch-image'
> make[3]: Leaving directory '/home/weedy/projects/openwrt/tools/firmware-utils'
> make[2]: Leaving directory '/home/weedy/projects/openwrt'
> tools/Makefile:133: recipe for target
> '/home/weedy/projects/openwrt/staging_dir/target-mips_34kc_musl-1.1.14/stamp/.tools_install_yyn

Re: [OpenWrt-Devel] rsync mirror of download.openwrt.org ?

[Weedy]

On 22 Apr 2016 11:38 am, "Laurent GUERBY"  wrote:
>
> Hi,
>
> Having no news we completed our mirror by using wget for 15.05.1:
>

Lftp is good for this. Or I guess aria2c
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] make -j on ar71xx dies.

[Weedy]

I "cat >" a few things into .config and then call defconfig.
bmon, curl, iperf, etc, little things. I don't even add filesystems.
My target is CONFIG_TARGET_ar71xx_generic_TLWDR4300.

If I start a clean build with -j1 for a few minutes I can switch the
-janything later and I'm fine.
But -j anything right off a distclean breaks.

$ make -j3 V=s
make[1]: Entering directory '/home/weedy/projects/openwrt'
make[2]: Entering directory '/home/weedy/projects/openwrt'
make[2]: Entering directory '/home/weedy/projects/openwrt'
+ mkdir -p /home/weedy/projects/openwrt/staging_dir/target-mips_34kc_musl-1.1.14
+ cd /home/weedy/projects/openwrt/staging_dir/target-mips_34kc_musl-1.1.14
+ mkdir -p bin lib include stamp
+ mkdir -p /home/weedy/projects/openwrt/staging_dir/host
mkdir -p 
/home/weedy/projects/openwrt/build_dir/target-mips_34kc_musl-1.1.14/stamp
+ cd /home/weedy/projects/openwrt/staging_dir/host
+ mkdir -p bin lib include stamp
touch 
/home/weedy/projects/openwrt/staging_dir/target-mips_34kc_musl-1.1.14/.prepared
mkdir -p /home/weedy/projects/openwrt/build_dir/host/stamp
/home/weedy/projects/openwrt/staging_dir/host/include/sys
install -m0644 /home/weedy/projects/openwrt/tools/include/*.h
/home/weedy/projects/openwrt/staging_dir/host/include/
install -m0644 /home/weedy/projects/openwrt/tools/include/sys/*.h
/home/weedy/projects/openwrt/staging_dir/host/include/sys/
ln -sf lib /home/weedy/projects/openwrt/staging_dir/host/lib64
touch /home/weedy/projects/openwrt/staging_dir/host/.prepared
make[3]: Entering directory '/home/weedy/projects/openwrt/tools/flock'
rm -rf 
/home/weedy/projects/openwrt/staging_dir/target-mips_34kc_musl-1.1.14/root-ar71xx
make[2]: Leaving directory '/home/weedy/projects/openwrt'
make[3]: Leaving directory '/home/weedy/projects/openwrt/tools/flock'
make[3]: Entering directory '/home/weedy/projects/openwrt/tools/flock'
make[3]: Leaving directory '/home/weedy/projects/openwrt/tools/flock'
make[3]: Entering directory '/home/weedy/projects/openwrt/tools/tar'
make[3]: Leaving directory '/home/weedy/projects/openwrt/tools/tar'
make[3]: Entering directory '/home/weedy/projects/openwrt/tools/tar'
make[3]: Leaving directory '/home/weedy/projects/openwrt/tools/tar'
make[3]: Entering directory '/home/weedy/projects/openwrt/tools/sstrip'
make[3]: Entering directory '/home/weedy/projects/openwrt/tools/expat'
make[3]: Entering directory '/home/weedy/projects/openwrt/tools/patch'
make[3]: Leaving directory '/home/weedy/projects/openwrt/tools/sstrip'
make[3]: Entering directory '/home/weedy/projects/openwrt/tools/make-ext4fs'
make[3]: Leaving directory '/home/weedy/projects/openwrt/tools/patch'
make[3]: Leaving directory '/home/weedy/projects/openwrt/tools/expat'
make[3]: Entering directory '/home/weedy/projects/openwrt/tools/patch-image'
make[3]: Entering directory '/home/weedy/projects/openwrt/tools/firmware-utils'
make -C /home/weedy/projects/openwrt/build_dir/host/make-ext4fs-2015-12-02
make_ext4fs STATIC=1
make[4]: Entering directory
'/home/weedy/projects/openwrt/build_dir/host/make-ext4fs-2015-12-02'
cc -o make_ext4fs allocate.o canned_fs_config.o contents.o crc16.o
ext4fixup.o ext4_sb.o ext4_utils.o extent.o indirect.o
make_ext4fs_main.o make_ext4fs.o sha1.o uuid.o wipe.o
libsparse/libsparse.a -Wl,-Bstatic -lz -Wl,-Bdynamic
contents.o:contents.c:function make_special: error: undefined
reference to 'major'
contents.o:contents.c:function make_special: error: undefined
reference to 'minor'
collect2: error: ld returned 1 exit status
Makefile:30: recipe for target 'make_ext4fs' failed
make[4]: *** [make_ext4fs] Error 1
make[4]: Leaving directory
'/home/weedy/projects/openwrt/build_dir/host/make-ext4fs-2015-12-02'
Makefile:40: recipe for target
'/home/weedy/projects/openwrt/build_dir/host/make-ext4fs-2015-12-02/.built'
failed
make[3]: *** 
[/home/weedy/projects/openwrt/build_dir/host/make-ext4fs-2015-12-02/.built]
Error 2
make[3]: Leaving directory '/home/weedy/projects/openwrt/tools/make-ext4fs'
tools/Makefile:134: recipe for target 'tools/make-ext4fs/compile' failed
make[2]: *** [tools/make-ext4fs/compile] Error 2
make[2]: *** Waiting for unfinished jobs
make[3]: Leaving directory '/home/weedy/projects/openwrt/tools/patch-image'
make[3]: Leaving directory '/home/weedy/projects/openwrt/tools/firmware-utils'
make[2]: Leaving directory '/home/weedy/projects/openwrt'
tools/Makefile:133: recipe for target
'/home/weedy/projects/openwrt/staging_dir/target-mips_34kc_musl-1.1.14/stamp/.tools_install_yynyynynynyyynynynnyynynnnnyy'
failed
make[1]: *** 
[/home/weedy/projects/openwrt/staging_dir/target-mips_34kc_musl-1.1.14/stamp/.tools_install_yynyynynynyyynynynnyynynnnnyy]
Error 2
make[1]: Leaving directory '/home/weedy/projects/openwrt'
Build failed - please re-run with -j1 to see the real error message
/home/weedy/projects/openwrt/include/toplevel.mk:192: recipe for
target 'world' failed
make: *** [w

Re: [OpenWrt-Devel] Sha256 checksum generation of images: why OpenSSL instead of sha256sum?

[Weedy]

$ openssl dgst -sha256 ubcd535.iso | awk '/^SHA256/ {
gsub(/^SHA256\(/,"",$1); gsub(/\)\=/,"",$1); print $2"  "$1 }'
f4ad684385845a0dfcd944dc6b6a0aa00886a05a7143efafa8403e01fea49849  ubcd535.iso
$ sha256sum ubcd535.iso
f4ad684385845a0dfcd944dc6b6a0aa00886a05a7143efafa8403e01fea49849  ubcd535.iso

It's fairly painless to reformat.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Where init scripts are linked to rc.d?

[Weedy]

On Sat, Feb 27, 2016 at 3:38 AM, Jakub Jančo  wrote:
> On Sat, Feb 27, 2016 at 2:12 AM, alzhao  wrote:
>> Use /etc/init.d/yourscript enable
>>
>> It should be enabled by default, as I know.
> Where do you put this command? I dont want do any tweaks after image is built.

/etc/rc.local
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Introducing "fastpath" - Kernel module for speeding up IP forwarding

[Weedy]

I think it's dead, and I'm sad.
On 6 Mar 2016 4:25 am, "valent.turko...@gmail.com" <
valent.turko...@gmail.com> wrote:

> A long shot, but are there any news from Marvel legal department? Would
> sending them a case of good beer solve this? :)
>
> On Sunday, 27 September 2015, Weedy <weedy2...@gmail.com> wrote:
>
>> Did this die?
>> On 22 Dec 2014 9:06 am, "Tomer Eliyahu" <tomereliya...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> We are software developers, part of Marvell's cellular platform
>>> infrastructure team.
>>>
>>> Our team has been working on a project named "fastpath" for speeding
>>> up IP forwarding in embedded systems.
>>> The initial version (fastpath v1) has already been successfully
>>> deployed in our latest pxa1801 (cellular modem) based products.
>>>
>>> We are in the final stages of fastpath v2 development, which is
>>> completely hardware independent and requires minimal changes in the
>>> generic networking code (the project consists of a kernel module and a
>>> single kernel patch); despite being hardware independent, fastpath v2
>>> already achieved the same level of performance (as fastpath v1) and
>>> even increased stability.
>>>
>>> Our development platform is running openwrt Barrier Breaker (r43694),
>>> so naturally we chose to suggest this to the openwrt development
>>> community first.
>>>
>>> You can find a brief description of our fastpath solution below.
>>>
>>> We are anxious to hear your thoughts/comments and will gladly share the
>>> code.
>>>
>>> Best Regards,
>>>
>>> Ram Marzin r...@marvell.com
>>> Tomer Eliyahu tom...@marvell.com
>>>
>>>
>>> Fastpath in a nutshell
>>> --
>>>
>>> The basic concept of fastpath is to optimize the data-plane while
>>> keeping the control-plane in the generic networking stack.
>>> This is a known concept in the industry which is commonly used in
>>> embedded systems [1], but so far we couldn't find any open source
>>> implementation for it.
>>>
>>> Fast path implements an optimized data-plane, which replaces the
>>> generic data-plane forwarding code for selected connections. The
>>> data-plane implementation includes a straight forward optimized packet
>>> processing engine which handles all the required packet manipulation
>>> for IP forwarding, such as decrement ttl/hop count, checksum
>>> adjustment, MAC header encapsulation and "dummy NAT" (TCP/UDP traffic
>>> which does not carry any L3/L4 information in the packet payload).
>>>
>>> As noted above, the control-plane is handled by the generic networking
>>> stack, with the only exception of learning new connections and marking
>>> the valid ones as fastpath - some connections can't participate in
>>> fastpath, such as any "non-dummy NAT" connections (e.g. FTP control
>>> port), local traffic, and any protocol which is not supported (e.g.
>>> IPv6 extensions, IPSec, IPv4 fragmanted packets, etc.).
>>> Needless to say that ALL non-fastpath connections / protocols will
>>> work as is, i.e. they simply won't go through fastpath.
>>>
>>> As a rule of thumb, it is safe to assume that in most of the cases,
>>> 90% of the data will go through fastpath. In our experiments on
>>> pxa1801, fastpath alone *almost doubled* the performance (both
>>> Throughput and MIPS consumption) for TCP/UDP IPv4/IPv6 forwarding.
>>>
>>> References
>>> [1]
>>> http://www.embedded.com/design/operating-systems/4403058/Accelerating-network-packet-processing-in-Linux
>>> ___
>>> 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

Re: [OpenWrt-Devel] Trac accounts

[Weedy]

On Tue, Feb 2, 2016 at 7:31 AM, Weedy <weedy2...@gmail.com> wrote:
> Am I supposed to make an account to post tickets?
>
> I thought I was supposed to play with things in
> https://dev.openwrt.org/prefs but saving returns a HTTP 400.
>
> Trying to make an account complains my username is taken. Trying to
> reset my password complains my account doesn't exist. What give?
>
> I have old tickets signed with my email so something worked at one point.

Bump
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Trac accounts

[Weedy]

Am I supposed to make an account to post tickets?

I thought I was supposed to play with things in
https://dev.openwrt.org/prefs but saving returns a HTTP 400.

Trying to make an account complains my username is taken. Trying to
reset my password complains my account doesn't exist. What give?

I have old tickets signed with my email so something worked at one point.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] qos-scripts: Add IPv6 support

[Weedy]

~Off topic~

So I'm going to guess this means both of you have qos-scripts running
on current trunk builds?

Have you seen anyone complaining about kernel panic in hfsc? Should I
make a trac ticket?

ar71xx/TLWDR4300
WARNING: CPU: 0 PID: 0 at net/sched/sch_hfsc.c:1429 0x831f5b2c()
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] qos-scripts: Add IPv6 support

[Weedy]

On 22 Jan 2016 07:15, "Felix Fietkau" <n...@openwrt.org> wrote:
>
> On 2016-01-22 13:12, Weedy wrote:
> > ~Off topic~
> >
> > So I'm going to guess this means both of you have qos-scripts running
> > on current trunk builds?
> >
> > Have you seen anyone complaining about kernel panic in hfsc? Should I
> > make a trac ticket?
> >
> > ar71xx/TLWDR4300
> > WARNING: CPU: 0 PID: 0 at net/sched/sch_hfsc.c:1429 0x831f5b2c()
> Can you please test if my recent removal of the txqueuelen override
> makes a difference here?
>
> - Felix

It's running 48424 and I just double checked that I still have the override
in place.

Is the override likely to cause or mask the problem?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] DD: CONFIG_BUSYBOX_DEFAULT_WGET is not set

[Weedy]

On 22 Jan 2016 08:22, "John Clark"  wrote:
>>>
>>> yes, is was dropped with r48386 + 48379
>>> so it *should* be automatically work with wget -> uclient-fetch
>
>
> I have updated to the latest trunk commit where I see your /usr/bin/wget
-> /bin/wget patch.  I have updated the feeds and symlinks to the latest
and greatest.  The packages are currently not configured to build
uclient-fetch by default, so I manually selected it.
>
> My resulting build now has a 112,453 byte /bin/uclient-fetch binary and I
can confirm wget does work.  I guess the only thing left to do is to have
the uclient-fetch binary build by default.
>
> Question: The busybox binary (for me) goes from 366,401 bytes to 300,327
with the removal of wget from it.  Therefore, the uclient-fetch binary
swapout causes a 46,379 byte increase in size. I assume the desire to move
to uclient-fetch from busybox is for the SSL support?  If so, it still does
not support SSL without also building ustream-ssl.
>
> --John

This also seems to have broken ddns-scripts.
Or at least now I need full wget/curl to update dyndns.
___
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

[Weedy]

On Mon, Jan 18, 2016 at 9:39 AM, Nishant Sharma  wrote:
> 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?
>
option disassoc_low_ack1
Adjust this code to trigger higher?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Introducing "fastpath" - Kernel module for speeding up IP forwarding

[Weedy]

Did this die?
On 22 Dec 2014 9:06 am, "Tomer Eliyahu"  wrote:

> Hi,
>
> We are software developers, part of Marvell's cellular platform
> infrastructure team.
>
> Our team has been working on a project named "fastpath" for speeding
> up IP forwarding in embedded systems.
> The initial version (fastpath v1) has already been successfully
> deployed in our latest pxa1801 (cellular modem) based products.
>
> We are in the final stages of fastpath v2 development, which is
> completely hardware independent and requires minimal changes in the
> generic networking code (the project consists of a kernel module and a
> single kernel patch); despite being hardware independent, fastpath v2
> already achieved the same level of performance (as fastpath v1) and
> even increased stability.
>
> Our development platform is running openwrt Barrier Breaker (r43694),
> so naturally we chose to suggest this to the openwrt development
> community first.
>
> You can find a brief description of our fastpath solution below.
>
> We are anxious to hear your thoughts/comments and will gladly share the
> code.
>
> Best Regards,
>
> Ram Marzin r...@marvell.com
> Tomer Eliyahu tom...@marvell.com
>
>
> Fastpath in a nutshell
> --
>
> The basic concept of fastpath is to optimize the data-plane while
> keeping the control-plane in the generic networking stack.
> This is a known concept in the industry which is commonly used in
> embedded systems [1], but so far we couldn't find any open source
> implementation for it.
>
> Fast path implements an optimized data-plane, which replaces the
> generic data-plane forwarding code for selected connections. The
> data-plane implementation includes a straight forward optimized packet
> processing engine which handles all the required packet manipulation
> for IP forwarding, such as decrement ttl/hop count, checksum
> adjustment, MAC header encapsulation and "dummy NAT" (TCP/UDP traffic
> which does not carry any L3/L4 information in the packet payload).
>
> As noted above, the control-plane is handled by the generic networking
> stack, with the only exception of learning new connections and marking
> the valid ones as fastpath - some connections can't participate in
> fastpath, such as any "non-dummy NAT" connections (e.g. FTP control
> port), local traffic, and any protocol which is not supported (e.g.
> IPv6 extensions, IPSec, IPv4 fragmanted packets, etc.).
> Needless to say that ALL non-fastpath connections / protocols will
> work as is, i.e. they simply won't go through fastpath.
>
> As a rule of thumb, it is safe to assume that in most of the cases,
> 90% of the data will go through fastpath. In our experiments on
> pxa1801, fastpath alone *almost doubled* the performance (both
> Throughput and MIPS consumption) for TCP/UDP IPv4/IPv6 forwarding.
>
> References
> [1]
> http://www.embedded.com/design/operating-systems/4403058/Accelerating-network-packet-processing-in-Linux
> ___
> 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

Re: [OpenWrt-Devel] 3-address Wi-Fi bridging (was: Multiple Wi-Fi client/AP interfaces on one radio)

[Weedy]

On 6 Aug 2015 23:15, John kerry kerry9...@gmail.com wrote:

 Hi,


 Could anyone please help me on this to configure the wireless in such a
way that when we connect to wireless WAN the LAN SSID should not change.


 Thanks,

You need 2 physical radios.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Change OpenWrt Wifi default settings

[Weedy]

Is there something wrong with the default rules for your use case?

Your WiFi interfaces are tagged LAN, things should just work.
On 4 Aug 2015 00:07, John kerry kerry9...@gmail.com wrote:

 Hi,

 below is the /etc/config/network and /etc/config/wireless changes.

 */etc/config/network:*
 config interface 'loopback'
 option ifname 'lo'
 option proto 'static'
 option ipaddr '127.0.0.1'
 option netmask '255.0.0.0'

 config interface 'lan'
 option ifname 'eth0.1 eth1'
 option type 'bridge'
 option proto 'static'
 option ipaddr '192.168.1.5'
 option netmask '255.255.255.0'

 config interface 'wan'
 option ifname 'eth0.2'
 option proto 'dhcp'

 config switch
 option name 'eth0'
 option reset '1'
 option enable_vlan '1'

 config switch_vlan
 option device 'eth0'
 option vlan '1'
 option ports '0t 2 3 4 5'

 config switch_vlan
 option device 'eth0'
 option vlan '2'
 option ports '0t 1'

 config switch
 option name 'eth1'
 option reset '1'
 option enable_vlan '1'

 config switch_vlan
 option device 'eth1'
 option vlan '1'
 option ports '0 1 2 3 4 5'



















 */etc/config/wireless:config wifi-device 'wifi0'option type
 'qcawifi'option channel 'auto'option macaddr
 '00:03:7f:42:06:61'option hwmode '11ng'option txpower
 '19'option htmode 'HT20'config wifi-ifaceoption device
 'wifi0'option network 'lan'option mode 'ap'option
 encryption 'psk2'option ssid 'Test_ap_1'option key *
 *'Test_ap_1'*

















 *config wifi-device 'wifi1'option type 'qcawifi'option
 channel 'auto'option macaddr '00:03:7f:42:06:62'option
 hwmode '11na'option txpower '23'option htmode 'HT20'config
 wifi-ifaceoption device 'wifi1'option network 'lan'
 option mode 'ap'option ssid 'Test_ap_2'option encryption
 'psk2'option key 'test_ap_2''*


 *Thanks,*

 On Tue, Aug 4, 2015 at 11:56 AM, David Lang da...@lang.hm wrote:

 can you connect via a wired port?

 given that you've been changing /etc/config/network and
 /etc/config/wireless, could you show us what you ended up with there?

 David Lang


 On Tue, 4 Aug 2015, John kerry wrote:

 Hi,

 I am using ar71xx OpenWrt. I have connected internet connection to WAN
 port
 and my PC to LAN. I have enabled the WiFi0. The LAN port static IP i am
 able to open GUI and even my mobile i connected to Wifi AP and able to
 open
 GUI in mobile. But I am not able to access internet on mobile which is
 connected to wifi0 AP.

 I have added below script under /etc/firewall.user file.
 iptables ...flush
 iptables --table nat --flush
 iptables --delete-chain
 iptables --table nat --delete-chain
 iptables -A FORWARD -j ACCEPT -i br-lan -o eth0.2 -m state --state NEW
 iptables -A FORWARD -m state --state ESTABLISHED,RELATED  -j ACCEPT
 iptables -A POSTROUTING -t nat -o eth0.2 -j MASQUERADE
 echo 1   /proc/sys/net/ipv4/ip_forward

 #where br-lan = LAN
   eth0.2 = WAN

 Could anyone help me to write the proper NAT rules so that able to access
 the internet.

 Thanks,

 On Mon, Aug 3, 2015 at 11:29 AM, John kerry kerry9...@gmail.com wrote:

 Hello Guys,

 It's working. Thanks a lot to all of you :)

 On Mon, Aug 3, 2015 at 10:43 AM, David Lang da...@lang.hm wrote:

 The way to do this is to first forget about the factory reset problem
 and
 configure the AP to do what you want (including any encryption)

 then you can take the resulting file and put it into the build system
 so
 that it becomes the 'factory default' settings.

 Since you are not understanding how to configure the files from the
 documentation, configure them from the GUI and then look at the
 resulting
 files.

 David Lang


 On Mon, 3 Aug 2015, John kerry wrote:

 Hi All,


 I created separate files directory and added network and wireless
 files
 and
 its working everything but still i am not able to use encryption wpa2.
 Below is the my script.
 config wifi-device  wifi0
option type qcawifi
option channel  auto
option macaddr  00:03:7f:42:06:61
option hwmode   11ng
# REMOVE THIS LINE TO ENABLE WIFI:
option disabled 0

 config wifi-iface
option device   wifi0
option network  lan
option mode ap
option ssid CD-1
option encryption psk2
option key  CD-1

 M I doing anything wrong?

 Thanks,

 On Mon, Aug 3, 2015 at 6:40 AM, David Lang da...@lang.hm wrote:

 to make the config be there after a factory reset, you need to put the

 changes into the image that you build.

 you already did this for /etc/config/network, do the same thing for
 /etc/config/wireless

 David Lang


 On Sun, 2 Aug 2015, John kerry wrote:

 Hi Leiten,


 I have one 

Re: [OpenWrt-Devel] Change OpenWrt Wifi default settings

[Weedy]

On 2 Aug 2015 12:19, John kerry kerry9...@gmail.com wrote:

 Hi,

 I am using below uci script,

 vi target/linux/ar71xx/base-files/etc/uci-defaults/99-wireless

If you're building images yourself you might like to use files/ instead.

svn checkout/files/etc/config/wireless

You can dump any file you want in the finished image in there.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Change OpenWrt Wifi default settings

[Weedy]

You seem to be having problems using uci-defaults. So forget that.

Copy the running/working/complete config file from your device into
files/etc/config/wireless.
You need to make the files directory. You can put anything in there.

weedy@HAF ~/projects/openwrt $ ls -al files/etc/config/
total 60
drwxr-xr-x 2 weedy weedy 4096 Jul 13 23:05 .
drwxr-xr-x 8 weedy weedy 4096 Jul 31 00:35 ..
-rw-r--r-- 1 weedy weedy  138 Jul 13 23:05 darkstat
-rw-r--r-- 1 weedy weedy  441 Jul 13 23:05 ddns
-rw-r--r-- 1 weedy weedy 1204 Jul 30 22:48 dhcp
-rw-r--r-- 1 weedy weedy  119 Jul 13 23:05 dropbear
-rw-r--r-- 1 weedy weedy 4290 Jul 13 23:05 firewall
-rw-r--r-- 1 weedy weedy   38 Jun 11  2013 netcheck
-rw-r--r-- 1 weedy weedy 1059 Jul 13 23:05 network
-rw-r--r-- 1 weedy weedy 1821 Jun 30 21:04 qos
-rw-r--r-- 1 weedy weedy  761 Jul 13 23:05 system
-rw-r--r-- 1 weedy weedy 2165 Jul 13 23:05 uhttpd
-rw-r--r-- 1 weedy weedy  639 Jul 13 23:05 upnpd
-rw-r--r-- 1 weedy weedy 1353 Jul 13 23:05 wireless
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Change OpenWrt Wifi default settings

[Weedy]

make

On Sun, Aug 2, 2015 at 12:56 PM, John kerry kerry9...@gmail.com wrote:
 Hi,

 so i created directory as below  and copy the following files

 root@OpenWrt:/# ls -al files/etc/config/
 drwxr-xr-x2 root root 0 Jul 30 18:42 .
 drwxr-xr-x3 root root 0 Jul 30 18:35 ..
 -rw-r--r--1 root root  4045 Jul 30 18:42 ddns
 -rw-r--r--1 root root   885 Jul 30 18:41 dhcp
 -rw-r--r--1 root root  2148 Jul 30 18:41 firewall
 -rw-r--r--1 root root   763 Jul 30 18:41 network
 -rw-r--r--1 root root   646 Jul 30 18:42 upnpd
 -rw-r--r--1 root root   718 Jul 30 18:36 wireless

 but how i will link this into building image.




 2015-08-03 0:38 GMT+08:00 Weedy weedy2...@gmail.com:

 You seem to be having problems using uci-defaults. So forget that.

 Copy the running/working/complete config file from your device into
 files/etc/config/wireless.
 You need to make the files directory. You can put anything in there.

 weedy@HAF ~/projects/openwrt $ ls -al files/etc/config/
 total 60
 drwxr-xr-x 2 weedy weedy 4096 Jul 13 23:05 .
 drwxr-xr-x 8 weedy weedy 4096 Jul 31 00:35 ..
 -rw-r--r-- 1 weedy weedy  138 Jul 13 23:05 darkstat
 -rw-r--r-- 1 weedy weedy  441 Jul 13 23:05 ddns
 -rw-r--r-- 1 weedy weedy 1204 Jul 30 22:48 dhcp
 -rw-r--r-- 1 weedy weedy  119 Jul 13 23:05 dropbear
 -rw-r--r-- 1 weedy weedy 4290 Jul 13 23:05 firewall
 -rw-r--r-- 1 weedy weedy   38 Jun 11  2013 netcheck
 -rw-r--r-- 1 weedy weedy 1059 Jul 13 23:05 network
 -rw-r--r-- 1 weedy weedy 1821 Jun 30 21:04 qos
 -rw-r--r-- 1 weedy weedy  761 Jul 13 23:05 system
 -rw-r--r-- 1 weedy weedy 2165 Jul 13 23:05 uhttpd
 -rw-r--r-- 1 weedy weedy  639 Jul 13 23:05 upnpd
 -rw-r--r-- 1 weedy weedy 1353 Jul 13 23:05 wireless


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Designated Driver

[Weedy]

+1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] OpenWrt release name

[Weedy]

The pun with Designated Driver is too strong.

Besides how did Dark Destroyer get in?
Southern comfort is like the worst boose on the face of the planet
(yes worse then prison boose).
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Why OpenWrt sucks?

[Weedy]

If you think Atheros hates Linux and doesn't contribute to the open source
driver after a few years of experience with OpenWrt you need to go back
to where ever you came from and keep studying.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Introducing fastpath - Kernel module for speeding up IP forwarding

[Weedy]

On Dec 23, 2014 10:02 AM, Tomer Eliyahu tomereliya...@gmail.com wrote:

 Hi,

 Our request for uploading the sources is pending approval from
 Marvell's legal department.

 Best Regards,

 Tomer

Please don't let this die.
Lawyers plea
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] ar8216: phy_init and bug report 18415

[Weedy]

On Jan 26, 2015 1:44 AM, Heiner Kallweit hkallwe...@gmail.com wrote:
 If it worked with a previous version of the driver then you could use
git bisect to find out which change actually introduced
 the problem.

https://dev.openwrt.org/changeset/43332
This was the change, there was a huge fit about it at the time. That
said

I've stepped through the tree and found
https://dev.openwrt.org/changeset/43356

I think something might have been out of sync in my tree (or the image I
flashed, I don't think I did a distclean). I've done a fresh check out into
a new directory and verified I have 43356+ changes in
target/linux/generic/files/drivers/net/phy/ar8216.c

All ports are working fine now. Sorry for the noise.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] ar8216: phy_init and bug report 18415

[Weedy]

On Wed, Dec 17, 2014 at 1:48 PM, Heiner Kallweit hkallwe...@gmail.com wrote:
 Ticket 18415 was closed as it was confirmed that as at least version =43419 
 is ok.
 (I assume 43410 fixed the issue.) Therefore current trunk should be ok.

 However if you want to check further what the actual root cause was:
 - Re-enable the additional reset by reverting 43410
 - Issue there?
 - If yes, check whether inserting a mdiobus_write(bus, i, MII_BMCR, 
 BMCR_ANENABLE);
before mdiobus_write(bus, i, MII_BMCR, BMCR_RESET | BMCR_ANENABLE); in
ar8xxx_phy_init fixes it.

 Heiner


So I'm shitty and I forgot about this.
Today I reapplied 43332 (so my checkout should be virgin), and made a image.
My WAN port broke again. Should I still go back to 43410?
I saw how many commits you have made since then which is why I flashed r44119.

# dmesg |grep Atheros
[0.00] SoC: Atheros AR9344 rev 2
[0.63] switch0: Atheros AR8327 rev. 2 switch registered on ag71xx-mdio.0
[1.30] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:00
[uid=004dd033, driver=Atheros AR8216/AR8236/AR8316]
[1.31] eth0: Atheros AG71xx at 0xb900, irq 4, mode:RGMII
[   11.76] ieee80211 phy0: Atheros AR9340 Rev:2 mem=0xb810, irq=47
[   11.81] ieee80211 phy1: Atheros AR9300 Rev:4 mem=0xb000, irq=40
[   24.82] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 2 is up
[   24.82] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 4 is up
[  423.90] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 3 is up
[  447.90] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 2 is down
[  453.90] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 1 is up


Sun Jan 25 10:49:21 2015 daemon.notice netifd: Interface 'wan' is now down
Sun Jan 25 10:49:21 2015 daemon.notice netifd: Interface 'wan' has
link connectivity loss
Sun Jan 25 10:49:21 2015 daemon.notice netifd: Interface 'modem' is now down
Sun Jan 25 10:49:21 2015 daemon.notice netifd: Interface 'modem' is disabled
Sun Jan 25 10:49:21 2015 daemon.notice netifd: Interface 'modem' is enabled
Sun Jan 25 10:49:21 2015 daemon.notice netifd: Interface 'modem' is
setting up now
Sun Jan 25 10:49:21 2015 daemon.notice netifd: Interface 'modem' is now up
Sun Jan 25 10:49:21 2015 daemon.notice netifd: Interface 'wan' is setting up now
Sun Jan 25 10:49:21 2015 daemon.notice netifd: Interface 'wan' is now up
Sun Jan 25 10:49:21 2015 daemon.notice netifd: Interface 'wan' has
link connectivity
Sun Jan 25 10:49:22 2015 user.notice firewall: Reloading firewall due
to ifup of modem (eth0.2)
Sun Jan 25 10:49:24 2015 user.err syslog: module is already loaded - cls_u32
Sun Jan 25 10:49:24 2015 user.err syslog: module is already loaded - em_u32
Sun Jan 25 10:49:24 2015 user.err syslog: module is already loaded -
act_connmark
Sun Jan 25 10:49:24 2015 user.err syslog: module is already loaded - act_mirred
Sun Jan 25 10:49:24 2015 user.err syslog: module is already loaded - sch_ingress
Sun Jan 25 10:49:24 2015 user.err syslog: module is already loaded - cls_fw
Sun Jan 25 10:49:24 2015 user.err syslog: module is already loaded - sch_hfsc
Sun Jan 25 10:49:25 2015 user.notice firewall: Reloading firewall due
to ifup of wan (eth0.2)
Sun Jan 25 10:49:28 2015 daemon.notice netifd: Interface 'wan' is now down
Sun Jan 25 10:49:30 2015 daemon.notice netifd: Interface 'wan' is setting up now
Sun Jan 25 10:49:30 2015 daemon.notice netifd: Interface 'wan' is now up
Sun Jan 25 10:49:31 2015 user.err syslog: module is already loaded - cls_u32
Sun Jan 25 10:49:31 2015 user.err syslog: module is already loaded - em_u32
Sun Jan 25 10:49:31 2015 user.err syslog: module is already loaded -
act_connmark
Sun Jan 25 10:49:31 2015 user.err syslog: module is already loaded - act_mirred
Sun Jan 25 10:49:31 2015 user.err syslog: module is already loaded - sch_ingress
Sun Jan 25 10:49:31 2015 user.err syslog: module is already loaded - cls_fw
Sun Jan 25 10:49:31 2015 user.err syslog: module is already loaded - sch_hfsc
Sun Jan 25 10:49:32 2015 user.notice firewall: Reloading firewall due
to ifup of wan (eth0.2)
Sun Jan 25 10:49:41 2015 daemon.notice netifd: Interface 'wan' is now down
Sun Jan 25 10:49:43 2015 daemon.notice netifd: Interface 'wan' is setting up now
Sun Jan 25 10:49:43 2015 daemon.notice netifd: Interface 'wan' is now up
Sun Jan 25 10:49:44 2015 user.err syslog: module is already loaded - cls_u32
Sun Jan 25 10:49:44 2015 user.err syslog: module is already loaded - em_u32
Sun Jan 25 10:49:44 2015 user.err syslog: module is already loaded -
act_connmark
Sun Jan 25 10:49:44 2015 user.err syslog: module is already loaded - act_mirred
Sun Jan 25 10:49:44 2015 user.err syslog: module is already loaded - sch_ingress
Sun Jan 25 10:49:44 2015 user.err syslog: module is already loaded - cls_fw
Sun Jan 25 10:49:44 2015 user.err syslog: module is already loaded - sch_hfsc
Sun Jan 25 10:49:44 2015 user.notice firewall: Reloading firewall due
to ifup of wan (eth0.2)
Sun Jan 25 10:49:53 2015 

Re: [OpenWrt-Devel] ar8216: phy_init and bug report 18415

[Weedy]

On Jan 25, 2015 1:06 PM, Heiner Kallweit hkallwe...@gmail.com wrote:

 To me it doesn't look like an issue with the AR8216 driver. All related
output is ok.
 The hardware is quite common and in case of a driver issue I would expect
much more
 people to complain.

 What looks a little strange to me is that there seem to be two interfaces
(modem + wan)
 fiddling with eth0.2

 Heiner

It's an alias.

My modem is 100mbit. I can plug and old 100mbit laptop into it and also
have it not show up. It rebooted with the modem plugged in and port 1
didn't come up until I used a gigabit switch.

Auto-neg is broken. Tomorrow I'll do a new checkout just to be sure. Any
commands you want me to run (switchcfg?) to show you the port status?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] 3.18 kernel timing? (Was Re: Moving to 3.17.x kernel?)

[Weedy]

On Dec 19, 2014 9:45 AM, Marc Nicholas m...@wimoto.com wrote:

 So let me turn my question around: given there seems to be some work on
the 3.18 kernel, is there a timeline for this to go into the development
trunk? :)

 Thx.

Beyond changing the makefile?
https://dev.openwrt.org/browser/trunk/target/linux/ar71xx/Makefile

Kernel version is right at there. You can change it to whatever your
platform has patches for.

https://dev.openwrt.org/browser/trunk/target/linux/ar71xx
https://dev.openwrt.org/browser/trunk/target/linux/brcm47xx

(Awww yes, Ontario bro. Vaughan here)
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] ar8216: phy_init and bug report 18415

[Weedy]

On Nov 28, 2014 3:24 PM, Weedy weedy2...@gmail.com wrote:


 On Nov 28, 2014 5:23 AM, Heiner Kallweit hkallwe...@gmail.com wrote:
  Anybody with a 8216-based device who can test this?

 Me me me, me me.
 4300 currently running trunk with 43332 reverted.
 I am at your service.

Is the current trunk fixed? You never replied after this.

Do I need to keep 43332 reverted to keep autoneg working?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] request for ar7 test hw / 3.14 testing

[Weedy]

U, I've never uses gpg but I feel like your MTC shouldn't be attaching
your private key.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Frequent adsl disconnections with BTHOMEHUBV2B (lantiq xway danube)

[Weedy]

On Dec 5, 2014 5:12 AM, Jaime T enopa...@gmail.com wrote:
 Problem fixed! After hours of trying to diagnose what was going wrong,
 I took a long shot and tried overwriting the openwrt-distributed adsl
 firmware blob (/lib/firmware/ltq-dsl-fw-a-danube.bin) with the
 firmware blob that was originally distributed by BT (the original
 supplier of the Home Hub). Hey presto! My dsl connection has been
 perfect ever since (even though my dsl supplier is _not_ BT!)

 The whole saga is documented here (in case anyone else has the same
 problem and wants to try this solution):
 http://openwrt.ebilan.co.uk/viewtopic.php?f=4t=68

 Many thanks to all who tried to help. With kind regards, Jaime

Are you connected to BTs network? Reseller?

Sounds like BT tuned the firmware for their specific hardware environment
after the generic did not deliver optimal performance.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] ar8216: phy_init and bug report 18415

[Weedy]

On Nov 28, 2014 5:23 AM, Heiner Kallweit hkallwe...@gmail.com wrote:
 Anybody with a 8216-based device who can test this?

Me me me, me me.
4300 currently running trunk with 43332 reverted.
I am at your service.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Autoneg problems with ar8216 on kernel 3.14 (related to ticket 17800)

[Weedy]

On Mon, Nov 24, 2014 at 3:45 AM, Heiner Kallweit hkallwe...@gmail.com wrote:

 On Mon, Nov 24, 2014 at 1:06 AM, Felix Fietkau n...@openwrt.org wrote:

 On 2014-11-23 23:03, Weedy wrote:
 
  On Nov 23, 2014 4:35 PM, Weedy weedy2...@gmail.com
  mailto:weedy2...@gmail.com wrote:
 
 
  On Nov 19, 2014 8:47 AM, John Crispin blo...@openwrt.org
  mailto:blo...@openwrt.org wrote:
  
  
  
   On 19/11/2014 14:44, Weedy wrote:
   
On Oct 30, 2014 5:08 PM, Heiner Kallweit hkallwe...@gmail.com
  mailto:hkallwe...@gmail.com
mailto:hkallwe...@gmail.com mailto:hkallwe...@gmail.com wrote:
   
Am 30.10.2014 um 07:22 schrieb Heiner Kallweit:
 Am 30.10.2014 um 03:36 schrieb Florian Fainelli:
 Le 28/10/2014 11:46, Heiner Kallweit a écrit :
 After a little more thinking about it and looking at the code
 I
basically have two questions:

 1.
 Is it actually needed to exclude certain phy's in
ar8xxx_phy_config_aneg?
 (At least for AR8327 it doesn't get called with an addr != 0
  anyway)
 Else we could remove ar8xxx_phy_config_aneg and directly
 register
genphy_config_aneg as
 callback for autoneg configuration.

 Address 0 is special, since this is a MDIO broadcast address
 that
will usually be handled by switches as write to all front-panel
  ports.


 2.
 Call sequence with regard to ar8216 is:
 ar8216: ar8xxx_phy_probe
 phy: phy_attach_direct
 phy: phy_init_hw
 ar8216: ar8xxx_phy_config_init
 ar8216: ar8xxx_phy_config_aneg

 ar8216 driver handles AR8327/AR8337 different from the other
supported switch types.
 ar8xxx_start incl. more detailed configuration is called from
ar8xxx_phy_probe already.
 For the other switch types it's called from
  ar8xxx_phy_config_init.

 I wonder whether doing detailed configuration in the probe
 stage
might be too early.
 phy_init_hw resets the switch anyway later.
 Doing the detailed setup in ar8xxx_phy_config_init seems to be
more suited however
 there might be good reason why it's handled the way it is.

 I suppose that you could re-advertise auto-negotiation by
 calling
genphy_config_advert() in the config_init routine.

 The actual problem is caused by BMCR_ANENABLE being cleared by
 the
reset in phy_init_hw.
 As far as I can see genphy_config_advert doesn't bring back
  this flag.
 What does genphy_config_aneg mainly do?
   - call genphy_config_advert
   - check if BMCR_ANENABLE is set
   - if it's not, call genphy_restart_aneg
 Therefore, to bring back BMCR_ANENABLE, we have to call
genphy_config_aneg or genphy_restart_aneg.
 genphy_restart_aneg most likely is sufficient, however I don't
 see
that genphy_config_aneg
 can do any harm if being called with addr == 0.
 At least for me it works perfectly fine to call
 genphy_config_aneg
for all addr's.

 Rgds, Heiner



 Rgds,
 Heiner


 Am 27.10.2014 um 22:00 schrieb Heiner Kallweit:
 With two different TPLINK routers (both with a AR8327N
 switch) I
faced the issue that with
 kernel 3.14 certain switch ports used 10MBit/half only.
 Under kernel 3.10 everything was fine and the same ports used
1000MBit/full.

 As the ar8216 driver is the same I had a look at the common
 phy
code in drivers/net/phy.
 In function phy_init_hw in phy_device.c kernel 3.14 resets
 the
phy whilst 3.10 does not.

 The issue turned out to be that when resetting only flag
BMCR_RESET is set, not BMCR_ANENABLE.
 (In ar8216.c always both flags are set when the switch is
 reset)
 Therefore autoneg was not enabled. Also later in the boot
  process
it doesn't get enabled.
 Adding BMCR_ANENABLE solved the problem and now also under
 3.14
all ports use 1000MBit/full.

 However I'm not sure whether it's a poper fix to add
BMCR_ANENABLE in this generic phy function.
 It might not be appropriate for other phy's.

 After resetting the switch later in the boot process
ar8xxx_phy_config_aneg is called with
 phydev-addr being 0.
 In this case the function returns immediately. Otherwise it
  would
call genphy_config_aneg.
 Calling genphy_config_aneg would also solve the problem as it
checks for BMCR_ANENABLE
 being set and sets it if needed.
 I don't know the reason why genphy_config_aneg isn't called
 in
case of addr 0.
 Or is this a typo and the check actually should be addr != 0
 ?

 Rgds, Heiner

   
The following rudimentary patch works fine for me with kernel
  3.14.18 on
TP-LINK TL-WDR4900 (mpc85xx with AR8327Nv4)
TP-LINK TL-WDR4300 ( ar71xx with AR8327Nv2)
   
Apart from using genphy_config_aneg also for addr==0 I replaced
msleep(1000)
with a polling function inspired

Re: [OpenWrt-Devel] Autoneg problems with ar8216 on kernel 3.14 (related to ticket 17800)

[Weedy]

On Nov 24, 2014 8:27 AM, Bastian Bittorf bitt...@bluebottle.com wrote:

 * Weedy weedy2...@gmail.com [24.11.2014 14:14]:

 [deleted ~250 lines fullquote]

 you (and the others too) are experienced users, so please read
 https://www.netmeister.org/news/learn2quote2.html#ss2.8

 bye, bastian

I've been replying from mobile lately.
It's pure laziness on my part, sorry about that.
(Gmail also collapses everything by default so I don't even think about it
anymore)
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Autoneg problems with ar8216 on kernel 3.14 (related to ticket 17800)

[Weedy]

On Nov 19, 2014 8:47 AM, John Crispin blo...@openwrt.org wrote:



 On 19/11/2014 14:44, Weedy wrote:
 
  On Oct 30, 2014 5:08 PM, Heiner Kallweit hkallwe...@gmail.com
  mailto:hkallwe...@gmail.com wrote:
 
  Am 30.10.2014 um 07:22 schrieb Heiner Kallweit:
   Am 30.10.2014 um 03:36 schrieb Florian Fainelli:
   Le 28/10/2014 11:46, Heiner Kallweit a écrit :
   After a little more thinking about it and looking at the code I
  basically have two questions:
  
   1.
   Is it actually needed to exclude certain phy's in
  ar8xxx_phy_config_aneg?
   (At least for AR8327 it doesn't get called with an addr != 0
anyway)
   Else we could remove ar8xxx_phy_config_aneg and directly register
  genphy_config_aneg as
   callback for autoneg configuration.
  
   Address 0 is special, since this is a MDIO broadcast address that
  will usually be handled by switches as write to all front-panel ports.
  
  
   2.
   Call sequence with regard to ar8216 is:
   ar8216: ar8xxx_phy_probe
   phy: phy_attach_direct
   phy: phy_init_hw
   ar8216: ar8xxx_phy_config_init
   ar8216: ar8xxx_phy_config_aneg
  
   ar8216 driver handles AR8327/AR8337 different from the other
  supported switch types.
   ar8xxx_start incl. more detailed configuration is called from
  ar8xxx_phy_probe already.
   For the other switch types it's called from ar8xxx_phy_config_init.
  
   I wonder whether doing detailed configuration in the probe stage
  might be too early.
   phy_init_hw resets the switch anyway later.
   Doing the detailed setup in ar8xxx_phy_config_init seems to be
  more suited however
   there might be good reason why it's handled the way it is.
  
   I suppose that you could re-advertise auto-negotiation by calling
  genphy_config_advert() in the config_init routine.
  
   The actual problem is caused by BMCR_ANENABLE being cleared by the
  reset in phy_init_hw.
   As far as I can see genphy_config_advert doesn't bring back this
flag.
   What does genphy_config_aneg mainly do?
 - call genphy_config_advert
 - check if BMCR_ANENABLE is set
 - if it's not, call genphy_restart_aneg
   Therefore, to bring back BMCR_ANENABLE, we have to call
  genphy_config_aneg or genphy_restart_aneg.
   genphy_restart_aneg most likely is sufficient, however I don't see
  that genphy_config_aneg
   can do any harm if being called with addr == 0.
   At least for me it works perfectly fine to call genphy_config_aneg
  for all addr's.
  
   Rgds, Heiner
  
  
  
   Rgds,
   Heiner
  
  
   Am 27.10.2014 um 22:00 schrieb Heiner Kallweit:
   With two different TPLINK routers (both with a AR8327N switch) I
  faced the issue that with
   kernel 3.14 certain switch ports used 10MBit/half only.
   Under kernel 3.10 everything was fine and the same ports used
  1000MBit/full.
  
   As the ar8216 driver is the same I had a look at the common phy
  code in drivers/net/phy.
   In function phy_init_hw in phy_device.c kernel 3.14 resets the
  phy whilst 3.10 does not.
  
   The issue turned out to be that when resetting only flag
  BMCR_RESET is set, not BMCR_ANENABLE.
   (In ar8216.c always both flags are set when the switch is reset)
   Therefore autoneg was not enabled. Also later in the boot process
  it doesn't get enabled.
   Adding BMCR_ANENABLE solved the problem and now also under 3.14
  all ports use 1000MBit/full.
  
   However I'm not sure whether it's a poper fix to add
  BMCR_ANENABLE in this generic phy function.
   It might not be appropriate for other phy's.
  
   After resetting the switch later in the boot process
  ar8xxx_phy_config_aneg is called with
   phydev-addr being 0.
   In this case the function returns immediately. Otherwise it would
  call genphy_config_aneg.
   Calling genphy_config_aneg would also solve the problem as it
  checks for BMCR_ANENABLE
   being set and sets it if needed.
   I don't know the reason why genphy_config_aneg isn't called in
  case of addr 0.
   Or is this a typo and the check actually should be addr != 0 ?
  
   Rgds, Heiner
  
 
  The following rudimentary patch works fine for me with kernel 3.14.18
on
  TP-LINK TL-WDR4900 (mpc85xx with AR8327Nv4)
  TP-LINK TL-WDR4300 ( ar71xx with AR8327Nv2)
 
  Apart from using genphy_config_aneg also for addr==0 I replaced
  msleep(1000)
  with a polling function inspired by phy_poll_reset in phy_device.c
  On AR8327 the reset actually takes less than 20ms. Sleeping for 1000ms
  seems to be a waste of time.
 
  Little more work would be needed to make it a proper patch:
  - move ar8xxx_phy_poll_reset more to the beginning so that it is
defined
before being used in any _hw_init function
  - replace msleep(1000) also in the other _hw_init functions
  - remove pr_info debug message or make it at least pr_dbg
  - insert some comments
  - use git format-patch output
 
  Rgds, Heiner
 
 
  --- ar8216.c.orig   2014-10-30 21:50:19.999723156 +0100
  +++ ar8216.c2014-10-30 21:42:11.996481099 +0100
  @@ -1591,6 +1591,29 @@
   #endif
 
   static int

Re: [OpenWrt-Devel] Autoneg problems with ar8216 on kernel 3.14 (related to ticket 17800)

[Weedy]

On Nov 23, 2014 4:35 PM, Weedy weedy2...@gmail.com wrote:


 On Nov 19, 2014 8:47 AM, John Crispin blo...@openwrt.org wrote:
 
 
 
  On 19/11/2014 14:44, Weedy wrote:
  
   On Oct 30, 2014 5:08 PM, Heiner Kallweit hkallwe...@gmail.com
   mailto:hkallwe...@gmail.com wrote:
  
   Am 30.10.2014 um 07:22 schrieb Heiner Kallweit:
Am 30.10.2014 um 03:36 schrieb Florian Fainelli:
Le 28/10/2014 11:46, Heiner Kallweit a écrit :
After a little more thinking about it and looking at the code I
   basically have two questions:
   
1.
Is it actually needed to exclude certain phy's in
   ar8xxx_phy_config_aneg?
(At least for AR8327 it doesn't get called with an addr != 0
anyway)
Else we could remove ar8xxx_phy_config_aneg and directly register
   genphy_config_aneg as
callback for autoneg configuration.
   
Address 0 is special, since this is a MDIO broadcast address that
   will usually be handled by switches as write to all front-panel
ports.
   
   
2.
Call sequence with regard to ar8216 is:
ar8216: ar8xxx_phy_probe
phy: phy_attach_direct
phy: phy_init_hw
ar8216: ar8xxx_phy_config_init
ar8216: ar8xxx_phy_config_aneg
   
ar8216 driver handles AR8327/AR8337 different from the other
   supported switch types.
ar8xxx_start incl. more detailed configuration is called from
   ar8xxx_phy_probe already.
For the other switch types it's called from
ar8xxx_phy_config_init.
   
I wonder whether doing detailed configuration in the probe stage
   might be too early.
phy_init_hw resets the switch anyway later.
Doing the detailed setup in ar8xxx_phy_config_init seems to be
   more suited however
there might be good reason why it's handled the way it is.
   
I suppose that you could re-advertise auto-negotiation by calling
   genphy_config_advert() in the config_init routine.
   
The actual problem is caused by BMCR_ANENABLE being cleared by the
   reset in phy_init_hw.
As far as I can see genphy_config_advert doesn't bring back this
flag.
What does genphy_config_aneg mainly do?
  - call genphy_config_advert
  - check if BMCR_ANENABLE is set
  - if it's not, call genphy_restart_aneg
Therefore, to bring back BMCR_ANENABLE, we have to call
   genphy_config_aneg or genphy_restart_aneg.
genphy_restart_aneg most likely is sufficient, however I don't see
   that genphy_config_aneg
can do any harm if being called with addr == 0.
At least for me it works perfectly fine to call genphy_config_aneg
   for all addr's.
   
Rgds, Heiner
   
   
   
Rgds,
Heiner
   
   
Am 27.10.2014 um 22:00 schrieb Heiner Kallweit:
With two different TPLINK routers (both with a AR8327N switch) I
   faced the issue that with
kernel 3.14 certain switch ports used 10MBit/half only.
Under kernel 3.10 everything was fine and the same ports used
   1000MBit/full.
   
As the ar8216 driver is the same I had a look at the common phy
   code in drivers/net/phy.
In function phy_init_hw in phy_device.c kernel 3.14 resets the
   phy whilst 3.10 does not.
   
The issue turned out to be that when resetting only flag
   BMCR_RESET is set, not BMCR_ANENABLE.
(In ar8216.c always both flags are set when the switch is reset)
Therefore autoneg was not enabled. Also later in the boot
process
   it doesn't get enabled.
Adding BMCR_ANENABLE solved the problem and now also under 3.14
   all ports use 1000MBit/full.
   
However I'm not sure whether it's a poper fix to add
   BMCR_ANENABLE in this generic phy function.
It might not be appropriate for other phy's.
   
After resetting the switch later in the boot process
   ar8xxx_phy_config_aneg is called with
phydev-addr being 0.
In this case the function returns immediately. Otherwise it
would
   call genphy_config_aneg.
Calling genphy_config_aneg would also solve the problem as it
   checks for BMCR_ANENABLE
being set and sets it if needed.
I don't know the reason why genphy_config_aneg isn't called in
   case of addr 0.
Or is this a typo and the check actually should be addr != 0 ?
   
Rgds, Heiner
   
  
   The following rudimentary patch works fine for me with kernel
3.14.18 on
   TP-LINK TL-WDR4900 (mpc85xx with AR8327Nv4)
   TP-LINK TL-WDR4300 ( ar71xx with AR8327Nv2)
  
   Apart from using genphy_config_aneg also for addr==0 I replaced
   msleep(1000)
   with a polling function inspired by phy_poll_reset in phy_device.c
   On AR8327 the reset actually takes less than 20ms. Sleeping for
1000ms
   seems to be a waste of time.
  
   Little more work would be needed to make it a proper patch:
   - move ar8xxx_phy_poll_reset more to the beginning so that it is
defined
 before being used in any _hw_init function
   - replace msleep(1000) also in the other _hw_init functions
   - remove pr_info debug message or make it at least pr_dbg
   - insert some comments
   - use git format-patch output
  
   Rgds

Re: [OpenWrt-Devel] Autoneg problems with ar8216 on kernel 3.14 (related to ticket 17800)

[Weedy]

On Oct 30, 2014 5:08 PM, Heiner Kallweit hkallwe...@gmail.com wrote:

 Am 30.10.2014 um 07:22 schrieb Heiner Kallweit:
  Am 30.10.2014 um 03:36 schrieb Florian Fainelli:
  Le 28/10/2014 11:46, Heiner Kallweit a écrit :
  After a little more thinking about it and looking at the code I
basically have two questions:
 
  1.
  Is it actually needed to exclude certain phy's in
ar8xxx_phy_config_aneg?
  (At least for AR8327 it doesn't get called with an addr != 0 anyway)
  Else we could remove ar8xxx_phy_config_aneg and directly register
genphy_config_aneg as
  callback for autoneg configuration.
 
  Address 0 is special, since this is a MDIO broadcast address that will
usually be handled by switches as write to all front-panel ports.
 
 
  2.
  Call sequence with regard to ar8216 is:
  ar8216: ar8xxx_phy_probe
  phy: phy_attach_direct
  phy: phy_init_hw
  ar8216: ar8xxx_phy_config_init
  ar8216: ar8xxx_phy_config_aneg
 
  ar8216 driver handles AR8327/AR8337 different from the other
supported switch types.
  ar8xxx_start incl. more detailed configuration is called from
ar8xxx_phy_probe already.
  For the other switch types it's called from ar8xxx_phy_config_init.
 
  I wonder whether doing detailed configuration in the probe stage
might be too early.
  phy_init_hw resets the switch anyway later.
  Doing the detailed setup in ar8xxx_phy_config_init seems to be more
suited however
  there might be good reason why it's handled the way it is.
 
  I suppose that you could re-advertise auto-negotiation by calling
genphy_config_advert() in the config_init routine.
 
  The actual problem is caused by BMCR_ANENABLE being cleared by the
reset in phy_init_hw.
  As far as I can see genphy_config_advert doesn't bring back this flag.
  What does genphy_config_aneg mainly do?
- call genphy_config_advert
- check if BMCR_ANENABLE is set
- if it's not, call genphy_restart_aneg
  Therefore, to bring back BMCR_ANENABLE, we have to call
genphy_config_aneg or genphy_restart_aneg.
  genphy_restart_aneg most likely is sufficient, however I don't see that
genphy_config_aneg
  can do any harm if being called with addr == 0.
  At least for me it works perfectly fine to call genphy_config_aneg for
all addr's.
 
  Rgds, Heiner
 
 
 
  Rgds,
  Heiner
 
 
  Am 27.10.2014 um 22:00 schrieb Heiner Kallweit:
  With two different TPLINK routers (both with a AR8327N switch) I
faced the issue that with
  kernel 3.14 certain switch ports used 10MBit/half only.
  Under kernel 3.10 everything was fine and the same ports used
1000MBit/full.
 
  As the ar8216 driver is the same I had a look at the common phy code
in drivers/net/phy.
  In function phy_init_hw in phy_device.c kernel 3.14 resets the phy
whilst 3.10 does not.
 
  The issue turned out to be that when resetting only flag BMCR_RESET
is set, not BMCR_ANENABLE.
  (In ar8216.c always both flags are set when the switch is reset)
  Therefore autoneg was not enabled. Also later in the boot process it
doesn't get enabled.
  Adding BMCR_ANENABLE solved the problem and now also under 3.14 all
ports use 1000MBit/full.
 
  However I'm not sure whether it's a poper fix to add BMCR_ANENABLE
in this generic phy function.
  It might not be appropriate for other phy's.
 
  After resetting the switch later in the boot process
ar8xxx_phy_config_aneg is called with
  phydev-addr being 0.
  In this case the function returns immediately. Otherwise it would
call genphy_config_aneg.
  Calling genphy_config_aneg would also solve the problem as it checks
for BMCR_ANENABLE
  being set and sets it if needed.
  I don't know the reason why genphy_config_aneg isn't called in case
of addr 0.
  Or is this a typo and the check actually should be addr != 0 ?
 
  Rgds, Heiner
 

 The following rudimentary patch works fine for me with kernel 3.14.18 on
 TP-LINK TL-WDR4900 (mpc85xx with AR8327Nv4)
 TP-LINK TL-WDR4300 ( ar71xx with AR8327Nv2)

 Apart from using genphy_config_aneg also for addr==0 I replaced
msleep(1000)
 with a polling function inspired by phy_poll_reset in phy_device.c
 On AR8327 the reset actually takes less than 20ms. Sleeping for 1000ms
 seems to be a waste of time.

 Little more work would be needed to make it a proper patch:
 - move ar8xxx_phy_poll_reset more to the beginning so that it is defined
   before being used in any _hw_init function
 - replace msleep(1000) also in the other _hw_init functions
 - remove pr_info debug message or make it at least pr_dbg
 - insert some comments
 - use git format-patch output

 Rgds, Heiner


 --- ar8216.c.orig   2014-10-30 21:50:19.999723156 +0100
 +++ ar8216.c2014-10-30 21:42:11.996481099 +0100
 @@ -1591,6 +1591,29 @@
  #endif

  static int
 +ar8xxx_phy_poll_reset(struct mii_bus *bus, int num_phys)
 +{
 +   unsigned int sleep_msecs = 20;
 +   int ret, elapsed, i;
 +
 +   for(elapsed = sleep_msecs; elapsed = 600; elapsed +=
sleep_msecs) {
 +   msleep(sleep_msecs);
 +   for (i = 0; i  num_phys; i++) {
 + 

Re: [OpenWrt-Devel] Frequent adsl disconnections with BTHOMEHUBV2B (lantiq xway danube)

[Weedy]

On Nov 17, 2014 12:08 PM, Jaime T enopa...@gmail.com wrote:

 On 16 November 2014 23:47, Weedy weedy2...@gmail.com wrote:
  I had issues in the past with Bell sympatico stingers (made by Ikanos).
They
  had firmware bugs verified by both Bell and Ikanos with anything that
didn't
  run a broadcom DSP. There was nothing I could do except find a decent
bridge
  modem based on a broadcom chipset.

 Thank you for the info. If you don't mind me asking, did you find a
 decent bridge modem based on a broadcom chipset? I'm happy to buy
 something else if I can use it with the bt home hub. I've got a spare
 usb socket and several spare ethernet ports on the home hub if that
 helps.

 Jaime

I don't know if my annex is the same as yours.
SpeedStream 4200, generic firmware
SpeedTouch ST516, generic firmware (play around with versions)
Now I have a SmartNG for VDSL
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Frequent adsl disconnections with BTHOMEHUBV2B (lantiq xway danube)

[Weedy]

Depending on the CO/stinger equipment it might just be your chipset is
incompatible.

I had issues in the past with Bell sympatico stingers (made by Ikanos).
They had firmware bugs verified by both Bell and Ikanos with anything that
didn't run a broadcom DSP. There was nothing I could do except find a
decent bridge modem based on a broadcom chipset.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [Cerowrt-devel] [RFC PATCH] packages: Smart Queue Management for AQM Packet Scheduling and Qos from CeroWrt

[Weedy]

sqm-scripts SQM Scripts
(QoS) (PACKAGE_sqm-scripts) [N/m/y/?] (NEW)

We got accepted?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] WAN bouncing at boot

[Weedy]

On Tue, Aug 12, 2014 at 10:05 AM, Bas Mevissen ab...@basmevissen.nl wrote:


 On 08/09/2014 04:13 AM, Weedy wrote:
 On Sun, Jul 27, 2014 at 3:31 PM, Weedy weedy2...@gmail.com wrote:
 Is there anything I can do to stop this? It started sometime in the
 last 6months of trunk.
 Right after this and couple minutes after boot my healing script fires
 and detects that WAN is broken and calls ifdown; sleep; ifup at which
 point I get an IP and keep it. But why it the WAN goinig up and down
 during boot?


 Difficult to help you without any information about the platform.

 You might go back in time and track down the change that caused the
 issue by bisection. Can take some time to execute, but is feasible when
 the problem is reproducible. Beware that when going back in time with
 the sources, you must force recompilation.

TP-Link 4300 on trunk. It only bounces at boot. I got 5 or 6
distcleans into it and it's just so disruptive. I would be nice to
have a hint.

Thu Oct  2 19:48:33 2014 kern.info kernel: [0.61] switch0:
Atheros AR8327 rev. 2 switch registered on ag71xx-mdio.0
Thu Oct  2 19:48:33 2014 kern.info kernel: [1.84] libphy:
ag71xx_mdio: probed
Thu Oct  2 19:48:33 2014 kern.info kernel: [2.39] ag71xx
ag71xx.0: connected to PHY at ag71xx-mdio.0:00 [uid=004dd033,
driver=Atheros AR8216/AR8236/AR8316]
Thu Oct  2 19:48:33 2014 kern.info kernel: [2.40] eth0:
Atheros AG71xx at 0xb900, irq 4, mode:RGMII
Thu Oct  2 19:48:33 2014 kern.info kernel: [2.41] TCP: cubic registered
Thu Oct  2 19:48:33 2014 kern.info kernel: [2.41] NET:
Registered protocol family 17
Thu Oct  2 19:48:33 2014 kern.info kernel: [2.42] 8021q:
802.1Q VLAN Support v1.8
Thu Oct  2 19:48:33 2014 kern.info kernel: [2.43] VFS: Mounted
root (squashfs filesystem) readonly on device 31:2.
Thu Oct  2 19:48:33 2014 kern.info kernel: [2.44] Freeing
unused kernel memory: 284K (80329000 - 8037)
Thu Oct  2 19:48:33 2014 kern.info kernel: [4.74] usbcore:
registered new interface driver usbfs
Thu Oct  2 19:48:33 2014 kern.info kernel: [4.75] usbcore:
registered new interface driver hub
Thu Oct  2 19:48:33 2014 kern.info kernel: [4.76] usbcore:
registered new device driver usb
Thu Oct  2 19:48:33 2014 kern.info kernel: [4.77] ehci_hcd:
USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Thu Oct  2 19:48:33 2014 kern.info kernel: [4.77]
ehci-platform: EHCI generic platform driver
Thu Oct  2 19:48:33 2014 kern.info kernel: [4.78]
ehci-platform ehci-platform: EHCI Host Controller
Thu Oct  2 19:48:33 2014 kern.info kernel: [4.78]
ehci-platform ehci-platform: new USB bus registered, assigned bus
number 1
Thu Oct  2 19:48:33 2014 kern.info kernel: [4.79]
ehci-platform ehci-platform: irq 3, io mem 0x1b00
Thu Oct  2 19:48:33 2014 kern.info kernel: [4.82]
ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00
Thu Oct  2 19:48:33 2014 kern.info kernel: [4.82] hub 1-0:1.0:
USB hub found
Thu Oct  2 19:48:33 2014 kern.info kernel: [4.83] hub 1-0:1.0:
1 port detected
Thu Oct  2 19:48:33 2014 kern.info kernel: [5.33] usb 1-1: new
high-speed USB device number 2 using ehci-platform
Thu Oct  2 19:48:33 2014 kern.info kernel: [5.48] hub 1-1:1.0:
USB hub found
Thu Oct  2 19:48:33 2014 kern.info kernel: [5.48] hub 1-1:1.0:
4 ports detected
Thu Oct  2 19:48:33 2014 kern.info kernel: [6.41] eth0: link
up (1000Mbps/Full duplex)
Thu Oct  2 19:48:33 2014 kern.info kernel: [8.65] eth0: link down
Thu Oct  2 19:48:33 2014 kern.info kernel: [   10.35] NET:
Registered protocol family 10
Thu Oct  2 19:48:33 2014 kern.info kernel: [   10.37] ip6_tables:
(C) 2000-2006 Netfilter Core Team
Thu Oct  2 19:48:33 2014 kern.info kernel: [   10.41] u32 classifier
Thu Oct  2 19:48:33 2014 kern.info kernel: [   10.41] input
device check on
Thu Oct  2 19:48:33 2014 kern.info kernel: [   10.41] Actions configured
Thu Oct  2 19:48:33 2014 kern.info kernel: [   10.42]
Mirror/redirect action on
Thu Oct  2 19:48:33 2014 kern.info kernel: [   10.44] nf_conntrack
version 0.5.0 (1976 buckets, 7904 max)
Thu Oct  2 19:48:33 2014 kern.info kernel: [   10.47] Loading
modules backported from Linux version master-2014-09-26-0-g25e3efa
Thu Oct  2 19:48:33 2014 kern.info kernel: [   10.47] Backport
generated by backports.git backports-20140905-1-gde42785
Thu Oct  2 19:48:33 2014 kern.info kernel: [   10.49] ip_tables:
(C) 2000-2006 Netfilter Core Team
Thu Oct  2 19:48:33 2014 kern.info kernel: [   10.63] xt_time:
kernel timezone is -
Thu Oct  2 19:48:33 2014 kern.info kernel: [   10.66] cfg80211:
Calling CRDA to update world regulatory domain
Thu Oct  2 19:48:33 2014 kern.info kernel: [   10.66] cfg80211:
World regulatory domain updated:
Thu Oct  2 19:48:33 2014 kern.info kernel: [   10.67] cfg80211:
DFS Master region: unset
Thu Oct  2 19:48:33

Re: [OpenWrt-Devel] [PATCH] [package] dropbear: enable sha2-based hmac by default.

[Weedy]

On 27/09/14 01:29 PM, Alive wrote:
 On 27/09/2014 23:34, Weedy wrote:
 I got bit by this last week when I audited my ssh config and dropped all
 weak/slow ciphers.
 Couldn't log into my routers and had to add md5 ciphers and macs back.

 You must rebuild dropbear package cleanly to test this patch
 
 Save the patch as file located on
 package/network/services/dropbear/patches/600-enable-hmac-sha2.patch,
 relative to OpenWrt source directory. The patch is available here
 http://patchwork.openwrt.org/patch/6322/
 
 Do make clean to clean up the package, and then make to build the
 firmware.
 Flash the resulting firmware and test connecting to dropbear ssh daemon.
 
 To test using hmac-sha2-256, run this command
 ssh -o MACs=hmac-sha2-256 root@OpenWrt
 To test using hmac-sha2-512, run this command
 ssh -o MACs=hmac-sha2-512 root@OpenWrt
 
 For your information, there is almost no difference between message
 authentication algorithm in time needed to establish ssh connection.
 
 I perform the test on my TL-MR3220 (AR9330, mips, dropbear 2014.65,
 r42321). The identity file is cached via ssh-agent. The test commands
 are bellow.
 time ssh -o MACs=hmac-md5 OpenWrt /bin/true
 time ssh -o MACs=hmac-sha1 OpenWrt /bin/true
 time ssh -o MACs=hmac-sha2-256 OpenWrt /bin/true
 time ssh -o MACs=hmac-sha2-512 OpenWrt /bin/true
 
 Here are time needed to establish ssh connection
 +-+--+--+--+--+
 |time\hmac|md5   |   sha1   |  sha256  |  sha512  |
 +-+--+--+--+--+
 | real| 0m3.526s | 0m3.631s | 0m3.519s | 0m3.543s |
 | user| 0m0.015s | 0m0.061s | 0m0.015s | 0m0.031s |
 | sys | 0m0.077s | 0m0.046s | 0m0.093s | 0m0.092s |
 +-+--+--+--+--+
 
 Putty and Bitvise will try connecting using hmac-sha2-256 when
 available, whereas OpenSSH will use hmac-md5 by default.
 
 I hope this information will be a good reason for enabling sha2-based
 hmac on dropbear by default.
 

Based off failed ciphers/macs
no matching cipher found: client rijndael-...@lysator.liu.se server
aes128-ctr,3des-ctr,aes256-ctr,aes128-cbc,3des-cbc,aes256-cbc
no matching mac found: client hmac-ripemd160-...@openssh.com server
hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-md5

for cipher in 3des-cbc 3des-ctr aes128-cbc aes256-cbc aes128-ctr
aes256-ctr; do for mac in hmac-md5 hmac-sha1 hmac-sha2-256
hmac-sha2-512; do echo ; echo cipher: $cipher; echo mac: $mac; for
bah in 1 2 3; do dd if=/dev/zero bs=1M count=25 | ssh -c $cipher -m
$mac -o Compression no r...@openwrt.lan 'time cat - /dev/null';
echo ; sleep 2; done; done; done

OpenSSH_6.6.1 connecting to TP-Link 4300, time to transfer 26MiB of junk
to null. Best of three, my router is in use and not idle.

3des-cbc
+-+--+--+--+--+
|time\hmac|md5   |   sha1   |  sha256  |  sha512  |
+-+--+--+--+--+
| real| 0m27.65s | 0m27.98s | 0m29.47s | 0m31.93s |
| user| 0m 0.05s | 0m 0.04s | 0m 0.02s | 0m 0.04s |
| sys | 0m 0.25s | 0m 0.22s | 0m 0.24s | 0m 0.22s |
+-+--+--+--+--+

aes128-cbc
+-+--+--+--+--+
|time\hmac|md5   |   sha1   |  sha256  |  sha512  |
+-+--+--+--+--+
| real| 0m12.07s | 0m12.62s | 0m13.61s | 0m16.05s |
| user| 0m 0.02s | 0m 0.03s | 0m 0.00s | 0m 0.02s |
| sys | 0m 0.27s | 0m 0.23s | 0m 0.21s | 0m 0.22s |
+-+--+--+--+--+

aes256-cbc
+-+--+--+--+--+
|time\hmac|md5   |   sha1   |  sha256  |  sha512  |
+-+--+--+--+--+
| real| 0m13.32s | 0m13.61s | 0m14.97s | 0m17.71s |
| user| 0m 0.02s | 0m 0.03s | 0m 0.03s | 0m 0.03s |
| sys | 0m 0.27s | 0m 0.23s | 0m 0.22s | 0m 0.28s |
+-+--+--+--+--+

aes128-ctr
+-+--+--+--+--+
|time\hmac|md5   |   sha1   |  sha256  |  sha512  |
+-+--+--+--+--+
| real| 0m12.64s | 0m12.80s | 0m13.74s | 0m16.19s |
| user| 0m 0.04s | 0m 0.02s | 0m 0.02s | 0m 0.01s |
| sys | 0m 0.18s | 0m 0.24s | 0m 0.17s | 0m 0.23s |
+-+--+--+--+--+

aes256-ctr
+-+--+--+--+--+
|time\hmac|md5   |   sha1   |  sha256  |  sha512  |
+-+--+--+--+--+
| real| 0m13.40s | 0m13.84s | 0m15.20s | 0m18.11s |
| user| 0m 0.01s | 0m 0.03s | 0m 0.02s | 0m 0.00s |
| sys | 0m 0.17s | 0m 0.16s | 0m 0.18s | 0m 0.24s |
+-+--+--+--+--+


We should dump 3des-* and pick up arcfour*
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo

Re: [OpenWrt-Devel] [RFC PATCH] packages: Smart Queue Management for AQM Packet Scheduling and Qos from CeroWrt

[Weedy]

On 30/03/14 06:29 PM, Dave Taht wrote:
 On Sun, Mar 30, 2014 at 02:24:44PM -0400, Weedy wrote:
 On Sat, Mar 29, 2014 at 2:56 PM, Dave Täht dave.t...@bufferbloat.netwrote:

 From: Dave Taht dave.t...@bufferbloat.net

 This adds support for the bufferbloat project's Smart Queue Management
 (SQM) system, which improves over openwrt's qos-scripts in the following
 ways

 + Uses HTB with two models for managing traffic
   a simplest one that merely uses fq_codel, and a three tier one that does
   some basic and tunable packet prioritization.

 + Works with ipv6 and ipv4 correctly (unlike qos-scripts)
 + extensive support for fixing ADSL and PPOe framing problems
 + Partial support for key diffserv markings
 + highly tuned fq_codel implementation especially for low bandwidths
 + Tested heavily on cable modems and on dsl devices

 It is a disimprovement in that:

 - There are no built-in tricks for doing l7 classification,
 or other forms of packet inspection.

 - We haven't explored hfsc all that much, prefering to rely
 on the predictable behavior of htb + fq_codel for everything

 - And there is support for a few qdiscs that are not in the linux
 kernel mainline that remain experimental.
 ---
  net/sqm-scripts/Makefile   |   48 +++
  net/sqm-scripts/files/etc/config/sqm   |   11 +
  net/sqm-scripts/files/etc/init.d/sqm   |   23 ++
  net/sqm-scripts/files/usr/lib/sqm/functions.sh |  335
 
  net/sqm-scripts/files/usr/lib/sqm/run.sh   |   67 
  net/sqm-scripts/files/usr/lib/sqm/simple.qos   |  187 +++
  net/sqm-scripts/files/usr/lib/sqm/simple.qos.help  |1 +
  net/sqm-scripts/files/usr/lib/sqm/simplest.qos |   84 +
  .../files/usr/lib/sqm/simplest.qos.help|1 +
  net/sqm-scripts/files/usr/lib/sqm/stop.sh  |   22 ++
  10 files changed, 779 insertions(+)
  create mode 100644 net/sqm-scripts/Makefile
  create mode 100644 net/sqm-scripts/files/etc/config/sqm
  create mode 100755 net/sqm-scripts/files/etc/init.d/sqm
  create mode 100644 net/sqm-scripts/files/usr/lib/sqm/functions.sh
  create mode 100755 net/sqm-scripts/files/usr/lib/sqm/run.sh
  create mode 100755 net/sqm-scripts/files/usr/lib/sqm/simple.qos
  create mode 100644 net/sqm-scripts/files/usr/lib/sqm/simple.qos.help
  create mode 100755 net/sqm-scripts/files/usr/lib/sqm/simplest.qos
  create mode 100644 net/sqm-scripts/files/usr/lib/sqm/simplest.qos.help
  create mode 100755 net/sqm-scripts/files/usr/lib/sqm/stop.sh

 diff --git a/net/sqm-scripts/files/etc/config/sqm
 b/net/sqm-scripts/files/etc/config/sqm
 new file mode 100644
 index 000..547d321
 --- /dev/null
 +++ b/net/sqm-scripts/files/etc/config/sqm
 @@ -0,0 +1,11 @@
 +
 +config queue 'ge00'
 +option enabled '0'
 +option interface 'ge00'
 +option download '2'
 +option upload '4000'
 +option qdisc 'fq_codel'
 +option script 'simple.qos'
 +option qdisc_advanced '0'
 +option linklayer 'none'
 +


 How hard is this to config from the command line/vim?
 
 There are a few more options than this (for DSL compensation, ecn
 and advanced configuration), the above would work if you changed
 enabled to '1' and the device from ge00 to your wan device. (not
 the wan firewall rule, presently. )
 
 It does help to have a sane long term and realistic measurement of your
 network using something like the rrul test rather than the oft-gamed 
 speedtest.
 
 http://www.bufferbloat.net/projects/cerowrt/wiki/Setting_up_SQM_for_CeroWrt_310
 
 You are right, we should fully document all the variables in this file.
 Until recently they were kind of in flux.
 
 I've never needed or really wanted luci on my box, I just use vim. Going by
 this patch, there is either nothing to config or no examples. I would think
 shipping a roughly equivalent config to what ships in qos-scripts would be
 a good start to get people testing.
 
 /etc/init.d/sqm start,stop etc work as expected.
 
 IE: highest priority: small ARP, DNS, and SSH packets
 
 The SQM default is local DNS and ntp. fq_codel automagically optimizes
 for other sparse flows like arp, ssh, mosh, tcp syn, synack, etc,
 no need to do that via classification.
 
 normal: HTTP, HTTPS
 
 So you want to deprioritize vpn, smtp, rsync, dropbox, http on odd ports,
 caching servers, etc, all in favor of the web gods?
 
 we just toss all that into the normal (best effort bin) and let fq_codel
 sort it out.
 
 bulk: everything else.
 
 We do respect the diffserv marking of CS1 (background) and toss it
 into the background queue.
 
 Side note: Will SQM do bandwidth slicing? Or at least handle hostile
 environments better? I say hostile as in roommates or maybe teenage kids.
 Multiple people/devices thinking they are entitled to the entire WAN
 bandwidth at all times.
 
 fq_codel does fair (well, we call it flow) queuing.
 
 https://tools.ietf.org/html/draft-hoeiland-joergensen-aqm-fq-codel

Re: [OpenWrt-Devel] b53: BCM5325 VLAN VID 15 possible?

[Weedy]

On 29 Sep 2014 05:19, Jonas Gorski j...@openwrt.org wrote:

 Hi,

 On Mon, Sep 29, 2014 at 10:43 AM, Ilya Lipnitskiy
 ilya.lipnits...@gmail.com wrote:
  Greetings!
 
  I have been trying to configure a NETGEAR WNDR3400 device to use VLAN
ID 201
  on its WAN port to be able to talk to a Calix FTTH ONT. Studying the
  problem, I have found that the device contains a BCM5325 switch, which
only
  supports up to 16 VLAN entries. However, each entry may have a VID that
is
  12 bits long, ie 0-4095.
 
  It does not seem that the current b53 driver supports this:
 
  From b53_common.c:
  static int b53_port_set_pvid(struct switch_dev *dev, int port, int val)
  {
  ...
  if (val  15  is5325(priv))
  return -EINVAL;
  ...
 
 
  I don't think this is hardware limitation, as people seem to have
gotten it

This is why you don't buy broadcom
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] [package] dropbear: enable sha2-based hmac by default.

[Weedy]

I got bit by this last week when I audited my ssh config and dropped all
weak/slow ciphers.
Couldn't log into my routers and had to add md5 ciphers and macs back.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Missing packages from packages feed on GitHub repository

[Weedy]

On 3 Sep 2014 04:21, Federico Di Marco fede...@gmail.com wrote:

 Well shouldn't there already be assigned a maintaner ?

They were never set in stone.
This is why we started over.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] toolchain size increase - 40MB vs 160MB

[Weedy]

On 25 Aug 2014 15:40, valent.turko...@gmail.com valent.turko...@gmail.com
wrote:

 Hmm, I just noticed that BB RC3 has enormus toolchain file for mips (the
one I use most often) [1] when compared to AA 12.09 toolchain [2]

 40MB vs 160MB

 Should I be worried that something is broken or is this quadruple size
increase planed?


 [1]
http://downloads.openwrt.org/barrier_breaker/14.07-rc3/ar71xx/generic/OpenWrt-Toolchain-ar71xx-for-mips_34kc-gcc-4.8-linaro_uClibc-0.9.33.2.tar.bz2

 [2]
http://downloads.openwrt.org/attitude_adjustment/12.09/ar71xx/generic/OpenWrt-Toolchain-ar71xx-for-mips_r2-gcc-4.6-linaro_uClibc-0.9.33.2.tar.bz2

I'm 90% sure 4.8 is just fat.
It added a bunch of optimization libs and I don't know offhand what OpenWRT
has enabled in the GCC build.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] 6in4 does not recover after wan outage

[Weedy]

On 26 Aug 2014 03:52, Richard Mortimer richm+open...@oldelvet.org.uk
wrote:

 Hi,


 On 23/08/2014 00:19, Weedy wrote:

 On Fri, Aug 22, 2014 at 9:15 AM, Richard Mortimer
 richm+open...@oldelvet.org.uk wrote:

 However I've noticed that if the ADSL line drops then when it recovers
my
 SiXXS 6in4 tunnel does not automatically re-establish the connection.


 Incase you need it fixed now, here's a workaround.
 Throw this in like /etc/hotplug.d/iface/99-6in4-fix.


 Many thanks. I've tested that and it does indeed workaround the problem.

 Best Regards

No problem.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] gigabit router !

[Weedy]

On 29 Aug 2014 15:26, Daniel Petre daniel.pe...@gmail.com wrote:

 Hello,
 is there any OpenWrt compatible gigabit router that can do more than 400
Mbit/s WAN to LAN except linksys wrt1900ac ?
 I know netgear wndr3700/wndr3800 and tp-link wr1043nd do around 380-400
Mbit/s but is there any other hardware more powerful with OpenWrt support?
 Thanks!

If you benched a wr1043nd at 380mbit, the wdr4300 has a faster CPU. Same
with the wdr4900 and wdr7500.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] 6in4 does not recover after wan outage

[Weedy]

On Fri, Aug 22, 2014 at 9:15 AM, Richard Mortimer
richm+open...@oldelvet.org.uk wrote:
 However I've noticed that if the ADSL line drops then when it recovers my
 SiXXS 6in4 tunnel does not automatically re-establish the connection. There
 doesn't seem to be any magic config values to set either in the LUCI
 interface or at
 http://wiki.openwrt.org/doc/uci/network#protocol.6in4.ipv6-in-ipv4.tunnel

 Is this a missing feature or is there a bug lurking somewhere in the new
 event mechanism?


Incase you need it fixed now, here's a workaround.
Throw this in like /etc/hotplug.d/iface/99-6in4-fix.
Not tested, chopped down version of what I run for another reason.
The loop isn't 10 seconds. The failed ping takes about 7 seconds. So
this tests the wan int for about 1m30s.

#!/bin/sh
if [ $ACTION = ifup ]  [ $INTERFACE = wan ]; then
fix6in4 () {
. /lib/functions/network.sh
network_get_device wanIF wan
loop=0
ping=/bin/ping -W 3 -c 5 -q -I $wanIF
until [ $loop -gt 10 ] || $ping 8.8.8.8   /dev/null 21; do
let loop++
sleep 1
done
if [ $loop -lt 11 ]; then ifup wan6
else /usr/bin/logger -t 6in4-fix -p user.notice Failed to
reset 6in4 tunnel.; fi
}
fix6in4 
fi
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] WAN bouncing at boot

[Weedy]

On Sun, Jul 27, 2014 at 3:31 PM, Weedy weedy2...@gmail.com wrote:
 Is there anything I can do to stop this? It started sometime in the
 last 6months of trunk.
 Right after this and couple minutes after boot my healing script fires
 and detects that WAN is broken and calls ifdown; sleep; ifup at which
 point I get an IP and keep it. But why it the WAN goinig up and down
 during boot?

 Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded - cls_u32
 Sun Jul 27 15:08:33 2014 kern.emerg already loaded - cls_u32
 Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded - em_u32
 Sun Jul 27 15:08:33 2014 kern.emerg already loaded - em_u32
 Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded -
 act_connmark
 Sun Jul 27 15:08:33 2014 kern.emerg already loaded - act_connmark
 Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded - 
 act_mirred
 Sun Jul 27 15:08:33 2014 kern.emerg already loaded - act_mirred
 Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded -
 sch_ingress
 Sun Jul 27 15:08:33 2014 kern.emerg already loaded - sch_ingress
 Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded - cls_fw
 Sun Jul 27 15:08:33 2014 kern.emerg already loaded - cls_fw
 Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded - sch_hfsc
 Sun Jul 27 15:08:33 2014 kern.emerg already loaded - sch_hfsc
 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
 Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
 Sun Jul 27 15:08:34 2014 user.emerg syslog: Cannot find device eth0.2
 Sun Jul 27 15:08:34 2014 user.emerg syslog: Cannot find device eth0.2
 Sun Jul 27 15:08:34 2014 user.emerg syslog: Cannot find device eth0.2
 Sun Jul 27 15:08:34 2014 kern.info kernel: [   20.72] IPv6:
 ADDRCONF(NETDEV_UP): eth0: link is not ready
 Sun Jul 27 15:08:34 2014 kern.info kernel: [   20.72] IPv6:
 ADDRCONF(NETDEV_UP): eth0.1: link is not ready
 Sun Jul 27 15:08:34 2014 kern.info kernel: [   20.74] device
 eth0.1 entered promiscuous mode
 Sun Jul 27 15:08:34 2014 kern.info kernel: [   20.74] device eth0
 entered promiscuous mode
 Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'lan' is enabled
 Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'loopback' is enabled
 Sun Jul 27 15:08:34 2014 kern.info kernel: [   20.77] IPv6:
 ADDRCONF(NETDEV_UP): br-lan: link is not ready
 Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'wan' is enabled
 Sun Jul 27 15:08:34 2014 kern.info kernel: [   20.80] IPv6:
 ADDRCONF(NETDEV_UP): eth0.2: link is not ready
 Sun Jul 27 15:08:34 2014 daemon.notice netifd: Network device 'lo' link is up
 Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'loopback'
 has link connectivity
 Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'loopback' is
 setting up now
 Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'loopback' is now up
 Sun Jul 27 15:08:34 2014 kern.info kernel: [   20.88] eth0: link
 up (1000Mbps/Full duplex)
 Sun Jul 27 15:08:34 2014 daemon.notice netifd: Network device 'eth0' link is 
 up
 Sun Jul 27 15:08:34 2014 daemon.notice netifd: VLAN 'eth0.2' link is up
 Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'wan' has
 link connectivity
 Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'wan' is setting up 
 now
 Sun Jul 27 15:08:34 2014 daemon.notice netifd: VLAN 'eth0.1' link is up
 Sun Jul 27 15:08:34 2014 kern.info kernel: [   20.92] IPv6:
 ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
 Sun Jul 27 15:08:35 2014 kern.info kernel: [   20.92] br-lan: port
 1(eth0.1) entered forwarding state
 Sun Jul 27 15:08:35 2014 kern.info kernel: [   20.93] br-lan: port
 1(eth0.1) entered forwarding state
 Sun Jul 27 15:08:35 2014 kern.info kernel: [   20.94] IPv6:
 ADDRCONF(NETDEV_CHANGE): eth0.1: link becomes ready
 Sun Jul 27 15:08

Re: [OpenWrt-Devel] Oops while shutting down WAN

[Weedy]

On Sun, Jul 27, 2014 at 3:34 PM, Weedy weedy2...@gmail.com wrote:
 Something I discovered while dealing with the WAN bouncing problem.
 If you ifdown while pppd is setting up it pukes.

 Sat Jul 26 02:41:52 2014 kern.info kernel: [   23.08] IPv6:
 ADDRCONF(NETDEV_UP): wlan0: link is not ready
 Sat Jul 26 02:41:53 2014 kern.info kernel: [   23.11] device wlan0
 entered promiscuous mode
 Sat Jul 26 02:41:53 2014 kern.info kernel: [   23.11] br-lan: port
 3(wlan0) entered forwarding state
 Sat Jul 26 02:41:53 2014 kern.info kernel: [   23.12] br-lan: port
 3(wlan0) entered forwarding state
 Sat Jul 26 02:41:53 2014 kern.info kernel: [   23.78] eth0: link down
 Sat Jul 26 02:41:53 2014 kern.info kernel: [   23.81] br-lan: port
 3(wlan0) entered disabled state
 Sat Jul 26 02:41:53 2014 kern.info kernel: [   23.81] br-lan: port
 1(eth0.1) entered disabled state
 Sat Jul 26 02:41:53 2014 daemon.notice netifd: Network device 'eth0'
 link is down
 Sat Jul 26 02:41:53 2014 daemon.notice netifd: VLAN 'eth0.2' link is down
 Sat Jul 26 02:41:53 2014 daemon.notice netifd: Interface 'wan' has
 link connectivity loss
 Sat Jul 26 02:41:53 2014 daemon.notice netifd: VLAN 'eth0.1' link is down
 Sat Jul 26 02:41:54 2014 kern.info kernel: [   24.65] eth0: link
 up (1000Mbps/Full duplex)
 Sat Jul 26 02:41:54 2014 kern.info kernel: [   24.65] br-lan: port
 1(eth0.1) entered forwarding state
 Sat Jul 26 02:41:54 2014 kern.info kernel: [   24.66] br-lan: port
 1(eth0.1) entered forwarding state
 Sat Jul 26 02:41:54 2014 daemon.notice netifd: Network device 'eth0' link is 
 up
 Sat Jul 26 02:41:54 2014 daemon.notice netifd: VLAN 'eth0.2' link is up
 Sat Jul 26 02:41:54 2014 daemon.notice netifd: Interface 'wan' has
 link connectivity
 Sat Jul 26 02:41:54 2014 daemon.notice netifd: VLAN 'eth0.1' link is up
 Sat Jul 26 02:41:55 2014 kern.info kernel: [   25.26] br-lan: port
 2(wlan1) entered forwarding state
 Sat Jul 26 02:41:55 2014 kern.info kernel: [   25.26] br-lan: port
 2(wlan1) entered forwarding state
 Sat Jul 26 02:41:55 2014 kern.info kernel: [   25.27] IPv6:
 ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
 Sat Jul 26 02:41:55 2014 kern.info kernel: [   25.30] br-lan: port
 3(wlan0) entered forwarding state
 Sat Jul 26 02:41:55 2014 kern.info kernel: [   25.31] br-lan: port
 3(wlan0) entered forwarding state
 Sat Jul 26 02:41:55 2014 kern.info kernel: [   25.31] IPv6:
 ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
 Sat Jul 26 02:41:55 2014 user.emerg syslog: setting up led USB1
 Sat Jul 26 02:41:55 2014 user.emerg syslog: setting up led USB2
 Sat Jul 26 02:41:55 2014 user.emerg syslog: setting up led WLAN2G
 Sat Jul 26 02:41:55 2014 daemon.notice netifd: Network device 'wlan1' link is 
 up
 Sat Jul 26 02:41:55 2014 daemon.notice netifd: Network device 'wlan0' link is 
 up
 Sat Jul 26 02:41:56 2014 user.emerg syslog: - init complete -
 Sat Jul 26 02:41:56 2014 kern.info kernel: [   26.66] br-lan: port
 1(eth0.1) entered forwarding state
 Sat Jul 26 02:41:57 2014 kern.info kernel: [   27.26] br-lan: port
 2(wlan1) entered forwarding state
 Sat Jul 26 02:41:57 2014 kern.info kernel: [   27.31] br-lan: port
 3(wlan0) entered forwarding state
 Sat Jul 26 02:41:58 2014 daemon.info dnsmasq[1696]: started, version
 2.71 cachesize 4096
 Sat Jul 26 02:41:58 2014 daemon.info dnsmasq[1696]: compile time
 options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua
 TFTP no-conntrack no-ipset no-auth no-DNSSEC
 Sat Jul 26 02:41:58 2014 daemon.info dnsmasq-dhcp[1696]: DHCP, IP
 range 192.168.8.150 -- 192.168.8.199, lease time 3h
 Sat Jul 26 02:41:58 2014 daemon.info dnsmasq[1696]: using local
 addresses only for domain lan
 Sat Jul 26 02:41:58 2014 daemon.info dnsmasq[1696]: reading
 /etc/resolv.conf.opendns
 Sat Jul 26 02:41:58 2014 daemon.info dnsmasq[1696]: using local
 addresses only for domain lan
 Sat Jul 26 02:41:58 2014 daemon.info dnsmasq[1696]: using nameserver
 66.163.0.161#53
 Sat Jul 26 02:41:58 2014 daemon.info dnsmasq[1696]: using nameserver
 206.248.154.170#53
 Sat Jul 26 02:41:58 2014 daemon.info dnsmasq[1696]: using nameserver
 206.248.154.22#53
 Sat Jul 26 02:41:58 2014 daemon.info dnsmasq[1696]: using nameserver 
 8.8.4.4#53
 Sat Jul 26 02:41:58 2014 daemon.info dnsmasq[1696]: read /etc/hosts -
 5 addresses
 Sat Jul 26 02:41:58 2014 daemon.info dnsmasq-dhcp[1696]: read
 /etc/ethers - 13 addresses
 Sat Jul 26 02:41:59 2014 user.notice firewall: Reloading firewall due
 to ifup of lan (br-lan)
 Sat Jul 26 02:42:00 2014 user.notice upnp daemon: external interface
 not found, not starting
 Sat Jul 26 02:42:01 2014 cron.info crond[861]: crond: USER root pid
 1857 cmd /bin/sh /etc/netCheck.sh
 Sat Jul 26 02:42:01 2014 daemon.info pppd[1107]: PPP session is 5594
 Sat Jul 26 02:42:01 2014 daemon.warn pppd[1107]: Connected to
 00:90:1a:a3:b7:45 via interface eth0.2
 Sat Jul 26 02:42:01 2014 daemon.info pppd[1107]: Using interface

Re: [OpenWrt-Devel] [PATCH]ramips:support Lenovo AC1200 Wireless router

[Weedy]

On 28 Jul 2014 12:45, John Crispin j...@phrozen.org wrote:

 Hi,

 where is the DTS file ?

 John

Attached to the first mail.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] WAN bouncing at boot

[Weedy]

Is there anything I can do to stop this? It started sometime in the
last 6months of trunk.
Right after this and couple minutes after boot my healing script fires
and detects that WAN is broken and calls ifdown; sleep; ifup at which
point I get an IP and keep it. But why it the WAN goinig up and down
during boot?

Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded - cls_u32
Sun Jul 27 15:08:33 2014 kern.emerg already loaded - cls_u32
Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded - em_u32
Sun Jul 27 15:08:33 2014 kern.emerg already loaded - em_u32
Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded -
act_connmark
Sun Jul 27 15:08:33 2014 kern.emerg already loaded - act_connmark
Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded - act_mirred
Sun Jul 27 15:08:33 2014 kern.emerg already loaded - act_mirred
Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded -
sch_ingress
Sun Jul 27 15:08:33 2014 kern.emerg already loaded - sch_ingress
Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded - cls_fw
Sun Jul 27 15:08:33 2014 kern.emerg already loaded - cls_fw
Sun Jul 27 15:08:33 2014 user.info syslog: module is already loaded - sch_hfsc
Sun Jul 27 15:08:33 2014 kern.emerg already loaded - sch_hfsc
Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
Sun Jul 27 15:08:33 2014 user.emerg syslog: Cannot find device eth0.2
Sun Jul 27 15:08:34 2014 user.emerg syslog: Cannot find device eth0.2
Sun Jul 27 15:08:34 2014 user.emerg syslog: Cannot find device eth0.2
Sun Jul 27 15:08:34 2014 user.emerg syslog: Cannot find device eth0.2
Sun Jul 27 15:08:34 2014 kern.info kernel: [   20.72] IPv6:
ADDRCONF(NETDEV_UP): eth0: link is not ready
Sun Jul 27 15:08:34 2014 kern.info kernel: [   20.72] IPv6:
ADDRCONF(NETDEV_UP): eth0.1: link is not ready
Sun Jul 27 15:08:34 2014 kern.info kernel: [   20.74] device
eth0.1 entered promiscuous mode
Sun Jul 27 15:08:34 2014 kern.info kernel: [   20.74] device eth0
entered promiscuous mode
Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'lan' is enabled
Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'loopback' is enabled
Sun Jul 27 15:08:34 2014 kern.info kernel: [   20.77] IPv6:
ADDRCONF(NETDEV_UP): br-lan: link is not ready
Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'wan' is enabled
Sun Jul 27 15:08:34 2014 kern.info kernel: [   20.80] IPv6:
ADDRCONF(NETDEV_UP): eth0.2: link is not ready
Sun Jul 27 15:08:34 2014 daemon.notice netifd: Network device 'lo' link is up
Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'loopback'
has link connectivity
Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'loopback' is
setting up now
Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'loopback' is now up
Sun Jul 27 15:08:34 2014 kern.info kernel: [   20.88] eth0: link
up (1000Mbps/Full duplex)
Sun Jul 27 15:08:34 2014 daemon.notice netifd: Network device 'eth0' link is up
Sun Jul 27 15:08:34 2014 daemon.notice netifd: VLAN 'eth0.2' link is up
Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'wan' has
link connectivity
Sun Jul 27 15:08:34 2014 daemon.notice netifd: Interface 'wan' is setting up now
Sun Jul 27 15:08:34 2014 daemon.notice netifd: VLAN 'eth0.1' link is up
Sun Jul 27 15:08:34 2014 kern.info kernel: [   20.92] IPv6:
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sun Jul 27 15:08:35 2014 kern.info kernel: [   20.92] br-lan: port
1(eth0.1) entered forwarding state
Sun Jul 27 15:08:35 2014 kern.info kernel: [   20.93] br-lan: port
1(eth0.1) entered forwarding state
Sun Jul 27 15:08:35 2014 kern.info kernel: [   20.94] IPv6:
ADDRCONF(NETDEV_CHANGE): eth0.1: link becomes ready
Sun Jul 27 15:08:35 2014 kern.info kernel: [   20.94] IPv6:
ADDRCONF(NETDEV_CHANGE): eth0.2: link becomes ready
Sun Jul 27 15:08:35 2014 kern.info kernel: [   

[OpenWrt-Devel] Oops while shutting down WAN

[Weedy]

Something I discovered while dealing with the WAN bouncing problem.
If you ifdown while pppd is setting up it pukes.

Sat Jul 26 02:41:52 2014 kern.info kernel: [   23.08] IPv6:
ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sat Jul 26 02:41:53 2014 kern.info kernel: [   23.11] device wlan0
entered promiscuous mode
Sat Jul 26 02:41:53 2014 kern.info kernel: [   23.11] br-lan: port
3(wlan0) entered forwarding state
Sat Jul 26 02:41:53 2014 kern.info kernel: [   23.12] br-lan: port
3(wlan0) entered forwarding state
Sat Jul 26 02:41:53 2014 kern.info kernel: [   23.78] eth0: link down
Sat Jul 26 02:41:53 2014 kern.info kernel: [   23.81] br-lan: port
3(wlan0) entered disabled state
Sat Jul 26 02:41:53 2014 kern.info kernel: [   23.81] br-lan: port
1(eth0.1) entered disabled state
Sat Jul 26 02:41:53 2014 daemon.notice netifd: Network device 'eth0'
link is down
Sat Jul 26 02:41:53 2014 daemon.notice netifd: VLAN 'eth0.2' link is down
Sat Jul 26 02:41:53 2014 daemon.notice netifd: Interface 'wan' has
link connectivity loss
Sat Jul 26 02:41:53 2014 daemon.notice netifd: VLAN 'eth0.1' link is down
Sat Jul 26 02:41:54 2014 kern.info kernel: [   24.65] eth0: link
up (1000Mbps/Full duplex)
Sat Jul 26 02:41:54 2014 kern.info kernel: [   24.65] br-lan: port
1(eth0.1) entered forwarding state
Sat Jul 26 02:41:54 2014 kern.info kernel: [   24.66] br-lan: port
1(eth0.1) entered forwarding state
Sat Jul 26 02:41:54 2014 daemon.notice netifd: Network device 'eth0' link is up
Sat Jul 26 02:41:54 2014 daemon.notice netifd: VLAN 'eth0.2' link is up
Sat Jul 26 02:41:54 2014 daemon.notice netifd: Interface 'wan' has
link connectivity
Sat Jul 26 02:41:54 2014 daemon.notice netifd: VLAN 'eth0.1' link is up
Sat Jul 26 02:41:55 2014 kern.info kernel: [   25.26] br-lan: port
2(wlan1) entered forwarding state
Sat Jul 26 02:41:55 2014 kern.info kernel: [   25.26] br-lan: port
2(wlan1) entered forwarding state
Sat Jul 26 02:41:55 2014 kern.info kernel: [   25.27] IPv6:
ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Sat Jul 26 02:41:55 2014 kern.info kernel: [   25.30] br-lan: port
3(wlan0) entered forwarding state
Sat Jul 26 02:41:55 2014 kern.info kernel: [   25.31] br-lan: port
3(wlan0) entered forwarding state
Sat Jul 26 02:41:55 2014 kern.info kernel: [   25.31] IPv6:
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Sat Jul 26 02:41:55 2014 user.emerg syslog: setting up led USB1
Sat Jul 26 02:41:55 2014 user.emerg syslog: setting up led USB2
Sat Jul 26 02:41:55 2014 user.emerg syslog: setting up led WLAN2G
Sat Jul 26 02:41:55 2014 daemon.notice netifd: Network device 'wlan1' link is up
Sat Jul 26 02:41:55 2014 daemon.notice netifd: Network device 'wlan0' link is up
Sat Jul 26 02:41:56 2014 user.emerg syslog: - init complete -
Sat Jul 26 02:41:56 2014 kern.info kernel: [   26.66] br-lan: port
1(eth0.1) entered forwarding state
Sat Jul 26 02:41:57 2014 kern.info kernel: [   27.26] br-lan: port
2(wlan1) entered forwarding state
Sat Jul 26 02:41:57 2014 kern.info kernel: [   27.31] br-lan: port
3(wlan0) entered forwarding state
Sat Jul 26 02:41:58 2014 daemon.info dnsmasq[1696]: started, version
2.71 cachesize 4096
Sat Jul 26 02:41:58 2014 daemon.info dnsmasq[1696]: compile time
options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua
TFTP no-conntrack no-ipset no-auth no-DNSSEC
Sat Jul 26 02:41:58 2014 daemon.info dnsmasq-dhcp[1696]: DHCP, IP
range 192.168.8.150 -- 192.168.8.199, lease time 3h
Sat Jul 26 02:41:58 2014 daemon.info dnsmasq[1696]: using local
addresses only for domain lan
Sat Jul 26 02:41:58 2014 daemon.info dnsmasq[1696]: reading
/etc/resolv.conf.opendns
Sat Jul 26 02:41:58 2014 daemon.info dnsmasq[1696]: using local
addresses only for domain lan
Sat Jul 26 02:41:58 2014 daemon.info dnsmasq[1696]: using nameserver
66.163.0.161#53
Sat Jul 26 02:41:58 2014 daemon.info dnsmasq[1696]: using nameserver
206.248.154.170#53
Sat Jul 26 02:41:58 2014 daemon.info dnsmasq[1696]: using nameserver
206.248.154.22#53
Sat Jul 26 02:41:58 2014 daemon.info dnsmasq[1696]: using nameserver 8.8.4.4#53
Sat Jul 26 02:41:58 2014 daemon.info dnsmasq[1696]: read /etc/hosts -
5 addresses
Sat Jul 26 02:41:58 2014 daemon.info dnsmasq-dhcp[1696]: read
/etc/ethers - 13 addresses
Sat Jul 26 02:41:59 2014 user.notice firewall: Reloading firewall due
to ifup of lan (br-lan)
Sat Jul 26 02:42:00 2014 user.notice upnp daemon: external interface
not found, not starting
Sat Jul 26 02:42:01 2014 cron.info crond[861]: crond: USER root pid
1857 cmd /bin/sh /etc/netCheck.sh
Sat Jul 26 02:42:01 2014 daemon.info pppd[1107]: PPP session is 5594
Sat Jul 26 02:42:01 2014 daemon.warn pppd[1107]: Connected to
00:90:1a:a3:b7:45 via interface eth0.2
Sat Jul 26 02:42:01 2014 daemon.info pppd[1107]: Using interface pppoe-wan
Sat Jul 26 02:42:01 2014 daemon.notice pppd[1107]: Connect: pppoe-wan
-- eth0.2
Sat Jul 26 02:42:02 2014 daemon.info pppd[1107]: Remote message: lcp
tunnel 

[OpenWrt-Devel] Force delete pppoe-wan

[Weedy]

I had some fun last night during my ISPs maintenance window.
It made my Internet unstable enough that I'm guessing something racy
happened.

How can I force remove/delete the pppoe-wan interface? I managed to get it
stuck twice before the window finished.

Random zombie interface:
pppoe-wan Link encap:Point-to-Point Protocol
  UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
  RX packets:7793 errors:0 dropped:0 overruns:0 frame:0
  TX packets:6541 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:5
  RX bytes:997481 (974.1 KiB)  TX bytes:607374 (593.1 KiB)

I had to reboot after I saw this.
Thu Jul  3 08:09:52 2014 daemon.info pppd[13707]: PPP session is 15745
Thu Jul  3 08:09:52 2014 daemon.warn pppd[13707]: Connected to
00:90:1a:a3:b7:45 via interface eth0.2
Thu Jul  3 08:09:52 2014 daemon.debug pppd[13707]: using channel 482
Thu Jul  3 08:09:52 2014 daemon.err pppd[13707]: Couldn't rename ppp1 to
pppoe-wan
Thu Jul  3 08:09:52 2014 daemon.info pppd[13707]: Exit.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] /var/state/wireless not being updated any more?

[Weedy]

On Wed, Jun 18, 2014 at 5:48 PM, Shankar Unni shankaru...@netscape.net
wrote:

 Thanks for the pointers, all!

 Let me try with this approach.  I'll probably have to build a wrapper
 around it, since it's being probed from within a C user-space program.


If you're in C shouldn't you use json directly with ubus/procd/whatever
it's called now?


 On Jun 16, 2014, at 12:20 PM, Jo-Philipp Wich j...@openwrt.org wrote:

  Hi,
 
  the data is cached upon the first call.
 
  To force a resync, run network_flush_cache.
 
  ~ Jow
 
  ___
  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

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] /var/state/wireless not being updated any more?

[Weedy]

On Thu, Jun 12, 2014 at 8:28 PM, Gui Iribarren g...@altermundi.net wrote:

 On 06/12/2014 09:13 PM, Shankar Unni wrote:
  Ping?
 
  How can I look up the current state of the various wireless interfaces
 using uci now?
 

 http://wiki.openwrt.org/doc/uci/network#determining.linux.interface.names

 The uci state vars are deprecated and not used anymore for network
 related information Quoting jow in the forum[0]
 Use /lib/functions/network.sh:

 source /lib/functions/network.sh

 if network_get_ipaddr addr wan; then
 echo IP is $addr
 fi


Is this cached or refreshed every call?
Can the IP/interface change in between network_get_ calls and I get stale
data?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] hotplug / micro-optimization

[Weedy]

On 5 Jun 2014 04:19, Bastian Bittorf bitt...@bluebottle.com wrote:

 i have a router here with 400 vlan-interfaces.
 i'am still not happy, that an hotplug-event triggers a lot of unneccesary
action.

I wasn't paying attention but what services are you complaining about?

On my router things like dnsmasq, the firewall, miniupnpd, and QoS run
/etc/init.d/whatever enabled as the first line of code.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] hotplug / micro-optimization

[Weedy]

On 5 Jun 2014 04:19, Bastian Bittorf bitt...@bluebottle.com wrote:
 3)
 during bootup or '/etc/init.d/$daemon enable' we build a directory for
 enabled scripts. while we are at it, we can e.g. call 'ifup'/$ACTION if
the
 daemon supports/implements it, otherwise ignore

You mean the symlinks in /etc/rcS/?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] Fix sysntpd to use multiple servers.

[Weedy]

On Wed, May 7, 2014 at 5:46 PM, Ben Kibbey b...@luxsci.net wrote:

 On Wed, May 07, 2014 at 04:28:00PM +0200, Jo-Philipp Wich wrote:
  Hi.
 
  Can you elaborate on this fix?
 
  The current implementation works fine here as well and I cannot spot a
  functional difference with your change.
 
  ~ Jow

 It adds a -p before each server specification. If run with -d you can
 see that the remaining servers arent considered without -p, only the
 first.


Uhh?
~/projects/openwrt  $ grep -C2 peer package/utils/busybox/files/sysntpd
procd_set_param command $PROG -n
[ $enable_server = 1 ]  procd_append_param command -l
for peer in $server; do
procd_append_param command -p $peer
done
procd_set_param respawn

root@OpenWrt:~# ps w|grep ntp
  420 root  1352 Sgrep ntp
 2110 root  1364 S/usr/sbin/ntpd -n -l -p tock.usask.ca -p
tock.utoronto.ca -p tick.usask.ca -p clock.uregina.ca
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] public ssh key

[Weedy]

Your public key goes in /etc/dropbear/authorized_keys.
Show us the logs when drop bear is restarted and when you try to login.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [RFC PATCH] packages: Smart Queue Management for AQM Packet Scheduling and Qos from CeroWrt

[Weedy]

On Sat, Mar 29, 2014 at 2:56 PM, Dave Täht dave.t...@bufferbloat.netwrote:

 From: Dave Taht dave.t...@bufferbloat.net

 This adds support for the bufferbloat project's Smart Queue Management
 (SQM) system, which improves over openwrt's qos-scripts in the following
 ways

 + Uses HTB with two models for managing traffic
   a simplest one that merely uses fq_codel, and a three tier one that does
   some basic and tunable packet prioritization.

 + Works with ipv6 and ipv4 correctly (unlike qos-scripts)
 + extensive support for fixing ADSL and PPOe framing problems
 + Partial support for key diffserv markings
 + highly tuned fq_codel implementation especially for low bandwidths
 + Tested heavily on cable modems and on dsl devices

 It is a disimprovement in that:

 - There are no built-in tricks for doing l7 classification,
 or other forms of packet inspection.

 - We haven't explored hfsc all that much, prefering to rely
 on the predictable behavior of htb + fq_codel for everything

 - And there is support for a few qdiscs that are not in the linux
 kernel mainline that remain experimental.
 ---
  net/sqm-scripts/Makefile   |   48 +++
  net/sqm-scripts/files/etc/config/sqm   |   11 +
  net/sqm-scripts/files/etc/init.d/sqm   |   23 ++
  net/sqm-scripts/files/usr/lib/sqm/functions.sh |  335
 
  net/sqm-scripts/files/usr/lib/sqm/run.sh   |   67 
  net/sqm-scripts/files/usr/lib/sqm/simple.qos   |  187 +++
  net/sqm-scripts/files/usr/lib/sqm/simple.qos.help  |1 +
  net/sqm-scripts/files/usr/lib/sqm/simplest.qos |   84 +
  .../files/usr/lib/sqm/simplest.qos.help|1 +
  net/sqm-scripts/files/usr/lib/sqm/stop.sh  |   22 ++
  10 files changed, 779 insertions(+)
  create mode 100644 net/sqm-scripts/Makefile
  create mode 100644 net/sqm-scripts/files/etc/config/sqm
  create mode 100755 net/sqm-scripts/files/etc/init.d/sqm
  create mode 100644 net/sqm-scripts/files/usr/lib/sqm/functions.sh
  create mode 100755 net/sqm-scripts/files/usr/lib/sqm/run.sh
  create mode 100755 net/sqm-scripts/files/usr/lib/sqm/simple.qos
  create mode 100644 net/sqm-scripts/files/usr/lib/sqm/simple.qos.help
  create mode 100755 net/sqm-scripts/files/usr/lib/sqm/simplest.qos
  create mode 100644 net/sqm-scripts/files/usr/lib/sqm/simplest.qos.help
  create mode 100755 net/sqm-scripts/files/usr/lib/sqm/stop.sh

 diff --git a/net/sqm-scripts/files/etc/config/sqm
 b/net/sqm-scripts/files/etc/config/sqm
 new file mode 100644
 index 000..547d321
 --- /dev/null
 +++ b/net/sqm-scripts/files/etc/config/sqm
 @@ -0,0 +1,11 @@
 +
 +config queue 'ge00'
 +option enabled '0'
 +option interface 'ge00'
 +option download '2'
 +option upload '4000'
 +option qdisc 'fq_codel'
 +option script 'simple.qos'
 +option qdisc_advanced '0'
 +option linklayer 'none'
 +


How hard is this to config from the command line/vim?

I've never needed or really wanted luci on my box, I just use vim. Going by
this patch, there is either nothing to config or no examples. I would think
shipping a roughly equivalent config to what ships in qos-scripts would be
a good start to get people testing.

IE: highest priority: small ARP, DNS, and SSH packets
normal: HTTP, HTTPS
bulk: everything else.

Side note: Will SQM do bandwidth slicing? Or at least handle hostile
environments better? I say hostile as in roommates or maybe teenage kids.
Multiple people/devices thinking they are entitled to the entire WAN
bandwidth at all times.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [v3, 1/4] Add kernel support for Sagemcom F@ST2704V2 ADSL router

[Weedy]

SO GUYS, MERGE PLOX?
On 9 Nov 2013 18:42, Weedy weedy2...@gmail.com wrote:

 On Sat, Nov 9, 2013 at 2:54 PM, David Lang da...@lang.hm wrote:

 That doesn't slow down bitrot of the patches, that just works for one
 person's systems, for not.

 Is there something wrong with this series that is preventing it from
 being merged upstream?

 do you need people to report that they need it to get it review priority?

 do you need reports of it working for people?

 do you need someone to sponsor reviews of it?

 There are a lot of people out there who would like to run OpenWRT on
 their ADSL router (myself included), so I would think that there's interest
 in adding support for these sorts of devices.


 ^ This.
 Pretty much anyone getting upgraded to VDSL in Canada could want this. We
 don't have a real bridge mode with the stock firmware and this is ass.


 David Lang


 On Fri, 8 Nov 2013, Martijn Zilverschoon wrote:

  Well if you need this that badly, you can patch it yourself :)

 Checkout the git repository:
 git clone git://git.openwrt.org/openwrt.git

 download the patches and apply them to the local git repo.
 the command for that is: git apply 'example.patch' (make sure that you
 are in the openwrt directory)
 I think you have to apply 4 patches since this one is 1/4.

 Sorry for the earlier message that was incomplete.

 -Martijn

 2013/11/8 Martijn Zilverschoon thefriedzom...@gmail.com:

 Well if you need this that badly, you can patch it yourself :)

 git clone git://git.openwrt.org/openwrt.git


 2013/11/8 Weedy weedy2...@gmail.com:

 Can this pretty please not die to bitrot?
 I need this merged so badly ;_;


 On Thu, Oct 31, 2013 at 7:33 PM, Marcin Jurkowski marci...@gmail.com
 wrote:


 This adds kernel support support for Sagemcom F@st 2704 wireless ADSL
 router.
 It's a BCM6328-based 802.11n wireless router with USB port and ADSL2+
 modem equipped with 64 MiB RAM and 8 MiB flash.
 ---
  .../brcm63xx/patches-3.10/536-board_fast2704.patch | 133
 +
  1 file changed, 133 insertions(+)
  create mode 100644
 target/linux/brcm63xx/patches-3.10/536-board_fast2704.patch

 diff --git a/target/linux/brcm63xx/patches-3.10/536-board_
 fast2704.patch
 b/target/linux/brcm63xx/patches-3.10/536-board_fast2704.patch
 new file mode 100644
 index 000..db34932
 --- /dev/null
 +++ b/target/linux/brcm63xx/patches-3.10/536-board_fast2704.patch
 @@ -0,0 +1,133 @@
 +--- a/arch/mips/bcm63xx/boards/board_bcm963xx.c
  b/arch/mips/bcm63xx/boards/board_bcm963xx.c
 +@@ -1477,6 +1477,122 @@ static struct board_info __initdata boar
 +   },
 + };
 +
 ++static struct board_info __initdata board_FAST2704V2 = {
 ++  .name   = F@ST2704V2,
 ++  .expected_cpu_id= 0x6328,
 ++
 ++  .has_uart0  = 1,
 ++  .has_pci= 1,
 ++  .has_ohci0  = 1,
 ++  .has_ehci0  = 1,
 ++  .has_usbd   = 1,
 ++
 ++  .has_enetsw = 1,
 ++
 ++  .enetsw = {
 ++  .used_ports = {
 ++  [0] = {
 ++  .used   = 1,
 ++  .phy_id = 1,
 ++  .name   = Port 1,
 ++  },
 ++  [1] = {
 ++  .used   = 1,
 ++  .phy_id = 2,
 ++  .name   = Port 2,
 ++  },
 ++  [2] = {
 ++  .used   = 1,
 ++  .phy_id = 3,
 ++  .name   = Port 3,
 ++  },
 ++  [3] = {
 ++  .used   = 1,
 ++  .phy_id = 4,
 ++  .name   = Port 4,
 ++  },
 ++  },
 ++  },
 ++
 ++  .leds = {
 ++  /* front LEDs */
 ++  {
 ++  .name   =
 F@ST2704V2:green:power,
 ++  .gpio   = 4,
 ++  .active_low = 1,
 ++  .default_trigger= default-on,
 ++  },
 ++  {
 ++  .name   = F@ST2704V2
 :red:power,
 ++  .gpio   = 5,
 ++  .active_low = 1,
 ++  },
 ++  {
 ++  .name   = F@ST2704V2
 :red:inet,
 ++  .gpio   = 2,
 ++  .active_low = 1,
 ++  },
 ++  {
 ++  .name   = F@ST2704V2
 :green:dsl,
 ++  .gpio   = 3,
 ++  .active_low = 1

Re: [OpenWrt-Devel] [PATCH] Fix regression in busybox sysntpd init when specifying more than one ntp server in the config file.

[Weedy]

Please accept this patch.
On 28 Feb 2014 14:16, Vittorio G (VittGam) open...@vittgam.net wrote:

 Hi,

 This patch fixes a regression introduced with r38787.

 Before patching:
 /usr/sbin/ntpd -n -l -p server1 server2 server3 server4

 After patching:
 /usr/sbin/ntpd -n -l -p server1 -p server2 -p server3 -p server4

 Signed-off-by: Vittorio Gambaletta open...@vittgam.net
 ---

 --- a/trunk/package/utils/busybox/files/sysntpd 2013-11-28
 12:28:40.0 +0100
 +++ b/trunk/package/utils/busybox/files/sysntpd 2014-02-28
 19:51:48.957785869 +0100
 @@ -24,7 +24,7 @@
 procd_open_instance
 procd_set_param command $PROG -n
 [ $enable_server = 1 ]  procd_append_param command -l
 -   for peer in $server; do
 +   for peer in $server; do
 procd_append_param command -p $peer
 done
 procd_set_param respawn
 ___
 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

[OpenWrt-Devel] My childhood

[Weedy]

https://www.youtube.com/watch?v=eCCrkN6KwPM#t=230

I'm dying
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] Oolite V1.0 Support

[Weedy]

On Fri, Feb 21, 2014 at 6:53 PM, Lars Boegild Thomsen l...@cow.dk wrote:

 The module I've got is described a bit here:

 http://wiki.openwrt.org/toh/oolite/oolitev1

 Including photos of the exact module.  And I actually thought I ordered
 the V2 but ended up with the V1 :)


Where are you finding these? i keep ending up on alibaba with Minimum
Order Quantity: 1000 Piece/Pieces.

I'm just interested in what they cost.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH 2/2] ar71xx: Fix WD My Net N750 weak signal issue

[Weedy]

On 7 Jan 2014 21:30, Steven Haigh net...@crc.id.au wrote:

 On 8/01/2014 9:20 AM, Felix Kaechele wrote:
  The LNAs need to be enabled by setting their respective GPIO to high
even
  though the original firmware's setting sets them to low on
initialization.
 
  Obviously the LNAs are then later initialized by the driver on the OEM
  firmware. Without this fix the device is mostly deaf.
 
  Signed-off-by: Felix Kaechele hef...@fedoraproject.org
  ---
   target/linux/ar71xx/files/arch/mips/ath79/mach-mynet-n750.c | 4 ++--
   1 file changed, 2 insertions(+), 2 deletions(-)
 
  diff --git
a/target/linux/ar71xx/files/arch/mips/ath79/mach-mynet-n750.c
b/target/linux/ar71xx/files/arch/mips/ath79/mach-mynet-n750.c
  index a44a7e0..737bec2 100644
  --- a/target/linux/ar71xx/files/arch/mips/ath79/mach-mynet-n750.c
  +++ b/target/linux/ar71xx/files/arch/mips/ath79/mach-mynet-n750.c
  @@ -179,10 +179,10 @@ static void __init mynet_n750_setup(void)
 *   board/ar7240/db12x/alpha_gpio.c
 */
gpio_request_one(MYNET_N750_GPIO_EXTERNAL_LNA0,
  -  GPIOF_OUT_INIT_LOW | GPIOF_EXPORT_DIR_FIXED,
  +  GPIOF_OUT_INIT_HIGH | GPIOF_EXPORT_DIR_FIXED,
 External LNA0);
gpio_request_one(MYNET_N750_GPIO_EXTERNAL_LNA1,
  -  GPIOF_OUT_INIT_LOW | GPIOF_EXPORT_DIR_FIXED,
  +  GPIOF_OUT_INIT_HIGH | GPIOF_EXPORT_DIR_FIXED,
 External LNA1);
 
mynet_n750_get_mac(wlan24mac=, tmpmac);
 

 Out of interest, would this also apply to the N600? I have this device
 and I've always thought it was 'deaf' as well

The patch is two lines. Try it and tell us.

 --
 Steven Haigh

 Email: net...@crc.id.au
 Web: https://www.crc.id.au
 Phone: (03) 9001 6090 - 0412 935 897
 Fax: (03) 8338 0299
 ___
 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

Re: [OpenWrt-Devel] [PATCH] Add sysfixtime init script, replacement of luci_fixtime

[Weedy]

I don't see a problem with adding this.
Sane usage case. Sane script. If we default to thirty days even if you turn
it on by accident it won't ware anything out.

I would like to see it take min,h,d,m as increment arguments.
On 2 Jan 2014 04:26, Bastian Bittorf bitt...@bluebottle.com wrote:

 * etienne.champet...@free.fr etienne.champet...@free.fr [02.01.2014
 10:25]:
  When you do a fresh (re)start, openvpn complains because certificate is
 not yet valid.

 so simply set the system-time to the filedate of your cert + X seconds.

 bye, bastian
 ___
 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

Re: [OpenWrt-Devel] HTTPS for binaries

[Weedy]

If this really bothers you, you build from source. And vet the source code
before building images.

This is what I do for my clients.
On 1 Jan 2014 05:24, iyCXLONo mVUTxeyv iycxl...@yandex.com wrote:

 Hello,

 Is it possible to download OpenWrt binaries over HTTPS?  If not, which
 seems to be the case, I want to suggest that HTTPS for downloads is needed.
  The HTTP downloads are at risk of man-in-the-middle attacks.  For
 instance, compromised binaries could be supplied in response to HTTP
 download requests.  Also, downloads could be eavesdropped to learn the
 hardware of a downloader, which increases the risk of the downloader to
 targeted attack.

 If this seems like a paranoid concern, it was reported a few days ago that
 the NSA is building a network of hacked routers across the globe as part of
 its QFIRE program [1].  Given the general state of consumer router
 security, it seems unlikely that intelligence agencies are targeting
 specifically OpenWrt downloads, but we know both that routers are a target
 and that HTTP downloads are a vulnerability, which amounts to a real risk
 for OpenWrt users.

 A Trac ticket from April exists for HTTPS downloads, but it has not gotten
 much attention [2].

 [1] http://cryptome.org/2013/12/appelbaum-30c3.pdf, slide 18
 [2] https://dev.openwrt.org/ticket/13346

 Thanks,
 iyCXLONo
 ___
 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

Re: [OpenWrt-Devel] WNDR3800 wifi and collectd issues - r38991

[Weedy]

On Tue, Dec 3, 2013 at 7:23 PM, Jim Henderson hende...@gmail.com wrote:

 On Wed, 04 Dec 2013 01:00:00 +, Jo-Philipp Wich wrote:

  Hi.
 
  I just built this while trying to resolve an Android connectivity issue
  (I'd been running r37866 previously) on a NetGear WNDR3800, and the new
  build seems somewhat better, but I've noticed a couple of odd things -
  I'm wondering if these are known issues, or if I should submit bugs on
  them.
 
  For the build, I had to manually re-configure busybox to enable
  readlink support - this was disabled by default, and without it my wifi
  wouldn't start at all.
 
  Caused by an outdated .config.

 Thanks - is there something in particular I should look at?  I've tried a
 number of things to preserve my existing config with each update, and
 generally that's worked well for me, but apparently the process isn't
 perfect yet.



https://lists.openwrt.org/pipermail/openwrt-devel/2013-November/022653.html
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Trunk build no /etc/init.d/firewall, uci firewall references

[Weedy]

After using OpenWRT for years with almost 0 issues this is my workflow.

weedy@HAF ~/projects/openwrt $ svn up .  make V=3 package/symlinks
weedy@HAF ~/projects/openwrt $ cat configs/tl-wdr4300-home.config
CONFIG_TARGET_ar71xx=y
CONFIG_TARGET_ar71xx_generic=y
CONFIG_TARGET_ar71xx_generic_TLWDR4300=y
weedy@HAF ~/projects/openwrt $ cat configs/base-no-LUCI.config
CONFIG_PACKAGE_bmon=y
CONFIG_PACKAGE_darkstat=y
CONFIG_PACKAGE_ddns-scripts=y
CONFIG_PACKAGE_iftop=y
CONFIG_PACKAGE_iperf=y
CONFIG_PACKAGE_iptables-mod-conntrack-extra=y
CONFIG_PACKAGE_iwinfo=y
CONFIG_PACKAGE_kmod-ipt-conntrack-extra=y
CONFIG_PACKAGE_miniupnpd=y
CONFIG_PACKAGE_muninlite=y
CONFIG_PACKAGE_qos-scripts=y
CONFIG_PACKAGE_screen=y
CONFIG_PACKAGE_tcpdump=y
CONFIG_PACKAGE_uhttpd=y
CONFIG_PACKAGE_wpad=y
weedy@HAF ~/projects/openwrt $ cp -p configs/tl-wdr4300-home.config .config
weedy@HAF ~/projects/openwrt $ cat configs/base-no-LUCI.config  .config
weedy@HAF ~/projects/openwrt $ make V=99 defconfig  nice -n 15 make V=s
-j2

Forcing deps to be resolved every time I update SVN has removed all well
shit moments from updates.
You can add a make V=99 oldconfig after the package/symlinks if you want
to see changes, but normally skimming over the svn output is enough to keep
on top of things.

Your seed config should be top level changes only. Do not add deps, just
the packages you want in the final image. jow/mbm/nbd have done a very good
job of making the build system resolve deps.

Hope this makes your life easier.

On Mon, Nov 18, 2013 at 7:55 PM, camden lindsay 
camden.lindsay+open...@gmail.com wrote:

 I found this must have been an error on my part.
 I cleared everythign out and re-synced.
 Somehow OpenWrt C Firewall  had been cleared in my .config.

 Sorry for the disturbance.
 Camden


 On Sun, Nov 17, 2013 at 11:24 AM, camden lindsay 
 camden.lindsay+open...@gmail.com wrote:

 Hello-
 Has something changed with options during build required to have the
 firewall scripts in the base image?

 I built an image from trunk this morning to upgrade my router.
 I am not doing anything special in make menuconfig other than setting
 target system and profile.


 But once i do an mtd write of the image, there does not appear to be any
 configuration for the firewall in uci, (/etc/config) nor in startup scripts
 (/etc/init.d)

 root@OpenWrt:/tmp# mtd write -r
 openwrt-ar71xx-generic-wzr-hp-ag300h-squashfs-sysupgrade.bin firmware
 Unlocking firmware ...

 Writing from openwrt-ar71xx-generic-wzr-hp-ag300h-squashfs-sysupgrade.bin
 to firmware ...
 Rebooting ...
 Write failed: Broken pipe
 dylan@BigBox ~ $ telnet 192.168.1.1
 Trying 192.168.1.1...
 Connected to 192.168.1.1.
 Escape character is '^]'.
  === IMPORTANT 
   Use 'passwd' to set your login password
   this will disable telnet and enable SSH
  --


 BusyBox v1.19.4 (2013-11-17 08:55:26 PST) built-in shell (ash)
 Enter 'help' for a list of built-in commands.

   ___ __
  |   |.-.-.-.|  |  |  |..|  |_
  |   -   ||  _  |  -__| ||  |  |  ||   _||   _|
  |___||   __|_|__|__||||__|  ||
   |__| W I R E L E S S   F R E E D O M
  -
  BARRIER BREAKER (Bleeding Edge, r38840)
  -
   * 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
  -
 root@OpenWrt:/# uci show firewall
 uci: Entry not found
 root@OpenWrt:/# uci show | grep firewall
 root@OpenWrt:/#
 root@OpenWrt:/# ls -l /etc/config
 -rw-r--r--1 root root   687 Nov 17  2013 6relayd
 -rw-r--r--1 root root   885 Nov 17  2013 dhcp
 -rw-r--r--1 root root   134 Nov 17  2013 dropbear
 -rw---1 root root   675 Jan  1 00:00 network
 -rw---1 root root   659 Jan  1 00:00 system
 -rw---1 root root   115 Jan  1 00:00 ubootenv
 -rw-r--r--1 root root   884 Jan  1 00:00 wireless
 root@OpenWrt:/#

 root@OpenWrt:/# ls -l /etc/init.d/
 -rwxr-xr-x1 root root  4096 Nov 17  2013 6relayd
 -rwxr-xr-x1 root root  1988 Nov 16  2013 boot
 -rwxr-xr-x1 root root   418 Nov 17  2013 cron
 -rwxr-xr-x1 root root   318 May 14  2013 defconfig
 -rwxr-xr-x1 root root 13151 Nov 17  2013 dnsmasq
 -rwxr-xr-x1 root root   308 May 14  2013 done
 -rwxr-xr-x1 root root  3920 Nov 17  2013 dropbear
 -rwxr-xr-x1 root root  2015 May 14  2013 led
 -rwxr-xr-x1 root root  1389 Nov 17  2013 log
 -rwxr-xr-x1 root root   729 Nov 16  2013 network
 -rwxr-xr-x1 root root

Re: [OpenWrt-Devel] [v3, 1/4] Add kernel support for Sagemcom F@ST2704V2 ADSL router

[Weedy]

On Sat, Nov 9, 2013 at 2:54 PM, David Lang da...@lang.hm wrote:

 That doesn't slow down bitrot of the patches, that just works for one
 person's systems, for not.

 Is there something wrong with this series that is preventing it from being
 merged upstream?

 do you need people to report that they need it to get it review priority?

 do you need reports of it working for people?

 do you need someone to sponsor reviews of it?

 There are a lot of people out there who would like to run OpenWRT on their
 ADSL router (myself included), so I would think that there's interest in
 adding support for these sorts of devices.


^ This.
Pretty much anyone getting upgraded to VDSL in Canada could want this. We
don't have a real bridge mode with the stock firmware and this is ass.


David Lang


 On Fri, 8 Nov 2013, Martijn Zilverschoon wrote:

  Well if you need this that badly, you can patch it yourself :)

 Checkout the git repository:
 git clone git://git.openwrt.org/openwrt.git

 download the patches and apply them to the local git repo.
 the command for that is: git apply 'example.patch' (make sure that you
 are in the openwrt directory)
 I think you have to apply 4 patches since this one is 1/4.

 Sorry for the earlier message that was incomplete.

 -Martijn

 2013/11/8 Martijn Zilverschoon thefriedzom...@gmail.com:

 Well if you need this that badly, you can patch it yourself :)

 git clone git://git.openwrt.org/openwrt.git


 2013/11/8 Weedy weedy2...@gmail.com:

 Can this pretty please not die to bitrot?
 I need this merged so badly ;_;


 On Thu, Oct 31, 2013 at 7:33 PM, Marcin Jurkowski marci...@gmail.com
 wrote:


 This adds kernel support support for Sagemcom F@st 2704 wireless ADSL
 router.
 It's a BCM6328-based 802.11n wireless router with USB port and ADSL2+
 modem equipped with 64 MiB RAM and 8 MiB flash.
 ---
  .../brcm63xx/patches-3.10/536-board_fast2704.patch | 133
 +
  1 file changed, 133 insertions(+)
  create mode 100644
 target/linux/brcm63xx/patches-3.10/536-board_fast2704.patch

 diff --git a/target/linux/brcm63xx/patches-3.10/536-board_
 fast2704.patch
 b/target/linux/brcm63xx/patches-3.10/536-board_fast2704.patch
 new file mode 100644
 index 000..db34932
 --- /dev/null
 +++ b/target/linux/brcm63xx/patches-3.10/536-board_fast2704.patch
 @@ -0,0 +1,133 @@
 +--- a/arch/mips/bcm63xx/boards/board_bcm963xx.c
  b/arch/mips/bcm63xx/boards/board_bcm963xx.c
 +@@ -1477,6 +1477,122 @@ static struct board_info __initdata boar
 +   },
 + };
 +
 ++static struct board_info __initdata board_FAST2704V2 = {
 ++  .name   = F@ST2704V2,
 ++  .expected_cpu_id= 0x6328,
 ++
 ++  .has_uart0  = 1,
 ++  .has_pci= 1,
 ++  .has_ohci0  = 1,
 ++  .has_ehci0  = 1,
 ++  .has_usbd   = 1,
 ++
 ++  .has_enetsw = 1,
 ++
 ++  .enetsw = {
 ++  .used_ports = {
 ++  [0] = {
 ++  .used   = 1,
 ++  .phy_id = 1,
 ++  .name   = Port 1,
 ++  },
 ++  [1] = {
 ++  .used   = 1,
 ++  .phy_id = 2,
 ++  .name   = Port 2,
 ++  },
 ++  [2] = {
 ++  .used   = 1,
 ++  .phy_id = 3,
 ++  .name   = Port 3,
 ++  },
 ++  [3] = {
 ++  .used   = 1,
 ++  .phy_id = 4,
 ++  .name   = Port 4,
 ++  },
 ++  },
 ++  },
 ++
 ++  .leds = {
 ++  /* front LEDs */
 ++  {
 ++  .name   =
 F@ST2704V2:green:power,
 ++  .gpio   = 4,
 ++  .active_low = 1,
 ++  .default_trigger= default-on,
 ++  },
 ++  {
 ++  .name   = F@ST2704V2
 :red:power,
 ++  .gpio   = 5,
 ++  .active_low = 1,
 ++  },
 ++  {
 ++  .name   = F@ST2704V2
 :red:inet,
 ++  .gpio   = 2,
 ++  .active_low = 1,
 ++  },
 ++  {
 ++  .name   = F@ST2704V2
 :green:dsl,
 ++  .gpio   = 3,
 ++  .active_low = 1,
 ++  },
 ++  {
 ++  .name   = F@ST2704V2
 :green:inet

Re: [OpenWrt-Devel] Newbie needs help in building stable for newer hardware

[Weedy]

On Sat, Nov 9, 2013 at 6:31 AM, Florian Effenberger flo...@gmail.comwrote:

 Hello,

 2013/11/8 Weedy weedy2...@gmail.com:

  Just use trunk. I update my 4300 once a week to HEAD. I I've had zero
  problems.

 what is your experience with configuration files? I haven't tested
 yet, but I am a bit afraid that my current configuration and
 user-defined scripts might not work anymore, as trunk is usually
 changing some internals over the time...


ehh, I guess needed to add ubus call network reload before ifup.
That was about it.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [v3, 1/4] Add kernel support for Sagemcom F@ST2704V2 ADSL router

[Weedy]

Can this pretty please not die to bitrot?
I need this merged so badly ;_;


On Thu, Oct 31, 2013 at 7:33 PM, Marcin Jurkowski marci...@gmail.comwrote:

 This adds kernel support support for Sagemcom F@st 2704 wireless ADSL
 router.
 It's a BCM6328-based 802.11n wireless router with USB port and ADSL2+
 modem equipped with 64 MiB RAM and 8 MiB flash.
 ---
  .../brcm63xx/patches-3.10/536-board_fast2704.patch | 133
 +
  1 file changed, 133 insertions(+)
  create mode 100644
 target/linux/brcm63xx/patches-3.10/536-board_fast2704.patch

 diff --git a/target/linux/brcm63xx/patches-3.10/536-board_fast2704.patch
 b/target/linux/brcm63xx/patches-3.10/536-board_fast2704.patch
 new file mode 100644
 index 000..db34932
 --- /dev/null
 +++ b/target/linux/brcm63xx/patches-3.10/536-board_fast2704.patch
 @@ -0,0 +1,133 @@
 +--- a/arch/mips/bcm63xx/boards/board_bcm963xx.c
  b/arch/mips/bcm63xx/boards/board_bcm963xx.c
 +@@ -1477,6 +1477,122 @@ static struct board_info __initdata boar
 +   },
 + };
 +
 ++static struct board_info __initdata board_FAST2704V2 = {
 ++  .name   = F@ST2704V2,
 ++  .expected_cpu_id= 0x6328,
 ++
 ++  .has_uart0  = 1,
 ++  .has_pci= 1,
 ++  .has_ohci0  = 1,
 ++  .has_ehci0  = 1,
 ++  .has_usbd   = 1,
 ++
 ++  .has_enetsw = 1,
 ++
 ++  .enetsw = {
 ++  .used_ports = {
 ++  [0] = {
 ++  .used   = 1,
 ++  .phy_id = 1,
 ++  .name   = Port 1,
 ++  },
 ++  [1] = {
 ++  .used   = 1,
 ++  .phy_id = 2,
 ++  .name   = Port 2,
 ++  },
 ++  [2] = {
 ++  .used   = 1,
 ++  .phy_id = 3,
 ++  .name   = Port 3,
 ++  },
 ++  [3] = {
 ++  .used   = 1,
 ++  .phy_id = 4,
 ++  .name   = Port 4,
 ++  },
 ++  },
 ++  },
 ++
 ++  .leds = {
 ++  /* front LEDs */
 ++  {
 ++  .name   = F@ST2704V2
 :green:power,
 ++  .gpio   = 4,
 ++  .active_low = 1,
 ++  .default_trigger= default-on,
 ++  },
 ++  {
 ++  .name   = F@ST2704V2:red:power,
 ++  .gpio   = 5,
 ++  .active_low = 1,
 ++  },
 ++  {
 ++  .name   = F@ST2704V2:red:inet,
 ++  .gpio   = 2,
 ++  .active_low = 1,
 ++  },
 ++  {
 ++  .name   = F@ST2704V2:green:dsl,
 ++  .gpio   = 3,
 ++  .active_low = 1,
 ++  },
 ++  {
 ++  .name   = F@ST2704V2:green:inet,
 ++  .gpio   = 11,
 ++  .active_low = 1,
 ++  },
 ++  {
 ++  .name   = F@ST2704V2:green:usb,
 ++  .gpio   = 1,
 ++  .active_low = 1,
 ++  },
 ++
 ++  /* side button LEDs */
 ++  {
 ++  .name   = F@ST2704V2:green:wps,
 ++  .gpio   = 10,
 ++  .active_low = 1,
 ++  },
 ++
 ++  /* FIXME: can't control gpio0 line in out state, needs
 further investigation */
 ++  /*
 ++  {
 ++  .name   = F@ST2704V2
 :green:rfkill,
 ++  .gpio   = 0,
 ++  .active_low = 1,
 ++  },
 ++  */
 ++
 ++  },
 ++  .buttons = {
 ++  {
 ++  .desc   = reset,
 ++  .gpio   = 23,
 ++  .active_low = 1,
 ++  .type   = EV_KEY,
 ++  .code   = KEY_RESTART,
 ++  .debounce_interval  =
 BCM963XX_KEYS_DEBOUNCE_INTERVAL,
 ++  },
 ++  {
 ++  .desc   = wps,
 ++  

Re: [OpenWrt-Devel] [RFC] uClibc: Deactivate oversized thread stack cache

[Weedy]

On 8 Nov 2013 12:52, s...@open-mesh.com wrote:

 From: Sven Eckelmann s...@open-mesh.com

 A small system like the common home router doesn't have 40 MiB per
process for
 a dirty stack cache. This can easily lead to an overbooking OOM problem
and
 caused a lot of hangs+reboots on 32 MiB systems running nodogsplash.

 Not using a stack cache can increase the time to spawn new threads. This
is
 hopefully no problem for system not running a lot of parallel
computations.

Do you have any benches or log dumps that show this fixed it for you?

Or just dropping it to 2mb or less?

I shouldn't notice this. But anyone with running LUCI probably has enough
process churn that this will hurt.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Newbie needs help in building stable for newer hardware

[Weedy]

On 8 Nov 2013 05:10, Florian Effenberger flo...@gmail.com wrote:

 Hello,

 anyone can provide insight? ;-)

 Thanks,
 Florian

Just use trunk. I update my 4300 once a week to HEAD. I I've had zero
problems.


 2013/10/9 Florian Effenberger flo...@gmail.com:
  Hello,
 
  I consider myself quite experienced with OpenWRT already, having
  deployed a few devices, but sadly, I'm a totally development newbie -
  so sorry if my question is maybe stupid. ;-)
 
  I'd like to stick with OpenWRT stable for my deployments, to have the
  same base system. The problem, however, is that my favorite device
  (TP-Link WDR4300) is rapidly changing its hardware revision, making it
  necessary to use trunk for newer models.
 
  Is there an easy way to compile OpenWRT stable only with those
  patchsets necessary to make it work with newer hardware revisions?
  From what I recall, micro releases of OpenWRT stable often include
  newer hardware revisions, without any other changes from trunk, so I
  assume it must be possible in theory - lacking any practical
  experience, however, I seek for your help. :-)
 
  Thanks a lot, and keep up the good work - you folks rock!
  Florian
 ___
 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

Re: [OpenWrt-Devel] zram backport for Attitude Adjustment

[Weedy]

On 8 Nov 2013 00:41, Ben West b...@gowasabi.net wrote:

 As someone who runs AA r38247 patched to include zram support, I can add
anecdotal experience that some processes don't behave well when paged to
swap.  I'm running AR7240 devices with 32MB RAM (i.e. UBNT M gear) as mesh
nodes, and I've found that services like olsrd, coovachilli, and
wpa_supplicant seem to behave erratically if they're swapped out and then
back in.  For this reason, I only enable 3MBytes of swap, preferring not to
depend on it for normal operation.  Only enough so that a node can detect
when it's in a low-memory state and do something to recover (e.g. reboot).

Have you tried turning down swappiness? The default setting likes to swap
things out quicker then you would think.


 I've not had opportunity to test whether this problem also happens with
the newer kernel under BB.


 On Thu, Nov 7, 2013 at 4:10 PM, Hauke Mehrtens ha...@hauke-m.de wrote:

 On 11/07/2013 12:08 AM, Fernando Frediani wrote:
  Hi Hauke,
 
  What you mean by zram worked differently ? As far as I know zram
  (previously known as compcache) has been merged to the Linux Kernel at
  3.2 so it should be there on 3.3 as well (check drivers/staging/zram).

 In Kernel 3.3 zram depends on XVMALLOC being build into the kernel, but
 in OpenWrt our plan was to build zram completely in a module so if
 someone does not want it nothing changes.

  I have talked to Bastien in another conversation and he mentioned he
has
  a WRT54G running fine with Barrier Breaker (which has zram as a kmod
  package), but not sure it's enabled by default or not. I'm interested
to
  to hear if it's having any improvements (how effective the swap zram is
  being used) and if it is a stripped down build (no LuCI and other
  packages) or a normal build. Also how big the swap zram should be ? 6MB
  (as kalua script suggests) or 8MB (half of the memory) ?

 Yes Bastien made the patch which introduced zram support. If you want
 that in AA, it should be possible to make it also build as a kernel
 module. When it is there you can try out what is the best size.

  I have seen a couple of people saying they have managed to flash
  brcm47xx Attitude Adjustment to WRT54G routers but got instability
  issues (slowness or disconnects).

 Yes flashing works, it just runs out of memory very often and the OOM
 killer starts to kill processes.

  So if Barrier Breaker is working fine on WRT54G (with zram activated?)
  then what would be the challenges to port that work already done back
to
  Attitude Adjustment ?

 I do not know if it works fine on these devices, but if it does with
 some traffic going over the router over some time then we should try to
 backport zram support.

 
  Best regards,
 
  Fernando
 
 
  On 6 November 2013 18:17, Hauke Mehrtens ha...@hauke-m.de
  mailto:ha...@hauke-m.de wrote:
 
  On 11/06/2013 05:15 PM, Fernando Frediani wrote:
   Hello Hauke,
  
   I have seen a few emails from you on openwrt-devel list about the
  zram module and also saw it is already present on the trunk(Barrier
  Breaker).
  
   Was wondering if there is any work going on or will be to
backport
  it to Attitude Adjustment then perhaps we can run it on the good
and
  old WRT54G and similar models with 16MB ? How difficult is it to
  backport to AA as it is already done for trunk ?
  
  
   Thanks and best regards,
  
   Fernando
  
  Hi Fernando,
 
  I have no plan to backport zram to Attitude Adjustment. Attitude
  Adjustment uses kernel 3.3 and there zram worked differently or
was not
  included at all, I do not know exactly. But I would like to see
zram
  backported to AA and would like to see a nice patch.
 
  Hauke
 
 
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel




 --
 Ben West
 http://gowasabi.net
 b...@gowasabi.net
 314-246-9434

 ___
 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

Re: [OpenWrt-Devel] AR9344 wifi dying on WD N600 routers

[Weedy]

On Sat, Oct 26, 2013 at 8:35 AM, omggo oom...@gmail.com wrote:
 out of interest weedy, what tp-link devices do you have?

Two WDR4300, a WR2543ND, and a WR1043ND (this one was bought and is
used in the Netherlands).
I also have a TL-WR702N or 703/710. I forget, the one that costs like
15 bucks. I haven't touched it in ages so I don't know off hand.


 On Sat, Oct 26, 2013 at 3:03 AM, Weedy weedy2...@gmail.com wrote:

 On 25 Oct 2013 09:40, Alvaro Kuolas kuo...@gmail.com wrote:
 
  I have the same issue with different Atheros based routers, namely:
  TP-Link WDR4300, WDR4900, TL-WR841ND V1 and TL-WR841ND V2.
 
  WiFi it's quite unstable and I don't know where to look for debugging
  this issue.

 My tp-link devices are rock solid.
 I'm Canadian. Maybe is regional firmware thing?

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] AR9344 wifi dying on WD N600 routers

[Weedy]

On 25 Oct 2013 09:40, Alvaro Kuolas kuo...@gmail.com wrote:

 I have the same issue with different Atheros based routers, namely:
TP-Link WDR4300, WDR4900, TL-WR841ND V1 and TL-WR841ND V2.

 WiFi it's quite unstable and I don't know where to look for debugging
this issue.

My tp-link devices are rock solid.
I'm Canadian. Maybe is regional firmware thing?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [OpenWrt-Devel 4/4] Add profile and build image for Sagemcom F@ST2704V2 ADSL router

[Weedy]

On 21 Oct 2013 14:47, Marcin Jurkowski marci...@gmail.com wrote:

 This adds profile and build image for Sagemcom F@st2704, using b43
 driver.
 For WiFi to work properly BCMA fallback SPROM support patch must
 be applied (http://git.io/z1Ki8A).


... I can put a real OS on this pile of ass?
I CAN HAVE REAL BRIDGE MODE?

I kinda want to have your kids. Or a donation link.

Thank you so much for this.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Quick hack for kernel entropy problem on MIPS

[Weedy]

On 18/10/13 07:09 AM, José Vázquez Fernández wrote:
 Take a look at this ticket: https://dev.openwrt.org/ticket/9631

Again, I do not personally have this issue but I can see why it would
need to be fixed.

$ ssh r...@openwrt.lan 'reboot';sleep 3;while ! ping -c3 openwrt.lan; do
sleep 2; done; ssh r...@openwrt.lan 'while :; do cat
/proc/sys/kernel/random/entropy_avail; sleep 1; done'
ping: unknown host openwrt.lan
snip
ping: unknown host openwrt.lan
PING openwrt.lan (192.168.8.1) 56(84) bytes of data.
64 bytes from OpenWrt.lan (192.168.8.1): icmp_seq=1 ttl=69 time=0.999 ms
64 bytes from OpenWrt.lan (192.168.8.1): icmp_seq=2 ttl=69 time=1.24 ms
64 bytes from OpenWrt.lan (192.168.8.1): icmp_seq=3 ttl=69 time=1.22 ms

--- openwrt.lan ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 0.999/1.158/1.247/0.112 ms
135
139
145
151
snip
200
207
213
218
222
229
232
237
242
snip
363
401
440
478
9
46
87
122
166
203
snip
684
726
762
799
837
snip
1346
1381
1416
1452
1481
1513
snip
1074
1106
1161
1197
1231
1263
snip
1270
1304
1347
1385
snip
1091
1123
1156
1185
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] ath9k / set txpower / TP-LINK TL-WR841N/ND v8

[Weedy]

On 17 Oct 2013 08:25, Bastian Bittorf bitt...@bluebottle.com wrote:

 we are facing a strange issue on 2 routers with identical
 hardware: TP-LINK TL-WR841N/ND v8 - i cannot set txpower 18 dBm
 according to 'iwconfig'/'iwinfo' on ONE router. the
 other (different location, same openwrt-revision r38432) can do that:

 what can we do?

 bye, bastian

From what I understand, old ath9k would accept any tx power level that was
valid for your region, but would fail silently if blocked by the EPROM.

Currently the driver relays the error if it's blocked by region AND EPROM,
instead of just region.
Nothing has changed physically, the driver just stopped pretending.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Quick hack for kernel entropy problem on MIPS

[Weedy]

On Thu, Oct 17, 2013 at 11:40 AM, chrono chr...@open-resource.org wrote:
 Ahoi everyone,

 it was requested on IRC that I send my solution to the entropy problem with
 the current
 kernel (e.g. having 0 available entropy):

 root@OpenWrt:/# cat /proc/sys/kernel/random/entropy_avail
 0
Uhh ok?
root@OpenWrt:~# cat /proc/sys/kernel/random/entropy_avail
1189

 This was tested on mips32r2/24kc (Mikrotik Routerboard 450G) but it might
root@OpenWrt:~# cat /proc/cpuinfo
system type: Atheros AR9344 rev 2
machine: TP-LINK TL-WDR3600/4300/4310
processor: 0
cpu model: MIPS 74Kc V4.12
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel