FlexQoS Graph Missing Downlink data for Guest Networks

  • ATTENTION! You'll notice a Prefix dropdown when you create a thread. If your post applies to one of the topics listed, please use that Prefix for your post. When browsing the thread list you can use the Prefix to filter the view.
  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

nikr

Regular Contributor
101.148 is my wife's work laptop. It seems that their IT has configured vpn so that all traffic is routed over VPN tunnel, Probably that's why I see only one connection to the VPN gateway (yes I verified the remote IP and it is their VPN gateway) and nothing else. What is puzzling me is that I only see traffic in uplink for that PC, always. Even when she is on a teams call (which is over vpn tunnel). In fact when I took this screenshot, she was on a call, yet no downlink data.

That constant uplink data for web surfing is for my nest cams spying on me.

Screen Shot 2021-04-20 at 10.50.23 AM.png
 

dave14305

Part of the Furniture
Is her laptop on Guest Network 1? QoS stats will only show up for traffic coming through br0 which would exclude Guest Network #1 (2 & 3 should work fine).
 

nikr

Regular Contributor
Yup, she is on Guest network 1. So Stats only show up for Guest network 2 and 3 and Main Network. But QoS should work on all networks (Guest 1, 2, 3 and Main), right?

It still does not explain why I see that uplink only traffic when her laptop is connected to the Guest network. If guest network 1 is not reported in stats there should be no uplink stats, unless if not from her laptop (which is highly unlikely).
 
Last edited:

dave14305

Part of the Furniture
But QoS should work on all networks (Guest 1, 2, 3 and Main), right?
I’m not sure if Adaptive QoS works on br1 or br2. Check with:
Code:
tc qdisc | grep br
It still does not explain why I see that uplink only traffic when her laptop is connected to the Guest network.
All Upload traffic regardless of source converges at the WAN interface, so guest network doesn’t matter for upload.
 

nikr

Regular Contributor
Sorry, I don't understand how all the interfaces are bridged together underneath.

Output of following command
Code:
tc qdisc | grep br
only contains br0.

And based on your comment above
QoS stats will only show up for traffic coming through br0 which would exclude Guest Network #1 (2 & 3 should work fine).
Does this mean QoS will work on Guest 2, 3 and Main network and not on Guest #1 (Not that I care about QoS on guest, but it'll be good to know).

This next question is probably going to be a dumb one.
If Adaptive QoS does not work with Guest Networks, does that mean all data from guest network is treated as default priority and if entire bandwidth is consumed by some higher priority data from main network like streaming video, Guest network will be throttled or since Guest #1 is not participating in QoS, not matter kind of data from main network it is treated as same priority as guest network and they both compete for the available bandwidth.

I have so many questions about how priorities work in Asus routers, if only there was some resource I can go read up on.

Thanks @dave14305 for explaining it to us.
 

dave14305

Part of the Furniture
Does this mean QoS will work on Guest 2, 3 and Main network and not on Guest #1 (Not that I care about QoS on guest, but it'll be good to know).
I think it should work fine on other Guest Networks. What’s the output of brctl show
If Adaptive QoS does not work with Guest Networks, does that mean all data from guest network is treated as default priority and if entire bandwidth is consumed by some higher priority data from main network like streaming video, Guest network will be throttled or since Guest #1 is not participating in QoS, not matter kind of data from main network it is treated as same priority as guest network and they both compete for the available bandwidth.
I assume that if there is no qdisc on the br1 or br2 interfaces, then downloads to guest network 1 will potentially run at full line speed. But I’m not very informed on how bridging and guest networks work on Asus (I don’t use them). And Guest Network 1 has been a headache for a lot of the previous understanding how Guest Networks work.

If you’re not using AiMesh, you may want to move your guest setup to #2 and leave all these worries behind.
 

nikr

Regular Contributor
Here is the output for both "tc qdisc" and "brctl show".
Screen Shot 2021-04-20 at 1.55.45 PM.png



