Ads Theme Blogger Template Comment Broken / Not Working [Fixed]

If you've installed the Ads Theme Blogger Template, chances are the comment section is NOT working.

I've tried a few things. 

An easy fix to it is look for the line:

<b:include data='post' name='comments'/>

and replace it with:

<b:include data='post' name='comment-form'/>

That's it.! The comment box section should work now.

Tell me if this works for you.

IPv6 Review: Simplified

In IPv6, the address size has moved from 32 bit IPv4 to 128 bit IPv6.

This provides huge amounts of addresses...trillions and trillions.

To make addresses more manageable, the IPv6 address is divided into 8 groups of 4 HEX characters each:
    2001:0050:0000:0000:0000:0AB4:1EA2:89AA

Each group is 16 bits.  Example, in 2001:..
                20 = 8 bits
                01 = 8 bits

Rules of IPv6:

RULE 1: Eliminate groups of consecutive zeros:
    Address above would be:
    2001:0050::0AB4:1EA2:89AA

RULE 2: Drop leading ZEROS:
    Address above would be:
    2001:50::AB4:1EA2:89AA

Types of Communication and Addresses in IPv6:

1. There is no broadcast in ipv6.
2. Unicast: one to one
3. Multicast: one to many
4. Anycast: one to closest

5. Link-local scope address:  layer 2 domain address.
6. Unique / Site-local scope address:  Organization address
7. Global scope address:  Internet / Public Address

Link-local scope address:

•  Assigned automatically as an ipv6 host comes online.    
•  Similar to the 169.254.x.x addresses of ipv4.  In ipv6 is a good thing. 
• Always begin with "FE80" (First 10 bits: 1111 1110 10...) followed by 54 bits of ZEROS.
• Last 64 bits is the 48 bit MAC ADDRESS with "FFFE" squeezed in the middle. 

            MAC ADDRESS:  0011.A123.DEF1
            fe80::0011:A1FF:FE23:DEF1  == notice FF.FE

Unique / Site-local scope address:

    - Was supposed to be similar to private addresses in ipv4.  The standard was later revised to be taken out of the RFC.

    - The ipv6 standard now don't use this scope.

Global scope address:

    - Have their high level 3 bits set to 001 (2000::/3)

    - N bits(global routing prefix 001..) - 64-BITS(SUBNET ID) -- 64 BITS HOST OR INTERFACE ID.
        The global routing prefix will be assigned to the ISPs.
            The ISPs will assign the subnets to its customers.
                The customers can further subnet it further and includes the hosts.

    - Global routing prefix is 48 bits or less.

    - Subnet ID is comprised of whatever bits are left over after the Global Routing Prefix.

    - The primary addresses expected to comprise the ipv6 internet are from the 2001::/16 subnet.

Google IPv6 BGP looking glass to see the available ipv6 out there that companies are using.

Configuring IPv6 OSPF example in Cisco:

router(config)# ipv6 unicast-routing
router(config)# ipv6 router ospf 1
router(config-router)# router-id 192.168.10.1
router(config)# interface f0/0 ==== ipv6 runs on the interface.
router(config-if)# ipv6 ospf 1 area 0

Leave a note if you like it.

FTP source-interface for FTP Cisco configs to FTP server

Transfering / Backup Cisco Configs from outside IP to internal FTP SERVER through Firewall.

First, you need to allow your Public IP network provided to you from your ISP through your firewall on port 21 (ftp port).

If you do not set the source interface for your FTP communication, the FTP transfer may fail.  By default Cisco Routers will use the uplink / outside interface, not the interface with IP addresses assigned to you by your ISP.

Router-INTERNET#sh ip int br
Interface                  IP-Address      OK? Method Status                Protocol
Embedded-Service-Engine0/0 unassigned      YES NVRAM  administratively down down
GigabitEthernet0/0         23.12.143.75     YES NVRAM  up                    up
GigabitEthernet0/1         132.95.160.113  YES NVRAM  up                    up
GigabitEthernet0/2         unassigned      YES NVRAM  administratively down down
Router-INTERNET#

ISP <---> g0/0---G0/1-->Inside

The command to set a source interface or IP on a cisco Router for backing up to ftp is:

router(config)#ip ftp source-interface GigabitEthernet0/1

router# copy running-config ftp

Now when you copy to your ftp server, it will use the source interface GigabitEthernet0/1 with ip 132.95.160.113, which is your company public IP.

tftp source-interface to backup Cisco configs to your tftp server

Transfering / Backup Cisco Configs from outside IP to internal TFTP SERVER through Firewall.

First, you need to allow your Public IP network provided to you from your ISP through your firewall on port 69 (tftp port).

If you do not set the source interface for your TFTP communication, the TFTP transfer may fail.  By default Cisco Routers will use the uplink / outside interface, not the interface with IP addresses assigned to you by your ISP.

Router-INTERNET#sh ip int br
Interface                  IP-Address      OK? Method Status                Protocol
Embedded-Service-Engine0/0 unassigned      YES NVRAM  administratively down down
GigabitEthernet0/0         23.12.143.75     YES NVRAM  up                    up
GigabitEthernet0/1         132.95.160.113  YES NVRAM  up                    up
GigabitEthernet0/2         unassigned      YES NVRAM  administratively down down
Router-INTERNET#

