From: George Bekmezian (george@bekmezian.com)
Date: Fri Oct 04 2002 - 11:54:48 GMT-3
You have it a little wrong. The 0 in the remote peer refers to
bgroup-lists and ring-lists. You can basically isolate traffic
communicated with a certain peer to list of rings and bridges.
You would do something like this:
dlsw bgroup-list 1 bgroups 5 10
Dlsw ring-list 1 rings 105 200
Dlsw remote-peer 1 tcp 10.1.1.2
In the above example, the remote peer is limitted to traffic on brige
groups 5 and 10 and ring numbers 105 and 200. So if certain interfaces
were in bridge group 1 for example, they wouldn't be bridged across to
that dlsw peer.
Hope this helps.
George
|-----Original Message-----
|From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
|Behalf Of chenyan
|Sent: Friday, October 04, 2002 7:23 AM
|To: ccielab
|Subject: dlsw problem
|
|
|hi,guys
|
|Using the commands:
|dlsw local-peer peer-id 10.1.1.1
|dlsw remote-peer 0 tcp 10.1.1.2
|I think the 0 means that all the interfaces of the local peer
|can be mapped to the remote peer, and if the 0 is replaced by
|non zero like 1, then I must add the command" dlsw
|bridge-group 1" to map the bridge-group to remote peer. Is it right?
|
|But if the remote peer only use the "dlsw local-peer peer-id
|10.1.1.2 promiscious" then how can I know which interfaces can
|be available to the dlsw traffic?
|
|Thanks
|
This archive was generated by hypermail 2.1.4 : Tue Nov 05 2002 - 08:35:39 GMT-3