Re: [OpenWrt-Devel] Advice needed - Proper approach to port 5G/LTE modem into OpenWRT

2020-04-27 Thread Bruno Antunes 
Hello Jeonghum,
Can you share some details on the boards and modems you are using?

Regards,
Bruno

On Mon, 27 Apr 2020 at 13:42, Bjørn Mork  wrote:
>
> Jeonghum Joh  writes:
>
> > I am porting a 5G/LTE modem into OpenWRT.
>
> Follow the instructions for LTE modems.  A 5G modem is pretty much the
> same wrt drivers and basic management.  At least for Qualcomm based
> modems on a USB bus.  Have no experience with anything else.  The Intel
> and Huawei modems are competely unknown to me, and most likely
> unsupported for the forseeable future.  And I'm also blank on the magic
> of Qualcomms PCIe interface. Qualcomm did work on a driver, but it's
> been a long time since I saw any update on that.  I guess no one cares
> enough.  SuperSpeed USB is fine for most users for now.
>
> Anyway, several X55 based modems are already supported out of the box in
> OpenWrt master.  There is no need to reinvent the wheel if you are using
> one of those.
>
> You may obviously decide to implement your own alternative solutions,
> like using some vendor software. But that will limit the user community
> severely. At least until the solution attracts more users.  And
> community support depends on users, which I believe is something you
> should consider since you have ended up in this forum.  You are unlikely
> to find anyone here who have any experience with your particular vendor
> software version.
>
> Personally, I am happy to give advice about anything regardless of
> experience.  But the quality of that advice is probably a tiny bit
> better when it is based on something I've tried myself.  Or maybe not?
> Is probably bad in any case.
>
>
> Bjørn
>
> ___
> 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] ATH10K VLAN firmware issue

2017-02-21 Thread Bruno Antunes 
On 21 February 2017 at 13:42, Tom Psyborg  wrote:
> have you tried this one
> https://forum.lede-project.org/t/new-qca988x-firmware-with-mesh-support/1587

From my testing it does not work.

>
> On 21 February 2017 at 14:19, Valo, Kalle  wrote:
>>
>> voncken  writes:
>>
>> > Do you know if the firmware team planned to fix the VLAN issue on ath10k
>> > firmware?
>>
>> I reported it forward only this week.
>>
>> --
>> Kalle Valo
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
>
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] ATH10K VLAN firmware issue

2016-11-15 Thread Bruno Antunes 
On 15 November 2016 at 14:55, Ben Greear <gree...@candelatech.com> wrote:
> The beta-18 release on my web page has the fix and should work fine.
>
> Probably soon I will promote the beta-18 to final release
> status.  Any help in testing and verifying the beta works well
> is welcome.

I will also do testing with that version.

For clarity can I refer you and your firmware releases in the bug report?

