0

Comcast’s weird routing from Pima County to Facebook

by

Only Comcast —

Instead of taking a short 21 mile hop from San Jose, California, to Menlo Park, California — Comcast does this:

Goes from San Jose, California to Dallas, Texas. 1700 miles.

Then it goes from Dallas, Texas to Marietta, Ga. Another almost 800 miles.

Then it goes from Marietta, Georgia, finally back to Facebook in Menlo Park, 2450 miles.

In order for Comcast to make that 21 mile trip up the road, they take a 4900 mile detour. Unbelievable. Welcome to Comcast.

nwayno@maggie:~$ traceroute facebook.com
traceroute to facebook.com (173.252.120.6), 30 hops max, 60 byte packets
1 Wiggum (192.168.1.1) 0.766 ms 1.489 ms 1.723 ms
2 * * *
3 * * *
4 te-0-1-1-0-ar02.pimaco.az.pima.comcast.net (68.86.201.205) 14.324 ms 14.540 ms 14.600 ms
5 he-0-3-0-0-10-cr01.sanjose.ca.ibone.comcast.net (68.86.93.117) 46.638 ms 46.843 ms 46.913 ms
6 be-11315-cr01.dallas.tx.ibone.comcast.net (68.86.85.141) 52.584 ms 45.716 ms 53.614 ms
7 be-11213-cr01.56marietta.ga.ibone.comcast.net (68.86.85.21) 71.292 ms 68.320 ms 68.191 ms
8 he-0-11-0-1-pe04.56marietta.ga.ibone.comcast.net (68.86.89.94) 65.796 ms 65.441 ms 65.505 ms
9 as32934-1-c.56marietta.ga.ibone.comcast.net (66.208.228.2) 68.866 ms 67.147 ms 67.117 ms
10 ae2.bb01.atl1.tfbnw.net (74.119.78.214) 65.548 ms 65.420 ms ae2.bb02.atl1.tfbnw.net (204.15.23.210) 67.759 ms
11 ae16.bb04.frc3.tfbnw.net (31.13.27.116) 72.204 ms ae15.bb04.frc3.tfbnw.net (31.13.27.114) 76.782 ms 75.143 ms
12 ae2.dr09.frc3.tfbnw.net (31.13.29.45) 70.846 ms ae1.dr09.frc3.tfbnw.net (31.13.29.43) 127.898 ms 124.045 ms
13 * * *
14 * * *
15 * * *
16 edge-star-shv-12-frc3.facebook.com (173.252.120.6) 75.695 ms 75.635 ms 72.918 ms
nwayno@maggie:~$

I knew Facebook had issues – Comcast just made it …? Well you tell me!(And all this time, I thought Facebook just suxed!)

I expect that the Customer Experience will only become obscenely more “quality challenged” if the merger with Time Warner is approved.

0

At&t 4G problems in Tucson

by

my_house

The symptoms: Dropped calls. Missing text messages. Text messages that wouldn’t send. Voice mail messages delayed…..

I have a Samsung Galaxy S5 with At&t. The cell tower is located at Cardinal and Los Reales (South of Valencia. Closest intersection is Cardinal/Valencia) (Drexel Heights area in Tucson.) I live about 1/2 mile WEST of the cell tower, and I get this blazing speed on 4G.

my_house

I was at the shopping centre today, and was about 500 feet EAST of the same cell tower. Line-of-sight The speeds are considerably different.

200ft_from_tower

I was informed by At&t that the cell tower was undergoing repair and to please be patient. The issues are due to an internal interference generated by At&T equipment. The tower has now been repaired. Really? Before this fiasco, I was getting 10-12 meg download on 4G lte at home. Other places in town, I get very good speeds. At home I get neinte. I no longer have 4G lte. I don’t even have 3G.

The At&t case number is: CM 20141022_95759252

At&t said they have escalated the issue to the next level, and that I should be getting a call RSN (real soon now.) Four calls, and over 3 hours on the phone with At&t tech support…..At&t said they would have the issue resolved by November 9, 2014 when I last spoke to At&t rep Kyle Moesch (At&t id: KM904C.)

As of 2:30 pm, Tuesday November 11, 2014, the problems still persist. Substandard data rates (under 1 meg down), delayed test/voice mail messages, unable to send some text messages.

I spoke with an AT&T rep today, and the new fix date is 7 pm, Friday, November 14, 2014.

