From: Scott Morris (swm@emanon.com)
Date: Tue Nov 23 2004 - 02:33:26 GMT-3
Technically the "icannotreach" will not block netbios from coming to it.
But all peers do a capabilities exchange, and since Netbios would not be
supported, nobody has any reason to send netbios traffic to that peer, or
ask it about reachable host information.
So in effect, it ends up blocking. The lsap-output-list becomes redundant
at that point.
HTH,
Scott Morris, MCSE, CCDP, CCIE4 (R&S/ISP-Dial/Security/Service Provider)
#4713, JNCIP, CCNA-WAN Switching, CCSP, Cable Communications Specialist, IP
Telephony Support Specialist, IP Telephony Design Specialist, CISSP
CCSI #21903
swm@emanon.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Nico
van Niekerk
Sent: Monday, November 22, 2004 9:13 PM
To: CCIELAB
Subject: DLSW+
You have a DLSW peering between R1 and R2. When you configure "dlsw
icannotreach saps F0" on R1, will R2 stop sending NetBIOS to R2? Or do you
need to configure an lsap-output-list on R2 to block the traffic?
This archive was generated by hypermail 2.1.4 : Thu Dec 02 2004 - 06:57:49 GMT-3