There are no br1 and br2 only br0. Interesting thing is wl0.1 (which is Guest #1) is part of br0 along with wl0.2 which is Guest #2. If so why missing data in graph. I'll switch to Guest#3 to see if it fixes it. Also now I feel, if Guest network does not participate in Adaptive QoS may be its best that clients connected to guest networks not show up in graph, or if it shows up maybe it should be marked appropriately. Because if its marked as Streaming video for example but prioritized as pfifo_fast, its gets confusing.

Here is the the complete tcqdisc output
Code:
/tmp/home/root# tc qdisc
qdisc htb 1: dev eth0 root refcnt 2 r2q 10 default 0 direct_packets_stat 48 direct_qlen 1000
qdisc fq_codel 8004: dev eth0 parent 1:2 limit 1000p flows 1024 quantum 1514 target 5ms interval 100ms
qdisc fq_codel 8006: dev eth0 parent 1:10 limit 1000p flows 1024 quantum 300 target 5ms interval 100ms
qdisc fq_codel 8008: dev eth0 parent 1:11 limit 1000p flows 1024 quantum 300 target 5ms interval 100ms
qdisc fq_codel 800a: dev eth0 parent 1:12 limit 1000p flows 1024 quantum 300 target 5ms interval 100ms
qdisc fq_codel 800c: dev eth0 parent 1:13 limit 1000p flows 1024 quantum 300 target 5ms interval 100ms
qdisc fq_codel 800e: dev eth0 parent 1:14 limit 1000p flows 1024 quantum 300 target 5ms interval 100ms
qdisc fq_codel 8010: dev eth0 parent 1:15 limit 1000p flows 1024 quantum 300 target 5ms interval 100ms
qdisc fq_codel 8012: dev eth0 parent 1:16 limit 1000p flows 1024 quantum 300 target 5ms interval 100ms
qdisc fq_codel 8014: dev eth0 parent 1:17 limit 1000p flows 1024 quantum 300 target 5ms interval 100ms
qdisc pfifo_fast 0: dev eth1 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
qdisc pfifo_fast 0: dev eth2 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
qdisc pfifo_fast 0: dev eth3 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
qdisc pfifo_fast 0: dev eth4 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
qdisc pfifo_fast 0: dev eth5 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
qdisc pfifo_fast 0: dev spu_us_dummy root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
qdisc pfifo_fast 0: dev spu_ds_dummy root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
qdisc pfifo_fast 0: dev eth6 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
qdisc pfifo_fast 0: dev eth7 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
qdisc htb 1: dev br0 root refcnt 2 r2q 10 default 0 direct_packets_stat 37 direct_qlen 2
qdisc fq_codel 8001: dev br0 parent 1:2 limit 1000p flows 1024 quantum 1514 target 5ms interval 100ms
qdisc fq_codel 8005: dev br0 parent 1:10 limit 1000p flows 1024 quantum 1514 target 5ms interval 100ms ecn
qdisc fq_codel 8007: dev br0 parent 1:11 limit 1000p flows 1024 quantum 1514 target 5ms interval 100ms ecn
qdisc fq_codel 8009: dev br0 parent 1:12 limit 1000p flows 1024 quantum 1514 target 5ms interval 100ms ecn
qdisc fq_codel 800b: dev br0 parent 1:13 limit 1000p flows 1024 quantum 1514 target 5ms interval 100ms ecn
qdisc fq_codel 800d: dev br0 parent 1:14 limit 1000p flows 1024 quantum 1514 target 5ms interval 100ms ecn
qdisc fq_codel 800f: dev br0 parent 1:15 limit 1000p flows 1024 quantum 1514 target 5ms interval 100ms ecn
qdisc fq_codel 8011: dev br0 parent 1:16 limit 1000p flows 1024 quantum 1514 target 5ms interval 100ms ecn
qdisc fq_codel 8013: dev br0 parent 1:17 limit 1000p flows 1024 quantum 1514 target 5ms interval 100ms ecn
qdisc pfifo_fast 0: dev wl0.1 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
qdisc pfifo_fast 0: dev wl0.2 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
qdisc pfifo_fast 0: dev tun21 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1

I am no expert, but looking at last 3 lines, it seems QoS does not work even in Guest #2. Or it first applies pfifo_fast on guest network then since guest network is also part of br0, it applies adaptive QoS as well. o_O
More I think about this more my mind hurts.

I am running YazFi. Dont know if it changes bridging in some way.

Update: I tried Guest #2 and even it do not show downlink data or any guest clients.
 
Last edited:

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top