On Fri, 2010-08-06 at 12:18 -0400, M Brown wrote: > Upon having another look at your mail.... > > The other thing that I stated in the original email, that may have been > unclear, is the fact that e0/0 is an "internal" interface, so ingress > there is actually my egress on e0/1 (actually dialer1).
No it isn't the same thing. Internal ingress is not the same as external egress. They are very different. Think of it this way: ---> eth0/0 lan ingress ---> router paket queue ----> eth0/1 wan egress For this reason, an ingress interface can not have queueing and therefore it can not do QOS. Ingress can only do policing, egress is where QOS happens. Policing is a quick & dirty way to restrict total bandwidth. In short, if the router sees traffic exceeding a certain level it just drops packets causing a "saw-tooth" effect. Shaping queues traffic, smoothing it to the desired speed and the queueing also lets you prioritize packets allowing you to do QOS. Google for the difference between policing and shaping, Cisco has a document on this. > Since there is > only two interfaces on this router - I can get away with that. The number of interfaces has no effect on ingress/egress or queueing etc as explained above. One thing you are correct about is that you can't put this on the dialer interface so getting in the right place when using PPPOE is tricky. Regards, -- John Lange http://www.johnlange.ca --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
