[OpenWrt-Devel] latest trunk r48016 factory image fails to boot on wd mynet n750

[Chirag Chhatriwala]

Hello,

I had a working build r42397 which was stable enough so I didn't touch it
until today.
I built openwrt trunk r48016 (last night) and everything built without any
issues.

I like to load thing the factory image but this time loading the factory
image resulted in no internet. Router came on, I could see activity on the
indicator lights but no IP. I did notice that the front LED light do not
stay on after the factory install on this build. On a working build, the
front LED stays on (solid) when working (default config).

I have LUCI pre-baked as I use the same configs. I personally run a diff
between the configs and didn't see anything that would have broken booting
from factory flash install.

Then I reverted to a working openwrt (r46900) build that I factory-flashed
and then proceeded to do a sysupgrade of r48016 (and wipe existing
settings). This WORKED, the router boots.

Something seems to be not working with factory install, but is working with
the sysupgrade. I have no way to debug this. Just thought I should bring
this to the attention of the devs in the forum.

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

[OpenWrt-Devel] BB r41023+: 40MHz -> 20MHz switch and stack-trace on ath9k routers (potentially hostapd related)

[Chirag Chhatriwala]

Hello,

I've got a problem where a single device (HP Pavilion Laptop running AR9285
bgn WiFi card) is causing a stack-trace/kernel panic on OpenWRT based
router (WD MyNet N750). This happens just when the laptop connects to the
WiFi network (which is running using "option noscan 1"). Up until this
point, all devices connected to the router work without any problem. As
soon as *this* laptop connects, router switches operation to 20MHz mode on
the TX Leg. Up until r41021, openwrt builds did not exhibit such behavior.
The router maintained a 40MHz connection to all clients.
Just before the stack-trace, the system log also indicates that the device
switched from 40MHz to 20MHz mode of operation.

For me the culprit is any build that includes the latest *hostapd* changes
in r41022 and higher. However, r41022 broke the build (fixed in r41023).
Consequently, every build upwards of r41023 result in the following stack
trace.

[12340.17] [ cut here ]
[12340.18] WARNING: at
/home/chirag/bb/mynet/build_dir/target-mips_34kc_uClibc-0.9.33.2/linux-ar71xx_generic/compat-wireless-2014-05-22/net/mac80211/chan.c:535
ieee80211_recalc_chanctx_min_def+0x4f8/0x6c4 [mac80211]()
[12340.20] Modules linked in: ath9k ath9k_common pppoe ppp_async
iptable_nat ath9k_hw ath pppox ppp_generic nf_nat_ipv4 nf_conntrack_ipv4
mac80211 ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_state xt_nat
xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS
xt_REDIRECT xt_LOG xt_CT ums_usbat ums_sddr55 ums_sddr09 ums_karma
ums_jumpshot ums_isd200 ums_freecom ums_datafab ums_cypress ums_alauda slhc
nf_nat_irc nf_nat_ftp nf_nat nf_defrag_ipv4 nf_conntrack_irc
nf_conntrack_ftp iptable_raw iptable_mangle iptable_filter ipt_REJECT
ip_tables crc_ccitt compat fuse sg ledtrig_usbdev ip6t_REJECT ip6table_raw
ip6table_mangle ip6table_filter ip6_tables x_tables nf_conntrack_ipv6
nf_conntrack nf_defrag_ipv6 vfat fat ntfs nls_utf8 nls_iso8859_1 nls_cp850
nls_cp437 ipv6 arc4 crypto_blkcipher usb_storage uhci_hcd ohci_hcd
ehci_platform ehci_hcd sd_mod scsi_mod gpio_button_hotplug ext4 crc16 jbd2
mbcache usbcore nls_base usb_common crypto_hash
[12340.29] CPU: 0 PID: 2200 Comm: hostapd Not tainted 3.10.49 #1
[12340.29] Stack :     80362eba
0035 86b4e758 873f9274
[12340.29]   802c0c68 8030f21b 0898 80362664 86b4e758 873f9274
86a33b88 002c
[12340.29]   0008 80079040 0003 80076ac0 872cbdd0 873f9274
802c2528 86a33a7c
[12340.29]        
 
[12340.29]        
 86a33a08
[12340.29]   ...
[12340.33] Call Trace:
[12340.33] [<8006e294>] show_stack+0x48/0x70I
[12340.34] [<80076bbc>] warn_slowpath_common+0x78/0xa8
[12340.34] [<80076c74>] warn_slowpath_null+0x18/0x24
[12340.35] [<872ab464>] ieee80211_recalc_chanctx_min_def+0x4f8/0x6c4
[mac80211]
[12340.35]
[12340.36] ---[ end trace 5bded13efd434a80 ]---



Syslog shows the same thing, except the following line appears just before
the stack-trace:

daemon.info hostapd: wlan0: STA 4c:xx:xx:xx:xx:xx IEEE 802.11: Switching to
20 MHz operation


Here's what my WiFi config looks like:

config wifi-device  radio0
option type mac80211
 option hwmode 11g
option path 'platform/ar934x_wmac'
 option channel  4
option htmode HT40
option noscan 1
 option country US

config wifi-iface
option device   radio0
 option network  lan
option wds 1
option mode ap
 option ssid OPENWRT2G
option encryption psk2
option key blahblahblah

config wifi-device  radio1
option type mac80211
option hwmode 11a
 option path 'pci:00/:00:00.0'
option channel  149
 option htmode HT40
option noscan 1
 option country US

config wifi-iface
option device   radio1
 option network  lan
option wds 1
option mode ap
 option ssid OPENWRT5G
option encryption psk2
option key blahblahblah


Between r41021 and r41023, there seem to be only hostapd related changes.
mac80211 is the same version. I'm no expert, but I would like to help
getting to the bottom of this issue. Would a tcpdump be helpful?
Most recent build r41797 also exhibits this behavior.

I've also set this up as a bug against BB on dev.openwrt.org as ticket
#17253 .

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

Re: [OpenWrt-Devel] [PATCHv2][orion] Add support for 3.7

[Chirag Chhatriwala]

On Mon, Feb 25, 2013 at 6:22 AM, Imre Kaloz  wrote:

> On Mon, 25 Feb 2013 11:45:38 +0100, Florian Fainelli 
> wrote:
>
>  On 02/25/2013 11:05 AM, Imre Kaloz wrote:
>>
>>> Hi,
>>>
>>> On Sat, 23 Feb 2013 16:29:20 +0100, Maarten Bezemer
>>>  wrote:
>>>
>>>  It seems that Imre Kaloz (the target maintainer) is not available?
 Is it possible that the patch gets reviewed/committed by someone else?

>>>
>>> Orion will be moved to DT, so 3.7 support won't be commited at all.
>>>
>>
>> Sounds like a good plan and a lot of work at the same time, would not it
>> be beneficial for users to have an interim 3.7 support for them to test?
>>
>
> I rather not at another outdated kernel. 3.7 doesn't bring any critical
> feature for us.
>
>
Sorry for my ignorance but what does "Orion will be moved to DT" mean ?


> Imre
>
> __**_
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.**org 
> https://lists.openwrt.org/**mailman/listinfo/openwrt-devel
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH][packages] asterisk-11.x : update to 11.2.2

[Chirag Chhatriwala]

On Thu, Mar 28, 2013 at 10:32 AM, Jiri Slachta  wrote:

>
> Signed-off-by: Jiri Slachta 
> Index: feeds/packages/net/asterisk-11.x/Makefile
> ===
> --- net/asterisk-11.x/Makefile  (revision 36134)
> +++ net/asterisk-11.x/Makefile  (working copy)
> @@ -8,12 +8,12 @@
>  include $(TOPDIR)/rules.mk
>
>  PKG_NAME:=asterisk11
> -PKG_VERSION:=11.2.1
> +PKG_VERSION:=11.2.2
>  PKG_RELEASE:=1
>
>  PKG_SOURCE:=asterisk-$(PKG_VERSION).tar.gz
>  PKG_SOURCE_URL:=
> http://downloads.asterisk.org/pub/telephony/asterisk/releases/
> -PKG_MD5SUM:=b82a82e5adfff0383769e923bfb54c56
> +PKG_MD5SUM:=3e7a732949b3f0bae6500d41eb19f1df
>
>  PKG_BUILD_DIR=$(BUILD_DIR)/asterisk-$(PKG_VERSION)
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>


Jiri,

I would suggest patching the OpenWRT's asterisk11 package to 11.3.0 (which
is released today), instead of the 11.2.2 (which was released yesterday).
Excerpt from the change log which address a known problem with google voice
calling which is included in 11.3.0 (but not in 11.2.2):


2013-01-11 23:04 + [r378917]  Joshua Colp 

* res/res_xmpp.c: Retain XMPP filters across reconnections so
  external modules continue to function as expected. Previously if
  an XMPP client reconnected any filters added by an external
  module were lost. This issue exhibited itself with chan_motif not
  receiving and reacting to Jingle signaling. (closes issue
  ASTERISK-20916) Reported by: kuj


If I'm not mistaken, there may be a small change may be required to
one of your patchfiles for 11.3.0 to compile to one of your patch
files(it is fairly straightforward).


regards,

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

[OpenWrt-Devel] E4200 and broadcom 47xx soc

[Chirag Chhatriwala]

Hi All,

I'm just about ready to solder on some header pins and connect my E4200 via
the serial/uart console.
In the meantime, what is the correct Target profile to make sure my
router's ethernet and wifi work without any issues (on my own build of
openwrt trunk).

Broadcom SoC, all Ethernet, BCM43xx WiFi (b43, default)
*Broadcom SoC, all Ethernet, BCM43xx WiFi (wl, proprietary) *
Broadcom SoC, all Ethernet, Atheros WiFi (ath5k)
Broadcom SoC, all Ethernet, No WiFi
Broadcom SoC, b44 Ethernet, BCM43xx WiFi (b43, default)
Broadcom SoC, b44 Ethernet, BCM43xx WiFi (wl, proprietary)
Broadcom SoC, b44 Ethernet, Atheros WiFi (ath5k)
Broadcom SoC, b44 Ethernet, No WiFi
Broadcom SoC, tg3 Ethernet, BCM43xx WiFi (b43)
Broadcom SoC, tg3 Ethernet, BCM43xx WiFi (wl, proprietary)
Broadcom SoC, tg3 Ethernet, no WiFi
Broadcom SoC, bgmac Ethernet, BCM43xx WiFi (bgmac)
*Broadcom SoC, bgmac Ethernet, BCM43xx WiFi (wl, proprietary)   *
Broadcom SoC, bgmac Ethernet, No WiFi


*Bold* ones are the ones I think are correct but just not sure.


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

Re: [OpenWrt-Devel] E4200 and broadcom 47xx soc

[Chirag Chhatriwala]

On Thu, Mar 28, 2013 at 7:19 PM, Hauke Mehrtens  wrote:

