From: Lord, Chris (chris.lord@lorien.co.uk)
Date: Fri Aug 22 2003 - 07:26:26 GMT-3
Hi,
I'm no expert when it comes to this area, but I've just finished researching IPExpert Lab 14 so I'll offer my guess at this...
icanreach and netbios-name affects peer-to-peer (i.e. router-to-router) capabilites. icanreach concerns SNA reachabilty whereas netbios-name concerns NetBios reachabilty - two different frame types I believe.
Your question relates to a specific host machine sitting on the R1 e0, not to a peering capabilty. I would put my money on you needing a netbios accss-list and access-experession on the e0 interface of R1 to specifically filter stuff from the TEST host.
Then again, someone out there probably knows better?
Regards,
Chris
-----Original Message-----
From: wwwjjang@chol.com [mailto:wwwjjang@chol.com]
Sent: 22 August 2003 09:25
To: ccielab@groupstudy.com
Subject: DLSW+'s Filtering Question..
Hi..Everyone..
I want to know the differences between "dlsw icanreach" & " dlsw netbios-name".
& My configuration is correct ??
Who knows the difference ??
Thanks...
-------------
My Diagram
-------------
(e0 1.1.1.1)--R1-(s0 2.2.2.1)----(s0 2.2.2.2)-R2-(e0 3.3.3.1)
----------
Question
----------
-Configure dlsw between R1'E0 & R2'E0
-Configure R1 to prevent explorer traffic for host TEST from being sent !!
=> Does This mean that I have to use "Dlsw netbios-name"-command ??
------------
My Solution => Is it right ??
------------
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
dlsw netbios-name IBM remote-peer ip 2.2.2.2 **>is it correct ??
!
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 bridge-group 1
bridge 1 protocol ieee
!
interface Ethernet0
ip address 3.3.3.1 255.255.255.0
bridge-group 1
This archive was generated by hypermail 2.1.4 : Tue Sep 02 2003 - 18:54:04 GMT-3