from:"support"

Re: [OpenWrt-Devel] QCA9994 outdoor 13km link

2019-09-25 Thread support

Hi, 

In the beginning i was using 2 dishes on each side. They are ubiquiti 2x2 dual 
polarized dishes and i connected the chains of station in the same way as AP 
and i still had issues. After that i thought the problem might be because this 
card uses mimo multipath and AP ch0 should talk with station ch  0 1 2 3. With 
2x2 dishes that's not possible because 

DISH 1 

CH0 -H 

CH1 -V 

CH2 -H 

CH3 -V 

The station pigtails were connected in the same way as AP.  

In this configuration AP ch0 whish is Horizontal can talk only with station ch0 
and ch2. 

So i decided to go with Jiroues single polarity dishes on each side. You think 
that single polarity might be the problem but why it doesn't cause problems in 
routers when there are 4 omni antennas and still you can get datarates 866Mbps 
by phone(my phone is 2x2). The testing distance now is 5km but the distance 
where they will be installed is 13km. We also have dozens of ubiquiti and 
mikrotik links and 13km it's not a big deal.  

Today also i noticed something strange. The AP was openwrt and station was 
ddwrt and i got  433/866 and after changing the station to openwrt the 
datarates got worse. Ddwrt wasn't good either. It had datarates problem.  

Can it be something wrong with firmware antenna configuration? Why it shows 
only two antennas iw phy phy0 info? 

Thank you 

On Wed, Sep 25, 2019 at 6:34 PM +0200, "Koen Vandeputte" 
 wrote:

On 25.09.19 17:14, supp...@maxnet.al wrote:
> This is long distance, 5km with 4 dishes on each side. They are all 
> vertical and all chains have signal range -60 to -65.
>
> I don't have omni antennas. Is there a problem that i am using dishes?
>
>
I run dozens of long-range devices, and I'm seeing 2 issues in your setup:

1)

- Ack-to issues kick in starting from roughly 1000m.  When you cannot 
alter ack_to (coverage class), you will notice severe performance issues 
above 1000m

2)

- Using identical polarization on all chains is an absolute performance 
killer.

I have 2 devices,  both 2x2 802.11n, HT40 SGI, which are only 150m 
apart, all chains V polarized.

When running speedtests, inspecting ath9k rate control shows it is stuck 
at the max speed for 1 chain (iso 2)

In my case it means the absolute link rate is 130Mbit iso 270 in this 
configuration.

I can imagine using 4 chains will even reduce performance a lot more.

You should really try to use use H + V+ (-45) + (+45).

Also, ensure radio's at both sides have the chains on identical 
polarization. (Chain0 - V,  Chain1 - H, ..)

Regards,

Koen

>
> On Wed, Sep 25, 2019 at 5:11 PM +0200, "Ben Greear" 
> > wrote:
>
> Is this short distance or long?
>
> Please try short distance with omni antenna first to make sure you are 
> not hitting the delayed-ack issue
> or problems with your antenna.
>
> Change your antenna orientation so that they point in different 
> directions.
>
> Thanks,
> Ben
>
> On 9/25/19 6:49 AM, supp...@maxnet.al wrote:
> > Hello,
> > 
> > Today i managed to connect the station wds at 80MHz channel. Signal is 
> -56 and i have very low datarates. I have attached a photo.
> > 
> >   When station was ddwrt and AP openwrt the datarates were 866/433. TX 
> won't do more than VHT-NSS 1 although RX it's not good either because it's a 
> 4 chain 
> > radio and it should do VHT-NSS4.
> > 
> > Thank you,
> > Klevis
> > 
> > 
> > 
> > 
> > On Mon, Sep 23, 2019 at 6:36 PM +0200, "Ben Greear" > wrote: > > Weeks 
> or months or whenever I have time, and maybe
> sooner if someone > wants to sponsor it. Please understand I, and
> probably everyone else working > on OpenWRT, am busy with lots of
> other projects and community work often > gets pushed to the back
> burner. > > Thanks, > Ben > > On 9/23/19 8:18 AM,
> supp...@maxnet.al wrote: > > Hi Ben, > > > > When do you think you
> might be able to make those changes to your driver? > > > >
> Thanks, > > Klevis. > > > > > > > > On 2019-09-20 13:00, Ben
> Greear wrote: > >> On 9/20/19 12:55 PM, Vincent Wiemann wrote: >
> >>> Hi Klevis, > >>> > >>> have you tried it with a short
> distance? > >>> If you did you should better ask Ben Greear
> directly. > >> > >> I asked him to post publicly so that others
> can help answer and that > >> my own answers might > >> help
> someone else. > >> > >> I have some patches that should enable
> coverage class settings for > >> wave-2, but I am too busy > >>
> with other things right now to port them to my ath10k-ct
> driver/firmware. > >> > >> Thanks, > >> Ben > >> > >>> > >>> By
> the way ath10k gen 2 chipsets don't work very well with long
> distance links without a > >>> special feature which
> implementation is only available to companies like Ubiquiti and
> very few > >>> people who have an own reverse-engineered
>

