Distributor–Retailer Management Network Design

Using Cisco Packet Tracer

Group Members:
Ammar Y. Sami – [A]
Saif Al-Deen M. Ramadan – [A]
Mohammed N. Nawfal – [A]

Date:
[ 2025 / Nov 27 ]

Abstract
This project presents the design and simulation of a computer network that connects a central
Distributor (head office) with three Retailer branches using Cisco Packet Tracer. The
scenario reflects a small city or town where the distributor is responsible for managing stock,
exchanging order information, and maintaining continuous communication with all retailers.
The network is implemented as a hub-and-spoke topology, with the Distributor at the core
and each Retailer connected via a dedicated wide area network (WAN) link.

The design integrates several key services typically required in a modern business
environment: local area networking (LAN) at each site, WAN connectivity between sites,
wireless access for mobile clients, IP telephony (VoIP) for voice calls, server-based web
and email services, and network printing. Cisco Packet Tracer is used as the simulation
platform, as it allows the creation, configuration, and testing of virtual networks with routers,
switches, servers, and end devices in an educational environment.([Link])

The primary objective of the project is to design a scalable, maintainable, and secure
network that fulfills functional requirements while respecting realistic constraints on devices
and complexity. The report documents the full life cycle of the design, from requirements
analysis and topology choice to IP addressing, routing, services configuration, security
measures, and verification tests. Results show that the proposed network successfully delivers
end-to-end connectivity, integrated services, and a clear structure that can be easily extended
to support additional retailers or new services in the future, aligning with best practices for
small enterprise network design.([Link])

Table of Contents
1. Introduction
1.1 Background and Motivation
1.2 Purpose and Goals
1.3 Scope
2. Network Requirements and Specifications
2.1 Functional Requirements
2.2 Non-Functional Requirements
2.3 Constraints
3. Design Overview / Topology
3.1 Logical Topology
3.2 Physical Topology
3.3 Site Descriptions
4. Device Inventory and Role Description
5. IP Addressing and Subnetting Plan
5.1 Addressing Principles
5.2 Subnet Allocations per Site
5.3 Example IP Assignment
6. Routing and Connectivity Configuration
7. Services Configuration and Implementation
8. Security Considerations
9. Testing and Verification
10. Results and Observations
11. Scalability and Future Enhancements
 12. Conclusion
13. Appendices
14. References

1. Introduction
1.1 Background and Motivation

Retail and distribution businesses depend heavily on timely, accurate information flow
between the central warehouse or distributor and the individual retail outlets. Stock levels,
purchase orders, invoices, pricing updates, and customer data must move reliably and
securely between locations. Without a proper network, these processes become slow, manual,
and error-prone, reducing efficiency and directly impacting revenue.

In many training and academic contexts, such real-world scenarios are modeled using Cisco
Packet Tracer, a network simulation tool that allows students and engineers to design and
test network topologies using virtual routers, switches, PCs, servers, and IoT devices.
([Link]) This project adopts exactly that approach: a small but realistic environment
where one Distributor coordinates activities with three Retailer branches, each having its
own local users and services but relying on the central site for management and some shared
infrastructure.

The motivation behind this network is twofold:

1. From a business perspective, to provide a communication backbone that supports

day-to-day distributor–retailer operations (orders, emails, reports, voice calls, etc.).
2. From a technical/educational perspective, to demonstrate good network design
practice—clear topology, structured IP addressing, basic security, and service
integration—on a scale that is understandable for students but still realistic compared
to small enterprise networks.(Scribd)

1.2 Purpose and Goals

The main purpose of this project is to design, implement, and document a complete
network solution for a distributor–retailer environment using Cisco Packet Tracer. The design
must connect:

 One Distributor (head office)

 Three Retailers (branch offices)

and support a range of services: LAN, WAN, Wi-Fi, VoIP, printing, and servers.

The specific goals are:

  To build a hub-and-spoke topology with the Distributor at the center, providing a
clear and easily manageable structure.(Selector)
 To provide reliable connectivity between all four sites so that data, voice, and
