From: Arvind Yadav (arvindyadav@comcast.net)
Date: Mon Jan 26 2004 - 15:22:22 GMT-3
Read this you will get the answer, specially the last two lines
Usage Guidelines
The dlsw icannotreach saps command causes the local router to send a control
vector to its peers during the capabilities exchange, which tells the peers
not to send canureach messages to the local router for sessions using those
DSAPs. (They are DSAPs from the peer's perspective, and SSAPs from the
perspective of the devices attached to the local router.) The effect is that
devices attached to the peer will not be able to initiate sessions to
devices attached to the local router using the listed DSAPs. Devices
attached to the local router, however, will still be able to start sessions
with devices on its peers using the listed saps as SSAPs. The reason is that
the local router can still send canureach requests to its peers, since no
filtering is actually done on the local router. The filtering done by the
peers does not prohibit the peers from responding to canureach requests from
the local router sending the control vector, only sending canureach requests
to the local router.
I hope this will help
Arvind
----- Original Message -----
From: <wwwjjang@chol.com>
To: <ccielab@groupstudy.com>
Sent: Monday, January 26, 2004 6:11 AM
Subject: Dlsw+ icannotreach's Question!!
> Hi..Evevryone..
>
> I'm testing "the Dlsw+ icannotreach saps",
> But it doesnot work well..
>
> What's the reason ??
>
> --------
> Diagram
> --------
>
> PC-A--(E0 1.1.1.1)--R1-(S0 2.2.2.1)---(S0 2.2.2.2)--R2--(E0 3.3.3.1)-PC-B
>
>
> ---------
> Question
> --------
> I wish that PC-A in R1 will not initiate netbios session to PC-B in
> R2 ..
>
>
> ----------
> My config
> ----------
> R1>
> ----
> dlsw local-peer peer-id 2.2.2.1
> dlsw remote-peer 0 tcp 2.2.2.2
> dlsw bridge-group 1
> bridge 1 protocol ieee
> !
> interface Ethernet0
> ip address 1.1.1.1 255.255.255.0
> bridge-group 1
>
> -----
> R2>
> -----
> dlsw local-peer peer-id 2.2.2.2
> dlsw remote-peer 0 tcp 2.2.2.1
> dlsw icannotreach sap F0 **
> dlsw bridge-group 1
> bridge 1 protocol ieee
> !
> interface Ethernet0
> ip address 3.3.3.1 255.255.255.0
> bridge-group 1
>
> ==> But When i searched the computer name of PC-B ,"PC-B", at PC-A
> I founded "PC-B" !!!
> ==> Because of the clause "dlsw icannotreach sap F0" in R2,
> I thought PC-B must not be finded by PC-A in R1 !!!
> What the reason ???
>
> _______________________________________________________________________
> Please help support GroupStudy by purchasing your study materials from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Mon Feb 02 2004 - 09:07:50 GMT-3