ISP <---> g0/0---G0/1-->Inside

The command to set a source interface or IP on a cisco Router for backing up to tftp is:

router(config)#ip tftp source-interface GigabitEthernet0/1

router# copy running-config tftp

Now when you copy to your tftp server, it will use the source interface GigabitEthernet0/1 with ip 132.95.160.113, which is your company public IP.

FIXED: Slow Internet Browsing Using Sophos UTM Is Now Fixed

I'm happy to report that after a few months of using Sophos UTM hardware appliances, browsing the internet is now fast or should I say user acceptable level.

The fixed was to upgrade the Sophos UTM to 9.205-12.  Before the upgrade, I had to disable Sophos web filtering.  Now, it works just fine after upgrading to the new software.

How to add devices using Self Service Portal in Sophos Mobile Control (SMC)

After many hours of installing and configuring the Sophos Mobile Client Control, I found out there's no steps to add your mobile devices in any of their docs.  They have so many docs on the SMC, but none on the info you want. 
You have the Super Admin Guide, the Admin guide, the startup guide, the install guide, the SMC as service guide, the technical guide, and on and on.... and on.

All I want is to install the SMC software, add my iPhone, Android phone, tablet, and manage it in less than 10 - 20 minutes.

I installed the Sophos Mobile Control software and I was able to login. But spent hours trying to find out how to add devices to the SMC server.  Needless to say, they need to have simpler docs. 

Well, if you want a simple way of installing the SMC server and immediately add devices to it and start managing it, here are the steps.  Skip to the bottom "Add devices using Self Service Portal in Sophos Mobile Control (SMC)" if you can already login to SMC.

Installing the SMC Server software:  (skip this step if you already installed the software)
1. install the Windows O/S and or SQL server.
2. Download the SMC Mobile Control software from Sophos.
3. Install the .exe software.  Follow the instruction on screen.  When ask for the SQL server, you can point to a remote SQL server or use local. 
4. Create an superadmin account to login:  admin user to login to the SMC WEB gui.
5. Take defaults for the rest when you can.
6. done.  You're done with the install.

Login to the Sophos Mobile Control SMC server:

1. To login, go to the url:  https://IP-Address-of-SMC-server/
2. login with admin / yourpassword, the superadmin account you created during the install.

Create a Customer in SMC:

1. You have to create a customer and login as the admin user of that Customer to add and manage mobile devices. 
A customer is your company / organization.  From here on, you should always login to the customer and add / change any iPhone, Android, devices, etc. and modify mobile profiles.

2. If you don't create a customer, it won't work.


Add devices using Self Service Portal in Sophos Mobile Control (SMC):

Adding mobile devices, ie, iPhones, Android, Windows phone, Tablets to the SMC server is quite simple.  You can have the user do it without the Administrator involve.

1.  Access the SMC self service portal URL:  https://IP-Address-of-SMC-server/ssp/
2.  Login with an Active Directory user / group allowed to be controled by SMC mobile control.  I just create a new AD group and add users with mobile phones I want to manage.
    (you setup the external Active Directory by login as the customer then, --> Settings-->System Setup-->user setup tab.

3.  From here on, I let the users add their own devices to the SMC server themselves without administrator involvement.
    a.  Users would need to go to their iPhones, Androids, Windows Phones, tablets and open a browser, ie. safari.
    b.  They go to the Self Service Portal URL: https://IP-Address-of-SMC-server/ssp/
    c.  Enter the Customer or company name and Active Directory user/password
    d.  After you login, you will see a button to "Register New Device"
    e.  Click on it and follow the on screen prompt and enter your telephone number, or you'll need to UPDATE the phone number by login as admin in SMC SERVER.
    f.  After a few minutes, you will get a "Configuration Finished", then click on "OK"
    g.  done. and Logout.
  
Option 2:
1.  You, the Administrator, login to the SMC server with the customer admin user:
go to Inventory --> Devices --> click on Create Device.
        Enter the 3 mandatory fields:
            Name:
            Description
            Phone number
you're done.








Tell me how this works for you.

Sophos UTM Running Slow 2

From the previous post:

Sophos UTM Running Slow

Update: It did not work.  After installing the active / active license and changing the HA MODE, and upgrading the firmware on the Sophos UTM, the internet is still slow.  If we disabled UTM, web browsing is super fast.
There was a slight improvement but I'll say it's about a 5% improvement compare to not switching to a active/active configuration.

Before the active/active mode change, we had a complete loss of web browsing for about 20 - 30 seconds.  And it would happen 3 times a day.  Now, the complete loss of internet browsing is solved, but it's still noticeably slow.  Sometimes it still takes 20 - 30 seconds to browse to your regular news or yahoo or any normal big websites.

So, at this point Sophos UTM is slow.  I'm hoping the next firmware upgrade will fix this.

I have high hopes for Sophos, since it's really user friendly.

Leave a comment if it happens to you.