management traffic can be exchanged without manual intervention.
 To integrate multiple networked services (web, email, DHCP, DNS, wireless access,
IP phones, and printing) on top of the IP infrastructure.
 To apply sound network design principles—scalability, reliability, security, and
documentation—aligned with established best practices in enterprise network design.
([Link])
 To validate the design through structured testing and verification, using tools and
commands available in Packet Tracer.

1.3 Scope

The project focuses on the internal private network of the organization. The scope includes:

 A central Distributor site with a router, switch, server, PC, IP phone, printer, wireless
access point, smartphone, and tablet.
 Three Retailer sites with largely identical device sets, each having its own small LAN.
 Interconnection of all four sites through simulated WAN links between routers.
 Design and documentation of:
o Logical and physical topology
o IP addressing and subnetting
o Routing configuration
o Server, wireless, VoIP, and printing services
o Basic security measures (segmentation, device hardening, wireless protection)
o Tests to verify that each requirement is satisfied

The project does not focus on Internet connectivity, MPLS, VPNs, or advanced data center
features. Those remain potential future enhancements, outside the core scope of this report.

2. Network Requirements and Specifications

2.1 Functional Requirements

Functional requirements describe what the network must do from a user and business
perspective. For this project, the key functional requirements are:

1. Local Area Network (LAN) within each site

o Each site must have a working Ethernet LAN connecting the router, switch,
server, PC, IP phone, printer, and access point.
o Devices on the same site must be able to communicate using IP, allowing
employees to reach local resources with low latency.
2. Wide Area Network (WAN) between sites
o The Distributor must be connected to each Retailer over separate WAN links.
o Any host at the Distributor should be able to reach any host at a Retailer, and
vice versa, using routed IP connectivity.
 3. IP Telephony (VoIP)
o IP phones at the Distributor and the three Retailers must be able to call each
other using internal extensions.
o Voice traffic should traverse the same converged network as data, illustrating
the integration of voice over IP.
4. Wireless Connectivity
o Each site must provide Wi-Fi coverage via an access point.
o Smartphones and tablets must connect to the LAN through secure wireless
connections and obtain IP addresses from DHCP.
5. Server-Based Services
o At least one server (typically at the Distributor) must provide web and email
services to users at all sites, reflecting real enterprise applications.(Scribd)
o Optional additional services include DNS and file sharing.
6. Network Printing
o Each site must have a network printer accessible from the local PC (and
optionally from its server).
o Printing should work using the printer’s IP address, demonstrating resource
sharing over the LAN.

These functional requirements ensure that the network supports the core daily activities of a
distributor–retailer operation: communication, information sharing, and document handling.

2.2 Non-Functional Requirements

Non-functional requirements capture how well the network must operate, not just what it
must do. For this project, the most important non-functional requirements are:

1. Scalability
o The design must support the easy addition of new Retailer sites without large
redesign.
o Using separate subnets and a hub-and-spoke topology makes it straightforward
to add more branches later.(Selector)
2. Reliability
o Links between routers should be stable and deterministic in the simulation.
o Routing should be configured in a way that avoids ambiguous or conflicting
routes.
3. Security (Baseline Level)
o Access to device management (console and remote) should require passwords.
o Wireless networks should use encryption (e.g., WPA2-PSK) to prevent casual
unauthorized access.
o Basic segmentation between different sites through separate subnets reduces
broadcast domains and limits the spread of failures or attacks.
([Link])
4. Maintainability and Clarity
o The network should follow a consistent pattern across Retailers: same types
of devices, similar addressing schemes, and similar configurations.
o Clear documentation (IP plan, diagrams, configuration summaries) must be
produced, in line with recommendations that emphasize documentation as a
core part of enterprise network design.([Link])
2.3 Constraints

The design is subject to several constraints, which influence the choices made:

 Simulation Environment Constraint

o All implementation and testing are performed in Cisco Packet Tracer, a
teaching-oriented simulator with a well-defined catalog of device models and
features.([Link])
 Scale Constraint