>
> You need the bgmac Ethernet driver and wifi should be supported by b43,
> brcmsmac or wl. The 5GHz wifi will not work in 5GHz mode and it could
> work in 2.4 GHZ mode with b43.
>
> Select a profile with "all Ethernet" or "bgmac Ethernet".
>
> Hauke
>

Strange, I thought the 5GHz wifi would work with broadcom-wl driver as it
is expected.
Am I missing something?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] E4200 and broadcom 47xx soc

[Chirag Chhatriwala]

On Thu, Mar 28, 2013 at 9:00 PM, Hauke Mehrtens  wrote:

> On 03/29/2013 01:47 AM, Chirag Chhatriwala wrote:
> >
> >
> >
> > On Thu, Mar 28, 2013 at 7:19 PM, Hauke Mehrtens  > <mailto:ha...@hauke-m.de>> wrote:
> >
> >
> > You need the bgmac Ethernet driver and wifi should be supported by
> b43,
> > brcmsmac or wl. The 5GHz wifi will not work in 5GHz mode and it could
> > work in 2.4 GHZ mode with b43.
> >
> > Select a profile with "all Ethernet" or "bgmac Ethernet".
> >
> > Hauke
> >
> >
> > Strange, I thought the 5GHz wifi would work with broadcom-wl driver as
> > it is expected.
> > Am I missing something?
> >
> No, broacom-wl only supports old wifi devices and no new cores released
> in the last ~4 years. The 5GHz wifi supports 450MBit/s so it is a
> BCM4331 with a HT-Phy and this is only supported by b43 with ieee80211g
> rates and in the 2.4 GHz band. This wifi will probably not work at all
> because it was not designed and programmed to be used in the 2.4GHz
> band. The 2.4GHz wifi of the BCM4718 should work with b43, brcmsmac or
> broadcom-wl.
>
> Hauke
>

Okay I get that. So basically on the E4200 I will have Ethernet (as a
result of bgmac), WiFi only on the SoC (BCM4718A1 integrated WiFi) , 2.4
GHz WiFi on the BCM4331 (through b43 or wl) but not 5 GHz ?
So what I understand is full 450 Mbps 5 Ghz WiFi support is still lacking
for (newer) broadcom based hardware. That is quite a bummer.

That has me questioning is there any OpenWrt roadmap on supporting the
broadcom based 5 Ghz chips?
Also, the new hardware (based on BCM4706) will support Ethernet (due to
bgmac) but the WiFi is still a question mark. Also, the BCM4706 boards are
not WiSoCs from what I understand (no integrated wifi). Its BCM4360/BCM4331
(RTN66U) and BCM4360/BCM4331 (EA4500).
Any plans of making the drivers more current/up-to-date now that
802.11an+ac hardware is gaining momentum.

PS. My CP2102 USB to UART is blown and I'm waiting to receive another one.
Do I just connect the TX, RX and GND? And the TX (on router) connects to RX
(on UART module) and vice versa or is it simple TX to TX and RX to RX?
We're still talking about the E4200.
Thanks.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH][packages][v2] asterisk-11.x : update to 11.3.0

[Chirag Chhatriwala]

Was about to build a new version of trunk when I decided to check on one of
my needs (asterisk). It's still in 11.2.1.
Can we get this pushed into trunk?


On Thu, Mar 28, 2013 at 10:57 PM, Jiri Slachta  wrote:

> The changelog for the latest version of asterisk mostly brings bugfixes
> for ConfBridge, resolves deadlocks between pending CDR and batch CDR locks,
> prevents DoS in HTTP server and prevents buffer overflow through H.264
> negotiation.
>
> Signed-off-by: Jiri Slachta 
> Index:
> net/asterisk-11.x/patches/010-asterisk-configure-undef-res-ninit.patch
> ===
> --- net/asterisk-11.x/patches/010-asterisk-configure-undef-res-ninit.patch
>  (revision 36140)
> +++ net/asterisk-11.x/patches/010-asterisk-configure-undef-res-ninit.patch
>  (working copy)
> @@ -1,12 +1,10 @@
>  --- a/configure
>  +++ b/configure
> -@@ -24043,9 +24043,6 @@ $as_echo "$ac_try_echo") >&5
> -   { $as_echo "$as_me:$LINENO: result: yes" >&5
> +@@ -16353,7 +16353,6 @@
> +   { $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
>   $as_echo "yes" >&6; }
>
> --cat >>confdefs.h <<\_ACEOF
> --#define HAVE_RES_NINIT 1
> --_ACEOF
> +-$as_echo "#define HAVE_RES_NINIT 1" >>confdefs.h
>
> -   { $as_echo "$as_me:$LINENO: checking for library containing
> res_9_ndestroy" >&5
> +   { $as_echo "$as_me:${as_lineno-$LINENO}: checking for library
> containing res_9_ndestroy" >&5
>   $as_echo_n "checking for library containing res_9_ndestroy... " >&6; }
> Index: net/asterisk-11.x/Makefile
> ===
> --- net/asterisk-11.x/Makefile  (revision 36134)
> +++ net/asterisk-11.x/Makefile  (working copy)
> @@ -8,12 +8,12 @@
>  include $(TOPDIR)/rules.mk
>
>  PKG_NAME:=asterisk11
> -PKG_VERSION:=11.2.1
> +PKG_VERSION:=11.3.0
>  PKG_RELEASE:=1
>
>  PKG_SOURCE:=asterisk-$(PKG_VERSION).tar.gz
>  PKG_SOURCE_URL:=
> http://downloads.asterisk.org/pub/telephony/asterisk/releases/
> -PKG_MD5SUM:=b82a82e5adfff0383769e923bfb54c56
> +PKG_MD5SUM:=e80bd74335994d856f732237a4a5bc5f
>
>  PKG_BUILD_DIR=$(BUILD_DIR)/asterisk-$(PKG_VERSION)
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Correct use of relayd on both 2.4 & 5 Ghz band (wifi pseudobridge(s))

[Chirag Chhatriwala]

Greetings,

I have come across this document to setup a wifi bridge using two routers.
http://wiki.openwrt.org/doc/recipes/relayclient

The guide explains assumes that you're bridging on either 2.4Ghz or the
5Ghz band, but not both.
I've tried to extrapolate the means to bridge both bands on both the
routers. However, on the main configuration of the wifi bridge, it lists
only one stabridge.
As it asks to create a stabridge and wwan, i created a stabridge2 and wwan2
and followed the instructions to the T to setup a bridge on the 5 Ghz band
as well.
Even after doing so, all the traffic is routed via the initially created
bridge on the 2.4 Ghz band, even if a wifi client connects to the 5ghz band
on the wifi bridge.

In short, if a client connects to the wifi bridge's 5Ghz band, the traffic
will be routed through the 2.4Ghz band to the main router (and the reverse
when the client is receiving data from the internet).

What am I doing wrong? Is what I'm trying to do even possible?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Correct use of relayd on both 2.4 & 5 Ghz band (wifi pseudobridge(s))

[Chirag Chhatriwala]

Can anyone help me with the question above? Thanks. I've been struggling to
get more than 65mbps with the pseudo-bridge router on either of the wifi
bands (2.4 and 5Ghz).



On Wed, Jun 26, 2013 at 3:12 AM, Chirag Chhatriwala wrote:

> Greetings,
>
> I have come across this document to setup a wifi bridge using two routers.
> http://wiki.openwrt.org/doc/recipes/relayclient
>
> The guide explains assumes that you're bridging on either 2.4Ghz or the
> 5Ghz band, but not both.
> I've tried to extrapolate the means to bridge both bands on both the
> routers. However, on the main configuration of the wifi bridge, it lists
> only one stabridge.
> As it asks to create a stabridge and wwan, i created a stabridge2 and
> wwan2 and followed the instructions to the T to setup a bridge on the 5 Ghz
> band as well.
> Even after doing so, all the traffic is routed via the initially created
> bridge on the 2.4 Ghz band, even if a wifi client connects to the 5ghz band
> on the wifi bridge.
>
> In short, if a client connects to the wifi bridge's 5Ghz band, the traffic
> will be routed through the 2.4Ghz band to the main router (and the reverse
> when the client is receiving data from the internet).
>
> What am I doing wrong? Is what I'm trying to do even possible?
>
>
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Question about squasfsh/jffs2 on NAND (WNDR3700v4 / WNDR4300)

[Chirag Chhatriwala]

On Sat, Aug 3, 2013 at 6:51 AM, Jonas Gorski  wrote:

>
> No, this is a generic NAND flash problem.
>
> The issue is that squashfs has no bad block management at all and
> requires all blocks on order; but for proper NAND bad block management
> you also need to be able to skip bad blocks and occasionally relocate
> blocks (see [1]). That's why raw squashfs is a bad idea on NAND (it
> works if you use a FTL like ubi).
>
> Regards,
> Jonas
>
> [1] http://www.infradead.org/pipermail/linux-mtd/2006-April/015386.html
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>

Jonas,

So what does this mean for the future of OpenWrt on NAND based devices? It
seems like there are quite a few new and upcoming devices making use of
NAND flash exclusively. If squashfs (which according to me has been the
filesystem of choice on my openwrt installations) is not it good shape, are
we throwing in the towel? Surely, there must be some hope for OpenWrt users
for these new devices.

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

Re: [OpenWrt-Devel] Question about squasfsh/jffs2 on NAND (WNDR3700v4 / WNDR4300)

[Chirag Chhatriwala]

On Sat, Aug 3, 2013 at 10:13 AM, John Crispin  wrote:

>
> Hi,
>
> why so negative ? no one said we are throwing the towel ... in general
> those targets using nand need to be converted to using an intermediate
> layer such as ubi, which several targets already do.
>
>
John,

Sorry, I did not mean to come off as negative. If I did, my apologies.
Simply wanted to know the means to an end (if there was one, and from your
response it seems there is one... but will take a bit of effort).

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

Re: [OpenWrt-Devel] [PATCH][RFC] Add 'N' mode support to broadcom-wl

[Chirag Chhatriwala]

On Aug 17, 2013 5:29 PM, "Nathan Hintz"  wrote:
>
> On Sat, 17 Aug 2013 15:40:43 +0200
> Hauke Mehrtens  wrote:
>
> > On 08/17/2013 02:09 PM, Hauke Mehrtens wrote:
> > > On 09/23/2012 11:07 PM, Nathan Hintz wrote:
> > >> This is partly based on patches sent by Łukasz Kwestarz (See
> > >>
https://lists.openwrt.org/pipermail/openwrt-devel/2012-March/014356.html).
> > >>
> > >> Signed-off-by: Nathan Hintz 
> > >>
> > >> Index: trunk/package/broadcom-wl/Makefile
> > >> ===
> > >> --- trunk/package/broadcom-wl/Makefile (revision 33530)
> > >> +++ trunk/package/broadcom-wl/Makefile (working copy)
> > >> @@ -10,7 +10,7 @@
> > >>
> > >>  PKG_NAME:=broadcom-wl
> > >>  PKG_VERSION:=5.10.56.27.3
> > >> -PKG_RELEASE:=4
> > >> +PKG_RELEASE:=5
> > >>
> > >>  PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION)_$(ARCH).tar.bz2
> > >>  PKG_SOURCE_URL:=http://downloads.openwrt.org/sources
> > >> Index: trunk/package/broadcom-wl/src/wlc.c
> > >> ===
> > >> --- trunk/package/broadcom-wl/src/wlc.c(revision 33530)
> > >> +++ trunk/package/broadcom-wl/src/wlc.c(working copy)
> > >> @@ -499,8 +499,8 @@
> > >>/* driver doesn't support GET */
> > >>
> > >>if ((param & PARAM_MODE) == SET) {
> > >> -  strncpy(pmk.key, value, WSEC_MAX_PSK_LEN);
> > >> -  pmk.key_len = strlen(value);
> > >> +  strncpy(pmk.key, str, WSEC_MAX_PSK_LEN);
> > >> +  pmk.key_len = strlen(str);
> > >>
> > >>if (pmk.key_len > WSEC_MAX_PSK_LEN)
> > >>pmk.key_len = WSEC_MAX_PSK_LEN;
> > >> @@ -912,6 +912,41 @@
> > >>.handler = wlc_ioctl,
> > >>.desc = "G Mode"
> > >>},
> > >> +  {
> > >> +  .name = "phytype",
> > >> +  .param = INT,
> > >> +  .data.num = (WLC_GET_PHYTYPE << 16),
> > >> +  .handler = wlc_ioctl,
> > >> +  .desc = "PHY Type"
> > >> +  },
> > >> +  {
> > >> +  .name = "nmode",
> > >> +  .param = INT,
> > >> +  .handler = wlc_iovar,
> > >> +  .data.str = "nmode",
> > >> +  .desc = "N Mode"
> > >> +  },
> > >> +  {
> > >> +  .name = "nreqd",
> > >> +  .param = INT,
> > >> +  .handler = wlc_iovar,
> > >> +  .data.str = "nreqd",
> > >> +  .desc = "N Mode required"
> > >> +  },
> > >> +  {
> > >> +  .name = "chanspec",
> > >> +  .param = INT,
> > >> +  .handler = wlc_iovar,
> > >> +  .data.str = "chanspec",
> > >> +  .desc = "Channel Spec (See bcmwifi.h)"
> > >> +  },
> > >> +  {
> > >> +  .name = "band",
> > >> +  .param = INT,
> > >> +  .data.num = ((WLC_GET_BAND << 16) | WLC_SET_BAND),
> > >> +  .handler = wlc_ioctl,
> > >> +  .desc = "Band"
> > >> +  },
> > >>  };
> > >>  #define wlc_calls_size (sizeof(wlc_calls) / sizeof(struct
> > >> wlc_call))
> > >> @@ -971,7 +1006,7 @@
> > >>set = 1;
> > >>switch(cmd->param & PARAM_TYPE) {
> > >>case INT:
> > >> -  intval = strtoul(arg, &end, 10);
> > >> +  intval = strtoul(arg, &end, 0);
> > >>if (end && !(*end)) {
> > >>memcpy(buf, &intval,
> > >> sizeof(intval)); } else {
> > >> Index: trunk/package/broadcom-wl/files/lib/wifi/broadcom.sh
> > >> ===
> > >> --- trunk/package/broadcom-wl/files/lib/wifi/broadcom.sh
> > >> (revision 33530) +++
> > >> trunk/package/broadcom-wl/files/lib/wifi/broadcom.sh
> > >> (working copy) @@ -131,6 +131,7 @@ config_get frag "$device" frag
> > >>config_get rts "$device" rts
> > >>config_get hwmode "$device" hwmode
> > >> +  config_get htmode "$device" htmode
> > >>local vif_pre_up vif_post_up vif_do_up vif_txpower
> > >>local doth=0
> > >>local wmm=1
> > >> @@ -161,15 +162,40 @@
> > >>;;
> > >>esac
> > >>
> > >> +  [ ${channel:-0} -ge 1 -a ${channel:-0} -le 14 ] && band=2
> > >> +  [ ${channel:-0} -ge 36 ] && band=1
> > >> +
> > >>case "$hwmode" in
> > >> -  *b)   hwmode=0;;
> > >> -  *bg)  hwmode=1;;
> > >> -  *g)   hwmode=2;;
> > >> -  *gst) hwmode=4;;
> > >> -  *lrs) hwmode=5;;
> > >> -  *)hwmode=1;;
> > >> +  *na)nmode=1; nreqd=0;;
> > >> +  *a) nmode=0;;
> > >> +  *ng)gmode=1; nmode=1; nreqd=0;;
> > >> +  *n) nmode=1; nreqd=1;;
> > >> +  *b) gmode=0; nmode=0;;
> > >> +  *bg)gmode=1; nmode=0;;
> > >> +  *g) gmode=2; nmode=0;;
> > >> +  *gst)   gmode=4; nmode=0;;
> > >> +  *lrs)   gmode=5; nmode=0;;
> > >> +  *)  case "$band" in
> > >> +  2) gmode=1; nmode=1; nreqd=0;;
> > >> +  1) nmode=1; n