The only consistent information I can get from At&t is they keep pushing out the completion date. First it was October 25.

Everything worked fine first week of October, 2014.

“A” for effort. “F-” for resolving the issue. Why does it work great 200 feet EAST of the tower, but 1/2 mile WEST, it sucks toenails?

0

Openvpn revisited: Howto install and configure openvpn

by

wayno vpn from outside

wayno vpn from outside

Virtual Private Networks. They are useful, but they can also seem daunting. As I have learned more about VPN’S from my first post, some 2 years ago, I thought we should re-vist and update.

1. What’s the first thing we do? Why install openvpn of course!

REMOTE (HOST) Configuration


sudo apt-get install openvpn

2. Now we need to generate our secret key. This is used to authenticate a remote user trying to gain access. We will use openvpn itself to generate the secret key. NOTE: Debian by default, does NOT provide a path to /usr/sbin

You can fully qualify it: /usr/sbin/openvpn

temporarily add it to the PATH variable: export PATH=$PATH:/sbin:/usr/sbin:/usr/sbin

Or just add:

export PATH=$PATH:/sbin:/usr/sbin:/usr/sbin

to .bashrc

If you add it to .bashrc, you will need to logout and back in again, so it will re-read the file.

Let’s generate that key! (The key below is named homer for the host, it can be anything)


openvpn --genkey --secret homer.key

Simple, huh?

3. Let’s move some files, and create the configuration file for openvpn.

first, let’s move our secret key file:


sudo cp homer.key /etc/openvpn/.

The period at the end, is significant. It says copy the file, right here.

4. Next is the configuration file. Using your favourite editor (nano in my case) create the
/etc/openvpn/openvpn.conf file as follows: Most of the explanations of the parameters come from here.


# Sample openvpn configuration file
# jjs June 6, 2012 V1.0
#
# annotated by Wayno April 26, 2014
#
# remote specifies the address of the server

local 192.168.1.101 5001
#local 192.168.1.101 1194

# dev tun specifies that we are using a tunnel device

dev tun

# ifconfig tells ip address for the interface

ifconfig 192.168.224.253 192.168.224.254

# and the secret key name (in /etc/openvpn)

secret homer.key

# use port 5001 (default) to connect to the vpn. This may require
# you to add this in your router.

port 5001
#port 1194

# if you want data compression

comp-lzo

# ping every 10 seconds, if no ping in 120 seconds, other side dead

keepalive 10 120

# ping timer starts after it receives a connection

ping-timer-rem

# don't recreate a virtual net interface TUN after automatic restart

persist-tun

# Don't read pre-shared static key file again after auto restart

persist-key

# user and group

user nobody
group nogroup

# after initialization, run in the background as a daemon

daemon

# append the /etc/openvpn/openvpn.log

log-append openvpn.log

5. Restart openvpn


sudo service openvpn restart

If you check /etc/openvpn/openvpn.log you will get something like this:

sudo cat openvpn.log
Tue Jun 24 20:00:39 2014 OpenVPN 2.3.2 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [eurephia] [MH] [IPv6] built on Feb 4 2014
Tue Jun 24 20:00:39 2014 TUN/TAP device tun0 opened
Tue Jun 24 20:00:39 2014 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Tue Jun 24 20:00:39 2014 /sbin/ip link set dev tun0 up mtu 1500
Tue Jun 24 20:00:39 2014 /sbin/ip addr add dev tun0 local 192.168.224.253 peer 192.168.224.253
Tue Jun 24 20:00:39 2014 GID set to nogroup
Tue Jun 24 20:00:39 2014 UID set to nobody
Tue Jun 24 20:00:39 2014 UDPv4 link local (bound): [AF_INET]192.168.1.101:5001
Tue Jun 24 20:00:39 2014 UDPv4 link remote: [undef]
Tue Jun 24 20:00:44 2014 Peer Connection Initiated with [AF_INET]192.168.1.103:5001
Tue Jun 24 20:00:45 2014 Initialization Sequence Completed

6. Let’s see if it works?


ping -c 5 192.168.224.253

PING 192.168.224.253 (192.168.224.253) 56(84) bytes of data.
64 bytes from 192.168.224.253: icmp_req=1 ttl=64 time=0.033 ms
64 bytes from 192.168.224.253: icmp_req=2 ttl=64 time=0.041 ms
64 bytes from 192.168.224.253: icmp_req=3 ttl=64 time=0.030 ms
64 bytes from 192.168.224.253: icmp_req=4 ttl=64 time=0.041 ms
64 bytes from 192.168.224.253: icmp_req=5 ttl=64 time=0.040 ms

— 192.168.224.253 ping statistics —
5 packets transmitted, 5 received, 0% packet loss, time 3999ms
rtt min/avg/max/mdev = 0.030/0.037/0.041/0.004 ms

==================

1. Now the CLIENT configuration /etc/openvpn/client.conf:


#
# openvpn CLIENT configuration
#
# V1.0 by Wayno April 26, 2014

# remote specifies the ip address of the remote (host) openvpn

remote 192.168.1.101

# dev tun specifies that we are using a tunnel device

dev tun

# ifconfig tells ip address for the interface
# NOTE that the ifconfig ip's are BACKWARD from the host

ifconfig 192.168.224.254 192.168.224.253

# The name of the secret key we generated (it could be anyname)

secret homer.key

# use port 5001 (note you may need to open this up in your router
# and make sure it points to the remote (host))

port 5001

# if you want data compression

comp-lzo

# ping every 10 seconds, if no ping in 60 seconds, other side dead

keepalive 10 60

# ping timer starts after it receives a connection

ping-timer-rem

# don't recreate a virtual net interface TUN after automatic restart

persist-tun

# Don't read pre-shared static key file again after auto restart

persist-key

#user and group

user nobody
group nogroup

# after initialization, run in the background as a daemon

daemon

log-append openvpn.log

2. Ensure you copy the secret key over to the /etc/openvpn on the client side. This assumes the key is already in your home folder


sudo cp ~/homer.key .

Note that the period (.) at the end IS significant.

3. And your output should look something like this:

sudo cat openvpn.log
Tue Jun 24 20:20:27 2014 OpenVPN 2.2.1 x86_64-linux-gnu [SSL] [LZO2] [EPOLL] [PKCS11] [eurephia] [MH] [PF_INET6] [IPv6 payload 20110424-2 (2.2RC2)] built on Jun 18 2013
Tue Jun 24 20:20:27 2014 NOTE: OpenVPN 2.1 requires ‘–script-security 2′ or higher to call user-defined scripts or executables
Tue Jun 24 20:20:27 2014 LZO compression initialized
Tue Jun 24 20:20:27 2014 TUN/TAP device tun0 opened
Tue Jun 24 20:20:27 2014 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Tue Jun 24 20:20:27 2014 /sbin/ifconfig tun0 192.168.224.254 pointopoint 192.168.224.253 mtu 1500
Tue Jun 24 20:20:27 2014 GID set to nogroup
Tue Jun 24 20:20:27 2014 UID set to nobody
Tue Jun 24 20:20:27 2014 UDPv4 link local (bound): [undef]
Tue Jun 24 20:20:27 2014 UDPv4 link remote: [AF_INET]192.168.1.101:5001
Tue Jun 24 20:20:27 2014 Peer Connection Initiated with [AF_INET]192.168.1.101:5001
Tue Jun 24 20:20:28 2014 Initialization Sequence Completed

3. ssh into the vpn

nwayno@Willy:~$ ssh 192.168.224.253
nwayno@192.168.224.253’s password:
Welcome to Ubuntu 14.04 LTS (GNU/Linux 3.13.0-29-generic x86_64)

* Documentation: https://help.ubuntu.com/

Last login: Tue Jun 24 20:40:04 2014 from 192.168.224.253
nwayno@Homer:~$

0

Ubuntu to go: Installing Linux onto a usb flash drive

by

Another lost article, originally from May 4, 2009

Putting Ubuntu on a flash drive, can seem a daunting task. But if you follow these steps, you’ will have a portable secure operating system.

Here’s what you”ll need:

A computer with:

USB Ports
256 meg of ram
cdrom
USB flash drive (at least 4 G)
32 bit Ubuntu 9.04 Install CD (desktop)
(download from here: Download Ubunutu)
A live (hot) internet connection

WARNING: CHOOSING THE WRONG DEVICE CAN RENDER YOUR HARD DRIVE UNBOOTABLE. IF YOU’RE NOT SURE, YOU MAY WANT TO REMOVE THE PLUGS FROM YOU HARD DRIVE BEFORE STARTING.

1. Boot off the install cd.

2. Choose Install Ubuntu and hit enter

3. When you come to the screen that says: “Prepare disk space” (step 4 of 7) on top,
choose “specify partitions manually (advanced)”

4. the usb drive (on my system) is called /dev/sdc

5. delete the partition on this drive, so you can start fresh.

6. It should show /dev/sdc
free space (size of drive — 8065 mb in my case — 8 G)

7. Select the “free space” for the usb drive by single clicking it (left mouse button)

8. Select “new partition” on the bottom of the screen.

We are going to create a 1 G fat32 partition for windows, and then the rest for linux.

Windows (will become /dev/sdc1)
New Partition should read: Primary
Size should be: 1024 meg
Beginning
Use as FAT32 file system
Mount Point: /dos

Select the remaining “free space” for the usb drive by single clicking it (left mouse button)

8. Select “new partition” on the bottom of the screen.

Linux (will become /dev/sdc2)
New partition should read: Primary
Size should be the remaining full size of the USB Drive (7039 meg)
Beginning
Use as ext2 file system (we want a “non-journaled” file system)
(USB flash drives do NOT have a fast transfer rate (4-5 meg tops), so we want a non-journaled file system)

Mount Point should be / (root directory)

The great thing is that windows will NOT see any of the Linux on the flash drive. However, Linux WILL see the windows partition. So you can easily exchange information between Windows and Linux.

to see the Windows Partition in Linux simply go into terminal mode (after the install of course) and type:

cd /dos (that was the mount point we created above)

So it should look like this before proceeding to the next step:

Devices Type Size
/dev/sdc1 fat32 1023
/dev/sdc2 ext2 7039

9. Hit forward and you will see “Who are you?” (screen 5 of 7) fill out as desired.

10. if you get the message “there are no users or operating system suitable for importing from” error – that’s normal – (step 6 of 7) just go forward.

11. When you arrive at step 7 of 7, this is the tricky part. “Ready to Install” We need to make the flash drive bootable.

There is an “advanced” tab at the bottom right of the screen. Click on that.

Click on “Install Boot Loader” and choose the correct DEVICE (not partition) device. In my case /dev/sdc

WARNING: CHOOSING THE WRONG DEVICE CAN RENDER YOUR HARD DRIVE UNBOOTABLE. IF YOU’RE NOT SURE, YOU MAY WANT TO REMOVE THE PLUGS FROM YOU HARD DRIVE BEFORE STARTING.

12. Click on install, and sit back. Like Alton Brown says: “Your patience WILL be rewarded!”

13. Boot up off your usb drive, and we are going to make a performance enhancement.

14. Open up a terminal window and type

cd /etc # go to the /etc directory

sudo cp fstab fstab.org # make a copy of the file structure table (always have a path back!)

sudo nano fstab

change “relatime” to “noatime”

from: http://en.wikipedia.org/wiki/Fstab

´╗┐By default Linux records when files are last accessed, modified and created. This behaviour can be controlled with the noatime option, which will prevent this information from being recorded. The advantage might be a performance increase, especially when files are accessed and modified often.

control+o to write the file changes, then control+x to exit.
(hold down the control key, and hit the letter)

NOTE: if you screw up fstab, your system may NOT boot. DON’T panic!

boot into recovery mode, then choose “Drop to root shell prompt with out networking”

mount -o remount rw / # mount root as read/write access

cd /etc # change to /etc

rm fstab # removes the existing (hosed) fstab

cp fstab.org fstab # copy back the original fstab

15. Install updates and enjoy! You now have in your pocket, a secure, portable operating system.

if you do a df (display free) at terminal mode you will see that Linux
has used approximately 2.5 G (yes with “X” installed) and have about 4G free!

16. One caution. In order to avoid file corruption, I always “shutdown” when done using my ubuntu2go flash drive. Removing the flash drive before the system has shutdown, may result in file corruption.

0

Configuring APC (American Power Conversion) UPS Support for Linux

by

This was an old article from June 23, 2009 that was somehow lost.

Installing APC (American Power Conversion) UPS (Un-interruptible Power Source) Support for Ubuntu Linux

(debunking the half truths)

Information garnered from: apcupsd.org

first step

sudo apt-get install apcupsd

1. HALF-TRUTH: Problem
2.6 kernels use udev and some distributions to not configure it to automatically create /dev/usb/hiddev?? as they should, causing apcupsd to fail to locate the UPS.
Workaround

Edit the file /etc/udev/rules.d/50-udev.rules, and add the following:

KERNEL=”hiddev*”, NAME=”usb/hiddev%n”

This results in a boot time error in Ubuntu, and doesn’t work.

TRUTH: This doesn’t work, don’t use it.

——–

2. HALF-TRUTH: Problem
On some systems such as Slackware 10.0, no USB devices will show up (see the next section).
Workaround

Add the following to rc.local

mount -t usbdevfs none /proc/bus/usb

TRUTH: mount requires root access:

nwayno@H:/$ sudo mount -t usbdevfs none /proc/bus/usb
[sudo] password for nwayno:
mount: unknown filesystem type ‘usbdevfs’

And that didn’t work, but here’s why:

From man mount (output)

Earlier, usbfs was known as usbdevfs.
So the mount really should look like this:

sudo mount -t usbfs none /proc/bus/usb

3. Verifying Device Detection and Driver

To make sure that your USB subsystem can see the UPS, just do this from a shell prompt:

cat /proc/bus/usb/devices

and sure enough, this is what I got:

T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=051d ProdID=0002 Rev= 1.06
S: Manufacturer=American Power Conversion
S: Product=Back-UPS BR 800 FW:9.o2 .D USB FW:o2
S: SerialNumber=QB0351236370
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 24mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid
E: Ad=81(I) Atr=03(Int.) MxPS= 6 Ivl=10ms

This is what my apcupsd.conf file looks like:

Important things to change in the following:

UPSNAME WaynoUps # name for ups
UPSCABLE usb # type of cable
UPSTYPE usb # yes it’s usb
NISIP 0.0.0.0 # this is what made networking work chg from localhost
DEVICE

nwayno@Homer:/etc/apcupsd$ cat apcupsd.conf

#—– BEGIN /etc/apcupsd/apcupsd.conf —–
## apcupsd.conf v1.1 ##
#
# for apcupsd release 3.14.4 (18 May 2008) – debian
#
# “apcupsd” POSIX config file

#
# ========= General configuration parameters ============
#

# UPSNAME xxx
# Use this to give your UPS a name in log files and such. This
# is particulary useful if you have multiple UPSes. This does not
# set the EEPROM. It should be 8 characters or less.
UPSNAME WaynoUps

# UPSCABLE
# Defines the type of cable connecting the UPS to your computer.
#
# Possible generic choices for
are:
# simple, smart, ether, usb
#
# Or a specific cable model number may be used:
# 940-0119A, 940-0127A, 940-0128A, 940-0020B,
# 940-0020C, 940-0023A, 940-0024B, 940-0024C,
# 940-1524C, 940-0024G, 940-0095A, 940-0095B,
# 940-0095C, M-04-02-2000
#
UPSCABLE usb

# To get apcupsd to work, in addition to defining the cable
# above, you must also define a UPSTYPE, which corresponds to
# the type of UPS you have (see the Description for more details).
# You must also specify a DEVICE, sometimes referred to as a port.
# For USB UPSes, please leave the DEVICE directive blank. For
# other UPS types, you must specify an appropriate port or address.
#
# UPSTYPE DEVICE Description
# apcsmart /dev/tty** Newer serial character device,
# appropriate for SmartUPS models using
# a serial cable (not USB).
#
# usb Most new UPSes are USB. A blank DEVICE
# setting enables autodetection, which is
# the best choice for most installations.
#
# net hostname:port Network link to a master apcupsd
# through apcupsd’s Network Information
# Server. This is used if you don’t have
# a UPS directly connected to your computer.
#
# snmp hostname:port:vendor:community
# SNMP Network link to an SNMP-enabled
# UPS device. Vendor is the MIB used by
# the UPS device: can be “APC”, “APC_NOTRAP”
# or “RFC” where APC is the powernet MIB,
# “APC_NOTRAP” is powernet with SNMP trap
# catching disabled, and RFC is the IETF’s
# rfc1628 UPS-MIB. You usually want “APC”.
# Port is usually 161. Community is usually
# “private”.
#
# dumb /dev/tty** Old serial character device for use
# with simple-signaling UPSes.
#
# pcnet ipaddr:username:passphrase
# PowerChute Network Shutdown protocol
# which can be used as an alternative to SNMP
# with AP9617 family of smart slot cards.
# ipaddr is the IP address of the UPS mgmt
# card. username and passphrase are the
# credentials for which the card has been
# configured.
#
UPSTYPE usb
DEVICE

# POLLTIME
# Interval (in seconds) at which apcupsd polls the UPS for status. This
# setting applies both to directly-attached UPSes (UPSTYPE apcsmart, usb,
# dumb) and networked UPSes (UPSTYPE net, snmp). Lowering this setting
# will improve apcupsd’s responsiveness to certain events at the cost of
# higher CPU utilization. The default of 60 is appropriate for most
# situations.
#POLLTIME 60

# LOCKFILE # Path for device lock file. Not used on Win32.
LOCKFILE /var/lock

# SCRIPTDIR # Directory in which apccontrol and event scripts are located.
SCRIPTDIR /etc/apcupsd

# PWRFAILDIR # Directory in which to write the powerfail flag file. This file
# is created when apcupsd initiates a system shutdown and is
# checked in the OS halt scripts to determine if a killpower
# (turning off UPS output power) is required.
PWRFAILDIR /etc/apcupsd

# NOLOGINDIR # Directory in which to write the nologin file. The existence
# of this flag file tells the OS to disallow new logins.
NOLOGINDIR /etc

#
# ======== Configuration parameters used during power failures ==========
#

# The ONBATTERYDELAY is the time in seconds from when a power failure
# is detected until we react to it with an onbattery event.
#
# This means that, apccontrol will be called with the powerout argument
# immediately when a power failure is detected. However, the
# onbattery argument is passed to apccontrol only after the
# ONBATTERYDELAY time. If you don’t want to be annoyed by short
# powerfailures, make sure that apccontrol powerout does nothing
# i.e. comment out the wall.
ONBATTERYDELAY 6

#
# Note: BATTERYLEVEL, MINUTES, and TIMEOUT work in conjunction, so
# the first that occurs will cause the initation of a shutdown.
#

# If during a power failure, the remaining battery percentage
# (as reported by the UPS) is below or equal to BATTERYLEVEL,
# apcupsd will initiate a system shutdown.
BATTERYLEVEL 5

# If during a power failure, the remaining runtime in minutes
# (as calculated internally by the UPS) is below or equal to MINUTES,
# apcupsd, will initiate a system shutdown.
MINUTES 3

# If during a power failure, the UPS has run on batteries for TIMEOUT
# many seconds or longer, apcupsd will initiate a system shutdown.
# A value of 0 disables this timer.
#
# Note, if you have a Smart UPS, you will most likely want to disable
# this timer by setting it to zero. That way, you UPS will continue
# on batteries until either the % charge remaing drops to or below BATTERYLEVEL,
# or the remaining battery runtime drops to or below MINUTES. Of course,
# if you are testing, setting this to 60 causes a quick system shutdown
# if you pull the power plug.
# If you have an older dumb UPS, you will want to set this to less than
# the time you know you can run on batteries.
TIMEOUT 0

# Time in seconds between annoying users to signoff prior to
# system shutdown. 0 disables.
ANNOY 300

# Initial delay after power failure before warning users to get
# off the system.
ANNOYDELAY 60

# The condition which determines when users are prevented from
# logging in during a power failure.
# NOLOGON [ disable | timeout | percent | minutes | always ]
NOLOGON disable

# If KILLDELAY is non-zero, apcupsd will continue running after a
# shutdown has been requested, and after the specified time in
# seconds attempt to kill the power. This is for use on systems
# where apcupsd cannot regain control after a shutdown.
# KILLDELAY 0 disables
KILLDELAY 0

#
# ==== Configuration statements for Network Information Server ====
#

# NETSERVER [ on | off ] on enables, off disables the network
# information server. If netstatus is on, a network information
# server process will be started for serving the STATUS and
# EVENT data over the network (used by CGI programs).
NETSERVER on

# NISIP
# IP address on which NIS server will listen for incoming connections.
# This is useful if your server is multi-homed (has more than one
# network interface and IP address). Default value is 0.0.0.0 which
# means any incoming request will be serviced. Alternatively, you can
# configure this setting to any specific IP address of your server and
# NIS will listen for connections only on that interface. Use the
# loopback address (127.0.0.1) to accept connections only from the
# local machine.
#NISIP 127.0.0.1
#
# change ip from local host to any interface GU 07/07/2009
#
NISIP 0.0.0.0

# NISPORT default is 3551 as registered with the IANA
# port to use for sending STATUS and EVENTS data over the network.
# It is not used unless NETSERVER is on. If you change this port,
# you will need to change the corresponding value in the cgi directory
# and rebuild the cgi programs.
NISPORT 3551

# If you want the last few EVENTS to be available over the network
# by the network information server, you must define an EVENTSFILE.
EVENTSFILE /var/log/apcupsd.events

# EVENTSFILEMAX
# By default, the size of the EVENTSFILE will be not be allowed to exceed
# 10 kilobytes. When the file grows beyond this limit, older EVENTS will
# be removed from the beginning of the file (first in first out). The
# parameter EVENTSFILEMAX can be set to a different kilobyte value, or set
# to zero to allow the EVENTSFILE to grow without limit.
EVENTSFILEMAX 10

#
# ========== Configuration statements used if sharing =============
# a UPS with more than one machine

#
# Remaining items are for ShareUPS (APC expansion card) ONLY
#

# UPSCLASS [ standalone | shareslave | sharemaster ]
# Normally standalone unless you share an UPS using an APC ShareUPS
# card.
UPSCLASS standalone

# UPSMODE [ disable | share ]
# Normally disable unless you share an UPS using an APC ShareUPS card.
UPSMODE disable

#
# ===== Configuration statements to control apcupsd system logging ========
#

# Time interval in seconds between writing the STATUS file; 0 disables
STATTIME 0

# Location of STATUS file (written to only if STATTIME is non-zero)
STATFILE /var/log/apcupsd.status

# LOGSTATS [ on | off ] on enables, off disables
# Note! This generates a lot of output, so if
# you turn this on, be sure that the
# file defined in syslog.conf for LOG_NOTICE is a named pipe.
# You probably do not want this on.
LOGSTATS off

# Time interval in seconds between writing the DATA records to
# the log file. 0 disables.
DATATIME 0

# FACILITY defines the logging facility (class) for logging to syslog.
# If not specified, it defaults to “daemon”. This is useful
# if you want to separate the data logged by apcupsd from other
# programs.
#FACILITY DAEMON

#
# ========== Configuration statements used in updating the UPS EPROM =========
#

#
# These statements are used only by apctest when choosing “Set EEPROM with conf
# file values” from the EEPROM menu. THESE STATEMENTS HAVE NO EFFECT ON APCUPSD.
#

# UPS name, max 8 characters
#UPSNAME UPS_IDEN

# Battery date – 8 characters
#BATTDATE mm/dd/yy

# Sensitivity to line voltage quality (H cause faster transfer to batteries)
# SENSITIVITY H M L (default = H)
#SENSITIVITY H

# UPS delay after power return (seconds)
# WAKEUP 000 060 180 300 (default = 0)
#WAKEUP 60

# UPS Grace period after request to power off (seconds)
# SLEEP 020 180 300 600 (default = 20)
#SLEEP 180

# Low line voltage causing transfer to batteries
# The permitted values depend on your model as defined by last letter
# of FIRMWARE or APCMODEL. Some representative values are:
# D 106 103 100 097
# M 177 172 168 182
# A 092 090 088 086
# I 208 204 200 196 (default = 0 => not valid)
#LOTRANSFER 208

# High line voltage causing transfer to batteries
# The permitted values depend on your model as defined by last letter
# of FIRMWARE or APCMODEL. Some representative values are:
# D 127 130 133 136
# M 229 234 239 224
# A 108 110 112 114
# I 253 257 261 265 (default = 0 => not valid)
#HITRANSFER 253

# Battery charge needed to restore power
# RETURNCHARGE 00 15 50 90 (default = 15)
#RETURNCHARGE 15

# Alarm delay
# 0 = zero delay after pwr fail, T = power fail + 30 sec, L = low battery, N = never
# BEEPSTATE 0 T L N (default = 0)
#BEEPSTATE T

# Low battery warning delay in minutes
# LOWBATT 02 05 07 10 (default = 02)
#LOWBATT 2

# UPS Output voltage when running on batteries
# The permitted values depend on your model as defined by last letter
# of FIRMWARE or APCMODEL. Some representative values are:
# D 115
# M 208
# A 100
# I 230 240 220 225 (default = 0 => not valid)
#OUTPUTVOLTS 230

