Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.networking > #2110 > unrolled thread
| Started by | clbeltz@gmail.com |
|---|---|
| First post | 2013-04-26 21:17 -0700 |
| Last post | 2013-04-28 13:23 +0200 |
| Articles | 4 — 2 participants |
Back to article view | Back to comp.os.linux.networking
QOS for AP and Router ... clbeltz@gmail.com - 2013-04-26 21:17 -0700
Re: QOS for AP and Router ... Pascal Hambourg <boite-a-spam@plouf.fr.eu.org> - 2013-04-27 10:38 +0200
Re: QOS for AP and Router ... clbeltz@gmail.com - 2013-04-27 12:56 -0700
Re: QOS for AP and Router ... Pascal Hambourg <boite-a-spam@plouf.fr.eu.org> - 2013-04-28 13:23 +0200
| From | clbeltz@gmail.com |
|---|---|
| Date | 2013-04-26 21:17 -0700 |
| Subject | QOS for AP and Router ... |
| Message-ID | <45f786eb-cf1a-4496-83af-74f87659d998@googlegroups.com> |
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
[toc] | [next] | [standalone]
| From | Pascal Hambourg <boite-a-spam@plouf.fr.eu.org> |
|---|---|
| Date | 2013-04-27 10:38 +0200 |
| Message-ID | <klg2q0$2pmv$1@saria.nerim.net> |
| In reply to | #2110 |
Hello, clbeltz@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 ?
[toc] | [prev] | [next] | [standalone]
| From | clbeltz@gmail.com |
|---|---|
| Date | 2013-04-27 12:56 -0700 |
| Message-ID | <81e42ceb-0529-41fa-b788-6661b5dc50b8@googlegroups.com> |
| In reply to | #2111 |
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.
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <boite-a-spam@plouf.fr.eu.org> |
|---|---|
| Date | 2013-04-28 13:23 +0200 |
| Message-ID | <klj0qn$org$1@saria.nerim.net> |
| In reply to | #2112 |
clbeltz@gmail.com a écrit : > 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. 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".
[toc] | [prev] | [standalone]
Back to top | Article view | comp.os.linux.networking
csiph-web