From: Tom Young (gitsyoung@xxxxxxxxxxx)
Date: Mon Jun 03 2002 - 11:55:15 GMT-3
Hansang, thanks for your reply. My lan is ethernet lan.
And you said it could be policy routing, I want to ask you
dose the SNA packet could be policy ROUTNG?
Thanks
Young
--- Hansang Bae <hbae@nyc.rr.com> $B$+$i$N%a%C%;!<%8!'(B
> At 04:36 PM 5/30/2002 +0900, Tom Young wrote:
> >I have two routers
> > ---------------------------LAN
> > | |
> > R1 R2
> > | |
> > | |
> > R3 R4
> >
> >R1 and R2 in a same LAN, I have some packet in the
> LAN,
> >include SNA.Notes,http,etc. Default gateway is R1.
> I want
> >to route all the SNA packet to R1, else will be
> routed to
> >R2.
> >If I make a Dlsw peer between R1and R3. And a
> static
> >routing 0.0.0.0 0.0.0.0 R2'lan address.
> >Does this way working? Because R2 and R4 havn't the
> dlsw
> >so all of the SNA will be done in the R1, and
> others will
> >be routed locally.
>
>
> If the DLSW+ peer for R1 is R3, then this might
> work. But you're going to have to use R3's serial
> interface for the peer's IP address. Otherwise, R1
> won't know where to send it since his default
> gateway is R2. This would be trivial *IF* the
> match clause in policy routing supports 200 level
> ACLs. Normally, those are not honored unless you
> are bridging. You might give it a shot to see if
> the "match ip address 2xx" will work or not. Then
> you can point everyone to R2, and R2's policy
> routing will say, anyone needing SNA service should
> have it's next-hop/ip as R1s LAN interface.
>
> Also, is your LAN a TR LAN or an Ethernet LAN?
>
> hsb
>
This archive was generated by hypermail 2.1.4 : Tue Jul 02 2002 - 08:12:22 GMT-3