You would need nbar to match http traffic, but without it, you could effectively match traffic by acl, meaning that you would match tcp/80. Obviously, nbar would pick up the traffic when it went over a port other than what you define as it looks in the application layers.
When you say you want to add QoS, what exactly do you mean? Are you wanting to prioiritize your http traffic, or limit it from using bandwidth needed for other applications?
You will only be able to effectively prioritize your outbound http traffic outbound.
1 - define the access-list
ip access-list extended webTraffic
permit tcp any any eq 80
permit tcp any any eq 443
2 - define the class-map
class-map match-any web
match access-group name webTraffic
3 - define the policy map
bandwidth 90 (or whatever you want this to be)
4 - apply the policy map to the interface
service-policy prioritizeWeb output
This is a very simple example which you will likely need to add on to. For example, if you are bridging with a seperate DSL modem and have a FastEthernet interface operating at 100Mb/s and have only 1Mb/s upload, you will also want to shape.
If you are using the built in modem, then yes, you would add the service-policy to the dialer interface. This means that under outbound congestion only, you're http/https would get 90kbps. If you would like to use percentages, you can substitute the bandwidth command with percent.
Keep in mind that the class-default, by default will get 25% of the interfaces bandwidth. I would not recommend using percentages in your case because your upload and download speeds are very different. When you use percentages, it carves the percentage based on what you issue with the bandwidth command, which is not upload/download specific.
Yes, it wouldn't make much sense unless you are just trying to test.
In your case it would be good for anything where you'll have queueing egress on that interface. On that type of interface, you'll not have igress queueing as it will happen a couple of hops before you.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...