Segmenting Network Traffic?

[davidw...@my-deja.com]

Doug,

*NICE* posting <pardon my snipping it down to size but it was BIG> ;)

I have IntranetWare at work running IPX <yeah, I know> on a single
segment network <gasp> spanning a 128k WAN. I did break up the NDS into
seperate partitions and replicated them locally. Additionally I bought
a Layer 2 Switch <non-manageable> on which I put one hub of users. The
switch made a difference to those on the hub plugged into the switch.
The overall problem of my WAN is the network is one segment <number>. I
have 2 Nic's in the server now and I want to use IPX routing to control
the WAN portion and isolate LAN traffic to the local network. I'm going
to try the Novell Server as a router but one <big> question:

Can you mention the NLM's used to do this?

Thanks,
David.
--
David Morris / CNA
NetWare / IntranetWare / NT Integration Specialist
Red Hat Linux 6.0 user ;)

In article <8533cr$mk...@nexus.provo.novell.com>,
"Doug Weathers" <weat...@metro.dst.or.us> wrote:

<--<snip>-->

> Note that you can configure a NetWare server as a router by sticking
in
> another Ethernet card. I have several systems set up this way - a
> building's file server will have two network cards in it, one
connected to
> the backbone and one connected to the internal network of the
building.
> Then the server is configured to route packets depending on the needs
of the
> building's users. NetWare servers can route IP, IPX, and AppleTalk,
just
> like those expensive Cisco routers. It works great, but the drawback
is
> that if a server goes down you lose your router and therefore your
> connection to the rest of the world. (Technically, the AppleShare NLM
> doesn't do any routing - it only provides file service to the Macs
using
> their native AppleShare protocol. The routing is done by NetWare
itself,
> and it works whether or not you've purchased the AppleShare NLM.
NetWare
> ships with several protocols in the box, including IP, IPX, and
AppleTalk,
> and it can route all of these.)
>
> Generally people set up a backbone network that runs between the
buildings,
> and hook all the building routers to the backbone. Shared resources
like
> the Internet connection will go on the backbone, but nothing else
should be
> there.
>
> Now you can configure the routers to stop all IPX and AppleTalk
traffic from
> passing through. This reduces the traffic on the backbone, but
prevents
> people using those protocols from accessing IPX and AppleTalk
resources in
> other buildings. In practice this will prevent Mac users (and
Windows users
> using IPX clients) in one building from accessing servers and
printers in
> another building, at least until IP clients are available for those
> machines. (Prosoft is working on a pure IP client for the Mac.)
>
> So we've talked about segmenting networks with routers. Now let's
talk
> about segmenting networks with switches.
>
> Switches are kind of like routers, but they work differently. First
of all
> they divide the network up into a whole bunch of parts (instead of
just two
> or so for a router), and second they pass broadcast packets.
Switches make
> good replacements for Ethernet hubs - generally you can pull out a
hub and
> insert a switch and be back on line in a few minutes. Switches don't
need a
> lot of configuration, unlike routers.

<--snip-->

Sent via Deja.com http://www.deja.com/
Before you buy.

[Hansang Bae]

davidw...@my-deja.com writes:
>I have IntranetWare at work running IPX <yeah, I know> on a single
>segment network <gasp> spanning a 128k WAN. I did break up the NDS into
>seperate partitions and replicated them locally. Additionally I bought
>a Layer 2 Switch <non-manageable> on which I put one hub of users. The
>switch made a difference to those on the hub plugged into the switch.
>The overall problem of my WAN is the network is one segment <number>. I
>have 2 Nic's in the server now and I want to use IPX routing to control
>the WAN portion and isolate LAN traffic to the local network. I'm going
>to try the Novell Server as a router but one <big> question:
>Can you mention the NLM's used to do this?

NetWare will automatically route IPX out of the box. But please read up
about NLSP and SAP at support.novell.com.

Just assign different IPX network numbers on the two NICs. You'll most
likley have to run dspreair to let it know about the new network numbers
on the old server (the one across the WAN)

*********** Remove the REMOVE if emailing me directly **************
Due to the volume of email that I receive, I may not not be able to
reply to emails sent to my account. Please post a followup instead.
********************************************************************
Hansang Bae Director of Network Operations, Eastern Region
hb...@richeysystems.com Reg. Office: (718) 352-9021
Specializing in Network Design/Troubleshooting and Protocol Analysis
********************************************************************

[Cameron Plato]

set up the advanced IPX settings to turn on filtering. read up a bit on
this, it will save you a lot of time.
<davidw...@my-deja.com> wrote in message
news:860kig$aq0$1...@nnrp1.deja.com...

> Doug,
>
> *NICE* posting <pardon my snipping it down to size but it was BIG> ;)
>

> I have IntranetWare at work running IPX <yeah, I know> on a single
> segment network <gasp> spanning a 128k WAN. I did break up the NDS into
> seperate partitions and replicated them locally. Additionally I bought
> a Layer 2 Switch <non-manageable> on which I put one hub of users. The
> switch made a difference to those on the hub plugged into the switch.
> The overall problem of my WAN is the network is one segment <number>. I
> have 2 Nic's in the server now and I want to use IPX routing to control
> the WAN portion and isolate LAN traffic to the local network. I'm going
> to try the Novell Server as a router but one <big> question:
>
> Can you mention the NLM's used to do this?
>