we have a low-speed leased-line to a customer-site, which is used for remote-administration. Because the traffic from GUI-clients is making telnet/ssh-sessions unworkable, we would like to implement priority-queueing.
I can see that the priority-queueing is working on our local-router by looking at the increasing access-list counters and the interface queue-counters, but it does not work on the remote-router. I presume this is due to the fact that we are using PAT on the remote-router. The priority access-list seems to be checked before the PAT translates the tcp-ports back to the original tcp-ports.
Anybody know of a solution to this problem? Or am I overlooking something obvious?
The (abreviated) setup:
ip address 10.0.0.1 255.255.255.0
access-list 150 permit tcp any any eq telnet
priority-list 1 protocol ip high list 150
priority-list 1 default low
ip address 10.1.1.1 255.255.255.0
ip nat outside
ip address 10.0.0.2 255.255.255.0
ip nat inside
ip nat inside source list 18 interface Ethernet0/0 overload
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...