The configuration isn't a problem, each server will send data to the router
which will forward it on. You can eliminate the router from the
communications by putting static ARP enties in the servers for each other IP
addresses. We currently do this to support a legacy application that has
the IP address of the host hard coded into the application.
> b. With the above configuration, will there be two
> route entries in the router and other routers that the
> router in this case is communicating to?
>
The router will automatically insert two static routes for both IP addresses
assigned to the interface. If you are using a routing protocol both will be
distributed as well otherwise you will need to put the routes into other
routing devices or use the appropriate default route.
> c. Is NT, Solaries, OS/2 and Linux supports secondary IP?
Solaris and NT allow multiple IP address assignment to a single interface,
I'm pretty sure Linux does to put I know about OS/2
> d. What is the performance impact (CPU,memory, processing speed) to router
> and server?
You are requiring the router to process packets between the two networks,
you can avoid this by using static ARP enties.
> e. Will the above setup protect server A from accessing server B?
I theory yes, you can install filters in the router to drop inter-server
communications but someone with the ability to add static ARP enties could
easily bypass the router.
You might want to consider a VLAN capable switch instead of a hub
Bill Stackpole, CISSP
Voice/Data Manager
Olympic Resource Management
19245 Tenth Ave NE
Poulsbo, WA 98370
Voice: 360-697-6626 Fax: 360-697-7519
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
[EMAIL PROTECTED]
**********************************************************************
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
