120 likes | 228 Views
Lab #4 for CS492 introduces students to ad-hoc networks and the AODV routing protocol. Students will configure their laptops in ad-hoc mode, set up an ad-hoc network, and test communication using the 'ping' command. The lab involves steps to install the necessary Linux kernel and drivers, edit network configurations, and implement MAC filtering. Students will also conduct tests to ensure proper functionality of the AODV protocol and exchange files between nodes. Key concepts include understanding ad-hoc networks and evaluating network performance under varying conditions.
E N D
2005 Spring CS492 Lab #4 2005.11.1. Tuesday 10:30am-Noon Building E3-1, Classroom #3 Dept of EECS, Div. of CS
Goals and Overview of Lab #4 • Goals • To introduce students to ad-hoc network and AODV routing protocol • Overview • Set up an ad-hoc network - bring up your laptop in an ad-hoc mode • Communicate other laptops with AODV routing protocol • Test ‘ping command’ • Exchange files with other nodes • Preparation for Lab #4 • Install Linux kernel v2.4.20-8 • Install a wireless LAN driver • Install an AODV driver
Lab #4: Step 1 • Configure your laptop in an ad-hoc mode • As an ad-hoc server #./RT2500-Linux-STA-1.4.6.2/Utility/Raconfig2500
Lab #4: Step 2 • Set up an ad-hoc network x x
Lab #4: Step 3 • Configure your laptop in an ad-hoc mode • As an ad-hoc client #./RT2500-Linux-STA-1.4.6.2/Utility/Raconfig2500 v
Lab #4: Step 4 • IP configuration 1) #setup • Edit Network Configuration IP: 192.168.11.1~4 (Group A) 192.168.100.5~9 (Group B) Netmask:255.255.255.0 Default Gateway(IP): 192.168.11.254 Primary Nameserver: 192.168.11.1 2) #vi /etc/sysconfig/network-scripts/ifcfg-eth0 (check network configuration) 3) #cp ifcfg-eth0 ./ifcfg-ra0 4) #vi ifcfg-ra0 DEVICE=ra0 (<-edit) 5) #setup - Edit Network Configuration DHCP 설정으로 바꾸고 저장 6) #vi /etc/sysconfig/network-scripts/ifcfg-eth0 (check DHCP) 7) #/etc/init.d/network restart
Lab #4: Step 5 • MAC filtering • Block getting frames which have a source MAC address xx:xx:xx:xx:xx:xx. • That is, a node can’ t communicate directly another node with a source MAC address xx:xx:xx:xx:xx:xx, but can through other nodes using AODV 1) #iptables -A INPUT -m mac --mac-source xx:xx:xx:xx:xx:xx -j DROP
Lab #4 Scenario 1 • test ‘ping command’- We use ‘ping command’ to test the AODV routing protocol in the 802.11 ad hoc network.
Lab #4: Scenario 1 • Test ‘ping’ with AODV #ifconfig - check wireless lan, ip configuration, ra0 #~/Utility/Raconfig2500 - check same channel and ssid in each group #iptables –L - check blocking mac address #ping 192.168.xxx.xxx - check whether ping is working or not #aodvd –d –l –r 3 - run AODV daemon #ps –aux - check whether AODV is working #ping 192.168.xxx.xxx - check again whether ping is working or not
Lab #4 Scenario 2 • Transfer Files - Nodes exchange files with other nodes using AODV routing protocol.
Lab #4: Scenario 2 • Exchange files using AODV routing protocol (sample_file in /var/ftp/pub) #ps –aux - check whether vsftpd is working or not (if vsftpd isn’t working, #/etc/init.d/vsftpd restart) #ftp 192.168.11.4 or 192.168.100.9 ftp username>anonymous password> get sample_file
Lab #4: Wrap Up • Questions to ask yourself • What is an ad-hoc network? • How does the AODV routing protocol work? • Beyond what number of hops did the throughput drop below a reasonable rate?