Can I have wired and wireless connection together?

I have a wired Ethernet connection to my black home hub with BT Total Broadband which works perfectly. However my son occasionally would like to connect via my home hub, but wirelessly at the same time. Whenever he tries to connect he gets several other outside connections available in the area but my home hub is seen but not available i.e. it has a red cross at the side of the selection panel. Would the instructions in the "How to set up ..." postings above enable me to solve this or is there something else I should do? He is using a PC and I am using a Mac if that has any relevance.

It makes no difference what O/s a computer is using. I think you probably need to switch wireless on in your router.
Enter 192.168.1.254 in your browsers addressbar, that'll take you into your routers config page. I'm afraid you'll have to rummage about in there to find your wireless settings as I use a Netgear router.
HEre's a link to some destructions... Click me
[EDIT]
Ok.. I found a link in my other link that should take you to the wireless config page...
Click me 2
When you find the right bit, write down the (E)SSID and network key as your son will need to enter them in his wireless network manager.
An MSCE in computing is like having a McDonalds Certification in World Cuisine, pointless.

Similar Messages

Can I have wired and wireless simultaneously - and connect via another Mac?

Here's my problem: My eMac (Feb 2005 running Leopard 10.5.8) is great except that it drops the ethernet cable internet every 15 minutes or so. "Sleep and wake" and I'm back on the internet for another 10-20 minutes, but this is not a long-term solution.
OK so I say that I will get a D-Link wireless USB adapter for the eMac (it has bluetooth, but not WiFi). Fine, except then the D-Link DIR-635 router that sends the WiFi signal is too far away and too weak. But I have another computer to which I can plug-in the Ethernet CABLE. Can I then connect the eMac via a wireless (airport) sharing? NOTE: At this time the ISP Modem goes to a DIR-635 router (a wired and wireless router) and the cable goes up 2 flights of stairs to the eMac. I'd plan to then plug-in the PBG4-12" to the cable instead of the eMac; and then connect the eMac via wireless sharing if that is possible. (The PBG4 does NOT drop the signal via wired ethernet - it is a problem with the eMac not the cable or router).
BUT then how to print? My MP640 printer is set-up for wired printing only right now. And for a number of reasons, I really want to keep it on wired (not wireless)-- I use this with another computer etc. etc. and wired gives me more selections for printing...
Any comments on this possibility and then I'll reply with comments and/or ideas-- THANKS!
Best regards,
Steve Schulte
Thursday 3 February 2011