o The project explicitly focuses on one Distributor and three Retailers, each
with a small number of hosts. It is not intended to model a large nationwide
chain, but rather a small enterprise / small city scenario.
 Device Set Constraint
o Only common devices available in Packet Tracer (such as Cisco 2811 routers
and 2960 switches) are used, reflecting typical lab and CCNA-level
equipment.
 Time and Complexity Constraint
o Advanced mechanisms (e.g., multi-area OSPF, BGP, MPLS VPNs, or full
redundancy) are outside the feasible scope for a single semester-level project
and are therefore treated as potential future enhancements rather than current
requirements.(Scribd)

3. Design Overview / Topology

3.1 Logical Topology

Logically, the network is built as a hub-and-spoke design:

 The Distributor site acts as the hub.

 The three Retailers act as spokes, each connected only to the Distributor, not directly
to each other.

In a hub-and-spoke topology, all communication between spokes flows through the hub,
which simplifies management and centralizes control over routing and security. This pattern
is widely used in small branch-office environments and is recommended when multiple small
locations depend on a central site for shared services.(CBT Nuggets)

In this project:

 Each site (Distributor and Retailers 1–3) has its own IP subnet.
 Routers provide Layer-3 connectivity between these subnets.
 Switches provide Layer-2 connectivity within each LAN.
 WAN links between routers form the hub-and-spoke structure.

The logical data flow is:

  A PC at Retailer 1 → sends traffic to its local router → WAN link → Distributor
router → either a local server at Distributor or onward to another Retailer.
 This centralization reflects the business model, where the Distributor coordinates
stock, pricing, and communication for all branches.

3.2 Physical Topology

Physically, each site follows a standardized layout:

 The router connects to:

o The WAN link (towards the Distributor or from the Distributor),
o The LAN switch (downlink to local devices).
 The 2960 switch acts as the central wiring point for all wired devices:
o Server, PC, IP phone, printer, and access point all plug into switch ports.
 The access point (AP) is placed logically where it can provide good wireless
coverage for the site’s smartphone and tablet clients. In real deployments, AP
placement and RF planning are critical; simulation abstracts away signal strength and
interference, but conceptually we still apply best-practice thinking: APs should be
placed to give reliable coverage for the intended office area.([Link])

Cabling is simple and consistent:

 Ethernet from router LAN interface to switch.

 Ethernet from switch to all wired endpoints.
 Serial or simulated WAN links between routers in Packet Tracer.

3.3 Site Descriptions

Distributor (Head Office)

The Distributor is the core site that hosts shared services and acts as the routing and
management center. Its LAN contains:

 A router with three WAN interfaces (one to each Retailer) and one LAN interface.
 A switch to which all local devices connect.
 A server providing central services (web, email and optionally DNS/DHCP).
 A PC used by staff for management, email, and web access.
 An IP phone for voice communication with Retailers.
 A network printer for printing invoices, reports, and summaries.
 A wireless access point connected to the switch.
 A smartphone and tablet that connect via Wi-Fi.

The Distributor router maintains routes to all Retailer LANs and is effectively the
“backbone” of the organization’s IP connectivity.

Retailer 1, Retailer 2, Retailer 3

Each Retailer site is deliberately designed to be architecturally identical:

 One router (single WAN link to Distributor, one LAN interface).

 One switch aggregating local wired devices.
 One server, one PC, one IP phone, one printer.
  One access point plus smartphone and tablet.

This repetition has two advantages:

1. Maintainability – Once you understand and configure one branch, the others are
almost the same.
2. Scalability – New branches can be brought online by replicating the same pattern
with a new subnet and router link.

4. Device Inventory & Role Description

4.1 Device Inventory

Per site, the inventory is:

 1 × Cisco 2811 Router

 1 × Cisco 2960 Switch
 1 × Server
 1 × PC
 1 × Cisco IP Phone
 1 × Network Printer
 1 × Wireless Access Point
 1 × Smartphone (wireless client)
 1 × Tablet (wireless client)

