Networking Wired and Wireless Computers

I must write before I need Rogaine for the bald patches where I've pulled out my hair.  I've read everything I can find about setting up wired/wireless home networks, and there is obviously something I don't grasp.
Here is my current setup:
My 'main computer' is my desktop PC running Win XP, and connected via Ethernet to a Westell 6100 modem.  It has no wireless adaptor. 
I have a WRT54G Linksys router.  I want to be able to run two notebooks (running XP, with the necessary wireless adaptors) wirelessly.  Is this even possible with the main computer being a wired computer?
If so, do I run the Linksys setup CD on the main computer first even though it has no wireless adaptor?  Or do I run the setup software only on the notebooks?
Additionally, when a wireless network is successfully set up, and an Internet connection ultimately established, must there be at least one Ethernet cable still connected to the Linksys router?
Thank you for reading this post, and I appreciate your tolerance of my ignorance.
Tania
Message Edited by bkzoner on 07-14-2007 08:57 AM
"One good judge of a man's character is how he treats another who can do him no good."

I have a WRT54G Linksys router.  I want to be able to run two notebooks (running XP, with the necessary wireless adaptors) wirelessly.  Is this even possible with the main computer being a wired computer?
To answer that.  Yes you need to have at least one wired PC  to be able to configure your router.  You can access/configure it manually by opening your browser and typing in http://192.168.1.1 (or what ever IP the router is set to) and hit enter.  That will bring up the routers log on window.  By default the user is left blank (some routers the user is admin) and the password is admin.  If the password has been set to something else(as it should be for security reasons) then use that password.  When you access your router make sure you set the SSID to something other then linksys so you can identify your wireless network and configure what ever security you need. If you configure any security write it down so when you connect your wireless computers to your SSID (wireless network) you can enter the settings exactly as they are in the router.
Richard Aichner (Ikester)

