From: Fred Ingham (fingham@xxxxxxx)
Date: Thu Jul 04 2002 - 04:12:14 GMT-3
Irhne: Did a quick test:
1. dlsw icanreach netbios-name T*
T* appears as a reachable name only in the capabilities, it does not
show up in reachability cache as you stated.
2. dlsw icanreach netbios-name T
T appears in dlsw capabilities and in the remote reachability cache as
"UNCONFIRMED", also as you stated.
3. dlsw icanreach netbios-name NMC*
NMC* appears in the capabilities exchange and, since there is
a real station "NMC2", NMC2 appears in the reachability cache.
Tentative conclusion is that an icanreach netbios name with wildcard will
not be put in reachability cache until a valid explorer is received from a
station matching the criteria.
Some data:
r5#sh run (edited)
source-bridge ring-group 200
dlsw local-peer peer-id 172.16.35.5
dlsw remote-peer 0 tcp 172.16.35.3
dlsw icanreach netbios-exclusive
dlsw icanreach netbios-name NMC*
dlsw icanreach netbios-name T
!
interface TokenRing0
no ip address
ring-speed 16
source-bridge 291 1 200
source-bridge spanning
-------------------------------------------------
r3#sh dlsw re
DLSw Local MAC address reachability cache list
Mac Addr status Loc. port rif
0080.9375.8746 FOUND LOCAL TBridge-003 --no rif--
DLSw Remote MAC address reachability cache list
Mac Addr status Loc. peer
0000.f669.5e42 FOUND REMOTE 172.16.35.5(2065)
0007.0dc6.d54b FOUND REMOTE 172.16.35.5(2065)
DLSw Local NetBIOS Name reachability cache list
NetBIOS Name status Loc. port rif
DLSw Remote NetBIOS Name reachability cache list
NetBIOS Name status Loc. peer
NMC2 FOUND REMOTE 172.16.35.5(2065)
T UNCONFIRM REMOTE 172.16.35.5(2065)
--------------------------------------------------------------
r3# sh dlsw cap ( r5 capabilities edited)
reachable mac addresses : none
reachable netbios names : NMC*
T
V2 multicast capable : yes
DLSw multicast address : none
Cheers, Fred.
----- Original Message -----
From: "GOLBERY Irhne" <irene.golbery@arche.fr>
To: "'Fred Ingham'" <fingham@cox.net>; <tkc9789@hotmail.com>;
<wicked01@ix.netcom.com>; <p729@cox.net>; <ccielab@groupstudy.com>
Sent: Wednesday, July 03, 2002 3:15 AM
Subject: RE: Netbios name filter
> Sorry for the delay I was out of line
>
> First, thanks for your answers ( Fred, David, Tommy and Mas)
>
> David,
> the Dlsw icanreach netbios-name t?to isn't seen in my remote dlsw
> reachability cache
> Like told in the previous mails and CD doc the "?" ( ctrl next V next ?)
> doesn't make sense in the Icanreach command.
>
> Fred,
> using the "dlsw icanreach netbios-name T*"
> T* isn't seen in the remote dlsw reachability cache- I don't now why ?
> However "dlsw icanreach netbios-name T" or "dlsw icanreach netbios-name t"
> is seen on the remote dlsw reachability cache
>
> Need your help to clarify this test
>
> Thanks in advance
>
> Irene
>
>
>
> -----Message d'origine-----
> De : Fred Ingham [mailto:fingham@cox.net]
> Envoyi : mardi 2 juillet 2002 20:18
> @ : GOLBERY Irhne; ccielab@groupstudy.com
> Objet : Re: Netbios name filter
>
>
> Irene: If you have a NetBIOS host on r1, and r2 is a configured peer of
r1,
> then you would use the following on r2:
>
> dlsw access-list host TEST permit T*
> dlsw remote-peer 0 tcp <r1 add> host-netbios-out TEST
> ( if you use the "?" then the name is a maximum of two characters)
>
> If you want to do the equivalent using icanreach then you would use the
> following on r1:
> dlsw icanreach netbios-name T*
>
> Look on r2 with a show dlsw capabilities and you should see that T*
> is there for reachable netbios names .
>
> Are you saying that you cannot enter the "*", or that it doesn't show up
in
> a capabalities exchange, or that a test doesn't work?
> DLSW uses caps for NetBIOS names.
>
> HTH (Espere que ce vous aider)
> Fred
>
>
> ----- Original Message -----
> From: "GOLBERY Irhne" <irene.golbery@arche.fr>
> To: <ccielab@groupstudy.com>
> Sent: Tuesday, July 02, 2002 11:41 AM
> Subject: Netbios name filter
>
>
> > Hi group,
> >
> >
> > I am looking for the equivalent of :
> >
> > netbios access-list host TEST permit t?to
> > using
> > Dlsw icanreach netbios-name t*to
> >
> > However the "*" doesn't match ?
> >
> > Does it make sense ?
> >
> > Can you give me your feed back ?
> >
> > Thanks
> >
> > Irene
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:36:18 GMT-3