Here i would like to share the network design that my group assignment
has made using a fake organization called Moritz Law firm.
***organization background***
Moritz Law Firm has exists in Australia for more than 5 years with two
branches located in Sydney and Melbourne. So far each branch has been able to
manage its own network (LAN) with its own documents and legal papers. Every time a
document or legal paper needed by the other branch, a mail was posted or attached
via e-mail when possible in terms of document size. However, due to the increase of
clients and expansion of the business, Moritz Law Firm has decided to interconnect
the two branches so that all data can be centralized for easier and better
management purposes. Besides it main goals is also to get a faster data transfer
between the branches. In Moritz Law Firm, it is essential to ensure that documents
are safe and used for proper purposes only, it should only be accessible for
authorized users and in a secure environment.
Based on the organization background, it is clear that the network will
need to connect the two LANs so that all documents are available for both
branches in a centralised database. However, some documents or legal papers are in high level of confidentiality that its permission should be limited. This means that
particular users will need to grant the permission before accessing the documents.
Sunday, July 19, 2009
Friday, May 29, 2009
Why we use this services?
Below are the lists of services and feature that the network includes in Moritz Law Firm.
Dynamic Host Configuration Protocol (DHCP)
To enable load balancing and wireless users on the network, DHCP will be
installed on each router. DHCP will assign IP addresses required by hosts inside
the LAN dynamically so that balance traffic for each IP address can be managed.
At least one network administrator on each LAN will have to manage and monitor the
information stored for each IP addresses assigned to a host.
Domain Name System (DNS)
Moritz Law Firm has currently managed a website from its web server in
Sydney.
However the web server will no longer served for static purposes only but
also as the interface for the new system. The new system will make the use of FTP
service to enable file upload and sharing that will be accesses through a browser as
an interface.
Apache - SSL
Apache is installed to serve the web site. It comes along with an SSL features that will enable the creation of a secure and reliable web system (The Apache HTTP Server
Project, 2009). It will then lead the website to make the use of HTTPS to secure the
web pages and its content from unauthorized users. Here users will need to gain a
certificate authority before actually logged in to the system. It will assist the network monitoring at the same time.
File Transfer Protocol (FTP)
To enable data sharing between the two branches, all files will need to be uploaded to the server. There are times when staff in Melbourne will be required to upload a file to the Sydney server directly or vice versa.
To do so, an FTP server is installed. Anonymous access has been disabled for security purposes so that only authorised users can access and use the server.
SSH
Due to the business atmosphere, SSH is installed in the server for data encryption
especially when high level of confidentiality document is about to accessed. This
service will allow users with higher level of authority to access important document.
Simple Network Management Protocol (SNMP)
SNMP is installed to allow monitoring of the entire network attached devices in the
network that may help the administrator to get through problems quickly (Zend
Technologies Ltd., 2009). SNMP is installed in the server and each workstation will
get act as an SNMP agent so that the network administrator can monitor each devices
remotely.
MRTG
To ensure that network traffic is keep in a reasonable load, a network monitoring
traffic is installed. MRTG is chosen since the network employs SNMP which make it
easier to use MRTG. Using MRTG, the network administrator may get a graph showing the traffic load for each five minutes. The OID is set to five minutes to allow time to time monitoring.
SQUID
The main purpose to install SQUID proxy server is to do traffic filtering which
include some websites access blocking so that only certain websites is allowed to be
access by staff. It is done to keep the load traffic low and in an appropriate use.
Another reason to install SQUID is to do web caching since only few defined
websites is accessible through the network which means caching will be extremely
helpful to speed up the network speed.
Dynamic Host Configuration Protocol (DHCP)
To enable load balancing and wireless users on the network, DHCP will be
installed on each router. DHCP will assign IP addresses required by hosts inside
the LAN dynamically so that balance traffic for each IP address can be managed.
At least one network administrator on each LAN will have to manage and monitor the
information stored for each IP addresses assigned to a host.
Domain Name System (DNS)
Moritz Law Firm has currently managed a website from its web server in
Sydney.
However the web server will no longer served for static purposes only but
also as the interface for the new system. The new system will make the use of FTP
service to enable file upload and sharing that will be accesses through a browser as
an interface.
Apache - SSL
Apache is installed to serve the web site. It comes along with an SSL features that will enable the creation of a secure and reliable web system (The Apache HTTP Server
Project, 2009). It will then lead the website to make the use of HTTPS to secure the
web pages and its content from unauthorized users. Here users will need to gain a
certificate authority before actually logged in to the system. It will assist the network monitoring at the same time.
File Transfer Protocol (FTP)
To enable data sharing between the two branches, all files will need to be uploaded to the server. There are times when staff in Melbourne will be required to upload a file to the Sydney server directly or vice versa.
To do so, an FTP server is installed. Anonymous access has been disabled for security purposes so that only authorised users can access and use the server.
SSH
Due to the business atmosphere, SSH is installed in the server for data encryption
especially when high level of confidentiality document is about to accessed. This
service will allow users with higher level of authority to access important document.
Simple Network Management Protocol (SNMP)
SNMP is installed to allow monitoring of the entire network attached devices in the
network that may help the administrator to get through problems quickly (Zend
Technologies Ltd., 2009). SNMP is installed in the server and each workstation will
get act as an SNMP agent so that the network administrator can monitor each devices
remotely.
MRTG
To ensure that network traffic is keep in a reasonable load, a network monitoring
traffic is installed. MRTG is chosen since the network employs SNMP which make it
easier to use MRTG. Using MRTG, the network administrator may get a graph showing the traffic load for each five minutes. The OID is set to five minutes to allow time to time monitoring.
SQUID
The main purpose to install SQUID proxy server is to do traffic filtering which
include some websites access blocking so that only certain websites is allowed to be
access by staff. It is done to keep the load traffic low and in an appropriate use.
Another reason to install SQUID is to do web caching since only few defined
websites is accessible through the network which means caching will be extremely
helpful to speed up the network speed.
Sample named.conf.local file
This one is sample named.conf.local file for DNS configuration.
Edit the name of the zone based on your domain name.
Hope it helps.
***Sample named.conf.local file***
include "/etc/bind/zones.rfc1918";
zone "1.1.10.in-addr.arpa"
{
//reverse lookup for moritz
type master;
file "/etc/bind/db.1.1.10";
};
acl trustedhosts
{
192.168.1.0/24; //any host from local host
};
zone "moritz"
{
//our domain
type master;
file "/etc/bind/db.moritz";
allow-transfer
{trustedhosts;};
};
server 192.168.1.254
{
transfer-format many-answers;
};
Edit the name of the zone based on your domain name.
Hope it helps.
***Sample named.conf.local file***
include "/etc/bind/zones.rfc1918";
zone "1.1.10.in-addr.arpa"
{
//reverse lookup for moritz
type master;
file "/etc/bind/db.1.1.10";
};
acl trustedhosts
{
192.168.1.0/24; //any host from local host
};
zone "moritz"
{
//our domain
type master;
file "/etc/bind/db.moritz";
allow-transfer
{trustedhosts;};
};
server 192.168.1.254
{
transfer-format many-answers;
};
Labels:
configure dns,
dns,
domain,
named.conf. configuration,
named.conf.local
Sample dhcpd.conf file
Here a sample configuration file for DHCP.
Hope it can be helpful.
Sample dhcpd.conf:
{
ddns-update-style none;
option domain-name "moritzlawfirm";
option domain-name-servers 192.168.1.254;
default-lease-time 600;
max-lease-time 7200;
log-facility local7;
subnet 192.168.1.0 netmask 255.255.255.0
{ range 192.168.1.1 192.168.1.20;
option routers 192.168.1.254;
}
host vpc01
{
hardware ethernet 00:11:11:6d:ee:97;
fixed-address 10.1.1.99;
}
}
Hope it can be helpful.
Sample dhcpd.conf:
{
ddns-update-style none;
option domain-name "moritzlawfirm";
option domain-name-servers 192.168.1.254;
default-lease-time 600;
max-lease-time 7200;
log-facility local7;
subnet 192.168.1.0 netmask 255.255.255.0
{ range 192.168.1.1 192.168.1.20;
option routers 192.168.1.254;
}
host vpc01
{
hardware ethernet 00:11:11:6d:ee:97;
fixed-address 10.1.1.99;
}
}
Subscribe to:
Posts (Atom)