Re: [OpenWrt-Devel] QCA9994 outdoor 13km link

2019-09-25 Thread support

This is long distance, 5km with 4 dishes on each side. They are all vertical 
and all chains have signal range -60 to -65. 




I don't have omni antennas. Is there a problem that i am using dishes? 




On Wed, Sep 25, 2019 at 5:11 PM +0200, "Ben Greear"  
wrote:










Is this short distance or long?

Please try short distance with omni antenna first to make sure you are not 
hitting the delayed-ack issue
or problems with your antenna.

Change your antenna orientation so that they point in different directions.

Thanks,
Ben

On 9/25/19 6:49 AM, supp...@maxnet.al wrote:
> Hello,
> 
> Today i managed to connect the station wds at 80MHz channel. Signal is -56 
> and i have very low datarates. I have attached a photo.
> 
>   When station was ddwrt and AP openwrt the datarates were 866/433. TX won't 
> do more than VHT-NSS 1 although RX it's not good either because it's a 4 
> chain 
> radio and it should do VHT-NSS4.
> 
> Thank you,
> Klevis
> 
> 
> 
> 
> On Mon, Sep 23, 2019 at 6:36 PM +0200, "Ben Greear" > wrote:
> 
> Weeks or months or whenever I have time, and maybe sooner if someone
> wants to sponsor it.  Please understand I, and probably everyone else 
> working
> on OpenWRT, am busy with lots of other projects and community work often
> gets pushed to the back burner.
> 
> Thanks,
> Ben
> 
> On 9/23/19 8:18 AM, supp...@maxnet.al wrote:
> > Hi Ben,
> > 
> > When do you think you might be able to make those changes to your 
> driver?
> > 
> > Thanks,
> > Klevis.
> > 
> > 
> > 
> > On 2019-09-20 13:00, Ben Greear wrote:
> >> On 9/20/19 12:55 PM, Vincent Wiemann wrote:
> >>> Hi Klevis,
> >>>
> >>> have you tried it with a short distance?
> >>> If you did you should better ask Ben Greear directly.
> >>
> >> I asked him to post publicly so that others can help answer and that
> >> my own answers might
> >> help someone else.
> >>
> >> I have some patches that should enable coverage class settings for
> >> wave-2, but I am too busy
> >> with other things right now to port them to my ath10k-ct 
> driver/firmware.
> >>
> >> Thanks,
> >> Ben
> >>
> >>>
> >>> By the way ath10k gen 2 chipsets don't work very well with long 
> distance links without a
> >>> special feature which implementation is only available to companies 
> like Ubiquiti and very few
> >>> people who have an own reverse-engineered implementation.
> >>> It works on IPQ401X, QCA9886 and QCA9888 based chips only.
> >>>
> >>> And it is not possible to set a coverage class for gen 2 devices, yet 
> as far as I know due to missing
> >>> documentation and implementation (correct me if that information is 
> outdated).
> >>> Furthermore a high channel width often results in problems
> >>> due to lower receiver sensibility.
> >>> We have better experiences with lower channel widths and sometimes 
> get more throughput with that.
> >>>
> >>> Actually I think this does not explain your connection issues as 13 
> km is not that much.
> >>>
> >>> Regards,
> >>>
> >>> Vincent Wiemann
> >>>
> >>> On 20.09.19 18:30, supp...@maxnet.al wrote:
>  Hello everyone,
> 
>  I am trying to setup a custom made outdoor link with Apu2d2 board 
> devices and QCA9994 cards from compex. After i installed openwrt and ath10k 
> ct driver, 
>  kmod ath10k and board-2.bin the device can run a 80MHz channel in 
> WDS AP. The problem is that it won't run as station or station wds. It can 
> scan
>  the SSIDs but won't connect them.
> 
>  Any suggestion?
> 
>  Thank you!
>  Klevis
> 
> >>>
> >>> ___
> >>> openwrt-devel mailing list
> >>> openwrt-devel@lists.openwrt.org
> >>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> >>>
> > 
> 
> 
> -- 
> Ben GreearCandela Technologies Inc http://www.candelatech.com
> 