[OpenWrt-Devel] relayd half bandwdith issue

[Chirag Chhatriwala]

Hello,

I presented this problem a while back and it seems like it went nowhere.
I have a couple of dual band 600 mbps routers based on ar71xx and I've set
them up to use the tutorial here:
http://wiki.openwrt.org/doc/recipes/relayclient

I've tried setting up the bridge on 2.4 GHz and also on the 5 GHz bands but
every time. In both instances, the bridge router connects to the main
router at full 40 MHz bandwidth. I've enabled noscan option just to ensure
proper 40 MHz connectivity.

However, all WiFi clients (laptops, my smart tv, google tv player, etc. all
of them being abgn + 40 MHz bandwidth capable), can connect only at 20MHz
bandwidth to the bridge router.
If these WiFi devices connect to the main router, they connect at full 40
MHz bandwidth. I have verified this placing the laptop and google tv player
physically closer to the pseudobridge. LUCI also shows the devices
connected to the bridge and their respective bandwidth is always 20MHz.
LUCI also shows connection data rates always at or below 130mbps.

When placed closer to the main router, these devices (laptop + google tv
player) connect to it and the LUCI web admin status shows 40MHz bandwidth
and connection rates in the 200+ mbps (peaking at 300 mbps limit).

Apparently, devices with a max of data rate of 130mbps (when connected to
the main router) get choked when their max data rate gets limited to 65mbps
(by connecting to the pseudobridge) as a result of this problem.

This has been tried and proven with 2.4 GHz alone and also at 5 GHz alone.
I'm all out of ideas.
I raised this ticket long ago: https://dev.openwrt.org/ticket/12720
I sent several emails regarding this as well to no avail:
http://www.mail-archive.com/openwrt-devel@lists.openwrt.org/msg18850.html

This is by far the only wrinkle I've faced in dealing with OpenWrt on my
routers. Everything else so far has been spot on and rock solid (knock on
wood).

If anyone can share their thoughts or help narrow down the cause of this
bug, it would be greatly appreciated.

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

Re: [OpenWrt-Devel] relayd half bandwdith issue

[Chirag Chhatriwala]

I find it hard to believe that after numerous attempts to update the ticket
in question (12720) and having mailed the group thrice, that there isn't a
single response to the aforementioned issue of half bandwidth.
Is there no one with ath9k and relayd expertise ? I'm sure some of the more
recent ath10k developments have been fruitful and will benefit the
community, just as a fix for this issue would benefit some ath9k/relayd
users.

If I had enough driver development expertise I would fix it myself. Please
do not take treat this response as a rant, as I am all very thankful for
being able to use OpenWrt on my devices.
However, this half bandwidth issue is a bit of a niggle that I'd like to
eliminate.

If anyone can chime in with something helpful it would be "greatly"
appreciated.

Thank you,
Chirag


On Sun, Aug 18, 2013 at 3:50 PM, Chirag Chhatriwala wrote:

> Hello,
>
> I presented this problem a while back and it seems like it went nowhere.
> I have a couple of dual band 600 mbps routers based on ar71xx and I've set
> them up to use the tutorial here:
> http://wiki.openwrt.org/doc/recipes/relayclient
>
> I've tried setting up the bridge on 2.4 GHz and also on the 5 GHz bands
> but every time. In both instances, the bridge router connects to the main
> router at full 40 MHz bandwidth. I've enabled noscan option just to ensure
> proper 40 MHz connectivity.
>
> However, all WiFi clients (laptops, my smart tv, google tv player, etc.
> all of them being abgn + 40 MHz bandwidth capable), can connect only at
> 20MHz bandwidth to the bridge router.
> If these WiFi devices connect to the main router, they connect at full 40
> MHz bandwidth. I have verified this placing the laptop and google tv player
> physically closer to the pseudobridge. LUCI also shows the devices
> connected to the bridge and their respective bandwidth is always 20MHz.
> LUCI also shows connection data rates always at or below 130mbps.
>
> When placed closer to the main router, these devices (laptop + google tv
> player) connect to it and the LUCI web admin status shows 40MHz bandwidth
> and connection rates in the 200+ mbps (peaking at 300 mbps limit).
>
> Apparently, devices with a max of data rate of 130mbps (when connected to
> the main router) get choked when their max data rate gets limited to 65mbps
> (by connecting to the pseudobridge) as a result of this problem.
>
> This has been tried and proven with 2.4 GHz alone and also at 5 GHz alone.
> I'm all out of ideas.
> I raised this ticket long ago: https://dev.openwrt.org/ticket/12720
> I sent several emails regarding this as well to no avail:
> http://www.mail-archive.com/openwrt-devel@lists.openwrt.org/msg18850.html
>
> This is by far the only wrinkle I've faced in dealing with OpenWrt on my
> routers. Everything else so far has been spot on and rock solid (knock on
> wood).
>
> If anyone can share their thoughts or help narrow down the cause of this
> bug, it would be greatly appreciated.
>
> Regards,
> Chirag
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] WD MyNet N750: ar9344 + ar8327 switch, unclear on phy/mdio/mac wiring

[Chirag Chhatriwala]

Were there any working patches to enable support for this router on trunk?
I just bought this device because of the 3x3 802.11an support.
I can test out firmware as well. (I believe this board comes with a serial
console populated).

Thanks.


On Sat, Oct 26, 2013 at 3:59 PM, Felix Kaechele  wrote:

> Oh, I forgot to attach the patch I use for testing.
>
> Here it is!
>
> - Felix
>
>
> ___
> 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] YATE 5.0.0 fails to build because PHP5 doesn't build

