Are these routers peers on the same subnet--in other words, would policy routing www traffic along router 2 reuire that the traffic come into router 1, then exit through the same interface, and then go out router 2? If so, you might be creating more problems than you are solving in the long run. :-)
Second, are you checking source or destination port? Most html traffic will be destined to port 80 from the client to the server, but from the server to the client it will be sourced from port 80.
Finally, if these two connect to the internet through a service provider, note that you won't be able to control the majority of the html traffic--the inbound stuff from the internet--through policy routing. Instead, you'll have to do it through your service provider, or through some sort of nat scheme which results in the html traffic being nat'd into one pool, and the rest being nat'd into another pool, or something similar. This gets real messy real fast.
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 customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...