https://pi-hole.net/

Pi-hole on Docker

Troubleshooting tips:
1. Custom blocking domain not working from web interface
- cp /etc/.pihole/gravity.sh /opt/pihole/
Some others scripts might need to be copy over.

2.Optimize DNS configuration
- vi /etc/dnsmasq.d/01-pihole.conf

cache-size=10000
local-ttl=300

QNAP Container Station

Docker in QNAP Container Station

A very light weight virtual environment for sandbox.

Docker networks:

-Bridge
-Host
-None
-Qnet (*Available on QNAP CS only)

The first three networks are built into Docker. When you run a container, you can use the --network flag to specify which networks your container should connect to.

Containers connected to the default bridge network can communicate with each other by IP address.

The host network adds a container on the host’s network stack. There is no isolation between the host machine and the container. If you run a container that runs a web server on port 80 using host networking, the web server is available on port 80 of the host machine.

The none and host networks are not configurable in Docker. You can configure the default bridge network, as well as your own user-defined bridge networks.

QNAP Qnet Docker Command

With QNAP CS, you can also use Docker command to create a network that belongs to Qnet driver and run a container with --net argument.
I will say the above in English :
It means you can bridge docker network to host network!!
Both docker and host can reside on the same LAN segment, and looks like 2 machine. 

DHCP mode

Create a new network named qnet-dhcp-eth1.

    $ docker network create -d qnet --ipam-driver=qnet --ipam-opt=iface=eth1 qnet-dhcp-eth1

Static mode

Create a new network named qnet-static-eth1.

    $ docker network create -d qnet --ipam-driver=qnet --ipam-opt=iface=eth1 \
          --subnet=192.168.18.0/23 --gateway=192.168.18.254 qnet-static-eth1

Reference:

https://docs.docker.com/engine/userguide/networking/
https://qnap-dev.github.io/container-station-api/qnet.html
https://success.docker.com/KBase/Multiple_Docker_Networks

Obi110 Voip SIP ATA

Obi110 is a great VOIP ATA for those frequent traveler intent to keep in touch with buddys and family members back at home.

Let's take a look at this small little box with VOIP magic that save thousands of dollars for my IDD phone call.
 

Mobile IPsec on Pfsense

You can connect a number of devices to pfSense 2.0 using IPsec, most notably Android (Phones and Tablets) and iOS (iPhone, iPad, iPod Touch, etc) devices but anything that is capable of IPsec will typically work. This document covers the most common setup for mobile devices, which is IPsec using Xauth and a mutual Pre-Shared Key.

1. IPsec Server Setup

This is the setup for the pfSense side of the connection
#Mobile Clients

Setup Debian netboot server on Synology

1. Install dnsmasq

Before installing dnsmasq, install optware if you haven’t done so (see [1]). Then install dnsmasq via ipkg:

ipkg install dnsmasq

2. Configuration

Edit dnsmasq.conf in /opt/etc, the following is sample config (or check the original example [2]):

# DHCP IP range and lease
dhcp-range=192.168.0.100,192.168.0.200,255.255.255.0,12h
dhcp-leasefile=/opt/var/lib/dnsmasq.leases
# DHCP Fixed IP settings
dhcp-host=XX:XX:XX:XX:XX:XX,192.168.0.101
# DHCP gateway option
dhcp-option=option:router,192.168.0.1
# DHCP dns option, if you don't want to use dnsmasq's DNS service
dhcp-option=option:dns-server,8.8.8.8,4.4.4.2
 
# PXE boot options
dhcp-boot=pxelinux.0
enable-tftp
tftp-root=/volume1/netboot

3. Prepare tftp root directory

The above configuration sets the root directory for tftp server to /volume1/netboot. If it is not there already, create it and put Debian netboot files ([3]) there.

mkdir /volume1/netboot
wget –O - http://ftp.debian.org/debian/dists/stable/main/installer-amd64/current/images/netboot/netboot.tar.gz | tar xzf - 