Thanks,
Bruno
>
> Thanks,
> Ben
>
> On 11/15/2016 06:37 AM, voncken wrote:
>>
>> Hi Ben,
>>
>> Do you plan to release a candelatech firmware with this fix?
>>
>> Regards.
>>
>> Cedric Voncken.
>>>
>>> -Message d'origine-
>>> De : linux-wireless-ow...@vger.kernel.org [mailto:linux-wireless-
>>> ow...@vger.kernel.org] De la part de Ben Greear
>>> Envoyé : samedi 5 novembre 2016 15:35
>>> À : Sebastian Gottschall; yu-chieh kung; Bruno Antunes
>>> Cc : Mauro Mozzarelli; linux-wirel...@vger.kernel.org; OpenWrt
>>> Development List; ath...@lists.infradead.org
>>> Objet : Re: [OpenWrt-Devel] ATH10K VLAN firmware issue
>>>
>>>
>>> Looks to me like 10.4 defaults to the right value, but possibly there
>>> are other issues with it.  I tested my CT 10.4 and it worked OK with
>>> vlans for me.
>>>
>>> Thanks,
>>> Ben
>>>
>>> On 11/05/2016 01:05 AM, Sebastian Gottschall wrote:
>>>>
>>>> would be good if qca can fix this bug finally in all available
>>>> firmwares. its a very annoying issue since a long time
>>>>
>>>> Sebastian
>>>>
>>>>
>>>> Am 04.11.2016 um 23:23 schrieb Ben Greear:
>>>>>
>>>>> The bug appears that vlan-tx-stripping is unconditionally enabled in
>>>>> at least my firmware.  I have re-compiled w/out that flag set, and
>>>
>>> it
>>>>>
>>>>> appears to work for me.
>>>>>
>>>>> Please download this firmware, rename it firmware-2.bin, make sure
>>>>> you remove/rename any firmware-5.bin (etc) so mine will load, and
>>>
>>> see if that fixes your problem.
>>>>>
>>>>>
>>>>> Please note that it is very likely you will have to use same MAC
>>>>> address for the VLAN devices that the underlying station uses in
>>>
>>> order for this to work.
>>>>>
>>>>>
>>>>> https://www.candelatech.com/downloads/tmp/firmware-2-full-
>>>
>>> community.b
>>>>>
>>>>> in
>>>>>
>>>>>
>>>>> Thanks,
>>>>> Ben
>>>>>
>>>>>
>>>>> On 11/04/2016 02:50 PM, Ben Greear wrote:
>>>>>>
>>>>>> I can reproduce this in my CT firmware. I'll see if I can fix it,
>>>>>> but for stock firmware, it might be that changing the driver to use
>>>>>> Ethernet packet type of native-wifi would make .1q vlans work.
>>>>>>
>>>>>> Thanks,
>>>>>> Ben
>>>>>>
>>>>>> On 11/04/2016 10:28 AM, yu-chieh kung wrote:
>>>>>>>
>>>>>>> I met the same problem before,
>>>>>>> if i modify the 1q header to other value (0xaa00) before go into
>>>
>>> firmware.
>>>>>>>
>>>>>>> I can capture the packet in the air I think the vlan packet is
>>>>>>> dropped in firmware.
>>>>>>>
>>>>>>> 2016-11-04 22:41 GMT+08:00 Bruno Antunes <baantu...@gmail.com>:
>>>>>>>>
>>>>>>>> On 4 November 2016 at 14:18, Mauro Mozzarelli
>>>
>>> <open...@ezplanet.net> wrote:
>>>>>>>>>
>>>>>>>>> Since the capability is implemented in software you might be
>>>>>>>>> testing the limit of your router's CPU i/o speed.
>>>>>>>>
>>>>>>>>
>>>>>>>> By loading the module in rawmode?
>>>>>>>>
>>>>>>>> The AP is an APU and Sta is an APU2.
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 04/11/16 14:13, Bruno Antunes wrote:
>>>>>>>>

Re: [OpenWrt-Devel] ATH10K VLAN firmware issue

2016-11-15 Thread Bruno Antunes 
On 15 November 2016 at 13:43, Valo, Kalle <kv...@qca.qualcomm.com> wrote:
> Bruno Antunes <baantu...@gmail.com> writes:
>
>> On 7 November 2016 at 18:06, Valo, Kalle <kv...@qca.qualcomm.com> wrote:
>>> Bruno Antunes <baantu...@gmail.com> writes:
>>>
>>>> On 4 November 2016 at 21:17, Valo, Kalle <kv...@qca.qualcomm.com> wrote:
>>>>
>>>>> Can someone file a bug to bugzilla about this so that all the info is
>>>>> properly stored? The more comprehensive the report is the better.
>>>>>
>>>>> https://bugzilla.kernel.org/
>>>>
>>>> I will file a bug report.
>>>
>>> Thanks, it's good to store all in one place so that it's easier to find
>>> the relevant info.
>>
>> Just file the bug with the ID 187241 - VLAN support in ATH10k Feel
>> free to ask for adicional info. I did not mention any names in the bug
>> report fell free to take credit if wanted.
>
> Thanks. I'll report it to the firmware team, let's see what happens. If
> there's more information which might help to fix this feel free to
> update that to the bug report.

I'm finishing my tests and will update the bug report ASAP.

Turns out the bad throughput was the result of a failure in the switch port.

With Ben's firmware the VLAN support is working fine with security.

Thanks,
Bruno
>
> https://bugzilla.kernel.org/show_bug.cgi?id=187241
>
> --
> Kalle Valo
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] ATH10K VLAN firmware issue

2016-11-07 Thread Bruno Antunes 
On 7 November 2016 at 18:06, Valo, Kalle <kv...@qca.qualcomm.com> wrote:
> Bruno Antunes <baantu...@gmail.com> writes:
>
>> On 4 November 2016 at 21:17, Valo, Kalle <kv...@qca.qualcomm.com> wrote:
>>> Bruno Antunes <baantu...@gmail.com> writes:
>>>
>>>> Old thread but I think the issue is still present.
>>>>
>>>> I'm running a setup with VLANs with WDS and ath10k cards.
>>>>
>>>> To make it work both cards must be loaded in rawmode, AP
>>>> and Sta, and with no security.
>>>>
>>>> I'm using a OpenWrt trunk r49941 and the most recent firmware,
>>>> 10.2.4.70.58, from Kalle ath10k firmware tree.
>>>>
>>>> Although it works the throughput is very bad.
>>>> Are there any alternatives to improve the throughput.
>>>
>>> Can someone file a bug to bugzilla about this so that all the info is
>>> properly stored? The more comprehensive the report is the better.
>>>
>>> https://bugzilla.kernel.org/
>>
>> I will file a bug report.
>
> Thanks, it's good to store all in one place so that it's easier to find
> the relevant info.

Just file the bug with the ID 187241 -  VLAN support in ATH10k
Feel free to ask for adicional info.
I did not mention any names in the bug report fell free to take credit
if wanted.

Regards,
Bruno

>
>> But since it appears to be a firmware related issue
>> under what category can fill in the bug?
>
> You can file it under Drivers/network-wireless, AFAIK we don't have any
> separate components for firmware bugs. Here's one example to follow:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=186161
>
> --
> Kalle Valo
> ___
> 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] ATH10K VLAN firmware issue

2016-11-07 Thread Bruno Antunes 
On 7 November 2016 at 14:06, Ben Greear <gree...@candelatech.com> wrote:
> On 11/07/2016 03:54 AM, Bruno Antunes wrote:
>>
>> On 4 November 2016 at 22:23, Ben Greear <gree...@candelatech.com> wrote:
>>>
>>> The bug appears that vlan-tx-stripping is unconditionally enabled in
>>> at least my firmware.  I have re-compiled w/out that flag set, and it
>>> appears
>>> to work for me.
>>>
>>> Please download this firmware, rename it firmware-2.bin, make sure you
>>> remove/rename
>>> any firmware-5.bin (etc) so mine will load, and see if that fixes your
>>> problem.
>>
>>
>> Thanks for the fast reply but it only solves "half"  the problem.
>>
>> Now the connection between the AP and the Sta can be secure and the
>> driver doesn't need to be loaded in rawmode.
>>
>> Unfortunatly the the throughput is still bad.
>>
>> iperf3 -c 10.10.4.15
>> Connecting to host 10.10.4.15, port 5201
>> [  4] local 10.10.4.16 port 44893 connected to 10.10.4.15 port 5201
>> [ ID] Interval   Transfer Bandwidth   Retr  Cwnd
>> [  4]   0.00-1.01   sec  42.4 KBytes   345 Kbits/sec6   1.41 KBytes
>> [  4]   1.01-2.01   sec  0.00 Bytes  0.00 bits/sec1   1.41 KBytes
>> [  4]   2.01-3.01   sec  0.00 Bytes  0.00 bits/sec1   1.41 KBytes
>> [  4]   3.01-4.01   sec  0.00 Bytes  0.00 bits/sec0   1.41 KBytes
>> [  4]   4.01-5.01   sec  0.00 Bytes  0.00 bits/sec0   1.41 KBytes
>> [  4]   5.01-6.01   sec  0.00 Bytes  0.00 bits/sec0   1.41 KBytes
>> [  4]   6.01-7.01   sec  0.00 Bytes  0.00 bits/sec1   1.41 KBytes
>> [  4]   7.01-8.01   sec  0.00 Bytes  0.00 bits/sec0   1.41 KBytes
>> [  4]   8.01-9.01   sec  0.00 Bytes  0.00 bits/sec0   1.41 KBytes
>> [  4]   9.01-10.01  sec  0.00 Bytes  0.00 bits/sec0   1.41 KBytes
>> - - - - - - - - - - - - - - - - - - - - - - - - -
>> [ ID] Interval   Transfer Bandwidth   Retr
>> [  4]   0.00-10.01  sec  42.4 KBytes  34.7 Kbits/sec9
>> sender
>> [  4]   0.00-10.01  sec  0.00 Bytes  0.00 bits/sec
>> receiver
>
>
> You have a complex setup, so I think it would be best if you could break it
> into
> simpler parts to test.

Some of the parts I already tested and are working
>
> First, try just STA to AP, no vlans, and see if you get useful throughput.
>
Works fine

> Then try with VLANs
>
To Do

> Then, try with WDS.

Works fine
>
> Then try with WDS and vlans.
>
The ultimate goal...

> In STA to AP mode with VLANs, it performed well for me.
>
> Thanks,
> Ben
>
>
>>
>> iperf Done.
>>
>>>
>>> Please note that it is very likely you will have to use same MAC address
>>> for the VLAN devices that the underlying station uses in order for this
>>> to
>>> work.
>>
>>
>> Can you please elaborate more?
>> My setup  is the folowing.
>> The connection between the AP and Sta is in WDS
>> For the moment all devices are in the same VLAN.
>>
>> client1 --- SW1  AP .. Sta  SW2 --- client2
>>
>>
>> Thanks,
>> Bruno
>>
>>>
>>> https://www.candelatech.com/downloads/tmp/firmware-2-full-community.bin
>>>
>>>
>>> Thanks,
>>> Ben
>>>
>>>
>>>
>>
>>> Ben Greear <gree...@candelatech.com>
>>> Candela Technologies Inc  http://www.candelatech.com
>>>
>>
>
> --
> Ben Greear <gree...@candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] ATH10K VLAN firmware issue

2016-11-07 Thread Bruno Antunes 
On 4 November 2016 at 21:17, Valo, Kalle <kv...@qca.qualcomm.com> wrote:
> Bruno Antunes <baantu...@gmail.com> writes:
>
>> Old thread but I think the issue is still present.
>>
>> I'm running a setup with VLANs with WDS and ath10k cards.
>>
>> To make it work both cards must be loaded in rawmode, AP
>> and Sta, and with no security.
>>
>> I'm using a OpenWrt trunk r49941 and the most recent firmware,
>> 10.2.4.70.58, from Kalle ath10k firmware tree.
>>
>> Although it works the throughput is very bad.
>> Are there any alternatives to improve the throughput.
>
> Can someone file a bug to bugzilla about this so that all the info is
> properly stored? The more comprehensive the report is the better.
>
> https://bugzilla.kernel.org/

I will file a bug report.

But since it appears to be a firmware related issue
under what category can fill in the bug?

Thanks,
Bruno

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

Re: [OpenWrt-Devel] ATH10K VLAN firmware issue

2016-11-07 Thread Bruno Antunes 
On 4 November 2016 at 22:23, Ben Greear  wrote:
> The bug appears that vlan-tx-stripping is unconditionally enabled in
> at least my firmware.  I have re-compiled w/out that flag set, and it
> appears
> to work for me.
>
> Please download this firmware, rename it firmware-2.bin, make sure you
> remove/rename
> any firmware-5.bin (etc) so mine will load, and see if that fixes your
> problem.

Thanks for the fast reply but it only solves "half"  the problem.

Now the connection between the AP and the Sta can be secure and the
driver doesn't need to be loaded in rawmode.

Unfortunatly the the throughput is still bad.

iperf3 -c 10.10.4.15
Connecting to host 10.10.4.15, port 5201
[  4] local 10.10.4.16 port 44893 connected to 10.10.4.15 port 5201
[ ID] Interval   Transfer Bandwidth   Retr  Cwnd
[  4]   0.00-1.01   sec  42.4 KBytes   345 Kbits/sec6   1.41 KBytes
[  4]   1.01-2.01   sec  0.00 Bytes  0.00 bits/sec1   1.41 KBytes
[  4]   2.01-3.01   sec  0.00 Bytes  0.00 bits/sec1   1.41 KBytes
[  4]   3.01-4.01   sec  0.00 Bytes  0.00 bits/sec0   1.41 KBytes
[  4]   4.01-5.01   sec  0.00 Bytes  0.00 bits/sec0   1.41 KBytes
[  4]   5.01-6.01   sec  0.00 Bytes  0.00 bits/sec0   1.41 KBytes
[  4]   6.01-7.01   sec  0.00 Bytes  0.00 bits/sec1   1.41 KBytes
[  4]   7.01-8.01   sec  0.00 Bytes  0.00 bits/sec0   1.41 KBytes
[  4]   8.01-9.01   sec  0.00 Bytes  0.00 bits/sec0   1.41 KBytes
[  4]   9.01-10.01  sec  0.00 Bytes  0.00 bits/sec0   1.41 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval   Transfer Bandwidth   Retr
[  4]   0.00-10.01  sec  42.4 KBytes  34.7 Kbits/sec9 sender
[  4]   0.00-10.01  sec  0.00 Bytes  0.00 bits/sec  receiver

iperf Done.

>
> Please note that it is very likely you will have to use same MAC address
> for the VLAN devices that the underlying station uses in order for this to
> work.

Can you please elaborate more?
My setup  is the folowing.
The connection between the AP and Sta is in WDS
For the moment all devices are in the same VLAN.

client1 --- SW1  AP .. Sta  SW2 --- client2


Thanks,
Bruno

>
> https://www.candelatech.com/downloads/tmp/firmware-2-full-community.bin
>
>
> Thanks,
> Ben
>
>
>

> Ben Greear 
> Candela Technologies Inc  http://www.candelatech.com
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] ATH10K VLAN firmware issue

2016-11-04 Thread Bruno Antunes 
On 4 November 2016 at 14:18, Mauro Mozzarelli <open...@ezplanet.net> wrote:
> Since the capability is implemented in software you might be testing the
> limit of your router's CPU i/o speed.

By loading the module in rawmode?

The AP is an APU and Sta is an APU2.

>
>
>
> On 04/11/16 14:13, Bruno Antunes wrote:
>>
>> Hi all,
>>
>> Old thread but I think the issue is still present.
>>
>> I'm running a setup with VLANs with WDS and ath10k cards.
>>
>> To make it work both cards must be loaded in rawmode, AP
>> and Sta, and with no security.
>>
>> I'm using a OpenWrt trunk r49941 and the most recent firmware,
>> 10.2.4.70.58, from Kalle ath10k firmware tree.
>>
>> Although it works the throughput is very bad.
>> Are there any alternatives to improve the throughput.
>>
>> Best Regards,
>> Bruno
>>
>> On 9 December 2015 at 17:24, voncken <cedric.vonc...@acksys.fr> wrote:
>>>
>>>
>>>> -Message d'origine-
>>>> De : Ben Greear [mailto:gree...@candelatech.com]
>>>> Envoyé : mercredi 9 décembre 2015 16:34
>>>> À : Cedric VONCKEN; ath...@lists.infradead.org; linux-wireless
>>>> Objet : Re: ATH10K VLAN firmware issue
>>>>
>>>> This only happens when you use STA  + WDS, or is .1q broken for you in
>>>> other cases as well?
>>>
>>> No, this issue occurs in all modes (STA, STA + WDS, AP).
>>>
>>> Thanks
>>>
>>> Cedric.
>>>
>>>> Thanks,
>>>> Ben
>>>>
>>>> On 12/08/2015 06:29 AM, Cedric VONCKEN wrote:
>>>>>
>>>>>  I'm testing to transmit frame with 802.1q tag (VLAN).
>>>>>
>>>>>  My client is set in STA + WDS and the netdev is bridged with eth0.
>>>>>  I have a computer with vlan configuration set connected to the STA
>>>>> eth0.
>>>>>
>>>>>  If I try to transmit frames with 802.1q tag, the frames are not
>>>
>>> sent.
>>>>>
>>>>>  I checked with wireless sniffer, and I don't see the frame with
>>>>> VLAN
>>>>> tag (the frames without VLAN tag are sent).
>>>>>
>>>>>  I tested with firmware 10.2.4.70.14-2 from kale github,
>>>>> 10.1.467-ct-com-full-015 from candelatech and 10.2.4.70-2 from
>>>>> openwrt, and in all cases I have the same issue.
>>>>>
>>>>>  Thanks for your help.
>>>>>
>>>>>
>>>>> --
>>>>> To unsubscribe from this list: send the line "unsubscribe
>>>>> linux-wireless" in the body of a message to majord...@vger.kernel.org
>>>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>>>
>>>> --
>>>> Ben Greear <gree...@candelatech.com>
>>>> Candela Technologies Inc  http://www.candelatech.com
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-wireless"
>>> in
>>> the body of a message to majord...@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] ATH10K VLAN firmware issue

2016-11-04 Thread Bruno Antunes 
Hi all,

Old thread but I think the issue is still present.

I'm running a setup with VLANs with WDS and ath10k cards.

To make it work both cards must be loaded in rawmode, AP
and Sta, and with no security.

I'm using a OpenWrt trunk r49941 and the most recent firmware,
10.2.4.70.58, from Kalle ath10k firmware tree.

Although it works the throughput is very bad.
Are there any alternatives to improve the throughput.

Best Regards,
Bruno

On 9 December 2015 at 17:24, voncken  wrote:
>
>
>> -Message d'origine-
>> De : Ben Greear [mailto:gree...@candelatech.com]
>> Envoyé : mercredi 9 décembre 2015 16:34
>> À : Cedric VONCKEN; ath...@lists.infradead.org; linux-wireless
>> Objet : Re: ATH10K VLAN firmware issue
>>
>> This only happens when you use STA  + WDS, or is .1q broken for you in
>> other cases as well?
>
> No, this issue occurs in all modes (STA, STA + WDS, AP).
>
> Thanks
>
> Cedric.
>
>>
>> Thanks,
>> Ben
>>
>> On 12/08/2015 06:29 AM, Cedric VONCKEN wrote:
>> > I'm testing to transmit frame with 802.1q tag (VLAN).
>> >
>> > My client is set in STA + WDS and the netdev is bridged with eth0.
>> > I have a computer with vlan configuration set connected to the STA
>> > eth0.
>> >
>> > If I try to transmit frames with 802.1q tag, the frames are not
> sent.
>> > I checked with wireless sniffer, and I don't see the frame with VLAN
>> > tag (the frames without VLAN tag are sent).
>> >
>> > I tested with firmware 10.2.4.70.14-2 from kale github,
>> > 10.1.467-ct-com-full-015 from candelatech and 10.2.4.70-2 from
>> > openwrt, and in all cases I have the same issue.
>> >
>> > Thanks for your help.
>> >
>> >
>> > --
>> > To unsubscribe from this list: send the line "unsubscribe
>> > linux-wireless" in the body of a message to majord...@vger.kernel.org
>> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> >
>>
>> --
>> Ben Greear 
>> Candela Technologies Inc  http://www.candelatech.com
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] UDP throughput problems with WDS and ath10k

2016-09-13 Thread Bruno Antunes 
Hello,


On 23 March 2016 at 10:53, Xue Liu  wrote:
> Hello everyone,
>
> Now I am doing point to point  throughput test using  and ath10k. The
> hardwares are clearfog A1 board with armada 388 and WLE900VX (QCA9880). The
> OpenWRT trunk is running on it.

Could you tell what is the OpenWrt Release and firmware used?
I'm using trunk R49886 and tried several versions of firmware and stll
can't send traffic trough the WDS link.
The link is established, there is a wlan0.sta1, but there is no L3 traffic.

Thanks,
Bruno

>
> At first I did UDP throughput test ( WDS AP <---> WDS Client ) with iperf3
> server on the WDS AP. The throughput is approx 630 Mbps.  But if the server
> sends the data, the throughput will rise to 700 Mbps.  I did the
> bidirectional test for many times. The UDP data transferring from AP side
> always has 70 - 80 Mbps more throughput.
>
> In the same situation, I did UDP throughput test between PC and WDS AP ( PC
> <>WDS Client <> WDS AP ) . The PC is connected with the WDS client
> via GbE port.  I have found a more interesting result. The data throughput
> is about 678 Mbps when the data is transmitted from AP to PC. There is
> almost no performance loss. But the throughput is only about 425 Mpbs from
> PC to AP.
>
> Can anyone give me some advises or some info about the reason and how to
> improve the transmitting performance from PC to AP side. Thank you.
>
> Regards,
>
> Xue Liu
>
> ___
> ath10k mailing list
> ath...@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Request for any netifd wireless documentation

2014-11-18 Thread Bruno Antunes 
Same here...

I'm trying to implement ht-mcs without luck.

Bruno

On 18 November 2014 11:19, Rafał Miłecki zaj...@gmail.com wrote:
 Could someone explain netifd and wireless management a bit, please? I
 tried to read some code, but so far it looks messy to me.
 Maybe if we had some short description of netifd wireless layout on
 wiki, it would be more developer friendly.

 I can see multiple files:
 /sbin/wifi
 /lib/wifi/mac80211.sh
 /lib/netifd/wireless/mac80211.sh
 /lib/netifd/hostapd.sh
 but they mostly don't contain any comments.

 I'm not sure how much it's worth to list unclear parts of that.

 It's confusing to have /lib/netifd/ and /lib/wifi/. It's confusing to
 have two APIs (inconsistent callbacks). I can't understand why even
 for mac80211.sh we keep detecting code in /lib/wifi/. There isn't
 anything documented in the /lib/netifd/netifd-wireless.sh. I have no
 idea how netifd - scripts communication works. What is handled in
 scripts and what in netifd?

 Could someone try to describe this a bit? Preferably on wiki page, so
 it can be easily found and extended by others?

 --
 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

[OpenWrt-Devel] Possible regression? Adhoc Mode broken kernel oops with batman-adv.

2014-08-29 Thread Bruno Antunes 
Using OpenWrt trunk r42000 on 2 different boards (gw2388-4  router station
pro) causes kernel oops when restarting the network or wifi.

The setting that causes the oops is connecting in adhoc mode to a
batman-adv mesh network.

As comparison WDS mode works fine for the same boards.

Also Adhoc mode using wpa_supplicant appears to be broken.
With wpa2 security only allows connections at 54 Mbps, removing security
allows for 802.11n rates.