# Self test interval in hours 336=2 weeks, 168=1 week, ON=at power on
# SELFTEST 336 168 ON OFF (default = 336)
#SELFTEST 336

#—– END /etc/apcupsd/apcupsd.conf —–

————-

4. Testing

HALF-TRUTH: Run apctest by invoking it with no arguments.

It will read your installed apcupsd.conf configuration (so it knows where to find the UPS) and then it will present you with the following output:

nwayno@H:/etc/apcupsd$ apctest

Could not create apctest.output: Permission denied
2009-06-22 18:18:59 Could not create apctest.output: Permission denied
apctest 3.14.4 (18 May 2008) debian
Could not create apctest.output: Permission denied
Checking configuration …
Could not create apctest.output: Permission denied
Attached to driver: usb
Could not create apctest.output: Permission denied
sharenet.type = DISABLE
Could not create apctest.output: Permission denied
cable.type = USB_CABLE
Could not create apctest.output: Permission denied

You are using a USB cable type, so I’m entering USB test mode
Could not create apctest.output: Permission denied
mode.type = USB_UPS
Could not create apctest.output: Permission denied
Setting up the port …
Could not create apctest.output: Permission denied

TRUTH: apctest requires ROOT access

nwayno@H:/etc/apcupsd$ sudo apctest

2009-06-22 18:16:59 apctest 3.14.4 (18 May 2008) debian
Checking configuration …
Attached to driver: usb
sharenet.type = DISABLE
cable.type = USB_CABLE

You are using a USB cable type, so I’m entering USB test mode
mode.type = USB_UPS
Setting up the port …
Hello, this is the apcupsd Cable Test program.
This part of apctest is for testing USB UPSes.

Getting UPS capabilities…SUCCESS

Please select the function you want to perform.

1) Test kill UPS power
2) Perform self-test
3) Read last self-test result
4) Change battery date
5) View battery date
6) View manufacturing date
7) Set alarm behavior
8 ) Set sensitivity
9) Set low transfer voltage
10) Set high transfer voltage
11) Quit

Select function number: 11

2009-06-22 18:17:14 End apctest.
nwayno@H:/etc/apcupsd$

5. HALF Truth:

and the client machine side: (SuSE)

## apcupsd.conf v1.1 ##
UPSCABLE ether
UPSTYPE net
LOCKFILE /var/lock
DEVICE server-network-address:3551
UPSCLASS standalone
UPSMODE disable
POLLTIME 10

infact it won’t work as is:

Change POLLTIME to NETTIME

so the file on the CLIENT looks like:

## apcupsd.conf v1.1 ##
UPSCABLE ether
UPSTYPE net
LOCKFILE /var/lock
DEVICE 192.168.0.102:3551
UPSCLASS standalone
UPSMODE disable
NETTIME 10

NOTE: You may need to bring down the firewall on the server side:

sudo ufw disable

6. and if we did our home work right — pulling the plug:

Broadcast Message from root@H (somewhere) at 17:09 (SERVER/UBUNTU)

Power failure on UPS WaynoUps. Running on batteries. (SERVER/UBUNTU)

Broadcast Message from root@P (somewhere) at 17:09 (CLIENT/SuSE)

Power failure on UPS WaynoUps. Running on batteries. (CLIENT/SuSE)

Broadcast Message from root@H (somewhere) at 17:10 (SERVER/UBUNTU)

Power has returned on UPS WaynoUps… (SERVER/UBUNTU)

Broadcast Message from root@P (somewhere) at 17:10 (CLIENT/SuSE)

Power has returned on UPS WaynoUps… (CLIENT/SuSE)

(thanks to Loni/lornix.com) for her assistance in figuring out why the client side wouldn’t work.

ADDENDUM: thanks Loni

1

Dear Comcast — I am NOT an idiot

by

Dear Comcast:

Today I interacted via telephone with one of your offshore tech support agents, since I was unable to go online. customer.comcast.net was unable to tell me of any outages in my area. One of my online experiences was with a computer anyway since it failed the Turing test.

Your Customer Service mark would vastly improve if you would stop assuming that the customer is an idiot.

Routers have absolutely nothing to do with whether or not my modem is online. I do not need to go out and buy and new modem.

If the modem is offline — That is controlled by your equipment, NOT mine.

LISTEN!

Wayno

1 2 3 4 5 19 20