If you use two routers then you should have the main one (connected to modem) as the official router. The second one should be configured to extend the existing network (you will need to consult its manual to find out how that's done.) If you try using two routers independently, then they will tend to interfere with each other because both are trying to deliver IP numbers on the network. So if the printer ends up on the secondary router then a machine connected to the main router may not be able to connect to the printer.

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.

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

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

Just click this link.

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.

Managing wired and wireless connections.

I have a client who wants to be able to use a wireless hotspot for backup internet when their main connection fails.
However when the main internet fails, they can't always use the wireless connection they've set up while still being on the wired LAN. The workstation will ignore the wireless connection and attempt to connect to the internet via LAN.
1. They need the LAN for networked printers
2. They want to be able to use the wireless hotspot to connect to the internet.
3. They want to be able to switch between connections without their users needing to change anything manually other than connecting to the wireless hotspot.
I've been looking but I haven't been able to find any kind of software that manages network connections in this way.
Is anyone able to suggest a 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.

Slow wired and wireless connections on new Mac Pro

I have a new 6-core Mac Pro with 64GB RAM that I seem to be having major network issues with. When I restart or first switch the machine on it's fine but after a few minutes the network (web browsing) become painfully slow - when I run a speed test it come out at ~2Mbit/s. This is the same whether I connect on a wired or wireless connection. I've tried various connections including a complete bypass of my time capsule to a direct wall connection that should be giving 100Mbit/s. When i run a speed test on my iPhone connected to the time capsule via 5GHz I comfortably get >60MBit/s.
Is there a bug in the latest OS 10.9.4 my MBAir also seems to require a lot of restarting to keep up even basic web browsing???

Your Macs are always looking for a better connection. To that end, they are evaluating every possible way to get to the Internet.
It is very important that you limit those choices to only the ones you actually want to connect to, and indicate that the other are "off the list", literally.
For example, to test your wired network connection, Ethernet must be at the top of the list AND WiFI must be OFF. (Otherwise, your Mac will be checking WiFi to see if it seems to be getting a better connection over WiFi. In the screenshot below, Ethernet is at the top of the list, so it is likely to be used, but since WiFi is still ON, it may be used instead.
To check YOUR WiFi connection (and not your neighbors' connections), you need to BOTH check that the "ask to Join new Networks" box is checked:
and that the Networks you wish to join are shown in the order you wish to join them. All extraneous networks should be removed from this list:

Can i use home sharing while mixing wired and wireless connections?

I have an HP Pavilion desktop connected to my wireless router with an Ethernet cable. My AppleTV is connected wirelessly to the 5GHz band on my simultaneous dual-band wireless-N router. How do I share photos and music from the HP desktop to the AppleTV using Home Sharing?

mikefilmguy wrote:
I have a similar problem.
I have 2 computers (and other ethernet addressable devices (printer etc) upstairs connected into a gigabit switch (d-link DG-2205) - computer A is an old 2002 G4 without wifi, computer B is a 2010 Mac mini wired into the switch. Downstairs, I have Computer C - a 2012 Mac mini connected to the fios router via wifi and there is a 1080p Apple TV connected via wifi.
Computer A (Wired switch Connection) can only see computer B's (Wired switch Connection) music library.
Computer B (Wired switch Connection) can see both computer A's and computer C's (Wireless router connection) Music library.
Computer C (Wireless router connection)) can see computer B's (Wired switch Connection) music library.
Apple TV can see computer B and C.
The problem is that computer A Is the music computer That I want to stream throughout.
If computer A and B can see each other, and computer C and AppleTV can see computer B, then why can't everyone see computer A ?
Any response appreciated.
What version of iTunes is the Computer A running - it may not support Home Sharing.

WRT54G2 v1 - Substantial Speed Difference Between Wired and Wireless Connection

Hi everyone,
I have a WRT54G2 v.1 router connected to an RCN Cable Modem. My download transfer rate direct from the cable modem is 18 Mbps. Thankfully, I can get the same download rate when I plug my laptop into a wired ethernet connection from the router. However, the wireless connection only gets a download rate of 0.8Mbps. Also, my wireless card is pretty new (Intel 4965AGN) and has the latest driver (I can get far higher download rates at mobile hotspots, for instance). Here is what I've tried with the router:
- I've upgraded the router firmware to the latest build (Version 1.0.04, 07/08/2009).
- I've tried multiple channels on the network (1, 6, 11).
- I use WPA Security.
- Upon advice from the Linksys live chat support, I've changed the MTU settings to manual and set them to 1300.
- They also recommended that I change the following settings: “RTS Threshold” – 2304 “Fragmentation Threshold” – 2304 “Beacon Interval” – 50
- And of course: I've got my own SSID. The router is 5 feet off the ground. There are no other wireless devices that would cause interference. The router is not near large metal objects, fish tanks, or any other physical obstruction.
Is there anything else I can do? Thank you so much in advance for reading. I really appreciate it.

Also, is there anything to the fact that only the download rate seems to change?
Wired:
Wireless:

How to use both wired and wireless connection with static addresses

Now that I have setup my home network with static addresses (router, mini1, mini2 and PC) in the way I want, (big thanks to BDAqua http://discussions.apple.com/thread.jspa?threadID=1271635&tstart=0) I would like to understand some more advanced network concepts.
I would like to change the network so that I use both the wireless connection and the built-in ethernet connection at the same time in my Mac mini1. I would like to connect my PC to my Mac mini by using the wired ethernet connection so that I reach the Internet from my PC as well. I would also like to be in control of all the addresses therefore I want to assign the addresses manually.
The question: What addresses should I use between mini1 and PC? Should I use the same wireless address space as I already use between the wireless router and the other computers (router: 192.168.1.1, mini1: 192.168.1.101, mini2: 192.168.1.103) or should I use something totally different like 10.X.X.X? What should I put in ethernet connection "Router"-field, the same as in Airport (192.168.1.1)? What about DNS, same as in Airport?

If I understand this correctly, you wish your Mini to perform Internet Sharing for your PC, correct!?
If so you'll pretty much have to let the Mini handle DHCP & NAT on the Ethernet port. You also want to be sure Airport is dragged to the top of Network>Show:>Network Port Configurations, that's what position the Mini will use 1st for Internet itself.
On the Mini turn on both Web Sharing & Internet Sharing. The PC once connected will have the Mini's Ethernet IP as it's Gateway addy.

Configure wired and wireless router together

Hello, I bought a WRT54G wireless router and I want to connect it to my wired router (Linksys BEFSR41 v2) and I don't know where to begin? I tried to connect the cable in the "Uplink" connection on the wired router and in the "Internet" connection in the wireless router and it doesn't work. Thank you for your help Dominic

Read this post.

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?

A very strange wired and wireless network issue

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

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

NetworkManager - switching between wired and wireless

Hello!
I’ve set up a new laptop with Arch and now have a question concerning NetworkManager. Is it possible in NM to switch between wired and wireless connections like it is with Connman (https://wiki.archlinux.org/index.php/Co … d_wireless)?
So far it appears that NM only disables the wired connection when wireless is used but keeps the wireless alive when switching to wired.
I have already looked for a corresponding configuration but couldn’t find anything that helps.
Thanks in advance.

Easy Mode:
You can install the tlp-rdw package and edit the /etc/default/tlp configuration file which has an option that does that.
Hard Mode:
If you don't want to install a package and its dependencies, you can write your own script and put it in /etc/NetworkManager/dispatcher.d and have the NetworkManager dispatcher hook run the script (which is actually what tlp-rdw does but you don't have to install the tlp package as a dependency)
Note: tlp is a power manager and if you have any other power managers installed it might conflict with them so be wary of that.
Here is the wiki page on tlp https://wiki.archlinux.org/index.php/Tlp
Last edited by fungle (2014-08-05 23:05:00)

I have an existing new belkin modem router which works fine with quite a few wired and wireless products in my house. My question is if i buy a time capsule can i put it in another room and wirelessly connect it to the belkin modem router, I would then ju

I have an existing new belkin modem router which works fine with quiet a few wired and wireless products in my house. My question is if i buy a time capsule can i put it in another room and wirelessly connect it to the belkin modem router, I would then just like my macbook pro and (imac future purchase) to wirelessly back up to it???????????

Your will need to perform a Factory Default Reset on the TIme Capsule to clear out the current network settings and then reconfigure it to "join" your wireless network using the AirPort Utility setup application.
To perform the Factory Default Reset on the Time Capsule....
Pull the power cord from the back of the device
Wait a few moments
Hold in the reset button on the back of the Time Capsule and keep holding it an additional 8-10 seconds while you simultaneously plug the power cord back in to the Time Capsule
Release the reset button after the hold period and allow 25-30 seconds for the Time Capsule to restart to a slow, blinking amber light
On your Mac.....
Open Macintosh HD > Applications > Utilities > AirPort Utility
Click Continue
Follow the guided setup and choose the "join" option when it appears duriing the setup
You will need to know the exact type of wireless security that the Belkin router is using to enter this information during the setup of the Belkin. Otherwise, the Time Capsule cannot join the network, and you will receive an error message after the configuration process.

Can I have wired and wireless connection together?

Similar Messages

Maybe you are looking for