Warning: WRT310N External and wireless Admin Disabled

Warning: WRT310N External and wireless Admin Disabled I found that if I browse to my router web IP address that even with external admin disabled the router still generates a pop up for admin log in which allows brut force attaches on your router.
Hopefully linksys is going to fix this soon? I did notify the support people and they verified that when they browed to my IP it would come up with the pop up and if they had login info they can take control of the router...
Just make sure you use STRONG Passwords, really, really strong! until they fix the problem
Genius is not in the understanding of complexity but in its simplification! by R.Ries
Windows defined as 32 bit extensions and a graphical shell for a 16 bit patch to an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company that can't stand 1 bit of competition. by R.Ries
Ban Internet Explorer from your website and force upgrades to real browsers, FF, Opera or other

If you are using "admin" as your router's password, change it to something else.  Also, change your ssid from "Linksys" to something else.
Use wpa2 as it is more secure than wep.
Wep uses a static key while wpa & wpa2 uses a dinamic key and a shared key or password.
Greetings from Northern Ontario, Canada

Similar Messages

  • How can I disable wireless admin privileges to the router ?

    I am using an Airport Utility for Windows for Airport Extreme. For the sake of better security, how can I disable wireless admin privileges to the router so that the router can only be configured via hardwire connection?

    For the sake of better security, how can I disable wireless admin privileges to the router so that the router can only be configured via hardwire connection?
    Sorry, but this is not possible.
    If you want to limit access to administration of the router, you should change the Base Station password, and only give out that password to those individuals that you want to have access to the administration settings of the router.
    The forums have been having problems displaying screenshots, but we will attach one below in the hopes that the problems may be fixed.
    Important Note.......even with this,  "security" on the AirPort routers is an illusion.......since a one second press on the reset button will give any user 5 minutes of free access to go in and change any settings that they want. 
    So, you might want to keep any eye on things.

  • I'm trying to update my apps in my macbook , the apple id is not mine and it's disabled and cannot change it, I'm the admin and my apple id shows correctly in iTunes and iCloud etc. only app store shows a disabled apple id why?! the computer has3 accounts

    Problem - grayed out apple id in app store
    I have signed in to my account, I am the admin and my apple id is correct shown in itunes, and other apps except the appstore.
    In Appstore, it shows another email id and it is disabled.  
    Problem
    1. I do not know why another email id is visible in my account (we have separate accounts on this laptop , all admins)
    2. Why wouldn't it allow me to change the login name and let me get on with my updates!!
    Options already looked
    1. phone - asked me to go to support blah blah .apple.com
    2. internet - i'm here.
    3. Applet id - manage on line- all is well there. no need to change anything.
    4. other apps with apple id involved - checked and works fine.

    Do you recognize the ID?

  • The wireless network appears to have been compromised and will be disabled

    I have been getting this message from time to time since I purchased my Airport about a month ago, I think in total I have received it 3-4 times. The reason it is interesting is because the behavior is similar to some other posts about dropped connections.
    They symptoms are I will be surfing along and suddenly I get no data at all, it just stops dead. If I have an active application that is trying to pull live data like PC Anywhere I will tend to get the above message. If I don't then no message but I have to turn off my Airport NIC in my laptop and turn it back to reconnect.
    I have found that by going into my Airport Utility and under Wireless Options changing the WPA Group Key Timeout to a longer period the problem has been mitigated. It is still a problem overall but at least the chance is only every 8 hours instead of every 1-2 hours.
    To improve security WPA changes encryption keys from time to time and my theory is that either the Airport base station or the Airport NIC card have problems with this procedure.
    One thought is that the Airport NIC misses the change and thus is still trying to send data using the old key. I don't know how this could happen, maybe it is going to sleep for a short period?? This would go along with the disconnect and reconnect working though.
    Another thought is that whatever method is being used to detect a security compromise during the exchange of new encryption keys in the WPA standard is way too sensitive and is thus deciding to lock all users out for the mandatory minute. This would explain why people seem to get it with D-link routers etc. Maybe after the minute things just don't negotiate properly, maybe this was by design for security?
    Has anyone played with the different encryption schemes? I am currently using WPA/WPA2 Personal. I am guessing that WEP won't have this issue because it doesn't use rolling keys. I wouldn't use WEP though because it can be cracked in ~1 minute. I know users have reported that no security works fine but I can't use this as I don't live on a 100 acre farm. Is WPA2 any better?

    I also switched to 5GHz N only mode at the same time. I see some other posts that indicate this helps.
    Maybe other 2.4 GHz traffic is being mis-read as a hack attempt and the wireless is shutting down??
    This is still better than the Netgear I had, when it stopped traffic both the wired and wireless were dead and there were no errors. I couldn't even access the config page.

  • Received warning re. McAfee ScriptScan 14.4.1 extension won't work with FF 10.0.2 update, and will be disabled. How should I proceed?

    MY system is Windows XP, SP3, laptop, running FF 9.0.1. When trying to update to FF 10.0.2 I got a msg that the McAfee ScriptScan 14.4.1 addon won't work with FF 10.0.2 and will be disabled. Shall I go ahead and install the FF update? Would it be a security risk either way? Which one is worse?

    I don't know what ScriptScanner does, but I think it's always a good idea to update Firefox to eliminate known vulnerabilities, particularly if it's your main browser. You can see what security problem were fixed in Firefox 10.0.2 (and earlier versions) on this page: https://www.mozilla.org/security/known-vulnerabilities/firefox.html
    According to the end of this long forum thread, there's a good chance it will still work (based on experience with the previous release): [https://community.mcafee.com/message/226187 McAfee Communities: McAfee ScriptScan for Firefox 14.4.0].
    However, it has been reported that the McAfee add-ons can cause Firefox to use much more memory. If you notice a performance slow-down, consider disabling them. More info: [http://blog.mozilla.com/nnethercote/2012/02/17/the-mcafee-site-advisor-add-on-has-an-appalling-memory-leak/ The McAfee Site Advisor add-on has an appalling memory leak | Nicholas Nethercote].
    Hope this helps.

  • Is it possible to disable the users ASGADM DEVELOPER and IBE ADMIN?

    need to know if they can be inactivated system users (ASGADM DEVELOPER and IBE ADMIN)
    We need to know what they are used and if they do not cause any problems with its inactivation
    we have EBS 11.5.10.2

    971780 wrote:
    need to know if they can be inactivated system users (ASGADM DEVELOPER and IBE ADMIN)
    We need to know what they are used and if they do not cause any problems with its inactivation
    we have EBS 11.5.10.2
    Please see:
    Secure Configuration Guide for Oracle E-Business Suite 11i (Doc ID 189367.1)
    Is it Safe To End Date Some Applications Users like GUEST ? (Doc ID 783428.1)
    Thanks,
    Hussein

  • 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 completely turn off Bluetooth and Wireless

    Hey everybody,
    I'm running Windows XP SP3 via Boot Camp and I was wondering if anyone can assist me in how to completely turn off Bluetooth and Wireless connectivity so that I can reserve as much batter life while being in class taking notes without a plug-in source, but not uninstall. I know there is a Bluetooth control panel and I disabled it there but under "connect to" its still remains there. Basically I want to have the Bluetooth and Wireless turned off completely when I startup and still have the icons shown in the taskbar to let me know that they are still there.
    Thanks!

    Joergen Thomson, I can see that you have the same thoughts like I do, I wish they could release a software that is stable and better then this.
    I dont have the energi or time to report all flaus back to cisco, this product have taking to much of my time and frustration already. Thank you so much for all the time you spend to try get this product stable and hopefully a good product.
    I have a costumer that have a webservice that is IP restricted, For now I have to define more then 93 policys openening for the same service because this doesnt handle address list and groups. And all the times I had to set it back to factory default becasue of HTTP Admin server stopped, VPN Problem, Firmware Upgrades, "Packet Loss" and so on takes alot of time becasue I need to reconfig policies back.
    For now to they release a firmware is stable I have take this piece off the network and put the back a old Fortinet 60 box.

  • Need to admin disable 802.11a radio from a few light weight access points

    Hi team,
    I need help to admin disable the 802.11a radio interface from a few lightweight APs. The operational status of these radio interfaces is down, so I am getting the following error when I try to disable them from the wireless LAN controller.
    (Cisco Controller) config>802.11a disable wds2.hyd.shaw.net
    This slot is not operational because Regulatory Domain Check has failed! Unable to disable the Cisco AP.
    Could you please let me know how I can administratively disable the 802.11a radios on these APs? Please let me know if you need more details here.
    Regards,
    Swati

    The two previous posts are correct: the regulatory domain is probably not allowing radio a to be enabled.
    To be sure about this you can go to GUI of the wireless LAN controller > Wireless > Country. Here your country (or region) should be selected. Then depending on the access points that you have they may or may not join or turn on the radio. Per example if you have an access point from Europe (like AIR-AP1131AG-E-K9) then you will have a conflict if only the “America” regulatory domain (-A) is selected.
    Here is a link with a list of products and their regulatory domain that might help:
    http://tools.cisco.com/squish/648C8
    What you can do here is to simply allow the regulatory domain that the access point needs and you should not have any problems.
    IMPORTANT NOTE: If you change the regulatory domain and use an access point that transmit at certain channels and frequencies that are not allowed (illegal) in your country (region) you may have legal implications.
    I hope this information helps you with your concern.

  • How to set up an integrated wired and wireless network

    I have an iMac 17" 1GHz connected to a ethernet hub which in turn is connected to a DSL modem and from there to my ISP. I also have a MacBook Pro wirelessly connected to an AirPort Express; the AE is connected to the same ethernet hub through its ethernet port.
    I can connect to the Internet wirelesly using the MacBook Pro, but I can not seem to connect to the iMac.
    How can I keep the iMac wired and the MacBook Pro wireless, but see both on a network? The AE instructions don't seem to have an example for this kind of network.
    Any help would be greatly appreciated!
    Cheers,
    Martin
    MacBook Pro   Mac OS X (10.4.6)  
    MacBook Pro   Mac OS X (10.4.6)  

    Martin,
    As Frank said, you'll need a router with DHCP and NAT abilities (nearly all have this) connected to the modem.
    But just in case your "ethernet hub" is actually a router, just re-configure the AE not to distribute IP addresses - AirPort Admin Utility - Network tab. Try that and let us know.
    For minimal clutter, if you were DSL broadband instead of cable, you could sell the modem, sell the ethernet router, sell the Airport Express and buy a single Ethernet and Wireless DSL modem router - for less than the price of the AE. Some people like to keep the modem separate to make upgrades to the modem cheaper. My solution is to buy a decent modem in the first place, ie make sure it has ADSL2+. Almost all modem/routers do this now, even my ancient ones have firmware upgrades to offer this.
    For minimal spend, you can pick up an Ethernet router for about $30. Just replace your ethernet hub with it.

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

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

  • I have a new Macbook Air 2012, Apple TV 2 and I have tried wired and wireless connections both result in stuttering during video airplay to the ATV2.

    I have a new Macbook Air 2012, Apple TV 2 and I have tried wired and wireless connections both still result in stuttering during video airplay to the ATV2.
    I have even bought a new Airport Extreme Router just to confirm it is not the router and it still didn't help.
    I have brought all items in the same room with wired connections and still same issue.
    I was thinking maybe ATV 3 might help since it has 2 wifi antennas and faster processor.
    Have tried everything I could think of.
    This was one of the main reasons I bought a Macbook Air for this airplay feature. Very frustrated.
    Any thoughts; any other suggestions would be greatly appreciated.
    Thanks

    Thanks for the suggestion.
    I also disabled Norton Firewall and restarted the Air and Now I'm able to use Air Play.
    I know that the Apple remedy said that to do that in the support article, but I totally forgot I had that enabled..
    It actually works. I can even stream to the Apple TV now through my MacBook Air.
    BTW, Go into setting under the ATV, and click on update...you'll see that there was another update avaialble for the last gen of ATV...
    It does have to restart twice..I guess once to download and and nother to apply.

  • HELP please Wi-Fi (Wireless LAN) Disabled by device manager

    I have HP 2000-2d02EIA Notebook PC, but my wireless not working it shows this message "Wi-Fi (Wireless LAN) Disabled by device manager" via hp connectin manager when its on, please help me.

    Hi,
    Try Reinstalling the Wireless drivers for your notebook..
    Follow the instructions from the link below to reinstall wireless drivers using recovery manager..
    Restoring applications and drivers on notebook computers with Windows 8
    Note:
    If you have HP Support Assistant installed on the computer(The Blue Question Mark) then open it ==> Complete all pending Updates & Tuneups==> Restart and Check. It may solve your problem
    Although I am an HP employee, I am speaking for myself and not for HP.
    **Click on “Kudos” Star if you think this reply helped** Or Mark it as "Solved" if issue got fixed.

  • Satellite L735 won't connect to the internet (both wired and wireless)

    Hi,
    I have a brand new Satellite L735, and I'm having a lot of trouble with the internet connections.
    When I connect it to a wireless network it finds the profile and connects to it but then still says "no internet access" for both IPv4 qnd IPv6 connectivity statuses.
    I have tried troubleshooting, turing off the computer and wireless network and back on, but it's stil not working.
    The same happens with the workplace wireless, despite other computers connecting to it fine (so it doesn't come from the networks). I've also tried connecting it at work with an ethernet cable but no luck.
    I have the Atheros AR9002WB-1NG Wireless network adapter and the Atheros AR8152/8158 PCI-E Fast ethernet controller.
    I'm not sure what to do as the laptop is new and so it shouldn't need updates, all the settings are default, etc. I'd very much appreciate any help on this!

    Hi
    Uninstall or disable the TCP/IPv6 and use only the TCP/IPv4 protocol.
    Furthermore check if in TCP/IPv4 properties the IP address and other settings are set to assign automatically
    Furthermore I would recommend checking the firewall and some security applications which could be preinstalled on the notebook.
    It could be possible that antivirus or firewall prevent the notebook from connecting to internet.

Maybe you are looking for

  • I NEED TO KNOW IF IN SAP WE HAVE THESE STANDARD REPORTS FOR PP Division.

    i NEED TO KNOW IF IN SAP WE HAVE THESE STANDARD REPORTS FOR PP Division. OR I NEED TO CREATE BI/ABAP REPORTS PLEASE HELP. Please tell me how to check in sap these reports exists if not on functional report how to give fields and table name etc.......

  • Ichat difficulties

    me and my friend just got macbooks and we have been trying to do a video chat but it doesnt work. i think its either my router or his router.... i have a netgear and i believe he has a dell. we have both been using our aim accounts on ichat. anybody

  • Best way to log/notify when someone logs into ASDM

    What is the best practice to get a notification and log when s omeone logs in and uses the ASDM?  I have syslog server setup and smtp, and snmp traps, but not sure where to tell it to notify me when someone logs into the asdm..... any suggestions? th

  • Automated Lock & Send - Essbase VBA

    Hello, I'd like to know if anybody has a VBA code for uploading ("Lock" & "Send") several Tabs and templates in Essbase ? The version of Essbase I have is ESB11.1.2.2. Thank you in advance for your help

  • Keywording Keyboard Shortcut for Collapsing Hierarchy???

    All, Is there a Keyboard shortcut that will allow me to collapse any/all expanded section in the Keyword List without having to go to each open branch and closing individualy? If anyone knows of a resource / list of shortcut specifically for keywordi