Evolve OS

I’ve taken a big interest in Evolve OS (Yes, another Linux distro). So much so, that I’ve started to package for the distro. This is a first for me! Although I’ve always wanted to get involved in the Linux community I never found the right fit. So far I’m having fun learning and having a good time meeting people.

eOS not getting DHCP offer

Elementary OS 0.3 has been giving me some problems. The most annoying one is in regards to the wifi. For some reason it will constantly fail to get an ipv4 address:

Oct  5 19:55:57 moniker NetworkManager[766]: <info> Activation (wlan0) starting connection 'Ryman'
Oct  5 19:55:57 moniker NetworkManager[766]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Oct  5 19:55:57 moniker NetworkManager[766]: <info> NetworkManager state is now CONNECTING
Oct  5 19:55:57 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Oct  5 19:55:57 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Oct  5 19:55:57 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Oct  5 19:55:57 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Oct  5 19:55:57 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Oct  5 19:55:57 moniker NetworkManager[766]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Oct  5 19:55:57 moniker NetworkManager[766]: <info> Activation (wlan0/wireless): access point 'Ryman' has security, but secrets are required.
Oct  5 19:55:57 moniker NetworkManager[766]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Oct  5 19:55:57 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Oct  5 19:55:57 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Oct  5 19:55:57 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Oct  5 19:55:57 moniker NetworkManager[766]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Oct  5 19:55:57 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Oct  5 19:55:57 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Oct  5 19:55:57 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Oct  5 19:55:57 moniker NetworkManager[766]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Oct  5 19:55:57 moniker NetworkManager[766]: <info> Activation (wlan0/wireless): connection 'Ryman' has security, and secrets exist.  No new secrets needed.
Oct  5 19:55:57 moniker NetworkManager[766]: <info> Config: added 'ssid' value 'Ryman'
Oct  5 19:55:57 moniker NetworkManager[766]: <info> Config: added 'scan_ssid' value '1'
Oct  5 19:55:57 moniker NetworkManager[766]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Oct  5 19:55:57 moniker NetworkManager[766]: <info> Config: added 'psk' value '<omitted>'
Oct  5 19:55:57 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Oct  5 19:55:57 moniker NetworkManager[766]: <info> Config: set interface ap_scan to 1
Oct  5 19:55:57 moniker NetworkManager[766]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Oct  5 19:55:58 moniker kernel: [ 1223.760070] wlan0: authenticate with ac:b3:13:05:97:a0
Oct  5 19:55:57 moniker wpa_supplicant[861]: message repeated 6 times: [ wlan0: CTRL-EVENT-SCAN-STARTED ]
Oct  5 19:55:58 moniker wpa_supplicant[861]: wlan0: SME: Trying to authenticate with ac:b3:13:05:97:a0 (SSID='Ryman' freq=2412 MHz)
Oct  5 19:55:58 moniker NetworkManager[766]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Oct  5 19:55:58 moniker wpa_supplicant[861]: wlan0: Trying to associate with ac:b3:13:05:97:a0 (SSID='Ryman' freq=2412 MHz)
Oct  5 19:55:58 moniker kernel: [ 1223.783718] wlan0: send auth to ac:b3:13:05:97:a0 (try 1/3)
Oct  5 19:55:58 moniker kernel: [ 1223.785681] wlan0: authenticated
Oct  5 19:55:58 moniker kernel: [ 1223.787082] wlan0: associate with ac:b3:13:05:97:a0 (try 1/3)
Oct  5 19:55:58 moniker NetworkManager[766]: <info> (wlan0): supplicant interface state: authenticating -> associating
Oct  5 19:55:58 moniker wpa_supplicant[861]: wlan0: Associated with ac:b3:13:05:97:a0
Oct  5 19:55:58 moniker kernel: [ 1223.797823] wlan0: RX AssocResp from ac:b3:13:05:97:a0 (capab=0xc31 status=0 aid=3)
Oct  5 19:55:58 moniker kernel: [ 1223.797952] wlan0: associated
Oct  5 19:55:58 moniker kernel: [ 1223.798372] cfg80211: Calling CRDA for country: US
Oct  5 19:55:58 moniker NetworkManager[766]: <info> (wlan0): supplicant interface state: associating -> associated
Oct  5 19:55:58 moniker kernel: [ 1223.810768] ath: EEPROM regdomain: 0x8348
Oct  5 19:55:58 moniker kernel: [ 1223.810792] ath: EEPROM indicates we should expect a country code
Oct  5 19:55:58 moniker kernel: [ 1223.810799] ath: doing EEPROM country->regdmn map search
Oct  5 19:55:58 moniker kernel: [ 1223.810805] ath: country maps to regdmn code: 0x3a
Oct  5 19:55:58 moniker kernel: [ 1223.810810] ath: Country alpha2 being used: US
Oct  5 19:55:58 moniker kernel: [ 1223.810814] ath: Regpair used: 0x3a
Oct  5 19:55:58 moniker kernel: [ 1223.810821] ath: regdomain 0x8348 dynamically updated by country IE
Oct  5 19:55:58 moniker kernel: [ 1223.810880] cfg80211: Regulatory domain changed to country: US
Oct  5 19:55:58 moniker kernel: [ 1223.810886] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct  5 19:55:58 moniker kernel: [ 1223.810893] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
Oct  5 19:55:58 moniker kernel: [ 1223.810899] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
Oct  5 19:55:58 moniker kernel: [ 1223.810906] cfg80211:   (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct  5 19:55:58 moniker kernel: [ 1223.810912] cfg80211:   (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct  5 19:55:58 moniker kernel: [ 1223.810918] cfg80211:   (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct  5 19:55:58 moniker kernel: [ 1223.810924] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
Oct  5 19:55:58 moniker kernel: [ 1223.810930] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm)
Oct  5 19:55:58 moniker wpa_supplicant[861]: wlan0: WPA: Key negotiation completed with ac:b3:13:05:97:a0 [PTK=CCMP GTK=CCMP]
Oct  5 19:55:58 moniker wpa_supplicant[861]: wlan0: CTRL-EVENT-CONNECTED - Connection to ac:b3:13:05:97:a0 completed [id=0 id_str=]
Oct  5 19:55:58 moniker NetworkManager[766]: <info> (wlan0): supplicant interface state: associated -> 4-way handshake
Oct  5 19:55:58 moniker NetworkManager[766]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Oct  5 19:55:58 moniker NetworkManager[766]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'Ryman'.
Oct  5 19:55:58 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Oct  5 19:55:58 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Oct  5 19:55:58 moniker NetworkManager[766]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Oct  5 19:55:58 moniker NetworkManager[766]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Oct  5 19:55:58 moniker NetworkManager[766]: <info> dhclient started with pid 2355
Oct  5 19:55:58 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Oct  5 19:55:58 moniker avahi-daemon[636]: Withdrawing address record for fe80::260a:64ff:feca:99b5 on wlan0.
Oct  5 19:55:58 moniker avahi-daemon[636]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::260a:64ff:feca:99b5.
Oct  5 19:55:58 moniker avahi-daemon[636]: Interface wlan0.IPv6 no longer relevant for mDNS.
Oct  5 19:55:58 moniker dhclient: Internet Systems Consortium DHCP Client 4.2.4
Oct  5 19:55:58 moniker dhclient: Copyright 2004-2012 Internet Systems Consortium.
Oct  5 19:55:58 moniker dhclient: All rights reserved.
Oct  5 19:55:58 moniker dhclient: For info, please visit https://www.isc.org/software/dhcp/
Oct  5 19:55:58 moniker dhclient:
Oct  5 19:55:58 moniker NetworkManager[766]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Oct  5 19:55:58 moniker dhclient: Listening on LPF/wlan0/24:0a:64:ca:99:b5
Oct  5 19:55:58 moniker dhclient: Sending on   LPF/wlan0/24:0a:64:ca:99:b5
Oct  5 19:55:58 moniker dhclient: Sending on   Socket/fallback
Oct  5 19:55:58 moniker dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 (xid=0x6135a9e8)
Oct  5 19:56:00 moniker avahi-daemon[636]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::260a:64ff:feca:99b5.
Oct  5 19:56:00 moniker avahi-daemon[636]: New relevant interface wlan0.IPv6 for mDNS.
Oct  5 19:56:00 moniker avahi-daemon[636]: Registering new address record for fe80::260a:64ff:feca:99b5 on wlan0.*.
Oct  5 19:56:01 moniker avahi-daemon[636]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::260a:64ff:feca:99b5.
Oct  5 19:56:01 moniker avahi-daemon[636]: Joining mDNS multicast group on interface wlan0.IPv6 with address 2605:e000:9605:9b00:f9c7:f399:6860:beec.
Oct  5 19:56:01 moniker avahi-daemon[636]: Registering new address record for 2605:e000:9605:9b00:f9c7:f399:6860:beec on wlan0.*.
Oct  5 19:56:01 moniker avahi-daemon[636]: Withdrawing address record for fe80::260a:64ff:feca:99b5 on wlan0.
Oct  5 19:56:01 moniker dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4 (xid=0x6135a9e8)
Oct  5 19:56:01 moniker avahi-daemon[636]: Registering new address record for 2605:e000:9605:9b00:260a:64ff:feca:99b5 on wlan0.*.
Oct  5 19:56:05 moniker dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5 (xid=0x6135a9e8)
Oct  5 19:56:10 moniker dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5 (xid=0x6135a9e8)
Oct  5 19:56:15 moniker dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14 (xid=0x6135a9e8)
Oct  5 19:56:29 moniker dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13 (xid=0x6135a9e8)
Oct  5 19:56:42 moniker dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12 (xid=0x6135a9e8)
Oct  5 19:56:43 moniker NetworkManager[766]: <warn> (wlan0): DHCPv4 request timed out.
Oct  5 19:56:43 moniker NetworkManager[766]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 2355
Oct  5 19:56:43 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
Oct  5 19:56:43 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 4 of 5 (IPv4 Configure Timeout) started...
Oct  5 19:56:43 moniker NetworkManager[766]: <info> (wlan0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Oct  5 19:56:43 moniker NetworkManager[766]: <info> NetworkManager state is now DISCONNECTED
Oct  5 19:56:43 moniker NetworkManager[766]: <info> Marking connection 'Ryman' invalid.
Oct  5 19:56:43 moniker kernel: [ 1269.418280] wlan0: deauthenticating from ac:b3:13:05:97:a0 by local choice (reason=3)
Oct  5 19:56:43 moniker NetworkManager[766]: <warn> Activation (wlan0) failed for connection 'Ryman'
Oct  5 19:56:43 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 4 of 5 (IPv4 Configure Timeout) complete.
Oct  5 19:56:43 moniker NetworkManager[766]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Oct  5 19:56:43 moniker NetworkManager[766]: <info> (wlan0): deactivating device (reason 'none') [0]
Oct  5 19:56:43 moniker avahi-daemon[636]: Withdrawing address record for 2605:e000:9605:9b00:f9c7:f399:6860:beec on wlan0.
Oct  5 19:56:43 moniker avahi-daemon[636]: Leaving mDNS multicast group on interface wlan0.IPv6 with address 2605:e000:9605:9b00:f9c7:f399:6860:beec.
Oct  5 19:56:43 moniker avahi-daemon[636]: Joining mDNS multicast group on interface wlan0.IPv6 with address 2605:e000:9605:9b00:260a:64ff:feca:99b5.
Oct  5 19:56:43 moniker avahi-daemon[636]: Withdrawing address record for 2605:e000:9605:9b00:260a:64ff:feca:99b5 on wlan0.
Oct  5 19:56:43 moniker avahi-daemon[636]: Leaving mDNS multicast group on interface wlan0.IPv6 with address 2605:e000:9605:9b00:260a:64ff:feca:99b5.
Oct  5 19:56:43 moniker avahi-daemon[636]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::260a:64ff:feca:99b5.
Oct  5 19:56:43 moniker avahi-daemon[636]: Registering new address record for fe80::260a:64ff:feca:99b5 on wlan0.*.
Oct  5 19:56:43 moniker avahi-daemon[636]: Withdrawing address record for fe80::260a:64ff:feca:99b5 on wlan0.
Oct  5 19:56:43 moniker avahi-daemon[636]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::260a:64ff:feca:99b5.
Oct  5 19:56:43 moniker avahi-daemon[636]: Interface wlan0.IPv6 no longer relevant for mDNS.
Oct  5 19:56:43 moniker kernel: [ 1269.436627] cfg80211: Calling CRDA to update world regulatory domain
Oct  5 19:56:43 moniker wpa_supplicant[861]: wlan0: CTRL-EVENT-DISCONNECTED bssid=ac:b3:13:05:97:a0 reason=3 locally_generated=1
Oct  5 19:56:43 moniker NetworkManager[766]: <warn> Connection disconnected (reason -3)
Oct  5 19:56:43 moniker NetworkManager[766]: <info> (wlan0): supplicant interface state: completed -> disconnected
Oct  5 19:56:44 moniker wpa_supplicant[861]: wlan0: CTRL-EVENT-SCAN-STARTED
Oct  5 19:56:44 moniker NetworkManager[766]: <warn> Connection disconnected (reason -3)
Oct  5 19:56:44 moniker kernel: [ 1269.451051] cfg80211: World regulatory domain updated:
Oct  5 19:56:44 moniker kernel: [ 1269.451062] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct  5 19:56:44 moniker kernel: [ 1269.451067] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct  5 19:56:44 moniker kernel: [ 1269.451071] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct  5 19:56:44 moniker kernel: [ 1269.451074] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Oct  5 19:56:44 moniker kernel: [ 1269.451077] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct  5 19:56:44 moniker kernel: [ 1269.451080] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct  5 19:56:45 moniker avahi-daemon[636]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::260a:64ff:feca:99b5.
Oct  5 19:56:45 moniker avahi-daemon[636]: New relevant interface wlan0.IPv6 for mDNS.
Oct  5 19:56:45 moniker avahi-daemon[636]: Registering new address record for fe80::260a:64ff:feca:99b5 on wlan0.*.

But then for no apparent reason I’ll finish the DHCP request and get an ipv4 address.

Oct  5 19:57:20 moniker NetworkManager[766]: <info> Activation (wlan0) starting connection 'Ryman'
Oct  5 19:57:20 moniker NetworkManager[766]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Oct  5 19:57:20 moniker NetworkManager[766]: <info> NetworkManager state is now CONNECTING
Oct  5 19:57:20 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Oct  5 19:57:20 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Oct  5 19:57:20 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Oct  5 19:57:20 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Oct  5 19:57:20 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Oct  5 19:57:20 moniker NetworkManager[766]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Oct  5 19:57:20 moniker NetworkManager[766]: <info> Activation (wlan0/wireless): access point 'Ryman' has security, but secrets are required.
Oct  5 19:57:20 moniker NetworkManager[766]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Oct  5 19:57:20 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Oct  5 19:57:20 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Oct  5 19:57:20 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Oct  5 19:57:20 moniker NetworkManager[766]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Oct  5 19:57:20 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Oct  5 19:57:20 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Oct  5 19:57:20 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Oct  5 19:57:20 moniker NetworkManager[766]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Oct  5 19:57:20 moniker NetworkManager[766]: <info> Activation (wlan0/wireless): connection 'Ryman' has security, and secrets exist.  No new secrets needed.
Oct  5 19:57:20 moniker NetworkManager[766]: <info> Config: added 'ssid' value 'Ryman'
Oct  5 19:57:20 moniker NetworkManager[766]: <info> Config: added 'scan_ssid' value '1'
Oct  5 19:57:20 moniker NetworkManager[766]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Oct  5 19:57:20 moniker NetworkManager[766]: <info> Config: added 'psk' value '<omitted>'
Oct  5 19:57:20 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Oct  5 19:57:20 moniker NetworkManager[766]: <info> Config: set interface ap_scan to 1
Oct  5 19:57:20 moniker NetworkManager[766]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Oct  5 19:57:21 moniker kernel: [ 1306.891365] wlan0: authenticate with ac:b3:13:05:97:a0
Oct  5 19:57:20 moniker wpa_supplicant[861]: message repeated 3 times: [ wlan0: CTRL-EVENT-SCAN-STARTED ]
Oct  5 19:57:21 moniker wpa_supplicant[861]: wlan0: SME: Trying to authenticate with ac:b3:13:05:97:a0 (SSID='Ryman' freq=2412 MHz)
Oct  5 19:57:21 moniker NetworkManager[766]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Oct  5 19:57:21 moniker wpa_supplicant[861]: wlan0: Trying to associate with ac:b3:13:05:97:a0 (SSID='Ryman' freq=2412 MHz)
Oct  5 19:57:21 moniker kernel: [ 1306.914260] wlan0: send auth to ac:b3:13:05:97:a0 (try 1/3)
Oct  5 19:57:21 moniker kernel: [ 1306.916547] wlan0: authenticated
Oct  5 19:57:21 moniker kernel: [ 1306.917507] wlan0: associate with ac:b3:13:05:97:a0 (try 1/3)
Oct  5 19:57:21 moniker NetworkManager[766]: <info> (wlan0): supplicant interface state: authenticating -> associating
Oct  5 19:57:21 moniker wpa_supplicant[861]: wlan0: Associated with ac:b3:13:05:97:a0
Oct  5 19:57:21 moniker kernel: [ 1306.927789] wlan0: RX AssocResp from ac:b3:13:05:97:a0 (capab=0xc31 status=0 aid=3)
Oct  5 19:57:21 moniker kernel: [ 1306.927885] wlan0: associated
Oct  5 19:57:21 moniker kernel: [ 1306.928040] cfg80211: Calling CRDA for country: US
Oct  5 19:57:21 moniker NetworkManager[766]: <info> (wlan0): supplicant interface state: associating -> associated
Oct  5 19:57:21 moniker kernel: [ 1306.937730] ath: EEPROM regdomain: 0x8348
Oct  5 19:57:21 moniker kernel: [ 1306.937741] ath: EEPROM indicates we should expect a country code
Oct  5 19:57:21 moniker kernel: [ 1306.937745] ath: doing EEPROM country->regdmn map search
Oct  5 19:57:21 moniker kernel: [ 1306.937748] ath: country maps to regdmn code: 0x3a
Oct  5 19:57:21 moniker kernel: [ 1306.937752] ath: Country alpha2 being used: US
Oct  5 19:57:21 moniker kernel: [ 1306.937754] ath: Regpair used: 0x3a
Oct  5 19:57:21 moniker kernel: [ 1306.937758] ath: regdomain 0x8348 dynamically updated by country IE
Oct  5 19:57:21 moniker kernel: [ 1306.937784] cfg80211: Regulatory domain changed to country: US
Oct  5 19:57:21 moniker kernel: [ 1306.937787] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct  5 19:57:21 moniker kernel: [ 1306.937791] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
Oct  5 19:57:21 moniker kernel: [ 1306.937795] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
Oct  5 19:57:21 moniker kernel: [ 1306.937799] cfg80211:   (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct  5 19:57:21 moniker kernel: [ 1306.937803] cfg80211:   (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct  5 19:57:21 moniker kernel: [ 1306.937807] cfg80211:   (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct  5 19:57:21 moniker kernel: [ 1306.937810] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
Oct  5 19:57:21 moniker kernel: [ 1306.937814] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm)
Oct  5 19:57:21 moniker wpa_supplicant[861]: wlan0: WPA: Key negotiation completed with ac:b3:13:05:97:a0 [PTK=CCMP GTK=CCMP]
Oct  5 19:57:21 moniker wpa_supplicant[861]: wlan0: CTRL-EVENT-CONNECTED - Connection to ac:b3:13:05:97:a0 completed [id=0 id_str=]
Oct  5 19:57:21 moniker NetworkManager[766]: <info> (wlan0): supplicant interface state: associated -> 4-way handshake
Oct  5 19:57:21 moniker NetworkManager[766]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Oct  5 19:57:21 moniker NetworkManager[766]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'Ryman'.
Oct  5 19:57:21 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Oct  5 19:57:21 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Oct  5 19:57:21 moniker NetworkManager[766]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Oct  5 19:57:21 moniker NetworkManager[766]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Oct  5 19:57:21 moniker NetworkManager[766]: <info> dhclient started with pid 2364
Oct  5 19:57:21 moniker avahi-daemon[636]: Withdrawing address record for fe80::260a:64ff:feca:99b5 on wlan0.
Oct  5 19:57:21 moniker avahi-daemon[636]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::260a:64ff:feca:99b5.
Oct  5 19:57:21 moniker avahi-daemon[636]: Interface wlan0.IPv6 no longer relevant for mDNS.
Oct  5 19:57:21 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Oct  5 19:57:21 moniker dhclient: Internet Systems Consortium DHCP Client 4.2.4
Oct  5 19:57:21 moniker dhclient: Copyright 2004-2012 Internet Systems Consortium.
Oct  5 19:57:21 moniker dhclient: All rights reserved.
Oct  5 19:57:21 moniker dhclient: For info, please visit https://www.isc.org/software/dhcp/
Oct  5 19:57:21 moniker dhclient:
Oct  5 19:57:21 moniker NetworkManager[766]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Oct  5 19:57:21 moniker dhclient: Listening on LPF/wlan0/24:0a:64:ca:99:b5
Oct  5 19:57:21 moniker dhclient: Sending on   LPF/wlan0/24:0a:64:ca:99:b5
Oct  5 19:57:21 moniker dhclient: Sending on   Socket/fallback
Oct  5 19:57:21 moniker dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 (xid=0x1d858457)
Oct  5 19:57:23 moniker avahi-daemon[636]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::260a:64ff:feca:99b5.
Oct  5 19:57:23 moniker avahi-daemon[636]: New relevant interface wlan0.IPv6 for mDNS.
Oct  5 19:57:23 moniker avahi-daemon[636]: Registering new address record for fe80::260a:64ff:feca:99b5 on wlan0.*.
Oct  5 19:57:24 moniker dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8 (xid=0x1d858457)
Oct  5 19:57:24 moniker avahi-daemon[636]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::260a:64ff:feca:99b5.
Oct  5 19:57:24 moniker avahi-daemon[636]: Joining mDNS multicast group on interface wlan0.IPv6 with address 2605:e000:9605:9b00:260a:64ff:feca:99b5.
Oct  5 19:57:24 moniker avahi-daemon[636]: Registering new address record for 2605:e000:9605:9b00:260a:64ff:feca:99b5 on wlan0.*.
Oct  5 19:57:24 moniker avahi-daemon[636]: Withdrawing address record for fe80::260a:64ff:feca:99b5 on wlan0.
Oct  5 19:57:25 moniker avahi-daemon[636]: Registering new address record for 2605:e000:9605:9b00:f9c7:f399:6860:beec on wlan0.*.
Oct  5 19:57:32 moniker dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20 (xid=0x1d858457)
Oct  5 19:57:52 moniker dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8 (xid=0x1d858457)
Oct  5 19:58:00 moniker dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14 (xid=0x1d858457)
Oct  5 19:58:06 moniker NetworkManager[766]: <warn> (wlan0): DHCPv4 request timed out.
Oct  5 19:58:06 moniker NetworkManager[766]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 2364
Oct  5 19:58:06 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
Oct  5 19:58:06 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 4 of 5 (IPv4 Configure Timeout) started...
Oct  5 19:58:06 moniker NetworkManager[766]: <info> (wlan0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Oct  5 19:58:06 moniker NetworkManager[766]: <info> NetworkManager state is now DISCONNECTED
Oct  5 19:58:06 moniker NetworkManager[766]: <info> Marking connection 'Ryman' invalid.
Oct  5 19:58:06 moniker NetworkManager[766]: <warn> Activation (wlan0) failed for connection 'Ryman'
Oct  5 19:58:06 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 4 of 5 (IPv4 Configure Timeout) complete.
Oct  5 19:58:06 moniker NetworkManager[766]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Oct  5 19:58:06 moniker NetworkManager[766]: <info> (wlan0): deactivating device (reason 'none') [0]
Oct  5 19:58:06 moniker avahi-daemon[636]: Withdrawing address record for 2605:e000:9605:9b00:f9c7:f399:6860:beec on wlan0.
Oct  5 19:58:06 moniker avahi-daemon[636]: Withdrawing address record for 2605:e000:9605:9b00:260a:64ff:feca:99b5 on wlan0.
Oct  5 19:58:06 moniker avahi-daemon[636]: Leaving mDNS multicast group on interface wlan0.IPv6 with address 2605:e000:9605:9b00:260a:64ff:feca:99b5.
Oct  5 19:58:06 moniker avahi-daemon[636]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::260a:64ff:feca:99b5.
Oct  5 19:58:06 moniker avahi-daemon[636]: Registering new address record for fe80::260a:64ff:feca:99b5 on wlan0.*.
Oct  5 19:58:06 moniker avahi-daemon[636]: Withdrawing address record for fe80::260a:64ff:feca:99b5 on wlan0.
Oct  5 19:58:06 moniker avahi-daemon[636]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::260a:64ff:feca:99b5.
Oct  5 19:58:06 moniker avahi-daemon[636]: Interface wlan0.IPv6 no longer relevant for mDNS.
Oct  5 19:58:06 moniker kernel: [ 1352.427481] wlan0: deauthenticating from ac:b3:13:05:97:a0 by local choice (reason=3)
Oct  5 19:58:06 moniker wpa_supplicant[861]: wlan0: CTRL-EVENT-DISCONNECTED bssid=ac:b3:13:05:97:a0 reason=3 locally_generated=1
Oct  5 19:58:06 moniker NetworkManager[766]: <warn> Connection disconnected (reason -3)
Oct  5 19:58:06 moniker NetworkManager[766]: <info> (wlan0): supplicant interface state: completed -> disconnected
Oct  5 19:58:06 moniker NetworkManager[766]: <warn> Connection disconnected (reason -3)
Oct  5 19:58:06 moniker kernel: [ 1352.445570] cfg80211: Calling CRDA to update world regulatory domain
Oct  5 19:58:07 moniker wpa_supplicant[861]: wlan0: CTRL-EVENT-SCAN-STARTED
Oct  5 19:58:07 moniker kernel: [ 1352.460330] cfg80211: World regulatory domain updated:
Oct  5 19:58:07 moniker kernel: [ 1352.460340] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct  5 19:58:07 moniker kernel: [ 1352.460345] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct  5 19:58:07 moniker kernel: [ 1352.460349] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct  5 19:58:07 moniker kernel: [ 1352.460352] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Oct  5 19:58:07 moniker kernel: [ 1352.460355] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct  5 19:58:07 moniker kernel: [ 1352.460358] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct  5 19:58:08 moniker avahi-daemon[636]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::260a:64ff:feca:99b5.
Oct  5 19:58:08 moniker avahi-daemon[636]: New relevant interface wlan0.IPv6 for mDNS.
Oct  5 19:58:08 moniker avahi-daemon[636]: Registering new address record for fe80::260a:64ff:feca:99b5 on wlan0.*.
Oct  5 19:59:42 moniker NetworkManager[766]: <info> Activation (wlan0) starting connection 'Ryman'
Oct  5 19:59:42 moniker NetworkManager[766]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Oct  5 19:59:42 moniker NetworkManager[766]: <info> NetworkManager state is now CONNECTING
Oct  5 19:59:42 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Oct  5 19:59:42 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Oct  5 19:59:42 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Oct  5 19:59:42 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Oct  5 19:59:42 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Oct  5 19:59:42 moniker NetworkManager[766]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Oct  5 19:59:42 moniker NetworkManager[766]: <info> Activation (wlan0/wireless): access point 'Ryman' has security, but secrets are required.
Oct  5 19:59:42 moniker NetworkManager[766]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Oct  5 19:59:42 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Oct  5 19:59:42 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Oct  5 19:59:42 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Oct  5 19:59:42 moniker NetworkManager[766]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Oct  5 19:59:42 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Oct  5 19:59:42 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Oct  5 19:59:42 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Oct  5 19:59:42 moniker NetworkManager[766]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Oct  5 19:59:42 moniker NetworkManager[766]: <info> Activation (wlan0/wireless): connection 'Ryman' has security, and secrets exist.  No new secrets needed.
Oct  5 19:59:42 moniker NetworkManager[766]: <info> Config: added 'ssid' value 'Ryman'
Oct  5 19:59:42 moniker NetworkManager[766]: <info> Config: added 'scan_ssid' value '1'
Oct  5 19:59:42 moniker NetworkManager[766]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Oct  5 19:59:42 moniker NetworkManager[766]: <info> Config: added 'psk' value '<omitted>'
Oct  5 19:59:42 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Oct  5 19:59:42 moniker NetworkManager[766]: <info> Config: set interface ap_scan to 1
Oct  5 19:59:42 moniker NetworkManager[766]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Oct  5 19:59:43 moniker kernel: [ 1449.350093] wlan0: authenticate with ac:b3:13:05:97:a0
Oct  5 19:59:42 moniker wpa_supplicant[861]: message repeated 4 times: [ wlan0: CTRL-EVENT-SCAN-STARTED ]
Oct  5 19:59:43 moniker wpa_supplicant[861]: wlan0: SME: Trying to authenticate with ac:b3:13:05:97:a0 (SSID='Ryman' freq=2412 MHz)
Oct  5 19:59:43 moniker NetworkManager[766]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Oct  5 19:59:43 moniker wpa_supplicant[861]: wlan0: Trying to associate with ac:b3:13:05:97:a0 (SSID='Ryman' freq=2412 MHz)
Oct  5 19:59:43 moniker kernel: [ 1449.372928] wlan0: send auth to ac:b3:13:05:97:a0 (try 1/3)
Oct  5 19:59:43 moniker kernel: [ 1449.375449] wlan0: authenticated
Oct  5 19:59:43 moniker kernel: [ 1449.376417] wlan0: associate with ac:b3:13:05:97:a0 (try 1/3)
Oct  5 19:59:43 moniker NetworkManager[766]: <info> (wlan0): supplicant interface state: authenticating -> associating
Oct  5 19:59:43 moniker wpa_supplicant[861]: wlan0: Associated with ac:b3:13:05:97:a0
Oct  5 19:59:43 moniker kernel: [ 1449.386773] wlan0: RX AssocResp from ac:b3:13:05:97:a0 (capab=0xc31 status=0 aid=7)
Oct  5 19:59:43 moniker kernel: [ 1449.386877] wlan0: associated
Oct  5 19:59:43 moniker kernel: [ 1449.387044] cfg80211: Calling CRDA for country: US
Oct  5 19:59:43 moniker NetworkManager[766]: <info> (wlan0): supplicant interface state: associating -> associated
Oct  5 19:59:43 moniker kernel: [ 1449.395044] ath: EEPROM regdomain: 0x8348
Oct  5 19:59:43 moniker kernel: [ 1449.395055] ath: EEPROM indicates we should expect a country code
Oct  5 19:59:43 moniker kernel: [ 1449.395059] ath: doing EEPROM country->regdmn map search
Oct  5 19:59:43 moniker kernel: [ 1449.395063] ath: country maps to regdmn code: 0x3a
Oct  5 19:59:43 moniker kernel: [ 1449.395066] ath: Country alpha2 being used: US
Oct  5 19:59:43 moniker kernel: [ 1449.395068] ath: Regpair used: 0x3a
Oct  5 19:59:43 moniker kernel: [ 1449.395071] ath: regdomain 0x8348 dynamically updated by country IE
Oct  5 19:59:43 moniker kernel: [ 1449.395103] cfg80211: Regulatory domain changed to country: US
Oct  5 19:59:43 moniker kernel: [ 1449.395106] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct  5 19:59:43 moniker kernel: [ 1449.395110] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
Oct  5 19:59:43 moniker kernel: [ 1449.395113] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
Oct  5 19:59:43 moniker kernel: [ 1449.395116] cfg80211:   (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct  5 19:59:43 moniker kernel: [ 1449.395119] cfg80211:   (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct  5 19:59:43 moniker kernel: [ 1449.395122] cfg80211:   (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct  5 19:59:43 moniker kernel: [ 1449.395126] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
Oct  5 19:59:43 moniker kernel: [ 1449.395129] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm)
Oct  5 19:59:44 moniker wpa_supplicant[861]: wlan0: WPA: Key negotiation completed with ac:b3:13:05:97:a0 [PTK=CCMP GTK=CCMP]
Oct  5 19:59:44 moniker NetworkManager[766]: <info> (wlan0): supplicant interface state: associated -> 4-way handshake
Oct  5 19:59:44 moniker wpa_supplicant[861]: wlan0: CTRL-EVENT-CONNECTED - Connection to ac:b3:13:05:97:a0 completed [id=0 id_str=]
Oct  5 19:59:44 moniker NetworkManager[766]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Oct  5 19:59:44 moniker NetworkManager[766]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'Ryman'.
Oct  5 19:59:44 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Oct  5 19:59:44 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Oct  5 19:59:44 moniker NetworkManager[766]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Oct  5 19:59:44 moniker NetworkManager[766]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Oct  5 19:59:44 moniker NetworkManager[766]: <info> dhclient started with pid 2374
Oct  5 19:59:44 moniker avahi-daemon[636]: Withdrawing address record for fe80::260a:64ff:feca:99b5 on wlan0.
Oct  5 19:59:44 moniker avahi-daemon[636]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::260a:64ff:feca:99b5.
Oct  5 19:59:44 moniker avahi-daemon[636]: Interface wlan0.IPv6 no longer relevant for mDNS.
Oct  5 19:59:44 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Oct  5 19:59:44 moniker dhclient: Internet Systems Consortium DHCP Client 4.2.4
Oct  5 19:59:44 moniker dhclient: Copyright 2004-2012 Internet Systems Consortium.
Oct  5 19:59:44 moniker dhclient: All rights reserved.
Oct  5 19:59:44 moniker dhclient: For info, please visit https://www.isc.org/software/dhcp/
Oct  5 19:59:44 moniker dhclient:
Oct  5 19:59:44 moniker NetworkManager[766]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Oct  5 19:59:44 moniker dhclient: Listening on LPF/wlan0/24:0a:64:ca:99:b5
Oct  5 19:59:44 moniker dhclient: Sending on   LPF/wlan0/24:0a:64:ca:99:b5
Oct  5 19:59:44 moniker dhclient: Sending on   Socket/fallback
Oct  5 19:59:44 moniker dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 (xid=0x7718e8c)
Oct  5 19:59:44 moniker dhclient: DHCPREQUEST of 192.168.1.7 on wlan0 to 255.255.255.255 port 67 (xid=0x7718e8c)
Oct  5 19:59:44 moniker dhclient: DHCPOFFER of 192.168.1.7 from 192.168.1.1
Oct  5 19:59:44 moniker dhclient: DHCPACK of 192.168.1.7 from 192.168.1.1
Oct  5 19:59:44 moniker dhclient: bound to 192.168.1.7 -- renewal in 1617 seconds.
Oct  5 19:59:44 moniker NetworkManager[766]: <info> (wlan0): DHCPv4 state changed preinit -> bound
Oct  5 19:59:44 moniker NetworkManager[766]: <info>   address 192.168.1.7
Oct  5 19:59:44 moniker NetworkManager[766]: <info>   prefix 24 (255.255.255.0)
Oct  5 19:59:44 moniker NetworkManager[766]: <info>   gateway 192.168.1.1
Oct  5 19:59:44 moniker NetworkManager[766]: <info>   hostname 'moniker'
Oct  5 19:59:44 moniker NetworkManager[766]: <info>   nameserver '8.8.8.8'
Oct  5 19:59:44 moniker NetworkManager[766]: <info>   nameserver '8.8.4.4'
Oct  5 19:59:44 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Oct  5 19:59:44 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
Oct  5 19:59:44 moniker avahi-daemon[636]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.7.
Oct  5 19:59:44 moniker avahi-daemon[636]: New relevant interface wlan0.IPv4 for mDNS.
Oct  5 19:59:44 moniker avahi-daemon[636]: Registering new address record for 192.168.1.7 on wlan0.IPv4.
Oct  5 19:59:45 moniker NetworkManager[766]: <info> (wlan0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Oct  5 19:59:45 moniker NetworkManager[766]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
Oct  5 19:59:45 moniker NetworkManager[766]: <info> (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Oct  5 19:59:45 moniker NetworkManager[766]: <info> NetworkManager state is now CONNECTED_GLOBAL
Oct  5 19:59:45 moniker NetworkManager[766]: <info> Policy set 'Ryman' (wlan0) as default for IPv4 routing and DNS.
Oct  5 19:59:45 moniker NetworkManager[766]: <info> DNS: starting dnsmasq...
Oct  5 19:59:45 moniker NetworkManager[766]: <warn> dnsmasq not available on the bus, can't update servers.
Oct  5 19:59:45 moniker NetworkManager[766]: <error> [1412564385.316200] [nm-dns-dnsmasq.c:396] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
Oct  5 19:59:45 moniker NetworkManager[766]: <warn> DNS: plugin dnsmasq update failed
Oct  5 19:59:45 moniker NetworkManager[766]: <info> Writing DNS information to /sbin/resolvconf
Oct  5 19:59:45 moniker dnsmasq[2377]: started, version 2.68 cache disabled
Oct  5 19:59:45 moniker dnsmasq[2377]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth
Oct  5 19:59:45 moniker dnsmasq[2377]: DBus support enabled: connected to system bus
Oct  5 19:59:45 moniker dnsmasq[2377]: warning: no upstream servers configured
Oct  5 19:59:45 moniker NetworkManager[766]: <info> Activation (wlan0) successful, device activated.
Oct  5 19:59:45 moniker dbus[536]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Oct  5 19:59:45 moniker NetworkManager[766]: <warn> dnsmasq appeared on DBus: :1.71
Oct  5 19:59:45 moniker NetworkManager[766]: <info> Writing DNS information to /sbin/resolvconf
Oct  5 19:59:45 moniker dnsmasq[2377]: setting upstream servers from DBus
Oct  5 19:59:45 moniker dnsmasq[2377]: using nameserver 8.8.4.4#53
Oct  5 19:59:45 moniker dnsmasq[2377]: using nameserver 8.8.8.8#53
Oct  5 19:59:45 moniker dbus[536]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct  5 19:59:45 moniker logger: [CapNetAssist] DetectCaptivePortal script triggered
Oct  5 19:59:45 moniker logger: [CapNetAssist] Display set
Oct  5 19:59:45 moniker logger: [CapNetAssist] HTTP response is: 204
Oct  5 19:59:45 moniker logger: [CapNetAssist] Connection already established
Oct  5 19:59:45 moniker whoopsie[997]: message repeated 60 times: [ offline]
Oct  5 19:59:45 moniker whoopsie[997]: online
Oct  5 19:59:45 moniker avahi-daemon[636]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::260a:64ff:feca:99b5.
Oct  5 19:59:45 moniker avahi-daemon[636]: New relevant interface wlan0.IPv6 for mDNS.
Oct  5 19:59:45 moniker avahi-daemon[636]: Registering new address record for fe80::260a:64ff:feca:99b5 on wlan0.*.
Oct  5 19:59:48 moniker wpa_supplicant[861]: wlan0: CTRL-EVENT-SCAN-STARTED
Oct  5 19:59:52 moniker ntpdate[2454]: adjust time server 91.189.89.199 offset -0.069916 sec

Interestingly enough when I get an ipv6 address I can’t get on the internet with it. Almost like it’s not being routed properly. No idea what’s going on but it’s annoying to say the least.

Time Warner Cable Is The Worst

This chat took place over the course of an hour. No answers came fast, and often the answers contradicted what I was told by the previous person.

info: Thank you for contacting Time Warner Cable. A representative will be with you shortly.
info: You are now chatting with Robert.
info: ** Please do not share credit card information in this window. If credit card information is required, the agent will push a separate and secure form to you.  **
Robert: Please give me a moment to review the notes you provided and I’ll be right with you. If at the end of this chat you would like to provide feedback, please click on “End Chat” and the survey will load in this same window.
Greg Ryman: Hello Robert, I just activated my new modem and it’s still showing that it’s getting a DOCSIS 2.0 signal and not a DOCSIS 3.0 signal which is needed for the new 300Mbps speed.
Robert: Ok let me look into that for you
Robert: So looking at the account infromation I am seeing that the Max speeds have not reached your area yet.
Greg Ryman: Well, that is fairly frustrating. I’ve had to contact TWC several times just to get my modem and each time I was told something different. And then it took contacting TWC three times just to get the modem activated. And now you’re telling me that the new speed isn’t even available.
Robert: I apologize for this inconvenience.
Greg Ryman: What is the ETA for the Maxx speed?
Robert: I am looking into this.
Robert: Can I please take 2 to 3 minutes to find the exact timeframe for you?
Greg Ryman: yes
Robert: Thank you very much.
Robert: I apologize for making you wait.
Robert: Greg the Max speeds have been upgraded in your area. I apologize for the miscommunication. The reason you haven’t gotten the upgraded speeds is due to a billing code issue.
Robert: I can get you over to a billing specialist and leave detailed notes for them to get you set up with that. If you are wanting me to get you to one.
Greg Ryman: ok
Robert: Thank you Greg.
Robert: In order to better assist you I would need to transfer you to another department. It would be my pleasure getting you over there immediately. One Moment Please….
info: Please wait while I transfer the chat to the appropriate group.
info: You are now chatting with Jerry.
info: ** Please do not share credit card information in this window. If credit card information is required, the agent will push a separate and secure form to you.  **
Jerry: Hello!
Greg Ryman: Hello
Greg Ryman: I’m not sure what notes are on the account, however the issue for me not getting my new Maxx speed is a billing code problem.
Greg Ryman: “Greg the Max speeds have been upgraded in your area. I apologize for the miscommunication. The reason you haven’t gotten the upgraded speeds is due to a billing code issue.”
Jerry: okay
Jerry: I will be glad to help you with this issue.
Jerry: let me check
Jerry: Please give me a couple of minutes while I check the details.
Greg Ryman: ok
Jerry: Please help me with the service address
Greg Ryman: *****  Anaheim CA 92804
Jerry: Thank you
Jerry: Thank you for the patience
Jerry: I have checked the details and would like to inform you that the maxx speed code is not available for your area.
Greg Ryman: This is like musical chairs. Sometimes it’s available, and sometimes it’s not.
Greg Ryman: Can you ask a supervisor to double check your information?
Greg Ryman: I’ve had to speak with almost a dozen people to get this upgrade to where it’s at, and now you’re telling me it’s not available.
Jerry: I’ll be right with you.
Jerry: I have checked the details from my end and the maxx speed is not yet launched in your area
Jerry: As soon as it is available you will receive a notification
Greg Ryman: I’ve received notifications telling me to upgrade my modem, which I finally did. And then tech support said it’s ready, but my billing code was incorrect. Now you’re telling me that it’s not available.
Greg Ryman: Do you have an ETA on when it will become available?
Jerry: We are aware of this and the technicians are working to get the available  at the earliest.
Jerry: Give it some time and you should be able to get all the features and functions just fine.
Jerry: Not an exact time frame, but usually when something like this is affecting a lot of people, we get it fixed pretty quick.
Greg Ryman: I have another question. I was supposed to receive a $300 gift card from purchasing the Intelligent Home system but I never did.
Jerry: Okay, I will transfer this chat to our promotion department and they will help you with the details
Jerry: please be online
info: Please wait while I transfer the chat to the appropriate group.
info: You are now chatting with Frederick.
info: ** Please do not share credit card information in this window. If credit card information is required, the agent will push a separate and secure form to you.  **
Frederick: Thank you for contacting Time Warner Cable online sales, home of the best triple play offer, My name is Frederick, how may I help you today?
Greg Ryman: I never received my $300 gift card after purchasing the Intelligent Home system.
Frederick: Let me check it on the account
Frederick: may I have the phone number also associated with it
Greg Ryman: *** *** ****
Frederick: Thank you for waiting. I’ll be with you in just a moment.
Frederick: And the zip code
Greg Ryman: 92804
Frederick: I’m sorry for the delay. I’ll be right with you.
Frederick: Thank you for waiting. I’ll be with you in just a moment.
Frederick: I’m sorry for the delay. I’ll be right with you.
Frederick: I’ll be right with you.
Frederick: In order for me to access the account, please verify the last 4 digit of your SSN
Greg Ryman: *****
Frederick: Ok perfect, I’m going to access the account now
Frederick: Since you mentioned that your main concern is the $300 gift card
Frederick: If  I may ask did you receive a redemption code in your email?
Greg Ryman: Yes, and I registered for it
Greg Ryman: TWCBetterReward@tristarfulfillment.com Apr 28 to me You’ve successfully registered for your reward card. Thank you for registering for your reward card.
Frederick: I’m sorry for the delay. I’ll be right with you.
Frederick: I’ll be right with you.
Frederick: Thank you for waiting. I’ll be with you in just a moment.
Frederick: Thank you for waiting. I’ll be with you in just a moment.
Frederick: Upon checking here there was no updates on the account
Frederick: For confirmation of the gift card let me give the number of our customer care department for further assistance
Greg Ryman: So you can’t assist me?
Frederick: We do not have access on the accurate information on the gift card
Greg Ryman: I’ve been through 4 different departments today for three different issues, and none of them were resolved. Now I have to call yet another department?
Frederick: I’m sorry for the delay. I’ll be right with you.
Greg Ryman: What is the number?
Frederick: ***** ***** 2253

Time Warner Cable Chat

I had the “pleasure” of chatting with my ISP for the 4th time over the same issue. It seems that this time I’ll finally get my modem and receive the upgraded speed I’m paying for. I don’t know where this “Samantha” is, but I highly doubt she (if it is a she) is in the U.S. This usually wouldn’t be a problem, but if a company can’t have people who communicate effectively, I would rather take my business elsewhere.

info: Thank you for contacting Time Warner Cable. A representative will be with you shortly.
info: You are now chatting with Samantha Vermont.
info: ** Please do not share credit card information in this window. If credit card information is required, the agent will push a separate and secure form to you.  **
Samantha Vermont: Hello, how are you doing?
You: Hello, I’ve had conflicting information about my account. I was told to schedule a tech to come out and upgrade my service to 300Mbps. When I called, someone told me that there was a charge if a tech came out, but I could do it myself if they shipped me the modem. I called back another time, and the rep told me that my modem was already DOCSIS 3 compliant, so there was no need to upgrade the hardware. Then I saw there was a scheduled appointment for the 30th, but that seems to have been removed.
Samantha Vermont: Greg, just to confirm, are you trying to remove the Technician visit for you?
You: No… I’m just trying to figure out what is happening or what needs to happen.
You: No one scheduled a tech visit with me, however I did see an appointment scheduled for the 30th. But I do not see the appointment anymore.
Samantha Vermont: Greg, I understand your question.
Samantha Vermont: May I place the chat on hold for two minutes while I check this information for you?
You: yes
Samantha Vermont: Thank you.
Samantha Vermont: I see that there is no Technician visit created on your account for 30th.
You: Ok, so what do I need to do to upgrade to the 300Mbps plan that I received an email about?
Samantha Vermont: I see that the Modem which you are currently using will support only up to ***** Mbps.
You: Alright, well then that make 4 different people from TWC telling me 4 different things.
Samantha Vermont: Apologize for the inconvenience caused to you.
You: Is all that is needed is a new modem then?
Samantha Vermont: Please give me a moment while I isolate this issue.
Samantha Vermont: Sorry for the delay in response.
Samantha Vermont: I am working on your issue.
You: I pulled up the manual for the modem I have, the Arris TG862 and it’s DOCSIS 3.0 compliant.
You: DOCSIS 3.0 8×4 channels should give 343.04 Mbps according to the RFC.
Samantha Vermont: Greg, I am checking for the availability of Maxx speeds on your account.
Samantha Vermont: Please be online.
Samantha Vermont: Greg, please be online while I check with the details for you.
You: I am online, chatting with you.
Samantha Vermont: Okay.
Samantha Vermont: Appreciate your patience.
Samantha Vermont: I have spoken with an Supervisor regarding your issue.
Samantha Vermont: As per our conversation with our Supervisor, we see that you are in the Maxx available area.
Samantha Vermont: The Modem Arris TG862 which you are using now is not compatible for ***** Mbps because it works under single band Modem ( 2.5 Mhz).
Samantha Vermont: However, we are shipping an Dual band Modem ( 5 Mhz ) for you at free of cost which will support up to ***** Mbps speeds.
Samantha Vermont: You will receive this Modem with in 5-6 working days.
You: Ok
Samantha Vermont: When you receive the new Modem, you will get the ***** Mbps speeds.
Samantha Vermont: Is that okay with you?
You: Yes, that is fine.
Samantha Vermont: Okay.
You: I do have another question in regards to my Intelligent Home system.
Samantha Vermont: I do apologize for any inconvenience or miscommunication caused to you.
Samantha Vermont: Sure.
Samantha Vermont: Go ahead.
You: When I ordered the service I was told that I would receive a $300 gift card, which would neutralize the installation costs. I never received that card.
Samantha Vermont: I understand your question.
Samantha Vermont: We have a dedicated department to deal with this issue.
Samantha Vermont: Once we are done with the Shipping process, I will transfer this chat to the concerned department.
You: ok
Samantha Vermont: Thank you.
Samantha Vermont: Sorry for the delay in response.
Samantha Vermont: Here is your order number: **************
Samantha Vermont:
You: Alright
Samantha Vermont: As we are Technical support, we will work for round the clock.
Samantha Vermont: In order to resolve the issue of Intelligent Home, the department is not available at this is not the business time, they will be available at 9AM-5PM.
Samantha Vermont: However, I will provide you with the contact number so that you can directly call to them and can ask your queries regarding the Intelligent home.
Samantha Vermont: Is that okay with you?
You: Yes
Samantha Vermont: Here is the contact number: 1-888-892-2253
Samantha Vermont:
Samantha Vermont: Once you get connected with them, they will surely help you out with this.
You: Alright, thank you
Samantha Vermont: It’s my pleasure chatting with a customer like you.
Samantha Vermont: Any questions or is there anything else I can help you with today?
You: No, that is it.
Samantha Vermont: Okay.
info: Your chat transcript will be sent to **********@gmail.com at the end of your chat.
Samantha Vermont: Bye and take care!

Setting up secure backups

I’ve decided to move my online storage off Dropbox and as part of this plan, my backups will also now be real backups. I’m moving to SpiderOak for numerous reasons, one of which is the zero knowledge encryption. The other is they like and support Linux, which is a huge plus and really a necessity. They’re also a backup company first, instead of a storage company. Those who know understand what I mean.

https://spideroak.com/download/referral/caced444a30fc855b5da8c1b683bff19

Like always, if you use my referral link it helps me and you. So please do! :)

Scrape site for inventory

While looking for a new carry gun I decided to just scrape the site every morning and email myself the inventory level.

 

root@mail:~# cat scraper.sh 
#!/bin/bash
 
inventory=`curl -s http://www.shootersconnectionstore.com/STI-40-Duty-One-9x19-Lite-Night-Sights-P3225.aspx | grep inventoryDetails`
 
SUBJECT="STI Duty One Inventory"
EMAIL="myemail@gmail.com"
 
echo -e $inventory | mail -a "From: info@mydomain.com" -a "Content-Type: text/html" -s "$SUBJECT" "$EMAIL"

PHP rDNS CSV Generator

Quick script to generate rDNS for the Bluecat Proteus IPAM import.

<?php
 
$minhost=4;
$maxhost=126;
$recordtype = "PTR";
$action = "add";
$arpa = ".10.168.192.in-addr.arpa.";
$ttl = "";
 
if (file_exists("ptr_records.csv")) die ("File already exists\n");
 
$file = fopen("ptr_records.csv", 'w') or die ("Failed to create file\n");
 
for($count = $minhost; $count <= $maxhost; $count++) {
        $text = $action . "," . $count . $arpa . "," . $ttl . "," . $recordtype  . ",192.168.10." . $count . ".domain.com\n";
        file_put_contents("ptr_records.csv",$text,FILE_APPEND);
}
 
fclose($file);
echo "File created\n";
 
?>

AUP Script

This script looks for a string over HTTP in a subnet supplied in CIDR notation

#!/bin/bash
 
function addzeros {
   NUM=$1
   ZS=$2
   NBITS=$(echo "$NUM" | grep -o "[0-9]" | wc -l)
   if (( $NBITS < $ZS )); then
      ZEROS2ADD=$(expr $ZS - $NBITS)
      while (( $ZEROS2ADD << 0 )); do
         NUM="0$NUM"
         ZEROS2ADD=$(expr $ZEROS2ADD - 1)
      done
      echo "$NUM"
   else
      echo $NUM
   fi
}
 
function bin2dec {
   echo "obase=10; ibase=2; $1" | bc
}
function dec2bin {
   echo "obase=2; $1" | bc
}
 
function ipbin2ip {
   cont=1
   for l in $(echo $1 | grep -o [0,1]); do
      VIPTMP[$cont]=$l
      cont=$(expr $cont + 1)
   done
   ONE=`bin2dec $(echo ${VIPTMP[@]:1:8} | tr -d [:space:])`
   TWO=`bin2dec $(echo ${VIPTMP[@]:9:8} | tr -d [:space:])`
   THREE=`bin2dec $(echo ${VIPTMP[@]:17:8} | tr -d [:space:])`
   FOUR=`bin2dec $(echo ${VIPTMP[@]:25:8} | tr -d [:space:])`
   FINALIP=$(echo ${ONE}.${TWO}.${THREE}.${FOUR})
   CONTENT=$(curl -L -m 2 -s $FINALIP| grep -i $SEARCH)
   if [ -z "$CONTENT" ]; then
	echo -n .
   else
	echo $FINALIP" -> "$CONTENT
   fi
}
 
if [ -z $1 ]; then
	echo "Usage: cidrSearch <CIDR> <Search String>"
	echo "Example: cidrSearch 74.125.224.195/30 title"
	exit 0
fi
 
SEARCH=$2
IPCIDR=$1
IP=$(echo $IPCIDR | cut -d"/" -f1)
BITS=$(echo $IPCIDR | cut -d"/" -f2)
 
FST=$(echo $IP | cut -d"." -f1)
FSTBIN=`addzeros $(echo "obase=2; $FST" | bc) 8`
SND=$(echo $IP | cut -d"." -f2)
SNDBIN=`addzeros $(echo "obase=2; $SND" | bc) 8`
TRD=$(echo $IP | cut -d"." -f3)
TRDBIN=`addzeros $(echo "obase=2; $TRD" | bc) 8`
FOH=$(echo $IP | cut -d"." -f4)
FOHBIN=`addzeros $(echo "obase=2; $FOH" | bc) 8`
 
VIP=0.0.0.0
IPBIN="$FSTBIN$SNDBIN$TRDBIN$FOHBIN"
 
i=1
for l in $(echo $IPBIN | grep -o [0,1]); do
   VIPBIN[$i]="$l"
   i=$(expr $i + 1)
done
 
BITSHOST=$(expr 32 - $BITS)
i=$BITSHOST
while (( $i > 0 )); do
   MAXHOSTBIN=1$MAXHOSTBIN
   i=$(expr $i - 1)
done
MAXHOST=$(bin2dec $MAXHOSTBIN)
 
n=$(echo ${VIPBIN[@]:1:$BITS} | tr -d [:space:])
c=$MAXHOST
while (( $c > 0 )); do
   h=$c
   EUREKA=${n}$(addzeros `dec2bin $h` $BITSHOST)
   ipbin2ip "$EUREKA"
   c=$(expr $c - 1)
done

DNS Query Script

We had a customer complaining about their IP address not resolving and slow lookup times. I ended up scripting the lookup which does a dig on the domain and retains the first A record IP and then on subsequent lookups compares the original IP with the one just looked up. Each time the script does a lookup it outputs the query time (similar to ping). When the script detects the IP as having changed, it will exit and print a summary.

Disclaimer:
This is not useful for people doing round-robin DNS balancing.

#!/bin/bash
 
trap ctrl_c INT
 
function ctrl_c() {
 
	find_mean
	printf "\n"
	echo Checked $counter times
	printf "\n"
	echo High: $mshigh ms  Low: $mslow ms  Avg: $msmean ms
	exit
}
 
function find_mean() {
	let "msmean = ($mstotal / $counter)"
}
 
full=`dig $1`
initialIp=`echo "$full" | awk '/ANSWER SECTION/ { getline; print $0 }' | awk '{print $5}'`
ip=$initialIp
 
counter=0
 
while [ "$initialIp" = "$ip" ]; do
	full=`dig $1`
	ip=`echo "$full" | awk '/ANSWER SECTION/ { getline; print $0 }' | awk '{print $5}'`
	msprint=`echo "$full" | awk ' /Query/ {print $4,$5}'`
	mskeep=`echo "$full" | awk ' /Query/ {print $4}'`
 
	if [ -z $mslow ]
		then
			mslow=$mskeep
	fi
	if [ -z $mshigh ]
		then
			mshigh=$mskeep
	fi
	if [ $mskeep -lt  $mslow ]
		then
			mslow=$mskeep
	fi
	if  [ $mskeep -gt $mshigh ]
		then
			mshigh=$mskeep
	fi
 
	let mstotal+=$mskeep
	echo $msprint
	let counter+=1
	sleep 15
done
 
find_mean
echo Checked $counter times
printf "\n"
echo Found discrepancy: Initial IP was $initialIp and the IP is now $ip
printf "\n"
echo High: $mshigh ms  Low: $mslow ms  Avg: $msmean ms

Lucene Search Init Script – CentOS6

This is the init script that used for CentOS 6 and Apache’s Lucene search for our Mediawiki implementation.

 

#!/bin/bash
# chkconfig: 2345 90 90
# description: program_name
### BEGIN INIT INFO
# Provides: program_name
# Required-Start: network
# Required-Stop: network
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Description: Start the program
### END INIT INFO
 
### Fill in these bits:
START_CMD="/usr/local/search/ls2/lsearchd"
NAME="search"
PGREP_STRING="/usr/local/search/ls2/lsearchd"
PID_FILE="/var/run/search/search.pid"
USER="root"
 
### No further muckin' about needed!
 
CUR_USER=`whoami`
 
killproc() {
  pkill -u $USER -f $PGREP_STRING
}
 
start_daemon() {
  eval "$*"
}
 
log_success_msg() {
  echo "$*"
  logger "$_"
}
 
log_failure_msg() {
  echo "$*"
  logger "$_"
}
 
check_proc() {
  pgrep -u $USER -f $PGREP_STRING >/dev/null
}
 
start_script() {
  if [ "${CUR_USER}" != "root" ] ; then
    log_failure_msg "$NAME can only be started as 'root'."
    exit -1
  fi
 
  check_proc
  if [ $? -eq 0 ]; then
    log_success_msg "$NAME is already running."
    exit 0
  fi
 
  [ -d /var/run/$NAME ] || (mkdir /var/run/$NAME )
 
   # make go now 
    start_daemon /bin/su $USER -c $START_CMD >> /dev/null &
 
  # Sleep for a while to see if anything cries
  sleep 5
  check_proc
 
  if [ $? -eq 0 ]; then
    log_success_msg "Started $NAME."
  else
    log_failure_msg "Error starting $NAME."
    exit -1
  fi
}
 
stop_script() {
  if [ "${CUR_USER}" != "root" ] ; then
    log_failure_msg "You do not have permission to stop $NAME."
    exit -1
  fi
 
  check_proc
  if [ $? -eq 0 ]; then
    killproc -p $PID_FILE >/dev/null
 
    # Make sure it's dead before we return
    until [ $? -ne 0 ]; do
      sleep 1
      check_proc
    done
 
    check_proc
    if [ $? -eq 0 ]; then
      log_failure_msg "Error stopping $NAME."
      exit -1
    else
      log_success_msg "Stopped $NAME."
    fi
  else
    log_failure_msg "$NAME is not running or you don't have permission to stop it"
  fi
}
 
check_status() {
  check_proc
  if [ $? -eq 0 ]; then
    log_success_msg "$NAME is running."
  else
    log_failure_msg "$NAME is stopped."
    exit -1
  fi
}
 
case "$1" in
  start)
    start_script
    ;;
  stop)
    stop_script
    ;;
  restart)
    stop_script
    start_script
    ;;
  status)
    check_status
    ;;
  *)
    echo "Usage: $0 {start|stop|restart|status}"
    exit 1
esac
 
exit 0