N. G.
PATEL POLYTECHNIC
Semester-5
Advanced Machine Learning
MICRO PROJECT ON Configure Proxy
Server In Intranet.
1. Introduction:
This report outlines the process of configuring a proxy server
within an intranet environment using Cisco Packet Tracer. While
Packet Tracer does not offer a dedicated "proxy server" device,
this configuration can be simulated using a server configured
with HTTP services and access control lists (ACLs) on a router to
control traffic flow, effectively mimicking proxy server
functionality.
2. Network Topology Design:
Devices:
One Router (e.g., 2911)
One Server (acting as the "proxy server")
Multiple End Devices (PCs)
One Switch (e.g., 2960)
Connections:
Connect PCs to the Switch.
Connect the Switch to the Router.
Connect the Server to the Router.
3. IP Addressing Scheme:
Assign IP addresses to all devices within a private IP range (e.g.,
[Link]/24 for the intranet, and a separate subnet for the
"proxy server" and its connection to the router).
Configure default gateways on PCs and the "proxy server" to
point to the Router's interface IP.
4. "Proxy Server" Configuration:
Server Services: On the Server device, navigate to the
"Services" tab and enable "HTTP."
Web Page Content: Edit the [Link] file within the HTTP
service to simulate a blocked or redirected page, or a page
indicating proxy usage.
5. Router Configuration (ACLs for Proxy Functionality):
Access Control List (ACL) Creation.
Router(config)# access-list 101 deny tcp [Link] [Link]
Router(config)# access-list 101 permit ip any any
This ACL denies direct HTTP access (port 80) from the intranet
([Link]/24) to any destination.
Applying ACL to Interface:
Router(config-if)# ip access-group 101 in
Apply the ACL to the router interface connecting to the
intranet, ensuring traffic from the PCs is filtered.
Static Route (Optional): If the "proxy server" is in a different
subnet, configure a static route on the router to direct traffic
towards it.
6. Client (PC) Configuration:
Manual Proxy Settings (Simulation): In a real-world scenario,
clients would be configured to use the proxy server. In Packet
Tracer, this is a conceptual step as the ACL on the router
enforces the "proxy" behavior. You would conceptually
configure the browser's proxy settings on each PC to point to
the "proxy server's" IP address and port (e.g., 80 for HTTP).
7. Verification:
Test Connectivity: Ping the "proxy server" from a PC to ensure
basic network connectivity.
Test Web Access: Attempt to access an external website
(simulated by a different server or the "proxy server" itself)
from a PC.
With the ACL in place, direct HTTP access to external sites should be
blocked, mimicking the proxy's filtering role.
If a client were truly configured to use the proxy, requests would be
routed through the "proxy server" first.
Steps To Implement Configure Proxy Server In Intranet:
Step 1:
Step 2:
Step 3:
Step 4:
Step 5:
Step 6:
Step 7: IP Address
Step 8:
Step 9:
Step 10:
Step 11: Verification of the process is working or not
Step 12:
Step 13:
Step 14:
8. Conclusion:
While Cisco Packet Tracer does not natively support a dedicated proxy server
device, its functionality can be effectively simulated using a server with HTTP
services and strategic application of Access Control Lists (ACLs) on a router. This
setup demonstrates how network traffic can be controlled and redirected,
providing a foundational understanding of proxy server concepts within an
intranet environment.
