From: Joe Chang (changjoe@earthlink.net)
Date: Thu Dec 26 2002 - 20:16:08 GMT-3
I think the original poster of the question got it right, the two "dlsw
icanreach" commands are a means of explorer reduction at a router local to
the resource in question, so they should be on RTB. Eugene may be thinking
of the "dlsw mac-address" command which reduces explorers at a router
remote from the host.
To the owner of the lab, could you do a "show dlsw capabilites" on RTC after
you set up the icanreach statements on RTB? There should be an entry listing
your WebCentral11 mac address. "dlsw icanreach mac-exclusive" sets up an
outgoing packet source address filter and an incoming address destination
filter on RTB and a outgoing packet destination filter on RTC. If you set a
"dlsw icanreach mac-address" with the wrong address or mask you will shut
down the circuit between your two hosts.
----- Original Message -----
From: <eward15@juno.com>
To: <ccielab@groupstudy.com>
Sent: Thursday, December 26, 2002 10:35 AM
Subject: Re:DLSW+ - please help!!!
> I could be wrong, but according to your diagram, I think that you have the
mac-exclusive commands on the woring router. Put them of RTC.
>
> Eugene Ward
>
>
>
> My question - is there any trick to the commands:-
>
> dlsw icanreach mac-exclusive
> &
> dlsw icanreach mac-address ?
>
> I have the following lab setup:-
>
> RTA
> / \
> WebCentral11---RTB RTC --- Hardcat-laptop
>
> Both workstations are on Ethernet.
>
> And the three routers are in a Frame-relay network.
>
> I must have done something fundermentally wrong. Since if I remove the 2
> icanreach
> commands, everything is ok (i.e. I can see Network neighborhood, I can see
the
> DLSW
> circuit up etc). But as soon as I put back the commands, I can't see
anything.
>
> My laptop (WebCentral11)'s MAC address is 0050.04b9.4584.
>
> C:\>ipconfig /all
>
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : FE575C-3COM 10/100 LAN CardBus-Fast
> Ethernet
> Physical Address. . . . . . . . . : 00-50-04-B9-45-84
> Dhcp Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> Autoconfiguration IP Address. . . : 169.254.205.7
> Subnet Mask . . . . . . . . . . . : 255.255.0.0
> Default Gateway . . . . . . . . . :
>
> C:\>
>
> And I have confirmed it with:-
>
> RTB#sh bridge
>
> Total of 300 station blocks, 298 free
> Codes: P - permanent, S - self
>
> Bridge Group 1:
>
> Address Action Interface Age RX count TX count
> 0050.ba76.ea5f forward DLSw Port0 0 1 1
> 0050.04b9.4584 forward Ethernet0 0 1 0
> RTB#
>
> RTC#sh bridge
>
> Total of 300 station blocks, 298 free
> Codes: P - permanent, S - self
>
> Bridge Group 1:
>
> Address Action Interface Age RX count TX count
> 0050.ba76.ea5f forward Ethernet0 0 9 1
> 0050.04b9.4584 forward DLSw Port0 0 1 3
> RTC#
>
> And here's the config:-
>
> For RTB-
>
> dlsw local-peer peer-id 1.1.1.1 promiscuous
> dlsw icanreach mac-exclusive
> dlsw icanreach mac-address 0050.04b9.4584 mask ffff.ffff.ffff
> dlsw bridge-group 1
>
> interface Loopback0
> ip address 1.1.1.1 255.255.255.255
>
> interface Ethernet0
> no ip address
> bridge-group 1
>
> bridge 1 protocol ieee
>
> As for RTC-
>
> dlsw local-peer peer-id 2.2.2.2
> dlsw remote-peer 0 tcp 1.1.1.1
> dlsw bridge-group 1
>
> interface Loopback1
> ip address 2.2.2.2 255.255.255.255
>
> interface Ethernet0
> no ip address
> bridge-group 1
>
> bridge 1 protocol ieee
>
>
> It would be greatly appreciated if anyone can shed some light on this.
>
>
>
>
>
>
> ________________________________________________________________
> Sign Up for Juno Platinum Internet Access Today
> Only $9.95 per month!
> Visit www.juno.com
> .
.
This archive was generated by hypermail 2.1.4 : Fri Jan 17 2003 - 17:21:53 GMT-3