Problem with WRT160NV2, both wired and wireless...
I bought a WRT160NV2 Refurbed from CompUSA about 2 weeks ago, and since then I've been having some problems.
It's not every site, but there are a few sites (three or four I've noticed) that load very, very, very slowly. It happens using wired or wireless (Main PC is wired). I've tried rebooting both the router and modem multiple times (10 or 20 times at least) and looked through the forums and noticed some people said try setting the MTU to 1300. I tried that and it didn't seem to do anything, so I tried 1350, 1400, 1450, 1490, and 1100, with no results with either. When I connect using just my modem everything works fine. I'm frustrated because I can't find a solution to this. Any help would be appreciated.
Firmware Version: v2.0.03 build 007 ;Jul 2, 2009
Message Edited by RagingShadow07 on 02-27-2010 01:48 PM
Since you have already changed the MTU size on your Router and still facing the same problem, then i think you need to Re-flash / Upgrade the firmware of your Router...
Download the firmware from the Linksys website and then upload the firmware on your Router... Once the firmware is upgraded on your Router, then you need to reset the router and re-configure all the settings on it again...
Similar Messages
-
Satellite L735 won't connect to the internet (both wired and wireless)
Hi,
I have a brand new Satellite L735, and I'm having a lot of trouble with the internet connections.
When I connect it to a wireless network it finds the profile and connects to it but then still says "no internet access" for both IPv4 qnd IPv6 connectivity statuses.
I have tried troubleshooting, turing off the computer and wireless network and back on, but it's stil not working.
The same happens with the workplace wireless, despite other computers connecting to it fine (so it doesn't come from the networks). I've also tried connecting it at work with an ethernet cable but no luck.
I have the Atheros AR9002WB-1NG Wireless network adapter and the Atheros AR8152/8158 PCI-E Fast ethernet controller.
I'm not sure what to do as the laptop is new and so it shouldn't need updates, all the settings are default, etc. I'd very much appreciate any help on this!Hi
Uninstall or disable the TCP/IPv6 and use only the TCP/IPv4 protocol.
Furthermore check if in TCP/IPv4 properties the IP address and other settings are set to assign automatically
Furthermore I would recommend checking the firewall and some security applications which could be preinstalled on the notebook.
It could be possible that antivirus or firewall prevent the notebook from connecting to internet. -
Problem with installing both 32 and 64bit Java7u45
Hi all.
For some reson we need to install Java7u45 because of an inhouse made application only runs on java7u45 32bit,
Now to my issue, we hava about 200 windows7 x64 machines who need both 32 and 64 bit java7u45.
If i install the 32bit the inhouse appliction works, but then other third party application will not run (SoapUI, Eclipse).
If i install both 64 and 32 bit the inhouse application will not run, i get this error message "NativeSwing[1]: Caused by: java.lang.UnsatisfiedLinkError: Cannot load 32-bit SWT libraries on 64-bit JVM"
In the Java Control Panel only the 64bit java shows up, and if i try to add javaw.exe from C:\program files (x86)\java\bin it will add the correct line, and i looks ok until i close the java control panel and open it, it will still only show the 64bit java.
So is there anyway to change the default 64bit java to 32bit and make it stick?
Thank you.panosk wrote:
uwinkelvos wrote:This isn't GWT, is it?
Hi, is there anybody using Eclipse and GWT in arch 64?
I use Eclipse Galileo 64 bit and trying to use GWT I get the error "...wrong ELF class: ELFCLASS32 (Possible cause: architecture word width mismatch)..."
Should I nstall bin32-jre from AUR and use it to start a 32 bit version of Eclipse? Is there another way using the 64 bit version of eclipse? -
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. -
Problem with adjusting both transparency and color of an object
I am writing a program where when an object is picked, both it's transparency and color will be altered (the object will become opaque, and its color will turn to a predefined "selected" color), while the previously selected object will return to its original transparency and color. I am able to get this to work, except that objects that were picked two or more picks ago will remain in the selected color, albeit in their original transparency. This problem only seems to occur when transparency is factored in. The picking/color & transparency altering code is as follows.
public class PickingListener extends MouseAdapter {
private PickCanvas pickCanvas;
private TextDisplay overlay;
private Primitive p;
private Primitive lastP;
private ColoringAttributes origColor;
private TransparencyAttributes origTransparency;
public PickingListener(PickCanvas pickCanvasArg, TextDisplay overlayArg) {
pickCanvas = pickCanvasArg;
overlay = overlayArg;
public void mouseClicked(MouseEvent e) {
pickCanvas.setShapeLocation(e);
PickResult result = pickCanvas.pickClosest();
if (result == null) {
System.out.println("Nothing picked");
} else {
p = (Primitive) result.getNode(PickResult.PRIMITIVE);
if (p != null) {
setSelectedColor();
overlay.setPickedBarInfo((BarInformation) p.getUserData());
else
System.out.println("null");
private void setSelectedColor() {
ColoringAttributes barCA = new ColoringAttributes();
TransparencyAttributes barTransp = new TransparencyAttributes(TransparencyAttributes.NICEST, 0.0f);
barCA.setColor(ColorConstants.SELECTED);
if (lastP != null) {
lastP.getAppearance().setColoringAttributes(origColor);
lastP.getAppearance().setTransparencyAttributes(origTransparency);
origColor = p.getAppearance().getColoringAttributes();
origTransparency = p.getAppearance().getTransparencyAttributes();
p.getAppearance().setColoringAttributes(barCA);
p.getAppearance().setTransparencyAttributes(barTransp);
lastP = p;
}Capabilities to alter the primitive's color and transparency are all set.
barAppearance.setCapability(Appearance.ALLOW_COLORING_ATTRIBUTES_READ);
barAppearance.setCapability(Appearance.ALLOW_COLORING_ATTRIBUTES_WRITE);
barAppearance.setCapability(Appearance.ALLOW_TRANSPARENCY_ATTRIBUTES_WRITE); barAppearance.setCapability(Appearance.ALLOW_TRANSPARENCY_ATTRIBUTES_READ);
ColoringAttributes barCA = new ColoringAttributes();
barCA.setCapability(ColoringAttributes.ALLOW_COLOR_WRITE);
barCA.setCapability(ColoringAttributes.ALLOW_COLOR_READ);)
Any insight as to why this would occur would be greatly appreciated.
-Adrian BentonA Behavior is the preferred way to make changes in a scenegraph. Here is an example from a previous post that changes the appearance of a shape when it collides with another shape.
The javadoc for javax.media.j3d.Behavior appears to refer to the issue you have.
Transparencies are confusing, different display adapters deal with them differently. Suggest you search the forum at
http://forums.java.net/jive/forum.jspa?forumID=70
for more detailed information.
regards
class CollisionDetector extends Behavior {
private static final Color3f highlightColor = new Color3f(0.0f, 1.0f, 0.0f);
private static final ColoringAttributes highlight = new ColoringAttributes(
highlightColor, ColoringAttributes.SHADE_GOURAUD);
private boolean inCollision = false;
private Shape3D shape;
private ColoringAttributes shapeColoring;
private Appearance shapeAppearance;
private WakeupOnCollisionEntry wEnter;
private WakeupOnCollisionExit wExit;
public CollisionDetector(Shape3D s) {
shape = s;
shapeAppearance = shape.getAppearance();
shapeColoring = shapeAppearance.getColoringAttributes();
inCollision = false;
public void initialize() {
wEnter = new WakeupOnCollisionEntry(shape);
wExit = new WakeupOnCollisionExit(shape);
wakeupOn(wEnter);
public void processStimulus(Enumeration criteria) {
inCollision = !inCollision;
if (inCollision) {
shapeAppearance.setColoringAttributes(highlight);
wakeupOn(wExit);
} else {
shapeAppearance.setColoringAttributes(shapeColoring);
wakeupOn(wEnter);
} -
Using both wired and wireless network Access?
I have a ThinkPad 510 with a docking station. Within the same room, connecting to the same network I may use the WiFi with the TP only, or connect using the docking station which is hardwired to the network. TP has W7 installed.
What is the correct procedure for bouncing between these two environments? Is there a setup which will allow
'automatic' access, depending on whether I'm using the docking port, or not?
Thanks,in the Thinkvantage Access software, you can set the network preferences. So you can set the Ethernet to be your most preferred network connection method, while your wireless as the second most preferred method. Or which way you prefer.
So for example, when you dock and the computer detects the ethernet network connection, it will automatically switch to the ethernet as it becomes available. And when you undock, your computer will switch back to wireless as ethernet is not available.
Regards,
Jin Li
May this year, be the year of 'DO'!
I am a volunteer, and not a paid staff of Lenovo or Microsoft -
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.
JonThanks 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 -
How to set up WRT54GS so the wired and wireless connections both work?
I have a DSL line in to a Motorola modem.
The modem is connected to the WRT54GS with an ethernet cable.
When I connect my computers directly into the WRT54GS with an ethernet cable (there are four connection spots at the back of the box), I cannot go to the internet. I have 3 computers plugged in, but none of them connect via Ethernet..
Is there a setting on the router so that I can use the router for both wired and wireless connectivity?
Added info: I tried to connect directly from the computer to the modem, but again, got no connectivity. When I "chatted" with ATT, they told me the modem is set to "bridge", and that I could connect only one device. I don't want to change this setting because I want to use the router for the wireless capability. Besides which, I have more than one computer to connect to the internet.
How come I cannot just plug in and go?
My firmware version is v2.07.1.
I don't know how to find out what hardware version I have.
Other info is "DirectEthernet Connection, Speed: 100.0 Mbps, Signal Strength: Excellent, Status: Connected"
Also "1394 Connection 3, Speed: 400.0 Mbps, Status: Connected"
I don't know what that's for, but thought it might prove useful to those of you who are knowledgeable about such things.
Wireless is ok, but if I'm sitting right next to the router, I'd like to connect with Ethernet and take advantage of the better speed, etc.
Thanks in advance.Just click this link.
-
Help with HP Laser CM1415fnw wired and wireless setup
Hello all,
I am have have trouble with both wired and wireless. It will only let me do one or the other. Is there a way i can do both?
everything works if i am wired or wireless but, the user wants to be able to use both.
Any help would be great.
This question was solved.
View Solution.Sorry, both cannot be enabled by design. That said, devices on a network do not care how others are connected. You can print from a wireless connection to a wired (Ethernet) printer and v/v.
Say thanks by clicking "Kudos" "thumbs up" in the post that helped you.
I am employed by HP -
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_failedWas 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? -
Both ethernet and wireless time-out trying to connect
I'm having a problem with getting my laptops' IP assigned by dhcp. Both over ethernet and wireless.
I have no problem connecting to my WPA connection at home, but now I'm at my parents for a week or two, it refuses to connect to their WEP network.
To connect to my WPA network I run this script from rc.local, which works fine on startup.
ifconfig ra0 up
iwconfig ra0 essid *********
iwconfig ra0 ap **:**:**:**:**:**
iwconfig ra0 rate auto
iwconfig ra0 channel auto
iwconfig ra0 mode Managed
iwconfig ra0 txpower auto
iwpriv ra0 set AuthMode=WPAPSK
iwpriv ra0 set EncrypType=AES
iwpriv ra0 set WPAPSK=***************************************
iwpriv ra0 set TxRate=0
dhcpcd ra0
So for the WEP network, I have commented all that out and changed rc.conf like so:
lo="lo 127.0.0.1"
eth0="dhcp"
ra0="dhcp"
wlan_ra0="ra0 essid ***** key *******************"
WLAN_INTERFACES=(ra0)
INTERFACES=(lo eth0 ra0)
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
But when I try to connect it just returns "Error, ra0: timed out".
I have also tried modifying rc.local (appropriately i think), but that seems to time-out too.
This wouldn't be so bad if I had the option to connect by ethernet, but that doesnt work either! It also times out, just like the wireless. I don't think it is the router, as all the other computers in the house work fine, both wired and wireless. But I don't think it's a driver issue either, as I can see all the AP's in kismet, and also I used the ethernet port when I first installed Arch a couple of months ago. I assume it's dodgy config files or clashing commands or something, but I've looked in the wiki and other forums etc, and I can't see what I'm doing wrong.
Any help would be very appreciated.
Thank you.
PaulMake sure about the addresses for the LAN the router at your parents is using - they are not necessarily the same.
-
How to use airport express wired and wireless at the same time
Hi,
I currently have FiOS with Verizon, they ran a coax cable to the Verizon router. I didn't ask them to switch to CAT6 cable since I have an airport extreme base station and an airport express base station (both are the newest generation). I ran a CAT6 cable from the Verizon FiOS router to my AEBS (extreme) to make it the default wireless router. The Verizon router and extreme are in one room. Now, the Airport express is in my living. I'd like to extend the wireless network from the extreme. However, I can't seem to find a way to use both wired and wireless from the airport express at the same time. It's now either via wired, or wiresless. So is there a way to get both work?Can you tell us if you used Apple's instructions for a "roaming" network?
http://support.apple.com/kb/HT4260
Although the instructions picture a 2nd AirPort Extreme in the illustrations, the setup instructions would be exactly the same for an AirPort Express. -
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.
ThanksHi 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 -
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,
SI 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 -
NAC differentiate wired and wireless users
We have NAC installed and are using it control both wired and wireless ports. We also have the Guest Server that we are in the process of implementing. We would like for only users that are created via the Guest Server to use both wired and wireless access, which we are able to do @ this point. Our issue is that we have a Guest account that we would like to restrict to only wired users, this account is posted in conference rooms for internet access only. We don't want this account to be able to be used on the wireless network, is this possible?
Thanks,
JoeWhere are those conference room guests authenticating currently ? Through Nac ? Through webauth on a switch linked with NGS ?
Nicolas
Maybe you are looking for
-
RFC destination error in posting 3rd party payment in 4.7 FI system
Hi, We are running in to a problem when we are processing a payment via transaction F110S in our R/3 4.7 system for Financials. We are integrating our Financial system with ECC6.0 for HCM. We receive 3rd party invoice from HCM successfully via ALE an
-
All of the inserts in audio tracks have stopped working
I do get audio input, but the inserts do not work. Does anyone know the fix for this? Thanks, Murray
-
I want to call an existing function returning string_rtn. Would I be able to call this function in an update statement as is without rewriting the function to return just the a_string. I am using Oracle 10.2.0.4.0 . Basically i want to call this fun
-
Linking multiple tables and Trying to insert records into Detail
Hello, I have been struggling with this one for years... Work Order, Employee Labor, and Materials. I then create a group headers using the Location field from the Work Order table. I then create another Group, suppress the group name, and insert s
-
Can I make PDFs expire after a specified period of time?
I found some older articles elsewhere, but they are fairly dated. Is it still possible to generate, created etc. PDF's and specify a time period that it would then expire? SO PDF1 is set to expire in 1month, PDF2 is set to expire in 6 weeks etc. Than