-- 
Ben Greear 
Candela Technologies Inc  http://www.candelatech.com






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

Re: [OpenWrt-Devel] QCA9994 outdoor 13km link

2019-09-25 Thread support

Hello,
Today i managed to connect the station wds at 80MHz channel. Signal is -56 and 
i have very low datarates. I have attached a photo.
 When station was ddwrt and AP openwrt the datarates were 866/433. TX won't do 
more than VHT-NSS 1 although RX it's not good either because it's a 4 chain 
radio and it should do VHT-NSS4.
Thank you,Klevis

On Mon, Sep 23, 2019 at 6:36 PM +0200, "Ben Greear"  
wrote:

Weeks or months or whenever I have time, and maybe sooner if someone
wants to sponsor it.  Please understand I, and probably everyone else working
on OpenWRT, am busy with lots of other projects and community work often
gets pushed to the back burner.

Thanks,
Ben

On 9/23/19 8:18 AM, supp...@maxnet.al wrote:
> Hi Ben,
> 
> When do you think you might be able to make those changes to your driver?
> 
> Thanks,
> Klevis.
> 
> 
> 
> On 2019-09-20 13:00, Ben Greear wrote:
>> On 9/20/19 12:55 PM, Vincent Wiemann wrote:
>>> Hi Klevis,
>>>
>>> have you tried it with a short distance?
>>> If you did you should better ask Ben Greear directly.
>>
>> I asked him to post publicly so that others can help answer and that
>> my own answers might
>> help someone else.
>>
>> I have some patches that should enable coverage class settings for
>> wave-2, but I am too busy
>> with other things right now to port them to my ath10k-ct driver/firmware.
>>
>> Thanks,
>> Ben
>>
>>>
>>> By the way ath10k gen 2 chipsets don't work very well with long distance 
>>> links without a
>>> special feature which implementation is only available to companies like 
>>> Ubiquiti and very few
>>> people who have an own reverse-engineered implementation.
>>> It works on IPQ401X, QCA9886 and QCA9888 based chips only.
>>>
>>> And it is not possible to set a coverage class for gen 2 devices, yet as 
>>> far as I know due to missing
>>> documentation and implementation (correct me if that information is 
>>> outdated).
>>> Furthermore a high channel width often results in problems
>>> due to lower receiver sensibility.
>>> We have better experiences with lower channel widths and sometimes get more 
>>> throughput with that.
>>>
>>> Actually I think this does not explain your connection issues as 13 km is 
>>> not that much.
>>>
>>> Regards,
>>>
>>> Vincent Wiemann
>>>
>>> On 20.09.19 18:30, supp...@maxnet.al wrote:
 Hello everyone,

 I am trying to setup a custom made outdoor link with Apu2d2 board devices 
 and QCA9994 cards from compex. After i installed openwrt and ath10k ct 
 driver, 
 kmod ath10k and board-2.bin the device can run a 80MHz channel in WDS AP. 
 The problem is that it won't run as station or station wds. It can scan
 the SSIDs but won't connect them.

 Any suggestion?

 Thank you!
 Klevis

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