Don't know if the 2 issues are related or not.

Below the kernel oops from the router station.

Regards,
Bruno

root@RSPro1:/# wifi
root@RSPro1:/# [  182.04] batman_adv: bat0: Interface deactivated:
adhoc0
[  182.05] batman_adv: bat0: Removing interface: adhoc0
[  182.08] br-mesh: port 2(bat0) entered disabled state
[  182.08] device bat0 left promiscuous mode
[  182.09] br-mesh: port 2(bat0) entered disabled state
[  182.10] CPU 0 Unable to handle kernel paging request at virtual
address 0020, epc == 87090884, ra == 870963e8
[  182.11] Oops[#1]:
[  182.11] CPU: 0 PID: 6 Comm: kworker/u2:0 Not tainted 3.10.49 #2
[  182.11] Workqueue: bat_events batadv_softif_vlan_get [batman_adv]
[  182.11] task: 878294f0 ti: 87844000 task.ti: 87844000
[  182.11] $ 0   :  0001 0020 
[  182.11] $ 4   :  8004 80321e28 803825a2
[  182.11] $ 8   : 00180041 00180041 0001 873d7080
[  182.11] $12   : 0020 0001 00170041 
[  182.11] $16   :  86913200  8690b100
[  182.11] $20   : 01b0  00200200 d1f2
[  182.11] $24   :  
[  182.11] $28   : 87844000 87845da0 802eb3b0 870963e8
[  182.11] Hi: 0009
[  182.11] Lo: 9c40
[  182.11] epc   : 87090884 batadv_softif_vlan_free_ref+0x14/0xe0
[batman_adv]
[  182.11] Not tainted
[  182.11] ra: 870963e8 batadv_tt_free+0xc0/0x2e4 [batman_adv]
[  182.11] Status: 1000fc03 KERNEL EXL IE
[  182.11] Cause : 0088
[  182.11] BadVA : 0020
[  182.11] PrId  : 00019374 (MIPS 24Kc)
[  182.11] Modules linked in: ath9k ath9k_htc ath9k_common pppoe
ppp_async iptable_nat ath9k_hw ath pppox ppp_generic pl2303 nf_nat_ipv4
nf_conntrack_ipvh
[  182.11] Process kworker/u2:0 (pid: 6, threadinfo=87844000,
task=878294f0, tls=)
[  182.11] Stack :  8692ebc0 8692e800 87845e30 8692ebc0
870963e8 d1f2 d1f2
  8692ebc0 8692ebc0 8692ebc0 8692e800 87845e30 8031 80310f20

  d1f2 8708a374 d1f2 87084fd4 87845e30 0001 80310f20
8692e800
  8692e800 8708fa24  87845e0c  8692ea08 8692ea08
801b2b74
  878294f0 8027c780  8692e800 87845e30 87845e30 87813900
8692ecb8
  ...
[  182.11] Call Trace:
[  182.11] [87090884] batadv_softif_vlan_free_ref+0x14/0xe0
[batman_adv]
[  182.11] [870963e8] batadv_tt_free+0xc0/0x2e4 [batman_adv]
[  182.11] [8708a374] batadv_mesh_free+0x54/0x88 [batman_adv]
[  182.11] [8708fa24] batadv_purge_outstanding_packets+0x2fc/0x8d8
[batman_adv]
[  182.11]
[  182.11]
Code: afb00010  afbf0014  00808021 c043 2464  e044  1080fffc
   24020001
[  182.36] ---[ end trace 19fd45c8593c0fb4 ]---
[  182.37] Kernel panic - not syncing: Fatal exception in interrupt
[  182.37] Rebooting in 3 seconds..+
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] WDS and adhoc support with ath10k

2014-04-08 Thread Bruno Antunes 
Hi,

I recently have been testing some 802.11ac hardware with the ath10k.

Could someone confirm if WDS and adhoc mode currently don't have support with 
this driver?

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