Best Config for 2 iTunes Libs, AppleTV, Wired and Wireless

Hi there,
Looking for a little configuration advice.
AppleTV connected wired to AirportExtreme.
PC 1 with iTunes (wife and kids library) connected wired to AirportExtreme. This is the "main" AppleTV library.
PC 2 with iTunes (my library) connected wirelessly to AirportExtreme and shared on Apple TV. PC2 has its iTunes library on an external USB drive.
I get the sense I have too many hops, though AppleTV seems to be working OK. I can't get away from the suspicion that streaming from PC2 isn't great.
Any advice on a better config? Part of the problem is that PC1 somethime gets rebooted by kids. A Mac is so in my future.
Connect hard drive from PC2 to back of AppleTV and then share connect iTunes on PC2 to lib wirelessly across network?
Consolidate libraries?
Synchronize ALL music to AppleTV (140gb). Won't I need to be sure iTunes is still running on PC1 or whatever the main AppleTV-iTunes instance is?
Anything else?
My thanks!!!

I'm not entirely sure what you are asking here, there doesn't seem much wrong with the way you have things, although if PC 1 sometimes gets restarted and itunes doesn't always get relaunched, you could either sync the PC 1 library rather than stream it, or have you thought about ensuring itunes always opens when the PC boots up.
You cannot add an external HD directly to the tv.

Similar Messages

AppleTV Wired and Wireless?

The AppleTV is on the opposite end of the house from all the other stuff. I bought an Express to put halfway and extend my Time Capsule network but the AppleTV still stutters and rebuffers a lot. I have just run six lines of CAT 6 under the house into the family room. The plan is to connect to those lines the AppleTV, Airport Express, DirecTV box, Blu-ray player, X-Box 360 and Pioneer receiver.
Can I still use AirPlay if I hard-wire the AppleTV? Not sure if I have to turn off wireless on the AppleTV if I use the ethernet connection or if I use both will the AppleTV get confused and try to use the slower low-signal wireless connection for streaming.
Thanks,
-= Ken =-

Great! It sounds like I can have wireless turned on while the AppleTV is hard-wired to the network. This way I can wirelessly use my iPad, iPhone or MacBook with it. Do you know if I can enable wireless on the AppleTV and tell it to not look for a wireless network or do I not even have to worry about that?
Thanks,
-= Ken =-

Is it possible for my printer to be wired and wireless?

Thank you for any suggestions on how to get my printer to be a wireless printer plus a wired one ...

Hi,
The printer can only be connected to a network using either Wireless or Wired.
However, once you connect the printer to your network it becomes available to any other device connected to that same network, either if it is connected wirelessly or wired.
Regards,
Shlomi
Say thanks by clicking the Kudos thumb up in the post.
If my post resolve your problem please mark it as an Accepted Solution

Best Practice for Multiple iTunes and One Account?

My wife and I share our account for our iPhone Applications and Songs in iTunes.
Can someone point me to a topic that covers a best practice for multiple iTunes syncing?
I travel a lot and keep my iPhone synced to my Macbook Pro while she uses the workstation at home to sync to. We keep the addresses and contacts and calendars synced through MobileMe, however, I'm trying to find the best way of pushing applications and songs I've bought over to the other PC so they're still around while I'm traveling for her to sync with.
Thoughts?

Hi Steve,
Might be trying for solution for a long time, If i understood your question clear let me clarify you few points.
You are trying to access the bex query which is designed with the exit's in the background based on the logic and trying to call the entire dimensions and key-figures in a single connection. Then you are trying to map those data in the charts.
Steve, try to make more connections based upon the logic and split them. use the same query but split them by sales per customer group, sales per day, sales per week by making three different connections and try. You can merge the prompts from all connections.
Hope this Helps!!!
Sorry if i misunderstood your question.
--SumanT

Itunes not connecting via airplay on wired and wireless network

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

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

Sharing iTunes between wired and wireless Macs

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

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

NAC Guest server for wired and wireless

Hi
My customer wants the NGS to install for both wired and wireless users. For wireless users we can integrate it with the WLC but i don't know how it will work for wired users at the same time. Pls suggest.
Thanks

Hi Vishal,
Please note that if you want to return ACLs (and usually in wired web auth you need to), you will have to integrate with ACS as NGS itself cannot return ACLs in the reply radius attributes.
Basically the process is as follows:
1 - Client plugs cable on switch.
2 - Web auth is triggered on the port.
3 - default ACL permiting only DNS and DHCP is applyed so that the client PC can obtain IP address and open a browser.
4 - Client will be redirected to the NGS hotspot login page.
5 - Client will enter credentials.
6 - Client broswer will send an HTTP POST packet containing the credentials.
7 - The switch will intercept the POS packets and retrieve the credentials entered.
8 - The switch will send Radius Access-Request to the ACS.
9 - The ACS will use the NGS as External Identity source to authenticate the client.
10 - The NGS will reply with Radius Access-Accept to the ACS and the ACS will reply to the switch including the ACL in the Access-Accept.
11 - the Switch authorizes the client on the port and applies the ACL it received from the ACS.
Please follow the document Nicolas posted as it is a good one.
HTH,
Thanks

DHCP Server - Different Range for Wired and Wireless Network

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

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

Hi, i want to buy a licence of Creative Cloud, but i have one question... Whats the best choose for a little enterprise?? And if i buy a Single Person Licence, on how many pc's can i install the suite??

Hi, i want to buy a licence of Creative Cloud, but i have one question... Whats the best choose for a little enterprise?? And if i buy a Single Person Licence, on how many pc's can i install the suite??
Thanks for helping

no, that's incorrect.
you can activate on 1 mac and 1 pc, or 2 pc's, or 2 mac's, concurrently.
i have cc installed on 2 pcs and 1 mac. i can only activate 2 at any one time which works well for me because my pcs are at home and my office and i use them most of the time.
but when i travel i take my macbook so i just deactivate one or both of my pcs (uninstalling is not needed) and sign in to my macs cc app.

How to control bandwidth for wired and wireless

I have a wrtn400n dual band router and I was wondering if there is a way from the router settings that can lower internet connection for wired and wireless. Reason why its because I have 3 cousins that ALWAYS downloading music, videos, or watching a movie from an asian website. It lags me so much, that I can not even play online games. My ISP is comcast which is cable. I can barely surf on the net. Its like, they're taking up all my connection. I know there is a way to do it without cutting them off from the connection. It's a 2.4 and a 5.4ghz router and I can't find my 5.4ghz ssid on my wireless networking thing. My sister and I are wired connected while my cousins are wireless, but sometimes one of my cousins wire their laptop. The modem and router is connected to my computer. Please help me!!! I know theres a way to do this, but I just can't find out how!
Message Edited by rayng6688 on 12-12-2009 03:38 AM

Simple answer: it's impossible. See here.

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?

WRT54G2 keeps dropping connection, wired and wireless

I have a Scientific Atlanta modem with WRT54G2 wireless router. Both are around 2 years old. In the past few months, I keep getting periodic connection drop, couple times a day, day on day off. I have 2 wired connections and 3 wireless connections to the router. I check with my internet provider, Cox, they say my connection is fine. So I guess it's the router or modem problem.
The funny thing is when connection drop, I cannot access any web sites via wired and wireless. However, my downloads in iTune are still running fine at full speed. I have to unplug and replug both router and modem for it to work again.
Is there a way to fix this? or do i need to buy a new router or modem?
Solved!
Go to Solution.

It's possible that Cox only recognizes the router's MAC address, probably the reason why you can't connect directly.
Anyway, try to lower the MTU settings on the router.

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.

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.

Problems with hp laser printing in leopard- wired and wireless

Printing problems in Leopard are slowly eating away at my last nerve!
Here's the background: I have a Macbook Pro 2.33GHz Core 2 Duo, 4GB ram, running 10.5.2. Ever since I upgraded to Leopard, I've been having printing problems, both wired and wireless. I have an HP Laserjet 1160, which is a wonderfully reliable printer- I've had it since 2005 and have never had a problem.
When I installed Leopard, I began getting a popup message after starting up my computer and logging in. The message has a lighthouse icon on it and reads:
"Popup Error: Failed to listen for incoming Popup jobs. You will not be able to use Popup printing for the duration of this session. Please report this incident to a system administrator."
(for the record, I only have one computer, it's not on any system, and I have the administrator account)
Here are the two problems I have:
-First, wired printing is spotty. Half of the time, when I connect the USB cable and click print, nothing prints. Usually, if I unplug the cable and plug it into the other USB port, then printing works. This is in spite of the fact that the computer recognizes that the printer is there- I can delete then re-add the printer to my printer list and still nothing.
-Second, wireless printing does not work at all. Again, the printer is recognized when plugged in to either the time capsule or the airport express, and I can add the printer, but printing doesn't work: the job is sent to the print queue, but the queue stalls on the "connecting to printer" phase.
This problem is a huge pain, and I have no idea how to solve it. Any help is appreciated.
Jon

Thanks for posting this problem Cathjock. I have had the same issue with a NEC Superscript 1400. Thinking it wast he printer, which is getting up there in age, I went out and purchased a new HP P1505 to no avail. I have been researching this for a few days now and think that all of this is related to a user permission in CUPS. I have de-installed, re-installed, re-booted etc as prescribed and got three pages hours after the fact via my Airport Express connected new printer. Generally, however, nothing comes out immediately as was the case in the past either on Airport Express or via USB cable. I am stumped and am starting to get worried.
I can't print invoices for my business and am considering firing up my old Windows machine if you can believe it !
Seriously, Apple has created a monstrous situation with all of htese printing issues and nothing is apparently being done, nothing that I can find in any of the discussion forums at this time.
My last option is to re-install 10.5 with an archive and install as I really cannot afford to start from scratch.
Now if you look at this forum, there are 242,847 views logged with 2,514 questions and 13,848 messages.
This should mean something for Apple as many people need help and are getting really really ******-off.
So pleeeeaaaaase Apple. respond and offer a fix for this problem that is plaguing a ton of people.
Chris

Best Config for 2 iTunes Libs, AppleTV, Wired and Wireless

Similar Messages

Maybe you are looking for