Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
QOS for AP and Router ...
16 views
Skip to first unread message
clb...@gmail.com
Apr 27, 2013, 12:17:07 AM4/27/13
to
All,
I've got a router and a 30' run of cabling to another router configured as an access point (lan-to-lan, no DHCP, etc). Working well, but would like to model network traffic. Both devices have QOS. Got some questions:
1) Suppose there are two router-set QOS quotas: 80% and 20% to IP .100 and all others, respectively. Let's call this SSID ROUTER.
2) Suppose the AP is leased IP .100 (80%), and a wireless client is leased IP .101 (other - 20%) from ROUTER.
3) suppose the AP has a separate SSID (let's call it AP), and three wireless clients connected, issued IPs .102 - .104 from ROUTER.
Do .102 - .104 inherit 80% quota since they are connected to .100?
We know .101 gets the 20% quota, but from ROUTER's perspective, .102 - .104 are also *other* IPs, and could share in the 20% quota.
Can anyone enlighten me?
Thanks,
Chris
I've got a router and a 30' run of cabling to another router configured as an access point (lan-to-lan, no DHCP, etc). Working well, but would like to model network traffic. Both devices have QOS. Got some questions:
1) Suppose there are two router-set QOS quotas: 80% and 20% to IP .100 and all others, respectively. Let's call this SSID ROUTER.
2) Suppose the AP is leased IP .100 (80%), and a wireless client is leased IP .101 (other - 20%) from ROUTER.
3) suppose the AP has a separate SSID (let's call it AP), and three wireless clients connected, issued IPs .102 - .104 from ROUTER.
Do .102 - .104 inherit 80% quota since they are connected to .100?
We know .101 gets the 20% quota, but from ROUTER's perspective, .102 - .104 are also *other* IPs, and could share in the 20% quota.
Can anyone enlighten me?
Thanks,
Chris
Pascal Hambourg
Apr 27, 2013, 4:38:22 AM4/27/13
to
Hello,
clb...@gmail.com a ï¿œcrit :
> All,
> I've got a router and a 30' run of cabling to another router [...]
What does it have to do with Linux ?
clb...@gmail.com a ï¿œcrit :
> All,
> I've got a router and a 30' run of cabling to another router [...]
What does it have to do with Linux ?
clb...@gmail.com
Apr 27, 2013, 3:56:12 PM4/27/13
to
Quite a bit, actually. There are several QOS posts in this group (none that answer this question), and the router firmware is implemented in linux, so I thought there may be some who understood how QOS implementation might be handled by linux.
If you're not someone who understands, don't reply.
If you're not someone who understands, don't reply.
Pascal Hambourg
Apr 28, 2013, 7:23:00 AM4/28/13
to
clb...@gmail.com a ï¿œcrit :
> and the router firmware is implemented in linux, so I thought there
> may be some who understood how QOS implementation might be handled by
> linux.
>
> If you're not someone who understands, don't reply.
Still, your question does not have much (if anything) to do with Linux,
and does not require to understand the QoS implementation in Linux.
If your QoS is based on the source (or destination) IP address, then the
fact that clients are connected to the AP matters only if the AP does
some NAT and replaces the client source address with its own address. If
packets sent by clients arrive unchanged at the QoS router, then they
will be treated as "other".
> Quite a bit, actually. There are several QOS posts in this group
So what ?
> and the router firmware is implemented in linux, so I thought there
> may be some who understood how QOS implementation might be handled by
> linux.
>
> If you're not someone who understands, don't reply.
and does not require to understand the QoS implementation in Linux.
If your QoS is based on the source (or destination) IP address, then the
fact that clients are connected to the AP matters only if the AP does
some NAT and replaces the client source address with its own address. If
packets sent by clients arrive unchanged at the QoS router, then they
will be treated as "other".
0 new messages