Networking 101
Have a web server, it has two ethers. One IP is set a public address the other is set to a private IP.The server is running DNS and I have SunScreen fire wall software installed. I have a cisco 675 router and is the default router. I want to put my other machines behind the firewall and assigned them a private networking IP. Not using DHCP at this piont. I have a 3m superstack switch which every thing is being connected to the one switch including the router. I have tried to set up a static and dynamic NAT rule between the private and the public network and assigned NT box a private IP. Nothing I do is working. The OS is Solaris 7 on the server.
I would appreciate any help I can get in finishing my set-up
Mark
No need for a(nother) router!
<pre>high-speed Internet access -> Airport Extreme Base Station WAN port
Airport Extreme Base Station LAN Ethernet port -> HUB
Airport Extreme Base Station USP port -> USB printer
HUB -> main computer
HUB -> Ethernet printer
Laptop connects wirelessly.</pre>
I've seen a report that says that one can't configure the Airport Extreme Base Station to act as a DHCP server on its Ethernet LAN port -- and this is consistent with the screens shown here... So it's possible that you'll have to assign your main computer and Ethernet printer static IP-addresses on the AEBS' Ethernet LAN; but I'd try it without, first.
Similar Messages
-
Networking 101 to a pc based domain
Newbie here,
Can anyone teach me or send a link to a step by step instruction guide for understanding mac OSX networking and setting up a connection to a corporate domain? Screenshots would be great. Remote desktop? How to add to domain? etcI think I understand that you have the printer somehow connected to the router? However, I thought the printer was a USB device. What happens you connect the printer to a PC USB port and turn on printer sharing?
As best I could determine at Belkin's web site is that your router doesn't even have a USB port. Exactly how is the printer connected to the router?
What happens if the printer is connected to the Mac's USB port directly? Does it work then?
Here are some articles that may help:
http://docs.info.apple.com/article.html?artnum=301768
http://docs.info.apple.com/article.html?artnum=301397
http://www.ifelix.co.uk/tech/index.html
http://www.macwindows.com/
The physical setup should be:
1. Cable or DSL service line connects to IN port on the modem.
2. The modem's WAN port is connected via Ethernet (CAT5) cable to the WAN port on the router.
3. Each Ethernet device (each computer) is connected to the router's LAN ports by Ethernet cable.
The router should be configured to have its DHCP server activated (this is usually the default configuration.) Each computer should have its network preferences configured to use DHCP.
Most routers issue IP addresses in the 192.168.xxx.xxx range. If you have a valid connection between the computer and router then the computer's IP address will be in this range. If the IP address begins with 169.xxx.xxx.xxx, then it's an invalid address and means the computer is not connecting properly to the router. The router should get its IP address from your ISP service.
After all the hardware connections have been setup you should configure the computers' network preferences then turn everything off for at least one minute. Then in sequence first turn on the modem and wait until the status lights indicate a connection to the ISP; next turn on the router and wait until its status light indicates communication with the modem; last turn on the computers. -
Home network 101: How to get 3 Macs to feed photos off the same external HD
This has to be a super simple setup but the search I did reveals a lot pf pieces to the puzzle but not the basic idea.
I currently have three Macs running 10.4.10: an old iMac G3 500Mhz, an iMac G4 1Ghz and an iBook 1.4Ghz. They are all connected via generic ethernet cables (RJ45) I installed throughout the house to a Lynksis BEFSR41 EtherFast Cable router in the garage. That one is then connected to a Motorola SB5101 cable modem for our internet connection. Each computer lives happily by itself at the moment and when I need to transfer something from one to the other I temporarily turn Personal Sharing On, do the transfer and then turn it off again. So Sharing is Off 99% of the time because I read that even though they all have passwords, this is the safest way to keep them.
One problem that we are facing more and more is that four people in the family use these computers and we each have downloaded pictures in iPhoto on all computers. This creates a bit of a mess so I would like to have a central 500GB hard drive next to the router in the garage that would host all the iPhoto files and be permanently visible by each computer.
I read that the new Airport would offer this possibility. However, I am not interested in wireless because I have already run ethernet cable throughout the house. So my questions are these:
- What is the best way to accomplish this scenario in terms of safety, speed and cost?
- Ethernet cable is still safer and faster then wireless, correct?
- I will be replacing the old iMac G3 with a new 24inch intel one as soon as they are introduced, hopefully this week. Would this old G3 one be useful as a server that the 500GB drive would be attached to? Or would its bus speed be so slow it would bring iPhoto on each machine down to a crawl? It wouldn't really be doing any work, just sit there with the 500 attached to its Firewire port so I can add it to the Lynksis chain.
Is the Lynksis now too old and slow to allow 3 computer to access that HD at firewire speed? If so, what would be a better choice?
Again, the three key factors and speed, safety nd cost. (But then again that's always the case, isn't it???) I really appreciate any help or redirection to existing threads or articles that I might have missed.
Thank you very much.
BoNot likely...
They'd need your Passwords & Usernames, then your Router would have to Forward Port 548 to a particular machine, then the icing on the cake is that almost all of this is being done by Bots looking for Internet Explorer running from Drive C:\ and an OS that can execute .exe, .pif, .com, .bat, .etc. files!
So, if your Macs & Router aren't set up to allow you access from the outside world, nobody else can either... if they are then it's still very unlikely someone else could, but if you want to be as anally paranoid as me, then...
ClamXAV, free Virus scanner...
http://www.clamxav.com/
Little Snitch, stops/alerts outgoing stuff...
http://www.obdev.at/products/littlesnitch/index.html
HenWen/Snort combo, that is a free MAJOR Firewall...
http://seiryu.home.comcast.net/henwen.html
Then the venerable old Brickhoues/Flying Buttress Firewall...
http://personalpages.tds.net/~brian_hill/downloads.html
WaterRoof is a firewall management frontend with bandwidth tuning, NAT setup, port redirection, dynamic rules tracking, predefined rule sets, wizard, logs, statistics and other features.
http://www.macupdate.com/info.php/id/23317
But really... no need to worry yourself YET with a Mac... I once challenged a group of people that poo-pooed Mac Security, by running a Machine as Root, gave them the IP, and a few more hints, and nobody got in at all. (There weren't many attempts though). -
Need help choosing how to extend my existing home network to my detached garage?
I have done as much research as possible on this scenario but cannot seem to match the ideal solution with my wants. Perhaps I simply just do not understand networking as well as I thought I did. Either way, any helpful information or suggestions are greatly appreciated.
Objective: Extend my wireless network to my detached garage.
My current ISP provider is Time Warner Cable. I have RoadRunner Extreme, which in my area gives consistent speeds of 50 Mbps download and 5 Mbps upload when I am connected via ethernet cable. When I upgraded to the "Extreme" package i found out I was forced to use their Motorola SB6580 ... its a DOCSIS 3.0 cable modem + wireless router. I was able to access the Motorola's setup options on the internet and I disabled the wireless function. This has allowed me to use my Time Capsule as the primary router to provide wireless access on my home network. I have not had any issues with this setup and is my preferred way to operate.
I have recently moved my home office to the 2nd story of my detached garage and need to extend my wireless network to meet the demands of all my gear. I have decided to achieve this goal by going with one of the following 3 options:
1.) enable the wireless function on the motorola modem making it the primary router. move my time capsule out to the office and use it in bridge mode. However I do not think I understand bridge mode correctly. I thought the secondary router (in this case my TC) in bridge mode needed to be connected w/ an ethernet cable at all times to enable this feature? If I understand similar networking discussions I will lose the ethernet ports with this option? If this isnt called Bridge mode once i take away the ethernet cable what is it "technically" called?
2.) buy a 2nd airport extreme base station and create the same type of wireless network extension setup. The difference here is I would leave my motorola's wireless features disabled, use 2 apple products that speak apples to apples wirelessly and relieve myself of all the headaches involved with a neopolitan setup. This seems like the obvious choice b/c Apple products are much more user friendly, but I dont want to spend the $200 on a new router if I can achieve a comparable setup by just enabling the equipment I already have.
3.) use either of these 2 scenarios above & go buy a 150' ethernet cable to join them together. if this is the case wouldnt a $50 hub suffice on the end of the cable? I dont necessarily need to have wireless, just reliable connectivity. I can access the existing wireless network now, but download speeds are not great and things really start to slow down when i have multiple clients connected. I would rather not have to drill through exterior walls, bury conduit and install learn how to install data wall plates, but i will if this is the pros far out way the cons.
Current modem/router placement: if standing @ the front door of my 1 story house facing out towards the street my motorola modem/router is in the front right-hand corner of the house.
Distance location of the detached garage office setup: if standing @ my front door my my work area is in the far back left corner of my property. it is approx 175' from the router and on the 2nd story of the garage. I said 150' cable earlier b/c i could relocate the router to a bedroom on the opposite end of the house, however this would eleminate the current wired status of the items connected to it and I would prefer to keep them wired in.
clients connected in the house: (4) apple tv's; Roku; Xbox; Wii; Playstation 3; (2) Lenovo laptops; iPad; (2) Blackberry's; (2) iPhones; iPod touch; (2) wireless netowrk printers; (2) smart tv's ... a handful of these are currently wired into the time capsule now which provides an uninterupted viwing experience for the MLB package. This of course trumps all opportunity costs involved with moving the router. There is nothing more frustrating than a screen buffering in the botton of the 9th inning after you've sat there for 3 hours.
clients connected in the office: (2) 27" imacs; apple tv; iPad; network printer; Wii; Harmony Link universal remote; Mac Book Pro ...
I have approx 5TB of digital media that is shared over the network via shared iTunes libraries that I would like to access as well. iCloud helps with all of our household gadgets as far as acessibility but with all the backups going on simutaneously it also creates headaches when you need the throughput. I need to do a better job of managing those settings. nonetheless, I would like some guidance on the best way to extend my current netowrk, suggestions for better scenarios i did not mention and thus am probably not aware of and any networking 101 schooling if it doesnt sound like i understand the way bridge mode/network extension works. sorry for the long post and thank you for your time & help.Ethernet beats all other solutions hands down..
A single ethernet connection from wherever is the closest point in the house to the garage office... wins. You can plug a router working as AP and switch or pure switch on to it. Get a cabler in to do the job.. and they can probably figure it out and do the whole job whilst you scatch your head.. yes you will pay for it.. but a cabler knows how to do it. And most likely leave the inside network exactly as it is. Since office is important to be reliable.. there is one and one only reliable method.. ethernet.
If the garage and house are on one electrical circuit.. which is doubtful if it is a separate building then EOP adapters can often work well.. They do not handle earth leakage protection, breakers (rather than fuses) or meters at all well.. but if they are simply all connected to power.. behind the same meter and using old fashioned fuse box.. EOP rated at 200mbps or some now are 500mbps can work reasonably well. Speed about the same as wireless at its best but if it works when installed will generally not change with the weather, moon, and wind direction which wireless is liable to do.
Wireless bridging.. hmm avoid if possible. For reliable connection no.. apple products can do wireless repeater but as you mentioned that turns off the ethernet ports except for the Express.. that is the only unit you can use as a bridge and plug a switch into it. Why Apple why??
So if you want to bridge two points by wireless buy specialised wireless bridge.. that means an AP in the house plugged into the existing network.. and AP unit perhaps on the outside of the garage.. or in windows if you have a window in the house that looks at a window in your office. Look at products from companies like ubiquiti.. they are not too expensive but professional equipment and designed for precisely this kind of work.
Hence the reliability is dramatically better than domestic stuff.. and will require a lot less work to maintain the link.
Conclusion.. wire it.
Unless you rent the house.. an investment in ethernet cabling install once properly and forget .. beats every other solution even if it costs x5 as other solutions. -
Global Correlation and Network Participation - what's the value of it ???
Hi security gurus!
Can someone please shed me more light on the value of Global Correlation and Network Participation available at IPS 7.x
We've enabled it on the clients IPS appliances and now the only information I see is some cryptic reports seen at IDM gadgets.
It says that the reputation filtering is 100% under Percentage of malicious packets indentified. So what ?
How would I know exactly what those packets are and where did they come from?
Other metrics are Global Correlation inspection and Traditional IPS Detection techniques are 0%
What does it mean? Doesn't something work ? Why are they 0% ?
How is this normally sold to the customer if there's no credible information about it?
EugeneHi,
I think this link will help you http://docs.oracle.com/cd/B14117_01/network.101/b10776/listener.htm -
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? -
Officejet Pro 8600 Plus - wired w/static IP address, stops working & need to reboot the computer
This happened a few times before and I went through it with tech and the guy told me that this setting had to be changed because the static IP. The printer is setup for DHCP but the static IP is better however the printer looks to renew the DHCP and loses connection with the network. I run the HP Print and Scan Doctor and everything comes up OK. Once I reboot the computer everything works OK, after sitting idle for awhile the printer doesn't respond to print jobs. Both the printer and computer are wired to the same ethernet switch. Does anyone know the setting that needs to be changed in the printer configuration so this does not happen again.
Thanks,
We don't get much help from HPTroubleshooting could be considered "jumping through hoops", it is process of elimination. We are at the diagnostic stage of our troubleshooting, thus I would like to determine functionality and ensure the printer works when connected directly to the router and not with the switch.
Please bear in mind, the Officejet 8600 is a consumer printer. Generally speaking, A.K.A - Networking 101, the printer should be connected either wirelessly to a router, or with an Ethernet cable, not to a switch or hub.
Let me know if we can eliminate the switch as a possible cause, by trying it without the switch.
Thanks.
Please click the Thumbs up icon below to thank me for responding.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Please click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution.
Sunshyn2005 - I work on behalf of HP -
Login error in creating new module
I am trying to create a new module to deploy my source objects. The Design repository is on a window client and the Runtime repository is on a UNIX server.
On step 3 of the wizard for creating a data source(New module Wizard) my connection info for the DB link is the following: the name of the user owning the schema where my source tables are located, the name of the host server and the name of the SID as service name. This db is on the UNIX server.
When I enter that user name and password I get a ORA-12514 TNS: no listener error message.
I have triple check all my TNS and listener files on the server and they are all working properly.
Am I using the proper user login for creating a new module. What user login I should be using??
Any help will be greatly appreciated.
Thanks a bunch!
AKAK,
OWB supports two ways of connecting to databases: SQL*Net Connect String or Host Name, you see these choices as a radio button list when creating DB link. SQL*Net Connect String relies on local tnsnames.ora and is more prone to error. We recommend using Host Name connection, where you specify host, port and service name, which is what you are trying to do. Test your connection outside of OWB by typing in your command prompt on the client machine:
sqlplus user/pw@host:port/db_service
If you need further details see this database doc: http://download-west.oracle.com/docs/cd/B14117_01/network.101/b10775/naming.htm#i498306
Nikolai Rochnik -
This was posted in the Security forum a week or so back, but has had no response. Perhaps one of the Oracle DB Product Managers could respond...
Can anyone clarify the current state of DBMS_CRYPTO_TOOLKIT in 10g? It is still in 10gDB, but not documented, and appears to require the Oracle Security Server. Has this package been updated under the hood to work with Identity Management / Certificate Authority?
I am trying to find the "least headache" approach to PKI (RSA) encryption in the DB. While integration all the way up the stack to SSO and certificates would be nice, it is not really necessary in this context. I can certainly use Java Stored Procedures that implement RSA, but that would not even come close to the speed of the native FFIs that were used with DBMS_CRYPTO_TOOLKIT.
Bottom Line :
1) Is anyone doing RSA in the database using DBMS_CRYPTO_TOOLKIT?
2) Does anyone have a workable alternative using native PL/SQL, Java Stored Procedures or C? (I am aware of DBCrypt, but it is a fairly "canned" system and appears to lack the flexibility I need)Hi, both the "dbms_obfuscation_toolkit" and "dbms_crypto" are available and functioning in 10g, but "dbms_crypto" should be used. See this link for details:
http://download-west.oracle.com/docs/cd/B14117_01/network.101/b10773/apdvncrp.htm#1006258
Cheers, Peter -
File Sharing with AirPort or Ethernet - Both connected, what happens?
Here's the scenario. Two Macs are connected using AirPort to the local wireless network, with an AirPort Extreme Base Station as the router. The two Macs are also connected directly, to each other, using an Ethernet cable.
One Mac is set up to do +File Sharing+ (to be the file server). On the (other) "client" Mac, I want to connect to the "file server" Mac using the direct Ethernet connection (because it is much faster than even 802.11n wireless). For all other networking, including Internet access, I want both Macs to use the AirPort connection. Use Ethernet connection only for file sharing between the two Macs.
*Is there some way to force file sharing to use the Ethernet connection* (not AirPort), when both are available and connected?
I don't want to be too long-winded about what I have tried, but here is want I have observed. If I go to System Preferences Network pane and +Set Service Order+ (under the gear icon) so that AirPort appears first, both Internet access and file sharing use AirPort. If I set it so that Ethernet appears first in the sidebar, file sharing uses Ethernet and Internet access does not work (unless I also enable +Internet Sharing+ on file server Mac). If I switch the service order back to AirPort being first, Internet access goes back to using AirPort, but if I leave the file sharing over Ethernet connected, it continues to work over Ethernet (sometimes); it does not seem consistent. Sometimes it cuts off. Other times, the Internet access over AirPort become problematic.
Secondary question - *Is there some place I can look to see which connection is being used* at a particular moment, for file sharing?
The way I checked was by transferring a large folder and noting the estimated transfer time. A few hours is from AirPort being used; 20-30 minutes is Ethernet being used.
If it matters, the +file server+ Mac is a Power Mac G5 with Leopard and the client Mac is a Mac mini with Snow Leopard. I can make it happen, but the process is convoluted and it does not seem to work reliably or consistently, with either the file sharing or Internet access connection becoming inaccessible until I restart. I am willing to accept +UNIX command line magic+ as a solution; it just has to be a method that works consistently, and is understandable.I don't understand what you just wrote. There is no category or forum in Apple Discussions that is generally about networking. There is a +Getting Online and Networking+ forum under Snow Leopard, and I suppose I could have posted it there. But if you have advice related to this topic question, I thinks it's OK for you to post a response in this topic, in this forum and category. If you don't know, that's fine. I don't know either. That's why I'm asking.
And this question is hardly +Networking 101+. -
When we write this command
alter user username quota 0 on tablespace_name;
does not this free this user from any space so he is not able to create any new database object or insert any new rows because he has no space ?
I tried to create new table and inserted new rows to that newly created table within this user schema ,and it was accepted I wonder why ?
any axplanation whould be hankful.If a table has been created in a user's schema, then another user with 0 quota on that tablespace may still be able to add records. The quota limitation doesn't apply to the 'inserter', unless the insert requires additional memory allocation (datafile is set to automatically grow), and the growth would excced the set quota for the object owner.
I haven't tested this, but this is where I got this info in the past:
http://download-west.oracle.com/docs/cd/B13789_01/network.101/b10773/admusers.htm#1006231
-Chuck -
Intel iMac/PowerMac G4--Sharing a Printer
I've been reading a bunch of posts, and just get confused, so hopefully someone can help me out with a simple answer. Have a PowerMac G4 running OS 9.1, with 2 printers connected with a USB hub (HP LaserJet 1320 and a Canon i860); have just added an Intel iMac (OS X 10.4.9) to the office. What do I need to be able to use both printers from either computer? It seems like a router is the answer, but I'm not totally clear on that. It would also be nice to be able to access the internet with both as well (Verizon DSL), but if only the iMac can do that, that's ok. We have an Asante FH305 ethernet hub, so I don't know if that can be used in some way . . . I'd like to do this the simplest way, for the least amount of $$ (doesn't everyone?)
Thanks.Let's take a quick breeze through networking 101 for non-majors (grin). Some printers are made to be shared over a network - they have an ethernet interface and are generally called network printers. Other printers, generally known as dedicated printers, are made to be connected to a single computer. Today the preferred interface for these printers is USB. A USB printer cannot be connected to an ethernet hub, only a network printer can.
Recognizing that lots of us have multiple computers but no pressing need for multiple printers, Apple built into its OS the ability to share a dedicated printer with other computers that are on the home network. That's what I recommended to you.
There is a second option that can work for some printers. There's a device called a USB print server. It connects to an ethernet network and, as its name implies, lets you connect USB printers to it. It doesn't work for all printers though. I used to own the same Canon printer you do and I have an Airport Extreme which includes a USB port for printer serving. It worked fine. Whether your laser printer would though, I cannot say. -
Any best practice for Key Management with Oracle Obfuscation?
Hi,
I was wondering if anyone is aware if there are any best practices regarding key management when using Oracle's DBMS_OBFUSCATION_TOOLKIT? I'm particularly interested in how we can protect the encryption/decryption key that we would use.
Thanks,
JimOracle offers this document, which includes a strategy for what you're after:
http://download-west.oracle.com/docs/cd/B13789_01/network.101/b10773/apdvncrp.htm#1006234
-Chuck -
What's the best authentication model for a PRO*C process?
We presently have a system where 5 or so PRO*C-based processes on remote nodes (HP OpenVMS) connect to a database (RH Linux) using Oracle Client and insert data. The current authentication method is for the C based program to read a connection string from a file and use that string to connect via an embedded sqlplus call.
This works fine, however having the string contained in a file isn't all that great an idea, even with the protection we give it. It would be easy for a programmer to recompile & debug the process and read the string, so it's not really all that secure. It also just doesn't seem the best way to do this....
I know this isn't much information to go on, but can anyone suggest a better model for this scenario that avoids putting connection strings and passwords in a file?
Thanks in advancethanks for your helpfull evaluation.
On the security question is it possible for you to use the Oracle Wallet ?
http://www.stanford.edu/dept/itss/docs/oracle/10g/network.101/b10772/asowalet.htm
Please ask more on that thread or post a question to the section : for security Questions/issues.
Forum Home » Technologies » Security
Hope this helps.
Regards,
Hub -
Using VPD (Virtual Private Database) with Discoverer for Dummies
Firstly could you please excuse me for the title of the thread, but it’s all I could come up with. For those of you who are looking at me with a strange look of disgust, please view thread that started it all: BIS vs DBI vs Noetix .
Otherwise I’m hoping to gain a greater understanding of how VPD can be used to enhance Discoverer and it’s performance. I've just read that :
“Oracle 8i introduced the notion of a Virtual Private Database (VPD). A VPD offers Fine-Grained Access Control (FGAC) for secure separation of data. This ensures that users only have access to data that pertains to them. Using this option, one could even store multiple companies' data within the same schema, without them knowing about it.
VPD configuration is done via the DBMS_RLS (Row Level Security) package. Select from SYS.V$VPD_POLICY to see existing VPD configuration.”
With Regards to Discoverer, I would like to ask the following:
-When would be best to use VPD in Discoverer?
-Pro’s and Con’s of VPD?
-Tips / Tricks?
-and anything else Michael would like to add (I don’t believe there is a post limit, although this could change in the future)
I've found a few handy links:
http://www.adp-gmbh.ch/ora/security/vpd/index.html
http://www.oracle.com/technology/oramag/oracle/04-mar/o24tech_security.html
As Metalink support would say : I Looking forward to your ‘Positive’ comments. ;-)
LanceLance,
You sure do raise some interesting questions here.
I've noticed from some of your previous posts that you are using views to link Discoverer through to apps. I have found this very interesting document that may help with your queries; http://www.oracle.com/technology/deploy/security/oracle9ir2/pdf/VPD9ir2twp.pdf
If you scroll down to the section "Additional VPD Capabilities" and read the following sub-topics, this might enable you to base your Discoverer reports on views that contain VPD policies.
I trust "My Positive Comment" may help!!
Merry Christmas
Si ;-)
P.s This also may come in handy if running 10g http://www.stanford.edu/dept/itss/docs/oracle/10g/network.101/b10773/apdvpoli.htm
Message was edited by:
Simon Pittaway
Maybe you are looking for
-
How do you set the duration of images before importing into a timeline
Is there a way to do a batch import of images where once I place them into a video group I can set the duration of each image automatically by detereming the overall timelime lenght as opposed to manually setting the duration of each image?
-
Batch Listing Metadata for Offline Files
Hello all - I'm using Premiere CC 2014 on OSX. I'm trying to do a batch list export of the metadata for a few dozen offline clips in my project. Here are the details: I need the filenames and video ins and outs (NOT the media start and end) for all o
-
Reader 11.0.10 crashes after upgrade to Yosemite.
I upgraded from Mtn Lion to Yosemite a week ago, and shortly after the upgrade, Adobe Reader crashed. I did an update to version 11.0.10; same result. Cleaned app from computer and after re-install, same result. Sometimes Reader opens for a few se
-
Spanning one image across two monitors?
If this has been asked before, I applogize. It is probably a simple solution, but, not sure if it is possible. I am using an Imac 17" Display, 160 Gig HDD, 1 Gig RAM and an external 19" monitor (as an extended desktop) I have downloaded some of the s
-
dear all in balance interest caluclation we have to assign interest cycle eg monthly, yearly , when we assign interest cycle the system will caluclate interest based on interest cycle monthly or yearly but my client requirement he dont want assign