From: Edward Monk (emonk@xxxxxxx)
Date: Fri Jun 28 2002 - 12:59:44 GMT-3
Duan,
Well one reason is a netbios output-access-filter will not do anything
in this case. All the clients it would effect are on the local LAN and
have access to hosts A-C already. A Netbios input-access-filter will
filter what is seen by incoming clients from the remote RSRB as being
available host services. The example states that you only want host A
and B accessed from the other RSRB end and not have host C available.
You are trying to limit access coming into the interface not going out.
This example could have used the following list instead and it would
work the same as in this example.
netbios access-list host filter1 deny C
netbios access-list host filter1 permit *
Not as good a practice as allowing only what you want to be seen. If you
added another netbios host in the future you would have to change this
list to reflect denying it. The original list would still only allow A
and B to be accessed from the RSRB.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
duan
Sent: Friday, June 28, 2002 4:56 AM
To: ccielab@groupstudy.com
Subject: netbios input-access-filter
Hi
i'm confused with netbios host filter because i know little of
netbios.the situation like this ,three host A ,B,C attached with
tokenring 0/0,i want the only A and B can be access from other RSRB end
.cisco CD can give configuration like follow
netbios access-list host filter1 permit A
netbios access-list host filter1 permit B
interface tokenring0/0
netbios input-access-filter filet1 ! why not netbios
output-access-filter
why it's input-access-filter instead of output-access-filter. I think
that 'netbios output-access-filter filet1' is more reasonable
.
please give some reason why input not output
thanks in advance
This archive was generated by hypermail 2.1.4 : Tue Jul 02 2002 - 08:12:43 GMT-3