[Chirag Chhatriwala]

I am having a bit difficulty building OpenWrt trunk as of today.
checked out from git, updated and installed feeds.
Selected the following yate modules:

CONFIG_PACKAGE_yate=y
CONFIG_PACKAGE_yate-mod-accfile=y
CONFIG_PACKAGE_yate-mod-jabberclient=y
CONFIG_PACKAGE_yate-mod-jbfeatures=y
CONFIG_PACKAGE_yate-mod-openssl=y
CONFIG_PACKAGE_yate-mod-regexroute=y
CONFIG_PACKAGE_yate-mod-regfile=y
CONFIG_PACKAGE_yate-mod-rmanager=y
CONFIG_PACKAGE_yate-mod-sipfeatures=y
CONFIG_PACKAGE_yate-mod-tonegen=y
CONFIG_PACKAGE_yate-mod-yjinglechan=y
CONFIG_PACKAGE_yate-mod-yrtpchan=y
CONFIG_PACKAGE_yate-mod-ysipchan=y
CONFIG_PACKAGE_yate-mod-ystunchan=y
CONFIG_PACKAGE_yate-sounds=y

As a result, php5 "attempts" to build (not sure why) and then fails with
the following error log:



make[3]: Entering directory
`/home/chirag/open/buffalo/feeds/packages/lang/php5'
WARNING: skipping php5 -- package not selected
(cd
/home/chirag/open/buffalo/build_dir/target-mips_34kc_uClibc-0.9.33.2/php-5.4.19/./;
if [ -x ./configure ]; then /usr/bin/find
/home/chirag/open/buffalo/build_dir/target-mips_34kc_uClibc-0.9.33.2/php-5.4.19/
-name config.guess | xargs -r chmod u+w; /usr/bin/find
/home/chirag/open/buffalo/build_dir/target-mips_34kc_uClibc-0.9.33.2/php-5.4.19/
-name config.guess | xargs -r -n1 cp
/home/chirag/open/buffalo/scripts/config.guess; /usr/bin/find
/home/chirag/open/buffalo/build_dir/target-mips_34kc_uClibc-0.9.33.2/php-5.4.19/
-name config.sub | xargs -r chmod u+w; /usr/bin/find
/home/chirag/open/buffalo/build_dir/target-mips_34kc_uClibc-0.9.33.2/php-5.4.19/
-name config.sub | xargs -r -n1 cp
/home/chirag/open/buffalo/scripts/config.sub;
AR=mips-openwrt-linux-uclibc-ar AS="mips-openwrt-linux-uclibc-gcc -c -Os
-pipe -mno-branch-likely -mips32r2 -mtune=34kc -fno-caller-saves
-fhonour-copts -Wno-error=unused-but-set-variable -msoft-float
-I/home/chirag/open/buffalo/staging_dir/target-mips_34kc_uClibc-0.9.33.2/usr/lib/libiconv-stub/include
-I/home/chirag/open/buffalo/staging_dir/target-mips_34kc_uClibc-0.9.33.2/usr/lib/libintl-stub/include"
LD=mips-openwrt-linux-uclibc-ld NM=mips-openwrt-linux-uclibc-nm
CC="mips-openwrt-linux-uclibc-gcc" GCC="mips-openwrt-linux-uclibc-gcc"
CXX="mips-openwrt-linux-uclibc-g++" RANLIB=mips-openwrt-linux-uclibc-ranlib
STRIP=mips-openwrt-linux-uclibc-strip
OBJCOPY=mips-openwrt-linux-uclibc-objcopy
OBJDUMP=mips-openwrt-linux-uclibc-objdump
SIZE=mips-openwrt-linux-uclibc-size CFLAGS="-Os -pipe -mno-branch-likely
-mips32r2 -mtune=34kc -fno-caller-saves -fhonour-copts
-Wno-error=unused-but-set-variable -msoft-float
-I/home/chirag/open/buffalo/staging_dir/target-mips_34kc_uClibc-0.9.33.2/usr/lib/libiconv-stub/include
-I/home/chirag/open/buffalo/staging_dir/target-mips_34kc_uClibc-0.9.33.2/usr/lib/libintl-stub/include
" CXXFLAGS="-Os -pipe -mno-branch-likely -mips32r2 -mtune=34kc
-fno-caller-saves -fhonour-copts -Wno-error=unused-but-set-variable
-msoft-float
-I/home/chirag/open/buffalo/staging_dir/target-mips_34kc_uClibc-0.9.33.2/usr/lib/libiconv-stub/include
-I/home/chirag/open/buffalo/staging_dir/target-mips_34kc_uClibc-0.9.33.2/usr/lib/libintl-stub/include
"
CPPFLAGS="-I/home/chirag/open/buffalo/staging_dir/target-mips_34kc_uClibc-0.9.33.2/usr/include
-I/home/chirag/open/buffalo/staging_dir/target-mips_34kc_uClibc-0.9.33.2/include
-I/home/chirag/open/buffalo/staging_dir/toolchain-mips_34kc_gcc-4.6-linaro_uClibc-0.9.33.2/usr/include
-I/home/chirag/open/buffalo/staging_dir/toolchain-mips_34kc_gcc-4.6-linaro_uClibc-0.9.33.2/include
-I/home/chirag/open/buffalo/staging_dir/target-mips_34kc_uClibc-0.9.33.2/usr/lib/libiconv-stub/include
-I/home/chirag/open/buffalo/staging_dir/target-mips_34kc_uClibc-0.9.33.2/usr/lib/libintl-stub/include
"
LDFLAGS="-L/home/chirag/open/buffalo/staging_dir/target-mips_34kc_uClibc-0.9.33.2/usr/lib
-L/home/chirag/open/buffalo/staging_dir/target-mips_34kc_uClibc-0.9.33.2/lib
-L/home/chirag/open/buffalo/staging_dir/toolchain-mips_34kc_gcc-4.6-linaro_uClibc-0.9.33.2/usr/lib
-L/home/chirag/open/buffalo/staging_dir/toolchain-mips_34kc_gcc-4.6-linaro_uClibc-0.9.33.2/lib
-L/home/chirag/open/buffalo/staging_dir/target-mips_34kc_uClibc-0.9.33.2/usr/lib/libiconv-stub/lib
-L/home/chirag/open/buffalo/staging_dir/target-mips_34kc_uClibc-0.9.33.2/usr/lib/libintl-stub/lib
"  ac_cv_c_bigendian_php=yes php_cv_cc_rpath="no"
iconv_impl_name="gnu_libiconv"
ac_cv_php_xml2_config_path="/home/chirag/open/buffalo/staging_dir/target-mips_34kc_uClibc-0.9.33.2/host/bin/xml2-config"
  ./configure --target=mips-openwrt-linux --host=mips-openwrt-linux
--build=x86_64-linux-gnu --program-prefix="" --program-suffix=""
--prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin
--libexecdir=/usr/lib --sysconfdir=/etc --datadir=/usr/share
--localstatedir=/var --mandir=/usr/man --infodir=/usr/info --disable-nls
--enable-shared --disable-static --disable-rpath --disable-debug
--without-pear --with-config-file-path=/etc
--with-config-file-scan-dir=/etc/php5 --disable-short-tags
--with-zlib="/home/chirag/ope

Re: [OpenWrt-Devel] YATE 5.0.0 fails to build because PHP5 doesn't build

[Chirag Chhatriwala]

>
> Selected how? Through menuconfig?
>

Yes Jo, through "make menuconfig" (Network->Telephony->yate) is how I
selected these packages (I did not manipulate the .config file manually).
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] YATE 5.0.0 fails to build because PHP5 doesn't build

[Chirag Chhatriwala]

On Sat, Nov 16, 2013 at 3:42 PM, Michael Heimpold  wrote:

> Hi,
>
> I guess CONFIG_PACKAGE_yate-scripts-php was selected priviously, then
> de-selected
> and the selected dependencies to php5 remains active in the configuration,
> because the dependencies to php5 and php5-cli seems to be correct.
>
> Regards,
> Michael
>

Micheal,
I have attempted two trunk builds (fresh git clone), both without ever
selecting any other yate sub-packages (specifically the yate php scripts
package) selected except for the ones I listed in my first email. Your
assumption is misplaced. And yes having php5 build by itself without
selecting php5-cli (through menuconfig) also leads to a compile error.

Openssl, if not selected, should be built if yate-mod-yjinglechan module is
being built, for google-voice compatibility. If it builds irrespective,
then there is an issue elsewhere.

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

[OpenWrt-Devel] Linksys E4200v1 Support

[Chirag Chhatriwala]

Hi All,

I've notcied a huge deal of progress with bgmac in the recent month and was
willing to help bring support for the E4200v1. I own one of these devices
but I'm not too familiar with the entire driver process. Also, I haven't
flashed anything via serial/uart or JTAG as I'm simply familiar with
flashing via tftp method.

I've reached out to Rafal and Nathan for advice as well.

Firstly, I wanted to know if there is anyone who owns one of these and can
help with enabling OpenWrt support. I can certainly help in any way I can.
I'm sure there are several folks out there who own one of these and I could
mean a lot to revive their E4200v1 with OpenWrt support.

I simply wish I had another one of these to donate to the OpenWrt devs for
the cause.

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

Re: [OpenWrt-Devel] Linksys E4200v1 Support

[Chirag Chhatriwala]

I haven't performed a serial connection ever so I do not know which cable
works best for connecting to the serial port on the E4200v1.
Most USB Serial cables have 9 pins and I don't think I can attach such a
cable to my router.

I think I am looking for a 4 or 5 pin cable, preferably tailored for my
device. Any advice?

Chirag


On Wed, Feb 13, 2013 at 4:46 PM, Hauke Mehrtens  wrote:

> On 02/13/2013 10:33 PM, Chirag Chhatriwala wrote:
> > Hi All,
> >
> > I've notcied a huge deal of progress with bgmac in the recent month and
> > was willing to help bring support for the E4200v1. I own one of these
> > devices but I'm not too familiar with the entire driver process. Also, I
> > haven't flashed anything via serial/uart or JTAG as I'm simply familiar
> > with flashing via tftp method.
> >
> > I've reached out to Rafal and Nathan for advice as well.
> >
> > Firstly, I wanted to know if there is anyone who owns one of these and
> > can help with enabling OpenWrt support. I can certainly help in any way
> > I can. I'm sure there are several folks out there who own one of these
> > and I could mean a lot to revive their E4200v1 with OpenWrt support.
> >
> > I simply wish I had another one of these to donate to the OpenWrt devs
> > for the cause.
> >
> > Thanks,
> > Chirag
> >
> Hi Chirag,
>
> Your device should work, at least Ethernet wifi probably not. When you
> have a serial console connected to your device just flash OpenWrt or
> boot it from the network and report your results.
>
> Hauke
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Linksys E4200v1 Support

[Chirag Chhatriwala]

Hi All,

I'm trying to get additional info.

Hauke: per your latest response indicating the changeset:
https://dev.openwrt.org/changeset/35597
This will not work for E4200v1.

I just dug a few things from the tomato source tree.
Line 36:
http://repo.or.cz/w/tomato.git/blob/tomato-RT:/release/src/router/shared/id.c
Shows much of the E4200 v1 board related identification

Also:
http://repo.or.cz/w/tomato.git/blob/tomato-RT:/release/src/router/rc/init.c
shows vlan[01]ports initializations settings, which do not match the patch
you mention.

I am not sure what else is needed to make sure the proper initializations
are in place for the switch to come up. Wifi (according to broadcom-wl)
should just work. However, I'm worried more about the switch.

Thanks,
Chirag


On Thu, Feb 14, 2013 at 7:41 AM, Hauke Mehrtens  wrote:

> On 02/14/2013 07:30 AM, Nathan Hintz wrote:
> > On Wed, 2013-02-13 at 19:03 -0800, Nathan Hintz wrote:
> >> On Wed, 2013-02-13 at 22:46 +0100, Hauke Mehrtens wrote:
> >>> On 02/13/2013 10:33 PM, Chirag Chhatriwala wrote:
> >>>> Hi All,
> >>>>
> >>>> I've notcied a huge deal of progress with bgmac in the recent month
> and
> >>>> was willing to help bring support for the E4200v1. I own one of these
> >>>> devices but I'm not too familiar with the entire driver process.
> Also, I
> >>>> haven't flashed anything via serial/uart or JTAG as I'm simply
> familiar
> >>>> with flashing via tftp method.
> >>>>
> >>>> I've reached out to Rafal and Nathan for advice as well.
> >>>>
> >>>> Firstly, I wanted to know if there is anyone who owns one of these and
> >>>> can help with enabling OpenWrt support. I can certainly help in any
> way
> >>>> I can. I'm sure there are several folks out there who own one of these
> >>>> and I could mean a lot to revive their E4200v1 with OpenWrt support.
> >>>>
> >>>> I simply wish I had another one of these to donate to the OpenWrt devs
> >>>> for the cause.
> >>>>
> >>>> Thanks,
> >>>> Chirag
> >>>>
> >>> Hi Chirag,
> >>>
> >>> Your device should work, at least Ethernet wifi probably not. When you
> >>> have a serial console connected to your device just flash OpenWrt or
> >>> boot it from the network and report your results.
> >>>
> >>> Hauke
> >>> ___
> >>> openwrt-devel mailing list
> >>> openwrt-devel@lists.openwrt.org
> >>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> >>>
> >> Will the ethernet work if the device is not recognized
> >> by /etc/init.d/netconfig?  It sounded like it had a different nvram
> >> value for "boardtype"?
> >>
> >> I've never booted my E3000 from the network, and tftp only works for me
> >> from a serial console using "upgrade code.bin" (I think my CFE is
> >> possibly broken).  What command do you use when you boot from the
> >> network; and do you need a factory ".bin" image, or does the generic
> >> ".trx" work for this?
> >>
> >> Thanks,
> >>
> >> Nathan
> >
> > Hi Hauke:
> >
> > I saw that /etc/init.d/netconfig has additional "boardtype" values
> > added.  Is the E4200v1 one of those added?  Chirag didn't have an nvram
> > dump, but he had a reference to a tomato issue that indicated it might
> > be "0xF52C".  Also, a patch had been added to the set maintained at
> >
> http://www.znau.edu.ua/temp/asus-rt-n16/2012-12-08T15-25/003-openwrt4716-TARGET_brcm4716-Linksys-E2000.patch
> >  that indicated the E2000 has a "boardtype" of "0x04EF"; although the
> > same tomato reference has that one in lower case for WRT320N/E2000.
>
> This list would have never been complete so now it is checked where the
> CPU port is and if it is port 8, this port is used instead of port 5 in
> the default switch configuration, see [0].
>
> Hauke
>
> [0]: https://dev.openwrt.org/changeset/35597
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Linksys E4200v1 Support

[Chirag Chhatriwala]

Tijs:

Are you using your settings on vlan0ports & vlan1ports
OR
vlan1ports & vlan2ports

I had a glance at vlanports assignment in OpenWRT, Tomato and DD-WRT and I
found that openwrt uses vlan[01]ports (according to the patchfile provided
by Hauke https://dev.openwrt.org/changeset/35597)
Tomato and DD-WRT use vlan[12]ports for port assignments.

All this is armchair programming as I have yet to receive my UART module
and cable to work with the E4200. However, I do want to get to the bottom
of this issue given that I want to understand the openwrt assignment using
vlan[01]ports and not vlan[12]ports (unlike Tomato & DD-WRT).

I apologize if I'm cross referencing the two alternatives to OpenWRT but
thats the only info I can go on so far.

Thanks,
Chirag


On Mon, Feb 18, 2013 at 3:12 AM, Tijs Van Buggenhout  wrote:

> **
>
> On Thursday 14 February 2013 18:35:48 Chirag Chhatriwala wrote:
>
> Hi All,
>
>
> I'm trying to get additional info.
>
>
> Hauke: per your latest response indicating the changeset:
> https://dev.openwrt.org/changeset/35597
>
> This will not work for E4200v1.
>
>
> I just dug a few things from the tomato source tree.
>
> Line 36:
> http://repo.or.cz/w/tomato.git/blob/tomato-RT:/release/src/router/shared/id.c
>
> Shows much of the E4200 v1 board related identification
>
>
> Also:
> http://repo.or.cz/w/tomato.git/blob/tomato-RT:/release/src/router/rc/init.c
>
> shows vlan[01]ports initializations settings, which do not match the patch
> you mention.
>
>
> I am not sure what else is needed to make sure the proper initializations
> are in place for the switch to come up. Wifi (according to broadcom-wl)
> should just work. However, I'm worried more about the switch.
>
>
> Thanks,
>
> Chirag
>
>
>
> On Thu, Feb 14, 2013 at 7:41 AM, Hauke Mehrtens  wrote:
>
> On 02/14/2013 07:30 AM, Nathan Hintz wrote:
> > On Wed, 2013-02-13 at 19:03 -0800, Nathan Hintz wrote:
> >> On Wed, 2013-02-13 at 22:46 +0100, Hauke Mehrtens wrote:
> >>> On 02/13/2013 10:33 PM, Chirag Chhatriwala wrote:
> >>>> Hi All,
> >>>>
> >>>> I've notcied a huge deal of progress with bgmac in the recent month
> and
> >>>> was willing to help bring support for the E4200v1. I own one of these
> >>>> devices but I'm not too familiar with the entire driver process.
> Also, I
> >>>> haven't flashed anything via serial/uart or JTAG as I'm simply
> familiar
> >>>> with flashing via tftp method.
> >>>>
> >>>> I've reached out to Rafal and Nathan for advice as well.
> >>>>
> >>>> Firstly, I wanted to know if there is anyone who owns one of these and
> >>>> can help with enabling OpenWrt support. I can certainly help in any
> way
> >>>> I can. I'm sure there are several folks out there who own one of these
> >>>> and I could mean a lot to revive their E4200v1 with OpenWrt support.
> >>>>
> >>>> I simply wish I had another one of these to donate to the OpenWrt devs
> >>>> for the cause.
> >>>>
> >>>> Thanks,
> >>>> Chirag
> >>>>
> >>> Hi Chirag,
> >>>
> >>> Your device should work, at least Ethernet wifi probably not. When you
> >>> have a serial console connected to your device just flash OpenWrt or
> >>> boot it from the network and report your results.
> >>>
> >>> Hauke
> >>> ___
> >>> openwrt-devel mailing list
> >>> openwrt-devel@lists.openwrt.org
> >>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> >>>
> >> Will the ethernet work if the device is not recognized
> >> by /etc/init.d/netconfig?  It sounded like it had a different nvram
> >> value for "boardtype"?
> >>
> >> I've never booted my E3000 from the network, and tftp only works for me
> >> from a serial console using "upgrade code.bin" (I think my CFE is
> >> possibly broken).  What command do you use when you boot from the
> >> network; and do you need a factory ".bin" image, or does the generic
> >> ".trx" work for this?
> >>
> >> Thanks,
> >>
> >> Nathan
> >
> > Hi Hauke:
> >
> > I saw that /etc/init.d/netconfig has additional "boardtype" values
> > added.  Is the E4200v1 one of those added?  Chirag didn't have an nvram
> > dump, but he

Re: [OpenWrt-Devel] WD MyNet N750: ar9344 + ar8327 switch, unclear on phy/mdio/mac wiring

[Chirag Chhatriwala]

Are there any plans to look at the bootloader and figure out where the PHY
+ MDIO breaks ? I'm too eager to flash OpenWrt on this device.
I would like to dump my buffalo n600 device as soon as this device becomes
functional.

Thanks,
cchhat01


On Fri, Nov 29, 2013 at 5:41 AM, Felix Kaechele  wrote:

> Bootloader code has been published as per my request.
>
> You can find it here: http://support.wdc.com/product/download.asp?groupid=
> 1702&sid=178&lang=en
>
> Now we just need to find where they broke it :)
>
> - Felix
>
> ___
> 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] Build fails at cp -fpR

[Chirag Chhatriwala]

cp: error: no such option: -p

Which "cp" does openwrt use here because ubuntu 12.04.2 contains a "cp"
which knows that "-p" option.

Here's the full log.

chirag@Zoidberg:~/open/n750$ make V=s
Collecting package info: done
Collecting target info: done
Checking 'working-make'... ok.
Checking 'case-sensitive-fs'... ok.
Checking 'getopt'... ok.
Checking 'fileutils'... ok.
Checking 'working-gcc'... ok.
Checking 'working-g++'... ok.
Checking 'ncurses'... ok.
Checking 'zlib'... ok.
Checking 'gawk'... ok.
Checking 'unzip'... ok.
Checking 'bzip2'... ok.
Checking 'perl'... ok.
Checking '/usr/bin/python2.7'... ok.
Checking 'wget'... ok.
Checking 'git'... ok.
Checking 'gnutar'... ok.
Checking 'svn'... ok.
Checking 'openssl'... ok.
Checking 'gnu-find'... ok.
Checking 'getopt-extended'... ok.
Checking 'non-root'... ok.
Checking 'xgettext'... ok.
make[1]: Entering directory `/home/chirag/open/n750'
make[2]: Entering directory `/home/chirag/open/n750'
+ mkdir -p
/home/chirag/open/n750/staging_dir/target-mips_34kc_uClibc-0.9.33.2
+ cd /home/chirag/open/n750/staging_dir/target-mips_34kc_uClibc-0.9.33.2
+ mkdir -p bin lib include stamp
mkdir -p
/home/chirag/open/n750/build_dir/target-mips_34kc_uClibc-0.9.33.2/stamp
touch
/home/chirag/open/n750/staging_dir/target-mips_34kc_uClibc-0.9.33.2/.prepared
+ mkdir -p /home/chirag/open/n750/staging_dir/host
+ cd /home/chirag/open/n750/staging_dir/host
+ mkdir -p bin lib include stamp
mkdir -p /home/chirag/open/n750/build_dir/host/stamp
/home/chirag/open/n750/staging_dir/host/include/sys
install -m0644 /home/chirag/open/n750/tools/include/*.h
/home/chirag/open/n750/staging_dir/host/include/
install -m0644 /home/chirag/open/n750/tools/include/sys/*.h
/home/chirag/open/n750/staging_dir/host/include/sys/
ln -sf lib /home/chirag/open/n750/staging_dir/host/lib64
touch /home/chirag/open/n750/staging_dir/host/.prepared
make[3]: Entering directory `/home/chirag/open/n750/tools/patch'
. /home/chirag/open/n750/include/shell.sh; xzcat
/home/chirag/open/n750/dl/patch-2.7.1.tar.xz | /bin/tar -C
/home/chirag/open/n750/build_dir/host/patch-2.7.1/.. -xf -
touch
/home/chirag/open/n750/build_dir/host/patch-2.7.1/.prepareddecdca928d03e70b0689be9d2e7f1864
(cd /home/chirag/open/n750/build_dir/host/patch-2.7.1/; if [ -x configure
]; then cp -fpR /home/chirag/open/n750/scripts/config.{guess,sub}
/home/chirag/open/n750/build_dir/host/patch-2.7.1// &&  /bin/bash
./configure CC="gcc" CFLAGS="-O2
-I/home/chirag/open/n750/staging_dir/host/include"
CPPFLAGS="-I/home/chirag/open/n750/staging_dir/host/include"
LDFLAGS="-L/home/chirag/open/n750/staging_dir/host/lib" SHELL="/bin/bash"
--target=x86_64-linux-gnu --host=x86_64-linux-gnu --build=x86_64-linux-gnu
--program-prefix="" --program-suffix=""
--prefix=/home/chirag/open/n750/staging_dir/host
--exec-prefix=/home/chirag/open/n750/staging_dir/host
--sysconfdir=/home/chirag/open/n750/staging_dir/host/etc
--localstatedir=/home/chirag/open/n750/staging_dir/host/var
--sbindir=/home/chirag/open/n750/staging_dir/host/bin ; fi )
Usage:
cp [options] FILE DEST
cp [options] FILE1 [FILE2 ...] DEST-DIR