Across the entire network (Distributor + 3 Retailers), this scales to:

 4 Routers, 4 Switches, 4 Servers, 4 PCs, 4 IP Phones, 4 Printers, 4 APs, 4

Smartphones, 4 Tablets.

4.2 Role Description

 Routers (Cisco 2811)

o Provide inter-site routing between the Distributor and the three Retailers.
o Maintain routing tables and forward packets between different IP subnets.
o Optionally provide DHCP, NAT, or telephony-service features.
 Switches (Cisco 2960)
o Provide Layer-2 Ethernet connectivity within each local site.
o Learn MAC addresses and forward frames efficiently between devices.
o Can support VLANs in more advanced designs.
 Servers
o At Distributor: host web, email, and possibly DNS/DHCP services, acting as
a central application point for the organization.(MSP360)
o At Retailers: can provide local file storage or backup services, reducing
dependency on WAN links for some tasks.
 PCs
 o User workstations for administrative and operational tasks: order entry, email,
printing, reporting, and web access to Distributor applications.
 IP Phones
o Provide voice over IP (VoIP) communication between staff at the Distributor
and Retailers.
o Use internal extensions and rely on a telephony service running on one of the
routers (commonly at the Distributor).
 Network Printers
o Shared printers reachable by IP.
o Allow staff to print documents (invoices, reports, stock lists) from any PC
within the same site.
 Wireless Access Points
o Extend the LAN to wireless clients.
o Bridge traffic from smartphone and tablet into the wired LAN, using WPA2 or
similar security.
 Smartphones and Tablets
o Represent mobile users; they use Wi-Fi to access web apps, email, or
dashboards hosted on the Distributor server.

Documenting a clear device inventory like this is considered a best practice in enterprise
network design, because it ties physical hardware, logical roles, and addressing together for
easier planning and troubleshooting.(Meter)

5. IP Addressing and Subnetting Plan

5.1 Addressing Principles

A clean IP addressing plan is critical to avoid conflicts, support growth, and simplify
routing. Industry guidance emphasizes using structured, summarizable blocks and leaving
headroom for future expansion.(Cisco Jedi)

In this project, the IPv4 plan follows these principles:

 Each site gets its own /24 subnet from the private range [Link]/16.
 Point-to-point WAN links between routers use a small /30 subnet from a separate
private block (e.g., [Link]/24).
 Servers and printers use static IPs, while PCs and Wi-Fi clients are typically assigned
via DHCP.
 Routers use the first usable IP address of each LAN subnet as the default gateway.

5.2 Subnet Allocations per Site (Example)

You can adjust numbers to match your own Packet Tracer file, but a good, consistent scheme
is:

 Distributor LAN: [Link] /24

 Retailer 1 LAN: [Link] /24
  Retailer 2 LAN: [Link] /24
 Retailer 3 LAN: [Link] /24

WAN links:

 Distributor ↔ Retailer 1: [Link] /30

 Distributor ↔ Retailer 2: [Link] /30
 Distributor ↔ Retailer 3: [Link] /30

This design uses contiguous subnets and separates LAN and WAN address spaces, which
aligns with standard recommendations for IP planning and summarization.(CBT IT
Certification Training)

5.3 Example IP Assignment Pattern

For each LAN, you can reuse a pattern to stay organized. Example for the Distributor:

 Router LAN interface: [Link] /24

 Server: [Link]
 PC: [Link]
 IP Phone: [Link]
 Printer: [Link]
 AP: [Link]
 DHCP pool for dynamic clients: [Link] – [Link], default gateway
[Link], DNS [Link].

Retailer 1 repeats the same pattern but with subnet [Link]/24 and gateway
[Link], and similarly for Retailers 2 and 3. This consistent scheme is easy to document
in a table in the final report or appendix.

6. Routing and Connectivity Configuration

6.1 Choice of Routing Method

The network has four routers (one Distributor, three Retailers) in a simple hub-and-spoke
layout. In such small, stable topologies, best-practice guidance is that static routing is often
preferable: it is easier to design, uses fewer resources, and fits star / hub-and-spoke networks
well.(GeeksforGeeks)

Key reasons for choosing static routing here:

 The topology is small and does not change frequently.

 There is a single clear path between sites (no complex multi-path decisions).
 Static routes are easy to understand and document for educational purposes.

Dynamic routing (e.g., RIP, OSPF) could be used as an extension exercise, but is not
necessary to meet the project goals.
6.2 Static Routing Design

The routing logic is:

 Each Retailer router has:

o A default route pointing towards the Distributor router (its only upstream).
 The Distributor router has:
o One directly-connected route to its own LAN.
o Directly connected routes for each WAN link.
o Explicit static routes to each Retailer LAN via the corresponding WAN
interface.

Conceptually:

 Retailer 1: ip route [Link] [Link] <R1-WAN-next-hop>

 Distributor:
o ip route [Link] [Link] <next-hop-to-Retailer1>
o ip route [Link] [Link] <next-hop-to-Retailer2>
o ip route [Link] [Link] <next-hop-to-Retailer3>

This ensures:

 Traffic from a Retailer destined for any unknown network (e.g., another Retailer) is
sent to the Distributor by default.
 The Distributor knows how to send traffic to each Retailer LAN through the
corresponding WAN interface.

7. Services Configuration & Implementation

7.1 DHCP / DNS / Server Services

DHCP:
A DHCP service is needed so that PCs, smartphones, and tablets receive IP addresses
automatically. Best practice is to place DHCP as close to the clients as possible, typically on
a local server or router at each site.(MSP360)

Two valid approaches:

 Centralized at Distributor:
o Distributor server or router hands out addresses for all subnets via DHCP relay
on remote routers.
 Distributed per site:
o Each site’s server or router runs a dedicated DHCP scope for its own subnet.

For simplicity in Packet Tracer, many students choose per-site DHCP on the router or server.
DNS:
A DNS service (usually on the Distributor server) maps names like [Link] or
[Link] to IP addresses, making it easier for users and apps to reach services. In
real enterprise environments, DNS is a core component tightly integrated with Active
Directory or other directory services.([Link])

Web & Email:

The Distributor server can host:

 A web service (HTTP/HTTPS) to provide a stock management portal or intranet

site.
 An email service (SMTP/POP3) for communication between Distributor and
Retailers.

Retailer servers may offer local file storage or mirror some applications for resilience.

7.2 Wireless Setup (SSID, Security, Access Control)

Each access point is configured with:

 A unique or clearly named SSID (e.g., DISTRIBUTOR_WIFI, RETAILER1_WIFI).

 Security using WPA2-PSK with a strong passphrase.

Wireless best-practice guidelines emphasize:

 Using encryption (WPA2/WPA3),

 Choosing strong keys,
 Placing APs to achieve good coverage and capacity.([Link])

In the simulation:

 The smartphone and tablet at each site are configured with the SSID and passphrase.
 They obtain IP addresses via DHCP and can then ping local and remote devices,
browse web services, and use email.

7.3 VoIP Setup (IP Phones and Call Management)

To enable VoIP:

1. On a chosen router (typically the Distributor), enable telephony-service (in Packet

Tracer: basic CME-like configuration).
2. Define a numbering plan, for example:
o Distributor IP phone: extension 1000
o Retailer 1: 2000
o Retailer 2: 3000
o Retailer 3: 4000
3. Configure each IP phone with:
o The correct voice VLAN or IP network (re-using the main LAN if VLANs
are not implemented).
 o The IP address of its TFTP/telephony server (usually the router hosting
telephony-service).

Once registered, phones can place calls between sites, demonstrating how voice traffic shares
the same infrastructure as data.

7.4 Printing Setup (Network Printer Configuration)

Each network printer is:

 Given a static IP address in the local subnet (e.g., .40 per site).
 Configured on the PC and, optionally, on the server as a network printer.

Printing tests (sending a job from the PC to the printer) confirm that:

 Layer-2 and Layer-3 connectivity inside the site are working.

 The IP addressing plan and default gateway configuration are correct.

7.5 Any Special or Optional Services

Optionally, the design can include:

 Remote management services (SSH/Telnet) on routers and switches for centralized

administration.
 Time synchronization (NTP) so logs and events are time-aligned.
 Backup/replication between servers at Distributor and Retailers to keep critical data
safe.

These extras are not mandatory for the basic distributor–retailer scenario, but they align with
real enterprise practices and can be mentioned as value-adding aspects of the design.(Meter)

8. Security Considerations
Security is a critical aspect of any enterprise network design, even in a small four-site
environment like this Distributor–Retailer topology. The goal is not to build a “military-
grade” network but to apply sensible baseline controls that align with widely recommended
best practices for segmentation, access control and wireless security.(U.S. Department of
War)

8.1 Network Segmentation (Subnets and Potential VLANs)

The first layer of security in this project is segmentation by IP subnet:

 Each site (Distributor and Retailers 1–3) uses a different /24 network.
 WAN links use separate /30 subnets.

This segmentation provides:

  Smaller broadcast domains, improving stability and performance.
 A natural security boundary between sites, so that policies can be applied per subnet
later if needed.

In more advanced deployments, segmentation is typically refined further using VLANs and
security policies. Cisco and other vendors recommend avoiding the default VLAN 1,
assigning all user ports to appropriate VLANs, and shutting down unused switch ports to
reduce the attack surface.(Cisco)

Although this particular Packet Tracer design does not require multiple VLANs, it can easily
be extended to:

 Separate voice, data, and management traffic into different VLANs.

 Use VLANs together with ACLs or more advanced technologies (e.g. TrustSec) for
network segmentation.(Cisco)

8.2 Access Control and Device Hardening

Beyond segmentation, access control mechanisms and device-hardening steps are needed to
protect the routers, switches and services.

Key hardening measures include:

 Configuring strong passwords and, where supported, using encrypted secrets for
privileged access on routers and switches.
 Protecting VTY lines with passwords and preferring SSH over Telnet when possible,
as recommended in infrastructure security guidance from organizations such as NSA
and NIST.(U.S. Department of War)
 Disabling unused switch ports and placing them in an unused VLAN, so that rogue
devices cannot simply be plugged into open jacks.(Cisco)

For traffic-level control, Access Control Lists (ACLs) can be deployed on router interfaces
to:

 Allow only the necessary traffic between sites (e.g. permit HTTP/HTTPS, SMTP,
VoIP signaling, and block unnecessary management protocols from user subnets).
 Restrict access to server IP addresses based on source subnets, as a simple form of
internal firewalling.

Cisco ACL best-practice guidance emphasizes using clearly documented ACLs, applied as
close to the source or destination as practical, and carefully testing policies to avoid breaking
business-critical traffic.([Link])

8.3 Wireless Security

Wireless LANs are an important part of this design (smartphones and tablets at each site), but
they also introduce additional risk. NIST’s WLAN security guidelines recommend:(NIST
Computer Security Resource Center)

 Using WPA2 or WPA3 as the minimum standard for new deployments.

  Using strong passphrases and protecting wireless management frames where
possible.(U.S. Department of War)

In this project, each access point is configured with:

 A unique or clearly identifiable SSID per site.

 WPA2-PSK with a non-trivial passphrase.

In a more advanced or real enterprise deployment, the network could be upgraded to WPA2-
Enterprise / 802.1X with per-user credentials, which industry sources identify as the
recommended model for securing business Wi-Fi.(SecureW2)

8.4 Physical Security

Even though the design is simulated, a real implementation should account for physical
security:

 Routers, switches, and servers placed in locked network rooms or cabinets.

 Printers, phones, and user devices located in supervised areas.
 Clear policies for who is allowed to connect cables, move devices, or access wiring
closets.

Physical controls complement logical security and help prevent direct tampering with
infrastructure devices.

9. Testing & Verification

After designing and configuring the network, a structured testing and verification phase is
essential to prove that requirements are met. Industry guidance on network change and
deployment emphasizes pre-checks, tests during changes, and post-checks to validate
behavior.(IP Fabric)

9.1 Connectivity Tests (Ping, Traceroute and Basic Checks)

The most basic tests are IP connectivity checks:

 From each PC and server, use ping to test reachability of:

o The default gateway (router LAN interface).
o Local devices (server, printer, IP phone).
o Remote devices at other sites (e.g. Distributor PC ↔ Retailer PCs).

Ping is widely recommended as a first step in troubleshooting, as it quickly confirms whether

a destination is reachable and provides basic latency and packet-loss information.(Cisco)

Traceroute is used from selected devices (or routers) to:

 Verify the actual path taken between sites.

  Confirm that traffic is routed via the Distributor in the expected hub-and-spoke
fashion.(Cisco)

If ping or traceroute fail, the results guide troubleshooting of routing tables, ACLs, or IP
addressing errors.

9.2 Service Tests (Web, Email, VoIP, Printing, Wireless)

Once basic connectivity is confirmed, service-level tests are performed:

 Web:
o From PCs and wireless clients, open a browser and access the Distributor’s
web server using its IP or DNS name.
o If pages load correctly from all sites, the HTTP/HTTPS service and related
routing are verified.
 Email:
o Configure email clients on PCs to use the Distributor mail server.
o Send and receive test messages between users at different sites, verifying
SMTP/POP3 reachability and functionality.
 VoIP:
o Place calls between IP phones at Distributor and each Retailer using their
configured extensions.
o Verify that phones ring and that two-way audio is established across the IP
network.
 Printing:
o From each PC, send test print jobs to the local network printer.
o Successful jobs indicate that local IP connectivity and printer configuration are
correct.
 Wireless:
o Connect smartphones and tablets to each site’s SSID, ensuring they receive
DHCP addresses in the correct subnet.
o Repeat ping and web/email tests from wireless clients to confirm that Wi-Fi
integration with the LAN is functioning as designed.

These tests collectively validate that the functional requirements (LAN, WAN, Wi-Fi,
VoIP, printing, servers) are properly implemented.

9.3 Failure and Redundancy Tests

Although the project does not implement advanced redundancy, it is still useful to simulate
failure scenarios:

 Link Failure Tests:

o Disconnect a WAN link in Packet Tracer and observe that communication
between the Distributor and the affected Retailer stops, while other branches
remain unaffected.
 Device Failure Tests:
o Power off a router or switch in the simulation and verify that hosts behind that
device lose connectivity.
These tests demonstrate the current limitations (e.g., no alternate paths or backup links), and
highlight where future redundancy mechanisms such as backup routers, dual links, or
dynamic VPN meshes could be introduced.(Cisco)

10. Results & Observations

The completed network design delivers the following results:

 End-to-end IP connectivity between all four sites: pings and traceroutes show that
traffic flows as intended through the Distributor hub.
 All core services—web, email, DHCP, DNS (if configured), wireless access, VoIP,
and printing—operate correctly in the simulation.
 The hub-and-spoke topology provides a clear operational model: all inter-branch
communication goes through the Distributor, which matches the business role of the
Distributor as the central management and stock control point.(Microsoft Learn)

Observations:

 The structured IP addressing and per-site subnetting greatly simplify troubleshooting

and documentation.
 Static routing is sufficient and easy to understand at this scale, but would become
more complex if the number of branches grew significantly.
 The absence of Internet connectivity and advanced security controls (firewalls,
IDS/IPS, VPN encryption) is acceptable for a lab project, but would need to be
addressed in any real deployment.

No significant performance issues appear in the simulated environment, though Packet Tracer
does not model detailed throughput or queuing; it primarily validates functional correctness.

11. Scalability and Future Enhancements

A key design objective was to build a network that can scale beyond the initial Distributor +
three Retailer topology and evolve to more advanced features if needed.

11.1 Adding More Retailer Sites