-- 
Ben Greear 
Candela Technologies Inc  http://www.candelatech.com

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

Re: [OpenWrt-Devel] QCA9994 outdoor 13km link

2019-09-23 Thread support


Hi Ben,

When do you think you might be able to make those changes to your 
driver?


Thanks,
Klevis.



On 2019-09-20 13:00, Ben Greear wrote:

On 9/20/19 12:55 PM, Vincent Wiemann wrote:

Hi Klevis,

have you tried it with a short distance?
If you did you should better ask Ben Greear directly.


I asked him to post publicly so that others can help answer and that
my own answers might
help someone else.

I have some patches that should enable coverage class settings for
wave-2, but I am too busy
with other things right now to port them to my ath10k-ct 
driver/firmware.


Thanks,
Ben



By the way ath10k gen 2 chipsets don't work very well with long 
distance links without a
special feature which implementation is only available to companies 
like Ubiquiti and very few

people who have an own reverse-engineered implementation.
It works on IPQ401X, QCA9886 and QCA9888 based chips only.

And it is not possible to set a coverage class for gen 2 devices, yet 
as far as I know due to missing
documentation and implementation (correct me if that information is 
outdated).

Furthermore a high channel width often results in problems
due to lower receiver sensibility.
We have better experiences with lower channel widths and sometimes get 
more throughput with that.


Actually I think this does not explain your connection issues as 13 km 
is not that much.


Regards,

Vincent Wiemann

On 20.09.19 18:30, supp...@maxnet.al wrote:

Hello everyone,

I am trying to setup a custom made outdoor link with Apu2d2 board 
devices and QCA9994 cards from compex. After i installed openwrt and 
ath10k ct driver, kmod ath10k and board-2.bin the device can run a 
80MHz channel in WDS AP. The problem is that it won't run as station 
or station wds. It can scan

the SSIDs but won't connect them.

Any suggestion?

Thank you!
Klevis



___
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] QCA9994 outdoor 13km link

2019-09-20 Thread support

Hi Ben,




When do you think you can port those changes to your firmware?




Thank you for your support.


Klevis.




On Fri, Sep 20, 2019 at 10:01 PM +0200, "Ben Greear"  
wrote:










On 9/20/19 12:55 PM, Vincent Wiemann wrote:
> Hi Klevis,
> 
> have you tried it with a short distance?
> If you did you should better ask Ben Greear directly.

I asked him to post publicly so that others can help answer and that my own 
answers might
help someone else.

I have some patches that should enable coverage class settings for wave-2, but 
I am too busy
with other things right now to port them to my ath10k-ct driver/firmware.

Thanks,
Ben

> 
> By the way ath10k gen 2 chipsets don't work very well with long distance 
> links without a
> special feature which implementation is only available to companies like 
> Ubiquiti and very few
> people who have an own reverse-engineered implementation.
> It works on IPQ401X, QCA9886 and QCA9888 based chips only.
> 
> And it is not possible to set a coverage class for gen 2 devices, yet as far 
> as I know due to missing
> documentation and implementation (correct me if that information is outdated).
> Furthermore a high channel width often results in problems
> due to lower receiver sensibility.
> We have better experiences with lower channel widths and sometimes get more 
> throughput with that.
> 
> Actually I think this does not explain your connection issues as 13 km is not 
> that much.
> 
> Regards,
> 
> Vincent Wiemann
> 
> On 20.09.19 18:30, supp...@maxnet.al wrote:
>> Hello everyone,
>>
>> I am trying to setup a custom made outdoor link with Apu2d2 board devices 
>> and QCA9994 cards from compex. After i installed openwrt and ath10k ct 
>> driver, kmod ath10k and board-2.bin the device can run a 80MHz channel in 
>> WDS AP. The problem is that it won't run as station or station wds. It can 
>> scan
>> the SSIDs but won't connect them.
>>
>> Any suggestion?
>>
>> Thank you!
>> Klevis
>>
> 
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> 


