4.6.5 Packet Tracer- Connect A Wired And Wireless Lan

Packet Tracer 4.6.5: Connect a Wired and Wireless LAN

Building a functional network that seamlessly integrates both traditional Ethernet connections and modern Wi-Fi access is a foundational skill for any aspiring network professional. In Cisco’s Packet Tracer 4.6.5, this hands-on exercise moves beyond theory, allowing you to construct, configure, and troubleshoot a small business or home office network where wired desktops and wireless laptops coexist under a single logical umbrella. This guide will walk you through the complete process, from physical topology design to final verification, ensuring you understand not just the how but the critical why behind each configuration step. Mastering this integration is essential because, in the real world, networks are almost never purely one type; they are hybrid ecosystems requiring careful planning of IP addressing, security policies, and gateway services.

Prerequisites and Conceptual Foundation

Before dragging a single device into the Packet Tracer workspace, a clear plan is non-negotiable. A hybrid LAN design requires you to answer three core questions: What is our IP addressing scheme? Which device will be the central gateway and DHCP server? How will we secure the wireless segment? For this exercise, we will use a common small office topology. A single Cisco 1841 router will serve as the default gateway and DHCP server. A Cisco 2960 switch will act as the central hub for all wired devices. For wireless, we will deploy a Linksys WRT300N router, configured not as a primary router but as an access point (AP), which is the correct architectural role for extending a wired LAN with Wi-Fi.

Your IP scheme should be simple yet scalable. We’ll use the private network 192.168.1.0/24. The router’s GigabitEthernet0/0 interface will have the static IP 192.168.1.1 and will provide DHCP addresses in the range 192.168.1.100 - 192.168.1.150. The switch will operate at Layer 2, requiring no IP configuration itself, but we will assign a management IP later for remote access. The wireless AP will need a static IP in the same subnet (e.g., 192.168.1.2) to be manageable. All devices—wired PCs and wireless clients—will obtain their IP settings automatically via DHCP from the router. This single DHCP server model prevents IP conflicts and simplifies management.

Step-by-Step Implementation: Building the Wired Backbone

The physical and logical wired infrastructure forms the reliable spine of your network. Start by placing the devices in the logical workspace. Drag a Cisco 1841 router, a Cisco 2960 switch, and two Generic PCs (representing wired workstations). Connect them using the correct cabling: use Copper Straight-Through cables to connect the router’s GigabitEthernet0/0 port to any switch port (e.g., Fa0/1), and connect each PC’s Ethernet port to separate switch ports (e.g., Fa0/2 and Fa0/3). The lights on the switch ports and PC NICs should turn green, indicating a physical layer connection.

Now, configure the router as the network’s brain. Click the router, go to the CLI tab, and enter the following commands in configuration mode:

enable
configure terminal
interface gigabitethernet 0/0
ip address 192.168.1.1 255.255.255.0
no shutdown
exit
ip dhcp pool OFFICE-POOL
network 192.168.1.0 255.255.255.0
default-router 192.168.1.1
dns-server 8.8.8.8
exit
line vty 0 4
password cisco
login
exit
enable password cisco
hostname OFFICE-ROUTER

Key points here: The no shutdown command activates the interface. The DHCP pool definition tells the router to lease IPs, set the default gateway to itself (192.168.1.1), and provide a public DNS server. The VTY line password secures remote Telnet access. Finally, verify your PC configurations. On each PC, go to the Desktop tab, click IP Configuration, and ensure it is set to DHCP. You should see them automatically receive an IP like 192.168.1.101. Test connectivity by having PC1 ping 192.168.1.1 (the router) and ping 192.168.1.102 (PC2). Successful pings confirm your wired backbone is operational.

Integrating the Wireless Access Point

The critical step in creating a unified LAN is configuring the wireless router to function purely as an Access Point, not as a separate router with its own NAT and DHCP. This prevents a "double NAT" scenario that would isolate wireless clients from the wired network. Place a Linksys WRT300N in the workspace. Physically, connect one of its LAN ports (not the Internet port) to an available port on your Cisco 2960 switch using another Copper Straight-Through cable.

Now, access the WRT300N’s configuration. By default, it has its own IP (often 192.168.1.1), which conflicts with your router. You must change it. Click the WRT300N, go to the CLI (or use the simulated web browser in Packet Tracer, but CLI is often more reliable in PT 4.6.5 for this model). First, assign it a static IP in your network:

enable
configure terminal
interface vlan 1
ip address 192.168.1.2 255.255.255.0
no shutdown
exit
ip default-gateway 192.168.1.1
hostname OFFICE-AP

The `

...
The end command exits configuration mode. Save the configuration with copy running-config startup-config to persist settings.

Verifying Wireless Connectivity

Connect a wireless PC (e.g., PC3) to the Office-AP SSID. In Packet Tracer, simulate this by selecting the PC, navigating to the Desktop tab, and configuring its wireless adapter to connect to the AP. Ensure the PC’s IP configuration is set to DHCP. The device should automatically request an IP from the router’s pool (`

192.168.1.0/24). Verify successful connectivity by pinging both the Access Point’s IP address (192.168.1.2) and the wired PC (192.168.1.102`). If both pings are successful, the wireless AP is properly integrated into your LAN.

Addressing Potential Issues

During this setup, several issues can arise. Double-check cable connections to ensure they are secure. Incorrect IP addressing on any device will prevent communication. If wireless clients fail to obtain an IP address, verify that the DHCP server on the Cisco router is enabled and that the IP address range is not exhausted. Also, confirm the wireless AP's SSID is broadcasting and that no MAC address filtering is enabled that might be blocking your wireless PC. Finally, if you experience intermittent connectivity, consider checking for wireless interference from other devices.

Conclusion

By following these steps, you have successfully established a unified wired and wireless LAN using a Cisco 2960 switch, a Cisco router, and a Linksys WRT300N wireless access point. This configuration demonstrates a common network architecture, allowing devices to communicate seamlessly regardless of whether they are connected via Ethernet cable or wirelessly. This setup provides a scalable and manageable network foundation for an office environment, offering both wired and wireless connectivity for employees and guests. The key to success lies in careful IP addressing, proper device configuration, and thorough testing to ensure reliable network operation. This basic setup can be further enhanced by implementing security measures like firewalls and VLANs to protect your network from unauthorized access and improve overall network performance. Remember to regularly review and update your network configuration to maintain a secure and efficient environment.

To expand on the foundationyou have just built, consider segmenting the LAN with VLANs to isolate broadcast domains and improve security. For example, create a VLAN 10 for staff workstations, VLAN 20 for VoIP phones, and VLAN 30 for guest wireless clients. Configure the 2960 switch with the appropriate trunk ports toward the router and the WRT300N, then enable inter‑VLAN routing on the Cisco router using sub‑interfaces or a Layer 3 switch if you upgrade. Assign each VLAN its own DHCP pool so that devices receive predictable address ranges, and apply ACLs to control which VLANs can communicate with one another.

Quality of Service (QoS) is another valuable enhancement, especially when VoIP or video conferencing will share the same infrastructure. Prioritize voice traffic by marking packets with DSCP values and configuring policy maps on the router or switch to ensure low latency and jitter for SIP/RTP streams. Similarly, you can implement bandwidth‑shaping policies to prevent a single wireless user from monopolizing the uplink.

Monitoring and documentation round out a robust deployment. Enable SNMP on the router and switch, configure a simple network‑management station, and schedule regular backups of the running configuration (copy running-config startup-config). In Packet Tracer you can use the “Simulation” mode to view packet flows, which helps pinpoint intermittent connectivity issues before they affect real users. Log events such as link failures or DHCP lease renewals to a syslog server for trend analysis.

If the network grows beyond a single AP, migrate to a centralized wireless controller or adopt a mesh‑based solution that can automatically balance clients across multiple radios. This approach reduces the chance of co‑channel interference and simplifies SSID management. Additionally, consider integrating a dedicated firewall appliance or using the router’s built‑in firewall features to enforce perimeter security, block unwanted inbound traffic, and provide VPN access for remote employees.

Finally, document every change—VLAN IDs, IP subnets, ACLs, and wireless parameters—so that future troubleshooting or audits are straightforward. Store the documentation in a version‑controlled repository and schedule periodic reviews to align the network design with evolving business needs.

Conclusion

By systematically extending the initial wired‑and‑wireless LAN with VLAN segmentation, QoS prioritization, proactive monitoring, and scalable wireless management, you transform a basic connectivity lab into a production‑ready network architecture. Each layer—from physical cabling to application‑level policies—works in concert to deliver reliable, secure, and manageable communication for both wired and wireless users. This iterative, well‑documented approach not only resolves the immediate requirements of the office environment but also establishes a flexible platform that can adapt to future growth, technological upgrades, and heightened security demands.