cp --help for options list


*cp: error: no such option: -p*
make[3]: ***
[/home/chirag/open/n750/build_dir/host/patch-2.7.1/.configured] Error 2
make[3]: Leaving directory `/home/chirag/open/n750/tools/patch'
make[2]: *** [tools/patch/compile] Error 2
make[2]: Leaving directory `/home/chirag/open/n750'
make[1]: ***
[/home/chirag/open/n750/staging_dir/target-mips_34kc_uClibc-0.9.33.2/stamp/.tools_install_n]
Error 2
make[1]: Leaving directory `/home/chirag/open/n750'
make: *** [world] Error 2

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

Re: [OpenWrt-Devel] Build fails at cp -fpR

[Chirag Chhatriwala]

On Wed, Jan 1, 2014 at 10:02 PM, Chirag Chhatriwala wrote:

> (cd /home/chirag/open/n750/build_dir/host/patch-2.7.1/; if [ -x configure
> ]; then cp -fpR /home/chirag/open/n750/scripts/config.{guess,sub}
> /home/chirag/open/n750/build_dir/host/patch-2.7.1// &&  /bin/bash
> ./configure CC="gcc" CFLAGS="-O2
> -I/home/chirag/open/n750/staging_dir/host/include"
> CPPFLAGS="-I/home/chirag/open/n750/staging_dir/host/include"
> LDFLAGS="-L/home/chirag/open/n750/staging_dir/host/lib" SHELL="/bin/bash"
> --target=x86_64-linux-gnu --host=x86_64-linux-gnu --build=x86_64-linux-gnu
> --program-prefix="" --program-suffix=""
> --prefix=/home/chirag/open/n750/staging_dir/host
> --exec-prefix=/home/chirag/open/n750/staging_dir/host
> --sysconfdir=/home/chirag/open/n750/staging_dir/host/etc
> --localstatedir=/home/chirag/open/n750/staging_dir/host/var
> --sbindir=/home/chirag/open/n750/staging_dir/host/bin ; fi )
>  Usage:
> cp [options] FILE DEST
> cp [options] FILE1 [FILE2 ...] DEST-DIR
>
> cp --help for options list
>
>
> *cp: error: no such option: -p*
>
>
Answering my own question after I found a response previously on the
Openwrt development threads:
https://lists.openwrt.org/pipermail/openwrt-users/2012-March/002066.html

the culprit, same the author's issue, was gcp, which was being preferred
over /bin/cp...
removed gcp and everything is working.

Hope this helps someone else as well. Not the ideal fix for people who need
to have both installed, should there be a patch to prefer cp and not use
gcp (if gcp is present as well).

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

Re: [OpenWrt-Devel] weak signal MyNet n600

[Chirag Chhatriwala]

On Sat, Dec 14, 2013 at 10:10 PM, omggo  wrote:

> about 2m away = 44% - Signal: -79 dBm, Noise: -95dBm
> right next to device = 82% - Signal -52 dBm, Noise: -95dBm
>
> On Sun, Dec 15, 2013 at 1:19 AM, Felix Fietkau  wrote:
>
>> On 2013-12-14 08:48, omggo wrote:
>> > Hi all,
>> >
>> > I'm currently using the latest trunk (r39047) with the "MyNet n600" and
>> > have noticed that the wifi signal on the is lower than the official
>> > firmware and will never reach 100% even with the device right next to
>> > the router.
>> >
>> > At about 2m away from the device the signal strength is about 45% on the
>> > 2.4ghz band and 85% on the 5ghz.
>> Signal strength values in % are meaningless. Please post the signal
>> strength in dBm instead.
>>
>> - Felix
>>
>

I think there is something wrong in the configuration as well.

Similar problem exhibited on the N750, which is nearly similar to N600 with
a different 802.11an chip.
My problem however, isn't that the device doesn't output enough power. I
see it just as strong as my other WiFi router through inSSIDer.

The problem I'm having is that the router doesn't properly see other
devices for their transmit power. For instance, my laptop which has
802.11bg WiFi card connects to the WD My Net N750 and sees great signal
when it is sitting next to the router. inSSIDer shows the router
broadcasting at about -20dbm sitting next to it. Same for when the laptop
connects to the Buffalo WZR-HP-AG300H or a Netgear WNDR3700v2.

However, there is a huge difference in what My Net N750 "sees" as the
laptop's WiFi signal strength, versus what my other two routers see the
laptop's broadcast/signal strength.

For example, the N750 while sitting next to the laptop, sees the laptop as
having a signal strength of -53dbm. Both my other routers see the laptop
broadcasting between -20dm ~ -30dbm depending on the antenna orientation.

There is definitely something weird going on with the way these My Net
Routers see signal strengths of 802.11bgn devices. Generally, the signal
strength is same on both ends (laptop and router). If inSSIDer shows the
router at about -30dbm, the router also sees the client device at about
-30dbm (give or take a few dBm's). Both the Buffalo WZR-HP-AG300H and
Netgear WNDR3700v2 show exhibit this behavior. The WD My Net N750 sees a
"huge signal drop" on 802.11bgn devices. I am guessing something similar is
happening on the WD My Net N600.

Fortunately, the 801.11an devices which connect to the My Net N750 don't
exhibit this problem.

Hope that we can get to the bottom of this issue.

Regards,
Chirag
___
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

[Chirag Chhatriwala]

Confirmed working on the WD MyNet N750.
Now the device is no longer "deaf".

This device broadcast stronger WiFi than any of my other routers.
Kudos to Felix for adding support for this device.




On Wed, Jan 8, 2014 at 12:42 AM, Steven Haigh  wrote:

> On 8/01/2014 2:44 PM, Weedy wrote:
> >
> > On 7 Jan 2014 21:30, "Steven Haigh"  > > 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  > >
> >> > ---
> >> >  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.
>
> Well, I actually noticed that in the n600 [PATCH 1/2] has this already -
> I've applied PATCH 1/2 and building now... Will advise.
>
> --
> 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] is anybody working on supporting Linksys WRT1900ac ?

[Chirag Chhatriwala]

>
> Hi,
>
> we talked about this internally and are not aware of any developer that
> was pinged by linksys. what we know so far
>
> * unit most likely runs on a ghz arm soc made by marvell
> * unit is about 1,5x the size of the original
> * the unit is really expensive - you can get a time capsule for that price
> with a 2TB disc or even a low end qnap
>
>
> lets see if they actually contact us or if it was a marketing hoax
>
> John
>

Not sure how I missed this thread. However, if they do end up working with
a few devs here on the OpenWrt team (fingers crossed), it would do wonders
for Belkin/Linksys brand as well as for the Marvell SoCs which have had
zero exposure to the open source community because of lack of drivers. I
never understood why Linksys (under Cisco) didn't capitalize on the
OpenSource Market after the huge success of the WRT54GL series. Linksys
(under Belkin) is appealing to its target end-users perfectly.

As an aside, this could potentially mean extended support for pre-existing
Linksys EA routers which are based off the Marvell SoC (maybe?).

Hope this isn't too good to be true.
Unless there are some NDAs involved, it would be great to hear some updates
on this subject.

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

Re: [OpenWrt-Devel] Android connectivity issues - MyNet n600

[Chirag Chhatriwala]

>
> I'm not sure how the issue got fixed with the non-android devices because
> they were doing the same thing on the 2.4ghz radio before a recent patch
> but I was hoping that this could have a similar fix.
>
>
>
If I may add a tidbit (and just as camden, I'm no expert either)...

That being said, I have a few android devices myself and while most of them
play nice, some of them are notorious for indicating a problem where none
exists (at least not with OpenWrt). However, given that trunk is always
changing, it might be a combination of OpenWrt changes and a badly written
kernel WiFi driver for the android device in question. For example, I own a
Google Nexus 4 and over the course of time, starting from the 10th
installment of android (Jelly Bean) through to the 11th (Kit-Kat), they
broke the 5 GHz WiFi on the 3-digit channels (149+). Not necessarily
Google's fault (but still Google's fault technically), because the related
WiFi code for the qualcomm msm itself if borked in that stock kernel. They
did fix the problem with delayed notification where any notification after
the screen went to sleep was delayed until the device was manually awakened
(caused by bad ARP translation offloading code). However, they introduced
horrible throughput on the 3-digit wifi channels (which is what I use in my
house).

What am I talking about? The Phone's 3-digit 5GHz wifi on the stock kernel
doesn't reach a download throughput anywhere higher than 12mbps (even
though it connects near at 65mbps). It definitely worked with stock 4.2.2
but not with 4.4.2. All my other Android devices are able saturate my WAN
connection throughput during speed tests, just not the nexus 4.
How do I know this? After trying out several other ROMs i figured out the
CyanogenMod (CM) uses a different code base (Code Aurora) and has a much
more functional WiFi at 5GHz than the one used by Google (Android Open
Source Project a.k.a AOSP). Problem is that qualcomm is done committing any
changes to the kernel used by AOSP (as far as I know), and their most
recent and functional WiFi code is available in Code Aurora (go figure
why...). To make matters worse, this isn't the case for all the devices. My
Dad's Nexus 5 doesn't have any issues with the stock AOSP/Google ROM.

So the bottom line is, android devices' WiFi performance is like a "baux
auf chaucklets" (read: box of chocolates), and you may be trying to look
for a solution in the wrong place. That being said, I'm sure debug
mode/TCPdump may be able to help you narrow down the issue. All I want to
point out is that it "might" turn out to be a dead-end (not saying it "is").

What I want to know is whether this problem exists with the router running
STOCK firmware from Western Digital. I have a Western Digital MyNet N750
(similar hardware maybe), and I have not had this issue. And even if such
an issue occurred, I'm more likely to blame Android's WiFi driver and not
OpenWrt, but hey that's just me. Also, do you have any other OpenWrt
compatible router where this problem doesn't occur?

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

Re: [OpenWrt-Devel] MyNET N750 - Actually turn the LNA on.

[Chirag Chhatriwala]

Very strange. I don't have the problem of the router being deaf anymore.
However further investigation into the code leads me to believe that the
value is never set to GPIOF_INIT_HIGH. Which is confusing. Or am I not
seeing the obvious?

ath79_wmac_set_ext_lna_gpio

calls

ar934x_set_ext_lna_gpio

calls

gpio_request_one  and sets to GPIOF_DIR_OUT | GPIOF_INIT_LOW for the
particular LNA GPIO. I reckon we need this to be GPIOF_INIT_HIGH in order
for this to be in line with Felix's original patch.

What bothers me is that if this patch isn't working, how is my device able
to hear other devices just fine.

I also agree with Felix, that value being passed in ath79_wmac_set_ext_lna_gpio
as 0 or 1 is simply cosmetic, to produce an output of LNA0 or LNA1. It IS
then later used to select AR934X_GPIO_OUT_EXT_LNA0
or AR934X_GPIO_OUT_EXT_LNA1 based on the provided value.

I got lost in the ath79_gpio_output_select (maybe this is where the magic
happens?)

Best Regards,
Chirag

PS I own 2 N750s and they run in WDS AP and WDS AP+CLIENT mode and the
devices see each other just fine.

On Thu, Feb 6, 2014 at 5:37 PM, Luis E. Garcia  wrote:

>
> Images found here:
> http://openwrt.crc.id.au/
>
>
> Steve
> The code you first sent was merged with revision 39213 for the N750.
> If I use your image with this patch ( the one marked ) r39211 - I can get
> connected with both radios. LuCI responds in a timely fashion.
> There is no lag when applying changes.
>
> They "cleaned up" the code in revision r39217, I couldn't find the
> definition for the function they're using "ath79_wmac_set_ext_lna_gpio"
> But all builds after that have issues with the radios, poor performance on
> the 5GHz radios - LuCI lags on the page that setups the WiFi radios.
>
> With the image you have as r39499 with the patch - the router behaves as
> with the r39213 with patch image. ( the first fix you sent )
>
> I wanted to verify the state of the GPIOs on the kernel under the running
> linux system - that is why I asked if there was a way to verify the State
> of the GPIOs in your blog.
>
> Luis Garcia
>
>
> ___
> 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] OpenWrt signaling early boot cycle (blinking LED) all the time on 1st boot

[Chirag Chhatriwala]

This is happening on my hardware/routers as well upon fresh install of
OpenWrt factory images (have not tested sysupgrade).
Hardware: WD My Net N750
LED keeps blinking during boot immediately after the flash and never stops
blinking (Until reboot).


On Fri, Feb 7, 2014 at 6:36 PM, Rafał Miłecki  wrote:

> I'm using bcm47xx.
>
> On the first boot after installation OpenWrt starts linking my LED and
> never stops. It starts around
> > Press the [f] key and hit [enter] to enter failsafe mode
> > Press the [1], [2], [3] or [4] key and hit [enter] to select the debug
> level
>
> Ofc I was waiting for few minutes, even after preparing JFFS2
> partition LED keeps blinking.
>
> On another boot this problem doesn't occur.
>
> My guess is that set_state (/etc/diag.sh) is never called with "done"
> argument on the first boot.
>
> --
> Rafał
> ___
> 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] MyNET N750 - Actually turn the LNA on.

[Chirag Chhatriwala]

On Sun, Feb 9, 2014 at 5:54 AM, Steven Haigh  wrote:

> Is there any further news on this?
>
> Its obviously helping some people - so the question is why?
>
> --
> 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
>
>
I just flashed r39535 without modifying any code.
I've attached my build procedure:
build_mynet.txt: commands issued to retrieve source code and then take
necessary steps to build
build_config_mynet.txt: I have a pre-determined set of packages I always
like to include. I just copy this file into the (as you will see in the
build_mynet.txt) and let make defconfig work its magic.

 So far, I haven't seen any issues with my routers not seeing any clients
or vice versa.
I run my WiFi as follows (country US):
2.4GHz Channel 3 HT40+ (noscan enabled)
5GHz Channel 149 HT40+ (noscan enabled)

I have two N750s as I've stated. None of them exhibit any issues.
I am still stumped as to the code
in 613-MIPS-ath79-add-ath79_wmac_setup_ext_lna_gpio-helper.patch (Line 28):

err = gpio_request_one(gpio, GPIOF_DIR_OUT | *GPIOF_INIT_LOW*, label);

Only one who can solve this mystery is Gabor since he refactored the code
and added this patch to initialize that particular GPIO with those flags.

Thanks,
Chirag
CONFIG_TARGET_ar71xx=y
CONFIG_TARGET_ar71xx_generic=y
CONFIG_TARGET_ar71xx_generic_MYNETN750=y

CONFIG_IMAGEOPT=y
CONFIG_PREINITOPT=y

CONFIG_PACKAGE_block-mount=y
CONFIG_BUSYBOX_CUSTOM=y
CONFIG_BUSYBOX_CONFIG_WHOAMI=y
CONFIG_PACKAGE_wireless-tools=y

CONFIG_PACKAGE_kmod-scsi-generic=y

CONFIG_PACKAGE_kmod-fs-ext4=y
CONFIG_PACKAGE_kmod-fs-ntfs=y
CONFIG_PACKAGE_kmod-fs-vfat=y

CONFIG_PACKAGE_kmod-ledtrig-usbdev=y

CONFIG_PACKAGE_kmod-nls-cp437=y
CONFIG_PACKAGE_kmod-nls-cp850=y
CONFIG_PACKAGE_kmod-nls-iso8859-1=y
CONFIG_PACKAGE_kmod-nls-utf8=y

CONFIG_PACKAGE_kmod-usb-ohci=y
CONFIG_PACKAGE_kmod-usb-storage-extras=y
CONFIG_PACKAGE_kmod-usb-uhci=y

CONFIG_ATH_USER_REGD=y

CONFIG_PACKAGE_luci=y
CONFIG_PACKAGE_luci-ssl=y
CONFIG_PACKAGE_luci-app-ddns=y
CONFIG_PACKAGE_luci-app-ntpc=y
CONFIG_PACKAGE_luci-app-upnp=y
CONFIG_PACKAGE_luci-theme-openwrt=y
CONFIG_PACKAGE_luci-sgi-uhttpd=y

CONFIG_PACKAGE_openssh-sftp-server=y

CONFIG_PACKAGE_asterisk11=y
CONFIG_PACKAGE_asterisk11-chan-motif=y
CONFIG_PACKAGE_asterisk11-codec-alaw=y
CONFIG_PACKAGE_asterisk11-codec-g722=y
CONFIG_PACKAGE_asterisk11-codec-gsm=y
CONFIG_PACKAGE_asterisk11-codec-ulaw=y
CONFIG_PACKAGE_asterisk11-func-cut=y
CONFIG_PACKAGE_asterisk11-func-db=y
CONFIG_PACKAGE_asterisk11-res-srtp=y
CONFIG_PACKAGE_asterisk11-res-xmpp=y
CONFIG_PACKAGE_asterisk11-sounds=y

CONFIG_PACKAGE_yate=y
CONFIG_PACKAGE_yate-mod-accfile=y
CONFIG_PACKAGE_yate-mod-gvoice=y
CONFIG_PACKAGE_yate-mod-jabberclient=y
CONFIG_PACKAGE_yate-mod-jbfeatures=y
CONFIG_PACKAGE_yate-mod-openssl=y
CONFIG_PACKAGE_yate-mod-regexroute=y
CONFIG_PACKAGE_yate-mod-regfile=y
CONFIG_PACKAGE_yate-mod-rmanager=y
CONFIG_PACKAGE_yate-mod-sipfeatures=y
CONFIG_PACKAGE_yate-mod-tonegen=y
CONFIG_PACKAGE_yate-mod-yjinglechan=y
CONFIG_PACKAGE_yate-mod-yrtpchan=y
CONFIG_PACKAGE_yate-mod-ysipchan=y
CONFIG_PACKAGE_yate-mod-ystunchan=y
CONFIG_PACKAGE_yate-sounds=y

CONFIG_PACKAGE_e2fsprogs=y
CONFIG_PACKAGE_ntfs-3g=y

CONFIG_PACKAGE_blkid=y
CONFIG_PACKAGE_fdisk=y
CONFIG_PACKAGE_swap-utils=y
# CONFIG_PACKAGE_coreutils is not set
# CONFIG_PACKAGE_coreutils-whoami is not set
CONFIG_PACKAGE_usbutils=y

CONFIG_PACKAGE_uboot-ar71xx-nbg460n_550n_550nh=y
git clone git://git.openwrt.org/openwrt.git mynet && \
cd mynet && \
./scripts/feeds update -a && \
./scripts/feeds install -a && \
cp ~/diskstation/router/configs/build_config_mynet.txt .config && \
make defconfig && \
grep = .config | sort > ~/mynet.txt.new && \
date && \
ionice -c 3 nice -n19 make -j 5 && \
date && \
cp bin/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-* 
~/diskstation/router/builds
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] is anybody working on supporting Linksys WRT1900ac ?

[Chirag Chhatriwala]

Why is everyone so gung-ho on this device? YES its interesting. YES we all
want to see support.
People are working on it (or so we think). We just saw a patch being
submitted. We will understand how open source Belkin wants to be by the
steps the take in response to the feedback on their first submitted patch.
Everyone needs to tone down on the kool-aid and get back to life as usual.

We'll know when there are people in the know want to tell us something.

Bye,
Chirag


On Mon, Apr 7, 2014 at 12:38 PM, Fernando Frediani wrote:

> That is very interesting.
>
> Does anyone know if the source code of the .ko module was finally provided
> by Belkin/Linksys ?
>
> Jose-Vasquez - Regarding your other email why there is so much interest on
> the WRT1900ac,, I think first because it was announced as a successor of
> the famous WRT54G, which  needless to say the importance of this in the
> start of the project. Also despite the fact other hardwares like TL-WDR7500
> are very interesting indeed, this one has its merits on the upcoming "ac"
> era and if Belkin/Linksys is truly interested to "work with OpenWRT
> developers" means, in theory, an always welcome contribution back to the
> project.
>
> Best regards,
>
> Fernando
>
>
>
> On 07/04/2014 14:32, Toke Høiland-Jørgensen wrote:
>
>> There was a patch posted from linksys last week:
>>
>> http://thread.gmane.org/gmane.comp.embedded.openwrt.devel/23500
>>
>> -Toke
>>
> ___
> 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] LAN "force_link" causes WDS Client routers to be no-longer administerable

[Chirag Chhatriwala]

Hello Felix and other devs,

I recently went from r39555 (BB) to r41055 (also BB) without sysupgrade,
direct update of firmware. I've got a couple of WD N750 Routers that I like
to run in WDS mode. After flashing 41055 and then configuring, WDS on the
routers, I was left completely locked out of the WDS Client router.

There were quite a few changes which I ruled out as the cause and
ultimately narrowed out the changeset in 40773 [1] causes WDS Client
Routers to stop being adminsterable via SSH or LuCI.

I'm not sure if this change warrants a trac ticket item so I emailed the
group as a heads-up. I can create a ticket if I don't hear back within a
couple of days.

Best Regards,
Chirag Chhatriwala
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] LAN "force_link" causes WDS Client routers to be no-longer administerable

[Chirag Chhatriwala]

On Mon, Jun 9, 2014 at 3:55 PM, Felix Fietkau  wrote:

> On 2014-06-09 21:37, Chirag Chhatriwala wrote:
> > Hello Felix and other devs,
> >
> > I recently went from r39555 (BB) to r41055 (also BB) without sysupgrade,
> > direct update of firmware. I've got a couple of WD N750 Routers that I
> > like to run in WDS mode. After flashing 41055 and then configuring, WDS
> > on the routers, I was left completely locked out of the WDS Client
> router.
> >
> > There were quite a few changes which I ruled out as the cause and
> > ultimately narrowed out the changeset in 40773 [1] causes WDS Client
> > Routers to stop being adminsterable via SSH or LuCI.
> >
> > I'm not sure if this change warrants a trac ticket item so I emailed the
> > group as a heads-up. I can create a ticket if I don't hear back within a
> > couple of days.
> I haven't seen anything similar in my own tests (and I've been using WDS
> as well). Please show me your configuration (network and wireless) so I
> can try to reproduce it.
>
> Thanks,
>
> - Felix
>
>
Hi Felix,

I've attached the /etc/config/network and /etc/config/wireless for both the
Main WDS Access Point (_ap files) and the 2ndary WDS Client+AP (_sta files).

Point to note that if I had went through a sysupgrade from (which I also
tried as well), this issue wouldn't manifest as r39555 did not yet make use
of "option force_link 1". In which case, there were no issues with the WDS
Client router receiving a proper IP and being accessible via SSH/LuCI.

Problem only occurred when I loaded a fresh install of r41055 on both WD
MyNet N750 routers and manually configured WDS in the AP and the Client
router.

Hope this helps,

Chirag


network_ap
Description: Binary data


wireless_ap
Description: Binary data


network_sta
Description: Binary data


wireless_sta
Description: Binary data


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

Re: [OpenWrt-Devel] How to rebuild exactly 12.09 from source?

[Chirag Chhatriwala]

I generally try to do the following:

1. perform a git clone on the branch or trunk.
2. perform "git log --grep="", grab the hashtag or commit id and
note the date and time of that checkin and perform a "git checkout ", this will create a detached HEAD and will leave you at the  and nothing after it.
3. if you are going to add feeds, you need to do something similar for the
feeds as well.. I.E. create a folder named "feeds" under your source and
checkout your feeds (most likely git based now).
4. for each feeds you checked out, perform a "git log
--before="-MM-DDThh:mm:ss+Zone" format
5. grab the latest commit id and perform a "git checkout "
(for each feed checked out)

This way you know that everything you are building is roughly the same age
as the latest svn commit that  you're trying to replicate. You may end up
missing a commit or two but you will be fairly close to building the
version you want. Its not exact science but it is close enough. Otherwise
you may end up checking out an old version of openwrt, but have it built
against the latest pacakges/luci/routing/telephony feeds and things may
(most likely will) break.

It used to be easier when everything was svn based and you could just
specify the svn id in your feeds in the format svn://feed.location@.
Things change so we adapt.

Hope this helps. Let me know if this is not clear.


Chirag



On Sat, Jun 21, 2014 at 8:54 AM, Nikolai Zhubr  wrote:

> 21.06.2014 14:39, Rafał Miłecki:
>
>  What about using tag in svn repo?
>> svn://svn.openwrt.org/openwrt/tags/attitude_adjustment_12.09/
>>
>
> I tried that, and although version.mk indeed stated 12.09, there is some
> discrepancy:
>
> - svn told me that it fetched r41293 this time;
> - the router flashed with this self-built 12.09 claimed it is r36422;
> - binary AA 12.09 from downloads.openwrt.org claims it is r36088.
>
> So I'm now closer, but still can't produce a build which would identify
> itself exactly as the official 12.09 release (12.09 r36088).
>
> Thank you,
> Nikolai
>
>
>
>> .
>>
>>  ___
> 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] How to rebuild exactly 12.09 from source?

[Chirag Chhatriwala]

Also, forgot to mention on small detail...

if you're using this approach, after checking out all the feeds, you will
need to manually run:

./scripts/feeds update -a -i
./scripts/feeds install -a

Don't forget to add the -i in the update. This way, the feeds on your
computer will be left in its current state and indices are created, etc.
Otherwise, it will try updating from git/svn.

Regards,

Chirag Chhatriwala


On Sat, Jun 21, 2014 at 3:59 PM, Chirag Chhatriwala 
wrote:

> I generally try to do the following:
>
> 1. perform a git clone on the branch or trunk.
> 2. perform "git log --grep="", grab the hashtag or commit id and
> note the date and time of that checkin and perform a "git checkout  id>", this will create a detached HEAD and will leave you at the  it> and nothing after it.
> 3. if you are going to add feeds, you need to do something similar for the
> feeds as well.. I.E. create a folder named "feeds" under your source and
> checkout your feeds (most likely git based now).
> 4. for each feeds you checked out, perform a "git log
> --before="-MM-DDThh:mm:ss+Zone" format
> 5. grab the latest commit id and perform a "git checkout "
> (for each feed checked out)
>
> This way you know that everything you are building is roughly the same age
> as the latest svn commit that  you're trying to replicate. You may end up
> missing a commit or two but you will be fairly close to building the
> version you want. Its not exact science but it is close enough. Otherwise
> you may end up checking out an old version of openwrt, but have it built
> against the latest pacakges/luci/routing/telephony feeds and things may
> (most likely will) break.
>
> It used to be easier when everything was svn based and you could just
> specify the svn id in your feeds in the format svn://feed.location@.
> Things change so we adapt.
>
> Hope this helps. Let me know if this is not clear.
>
>
> Chirag
>
>
>
> On Sat, Jun 21, 2014 at 8:54 AM, Nikolai Zhubr 
> wrote:
>
>> 21.06.2014 14:39, Rafał Miłecki:
>>
>>  What about using tag in svn repo?
>>> svn://svn.openwrt.org/openwrt/tags/attitude_adjustment_12.09/
>>>
>>
>> I tried that, and although version.mk indeed stated 12.09, there is some
>> discrepancy:
>>
>> - svn told me that it fetched r41293 this time;
>> - the router flashed with this self-built 12.09 claimed it is r36422;
>> - binary AA 12.09 from downloads.openwrt.org claims it is r36088.
>>
>> So I'm now closer, but still can't produce a build which would identify
>> itself exactly as the official 12.09 release (12.09 r36088).
>>
>> Thank you,
>> Nikolai
>>
>>
>>
>>> .
>>>
>>>  ___
>> 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] LAN "force_link" causes WDS Client routers to be no-longer administerable

[Chirag Chhatriwala]

Hello Felix,

Didn't hear back on an email I had sent a couple weeks ago so I'm following
up with a polite inquiry.
Were you able to reproduce the problem with your setup as I described?

Please let me know. If you would like, I will file a bug report on
dev.openwrt.org against trunk.

Thanks,
Chirag


On Mon, Jun 9, 2014 at 10:19 PM, Chirag Chhatriwala 
wrote:

> On Mon, Jun 9, 2014 at 3:55 PM, Felix Fietkau  wrote:
>
>> On 2014-06-09 21:37, Chirag Chhatriwala wrote:
>> > Hello Felix and other devs,
>> >
>> > I recently went from r39555 (BB) to r41055 (also BB) without sysupgrade,
>> > direct update of firmware. I've got a couple of WD N750 Routers that I
>> > like to run in WDS mode. After flashing 41055 and then configuring, WDS
>> > on the routers, I was left completely locked out of the WDS Client
>> router.
>> >
>> > There were quite a few changes which I ruled out as the cause and
>> > ultimately narrowed out the changeset in 40773 [1] causes WDS Client
>> > Routers to stop being adminsterable via SSH or LuCI.
>> >
>> > I'm not sure if this change warrants a trac ticket item so I emailed the
>> > group as a heads-up. I can create a ticket if I don't hear back within a
>> > couple of days.
>> I haven't seen anything similar in my own tests (and I've been using WDS
>> as well). Please show me your configuration (network and wireless) so I
>> can try to reproduce it.
>>
>> Thanks,
>>
>> - Felix
>>
>>
> Hi Felix,
>
> I've attached the /etc/config/network and /etc/config/wireless for both
> the Main WDS Access Point (_ap files) and the 2ndary WDS Client+AP (_sta
> files).
>
> Point to note that if I had went through a sysupgrade from (which I also
> tried as well), this issue wouldn't manifest as r39555 did not yet make use
> of "option force_link 1". In which case, there were no issues with the WDS
> Client router receiving a proper IP and being accessible via SSH/LuCI.
>
> Problem only occurred when I loaded a fresh install of r41055 on both WD
> MyNet N750 routers and manually configured WDS in the AP and the Client
> router.
>
> Hope this helps,
>
> Chirag
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel