From: Simon Hope (shope@xxxxxxxxxxx)
Date: Thu Feb 01 2001 - 19:38:10 GMT-3
Hi bernard, does that work on all interfaces? I have had similar trouble
filtering netbios names coming from Ethernet interfaces, but no problem
blocking them on token ring ones
Router4(config-if)#netbios output-access-filter host simon
netbios interface commands only allowed on Token Rings
Router4(config-if)#
this router is only running 11.2 JS tho
Simon
----- Original Message -----
From: "Bernard Dunn" <dunn@cisco.com>
To: "Brian Hescock" <bhescock@cisco.com>
Cc: <ccielab@groupstudy.com>
Sent: Thursday, February 01, 2001 10:24 PM
Subject: Re: netbios filters
> Brian,
>
> You should be able to use :
>
> (global)
> netbios access-list <label>
>
> (On the interface)
> netbios input-access-filter host
> netbios output-access-filter host
>
> Hope this helps.
>
> Bernard.
>
> On Thu, 1 Feb 2001, Brian Hescock wrote:
>
> > ok, this is probably a stupid question but I can seem to find it
> > anywhere, perhaps it isn't possible. Netbios filters only seem to be
> > allowed on token ring interfaces, other than on the dlsw remote-peer
> > command. But that command only keeps connections from being formed by
> > blocking the name query it seems and the entries still make it into the
> > reachability table. Is there a way to filter netbios so I
> > don't even get the netbios names in the reachability info? The only way
I
> > can think to do it would be a real kluge:
> >
> > - on the remote-peer use "netbios-exclusive" and not have any
> > "icanreach" netbios commands. I would think this *should* prevent it
from
> > forwarding any netbios. Again, this would be a complete kluge and this
> > wouldn't work if you wanted to just filter out one name.
> >
> > Is there a way to do it?
> >
> > Brian
> >
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:28:33 GMT-3