-- 
Ben Greear 
Candela Technologies Inc  http://www.candelatech.com






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

Re: [OpenWrt-Devel] QCA9994 outdoor 13km link

2019-09-20 Thread support

Hi Vincent,

I have tried short distance with ddwrt and i get 1733/1733 datarates and about 
1Gbps real traffic using iperf. Ubiquiti and MikroTik have 80MHz outdoor radios 
and they work good. I don't want to use 160MHz which is very wide and there are 
lot of 20MHz channels within that will create interferences. Actually i want to 
benefit from VHT-NSS4 so at 80MHz channel i will get 1560Mbps. Ben Greear also 
thinks that is something wrong with ACK timing.From: Vincent Wiemann 

Sent: Friday, 20 September 2019, 21:56
To: supp...@maxnet.al; openwrt-devel@lists.openwrt.org
Subject: Re: [OpenWrt-Devel] QCA9994 outdoor 13km link

Hi Klevis,

have you tried it with a short distance?
If you did you should better ask Ben Greear directly.

By the way ath10k gen 2 chipsets don't work very well with long distance links 
without a
special feature which implementation is only available to companies like 
Ubiquiti and very few
people who have an own reverse-engineered implementation.
It works on IPQ401X, QCA9886 and QCA9888 based chips only.

And it is not possible to set a coverage class for gen 2 devices, yet as far as 
I know due to missing
documentation and implementation (correct me if that information is outdated).
Furthermore a high channel width often results in problems
due to lower receiver sensibility.
We have better experiences with lower channel widths and sometimes get more 
throughput with that.

Actually I think this does not explain your connection issues as 13 km is not 
that much.

Regards,

Vincent Wiemann

On 20.09.19 18:30, supp...@maxnet.al wrote:
> Hello everyone,
> 
> I am trying to setup a custom made outdoor link with Apu2d2 board devices and 
> QCA9994 cards from compex. After i installed openwrt and ath10k ct driver, 
> kmod ath10k and board-2.bin the device can run a 80MHz channel in WDS AP. The 
> problem is that it won't run as station or station wds. It can scan
> the SSIDs but won't connect them. 
> 
> Any suggestion?
> 
> Thank you!
> Klevis
> 

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

[OpenWrt-Devel] QCA9994 outdoor 13km link

2019-09-20 Thread support

Hello everyone,
I am trying to setup a custom made outdoor link with Apu2d2 board devices and 
QCA9994 cards from compex. After i installed openwrt and ath10k ct driver, kmod 
ath10k and board-2.bin the device can run a 80MHz channel in WDS AP. The 
problem is that it won't run as station or station wds. It can scan the SSIDs 
but won't connect them. 
Any suggestion?
Thank you!Klevis

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

Re: [OpenWrt-Devel] [PATCH CC 25/32] ar71xx: compex wpj531 fix setting mac address on ethernet

2016-03-22 Thread Andrew | PolkaSpots Support

Do you reckon the same issue is affecting the wpj344?

