As you can imagine, with a system this complex, there’s plenty of places for things to go wrong. The main thing to remember when troubleshooting problems is to break the system down into the individual components and test each one.
Here are a few things that could go wrong, along with tips on what to check for:
|✓||You don’t see the wireless access point in the client’s list of access points: Check to make sure that the client is in range of the wireless access point. Remember, if you’re using a PC wireless network card, the range may be somewhat limited.|
|Next, use the Network configuration tool to ensure that the wireless network card is active. If something goes wrong with your rc.local script, the wireless cards may not be activated.|
|✓||You can connect to the wireless access point, but you can’t connect to the Internet: Check that the wired network card is active. Use the Network configuration tool to see the status of the wired network card, and activate it if necessary.|
|Also, use the command line brctl command to check the status of the bridge. You can use the showmacs command to see if the client’s network card Ethernet address appears on the bridge’s list of addresses.|
|✓||Everything worked great when you manually set it up, but after rebooting, nothing works: Check your /etc/rc.local script to ensure that you entered the ifconfig and brctl commands in the correct order. It’s also possible that these commands were run before the wireless network card was ...|