From: Mark Lewis (markl11@xxxxxxxxxxx)
Date: Mon Aug 21 2000 - 10:55:46 GMT-3
Hi all,
Simon, I can see you say that you can use dlsw bgroup-list OR dlsw
bridge-group. I thought that were used in conjunction - am I wrong ?
ie.
dlsw bridge-group 1 (makes bridge-group 1 eligible for dlsw)
dlsw bgroup-list 5 bgroups 1 (which puts bridge-hroup 1 in bgroup-list 5)
dlsw remote peer 5 tcp x.x.x.x (links remote peer to bgroup 5)
bridge 1 prot ieee
int e0
bridge-group 1
I think that's correct.
Mark
>From: Simon Baxter <Simon.Baxter@au.logical.com>
>Reply-To: Simon Baxter <Simon.Baxter@au.logical.com>
>To: SIT Yao Fucheng <yaofucheng@sbell.com.cn>
>CC: ccielab@groupstudy.com
>Subject: RE: ??: about dlsw icanreach mac
>Date: Mon, 21 Aug 2000 18:48:41 +1000
>
>I've never used the dlsw port-list command on an ethernet interface - but I
>would imagine you'd be better to use the 'dlsw bgroup-list' or 'dlsw
>bridge-group' commands to actually TIE in the DLSW to a bridge group
>number.
>
>
>If you only wanted to pass bridged traffic from the one interface, then use
>the port list command. If you want to include all bridged traffic in a
>bridge number, use the bridge-group command
>
>ie
>
>dlsw bridge-group 1
>!
>int e0
>bridge-group 1
>!
>int e1
>bridge-group 1
>!
>bridge 1 protocol ieee
>!
>
>
>
>I haven't tried this :
>
>dlsw local-peer peer-id 7.7.7.7
>dlsw port-list 2 Ethernet0
>dlsw remote-peer 2 tcp 2.2.2.2
>!
>
>But I guess it would work - as the port-list command lists ethernet
>interfaces.
>
>
>Anyone else got any idea on this????
>
>-----Original Message-----
>From: SIT Yao Fucheng [mailto:yaofucheng@sbell.com.cn]
>Sent: Monday, August 21, 2000 6:40 PM
>To: Simon Baxter
>Cc: ccielab@groupstudy.com
>Subject: ??: about dlsw icanreach mac
>
>
>Thanks ! Simon Baxter ,your are right !
>Can you tell another question : when we use dlsw bgroup-list or dlsw
>port-list , Is the two have the same effect for Ethernet bridge-group
>interface,
>for example : dlsw remote 1 tcp x.x.x.x (dlsw port-list 1 ether 0 or
>dlsw bgroup-list 1 bridge group 2 & int e 0 ¨Cbridge group 2) ,what¡¯s the
>different ?
>thanks for any reply !!
>
> ----------
> ¡¤¡é1/4t¨¨?: Simon Baxter [SMTP:Simon.Baxter@au.logical.com]
> ¡¤¡é?¨ª¨º¡À1/4?: Monday, August 21, 2000 16:01
> ¨º?1/4t¨¨?: SIT Yao Fucheng; ccielab@groupstudy.com
> ?¡Â¨¬a: RE: about dlsw icanreach mac
>
> I would think it's
> dlsw icanreach mac 1111.1111.0000 mask ffff.ffff.0000
>
> even though the docs says : The "f" value represents the "don't
>care" bit
> and the "0" value represents the "care" bit, I think it's mis-worded
>when
> everything else refers to 'mask' and not 'wildcards'.
>
>
>
>
> -----Original Message-----
> From: SIT Yao Fucheng [mailto:yaofucheng@sbell.com.cn]
> Sent: Monday, August 21, 2000 5:36 PM
> To: ccielab@groupstudy.com
> Subject: about dlsw icanreach mac
>
>
> Hi erveryone:
> The follow describe in the 12.0 cd about mac mask is different
>with the
> command line describ in the router (MASK set a Mac Mask ¨CMACx is
> reachable if( MACx & MASK)==MACVALUE) .
> If I want announce the mac from 1111.1111.0000 to 1111.1111.ffff
>which will
> be true
> 1. dlsw Icanreach mac 1111.1111.0000 mask 0000.0000.ffff
> 2. dlsw icanreach mac 1111.1111.0000 mask ffff.ffff.0000
>
> thanhs !!
>
>
> the cd 12.0 ios as follow:
> dlsw icanreach
> Use the dlsw icanreach global configuration command to configure a
>resource
> that is locally reachable by this router. 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-addr
> [mask mask] | netbios-name name | saps}
>
> Syntax Description
> mac-exclusive
> Router can reach only the MAC addresses that are user configured.
>
> netbios-exclusive
> Router can reach only the NetBIOS names that are user configured.
>
> remote
> 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-addr
> Configures 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.
>The mask
> indicates which bits in the MAC address are relevant.
>
> netbios-name name
> Configures 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.
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:24:28 GMT-3