IGNITe/400 Mailing List Archive Entry
Hi Bob the interfaces on the 400 are all on the same network we just wanted
to physically separate the traffic so make use of the two TR cards. Both use
an Internal 10 class to cover all the offices and I don't think under V370
this can be done? I wanted to analyse the traffic coming in from the remote
offices without having any effect from internal devices such as NC's. I
think we will have to run a big LAN till they upgrade to V420 in the near
future.

Thanks Bleddyn

-----Original Message-----
ign_list@ignite400.org [mailto:ign_list@ignite400.org]
Sent: 29 July 1998 15:42
To: Ignite400 Members List Mailing List
RE: Multiple Interfaces Under 370


Bob Crothers

Bleddyn,

The 2 NIC's should be on different networks based on the IP address
and Subnet masks. Correct?

The default route should be pointing (next hop address) at an IP
address (of a router or routing device) in the same network as one of
the NIC's. This probably is your internet router. Everything should
then go over that NIC.

You can then setup routings for the networks on the other NIC so stuff
that goes over routers on that segment will get thru.

At least, this is how I understand the AS/400 static routings.

Bob

-----Original Message-----
Ignite400 Members List [SMTP:ign_list@ignite400.org]
Sent: Wednesday, July 29, 1998 1:40 PM
To: Ignite400 Members List Mailing List
Multiple Interfaces Under 370

Bleddyn Williams

Don't know if anyone has seen this or knows a way to get round it but
we
have been working with a customer who has two token ring cards in the
400.
On one we have separated it of with a separate MAU's to point to
another
network with its own router while the other connects the local office
and
the Internet connection to the 400.

They both run TCP/IP but the problem is there is no way to define a
route to
an interface and what is happening is that IP wants to send traffic
down the
wrong side. So it thinks the default route is down the non Internet
connection and promptly starts sending all packets down there. Now on
TR
when you ping it sends the request out to the network and you are then
unable to ping any of the interfaces sitting on the local office side.
Its
very strange and a pain I can see with 420 and 430 you can bind a
route to
an interface but how can we get round it on V370?

Thanks Bleddyn




Posted by  Subject  Date 

Return to the Mailing List Archive Page
Click to return to home page
© Copyright 1999 by IGNITe/400
This page last updated Sat, 21 Aug 1999 16:41:00