Similar Messages

  • Wired and wireless computers on the same network?

    Here’s the scenario: I’ve got Verizon FIOS which comes with a modem with four Ethernet ports. I have an Airport Extreme plugged into the modem. There are six macs in the house (three desktops and three laptops) and they can all connect wirelessly although the signal fades in the living room and in my son’s room. I decided to run an Ethernet cable from the modem to the G5 that is in the living room and another one to my son’s room. Everything works fine but the “wired” computers are now no longer on the same network.
    (At first I thought it was neat: if I was near the G5 and the signal from the Airport Extreme was weak, I could just hop onto the G5’s network (which has “Internet sharing” via airport enabled) but it’s become a nuisance because we always seem to be needing to change from one network to another: The computer connected to the printers is on Airport Extreme so I can’t print from the G5 unless I change the settings; if we’re in the bedroom connected to the Internet via the AirPort Extreme, we can’t access our iTunes music from the G5 without switching networks.)
    I don’t know if there is a solution but it seems there should be.
    I’d like to have two computers hard-wired and have all of them be part of the same home network. Is that possible?

    The solution is simple. Configure the AirPort Extreme base station (AEBS) so that the option to distribute IP addresses is DISABLED.
    This will disable the AEBS's DHCP server and NAT. The net effect will be that anything connected to the AEBS's WAN port (anything connected to Verizon's router's LAN ports like your Ethernet computers) on the same subnet as the AEBS's LAN and wireless clients.

  • Sharing printer with wired and wireless computers

    I am sure there's a topic about this somewhere, but I can't seem to find a clear answer. I have a PowerMac G4 that does not have wireless capabilites. I have a PowerBook G4 that does, and an Airport Express that makes everything possible. Last night I went to hook my laser printer up to the Airport Express. Everything went smoothly, but now I cannot print from my PowerMac. Is there a way that I can set this all up so both computers can use the printer without having to buy an Airport card for the PowerMac?
    Right now the printer is connected to the Airport Express which is connected to my router. The PowerMac is also connected to the router.
    Sorry that I am so clueless about this. Networking baffles me.

    Go to Airport Admin and uncheck "Distribute IP Addresses." With both a router and an Airport Express, you have created two separate networks - turning off part of that brings it back to one. (You may need to restart the Macs)

  • Windows 7 Pro not finding network connections after boot camp installation. Is there something special we have to do to get the network (wired and wireless) set up?

    Any suggestions for getting the network connections working on Windows 7 Pro running on a Mac Min with OSX Lion?

    tim-bob wrote:
    Any suggestions for getting the network connections working on Windows 7 Pro running on a Mac Min with OSX Lion?
    If you haven't yet installed the Windows Support Software, that's probably why, so install it now.

  • Itunes not connecting via airplay on wired and wireless network

    I have some computers on the wired part of my network, and others on wireless. My appletv2 shows in itunes on ALL (both wired and wireless) computers that there exists an AppleTv airplay speaker, but only the computers on the same "side" of the network (wired, or wireless) can actually connect and use the appletv as an airplay device. I have Bell Fibe25 and they provide 2 devices to achieve wireless connectivity, the main VDSL unit that has 4 lan ports on the back, and a basic Cisco WAP610N that connects into one of the lan ports on the VDSL unit for the wireless part.
    My firewall is turned off as well.
    Can anyone shed some light on why this is happening? My MacPro does not have wireless, and it would not be practical to connect my AppleTV2 to Ethernet cable.
    Thanks in advance,
    S

    I have Windows 7 and the same resolution fixed my problem but you do it in a slightly different way:
    Open Control Panel.
    Network and Internet
    Network and Sharing Center
    On the left menu bar select "Change adapter Settings"
    Right Click on Network Adapter (Might be Wireless or Wired or change Both) select Properties
    Under "The connection uses the following items:" UNCHECK - Internet Protocol Version 6 (TCP/IPv6)
    Click OK
    Restart Itunes and refresh Connection!
    Thanks for your help Shane

  • Wired and Wireless Connections to OfficeJet 8620?

    We have a small wired Ethernet network.  We are planning to install an HP OfficeJet 8620 multi-function printer tomorrow.  I understand that for a wired-only Ethernet network, I would just connect the OfficeJet to our router, then install the drivers on each workstation.
    Unfortunately, our situation is more complicated than that.  Several people want to use wireless devices to print to the OfficeJet 8620.  We have a working wireless network in place, and the wireless devices are able to access it without problem..
    All devices on the network (wired and wireless) use the same router, which has both wired Ethernet ports and wireless capability.  So, everything is on the same network, going through the same router.
    From reading the 8620 documentation, it looks like you can only have a wired OR a wireless connection, but not both.  Apparently connecting a CAT-5 cable to the Ethernet port on the printer disables the wireless capability of the printer.
    If that is correct, what can we do to enable both wired computers and wireless mobile devices to print to the 8620, given the network structure I have described above?
    Thanks very much for any assistance you can offer.
    This question was solved.
    View Solution.

    Hi,
    You can setup as shown on page #7 of tyhe following guide:
          http://www.hp.com/ctg/Manual/c00389927.pdf 
    Regards.
    BH
    **Click the KUDOS thumb up on the left to say 'Thanks'**
    Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

  • A very strange wired and wireless network issue

    Hello,
    I have never had any issue at all with my macbook (2008) until this week, I use it both for work and personal use.
    Most of time, I'm used to be on customer site, so I use wired and wireless connections depending of the situation....
    I have never had any issue at all with wifi neither ethernet connections during three years, until this week... and I can say this is the most strange thing I have ever seen....
    Using wired or wireless connection, always the speed of network was really good, at home, many customers, etc never had any problem...
    But this week I'm currently out of home, and the hotel where I'm staying I'm having very poor network rate....
    Using wireless connection, the download speed is no more than 10kb.... and using ethernet I get less speed... but during the day I'm on customer site, using the ethernet connection and download speed is really good, more than 500k-800k....
    I have already tried in the hotel few wifi connections (there are three) and differents wired connections (in diferent rooms) and the download speed is always the same, no more than 10kb...
    During this afternoon, I could go into hotel's lab and could connect directly to the router using cable, same speed no more than 10kb....
    The most strange thing is on their computers the download speed using wired connection is around 6Mb....
    how is possible I'm getting no more than 10kb of download speed when the pc's at hotel using same wired connection gets 6Mb?
    I have already deleted current network connections, execute onyx to clear everything, perform dhcp connection, tried manual ip etc, and always the results are the same...
    I know there is no problem with the macbook, because it works pretty good at every location I've been... but until this week...
    Sincerely I'm getting a little crazy here, I'll appreciate any help!!!
    thanks in advance

    I've seen something like this on my T400 when it was running Vista.  Now that I use Win 7 it's been OK. I rather doubt that your issue is the same but I'm tossing it out here just on the off chance.
    Im my case, I had to downgrade my Intel 5300 card to a 5100 (as suggested by a Lenovo 2nd-tier tech) to get things working.
    My symptoms were a little different.  Wifi was fine until I went back to a wired network.  After that, trying to use the same wifi AP as before would end up associated, but no internet access.  DHCP wasn't working.  The GUI "find" app didn't work as expected either.  Some APs showed up, and some didn't.
    If I configured for automatic connection to my home AP it would try and fail.  Just rebooting at that point would again attempt an automatic connection that would succeed.
    What I have noticed now that I run Win 7 is that Access Connections is completely useless.  Often the "finder" doesn't show an AP 3 feet away.  I didn't notice that this happened after a switch from wired, but maybe.
    Are you using Access Connections?  If so, you might try uninstalling it.
    Sorry I can't be of real help,
    Z.
    The large print: please read the Community Participation Rules before posting. Include as much information as possible: model, machine type, operating system, and a descriptive subject line. Do not include personal information: serial number, telephone number, email address, etc.  The fine print: I do not work for, nor do I speak for Lenovo. Unsolicited private messages will be ignored. ... GeezBlog
    English Community   Deutsche Community   Comunidad en Español   Русскоязычное Сообщество

  • DHCP Server - Different Range for Wired and Wireless Network

    We have DHCP setup on Windows Server 2012r2 and the range given to us by the main HQ is 10.65.112.1-10.65.112.254 (there are several exclusions under this range)
    Now since the range gets exhausted quickly, they provided another one 10.65.122.1-10.65.122.254.
    What our branch would love to do is to dedicate the first range for Wired Computers and the other range for Wireless Devices (Phone,Tablets, Mobiles)
    Right now we have 2 different scopes setup in DHCP, the second one is disabled. In our network we have 6 access points and also have a CISCO SG300-52 Managed Switch. It has an inbuilt DHCP Server and also has the function for DHCP Relay. But we are not actually using any of its functionality as of now.
    So my question is how to have 2 separate ranges for wired and wireless network. People have mentioned vlans but I have no clue on how to get that done.
    Is there a simpler way avoding V-LANS or if not, would love to get step by step procedure on how to go about this. Any help will be much appreciated
    Regards,
    Sheldon

    Hi Sheldon, please read this post
    https://supportforums.cisco.com/thread/2270049
    You will need some modifications though. Steps 1-6 is very relevant. On step 6, you need to pay particular close attention to the "default router". If the SX300 handles your intervlan routing then the default router needs to be the IP of your VLAN. If you have a different device to handle VLAN routing then the default router needs to be that IP address.
    -Tom
    Please mark answered for helpful posts
    http://blogs.cisco.com/smallbusiness/

  • I have a Time Capsule as my router.  I can connect wirelessly to the network and internet with my MBPr, but my Mac Mini will only connect to the network wired or wirelessly. Airport on it sees the internet as green, but will not connect.

    I have the Time Capsule hooked to a wireless modem.  It uses a static IP, which is put in and running.  The MBPr connects, as well as my iPhone 5, to the internet and network without problem.  I can see the Mac Mini, external drive attached to it, and the Time Capsule.  The Mac Mini connects to the network wired or wirelessly, but not to the internet.  On wireless, using AirPort the Internet shows green, but no connection when I open Safari.  The settings under network settings are identical except for LAN IP between the Mac Mini and the MBPr.  I was hoping someone might have an idea of what was going on.  Before I moved the Time Capsule was on Bridge mode from another router, now it is on DHCP and NAT for the internal network.

    No, its is connected direct to the providers fiber box.

  • Officejet Pro L7780 Wired and wireless networking at same time

    I have an officejet pro L7780 printer that I would like to use wired and wireless networking at the same time.  It that possible.  The printer is connected directly to the network by ethernet, but I would like to print wirelessly with an ipad or iphone using HP ePrint Home and Biz.
    Thanks,
    Maurice Hawley

    The bad news: no it is not possible to have two connections active on your printer at once.
    The good news: the router will connect any device to the printer regardless of how the printer or the devices are connected.  So your iPad can print to a printer that is wired (with Ethernet) to your router.
    If it does not work, restart your router by pulling its power plug momentarily.
    Say thanks by clicking "Kudos" "thumbs up" in the post that helped you.
    I am employed by HP

  • Sharing iTunes between wired and wireless Macs

    Hi,
    I have a Mac laptop connected wirelessly to an Airport Express -- which is wired to a desktop Mac Mini. I'm trying to share music but cannot. I've done all the proper settings in the iTunes preferences and the same in System Preferences -- I think -- on both computers, but on neither computer is anything showing in the Sources window. It says that there are no users online.
    Is there something in the System Preferences box that I'm missing? Should I turn the firewall off (I shouldn't need to, since I've checked the iTunes Sharing box)? Is the main problem here that you can't share music between a wired and wireless computer? (This would be a bit strange to me, but you never know.)
    One other thing. I was trying out the network and I can only get access to the wired Mini's Public folder as a Guest, not as a Registered User. Is there something very badly wrong here?
    Any suggestions welcome. Thanks.

    Thanks for the rapid response. All of those preferences, however, are already set properly (i.e., as you said) on both computers. When I try to go to the Network, I can access the wired desktop Mini's hard drive, but when I try to do it on the mini to get into the laptop's it can't find the afp. It just keeps searching but then says it doesn't exist. Not sure if this network-connectivity problem is relevant or not for this particular issue of iTunes sharing. Grateful for any advice.

  • Wired and Wireless sometimes work (mostly not) after update.

    So I have an issue with my network connection.  It sometimes works, sometimes doesn't (mostly doesn't).  This is for both wired and wireless.  This started to happen a couple of days ago after an update.  I had not updated for about a month prior.  Prior to the update I used WICD and it worked just fine with no problems.  I have no exotic hardware (ipw2200 using its firmware, dell xps gen2 notebook) and I set up everything about 6 months ago based on all the wikis.  I have a dlink dir-825 router.  Both wired and wireless connections work in windows every boot so it's not hardware.
    I've included as much info as possible... sorry for the length.
    Things I've tried:
    Removing the ! from the INTERFACES=(!eth0 !eth1) in rc.conf
    Removing netfs from the daemons
    all the hostnames match in hosts and rc.conf
    Here is my rc.conf
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    # LOCALE: available languages can be listed with the 'locale -a' command
    # HARDWARECLOCK: set to "UTC" or "localtime"
    # USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
    # TIMEZONE: timezones are found in /usr/share/zoneinfo
    # KEYMAP: keymaps are found in /usr/share/kbd/keymaps
    # CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
    # CONSOLEMAP: found in /usr/share/kbd/consoletrans
    # USECOLOR: use ANSI color sequences in startup messages
    LOCALE="en_US.utf8"
    HARDWARECLOCK="local"
    USEDIRECTISA="no"
    TIMEZONE="America/New_York"
    KEYMAP="us"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    # HARDWARE
    # MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
    # MOD_BLACKLIST: Prevent udev from loading these modules
    # MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
    # NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
    MOD_AUTOLOAD="yes"
    #MOD_BLACKLIST=() #deprecated
    MODULES=(acpi-cpufreq cpufreq_ondemand cpufreq_powersave cpufreq_conservative cpufreq_userspace fuse ipw2200)
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="yes"
    # NETWORKING
    # HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
    HOSTNAME="stupendiousman"
    # Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
    # Interfaces to start at boot-up (in this order)
    # Declare each interface then list in INTERFACES
    #   - prefix an entry in INTERFACES with a ! to disable it
    #   - no hyphens in your interface names - Bash doesn't like it
    # DHCP:     Set your interface to "dhcp" (eth0="dhcp")
    # Wireless: See network profiles below
    #eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
    INTERFACES=(!eth0 !eth1)
    # Routes to start at boot-up (in this order)
    # Declare each route then list in ROUTES
    #   - prefix an entry in ROUTES with a ! to disable it
    gateway="default gw 192.168.0.1"
    ROUTES=(!gateway)
    # Enable these network profiles at boot-up.  These are only useful
    # if you happen to need multiple network configurations (ie, laptop users)
    #   - set to 'menu' to present a menu during boot-up (dialog package required)
    #   - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This now requires the netcfg package
    #NETWORKS=(main)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    #   - prefix a daemon with a ! to disable it
    #   - prefix a daemon with a @ to start it up in the background
    DAEMONS=(syslog-ng hal cpufreq wicd alsa crond fam bluetooth)
    Here is my hosts
    # /etc/hosts: static lookup table for host names
    #<ip-address>   <hostname.domain.org>   <hostname>
    127.0.0.1               localhost.localdomain   localhost stupendiousman
    # End of file
    Here is my mkinitcpio.conf
    # vim:set ft=sh
    # MODULES
    # The following modules are loaded before any boot hooks are
    # run.  Advanced users may wish to specify all system modules
    # in this array.  For instance:
    #     MODULES="piix ide_disk reiserfs"
    MODULES=""
    CRYPTO_MODULES="aes_generic aes_i586 dm_crypt xts"
    # BINARIES
    # This setting includes, into the CPIO image, and additional
    # binaries a given user may wish.  This is run first, so may
    # be used to override the actual binaries used in a given hook.
    # (Existing files are NOT overwritten is already added)
    # BINARIES are dependancy parsed, so you may safely ignore libraries
    BINARIES=""
    # FILES
    # This setting is similar to BINARIES above, however, files are added
    # as-is and are not parsed in anyway.  This is useful for config files.
    # Some users may wish to include modprobe.conf for custom module options,
    # like so:
    #    FILES="/etc/modprobe.conf"
    FILES=""
    # HOOKS
    # This is the most important setting in this file.  The HOOKS control the
    # modules and scripts added to the image, and what happens at boot time.
    # Order is important, and it is recommended that you do not change the
    # order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
    # help on a given hook.
    # 'base' is _required_ unless you know precisely what you are doing.
    # 'udev' is _required_ in order to automatically load modules
    # 'modload' may be used in place of 'udev', but is not recommended
    # 'filesystems' is _required_ unless you specify your fs modules in MODULES
    # Examples:
    #    This setup specifies all modules in the MODULES setting above.
    #    No raid, lvm2, or encrypted root is needed.
    #    HOOKS="base"
    #    This setup will autodetect all modules for your system and should
    #    work as a sane default
    #    HOOKS="base udev autodetect pata scsi sata filesystems"
    #    This is identical to the above, except the old ide subsystem is
    #    used for IDE devices instead of the new pata subsystem.
    #    HOOKS="base udev autodetect ide scsi sata filesystems"
    #    This setup will generate a 'full' image which supports most systems.
    #    No autodetection is done.
    #    HOOKS="base udev pata scsi sata usb filesystems"
    #    This setup assembles an pata raid array with an encrypted root FS.
    #    Note: See 'mkinitcpio -H raid' for more information on raid devices.
    #    HOOKS="base udev pata raid encrypt filesystems"
    #    This setup loads an lvm2 volume group on a usb device.
    #    HOOKS="base udev usb lvm2 filesystems"
    HOOKS="base udev autodetect pata scsi sata encrypt lvm2 resume filesystems firmware"
    lspci
    00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03)
    00:01.0 PCI bridge: Intel Corporation Mobile 915GM/PM Express PCI Express Root Port (rev 03)
    00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03)
    00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03)
    00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03)
    00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03)
    00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03)
    00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3)
    00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03)
    00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Modem Controller (rev 03)
    00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 03)
    00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 03)
    00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03)
    01:00.0 VGA compatible controller: nVidia Corporation NV41.9 [GeForce Go 6800 Ultra] (rev a2)
    03:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5705M_2 Gigabit Ethernet (rev 03)
    03:01.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev b3)
    03:01.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE 1394 Controller (rev 08)
    03:01.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 17)
    03:03.0 Network controller: Intel Corporation PRO/Wireless 2915ABG [Calexico2] Network Connection (rev 05)
    ifconfig returns:
    [rick@stupendiousman ~]$ ifconfig
    eth0      Link encap:Ethernet  HWaddr 00:12:F0:3E:CA:66 
              inet6 addr: fe80::212:f0ff:fe3e:ca66/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0 b)  TX bytes:4454 (4.3 Kb)
              Interrupt:17 Base address:0x6000 Memory:dcfef000-dcfeffff
    eth1      Link encap:Ethernet  HWaddr 00:11:43:72:B5:96 
              UP BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
              Interrupt:18
    lo        Link encap:Local Loopback 
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:4 errors:0 dropped:0 overruns:0 frame:0
              TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:280 (280.0 b)  TX bytes:280 (280.0 b)
    If I do a iwlist scan I get:
    [rick@stupendiousman ~]$ iwlist scan
    lo        Interface doesn't support scanning.
    eth0      No scan results
    eth1      Interface doesn't support scanning.
    pan0      Interface doesn't support scanning.
    Here is a portion of my /var/log/wicd/wicd.log
    2009/08/15 09:19:29 :: ---------------------------
    2009/08/15 09:19:29 :: wicd initializing...
    2009/08/15 09:19:29 :: ---------------------------
    2009/08/15 09:19:29 :: wicd is version 1.6.2 436
    2009/08/15 09:19:29 :: setting backend to external
    2009/08/15 09:19:29 :: trying to load backend external
    2009/08/15 09:19:30 :: successfully loaded backend external
    2009/08/15 09:19:30 :: trying to load backend external
    2009/08/15 09:19:30 :: successfully loaded backend external
    2009/08/15 09:19:30 :: Automatically detected wireless interface eth0
    2009/08/15 09:19:30 :: setting wireless interface eth1
    2009/08/15 09:19:30 :: automatically detected wired interface eth1
    2009/08/15 09:19:30 :: setting wired interface eth0
    2009/08/15 09:19:30 :: setting wpa driver wext
    2009/08/15 09:19:30 :: setting use global dns to False
    2009/08/15 09:19:30 :: setting global dns
    2009/08/15 09:19:30 :: global dns servers are None None None
    2009/08/15 09:19:30 :: domain is None
    2009/08/15 09:19:30 :: search domain is None
    2009/08/15 09:19:30 :: setting automatically reconnect when connection drops True
    2009/08/15 09:19:30 :: Setting dhcp client to 0
    2009/08/15 09:19:30 :: Wireless configuration file found...
    2009/08/15 09:19:30 :: Wired configuration file found...
    2009/08/15 09:19:30 :: chmoding configuration files 0600...
    2009/08/15 09:19:30 :: chowning configuration files root:root...
    2009/08/15 09:19:30 :: Using wireless interface...eth1
    2009/08/15 09:19:30 :: Using wired interface...eth0
    2009/08/15 09:19:36 :: Autoconnecting...
    2009/08/15 09:19:39 :: Attempting to autoconnect with wired interface...
    2009/08/15 09:19:39 :: Putting interface down
    2009/08/15 09:19:39 :: Releasing DHCP leases...
    2009/08/15 09:19:39 :: Setting false IP...
    2009/08/15 09:19:39 :: Flushing the routing table...
    2009/08/15 09:19:39 :: Putting interface up...
    2009/08/15 09:19:39 :: Running DHCP
    2009/08/15 09:19:39 :: dhcpcd: version 5.0.6 starting
    2009/08/15 09:19:39 ::
    2009/08/15 09:19:39 :: dhcpcd: eth0: broadcasting for a lease
    2009/08/15 09:19:39 ::
    2009/08/15 09:20:09 :: dhcpcd: timed out
    2009/08/15 09:20:09 ::
    2009/08/15 09:20:09 :: DHCP connection failed
    2009/08/15 09:20:09 :: exiting connection thread
    2009/08/15 09:20:11 :: No wired connection present, attempting to autoconnect to wireless network
    2009/08/15 09:20:11 :: Unable to autoconnect, you'll have to manually connect
    2009/08/15 09:20:11 :: Sending connection attempt result dhcp_failed
    2009/08/15 09:21:03 :: trying to load backend ioctl
    2009/08/15 09:21:03 :: WARNING: python-iwscan not found, falling back to using iwlist scan.
    2009/08/15 09:21:03 :: WARNING: python-wpactrl not found, falling back to using wpa_cli.
    2009/08/15 09:21:03 :: trying to load backend external
    2009/08/15 09:21:10 :: Putting interface down
    2009/08/15 09:21:10 :: Releasing DHCP leases...
    2009/08/15 09:21:10 :: Setting false IP...
    2009/08/15 09:21:10 :: Flushing the routing table...
    2009/08/15 09:21:10 :: Putting interface up...
    2009/08/15 09:21:10 :: Running DHCP
    2009/08/15 09:21:10 :: dhcpcd: version 5.0.6 starting
    2009/08/15 09:21:10 ::
    2009/08/15 09:21:10 :: dhcpcd: eth0: broadcasting for a lease
    2009/08/15 09:21:10 ::
    2009/08/15 09:21:40 :: dhcpcd: timed out
    2009/08/15 09:21:40 ::
    2009/08/15 09:21:40 :: DHCP connection failed
    2009/08/15 09:21:40 :: exiting connection thread
    2009/08/15 09:21:40 :: Sending connection attempt result dhcp_failed
    2009/08/15 09:22:28 :: Putting interface down
    2009/08/15 09:22:28 :: Releasing DHCP leases...
    2009/08/15 09:22:28 :: Setting false IP...
    2009/08/15 09:22:28 :: Flushing the routing table...
    2009/08/15 09:22:28 :: Putting interface up...
    2009/08/15 09:22:28 :: Running DHCP
    2009/08/15 09:22:28 :: dhcpcd: version 5.0.6 starting
    2009/08/15 09:22:28 ::
    2009/08/15 09:22:28 :: dhcpcd: eth0: broadcasting for a lease
    2009/08/15 09:22:28 ::
    2009/08/15 09:22:58 :: dhcpcd: timed out
    2009/08/15 09:22:58 ::
    2009/08/15 09:22:58 :: DHCP connection failed
    2009/08/15 09:22:58 :: exiting connection thread
    2009/08/15 09:22:58 :: Sending connection attempt result dhcp_failed
    2009/08/15 09:23:17 :: Daemon going down, killing wicd-monitor...
    2009/08/15 09:23:17 :: Removing PID file...
    2009/08/15 09:23:17 :: Shutting down...
    2009/08/15 13:16:59 :: ---------------------------
    2009/08/15 13:16:59 :: wicd initializing...
    2009/08/15 13:16:59 :: ---------------------------
    2009/08/15 13:16:59 :: wicd is version 1.6.2 436
    2009/08/15 13:16:59 :: setting backend to external
    2009/08/15 13:16:59 :: trying to load backend external
    2009/08/15 13:17:00 :: successfully loaded backend external
    2009/08/15 13:17:00 :: trying to load backend external
    2009/08/15 13:17:00 :: successfully loaded backend external
    2009/08/15 13:17:00 :: Automatically detected wireless interface eth0
    2009/08/15 13:17:00 :: setting wireless interface eth1
    2009/08/15 13:17:00 :: automatically detected wired interface eth1
    2009/08/15 13:17:00 :: setting wired interface eth0
    2009/08/15 13:17:00 :: setting wpa driver wext
    2009/08/15 13:17:00 :: setting use global dns to False
    2009/08/15 13:17:00 :: setting global dns
    2009/08/15 13:17:00 :: global dns servers are None None None
    2009/08/15 13:17:00 :: domain is None
    2009/08/15 13:17:00 :: search domain is None
    2009/08/15 13:17:00 :: setting automatically reconnect when connection drops True
    2009/08/15 13:17:00 :: Setting dhcp client to 0
    2009/08/15 13:17:00 :: Wireless configuration file found...
    2009/08/15 13:17:00 :: Wired configuration file found...
    2009/08/15 13:17:00 :: chmoding configuration files 0600...
    2009/08/15 13:17:00 :: chowning configuration files root:root...
    2009/08/15 13:17:00 :: Using wireless interface...eth1
    2009/08/15 13:17:00 :: Using wired interface...eth0
    2009/08/15 13:17:06 :: Autoconnecting...
    2009/08/15 13:17:09 :: Attempting to autoconnect with wired interface...
    2009/08/15 13:17:09 :: Putting interface down
    2009/08/15 13:17:09 :: Releasing DHCP leases...
    2009/08/15 13:17:09 :: Setting false IP...
    2009/08/15 13:17:09 :: Flushing the routing table...
    2009/08/15 13:17:09 :: Putting interface up...
    2009/08/15 13:17:09 :: Running DHCP
    2009/08/15 13:17:09 :: dhcpcd: version 5.0.6 starting
    2009/08/15 13:17:09 ::
    2009/08/15 13:17:09 :: dhcpcd: eth0: broadcasting for a lease
    2009/08/15 13:17:09 ::
    2009/08/15 13:17:39 :: dhcpcd: timed out
    2009/08/15 13:17:39 ::
    2009/08/15 13:17:39 :: DHCP connection failed
    2009/08/15 13:17:39 :: exiting connection thread
    2009/08/15 13:17:41 :: No wired connection present, attempting to autoconnect to wireless network
    2009/08/15 13:17:41 :: Unable to autoconnect, you'll have to manually connect
    2009/08/15 13:17:41 :: Sending connection attempt result dhcp_failed
    2009/08/15 13:18:10 :: Daemon going down, killing wicd-monitor...
    2009/08/15 13:18:10 :: Removing PID file...
    2009/08/15 13:18:10 :: Shutting down...
    2009/08/15 13:19:01 :: ---------------------------
    2009/08/15 13:19:01 :: wicd initializing...
    2009/08/15 13:19:01 :: ---------------------------
    2009/08/15 13:19:01 :: wicd is version 1.6.2 436
    2009/08/15 13:19:01 :: setting backend to external
    2009/08/15 13:19:01 :: trying to load backend external
    2009/08/15 13:19:02 :: successfully loaded backend external
    2009/08/15 13:19:02 :: trying to load backend external
    2009/08/15 13:19:02 :: successfully loaded backend external
    2009/08/15 13:19:02 :: Automatically detected wireless interface eth0
    2009/08/15 13:19:02 :: setting wireless interface eth1
    2009/08/15 13:19:02 :: automatically detected wired interface eth1
    2009/08/15 13:19:02 :: setting wired interface eth0
    2009/08/15 13:19:02 :: setting wpa driver wext
    2009/08/15 13:19:02 :: setting use global dns to False
    2009/08/15 13:19:02 :: setting global dns
    2009/08/15 13:19:02 :: global dns servers are None None None
    2009/08/15 13:19:02 :: domain is None
    2009/08/15 13:19:02 :: search domain is None
    2009/08/15 13:19:02 :: setting automatically reconnect when connection drops True
    2009/08/15 13:19:02 :: Setting dhcp client to 0
    2009/08/15 13:19:02 :: Wireless configuration file found...
    2009/08/15 13:19:02 :: Wired configuration file found...
    2009/08/15 13:19:02 :: chmoding configuration files 0600...
    2009/08/15 13:19:02 :: chowning configuration files root:root...
    2009/08/15 13:19:02 :: Using wireless interface...eth1
    2009/08/15 13:19:02 :: Using wired interface...eth0
    2009/08/15 13:19:08 :: Autoconnecting...
    2009/08/15 13:19:11 :: Attempting to autoconnect with wired interface...
    2009/08/15 13:19:11 :: Putting interface down
    2009/08/15 13:19:11 :: Releasing DHCP leases...
    2009/08/15 13:19:11 :: Setting false IP...
    2009/08/15 13:19:11 :: Flushing the routing table...
    2009/08/15 13:19:11 :: Putting interface up...
    2009/08/15 13:19:11 :: Running DHCP
    2009/08/15 13:19:11 :: dhcpcd: version 5.0.6 starting
    2009/08/15 13:19:11 ::
    2009/08/15 13:19:11 :: dhcpcd: eth0: broadcasting for a lease
    2009/08/15 13:19:11 ::
    2009/08/15 13:19:41 :: dhcpcd: timed out
    2009/08/15 13:19:41 ::
    2009/08/15 13:19:41 :: DHCP connection failed
    2009/08/15 13:19:41 :: exiting connection thread
    2009/08/15 13:19:43 :: No wired connection present, attempting to autoconnect to wireless network
    2009/08/15 13:19:43 :: Unable to autoconnect, you'll have to manually connect
    2009/08/15 13:19:43 :: Sending connection attempt result dhcp_failed
    2009/08/15 13:30:36 :: Daemon going down, killing wicd-monitor...
    2009/08/15 13:30:36 :: Removing PID file...
    2009/08/15 13:30:36 :: Shutting down...
    2009/08/15 13:31:29 :: ---------------------------
    2009/08/15 13:31:29 :: wicd initializing...
    2009/08/15 13:31:29 :: ---------------------------
    2009/08/15 13:31:29 :: wicd is version 1.6.2 436
    2009/08/15 13:31:29 :: setting backend to external
    2009/08/15 13:31:29 :: trying to load backend external
    2009/08/15 13:31:30 :: successfully loaded backend external
    2009/08/15 13:31:30 :: trying to load backend external
    2009/08/15 13:31:30 :: successfully loaded backend external
    2009/08/15 13:31:30 :: Automatically detected wireless interface eth0
    2009/08/15 13:31:30 :: setting wireless interface eth1
    2009/08/15 13:31:30 :: automatically detected wired interface eth1
    2009/08/15 13:31:30 :: setting wired interface eth0
    2009/08/15 13:31:30 :: setting wpa driver wext
    2009/08/15 13:31:30 :: setting use global dns to False
    2009/08/15 13:31:30 :: setting global dns
    2009/08/15 13:31:30 :: global dns servers are None None None
    2009/08/15 13:31:30 :: domain is None
    2009/08/15 13:31:30 :: search domain is None
    2009/08/15 13:31:30 :: setting automatically reconnect when connection drops True
    2009/08/15 13:31:30 :: Setting dhcp client to 0
    2009/08/15 13:31:30 :: Wireless configuration file found...
    2009/08/15 13:31:30 :: Wired configuration file found...
    2009/08/15 13:31:30 :: chmoding configuration files 0600...
    2009/08/15 13:31:30 :: chowning configuration files root:root...
    2009/08/15 13:31:30 :: Using wireless interface...eth1
    2009/08/15 13:31:30 :: Using wired interface...eth0
    2009/08/15 13:31:37 :: Autoconnecting...
    2009/08/15 13:31:39 :: Attempting to autoconnect with wired interface...
    2009/08/15 13:31:39 :: Putting interface down
    2009/08/15 13:31:39 :: Releasing DHCP leases...
    2009/08/15 13:31:39 :: Setting false IP...
    2009/08/15 13:31:39 :: Flushing the routing table...
    2009/08/15 13:31:39 :: Putting interface up...
    2009/08/15 13:31:39 :: Running DHCP
    2009/08/15 13:31:39 :: dhcpcd: version 5.0.6 starting
    2009/08/15 13:31:39 ::
    2009/08/15 13:31:40 :: dhcpcd: eth0: broadcasting for a lease
    2009/08/15 13:31:40 ::
    2009/08/15 13:32:09 :: dhcpcd: timed out
    2009/08/15 13:32:09 ::
    2009/08/15 13:32:09 :: DHCP connection failed
    2009/08/15 13:32:09 :: exiting connection thread
    2009/08/15 13:32:12 :: No wired connection present, attempting to autoconnect to wireless network
    2009/08/15 13:32:12 :: Unable to autoconnect, you'll have to manually connect
    2009/08/15 13:32:12 :: Sending connection attempt result dhcp_failed
    2009/08/15 13:38:00 :: Daemon going down, killing wicd-monitor...
    2009/08/15 13:38:00 :: Removing PID file...
    2009/08/15 13:38:00 :: Shutting down...
    2009/08/15 13:39:19 :: ---------------------------
    2009/08/15 13:39:19 :: wicd initializing...
    2009/08/15 13:39:19 :: ---------------------------
    2009/08/15 13:39:19 :: wicd is version 1.6.2 436
    2009/08/15 13:39:19 :: setting backend to external
    2009/08/15 13:39:19 :: trying to load backend external
    2009/08/15 13:39:20 :: successfully loaded backend external
    2009/08/15 13:39:20 :: trying to load backend external
    2009/08/15 13:39:20 :: successfully loaded backend external
    2009/08/15 13:39:20 :: Automatically detected wireless interface eth0
    2009/08/15 13:39:20 :: setting wireless interface eth1
    2009/08/15 13:39:20 :: automatically detected wired interface eth1
    2009/08/15 13:39:20 :: setting wired interface eth0
    2009/08/15 13:39:20 :: setting wpa driver wext
    2009/08/15 13:39:20 :: setting use global dns to False
    2009/08/15 13:39:20 :: setting global dns
    2009/08/15 13:39:20 :: global dns servers are None None None
    2009/08/15 13:39:20 :: domain is None
    2009/08/15 13:39:20 :: search domain is None
    2009/08/15 13:39:20 :: setting automatically reconnect when connection drops True
    2009/08/15 13:39:20 :: Setting dhcp client to 0
    2009/08/15 13:39:20 :: Wireless configuration file found...
    2009/08/15 13:39:20 :: Wired configuration file found...
    2009/08/15 13:39:20 :: chmoding configuration files 0600...
    2009/08/15 13:39:20 :: chowning configuration files root:root...
    2009/08/15 13:39:20 :: Using wireless interface...eth1
    2009/08/15 13:39:20 :: Using wired interface...eth0
    2009/08/15 13:39:27 :: Autoconnecting...
    2009/08/15 13:39:29 :: Attempting to autoconnect with wired interface...
    2009/08/15 13:39:29 :: Putting interface down
    2009/08/15 13:39:29 :: Releasing DHCP leases...
    2009/08/15 13:39:29 :: Setting false IP...
    2009/08/15 13:39:29 :: Flushing the routing table...
    2009/08/15 13:39:29 :: Putting interface up...
    2009/08/15 13:39:29 :: Running DHCP
    2009/08/15 13:39:29 :: dhcpcd: version 5.0.6 starting
    2009/08/15 13:39:29 ::
    2009/08/15 13:39:30 :: dhcpcd: eth0: broadcasting for a lease
    2009/08/15 13:39:30 ::
    2009/08/15 13:39:59 :: dhcpcd: timed out
    2009/08/15 13:39:59 ::
    2009/08/15 13:39:59 :: DHCP connection failed
    2009/08/15 13:39:59 :: exiting connection thread
    2009/08/15 13:40:02 :: No wired connection present, attempting to autoconnect to wireless network
    2009/08/15 13:40:02 :: Unable to autoconnect, you'll have to manually connect
    2009/08/15 13:40:02 :: Sending connection attempt result dhcp_failed
    2009/08/15 13:45:10 :: Daemon going down, killing wicd-monitor...
    2009/08/15 13:45:10 :: Removing PID file...
    2009/08/15 13:45:10 :: Shutting down...
    2009/08/15 13:46:13 :: ---------------------------
    2009/08/15 13:46:13 :: wicd initializing...
    2009/08/15 13:46:13 :: ---------------------------
    2009/08/15 13:46:13 :: wicd is version 1.6.2 436
    2009/08/15 13:46:13 :: setting backend to external
    2009/08/15 13:46:13 :: trying to load backend external
    2009/08/15 13:46:14 :: successfully loaded backend external
    2009/08/15 13:46:14 :: trying to load backend external
    2009/08/15 13:46:14 :: successfully loaded backend external
    2009/08/15 13:46:14 :: Automatically detected wireless interface eth1
    2009/08/15 13:46:14 :: setting wireless interface eth1
    2009/08/15 13:46:14 :: automatically detected wired interface eth0
    2009/08/15 13:46:14 :: setting wired interface eth0
    2009/08/15 13:46:14 :: setting wpa driver wext
    2009/08/15 13:46:14 :: setting use global dns to False
    2009/08/15 13:46:14 :: setting global dns
    2009/08/15 13:46:14 :: global dns servers are None None None
    2009/08/15 13:46:14 :: domain is None
    2009/08/15 13:46:14 :: search domain is None
    2009/08/15 13:46:14 :: setting automatically reconnect when connection drops True
    2009/08/15 13:46:14 :: Setting dhcp client to 0
    2009/08/15 13:46:14 :: Wireless configuration file found...
    2009/08/15 13:46:14 :: Wired configuration file found...
    2009/08/15 13:46:14 :: chmoding configuration files 0600...
    2009/08/15 13:46:14 :: chowning configuration files root:root...
    2009/08/15 13:46:14 :: Using wireless interface...eth1
    2009/08/15 13:46:14 :: Using wired interface...eth0
    2009/08/15 13:46:20 :: Autoconnecting...
    2009/08/15 13:46:22 :: No wired connection present, attempting to autoconnect to wireless network
    2009/08/15 13:46:22 :: trying to automatically connect to...101
    2009/08/15 13:46:22 :: Connecting to wireless network 101
    2009/08/15 13:46:23 :: Putting interface down
    2009/08/15 13:46:23 :: Releasing DHCP leases...
    2009/08/15 13:46:23 :: Setting false IP...
    2009/08/15 13:46:23 :: Stopping wpa_supplicant
    2009/08/15 13:46:23 :: Flushing the routing table...
    2009/08/15 13:46:23 :: Putting interface up...
    2009/08/15 13:46:23 :: Generating psk...
    2009/08/15 13:46:23 :: Attempting to authenticate...
    2009/08/15 13:46:34 :: Running DHCP
    2009/08/15 13:46:34 :: dhcpcd: version 5.0.6 starting
    2009/08/15 13:46:34 ::
    2009/08/15 13:46:34 :: dhcpcd: eth1: broadcasting for a lease
    2009/08/15 13:46:34 ::
    2009/08/15 13:46:35 :: dhcpcd: eth1: offered 192.168.0.183 from 192.168.0.1
    2009/08/15 13:46:35 ::
    2009/08/15 13:46:35 :: dhcpcd: eth1: acknowledged 192.168.0.183 from 192.168.0.1
    2009/08/15 13:46:35 ::
    2009/08/15 13:46:35 :: dhcpcd: eth1: checking for 192.168.0.183
    2009/08/15 13:46:35 ::
    2009/08/15 13:46:38 :: dhcpcd: eth1: carrier lost
    2009/08/15 13:46:38 ::
    2009/08/15 13:46:40 :: dhcpcd: eth1: carrier acquired
    2009/08/15 13:46:40 ::
    2009/08/15 13:46:40 :: dhcpcd: eth1: broadcasting for a lease
    2009/08/15 13:46:40 ::
    2009/08/15 13:46:45 :: dhcpcd: eth1: offered 192.168.0.183 from 192.168.0.1
    2009/08/15 13:46:45 ::
    2009/08/15 13:46:45 :: dhcpcd: eth1: acknowledged 192.168.0.183 from 192.168.0.1
    2009/08/15 13:46:45 ::
    2009/08/15 13:46:45 :: dhcpcd: eth1: checking for 192.168.0.183
    2009/08/15 13:46:45 ::
    2009/08/15 13:46:51 :: dhcpcd: eth1: leased 192.168.0.183 for 86400 seconds
    2009/08/15 13:46:51 ::
    2009/08/15 13:46:51 :: dhcpcd: forking to background
    2009/08/15 13:46:51 ::
    2009/08/15 13:46:51 ::
    2009/08/15 13:46:51 :: DHCP connection successful
    2009/08/15 13:46:51 :: Connecting thread exiting.
    2009/08/15 13:46:55 :: Sending connection attempt result Success
    2009/08/15 13:48:50 :: Putting interface down
    2009/08/15 13:48:50 :: Releasing DHCP leases...
    2009/08/15 13:48:50 :: Setting false IP...
    2009/08/15 13:48:51 :: Flushing the routing table...
    2009/08/15 13:48:51 :: Putting interface up...
    2009/08/15 13:48:51 :: Running DHCP
    2009/08/15 13:48:51 :: dhcpcd: version 5.0.6 starting
    2009/08/15 13:48:51 ::
    2009/08/15 13:48:51 :: dhcpcd: eth0: broadcasting for a lease
    2009/08/15 13:48:51 ::
    2009/08/15 13:48:51 :: dhcpcd: eth0: carrier lost
    2009/08/15 13:48:51 ::
    2009/08/15 13:48:53 :: dhcpcd: eth0: carrier acquired
    2009/08/15 13:48:53 ::
    2009/08/15 13:48:53 :: dhcpcd: eth0: broadcasting for a lease
    2009/08/15 13:48:53 ::
    2009/08/15 13:48:54 :: dhcpcd: eth0: offered 192.168.0.193 from 192.168.0.1
    2009/08/15 13:48:54 ::
    2009/08/15 13:48:54 :: dhcpcd: eth0: acknowledged 192.168.0.193 from 192.168.0.1
    2009/08/15 13:48:54 ::
    2009/08/15 13:48:54 :: dhcpcd: eth0: checking for 192.168.0.193
    2009/08/15 13:48:54 ::
    2009/08/15 13:49:00 :: dhcpcd: eth0: leased 192.168.0.193 for 86400 seconds
    2009/08/15 13:49:00 ::
    2009/08/15 13:49:00 :: dhcpcd: forking to background
    2009/08/15 13:49:00 ::
    2009/08/15 13:49:00 ::
    2009/08/15 13:49:00 :: DHCP connection successful
    2009/08/15 13:49:00 :: Connecting thread exiting.
    2009/08/15 13:49:00 :: Sending connection attempt result Success
    2009/08/15 13:53:46 :: Connecting to wireless network 102
    2009/08/15 13:53:47 :: Putting interface down
    2009/08/15 13:53:47 :: Releasing DHCP leases...
    2009/08/15 13:53:47 :: Setting false IP...
    2009/08/15 13:53:47 :: Stopping wpa_supplicant
    2009/08/15 13:53:47 :: Flushing the routing table...
    2009/08/15 13:53:47 :: Putting interface up...
    2009/08/15 13:53:47 :: Generating psk...
    2009/08/15 13:53:47 :: Attempting to authenticate...
    2009/08/15 13:54:03 :: Running DHCP
    2009/08/15 13:54:03 :: dhcpcd: version 5.0.6 starting
    2009/08/15 13:54:03 ::
    2009/08/15 13:54:03 :: dhcpcd: eth1: rebinding lease of 192.168.0.183
    2009/08/15 13:54:03 ::
    2009/08/15 13:54:03 :: dhcpcd: eth1: acknowledged 192.168.0.183 from 192.168.0.1
    2009/08/15 13:54:03 ::
    2009/08/15 13:54:03 :: dhcpcd: eth1: checking for 192.168.0.183
    2009/08/15 13:54:03 ::
    2009/08/15 13:54:05 :: dhcpcd: eth1: carrier lost
    2009/08/15 13:54:05 ::
    2009/08/15 13:54:06 :: dhcpcd: eth1: carrier acquired
    2009/08/15 13:54:06 ::
    2009/08/15 13:54:06 :: dhcpcd: eth1: rebinding lease of 192.168.0.183
    2009/08/15 13:54:06 ::
    2009/08/15 13:54:06 :: dhcpcd: eth1: acknowledged 192.168.0.183 from 192.168.0.1
    2009/08/15 13:54:06 ::
    2009/08/15 13:54:06 :: dhcpcd: eth1: checking for 192.168.0.183
    2009/08/15 13:54:06 ::
    2009/08/15 13:54:11 :: dhcpcd: eth1: leased 192.168.0.183 for 86400 seconds
    2009/08/15 13:54:11 ::
    2009/08/15 13:54:11 :: dhcpcd: forking to background
    2009/08/15 13:54:11 ::
    2009/08/15 13:54:11 ::
    2009/08/15 13:54:11 :: DHCP connection successful
    2009/08/15 13:54:11 :: Connecting thread exiting.
    2009/08/15 13:54:11 :: Sending connection attempt result Success
    2009/08/15 13:55:03 :: Daemon going down, killing wicd-monitor...
    2009/08/15 13:55:03 :: Removing PID file...
    2009/08/15 13:55:03 :: Shutting down...
    2009/08/15 13:55:52 :: ---------------------------
    2009/08/15 13:55:52 :: wicd initializing...
    2009/08/15 13:55:52 :: ---------------------------
    2009/08/15 13:55:52 :: wicd is version 1.6.2 436
    2009/08/15 13:55:52 :: setting backend to external
    2009/08/15 13:55:52 :: trying to load backend external
    2009/08/15 13:55:53 :: successfully loaded backend external
    2009/08/15 13:55:53 :: trying to load backend external
    2009/08/15 13:55:53 :: successfully loaded backend external
    2009/08/15 13:55:53 :: Automatically detected wireless interface eth0
    2009/08/15 13:55:53 :: setting wireless interface eth1
    2009/08/15 13:55:53 :: automatically detected wired interface eth1
    2009/08/15 13:55:53 :: setting wired interface eth0
    2009/08/15 13:55:53 :: setting wpa driver wext
    2009/08/15 13:55:53 :: setting use global dns to False
    2009/08/15 13:55:53 :: setting global dns
    2009/08/15 13:55:53 :: global dns servers are None None None
    2009/08/15 13:55:53 :: domain is None
    2009/08/15 13:55:53 :: search domain is None
    2009/08/15 13:55:53 :: setting automatically reconnect when connection drops True
    2009/08/15 13:55:53 :: Setting dhcp client to 0
    2009/08/15 13:55:53 :: Wireless configuration file found...
    2009/08/15 13:55:53 :: Wired configuration file found...
    2009/08/15 13:55:53 :: chmoding configuration files 0600...
    2009/08/15 13:55:53 :: chowning configuration files root:root...
    2009/08/15 13:55:53 :: Using wireless interface...eth1
    2009/08/15 13:55:53 :: Using wired interface...eth0
    2009/08/15 13:55:59 :: Autoconnecting...
    2009/08/15 13:56:02 :: Attempting to autoconnect with wired interface...
    2009/08/15 13:56:02 :: Putting interface down
    2009/08/15 13:56:02 :: Releasing DHCP leases...
    2009/08/15 13:56:02 :: Setting false IP...
    2009/08/15 13:56:02 :: Flushing the routing table...
    2009/08/15 13:56:02 :: Putting interface up...
    2009/08/15 13:56:02 :: Running DHCP
    2009/08/15 13:56:02 :: dhcpcd: version 5.0.6 starting
    2009/08/15 13:56:02 ::
    2009/08/15 13:56:02 :: dhcpcd: eth0: rebinding lease of 192.168.0.193
    2009/08/15 13:56:02 ::
    2009/08/15 13:56:12 :: dhcpcd: eth0: broadcasting for a lease
    2009/08/15 13:56:12 ::
    2009/08/15 13:56:32 :: dhcpcd: timed out
    2009/08/15 13:56:32 ::
    2009/08/15 13:56:32 :: DHCP connection failed
    2009/08/15 13:56:32 :: exiting connection thread
    2009/08/15 13:56:34 :: No wired connection present, attempting to autoconnect to wireless network
    2009/08/15 13:56:34 :: Unable to autoconnect, you'll have to manually connect
    2009/08/15 13:56:34 :: Sending connection attempt result dhcp_failed
    2009/08/15 13:57:31 :: Daemon going down, killing wicd-monitor...
    2009/08/15 13:57:31 :: Removing PID file...
    2009/08/15 13:57:31 :: Shutting down...
    2009/08/15 13:57:32 :: ---------------------------
    2009/08/15 13:57:32 :: wicd initializing...
    2009/08/15 13:57:32 :: ---------------------------
    2009/08/15 13:57:32 :: wicd is version 1.6.2 436
    2009/08/15 13:57:32 :: setting backend to external
    2009/08/15 13:57:32 :: trying to load backend external
    2009/08/15 13:57:32 :: successfully loaded backend external
    2009/08/15 13:57:32 :: trying to load backend external
    2009/08/15 13:57:32 :: successfully loaded backend external
    2009/08/15 13:57:32 :: Automatically detected wireless interface eth0
    2009/08/15 13:57:32 :: setting wireless interface eth1
    2009/08/15 13:57:32 :: automatically detected wired interface eth1
    2009/08/15 13:57:32 :: setting wired interface eth0
    2009/08/15 13:57:32 :: setting wpa driver wext
    2009/08/15 13:57:32 :: setting use global dns to False
    2009/08/15 13:57:32 :: setting global dns
    2009/08/15 13:57:32 :: global dns servers are None None None
    2009/08/15 13:57:32 :: domain is None
    2009/08/15 13:57:32 :: search domain is None
    2009/08/15 13:57:32 :: setting automatically reconnect when connection drops True
    2009/08/15 13:57:32 :: Setting dhcp client to 0
    2009/08/15 13:57:32 :: Wireless configuration file found...
    2009/08/15 13:57:32 :: Wired configuration file found...
    2009/08/15 13:57:32 :: chmoding configuration files 0600...
    2009/08/15 13:57:32 :: chowning configuration files root:root...
    2009/08/15 13:57:32 :: Using wireless interface...eth1
    2009/08/15 13:57:32 :: Using wired interface...eth0
    2009/08/15 13:57:38 :: Autoconnecting...
    2009/08/15 13:57:38 :: Putting interface down
    2009/08/15 13:57:38 :: Attempting to autoconnect with wired interface...
    2009/08/15 13:57:38 :: Releasing DHCP leases...
    2009/08/15 13:57:38 :: Setting false IP...
    2009/08/15 13:57:38 :: Flushing the routing table...
    2009/08/15 13:57:38 :: Putting interface up...
    2009/08/15 13:57:38 :: Running DHCP
    2009/08/15 13:57:38 :: dhcpcd: version 5.0.6 starting
    2009/08/15 13:57:38 ::
    2009/08/15 13:57:38 :: dhcpcd: eth0: rebinding lease of 192.168.0.193
    2009/08/15 13:57:38 ::
    2009/08/15 13:57:48 :: dhcpcd: eth0: broadcasting for a lease
    2009/08/15 13:57:48 ::
    2009/08/15 13:58:08 :: dhcpcd: timed out
    2009/08/15 13:58:08 ::
    2009/08/15 13:58:08 :: DHCP connection failed
    2009/08/15 13:58:08 :: exiting connection thread
    2009/08/15 13:58:08 :: Sending connection attempt result dhcp_failed
    2009/08/15 13:58:10 :: No wired connection present, attempting to autoconnect to wireless network
    2009/08/15 13:58:10 :: Unable to autoconnect, you'll have to manually connect
    2009/08/15 13:58:46 :: Putting interface down
    2009/08/15 13:58:46 :: Releasing DHCP leases...
    2009/08/15 13:58:46 :: Setting false IP...
    2009/08/15 13:58:46 :: Flushing the routing table...
    2009/08/15 13:58:46 :: Putting interface up...
    2009/08/15 13:58:46 :: Running DHCP
    2009/08/15 13:58:46 :: dhcpcd: version 5.0.6 starting
    2009/08/15 13:58:46 ::
    2009/08/15 13:58:46 :: dhcpcd: eth0: rebinding lease of 192.168.0.193
    2009/08/15 13:58:46 ::
    2009/08/15 13:58:56 :: dhcpcd: eth0: broadcasting for a lease
    2009/08/15 13:58:56 ::
    2009/08/15 13:59:16 :: dhcpcd: timed out
    2009/08/15 13:59:16 ::
    2009/08/15 13:59:16 :: DHCP connection failed
    2009/08/15 13:59:16 :: exiting connection thread
    2009/08/15 13:59:16 :: Sending connection attempt result dhcp_failed
    2009/08/15 14:10:08 :: Daemon going down, killing wicd-monitor...
    2009/08/15 14:10:08 :: Removing PID file...
    2009/08/15 14:10:08 :: Shutting down...
    2009/08/15 14:10:59 :: ---------------------------
    2009/08/15 14:10:59 :: wicd initializing...
    2009/08/15 14:10:59 :: ---------------------------
    2009/08/15 14:10:59 :: wicd is version 1.6.2 436
    2009/08/15 14:10:59 :: setting backend to external
    2009/08/15 14:10:59 :: trying to load backend external
    2009/08/15 14:10:59 :: successfully loaded backend external
    2009/08/15 14:10:59 :: trying to load backend external
    2009/08/15 14:10:59 :: successfully loaded backend external
    2009/08/15 14:10:59 :: Automatically detected wireless interface eth0
    2009/08/15 14:10:59 :: setting wireless interface eth1
    2009/08/15 14:10:59 :: automatically detected wired interface eth1
    2009/08/15 14:10:59 :: setting wired interface eth0
    2009/08/15 14:10:59 :: setting wpa driver wext
    2009/08/15 14:10:59 :: setting use global dns to False
    2009/08/15 14:10:59 :: setting global dns
    2009/08/15 14:10:59 :: global dns servers are None None None
    2009/08/15 14:10:59 :: domain is None
    2009/08/15 14:10:59 :: search domain is None
    2009/08/15 14:10:59 :: setting automatically reconnect when connection drops True
    2009/08/15 14:10:59 :: Setting dhcp client to 0
    2009/08/15 14:10:59 :: Wireless configuration file found...
    2009/08/15 14:10:59 :: Wired configuration file found...
    2009/08/15 14:10:59 :: chmoding configuration files 0600...
    2009/08/15 14:10:59 :: chowning configuration files root:root...
    2009/08/15 14:10:59 :: Using wireless interface...eth1
    2009/08/15 14:10:59 :: Using wired interface...eth0
    2009/08/15 14:11:06 :: Autoconnecting...
    2009/08/15 14:11:09 :: Attempting to autoconnect with wired interface...
    2009/08/15 14:11:09 :: Putting interface down
    2009/08/15 14:11:09 :: Releasing DHCP leases...
    2009/08/15 14:11:09 :: Setting false IP...
    2009/08/15 14:11:09 :: Flushing the routing table...
    2009/08/15 14:11:09 :: Putting interface up...
    2009/08/15 14:11:09 :: Running DHCP
    2009/08/15 14:11:09 :: dhcpcd: version 5.0.6 starting
    2009/08/15 14:11:09 ::
    2009/08/15 14:11:09 :: dhcpcd: eth0: rebinding lease of 192.168.0.193
    2009/08/15 14:11:09 ::
    2009/08/15 14:11:19 :: dhcpcd: eth0: broadcasting for a lease
    2009/08/15 14:11:19 ::
    2009/08/15 14:11:39 :: dhcpcd: timed out
    2009/08/15 14:11:39 ::
    2009/08/15 14:11:39 :: DHCP connection failed
    2009/08/15 14:11:39 :: exiting connection thread
    2009/08/15 14:11:41 :: No wired connection present, attempting to autoconnect to wireless network
    2009/08/15 14:11:41 :: Unable to autoconnect, you'll have to manually connect
    2009/08/15 14:11:41 :: Sending connection attempt result dhcp_failed
    2009/08/15 14:13:00 :: Daemon going down, killing wicd-monitor...
    2009/08/15 14:13:00 :: Removing PID file...
    2009/08/15 14:13:00 :: Shutting down...
    2009/08/15 14:13:50 :: ---------------------------
    2009/08/15 14:13:50 :: wicd initializing...
    2009/08/15 14:13:50 :: ---------------------------
    2009/08/15 14:13:50 :: wicd is version 1.6.2 436
    2009/08/15 14:13:50 :: setting backend to external
    2009/08/15 14:13:50 :: trying to load backend external
    2009/08/15 14:13:50 :: successfully loaded backend external
    2009/08/15 14:13:50 :: trying to load backend external
    2009/08/15 14:13:50 :: successfully loaded backend external
    2009/08/15 14:13:51 :: Automatically detected wireless interface eth1
    2009/08/15 14:13:51 :: setting wireless interface eth1
    2009/08/15 14:13:51 :: automatically detected wired interface eth0
    2009/08/15 14:13:51 :: setting wired interface eth0
    2009/08/15 14:13:51 :: setting wpa driver wext
    2009/08/15 14:13:51 :: setting use global dns to False
    2009/08/15 14:13:51 :: setting global dns
    2009/08/15 14:13:51 :: global dns servers are None None None
    2009/08/15 14:13:51 :: domain is None
    2009/08/15 14:13:51 :: search domain is None
    2009/08/15 14:13:51 :: setting automatically reconnect when connection drops True
    2009/08/15 14:13:51 :: Setting dhcp client to 0
    2009/08/15 14:13:51 :: Wireless configuration file found...
    2009/08/15 14:13:51 :: Wired configuration file found...
    2009/08/15 14:13:51 :: chmoding configuration files 0600...
    2009/08/15 14:13:51 :: chowning configuration files root:root...
    2009/08/15 14:13:51 :: Using wireless interface...eth1
    2009/08/15 14:13:51 :: Using wired interface...eth0
    2009/08/15 14:13:57 :: Autoconnecting...
    2009/08/15 14:13:59 :: No wired connection present, attempting to autoconnect to wireless network
    2009/08/15 14:14:00 :: trying to automatically connect to...101
    2009/08/15 14:14:00 :: Connecting to wireless network 101
    2009/08/15 14:14:00 :: Putting interface down
    2009/08/15 14:14:00 :: Releasing DHCP leases...
    2009/08/15 14:14:00 :: Setting false IP...
    2009/08/15 14:14:00 :: Stopping wpa_supplicant
    2009/08/15 14:14:00 :: Flushing the routing table...
    2009/08/15 14:14:00 :: Putting interface up...
    2009/08/15 14:14:00 :: Generating psk...
    2009/08/15 14:14:01 :: Attempting to authenticate...
    2009/08/15 14:14:11 :: Running DHCP
    2009/08/15 14:14:11 :: dhcpcd: version 5.0.6 starting
    2009/08/15 14:14:11 ::
    2009/08/15 14:14:11 :: dhcpcd: eth1: rebinding lease of 192.168.0.183
    2009/08/15 14:14:11 ::
    2009/08/15 14:14:11 :: dhcpcd: eth1: acknowledged 192.168.0.183 from 192.168.0.1
    2009/08/15 14:14:11 ::
    2009/08/15 14:14:11 :: dhcpcd: eth1: checking for 192.168.0.183
    2009/08/15 14:14:11 ::
    2009/08/15 14:14:15 :: dhcpcd: eth1: leased 192.168.0.183 for 86400 seconds
    2009/08/15 14:14:15 ::
    2009/08/15 14:14:15 :: dhcpcd: forking to background
    2009/08/15 14:14:15 ::
    2009/08/15 14:14:15 ::
    2009/08/15 14:14:15 :: DHCP connection successful
    2009/08/15 14:14:15 :: Connecting thread exiting.
    2009/08/15 14:14:17 :: Sending connection attempt result Success
    2009/08/15 14:14:17 :: Autoconnecting...
    2009/08/15 14:14:17 :: No wired connection present, attempting to autoconnect to wireless network
    2009/08/15 14:14:17 :: trying to automatically connect to...102
    2009/08/15 14:14:17 :: Connecting to wireless network 102
    2009/08/15 14:14:17 :: Putting interface down
    2009/08/15 14:14:17 :: Releasing DHCP leases...
    2009/08/15 14:14:18 :: Setting false IP...
    2009/08/15 14:14:18 :: Stopping wpa_supplicant
    2009/08/15 14:14:18 :: Flushing the routing table...
    2009/08/15 14:14:18 :: Putting interface up...
    2009/08/15 14:14:18 :: Generating psk...
    2009/08/15 14:14:18 :: Attempting to authenticate...
    2009/08/15 14:14:19 :: Running DHCP
    2009/08/15 14:14:19 :: dhcpcd: version 5.0.6 starting
    2009/08/15 14:14:19 ::
    2009/08/15 14:14:19 :: dhcpcd: eth1: rebinding lease of 192.168.0.183
    2009/08/15 14:14:19 ::
    2009/08/15 14:14:19 :: dhcpcd: eth1: acknowledged 192.168.0.183 from 192.168.0.1
    2009/08/15 14:14:19 ::
    2009/08/15 14:14:19 :: dhcpcd: eth1: checking for 192.168.0.183
    2009/08/15 14:14:19 ::
    2009/08/15 14:14:24 :: dhcpcd: eth1: leased 192.168.0.183 for 86400 seconds
    2009/08/15 14:14:24 ::
    2009/08/15 14:14:24 :: dhcpcd: forking to background
    2009/08/15 14:14:24 ::
    2009/08/15 14:14:24 ::
    2009/08/15 14:14:24 :: DHCP connection successful
    2009/08/15 14:14:24 :: Connecting thread exiting.
    2009/08/15 14:14:29 :: Sending connection attempt result Success
    2009/08/15 14:15:02 :: Daemon going down, killing wicd-monitor...
    2009/08/15 14:15:02 :: Removing PID file...
    2009/08/15 14:15:02 :: Shutting down...
    2009/08/15 14:15:52 :: ---------------------------
    2009/08/15 14:15:52 :: wicd initializing...
    2009/08/15 14:15:52 :: ---------------------------
    2009/08/15 14:15:52 :: wicd is version 1.6.2 436
    2009/08/15 14:15:52 :: setting backend to external
    2009/08/15 14:15:52 :: trying to load backend external
    2009/08/15 14:15:52 :: successfully loaded backend external
    2009/08/15 14:15:52 :: trying to load backend external
    2009/08/15 14:15:52 :: successfully loaded backend external
    2009/08/15 14:15:52 :: Automatically detected wireless interface eth0
    2009/08/15 14:15:52 :: setting wireless interface eth1
    2009/08/15 14:15:52 :: automatically detected wired interface eth1
    2009/08/15 14:15:52 :: setting wired interface eth0
    2009/08/15 14:15:52 :: setting wpa driver wext
    2009/08/15 14:15:52 :: setting use global dns to False
    2009/08/15 14:15:52 :: setting global dns
    2009/08/15 14:15:52 :: global dns servers are None None None
    2009/08/15 14:15:52 :: domain is None
    2009/08/15 14:15:52 :: search domain is None
    2009/08/15 14:15:52 :: setting automatically reconnect when connection drops True
    2009/08/15 14:15:52 :: Setting dhcp client to 0
    2009/08/15 14:15:52 :: Wireless configuration file found...
    2009/08/15 14:15:52 :: Wired configuration file found...
    2009/08/15 14:15:52 :: chmoding configuration files 0600...
    2009/08/15 14:15:52 :: chowning configuration files root:root...
    2009/08/15 14:15:52 :: Using wireless interface...eth1
    2009/08/15 14:15:52 :: Using wired interface...eth0
    2009/08/15 14:15:59 :: Autoconnecting...
    2009/08/15 14:16:02 :: Attempting to autoconnect with wired interface...
    2009/08/15 14:16:02 :: Putting interface down
    2009/08/15 14:16:02 :: Releasing DHCP leases...
    2009/08/15 14:16:02 :: Setting false IP...
    2009/08/15 14:16:02 :: Flushing the routing table...
    2009/08/15 14:16:02 :: Putting interface up...
    2009/08/15 14:16:02 :: Running DHCP
    2009/08/15 14:16:02 :: dhcpcd: version 5.0.6 starting
    2009/08/15 14:16:02 ::
    2009/08/15 14:16:02 :: dhcpcd: eth0: rebinding lease of 192.168.0.193
    2009/08/15 14:16:02 ::
    2009/08/15 14:16:12 :: dhcpcd: eth0: broadcasting for a lease
    2009/08/15 14:16:12 ::
    2009/08/15 14:16:32 :: dhcpcd: timed out
    2009/08/15 14:16:32 ::
    2009/08/15 14:16:32 :: DHCP connection failed
    2009/08/15 14:16:32 :: exiting connection thread
    2009/08/15 14:16:34 :: No wired connection present, attempting to autoconnect to wireless network
    2009/08/15 14:16:34 :: Unable to autoconnect, you'll have to manually connect
    2009/08/15 14:16:34 :: Sending connection attempt result dhcp_failed
    2009/08/15 14:17:02 :: Daemon going down, killing wicd-monitor...
    2009/08/15 14:17:02 :: Removing PID file...
    2009/08/15 14:17:02 :: Shutting down...
    2009/08/15 15:39:03 :: ---------------------------
    2009/08/15 15:39:03 :: wicd initializing...
    2009/08/15 15:39:03 :: ---------------------------
    2009/08/15 15:39:03 :: wicd is version 1.6.2 436
    2009/08/15 15:39:03 :: setting backend to external
    2009/08/15 15:39:03 :: trying to load backend external
    2009/08/15 15:39:03 :: successfully loaded backend external
    2009/08/15 15:39:03 :: trying to load backend external
    2009/08/15 15:39:03 :: successfully loaded backend external
    2009/08/15 15:39:03 :: Automatically detected wireless interface eth0
    2009/08/15 15:39:03 :: setting wireless interface eth1
    2009/08/15 15:39:03 :: automatically detected wired interface eth1
    2009/08/15 15:39:03 :: setting wired interface eth0
    2009/08/15 15:39:03 :: setting wpa driver wext
    2009/08/15 15:39:03 :: setting use global dns to False
    2009/08/15 15:39:03 :: setting global dns
    2009/08/15 15:39:03 :: global dns servers are None None None
    2009/08/15 15:39:03 :: domain is None
    2009/08/15 15:39:03 :: search domain is None
    2009/08/15 15:39:03 :: setting automatically reconnect when connection drops True
    2009/08/15 15:39:03 :: Setting dhcp client to 0
    2009/08/15 15:39:03 :: Wireless configuration file found...
    2009/08/15 15:39:03 :: Wired configuration file found...
    2009/08/15 15:39:03 :: chmoding configuration files 0600...
    2009/08/15 15:39:03 :: chowning configuration files root:root...
    2009/08/15 15:39:03 :: Using wireless interface...eth1
    2009/08/15 15:39:03 :: Using wired interface...eth0
    2009/08/15 15:39:10 :: Autoconnecting...
    2009/08/15 15:39:13 :: Attempting to autoconnect with wired interface...
    2009/08/15 15:39:13 :: Putting interface down
    2009/08/15 15:39:13 :: Releasing DHCP leases...
    2009/08/15 15:39:13 :: Setting false IP...
    2009/08/15 15:39:13 :: Flushing the routing table...
    2009/08/15 15:39:13 :: Putting interface up...
    2009/08/15 15:39:13 :: Running DHCP
    2009/08/15 15:39:13 :: dhcpcd: version 5.0.6 starting
    2009/08/15 15:39:13 ::
    2009/08/15 15:39:13 :: dhcpcd: eth0: rebinding lease of 192.168.0.193
    2009/08/15 15:39:13 ::
    2009/08/15 15:39:23 :: dhcpcd: eth0: broadcasting for a lease
    2009/08/15 15:39:23 ::
    2009/08/15 15:39:43 :: dhcpcd: timed out
    2009/08/15 15:39:43 ::
    2009/08/15 15:39:43 :: DHCP connection failed
    2009/08/15 15:39:43 :: exiting connection thread
    2009/08/15 15:39:45 :: No wired connection present, attempting to autoconnect to wireless network
    2009/08/15 15:39:45 :: Unable to autoconnect, you'll have to manually connect
    2009/08/15 15:39:45 :: Sending connection attempt result dhcp_failed
    2009/08/15 15:41:46 :: Daemon going down, killing wicd-monitor...
    2009/08/15 15:41:46 :: Removing PID file...
    2009/08/15 15:41:46 :: Shutting down...
    2009/08/15 15:42:33 :: ---------------------------
    2009/08/15 15:42:33 :: wicd initializing...
    2009/08/15 15:42:33 :: ---------------------------
    2009/08/15 15:42:33 :: wicd is version 1.6.2 436
    2009/08/15 15:42:33 :: setting backend to external
    2009/08/15 15:42:33 :: trying to load backend external
    2009/08/15 15:42:33 :: successfully loaded backend external
    2009/08/15 15:42:33 :: trying to load backend external
    2009/08/15 15:42:33 :: successfully loaded backend external
    2009/08/15 15:42:33 :: Automatically detected wireless interface eth0
    2009/08/15 15:42:33 :: setting wireless interface eth1
    2009/08/15 15:42:33 :: automatically detected wired interface eth1
    2009/08/15 15:42:33 :: setting wired interface eth0
    2009/08/15 15:42:33 :: setting wpa driver wext
    2009/08/15 15:42:33 :: setting use global dns to False
    2009/08/15 15:42:33 :: setting global dns
    2009/08/15 15:42:33 :: global dns servers are None None None
    2009/08/15 15:42:33 :: domain is None
    2009/08/15 15:42:33 :: search domain is None
    2009/08/15 15:42:33 :: setting automatically reconnect when connection drops True
    2009/08/15 15:42:33 :: Setting dhcp client to 0
    2009/08/15 15:42:33 :: Wireless configuration file found...
    2009/08/15 15:42:33 :: Wired configuration file found...
    2009/08/15 15:42:33 :: chmoding configuration files 0600...
    2009/08/15 15:42:33 :: chowning configuration files root:root...
    2009/08/15 15:42:33 :: Using wireless interface...eth1
    2009/08/15 15:42:33 :: Using wired interface...eth0
    2009/08/15 15:42:39 :: Autoconnecting...
    2009/08/15 15:42:42 :: Attempting to autoconnect with wired interface...
    2009/08/15 15:42:42 :: Putting interface down
    2009/08/15 15:42:42 :: Releasing DHCP leases...
    2009/08/15 15:42:42 :: Setting false IP...
    2009/08/15 15:42:42 :: Flushing the routing table...
    2009/08/15 15:42:42 :: Putting interface up...
    2009/08/15 15:42:42 :: Running DHCP
    2009/08/15 15:42:42 :: dhcpcd: version 5.0.6 starting
    2009/08/15 15:42:42 ::
    2009/08/15 15:42:42 :: dhcpcd: eth0: rebinding lease of 192.168.0.193
    2009/08/15 15:42:42 ::
    2009/08/15 15:42:52 :: dhcpcd: eth0: broadcasting for a lease
    2009/08/15 15:42:52 ::
    2009/08/15 15:43:12 :: dhcpcd: timed out
    2009/08/15 15:43:12 ::
    2009/08/15 15:43:12 :: DHCP connection failed
    2009/08/15 15:43:12 :: exiting connection thread
    2009/08/15 15:43:14 :: No wired connection present, attempting to autoconnect to wireless network
    2009/08/15 15:43:14 :: Unable to autoconnect, you'll have to manually connect
    2009/08/15 15:43:14 :: Sending connection attempt result dhcp_failed
    2009/08/15 15:44:27 :: Daemon going down, killing wicd-monitor...
    2009/08/15 15:44:27 :: Removing PID file...
    2009/08/15 15:44:27 :: Shutting down...
    2009/08/15 15:44:48 :: ---------------------------
    2009/08/15 15:44:48 :: wicd initializing...
    2009/08/15 15:44:48 :: ---------------------------
    2009/08/15 15:44:48 :: wicd is version 1.6.2 436
    2009/08/15 15:44:48 :: setting backend to external
    2009/08/15 15:44:48 :: trying to load backend external
    2009/08/15 15:44:48 :: successfully loaded backend external
    2009/08/15 15:44:48 :: trying to load backend external
    2009/08/15 15:44:48 :: successfully loaded backend external
    2009/08/15 15:44:48 :: Automatically detected wireless interface eth0
    2009/08/15 15:44:48 :: setting wireless interface eth1
    2009/08/15 15:44:48 :: automatically detected wired interface eth1
    2009/08/15 15:44:48 :: setting wired interface eth0
    2009/08/15 15:44:48 :: setting wpa driver wext
    2009/08/15 15:44:48 :: setting use global dns to False
    2009/08/15 15:44:48 :: setting global dns
    2009/08/15 15:44:48 :: global dns servers are None None None
    2009/08/15 15:44:48 :: domain is None
    2009/08/15 15:44:48 :: search domain is None
    2009/08/15 15:44:48 :: setting automatically reconnect when connection drops True
    2009/08/15 15:44:48 :: Setting dhcp client to 0
    2009/08/15 15:44:48 :: Wireless configuration file found...
    2009/08/15 15:44:48 :: Wired configuration file found...
    2009/08/15 15:44:48 :: chmoding configuration files 0600...
    2009/08/15 15:44:48 :: chowning configuration files root:root...
    2009/08/15 15:44:48 :: Using wireless interface...eth1
    2009/08/15 15:44:48 :: Using wired interface...eth0
    2009/08/15 15:44:58 :: trying to load backend ioctl
    2009/08/15 15:44:58 :: WARNING: python-iwscan not found, falling back to using iwlist scan.
    2009/08/15 15:44:58 :: WARNING: python-wpactrl not found, falling back to using wpa_cli.
    2009/08/15 15:44:58 :: trying to load backend external
    2009/08/15 15:45:57 :: Autoconnecting...
    2009/08/15 15:45:57 :: Putting interface down
    2009/08/15 15:45:57 :: Attempting to autoconnect with wired interface...
    2009/08/15 15:45:57 :: Releasing DHCP leases...
    2009/08/15 15:45:57 :: Setting false IP...
    2009/08/15 15:45:57 :: Flushing the routing table...
    2009/08/15 15:45:57 :: Putting interface up...
    2009/08/15 15:45:57 :: Running DHCP
    2009/08/15 15:45:57 :: dhcpcd: version 5.0.6 starting
    2009/08/15 15:45:57 ::
    2009/08/15 15:45:57 :: dhcpcd: eth0: rebinding lease of 192.168.0.193
    2009/08/15 15:45:57 ::
    2009/08/15 15:46:07 :: dhcpcd: eth0: broadcasting for a lease
    2009/08/15 15:46:07 ::
    2009/08/15 15:46:27 :: dhcpcd: timed out
    2009/08/15 15:46:27 ::
    2009/08/15 15:46:27 :: DHCP connection failed
    2009/08/15 15:46:27 :: exiting connection thread
    2009/08/15 15:46:29 :: No wired connection present, attempting to autoconnect to wireless network
    2009/08/15 15:46:29 :: Unable to autoconnect, you'll have to manually connect
    2009/08/15 15:46:29 :: Sending connection attempt result dhcp_failed

    Was able to boot this weekend and did an update which updated the kernel.  Rebooted and there was no network.  Rebooted again and no network... rebooted again and... had network!?  I tried changing wicd to use dhclient only and did the triple reboot test again and it didn't change anything... randomly working network... same with dhcpcd.
    So it appears to be a dhcp timeout issue however it makes no sense because before the update a couple weeks ago it was working every time with no hiccup.  Am I not providing enough information that will aid in anyone helping me figure this out?

  • How to set up WRT54GS so the wired and wireless connections both work?

    I have a DSL line in to a Motorola modem.
    The modem is connected to the WRT54GS with an ethernet cable.
    When I connect my computers directly into the WRT54GS with an ethernet cable (there are four connection spots at the back of the box), I cannot go to the internet.  I have 3 computers plugged in, but none of them connect via Ethernet..
    Is there a setting on the router so that I can use the router for both wired and wireless connectivity?
    Added info: I tried to connect directly from the computer to the modem, but again, got no connectivity.  When I "chatted" with ATT, they told me the modem is set to "bridge", and that I could connect only one device.  I don't want to change this setting because I want to use the router for the wireless capability.  Besides which, I have more than one computer to connect to the internet.
    How come I cannot just plug in and go?  
    My firmware version is v2.07.1. 
    I don't know how to find out what hardware version I have.
    Other info is "DirectEthernet Connection, Speed: 100.0 Mbps, Signal Strength: Excellent, Status: Connected"
    Also "1394 Connection 3, Speed: 400.0 Mbps, Status: Connected"  
    I don't know what that's for, but thought it might prove useful to those of you who are knowledgeable about such things.
    Wireless is ok, but if I'm sitting right next to the router, I'd like to connect with Ethernet and take advantage of the better speed, etc.
    Thanks in advance.

    Just click this link.

  • Help with HP Laser CM1415fnw wired and wireless setup

    Hello all,
    I am have have trouble with both wired and wireless. It will only let me do one or the other. Is there a way i can do both?
    everything works if i am wired or wireless but, the user wants to be able to use both.
    Any help would be great.
    This question was solved.
    View Solution.

    Sorry, both cannot be enabled by design.  That said, devices on a network do not care how others are connected.  You can print from a wireless connection to a wired (Ethernet) printer and v/v.
    Say thanks by clicking "Kudos" "thumbs up" in the post that helped you.
    I am employed by HP

  • 802.1x Authentication on Wired and Wireless LAN

    I have successfully configured 802.1x authentication on wired and wireless Lan. We have Cisco Switches, ACS SE and Windows AD.
    But i have one issue regarding the Single Sign on while authentication using the 802.1x with Windows Active directory the users that are login first time not able to logon but the users that have their profiles already existed in their PC then there is no issue and they successfully authenticated and login easily.
    Is there any way of login successfully for the users first time using 802.1x authentication with Windows AD like a Single Sign On?

    We ran into the same situation from time to time. We implemented 802.1x authentication using the Cisco Secure Services Client (SSC) on the windows hosts.
    At the beginning we were completly unable to logon on the maschines where no locally stored windows profile exists. After change to timeout to authenticate at the network in the SSC options we are able to logon to the network and also be authenticated by the domain controller.
    Sadly this works out often as a timing issue. Most times the user needs to try a couple of times. At the moment, I'm also very interessted in a good way to avoid this (as it seems to be) racecondition.
    Hope that someone else has any clue?

Maybe you are looking for