On Tue, 2016-03-01 at 04:06 +0100, Matthias Schiffer wrote:
> Signed-off-by: Christian Mehlis 
> 
> Backport of r46282
> ---
>  target/linux/ar71xx/files/arch/mips/ath79/mach-wpj531.c | 11 +--
> 
>  1 file changed, 5 insertions(+), 6 deletions(-)
> 
> diff --git a/target/linux/ar71xx/files/arch/mips/ath79/mach-wpj531.c
> b/target/linux/ar71xx/files/arch/mips/ath79/mach-wpj531.c
> index b106917..2cc2fe8 100644
> --- a/target/linux/ar71xx/files/arch/mips/ath79/mach-wpj531.c
> +++ b/target/linux/ar71xx/files/arch/mips/ath79/mach-wpj531.c
> @@ -94,9 +94,8 @@ static struct gpio_keys_button wpj531_gpio_keys[]
> __initdata = {
>  
>  static void __init common_setup(void)
>  {
> - u8 *mac = (u8 *) KSEG1ADDR(0x1f01fc00);
> - u8 *ee = (u8 *) KSEG1ADDR(0x1fff1000);
> - u8 tmpmac[ETH_ALEN];
> + u8 *art = (u8 *) KSEG1ADDR(0x1fff);
> + u8 *mac = (u8 *) KSEG1ADDR(0x1f02e000);
>  
>   ath79_register_m25p80(NULL);
>  
> @@ -109,7 +108,7 @@ static void __init common_setup(void)
>   ath79_eth0_data.phy_if_mode = PHY_INTERFACE_MODE_MII;
>   ath79_eth0_data.speed = SPEED_100;
>   ath79_eth0_data.phy_mask = BIT(4);
> - ath79_init_mac(ath79_eth0_data.mac_addr, mac, 0);
> + ath79_init_mac(ath79_eth0_data.mac_addr, mac +
> WPJ531_MAC0_OFFSET, 0);
>   ath79_register_eth(0);
>  
>   /* WAN */
> @@ -118,10 +117,10 @@ static void __init common_setup(void)
>   ath79_eth1_data.phy_if_mode = PHY_INTERFACE_MODE_GMII;
>   ath79_eth1_data.speed = SPEED_1000;
>   ath79_switch_data.phy_poll_mask |= BIT(4);
> - ath79_init_mac(ath79_eth1_data.mac_addr, mac, 1);
> + ath79_init_mac(ath79_eth1_data.mac_addr, mac +
> WPJ531_MAC1_OFFSET, 0);
>   ath79_register_eth(1);
>  
> - ath79_register_wmac(ee, tmpmac);
> + ath79_register_wmac(art + WPJ531_WMAC_CALDATA_OFFSET, NULL);
>  
>   ath79_register_pci();
>  }
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] 15.05.1 - Chaos Calmer

2016-03-19 Thread Andrew | PolkaSpots Support

Well done!
Is that included in the main 15.05 openwrt git branch? or is it a
different one?
https://git.openwrt.org/?p=15.05/openwrt.git;a=summary

Cheers

On Wed, 2016-03-16 at 13:06 +0100, John Crispin wrote:
> The OpenWrt developers are proud to announce the minor fix release of
> OpenWrt Chaos Calmer.
> 
>___ __
>  |   |.-.-.-.|  |  |  |..|  |_
>  |   -   ||  _  |  -__| ||  |  |  ||   _||   _|
>  |___||   __|_|__|__||||__|  ||
>   |__| W I R E L E S S   F R E E D O M
>  -
>  CHAOS CALMER (15.05.1)
>  -
>   * 1 1/2 oz GinShake with a glassful
>   * 1/4 oz Triple Sec   of broken ice and pour
>   * 3/4 oz Lime Juice   unstrained into a goblet.
>   * 1 1/2 oz Orange Juice
>   * 1 tsp. Grenadine Syrup
>  -
> 
>  -
> http://downloads.openwrt.org/chaos_calmer/15.05.1/
> 
> 
> ** Highlights since Chaos Calmer 15.05 **
> 
> * Linux kernel updated to version 3.18.23
> * Security fixes:
> - kernel: fix keyring reference leak (CVE-2016-0728)
> - openssl updated to 1.0.2f
> - hostapd security fixes
> - samba36 (CVE patches from 2015-12-16)
> * Update of netifd, procd, uci, rpcd, ubox & uhttpd
> * Driver updates
> - ledtrig-netdev: fix possible deadlock
> - bcm47xxpart: fix bcm53xx booting on NAND with badblocks
> - brcmfmac: fix getting/setting TX power, add stations dumping
> and
> support beamforming
> - 8139c: backport v4.3 fixes
> - backport spi layer fixes from v4.2+
> - solos-pci: increase headroom on RX
> - xrx200-net: fix port mirroring issues
> - update mac80211 (adding mt76)
> * Support for new devices:
> - Linksys WRT1900ACS (mvebu)
> - D-LINK DIR-615 rev. Ix (ar71xx)
> - LinkIt Smart7688 (ramips)
> - Gainstrong MiniBox v1.0 (ar71xx)
> - ZBT WG2626 (ramips)
> - TP-LINK TL-WR841N/ND v10 (ar71xx)
> - TL-WR741ND v5 (ar71xx)
> - WR740N v5.0 (ar71xx)
> - TP-LINK TL-WR941ND v6 international version (ar71xx)
> * Improved support for existing devices:
> - Netgear R8000: USB power and CPU speed
> - RapsberryPi: Add sysupgrade support
> * Kernel fixes
> - ramoverlay
> - multicast-to-unicast
> - ip6_fragment related skb_leak
> * Package fixes
> - igmpproxy: spurious restart issues
> 
> Have fun!
> The OpenWrt developer team
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH v4 1/2] Add ubnt_hsr platform flag and enable for UniFi Outdoor Plus

2016-02-19 Thread Andrew | PolkaSpots Support

The ubnt pro and outdoor+ have a different factory TFTP firmware.
Let me know if you need that, however you should be able to recover
with the openwrt one.
Still digging through the commit loggs for trunk, can't see the patch.
Am I missing something?

Cheers,
A
On Mon, 2015-12-14 at 12:54 +0100, Stefan Rompf wrote:
> Hi Tim,
> 
> > The auto-built image of 9 December 2015 for this device results in
> > a
> > bricked state. TFTP recovery with a stock recovery firmware from
> > Ubiquity does not allow the device to boot either.
> 
> try flashing the chaos calmer factory image with TFTP
> (openwrt-15.05-ar71xx-generic-ubnt-unifi-outdoor-plus-squashfs
> -factory.bin)
> 
> This has allowed me to recover a bricked Outdoor Plus. Flashing the
> Ubiquiti 
> firmware via TFTP didn't work for me either.
> 
> > but if anyone wants this device as a donation to get it
> > supported by OpenWRT, please let me know.
> 
> Well on one hand I'd be interested because the access point I had is
> mounted 
> onsite now and therefore not available for hacking anymore.
> 
> On the other hand, I got the impression that mine and Kyrills patches
> were not 
> too welcome, so I'm a bit hesitant to invest more time.
> 
> So good luck with unbricking, may be the device gets usable for your
> again!
> 
> Stefan
> ___
> 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] QCA9994 outdoor 13km link

Re: [OpenWrt-Devel] QCA9994 outdoor 13km link

Re: [OpenWrt-Devel] QCA9994 outdoor 13km link

Re: [OpenWrt-Devel] QCA9994 outdoor 13km link

Re: [OpenWrt-Devel] QCA9994 outdoor 13km link

Re: [OpenWrt-Devel] QCA9994 outdoor 13km link

[OpenWrt-Devel] QCA9994 outdoor 13km link

Re: [OpenWrt-Devel] [PATCH CC 25/32] ar71xx: compex wpj531 fix setting mac address on ethernet

Re: [OpenWrt-Devel] 15.05.1 - Chaos Calmer

Re: [OpenWrt-Devel] [PATCH v4 1/2] Add ubnt_hsr platform flag and enable for UniFi Outdoor Plus

10 matches

Site Navigation

Mail list logo

Footer information