From: Ben_J_Durand@xxxxxxxxxx
Date: Sun Mar 26 2000 - 20:36:42 GMT-3
Earl,
We understand that this is what the docs say, but the IOS command line help on
the router and apparently some other published books say it's the other way.
We're just trying to figure out which was is the correct way :)
- Ben
Earl Aboytes <earl@linkline.com> on 03/26/2000 06:45:07 PM
To: "Mosley, Arthur" <Arthur.Mosley@wang.com>, ccielab@groupstudy.com, Ben J
Durand/Tivoli Systems@Tivoli Systems
cc:
Subject: Re: FW: DLSW clarification on mac address filter/ICANREACH exchange
Here is a direct posting from the Doc CD
dlsw icanreach
To configure a resource that is locally reachable by this router, use the dlsw
icanreach global configuration command. Use the no form of this command to
remove the resource.
dlsw icanreach {mac-exclusive | netbios-exclusive [remote] | mac-address
mac-addr [mask mask] | netbios-name name | saps}
no dlsw icanreach {mac-exclusive | netbios-exclusive [remote] | mac-address
mac-add [mask mask] | netbios-name name | saps}
Syntax Description
mac-exclusiveRouter can reach only the MAC addresses that are user configured.
netbios-exclusiveRouter can reach only the NetBIOS names that are user
configured.
remote(Optional) Gives the NetBIOS workstations (that are local to the router
and that are not already defined in the dlsw icanreach netbios-name name
statement) access to remote servers.
mac-address mac-addrConfigures a MAC address that this router can locally reach
.
mask mask(Optional) MAC address mask in hexadecimal h.h.h. The "f" value
represents the "don't care" bit and the "0" value represents the "care" bit. Th
e
mask indicates which bits in the MAC address are relevant.
netbios-name nameConfigures a NetBIOS name that this router can locally reach.
Wildcards (*) are allowed at the end of the name. Trailing white spaces are
ignored when comparing against an actual name in a NetBIOS frame.
saps (Optional) Array of SAPs.
At 05:50 PM 3/26/00 -0500, Mosley, Arthur wrote:
>I am confused also! Here's one I posted earlier this month.
>
>Art
>
>p.s. I guess this is one for the CCIGs (lower case g od). I'll test it if
>I can find the time and equipment.
>
>-----Original Message-----
>From: Mosley, Arthur [mailto:Arthur.Mosley@wang.com]
>Sent: Sunday, March 12, 2000 11:54 PM
>To: 'ccielab@groupstudy.com'
>Subject: DLSW clarification on mac address filter/ICANREACH exchange
>
>
>Are the masks for mac address filters and ICANREACH commands the opposite of
>each other? I cannot find a good example that explains the ICANREACH mask.
>
>Art
>
>
>
>Vendor code filter - filters explorer packets sent out from router
>vendor portion/any portion of Mac address
>
>700-799 48-bit MAC address access list
>access-list 704 deny 0260.8c00.0000 0000.00FF.FFFF - deny's 3Com NICs
>access-list 704 permit 0000.0000.0000 FFFF.FFFF.FFFF - permit all others
>
>dmac-output-list - mac address filter
>F's are don't care
>0's must match
>
>
>ICANREACH - will prevent a router from sending out an explorer packet
>because it is learned during the capabilities exchange process.
>
>dlsw icanreach mac-address 0006.e9db.31ce mask ffff.ffff.ffff
>
>F's mush match
>
> >From Configuring Cisco Routers for Bridging, DLSw+ & Desktop Protocols
>Mcgraw-Hill publishing - written by Tan Nam-Kee
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:06 GMT-3