original presentation

725 views
667 views

Published on

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
725
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
8
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

original presentation

  1. 1. Wireless Networking at the Beckman Institute Christine Gressley Nancy Mansfield BI Systems Services March 28, 2002
  2. 2. Outline <ul><li>Status of Campus Wireless Network </li></ul><ul><li>UIUCnet Wireless or Beckman Wireless </li></ul><ul><li>Beckman Wireless Implementation </li></ul><ul><li>Wireless Limitations </li></ul><ul><li>Wireless Network Policies </li></ul><ul><li>Wireless Network Security </li></ul><ul><li>Accessing Beckman Wireless Network </li></ul><ul><li>Future Plans for Beckman Wireless </li></ul><ul><li>Questions and Comments </li></ul>
  3. 3. Status of Campus Wireless Network Beta Test <ul><li>“ UIUCnet Wireless” is in Beta Testing </li></ul><ul><li>Available in CCSO Areas Only </li></ul><ul><ul><li>Digital Computer Lab (DCL) </li></ul></ul><ul><ul><li>Fox Drive </li></ul></ul><ul><ul><li>Presidential Towers </li></ul></ul><ul><li>17 Buildings on Waiting List </li></ul><ul><li>3 Buildings in Site Survey Phase </li></ul><ul><li>Development Information at: </li></ul><ul><ul><li>http://www-commeng.cso.uiuc.edu/docs/wireless </li></ul></ul>
  4. 4. Status of Campus Wireless Network VPN Solution <ul><li>Virtual Private Network (VPN) </li></ul><ul><ul><li>Encrypts Data and Passwords </li></ul></ul><ul><ul><li>http://www.cso.uiuc.edu/network/vpn </li></ul></ul><ul><li>Requires VPN Client Software </li></ul><ul><ul><li>Windows, Macintosh, Linux, Solaris </li></ul></ul><ul><ul><ul><li>Only Cisco VPN client supported by CCSO </li></ul></ul></ul><ul><ul><ul><li>Free </li></ul></ul></ul><ul><ul><li>PalmOS and Windows CE </li></ul></ul><ul><ul><ul><li>Movian VPN client </li></ul></ul></ul><ul><ul><ul><li>Not supported by CCSO </li></ul></ul></ul><ul><ul><ul><li>$29.95 </li></ul></ul></ul>
  5. 5. UIUCnet or Beckman Wireless? Implementation Questions <ul><li>BISS and BI Sys Admins met with Debbie Fligor of CCSO in October </li></ul><ul><li>Discussed campus wireless network implementation and issues </li></ul><ul><li>Should Beckman participate in CCSO wireless network beta test? </li></ul><ul><li>Should Beckman deploy independent department wireless? </li></ul><ul><li>Should Beckman do both? </li></ul>
  6. 6. UIUCnet or Beckman Wireless? Public Use vs Research Use <ul><li>CCSO </li></ul><ul><ul><li>Focus is on general user access </li></ul></ul><ul><ul><li>Any conflict between wireless devices will be resolved in favor of general access for public users </li></ul></ul><ul><li>Beckman </li></ul><ul><ul><li>Focus is on research </li></ul></ul><ul><ul><li>Any conflict between wireless devices will be resolved in order to accommodate research needs first </li></ul></ul>
  7. 7. UIUCnet or Beckman Wireless? AppleTalk <ul><li>CCSO </li></ul><ul><ul><li>Only supports TCP/IP </li></ul></ul><ul><ul><li>No AppleTalk </li></ul></ul><ul><ul><li>No Microsoft browsing and file sharing? </li></ul></ul><ul><li>Beckman </li></ul><ul><ul><li>AppleTalk needed for access to BI Public Printers </li></ul></ul><ul><ul><li>AppleTalk will not be routed to campus </li></ul></ul><ul><ul><li>Only access BI AppleTalk computers </li></ul></ul>
  8. 8. UIUCnet or Beckman Wireless? Static vs Dynamic IP <ul><li>CCSO </li></ul><ul><ul><li>DHCP only </li></ul></ul><ul><ul><li>IP addresses assigned dynamically </li></ul></ul><ul><ul><li>No reserved static IP addresses available </li></ul></ul><ul><li>Beckman </li></ul><ul><ul><li>IP addresses assigned dynamically, but… </li></ul></ul><ul><ul><li>Static IP addresses may be requested for research purposes only, e.g. robots </li></ul></ul>
  9. 9. UIUCnet or Beckman Wireless? Security <ul><li>CCSO </li></ul><ul><ul><li>VPN solution </li></ul></ul><ul><ul><li>Authorization and authentication using NetID login and password </li></ul></ul><ul><ul><li>Encrypts all data over air waves </li></ul></ul><ul><ul><li>Extremely secure </li></ul></ul><ul><ul><li>VPN client issues </li></ul></ul><ul><li>Beckman </li></ul><ul><ul><li>Access limited to BI affiliates and guests </li></ul></ul><ul><ul><li>Client MAC address authorization </li></ul></ul><ul><ul><li>No authentication </li></ul></ul><ul><ul><li>Limited security </li></ul></ul>
  10. 10. UIUCnet or Beckman Wireless? Consequences <ul><li>By not using UIUCnet Wireless </li></ul><ul><ul><li>Must ensure security </li></ul></ul><ul><ul><ul><li>Protect Network ID logins and passwords </li></ul></ul></ul><ul><ul><ul><li>Restrict access to legitimate users </li></ul></ul></ul><ul><ul><li>Document wireless network for CCSO </li></ul></ul><ul><ul><li>Users unable to roam to UIUCnet Wireless from Beckman </li></ul></ul><ul><ul><li>Must not interfere with UIUCnet Wireless </li></ul></ul>
  11. 11. Beckman Wireless Implementation Goals <ul><li>Provide a wireless infrastructure that allows research to use technology in ways that minimize the possible impact on others </li></ul><ul><li>To limit the potential security risks that are associated with wireless network technology </li></ul><ul><li>To educate researchers about some of the impacts of wireless network technology </li></ul><ul><li>Reliability is a concern due to possible radio interference from other wireless devices </li></ul>
  12. 12. Beckman Wireless Implementation Equipment <ul><li>Cisco Aironet 352 access points </li></ul><ul><li>IEEE 802.11b Wi-Fi </li></ul><ul><ul><li>2.4 GHz shared bandwidth </li></ul></ul><ul><ul><li>14 channels </li></ul></ul><ul><ul><li>3 non-overlapping </li></ul></ul><ul><ul><li>11 Mbps </li></ul></ul><ul><ul><li>Direct Sequence Spread Spectrum (DSSS) </li></ul></ul><ul><ul><li>128-bit WEP encryption </li></ul></ul><ul><ul><li>Range up to 300ft </li></ul></ul><ul><ul><li>Dynamic Rate shifting (11, 5.5, 2, 1 Mbps) </li></ul></ul>
  13. 13. Beckman Wireless Implementation Project Status <ul><li>Deploy access points </li></ul><ul><ul><li>Initial site survey and mapping – Done </li></ul></ul><ul><ul><li>Install access points in public areas – Done </li></ul></ul><ul><ul><li>Install access points in non-public areas – By Priority </li></ul></ul><ul><ul><li>Final site survey and mapping </li></ul></ul><ul><li>Develop wireless database – Done </li></ul><ul><li>Create redundant DHCP service – Done </li></ul><ul><li>Automatic registration application – In Progress </li></ul><ul><li>Publish wireless network policy – In Progress </li></ul><ul><li>Write user documentation – In Progress </li></ul><ul><li>Train BISS Help Desk staff </li></ul>
  14. 14. Beckman Wireless Implementation Project Updates <ul><li>Sign-up sheet available for users who wish to beta-test wireless </li></ul><ul><li>Beta testers will need to demonstrate an understanding of how to secure their wireless network communications </li></ul><ul><li>Will e-mail beta-testers when the on-line registration web form completed </li></ul><ul><li>Check web page for status updates </li></ul><ul><ul><li>http://biss.beckman.uiuc.edu/network/wireless </li></ul></ul>
  15. 15. Beckman Wireless Implementation Public Space Completed <ul><ul><li>Atrium and Bridges </li></ul></ul><ul><ul><li>Café and Garden </li></ul></ul><ul><ul><li>Auditorium </li></ul></ul><ul><ul><li>Tower Rooms </li></ul></ul><ul><ul><ul><li>2269, 3269, 4269, 5269 </li></ul></ul></ul><ul><ul><li>Public Conference Rooms </li></ul></ul><ul><ul><ul><li>1003, 1005, 1237, 1227, 5602 </li></ul></ul></ul><ul><ul><li>Side Conference Rooms </li></ul></ul><ul><ul><ul><li>1309, 2169*, 2369, 3169, 3369 </li></ul></ul></ul><ul><ul><li>Beckman Library </li></ul></ul>
  16. 16. Beckman Wireless Implementation Office and Lab Space Completed <ul><li>1300 block </li></ul><ul><li>1700 block </li></ul><ul><li>2000 block </li></ul><ul><li>2200 block* </li></ul><ul><li>2300 block </li></ul><ul><li>2400 block* </li></ul><ul><li>*Signal leakage </li></ul><ul><li>3000 block </li></ul><ul><li>3100 block </li></ul><ul><li>3200 block </li></ul><ul><li>3300 block </li></ul><ul><li>3400 block* </li></ul><ul><li>4200 block* </li></ul><ul><li>4300 block </li></ul>
  17. 17. Beckman Wireless Implementation Office and Lab Space Incomplete <ul><li>1400 block </li></ul><ul><li>1500 block </li></ul><ul><li>1600 block </li></ul><ul><li>2300 block </li></ul><ul><li>2400 block </li></ul><ul><li>2500 block </li></ul><ul><li>2600 block </li></ul><ul><li>2700 block </li></ul><ul><li>3400 block </li></ul><ul><li>3500 block </li></ul><ul><li>3600 block </li></ul><ul><li>3700 block </li></ul><ul><li>4600 block </li></ul><ul><li>B400 block </li></ul><ul><li>B500 block </li></ul><ul><li>B600 block </li></ul>
  18. 18. Beckman Wireless Implementation Site Survey <ul><li>Test signal strength and noise information </li></ul><ul><li>Identify placement of access points </li></ul><ul><li>Determine user density </li></ul><ul><li>Frequency channel selection </li></ul><ul><li>Identify possible causes of interference </li></ul><ul><li>Deploy access points </li></ul><ul><li>Retest signals after deployment </li></ul>
  19. 19. Beckman Wireless Implementation WEP Key Encryption <ul><li>WEP keys can be quickly hacked with commonly available free tools </li></ul><ul><ul><li>AirSnort http://airsnort.shmoo.com </li></ul></ul><ul><ul><li>WEPCrack http://sourceforge.net/projects/wepcrack </li></ul></ul><ul><li>Inherently weak scheme when used with large user populations </li></ul>
  20. 20. Beckman Wireless Implementation Access Control <ul><li>The registration of the media access (MAC) address or hardware address of the wireless network card is required </li></ul><ul><li>The DHCP server will only assign dynamic IP addresses to registered MAC addresses </li></ul><ul><li>The access points use MAC address filtering capabilities to only allow registered addresses to associate to the access points </li></ul><ul><li>Software will search for and block illegal MAC address and IP address usage </li></ul><ul><li>Only Beckman affiliates permitted to register </li></ul><ul><li>Guest access registration will be accommodated </li></ul>
  21. 21. Beckman Wireless Implementation Network Information <ul><li>Created a Beckman Wireless VLAN </li></ul><ul><li>Users will not have IP addresses on their research group VLANs </li></ul><ul><li>DHCP Range </li></ul><ul><ul><li>128.174.209.1 – 128.174.209.254 </li></ul></ul><ul><li>Static Addresses </li></ul><ul><ul><li>128.174.208.64 – 128.174.208.254 </li></ul></ul><ul><li>Router / Subnet Mask </li></ul><ul><ul><li>128.174.208.1 / 255.255.255.254 </li></ul></ul>
  22. 22. Beckman Wireless Implementation Roaming <ul><li>Ability to move from one coverage area to another without connectivity loss </li></ul><ul><li>Wireless card may “see” two or more access points </li></ul><ul><li>Wireless card will always connect to the access point with a stronger signal </li></ul><ul><li>As soon as another access point has a stronger signal, your wireless card will switch but continue uninterrupted service </li></ul><ul><li>If you leave the coverage area, any open network connections will be broken </li></ul>
  23. 23. Beckman Wireless Implementation Frequencies <ul><li>Only three non-overlapping frequencies available: channels 1, 6, 11 </li></ul><ul><li>To cover a large area, the channels must be carefully coordinated </li></ul><ul><li>Overlapping access points using same channel creates interference </li></ul><ul><li>Available bandwidth is cut in half </li></ul>
  24. 24. Beckman Wireless Implementation Health and Safety <ul><li>Extensive research on safety to exposure to radio frequencies </li></ul><ul><li>Output of wireless LAN systems is very low, much less than cell phone </li></ul><ul><li>White Paper on Cisco RF Safety </li></ul><ul><li>http://www.cisco.com/warp/public/cc/pd/witc/ao340ap/prodlit/rfhr_wi.htm </li></ul><ul><li>Wireless LANs Health Risk </li></ul><ul><li>http://www.wlana.com/learn/health.htm </li></ul>
  25. 25. Wireless Limitations Overview <ul><li>Range </li></ul><ul><li>Interference </li></ul><ul><li>Shared bandwidth </li></ul><ul><li>Roaming limited to one subnet </li></ul><ul><li>Lower data rates than wired </li></ul><ul><li>Security </li></ul>
  26. 26. Wireless Limitations Range <ul><li>Range of coverage varies </li></ul><ul><ul><li>Location </li></ul></ul><ul><ul><li>Building material </li></ul></ul><ul><ul><li>Surrounding surfaces </li></ul></ul><ul><li>Signal leakage </li></ul><ul><ul><li>Signals bounce </li></ul></ul><ul><ul><li>Coverage may extend to unexpected areas </li></ul></ul>
  27. 27. Wireless Limitations Interference <ul><li>Frequency collisions </li></ul><ul><ul><li>Bluetooth wireless devices </li></ul></ul><ul><ul><li>2.4 GHz cordless telephones </li></ul></ul><ul><ul><li>Microwave ovens </li></ul></ul><ul><ul><li>High voltage audio speakers </li></ul></ul><ul><ul><li>Wireless mice and keyboards </li></ul></ul><ul><ul><li>Research equipment </li></ul></ul><ul><ul><li>Surveillance cameras </li></ul></ul><ul><li>Electromagnetic interference (EMI) </li></ul><ul><ul><li>Electronic motors, moving metal parts </li></ul></ul><ul><li>Debugging interference sources is difficult </li></ul>
  28. 28. Wireless Limitations Interference <ul><li>Channel collisions </li></ul><ul><ul><li>Access points in same coverage area </li></ul></ul><ul><ul><li>Using overlapping channel </li></ul></ul><ul><ul><li>Degrades available bandwidth </li></ul></ul><ul><li>Dueling access points </li></ul><ul><ul><li>Misconfigured access points </li></ul></ul><ul><ul><li>Clients associate to wrong access point </li></ul></ul><ul><ul><li>Creates wireless connectivity problems </li></ul></ul>
  29. 29. Wireless Limitations Shared Bandwidth <ul><li>All users associated with same access point share 11Mbps bandwidth </li></ul><ul><li>The more active users, the slower the network gets </li></ul><ul><li>One person can monopolize the bandwidth of an access point and kill performance for others </li></ul>
  30. 30. Wireless Limitations Lower Data Rates Than Wired <ul><li>Theoretical maximum of 11Mbps </li></ul><ul><li>In practice, closer to 5 Mbps </li></ul><ul><li>Considerable overhead in wireless protocol </li></ul><ul><li>Distance between access point and wireless client card </li></ul>
  31. 31. Wireless Limitations Security <ul><li>Inherently insecure </li></ul><ul><li>WEP encryption weak </li></ul><ul><li>Public tools to break WEP </li></ul><ul><li>Public tools to snoop wireless </li></ul><ul><li>No security! </li></ul><ul><li>No security! </li></ul><ul><li>No security! </li></ul>
  32. 32. Wireless Policies University Policy Documents <ul><li>UIUCnet Appropriate Use of Computers and Networks Policy </li></ul><ul><li>http://www.admin.uiuc.edu/cam/CAM/viii/viii-1.1.html </li></ul><ul><li>Campus Policies and Procedures Manuals </li></ul><ul><li>http://www.uiuc.edu/admin_manuals.html </li></ul><ul><li>Campus Wireless Guidelines (Draft) </li></ul><ul><li>http://www-commeng.cso.uiuc.edu/docs/wireless/DRAFT-Wireless-guidelines.html </li></ul>
  33. 33. Wireless Policies Wireless Guidelines Draft <ul><li>Wireless network access points must be registered with CCSO </li></ul><ul><li>Wireless equipment must be registered, including </li></ul><ul><ul><li>2.4 GHz cordless telephones </li></ul></ul><ul><ul><li>Apple Airport Base Stations </li></ul></ul><ul><ul><li>Any computer operating in ad-hoc mode </li></ul></ul><ul><ul><li>Some scientific equipment </li></ul></ul><ul><li>Departmental wireless networks are required to guarantee security </li></ul><ul><li>Resolution of wireless device conflicts </li></ul>
  34. 34. Wireless Policies Beckman Wireless Policy <ul><li>BI researchers with existing wireless networks must provide BISS with the following information: </li></ul><ul><ul><li>Location of access point (room and jack) </li></ul></ul><ul><ul><li>Frequency / channel </li></ul></ul><ul><ul><li>Power output </li></ul></ul><ul><ul><li>Coverage area (intended and active) </li></ul></ul><ul><ul><li>Equipment description (manufacturer and model) </li></ul></ul><ul><ul><li>Responsible admin and tech contacts </li></ul></ul><ul><ul><li>Number of expected users </li></ul></ul><ul><ul><li>How security issues are being addressed </li></ul></ul>
  35. 35. Wireless Policies Beckman Wireless Policy <ul><li>New wireless network equipment should be approved by BISS prior to its purchase and deployment </li></ul><ul><li>Whenever possible, research groups are encouraged to use the Beckman Wireless network for their research rather then purchase stand-alone wireless equipment </li></ul><ul><li>BISS should be provided access to any wireless network equipment deployed by a research group </li></ul>
  36. 36. Wireless Policies Beckman Wireless Policy <ul><li>Running servers or daemons, e.g. www, on the wireless network is prohibited. Such programs use an exorbitant amount of bandwidth and resources. </li></ul><ul><li>Very large downloads, streaming video, or intensive graphic applications are discouraged. </li></ul><ul><li>We reserve the right to limit bandwidth on a per client basis on the wireless network, as necessary, to ensure the reliability and fair sharing of network resources for all wireless users. </li></ul><ul><li>Running any unauthorized data packet collection programs on the wireless network is prohibited. </li></ul>
  37. 37. Wireless Policies Beckman Wireless Policy <ul><li>Restricted access to CCSO student and staff clusters from BI Wireless Network </li></ul><ul><ul><li>No Telnet, FTP POP or IMAP </li></ul></ul><ul><ul><li>SSH only </li></ul></ul><ul><li>Access to other services may be restricted in the future </li></ul><ul><li>Place the BI Wireless Network behind a mostly-closed firewall </li></ul><ul><li>No IP-multicast traffic is allowed </li></ul><ul><li>In-building AppleTalk only </li></ul>
  38. 38. Wireless Policies Beckman Wireless Policy <ul><li>Faculty, staff, and students that register to use the wireless network are assumed to have read and accepted: </li></ul><ul><ul><li>UIUCnet and Campus Acceptable Use Policies </li></ul></ul><ul><ul><li>Beckman Wireless Network Policy </li></ul></ul><ul><ul><li>Computing and Networking sections of the Beckman Information Manual (update for Summer 2002) </li></ul></ul><ul><li>Users assume responsibility to ensure sensitive information (passwords) are secured via VPN, SSH, and/or SSL applications software </li></ul>
  39. 39. Wireless Policies Beckman Wireless Policy <ul><li>Beckman Computer and Network policy is available in the Beckman Information manual </li></ul><ul><li>Information manual being updated for summer 2002 </li></ul>
  40. 40. Wireless Security Think Carefully <ul><li>Consider how critical it is for data to remain secure </li></ul><ul><ul><li>Social security numbers </li></ul></ul><ul><ul><li>Credit card numbers </li></ul></ul><ul><ul><li>Human-subject medical data </li></ul></ul><ul><li>Do not access business applications, such as AITS EOS, ECOS, P-CARD, etc. </li></ul>
  41. 41. Wireless Security Application-Layer Encryption <ul><li>It is imperative that users employ secure applications on top of the wireless network such as SSH and SSL </li></ul><ul><li>Only submit private information, such as passwords and credit card numbers, over SSL-based secure websites </li></ul><ul><li>Use Secure Shell (SSH) instead of telnet for remote logins </li></ul><ul><li>Use Secure FTP (SFTP) instead of FTP </li></ul><ul><li>Use SSH tunnels to check e-mail via POP or IMAP </li></ul>
  42. 42. Wireless Security Web Browser <ul><li>When submitting username and password on web site, make sure it is SSL encrypted </li></ul><ul><li>A padlock appears near the bottom right-hand corner of the web browser </li></ul><ul><li>Internet Explorer </li></ul><ul><ul><li>A padlock appears only if the web page is secure with SSL encryption </li></ul></ul><ul><li>Netscape </li></ul><ul><ul><li>Padlock is open if the web page is unsecured </li></ul></ul><ul><ul><li>Padlock is closed (surrounded by a yellow glow) if the web page is secure with SSL encryption </li></ul></ul>
  43. 43. Wireless Security Telnet and FTP <ul><li>Use SSH instead of telnet </li></ul><ul><li>Use SFTP instead of FTP </li></ul><ul><li>UIUC Site License </li></ul><ul><ul><li>Windows and Linux </li></ul></ul><ul><ul><li>http://www.cso.uiuc.edu/software/sls/index.html </li></ul></ul><ul><li>Windows and Unix clients SSH Secure Shell </li></ul><ul><ul><li>Free to academic institutions </li></ul></ul><ul><ul><li>http://www.ssh.com </li></ul></ul><ul><li>Free Macintosh client MacSSH </li></ul><ul><ul><li>http://www. macssh.com </li></ul></ul><ul><li>CCSO SSH Configuration Documentation </li></ul><ul><ul><li>http://www.cso.uiuc.edu/security/winssh.html </li></ul></ul><ul><ul><li>http://www.cso.uiuc.edu/security/macssh.html </li></ul></ul>
  44. 44. Wireless Security E-mail <ul><li>Do not use POP or IMAP to check email </li></ul><ul><ul><li>Eudora, Outlook, Netscape Mail, etc. </li></ul></ul><ul><li>Webmail – SSL encrypted </li></ul><ul><ul><li>Webmail.uiuc.edu </li></ul></ul><ul><ul><li>Bi-webmail.beckman.uiuc.edu </li></ul></ul><ul><li>SSH to shell accounts </li></ul><ul><ul><li>Pine, Elm, Mutt, etc. </li></ul></ul><ul><li>SSH Tunnels to encrypt POP or IMAP </li></ul><ul><li>http://www.cso.uiuc.edu/security/winssh.html#sshtunnels </li></ul>
  45. 45. Wireless Security VPN <ul><li>Use CCSO’s VPN solution to encrypt all data from your wireless device to the campus backbone </li></ul><ul><li>Continue to use SSH to secure data over the campus backbone and Internet </li></ul>
  46. 46. Accessing the Beckman Wireless Recommended Wireless NICs <ul><li>Any 802.11b WiFi compliant NIC </li></ul><ul><li>Macintosh iBook, iMac, PowerMac G4s </li></ul><ul><ul><li>Apple Airport Card Part# M7600LL/C </li></ul></ul><ul><ul><li>$89 from Computer Stores </li></ul></ul><ul><li>PC Card WinNT/2K/XP and Linux and older Macs </li></ul><ul><ul><li>Lucent ORiNOCO Turbo Gold 128-bit WEP </li></ul></ul><ul><ul><ul><li>$90 from CDWG </li></ul></ul></ul><ul><ul><ul><li>MFR# LUA-848441556 </li></ul></ul></ul><ul><li>Older Macintosh laptops that do not support Airport </li></ul><ul><ul><li>Lucent ORiNOCO Turbo Gold 128-bit WEP </li></ul></ul><ul><li>Others Tested </li></ul><ul><ul><li>Dell TrueMobile Wireless LAN Adapter (built-in to Dell laptops) </li></ul></ul><ul><ul><li>Cisco Aironet 350 Wireless PC Card </li></ul></ul>
  47. 47. Accessing the Beckman Wireless Registration <ul><li>Step 1. Make sure that you have an active UIUC Network ID and password. </li></ul><ul><li>Step 2. Make sure that you are correctly listed in the Beckman Institute personnel web directory with a Network ID. </li></ul>
  48. 48. Access the Beckman Wireless Registration <ul><li>Step 3. Determine the MAC address of the wireless network card you will use. </li></ul><ul><ul><li>The hardware address is a 12-digit hexadecimal address that can be found on the back of the wireless card </li></ul></ul><ul><ul><li>E.g. 00-40-95-34-14-FE </li></ul></ul>
  49. 49. Access the Beckman Wireless Registration <ul><li>Step 4. Register your MAC address. </li></ul><ul><li>Step 5. Install the wireless network card in your portable computer. </li></ul><ul><li>Step 6. Configure your computer to use the Beckman Wireless Network. </li></ul><ul><ul><li>Network (SSID) Name: BeckmanInstitute </li></ul></ul><ul><ul><li>WEP Setting: disabled </li></ul></ul><ul><ul><li>Make sure your TCP/IP network configuration is set to obtain address automatically or dynamically via DHCP </li></ul></ul>
  50. 50. Accessing the Beckman Wireless Troubleshooting <ul><li>Lucent utility called “Site Monitor” </li></ul><ul><li>Make sure that you are in range of the wireless access points </li></ul><ul><li>Shows which versions of firmware and drivers </li></ul><ul><li>Displays signal strength of network where you are located </li></ul><ul><li>Indicates MAC address of access point you are associated with </li></ul><ul><li>Displays radio quality </li></ul><ul><li>Verify you have received an IP address from the DHCP server </li></ul><ul><ul><li>Win 95/98/ME – run “winipcfg” </li></ul></ul><ul><ul><li>Win NT/2K/XP – run “ipconfig /all” </li></ul></ul>
  51. 51. Accessing the Beckman Wireless WEP Keys <ul><li>WEP is optional on Beckman Wireless network </li></ul><ul><li>WEP keys may be entered on wireless devices by BISS staff by request </li></ul><ul><li>Many technical issues </li></ul><ul><ul><li>Some wireless cards will not associate in a mixed-cell environment </li></ul></ul><ul><ul><li>Some versions of MacOS require WEP key to be re-entered upon reboot </li></ul></ul><ul><li>Talk to BISS for more information </li></ul>
  52. 52. Future <ul><li>Investigate 802.11a – 5 GHz </li></ul><ul><ul><li>802.11b interoperability and/or migration? </li></ul></ul><ul><ul><li>Shorter range, greater speed (up to 54 Mbps) </li></ul></ul><ul><li>Investigate 802.11g – 2.4 GHz </li></ul><ul><ul><li>Greater speed (up to 54 Mbps) </li></ul></ul><ul><ul><li>Backward compatible with 802.11b </li></ul></ul><ul><li>Investigate 802.11i – Security </li></ul><ul><ul><li>Data encryption </li></ul></ul><ul><ul><li>User-level authentication / authorization </li></ul></ul><ul><li>Investigate VPN solutions </li></ul>
  53. 53. Comments and Questions <ul><li>We welcome feedback and suggestions on how to accommodate your research needs on the Beckman Wireless network </li></ul>

×