Marvell Kirkwood MV6282 1.6Ghz ARM

Finally, i have bought my 1st NAS on 22March2011.
Between Synology and QNAP, i made my choice.

Besides the price tag but the nice interface and forum support.
For the next few weeks, I can imagine i'll be very busy
setting up my first ARM linux box.

By the way, [My first x86 linux => Fedora 5 x86 @ 2005]
The very first i would like to try to cross compile Gnokii on my Ubuntu 9.

Install Seagate HDD on my DS111.

My 5M UniFi

We have our application submitted on Dec2010,
finally the installation team arrived.

With some extra charges to get the fiber into my ceiling.
UP for my 5M package.



Sayonaro for my 1M Streamyx after so many years.

Special thanks to:-

unofficial HSBB (Unifi) "handbook" => http://unifi.athena.my/index.html
Broadband U2U @ LYN => http://forum.lowyat.net/BroadbandUser-2-User
KL Seet => http://klseet.com/

for all the UniFi pre and post installation guide.

Ubuntu-Jaunty-desktop

Virtual-Box + XPsp2 => Jaunty.
Success!

[分享] 1Mb宽频是芬兰法定权利！大马呢？

还在为网速超慢或无法连线上网而烦吗？请珍惜你手中一票，在下一次大选推选一个尊重宽频发展的政府，并促请朝野各政党议员们透过一项法案：1Mbps宽频连线是法定权利!

是的，你没有听错，1Mbps宽频是法定权利。这并不是笑话，芬兰的运输与通讯部已把1Mb宽频网络存取权明定为法定权利。

根据芬兰国家广播公司YLE网站报导指出，自7月起，芬兰所有的人民(据2009年估计，总数略超高500万人)都将享有存取1Mb宽频网络的权利，未来他们还可能有权存取100Mb宽频网络。

一年多前芬兰就预告，要在2015年底之前，把存取100Mb宽频网络定为国民的法定权利。周三的声明被视为过渡时期的措施。

存取互联网是基本人权

在法国，宪法委员会今年稍早已裁定，存取互联网是一种基本人权。但法国并未规定“宽频存取”(broadband access)是法定权利。芬兰宣称，该国是全球第一个明定宽频存取为法定权利的国家。

不过，芬兰并没有阐明如果电讯商已经违法的话，有何惩罚？而且对于宽频“存取”(access)的定义也有点模糊。

根据赫尔辛基时报(Helsinki Times)去年针对100Mb宽频网路目标的报导，芬兰政府当时说，全国各地的家庭，“未来与可提供宽频网络的连线的距离，都会在2公里范围内，而宽频网络的资料传输速率至少是每秒100Mb”。但报导另指出，偏远地区约2,000户家庭不包括在内。显然，芬兰实施1Mb宽频存取计划时，也将比照办理。

芬兰一向是科技业的领导者，在科技方面的投资不遗余力，比欧洲许多国家先进。芬兰也是全球手机龙头诺基亚（Nokia）及其他科技公司的家乡。

大马需要多久才敢把1Mb宽频网络存取定为法定权利？如果真的在我国实施的话，有多少家电讯商已经违法？


（TechDaily电子报10月15日综合报道）

Adding JDK 6 Javadoc to NetBeans IDE 6

I have been working on this for bl**dy ages...
I google and try a tons of useless tips and trick,
Finally i figure out, it is only some simple steps.
Not complicated at all and no JAR involved.

I would like to share a few useful step here.

Download JDK documentation from
http://java.sun.com/javase/downloads/index.jsp#docs
The site is shutdown temporary.
Try google for mirror site.
Unzip the zip file to the JDK directory
In NetBeans IDE

1. Choose Tools > Java Platform Manager from the main window.
2. Select the platform to which you want to add Javadoc in the left panel of the dialog box.
3. In the Javadoc tab, click Add ZIP/Folder and specify the location of the Javadoc files.
4. Click Close.