From: Bauer, Rick (BAUERR@xxxxxxxxxxx)
Date: Thu May 23 2002 - 14:56:58 GMT-3
My argument with using access-lists, is that access-lists do not apply to
traffic originating from within the router.
I use for traffic originating within the router, (queuing on the dlsw
router)
queue-list 1 prot ip 16 tcp 2065 - this handles both source and or
destination
queue-list 1 prot ip 16 udp 2067
As for traffic passing through a router, I use an access-list. This is when
you have a non-DLSW router between two DLSWs.
-----Original Message-----
From: Sasa Milic [mailto:smilic@EUnet.yu]
Sent: Tuesday, May 21, 2002 1:52 PM
To: Lance
Cc: ccielab@groupstudy.com
Subject: Re: DLSW Custom Queueing
"protocol dlsw" can be used only with FST encapsulation. If you
use TCP, then you have to use access-list to identify port(s)
(don't forget 1981, 1982 and 1983 if you use dlsw priority).
Sasa,
CCIE No. 8635
> I have seen many posts regarding the access-list needed to capture DLSW
> packets,however there is the option of specifying dlsw as the protocol
within
> the custom que list defenition. such as:
>
> queue-list 1 protocol dlsw 3
>
> is there a reason that you would want to use an access-list to identify
the
> dlsw packets instead of using the above mentioned command??
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:59:06 GMT-3