Snorby No time_zone specified in snorby_config.yml; detected time_zone:

November 2, 2013

When I installed Snorby 2.6.2 and I started it, everything looked good and worked but I was getting that warning below, all the time:


No time_zone specified in snorby_config.yml; detected time_zone: America/Los_Angeles

Regardless of the fact I already put it in the config file: snorby_config.yml

  # If timezone_search is undefined or false, searching based on time will
  # use UTC times (historical behavior). If timezone_search is true
  # searching will use local time.
  timezone_search: true
  # uncomment to set time zone to time zone of box from /usr/share/zoneinfo, e.g. “America/Cancun”
  time_zone: ‘America/Los_Angeles’


So how did I fix it? Pretty simple actually but took me a lot of digging. Edit application.rd which is in the config directory, that way:

## time_zone = CONFIG[:time_zone] # set your local time zone here. use rake time:zones:local to choose a value, or use UTC.
    time_zone = “America/Los_Angeles”


That’s it. Search for the string “Central Time”. It is right after it. Line 77


Fake Time Warner (FTW)

April 17, 2013

Today I updated my Time Warner TV iPhone app and it stopped working. My iPhone 4 has iOS 6.1.2 and it is jb, so I am running FTW but it didn’t work anyway, ever I reinstalled FTW.

1) So I removed FTW completely, removed TW TV app completely, ran iCleaner (can be found in Cydia), rebooted the device.

2) Installed TW TV app, installed FTW and everything works now.


Changing back to IPTables in Fedora 18

March 18, 2013

By default Fedora 18 has changed to using firewalld to maintain the host firewall.  While this may be a good thing some times we need the old ways to allow us to catch up.  Especially when we haven’t the time to migrate complicated rules.  Thankfully Fedora has not removed IPTables.  The following set of commands should disable Firewalld and enable IPTables for those of us needing the breathing space to catch up.

systemctl disable firewalld.service
systemctl stop firewalld.service
systemctl enable iptables.service
systemctl enable ip6tables.service
systemctl start iptables.service
systemctl start ip6tables.service

Of course if you are like me and like to install minimal systems you may need to run this command first.

yum -y install iptables-services iptables-utils


Source: http://www.chesterproductions.net.nz/blogs/it/sysadmin/changing-back-to-iptables-in-fedora-18/616/


The definitive guide of connecting Apache via LDAP SSL to ActiveDirectory + Subversion

March 15, 2013

Being taken though hell I of configuring the damn authentication mechanism.
I needed to integrate Apache with ActiveDirectory via LDAP SSL. The manual SUCKS! It does not say anything useful, except for the syntax of the directives.
This article was the most definitive of configuring the integration. But lacks the information about how to make the SSL work correctly.

Here’s the kicker, it is as simple as the following several elements(this is in the top of /etc/apache2/sites-available/default):

# Make sure ve don’t care about the server’s certificate, because we don’t
LDAPVerifyServerCert off
LDAPTrustedMode SSL
# The server’s client cert information: the cert and the matching private key
LDAPTrustedGlobalCert CERT_BASE64 /etc/apache2/sites-available/cert1.pem
LDAPTrustedGlobalCert KEY_BASE64 /etc/apache2/sites-available/key1.pem

These go into the ROOT. Do not try to put them in the Location, nor Directory, nor VirtualHost.

And the main change to enable the SSL transport:
AuthLDAPURL “ldaps://adserver.example:636/DC=adserver,DC=example?sAMAccountName?sub?(objectClass=*)” SSL

These are the steps:

1. Create the client Key and Certificate

The cert1.pem and key1.pem are created like described here:

openssl genrsa 1024 > key1.pem
openssl req -new -x509 -nodes -sha1 -days 365 -key key1.pem > cert1.pem

For an additional configuration reduction bonus you can have it in one single file:
cat cert1.pem key1.pem > pcert.pem
LDAPTrustedGlobalCert CERT_BASE64 /etc/apache2/sites-available/pcert.pem

2. Enable the correct modules on Apache HTTP Server 2.2.

On my Ubuntu system the module enabling is done like this:

sudo a2enmod alias
sudo a2enmod auth_basic
sudo a2enmod authnz_ldap
sudo a2enmod authz_default
sudo a2enmod authz_user
sudo a2enmod dav
sudo a2enmod dav_svn
sudo a2enmod ldap

Or uncomment these elements in the httpd.conf:
LoadModule actions_module modules/mod_actions.so
LoadModule auth_basic_module modules/mod_auth_basic.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule ldap_module modules/mod_ldap.so

And the modules that are prescribed by the Subversion.

3. The access restrictions and Subversion

The short info for configuring the access restrictions.
This will allow people in the users in SVN Writers to commit and SVN Readers will be able to checkout and connect.

# This enables Subversion
DAV svn
# Location of the Subversion repository
SVNPath /home/ldaptest/

# How we are going to get authenticated
AuthBasicProvider ldap
AuthType Basic
AuthzLDAPAuthoritative on
AuthName “My Subversion server”
#The URL of the ActiveDirectory server
AuthLDAPURL “ldaps://adserver.example:636/DC=adserver,DC=example?sAMAccountName?sub?(objectClass=*)” SSL
# Credentials for the Apache HTTP to connect to the A/D to issue queries
AuthLDAPBindDN “subversion@adserver.example”
AuthLDAPBindPassword 555

# Limit all write operations to users within SVN Writers group
require ldap-group CN=SVN Writers,CN=Users,DC=adserver,DC=example
# Limit logon and reading to only users in SVN Readers group
require ldap-group CN=SVN Readers,CN=Users,DC=adserver,DC=example

4. Add the following to the default site on Apache HTTP

The file is /etc/apache2/sites-available/default
Right at the TOP.

# Make sure ve don’t care about the server’s certificate, because we don’t
LDAPVerifyServerCert off
LDAPTrustedMode SSL
# The server’s client cert information: the cert and the matching private key
LDAPTrustedGlobalCert CERT_BASE64 /etc/apache2/sites-available/cert1.pem
LDAPTrustedGlobalCert KEY_BASE64 /etc/apache2/sites-available/key1.pem

Posted 10th June 2009 by

Backup Csico routers and switches

March 5, 2013

I think my idea is secure, fast and easy to be implemented by anyone. No need of special software. All you need is tftp client. My stuff is working under Linux and I am not with “root” privileges when I am doing all that.

In the case I’m describing below is my router and is my Linux box. I am creating ACL #55 on the router, which ACL allows only the Linux box to have tftp access to it.

tftp-server nvram:startup-config 55

access-list 55 remark PERMIT hosts requesting TFTP access
access-list 55 permit

On the Linux box my “super” file is named “routers_backup.sh” and looks like:


/usr/bin/tftp -c get startup-config /home/jo/configs_backups/routers/Router_$(date “+%Y%m%d”)

and I do have crontab job running every Friday at 12:55 during the day:

55 12 * * 5 /home/jo/configs_backups/routers_backups.sh


3Com 4500 switch SPAN (port mirroring)

February 12, 2013

In the example below I am creating monitoring on port 50 for port 49. My port 49 is my uplink port for that 3Com 4500 48+2 port switch:

interface GigabitEthernet1/0/49
port link-type trunk
port trunk permit vlan all
port trunk pvid vlan 10
mirroring-group 1 mirroring-port both
[SD-LIB-3C4500-50P]dis cur int g1/0/50
interface GigabitEthernet1/0/50
port link-type trunk
port trunk permit vlan all
port trunk pvid vlan 10
mirroring-group 1 monitor-port
[SD-LIB-3C4500-50P]display mirror 1
mirroring-group 1:
type: local
status: active
mirroring port:
GigabitEthernet1/0/49  both
monitor port: GigabitEthernet1/0/50


Motorola Netopia 3347-02-1002 3347-02-1006 3347-02-1022

May 14, 2011

All there three AT&T modem could be upgraded to 7.8.1r2.

I just did an upgrade to two of my 3347-02-1002 and they are working without any problems. Of course 3347-02-1022 has more features even over the same firmware because it’s newer.

The upgrade is 100% safe.

The URL the firmware could be downloaded from is:


or if the page is not present, please let me know and I could provide the software.