Wired PC and Wireless Laptops

We just got a wireless router for the cable internet we have for a wired desktop. Our laptops are picking up the internet just fine. But how in the world do you set up a network with a wired desktop and the two laptops? We were told we could access files and printers from the desktop using the laptops but no one will expand on how to do that. Do you have to actually hardwire the laptops to the router or something in order to create a network between the wired desktop and wireless laptops? The guys at the computer store were standing there offering to charge us $200 to solve the problem. Can someone please help?

The desktop does have an ethernet port and is currently connected to the internet via that port. However, every time I try to connect the desktop to another computer by setting up a new connection, it doesn't give me the option of using the router as the hub to connect all my computers together. The microsoft website talks mainly about wiring all the comps directly to the computer but I'm trying to be able to access the desktop wirelessly from the laptop. the room the desktop is in is way way too hot to work in comfortably, so we were hoping to access it from an air conditioned room via the laptop. I'm just at a loss.

Similar Messages

  • Braodband - Wired PC and Wireless Laptop

    Hello
    I've a question about wireless broadband.
    My sister currently uses BT broadband thru her PC connected via a wired router which is quite old (the PC that is...doesn't have a wireless card) but is quite happy with it and doesn't want to try installing a card or buy a new PC.
    However, daughter # 2 wants a laptop and wants to connect wirelessly, via a wireless router. I've had a quick chat with a BT guy and it seems it's possible to connect both. However, I forgot to ask how this happens. Is the broadband connection effectively split? 1 wire going to the PC router and 1 going to the wireless router?
    Are there extra expenses involved (apart from the wireless router) and major wiring required?
    Thanks for your help.
    Cheers,
    Dave
    Solved!
    Go to Solution.

    I have the latest home hub from bt. I got it free like most when I renewed my contract for broadband; you need to ask or you won't get. My desktop is connected to one of four ethernet cable connectors round the back, so you would need to locate it pretty close to your desktop. My laptop connects by wifi. No extra cable or splitters needed. The laptop, which should already have a wifi card, will look for networks and list the ones it picks up. You select which one you want to connect to and type in the wireless key and away you go. Hope this helps.

  • Wired PC and wireless laptops not communicating

    Hey everyone, I recently switched from a wired router to a wireless router, the WRT54g V8.  Before the switch my PC (win XP srvpck2), 2 laptops (win vista)  and printer were all visible on the network.  All three computers had access to each other. 
    Life was good.
    Then the switch came.  Now the PC is wired to the new router and the two laptops are wireless.  The printer was wired up to the old and new router but now with the new router I had to hook it back up to just the PC.
    All the computers have internet access.  The PC is stand alone right now but the two laptops can see each other on the network and share info.
    I am hoping that someone knows how to get all my computers and the printer back together on a network.

    hi... logon to router's setup page and try reducing MTU to 1365, click on wireless tab and try changing wireless channel to 11, click on advanced wireless settings try changing fragmentation and RTS threshold to 2304, make sure that AP isolation is off...also try upgrading latest firmware on the router...try disabling personal firewall and antivirus software on the computer...let me know the results. 

  • Wired PC and Wireless PC cannot connect to each other

    Hi, I recently bought a new Linksys WRT54G router and I was able to succesfully connect my wired desktop pc and my wireless laptop to the internet through the router. My only concern is that I want my laptop to share its files through my desktop pc and vice versa, however, it seems it does not work. Both pcs cannot connect to each other. Any suggestions will do. Thanks and Good Luck.

    This may be a file sharing problem about which many have asked. You have an additional problem. File sharing between wireless and wired. I have a VPN connection where the wireless can see the wired network (subnet) but the wired cannot see the wireless.
    The problem remains: why is the wireless network remaining "invisible" unpingable -- not shared?
    I know this is not a answer, just a plea for a further answer from some networking genius logging into to the forum.
    Message Edited by bodywise on 08-04-2007 11:42 PM

  • CSA and Wireless Laptops

    Is it possible to build a CSA rule to stop a wireless laptop from attaching to a wireless network with the SSID of "guest"??
    If so how??

    The short answer is yes, CSA can be configured such to limit SSIDs hosts can connect to.
    What version of CSA are you running?
    Look at this doc, it rocks for CSA and wireless.
    http://www.cisco.com/application/pdf/en/us/guest/netsol/ns386/c649/ccmigration_09186a00808753b3.pdf
    Right around page 29.
    Mike

  • HP CP1525nw - Connect via wired network and wireless ad hoc?

    At my job we have our HP 1525nw printer connected into the network printserver via ethernet cable.  The printer has its own IP address setup on the network.   
    With support for XP computers ceasing, a copule of computers will be cut off/blocked from the job's network.  One computer is close enough where we can make a USB connection to print.  Another is located on another bench.  Furthermore, the one that is further away from the printer also can't be upgraded to a compliant Windows OS due to incompatibility with specialized software used to operate equipment hooked up to this computer. 
    Is it at all possible for this wired network printer to also be setup to print wireless via an ad hoc connection?  The idea was perhaps we could install a wireless card on thix XP computer and  print wirelessly via a direct connection to the printer, avoiding having to connect to it via the wired network at all.  But it is sounding like this wouldn't be possible.  Looking for a direct answer before I start shopping around for a wireless PCI card. 
    This question was solved.
    View Solution.

    From other posts I have read, I think the CP1525 can be either ethernet or wireless not both at the same time.  That will prevent you from setting up with an adhoc network the way you described.
    You might try an inexpensive wireless router with a build in print server attached to the usb port.  then add wireless USB wireless dongles to the XP computers.  Be sure you make sure that the wireless dongles support XP. Also for security purposes you will want to leave the wireless router disconnected from your network.
    If your fairly tecky and you don't mind playing a bit you could check your local thrift store for a used router with a print server.  For printing you don't need the fastest wireless available.  Just make sure it is a b/g router (not a B only one).
    Treefrog
    Please mark the post that solves your problem as "Accepted Solution"
    Sometimes it takes several posts back and forth to get to a solution - please be patient.
    I am employed by HP

  • Time Capsule and Tiger with wired G5 and wireless PowerBook

    Do I want to create a new wireless network with TC as new base station or just add it to my existing network? Are there performance differences? I currently have the phone line connected to my wireless modem (2Wire812), then the modem connected to the internet WAN port on TC, G5 via ethernet to a ethernet port on TC. Everything is working and I have internet access from both the G5 and PowerBook, just wondering if this is the best wiring setup.
    Second question ... I will be using Backup to back up files. Where do I find TC to back up to? I don't see it in the destinations list. And for that matter, where do I find TC in general in the finder?
    Any help would be appreciated.
    Keith

    To connect to the TC, you'll also see it under shared, or go to network from the finder. You can open it up just like an external hard drive.
    You can also simply plug in an ethernet cable to the back of the TC, and then to your PowerBook for direct link. Apple recommends this for the first backup, since it's faster, unless you are on just an 802.11n network (not g, or earlier). I just setup a dual-band network so my TC and MacBook can talk to each other at 802.11n.

  • Native VLAN on wired switch and wireless AP

    On our 3560g switch we have g0/15 set up as a trunk to connect our wireless AP.
    Port Mode Encapsulation Status Native vlan
    Gi0/15 on 802.1q trunking 35
    Port Vlans allowed on trunk
    Gi0/15 1-4094
    Port Vlans allowed and active in management domain
    Gi0/15 1,10-14,18,20,22,30,35
    Port Vlans in spanning tree forwarding state and not pruned
    Gi0/15 1,10-14,18,20,22,30,35
    On my AP I have the native VLAN as 1.
    From my reading I found that the AP and the switch port should have the same Native vlan on both ends of the trunk. Well my access point will not work unless the AP trunk is on 1 and the switch is on 35. Any ideas?

    dot11 ssid guestwifi
    vlan 20
    authentication open eap eap_methods
    authentication network-eap eap_methods
    authentication key-management wpa
    dot11 ssid nwifi
    vlan 35
    authentication open eap eap_methods
    authentication network-eap eap_methods
    authentication key-management wpa
    guest-mode
    dot11 arp-cache optional
    c
    bridge irb
    interface Dot11Radio0
    no ip address
    no ip route-cache
    encryption mode ciphers aes-ccm tkip
    encryption vlan 35 mode ciphers aes-ccm tkip
    encryption vlan 1 mode ciphers aes-ccm tkip
    encryption vlan 20 mode ciphers aes-ccm tkip
    ssid guestwifi
    ssid raydonwifi
    mbssid
    speed basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0 12.0 18.0 24.0 36.0 48.0 54.0
    channel 2462
    station-role root
    no dot11 extension aironet
    interface Dot11Radio0.1
    encapsulation dot1Q 1 native
    no ip route-cache
    bridge-group 1
    bridge-group 1 block-unknown-source
    no bridge-group 1 source-learning
    no bridge-group 1 unicast-flooding
    bridge-group 1 spanning-disabled
    interface Dot11Radio0.20
    encapsulation dot1Q 20
    no ip route-cache
    bridge-group 20
    bridge-group 20 block-unknown-source
    no bridge-group 20 source-learning
    no bridge-group 20 unicast-flooding
    bridge-group 20 spanning-disabled
    interface Dot11Radio0.35
    encapsulation dot1Q 35
    no ip route-cache
    bridge-group 35
    bridge-group 35 block-unknown-source
    no bridge-group 35 source-learning
    no bridge-group 35 unicast-flooding
    bridge-group 35 spanning-disabled
    interface Dot11Radio1
    no ip address
    no ip route-cache
    shutdown
    encryption mode ciphers tkip
    speed basic-6.0 9.0 basic-12.0 18.0 basic-24.0 36.0 48.0 54.0
    channel 5200
    station-role root bridge
    antenna receive right
    antenna transmit right
    bridge-group 1
    bridge-group 1 spanning-disabled
    interface FastEthernet0
    no ip address
    no ip route-cache
    duplex auto
    speed auto
    interface FastEthernet0.1
    encapsulation dot1Q 1 native
    no ip route-cache
    bridge-group 1
    interface FastEthernet0.20
    encapsulation dot1Q 20
    no ip route-cache
    bridge-group 20
    bridge-group 20 spanning-disabled
    interface FastEthernet0.35
    encapsulation dot1Q 35
    no ip route-cache
    bridge-group 35
    bridge-group 35 spanning-disabled
    interface BVI1
    ip address 192.168.35.12 255.255.255.0
    no ip route-cache
    ip default-gateway 192.168.35.1
    no ip http server
    ip http authentication aaa
    ip http secure-server
    ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
    ip radius source-interface BVI1
    access-list 111 permit tcp any any neq telnet
    snmp-server community home RO
    snmp-server enable traps tty
    control-plane
    bridge 1 route ip
    line con 0
    access-class 111 in
    transport preferred all
    transport output all
    line vty 0 4
    access-class 111 in
    transport preferred all
    transport input all
    transport output all
    line vty 5 15
    access-class 111 in
    transport preferred all
    transport input all
    transport output all
    end

  • How do i connect a wired pc, and wireless nb to same network?

    is it possible to connect my desktop to a network with a wireless notebook without adding a wireless card to the desktop? I have a wrt54g wireless router.

    On the back of the router you should have 4 ethernet output ports.  If your desktop has a ethernet adapter all you need is a ethernet cable.  This BTW is the prefered configuration as you will always have communication with the router even if there are wireless problems.

  • "wired AND wireless" or is it "wired OR wireless"? using a C309a

    I am setting up a C309a (also called a photosmart premium all in one) for a school.  I got the wireless to work.  That is, all is setup and I can print from a laptop using only a wireless connection.  The school has a few desktop computers without wireless capability.  Can I use the ethernet wired connection for those with in order to print from those desktops without losing my wireless capability on the laptops?

    To be a little more specific, the HP Photosmart C309A can support either a LAN (wired) or a Wi-Fi (wireless) connection to the access-point or wireless-router.  It does not support a LAN and Wi-Fi connection simultaneously.  In fact, connecting the LAN cable to the printer disables the wireless connection.
    It sounds like you've connected the C309A to the network wirelessly and that's fine.
    As to whether the laptops and desktops are connected to the network via LAN or Wi-Fi, it doesn't matter to the printer.  From the printer's point of view, it's just one network.
    There's one more combination to talk about:  you can connect to the C309A a single computer via USB while it's also connected to the network (either wired or wirelessly).
    So at the risk of confusing everyone, you can connect some HP Inkjet printers "Wired (USB) and Wirelessly (Wi-Fi)" or "Wired (LAN) OR  Wirelessly (Wi-Fi)". 
    Regards / Jim B / Wireless Enthusiasts
    ( While I'm an embedded wireless systems engineer at work, on this forum I do not represent my former employer, Hewlett-Packard, or my current employer, Microsoft )
    + Click the White Kudos star on the left as a way to say "thank you" for helpful posts.

  • 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.

  • Officejet 7210 wont print on wireless laptop

    Ok...my printer and wireless laptop read each other perfectly until I got a virus...took it in ..and after I got home with the computer, it would no longer work with the printer. Printer is plugged in through ethernet cable to wireless router.
    Running windows xp home
     by the way it works when printer and laptop are hooked up via usb
    Thank you for your help..Dave

    If you still have the driver loaded you can add it manually: 
    First, verify that you can browse to the printer's internal web page by its IP address.
    1. Click "Start" button --> Printers and Faxes.
    2. Under Printer Tasks, click "Add Printer".
    3. Click "Next" button on the Add Printer Wizard window.
    4. Select "Local printer attached to this computer". Deselect "Automatically detect and install My Plug and play printer". Click "Next".
    5. Under Select a Printer Port option, select "Create a new port" and select "Standard TCP/IP Port" and click "Next" button.
    6. In the "Welcome to the Add Standard TCP/IP printer port wizard" make sure that the printer is turned on and connected to same network that your computer is connected to. Click "Next" button.
    7. Under "Add Standard TCP/IP Printer Port" enter the printer's IP address. Click "Next" then click "Finish".
    8. Now, select HP from the list of manufacturers, select your printer from the list of Printer models and click 'Next' button.
    9. If you can't find your printer, you'll need to find the install CD and use the "Have Disk" option to select one of the hp*.ini files. Alternatively, you can select another HP printer model from the same type.
    10. Add the print spooler name and click "Next".
    11. Click "Next"
    12. Click "Next" and then "Finish"
    Say thanks by clicking "Kudos" "thumbs up" in the post that helped you.
    I am employed by HP

  • One server 4 wire and wireless

    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:"";
    mso-padding-alt:0in 5.4pt 0in 5.4pt;
    mso-para-margin-top:0in;
    mso-para-margin-right:0in;
    mso-para-margin-bottom:10.0pt;
    mso-para-margin-left:0in;
    line-height:115%;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"Calibri","sans-serif";
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:"Times New Roman";
    mso-fareast-theme-font:minor-fareast;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;}
    Hi
    Can we use the one NAC server for wired user and wireless users? One more thing wired users license can be used for wireless user or not ?
    Regards,
    Vashdev

    Vashdev,
    Yes, using one server for both is possible.
    No differentiation is made between licenses.
    HTH,
    Faisal

  • 5510 - prints via USB and wirelessly but can't print emails from ePrint on iphone

    Just installed new Photosmart 5510. Prints fine via USB (main computer) and wirelessly (laptop) but I can't print anything from ePrint app on iPhone. HP ePrint Home & Biz works from iPhone but it doesn't have email printing function!

    Hi Andy760,
    From your iPhone, printing email would be from Apple Airprint.  With your email open, touch the action button and select Print.  You might have to select the printer, but it should print fine at that point.
    To send email to print by using ePrint, you would forward the email to the printer's ePrint email address.  Have you registered the printer on www.eprintcenter.com?
    I was an HP employee.
    Please mark the post that solves your problem as "Accepted Solution"

  • 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?

Maybe you are looking for