Because each Retailer site follows the same template (router + switch + devices + one /24
subnet), adding a new branch involves:

 Assigning a new subnet (e.g., [Link]/24).

 Adding a new WAN link from the Distributor router (with its own /30).
 Configuring static routes at the Distributor and a default route at the new retail router.

This is directly aligned with common hub-and-spoke design guides where spokes can be
added with minimal impact to the existing network.(Microsoft Learn)
11.2 Dynamic Routing and VPN Enhancements

As the number of branches grows, managing many static routes becomes error-prone. At that
point, the network can be upgraded to use:

 A dynamic routing protocol such as OSPF or EIGRP across all routers.

 In a real WAN, secure inter-site connectivity using IPsec VPNs in a hub-and-spoke or
DMVPN design, which vendors like Cisco recommend for scalable secure branch
connectivity.(Cisco)

These enhancements would preserve the logical topology while improving manageability and
security across many sites.

11.3 VLANs, ACLs and Advanced Segmentation

To improve security and performance, the design can incorporate:

 VLANs at each site to separate voice, data, and management traffic.

 ACLs on router interfaces or VLAN interfaces to control which segments can talk to
which services.

Recent studies and practical guides show that combining VLAN-based segmentation with
ACLs can reduce broadcast traffic and improve security in campus and branch networks, and
Packet Tracer is commonly used to simulate such designs before deployment.(ResearchGate)

11.4 Internet Access, Firewalls and Redundancy

In a more realistic enterprise deployment, additional enhancements would include:

 Internet connectivity at the Distributor site, with NAT for internal hosts.
 A dedicated firewall or next-generation security appliance at the hub, enforcing
policies between the internal network, partner networks and the Internet.(Cisco)
 Redundant links and possibly HSRP/VRRP or similar first-hop redundancy
protocols to increase availability for critical sites.(ResearchGate)

These features are not required for the current academic project but form a natural roadmap
for future work.

12. Conclusion
This project has designed and simulated a Distributor–Retailer management network
using Cisco Packet Tracer, connecting one central Distributor site with three Retailers over a
hub-and-spoke topology. The network provides fully functional LAN and WAN
connectivity, wireless access, VoIP, printing, and server-based services, satisfying the
functional and non-functional requirements defined at the outset.
The design follows sound principles widely recommended in enterprise networking literature:
clear segmentation, structured IP addressing, centralized hub routing, and modular branch
templates.(Cisco) Baseline security measures—such as subnet separation, basic device
hardening, encrypted wireless, and the potential for VLANs and ACLs—further align the
project with modern best practices.

Testing and verification show that hosts at all sites can communicate and use shared services,
and that the network behaves predictably under both normal and simple failure conditions.
While the current topology omits advanced features like VPN encryption, enterprise
firewalls, dynamic routing and full redundancy, the structure is explicitly designed so these
capabilities can be added later without redesigning the entire network.

Overall, the project successfully meets its goal: to provide a clean, scalable and
educationally valuable example of how a small enterprise network can be built to support
distributor–retailer operations, and to form a foundation for more advanced study of
enterprise networking, security, and WAN design.

14. References
1. Aditya Swaroop, “Computer-Networks-Distributer-Retailer-management”,
GitHub repository (source of base Packet Tracer project).([Link])
2. Cisco, “VLAN Best Practices and Security Tips for Cisco Business
Routers.”(Cisco)
3. Cisco, “Understand the Ping and Traceroute Commands.”(Cisco)
4. NIST, “Guidelines for Securing Wireless Local Area Networks (WLANs), NIST
SP 800-153.”(NIST Computer Security Resource Center)
5. Cisco, “Basic Small Branch Network – System Assurance Guide.”(Cisco)
6. Cisco, “Dynamic Multipoint VPN (DMVPN) – Simple and Secure Branch
Connectivity.”(Cisco)
7. NSA, “Network Infrastructure Security Guide.”(U.S. Department of War)
8. Research article, “Implementation of VLAN and ACL for Network Security”
(Packet Tracer case study).(ResearchGate)