* Johannes Berg [31.05.2017 10:09]:
> > Is there any way to dump out the socket information if we reproduce
> > the problem?
>
> I have no idea, sorry.
>
> If you or Bastian can tell me how to reproduce the problem, I can try
> to investigate it.
there was an interesting fix regarding the shell
* Johannes Berg [17.05.2017 20:18]:
> On Wed, 2017-05-17 at 12:08 +0200, Bastian Bittorf wrote:
> > * Ben Greear [17.05.2017 11:51]:
[...]
> > > kernels, but when testing on 4.9 overnight, I notice that 'iw
> > > events' is not showing any input. '
* Ben Greear [17.05.2017 11:51]:
> I have been keeping an 'iw events' program running with a perl script
> gathering its
> output and post-processing it. This has been working for several years on
> 4.7 and earlier
> kernels, but when testing on 4.9 overnight, I notice that 'iw events' is not
* Simon Wunderlich [16.05.2017 12:24]:
> * station A detects a Radar, and informs userspace
> * userspace of station A will initiate a CSA, kernel will execute it (action
> frame, beacons)
> * station B picks up the CSA, and executes it as well
> * station B also marks the channel as unavaila
* Simon Wunderlich [16.05.2017 11:35]:
> This patchset adds DFS and CSA functionality:
thanks a lot. can you give a brief 'iw event' output when applied:
for a two-node mesh, where station A detects CSA and station B
should emit an event...
question: there is no userspace part for now, or maybe
* Janusz Dziedzic [30.03.2017 08:26]:
> On 29 March 2017 at 19:03, Tim Harvey wrote:
> > I don't know when ath9k last worked honestly. I usually use them under
> > OpenWrt which has its own patches against periodic updates of linux
> > backports. I noticed this first with Ubuntu 16.04 with the Ub
the former patch about rate-report/unfilled values
reminded me, that i can see with recent 'wireless-testing'
strange values when watching the output of 'iw event'.
maybe something similar...:
Mon Feb 13 11:18:52 CET 2017 DEBUG: wlan1-1 (phy #1): unknown event 60
Mon Feb 13 11:18:52 CET 2017 DEBUG
* Ben Greear [30.09.2015 21:08]:
> I've been asked to not post any ath10k CT firmware related info
this makes me sad, because it is related.
whoever asked you, can she/he stand up and explain?
bye, bastian
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body o
* Pavel Machek [30.09.2015 19:27]:
> This should send the second ping to the priority queue based on -Q,
> but I don't see an effect against one access point and it seems to
> work somehow against second one. Good!
you still need to hack/tune minstrel, because a lot of magic is
happen there
* Johannes Berg [28.09.2015 14:38]:
> Depends what you're measuring, but ping should apply the same DSCP tag
> on the response I believe.
your are right, I did not know this till yet 8-)
(i applied 0xb8 with 'ping -c1 -Q' just for testing)
14:49:52.491925 IP (tos 0xb8, ttl 64, id 51117, offset 0
* Johannes Berg [28.09.2015 14:00]:
> > > # you have to add some magic for matching your data
> > > e.g. $IPT -t mangle -I OUTPUT -j DSCP --set-dscp-class CS7
> >
> > Again, this is ping -Q equivalent, right? I was doing
>
> Yes.
IMHO this is not the same: you have to do it on both ends.
(also
* Pavel Machek [23.09.2015 13:38]:
> Is there way to manipulate type of service from userland to get
> similar behaviour without patching kernel?
yes, iptables DSCP / DiffServ / Differentiated Services Field
# you have to add some magic for matching your data
e.g. $IPT -t mangle -I OUTPUT -j DSC
* Johannes Berg [23.09.2015 11:03]:
> > > non-ASCII symbol all the time, line up the columns properly.
> >
> > who warns you? the compiler? the terminal?
>
> sparse, or perhaps smatch? either way, those tools are crucial for my
> workflow, and there seems to be very little downside to the change
* Johannes Berg [23.09.2015 10:44]:
> Replace the average symbol by "avg" to avoid being warned about the
> non-ASCII symbol all the time, line up the columns properly.
who warns you? the compiler? the terminal?
bye, bastian
--
To unsubscribe from this list: send the line "unsubscribe linux-wire
* Varka Bhadram [21.08.2015 10:52]:
> ath: skbuff alloc of size 1974 failed
i have seen this issue some month ago:
https://dev.openwrt.org/ticket/14782
how old - or better: which exact version
(kernel/ath9k) you are running?
bye, bastian
--
To unsubscribe from this list: send the line "unsubscr
,0.0,0,0,0,0,0,0,0,1.0
1424897596.239275,HT20,LGI,2,,MCS14,16,84,52.0,0.0,0.0,0.0,0.0,0.0,0,0,0,0,0,0,0,1.0
1424897596.239275,HT20,LGI,2,,MCS15,17,76,54.3,0.0,0.0,0.0,0.0,0.0,0,0,0,0,0,0,0,1.0
so a just want to say:
Tested-by: Bastian Bittorf
--
To unsubscribe from this list: send the line "uns
,0.0,0,0,0,0,0,0,0,1.0
1424897596.239275,HT20,LGI,2,,MCS14,16,84,52.0,0.0,0.0,0.0,0.0,0.0,0,0,0,0,0,0,0,1.0
1424897596.239275,HT20,LGI,2,,MCS15,17,76,54.3,0.0,0.0,0.0,0.0,0.0,0,0,0,0,0,0,0,1.0
so a just want to say:
Tested-by: Bastian Bittorf
--
To unsubscribe from this list: send the line "uns
* vadi...@gmail.com [10.12.2014 08:55]:
> > have we considered also exposing the mode of this netdev. So for example
> > sta,ap,p2p-go,p2p-client etc. If we can send dynamic updates via RTNL, we
> > could easily tell the networking management system what type of wireless
> > device we have here
18 matches
Mail list logo
