1. Setup unifi
2. Setup DynDNS
3. Port Forwarding http://inranrumani.blogspot.com/2011/11/port-forward-di-openwrt-menggunakan.html
4. UPnP (http://wiki.openwrt.org/doc/howto/upnp)
5. ExtRoot
6. USB, Swap, FTP


USB+Swap+ExtRoot, Samba+FTP+Transmission, MiniDLNA, print server

Posted in Uncategorized.

Cisco Prime Data Center Network Manager (DCNM) is designed to help you efficiently implement and manage virtualized data centers. It includes a feature-rich, customizable dashboard that provides visibility and control through a single pane of glass to Cisco Nexus and MDS products.


1. You must have a desktop manager installed
2. Run dcnm installer from GUI (double-click), not from terminal
update: in v6.x you need to run the script from terminal, the installer wizard will popup to your desktop
Continue reading

VLAN Trunk Protocol (VTP) reduces administration in a switched network. When you configure a new VLAN on one VTP server, the VLAN is distributed through all switches in the domain. This reduces the need to configure the same VLAN everywhere.

VTP Modes

You can configure a switch to operate in any one of these VTP modes:

  • Server—In VTP server mode, you can create, modify, and delete VLANs and specify other configuration parameters, such as VTP version and VTP pruning, for the entire VTP domain. VTP servers advertise their VLAN configuration to other switches in the same VTP domain and synchronize their VLAN configuration with other switches based on advertisements received over trunk links. VTP server is the default mode.

  • Client—VTP clients behave the same way as VTP servers, but you cannot create, change, or delete VLANs on a VTP client.

  • Transparent—VTP transparent switches do not participate in VTP. A VTP transparent switch does not advertise its VLAN configuration and does not synchronize its VLAN configuration based on received advertisements, but transparent switches do forward VTP advertisements that they receive out their trunk ports in VTP Version 2.

VTP Password

If you configure a password for VTP, you must configure the password on all switches in the VTP domain. The password must be the same password on all those switches. The VTP password that you configure is translated by algorithm into a 16-byte word (MD5 value) that is carried in all summary-advertisement VTP packets.

VTP Pruning

VTP ensures that all switches in the VTP domain are aware of all VLANs. However, there are occasions when VTP can create unnecessary traffic. All unknown unicasts and broadcasts in a VLAN are flooded over the entire VLAN. All switches in the network receive all broadcasts, even in situations in which few users are connected in that VLAN. VTP pruning is a feature that you use in order to eliminate or prune this unnecessary traffic.

    Broadcast traffic in a switched network without pruning

    This figure shows a switched network without VTP pruning enabled. Port 1 on Switch A and Port 2 on Switch D are assigned to the Red VLAN. If a broadcast is sent from the host connected to Switch A, Switch A floods the broadcast and every switch in the network receives it, even though Switches C, E, and F have no ports in the Red VLAN.

    Broadcast traffic in a switched network with pruning
    This figure shows the same switched network with VTP pruning enabled. The broadcast traffic from Switch A is not forwarded to Switches C, E, and F because traffic for the Red VLAN has been pruned on the links shown (Port 5 on Switch B and Port 4 on Switch D).

Configuration Revision Number

The configuration revision number is a 32-bit number that indicates the level of revision for a VTP packet. Each VTP device tracks the VTP configuration revision number that is assigned to it. Most of the VTP packets contain the VTP configuration revision number of the sender.

This information is used in order to determine whether the received information is more recent than the current version. Each time that you make a VLAN change in a VTP device, the configuration revision is incremented by one. In order to reset the configuration revision of a switch, change the VTP domain name, and then change the name back to the original name.

Summary Advertisements

By default, Catalyst switches issue summary advertisements in five-minute increments. Summary advertisements inform adjacent Catalysts of the current VTP domain name and the configuration revision number.

When the switch receives a summary advertisement packet, the switch compares the VTP domain name to its own VTP domain name. If the name is different, the switch simply ignores the packet. If the name is the same, the switch then compares the configuration revision to its own revision. If its own configuration revision is higher or equal, the packet is ignored. If it is lower, an advertisement request is sent.


  • If a switch is configured as a VTP server without a VTP domain name, you cannot configure a VLAN on the switch.

    Note: It is applicable only for CatOS. You can configure VLAN(s) without having the VTP domain name on the switch which runs on IOS.

  • If a new Catalyst is attached in the border of two VTP domains, the new Catalyst keeps the domain name of the first switch that sends it a summary advertisement. The only way to attach this switch to another VTP domain is to manually set a different VTP domain name.

  • Dynamic Trunking Protocol (DTP) sends the VTP domain name in a DTP packet. Therefore, if you have two ends of a link that belong to different VTP domains, the trunk does not come up if you use DTP. In this special case, you must configure the trunk mode as on or nonegotiate, on both sides, in order to allow the trunk to come up without DTP negotiation agreement.

  • If the domain has a single VTP server and it crashes, the best and easiest way to restore the operation is to change any of the VTP clients in that domain to a VTP server. The configuration revision is still the same in the rest of the clients, even if the server crashes. Therefore, VTP works properly in the domain.

Source: http://www.cisco.com/en/US/tech/tk389/tk689/technologies_tech_note09186a0080094c52.shtml

1. Root using superoneclick
2. Download ODIN and modded kernel
3. Flash using ODIN, click on PDA and browse to modded kernel. Click start.
4. To confirm CWM installed, press vol down, home and power button together during boot.
5. Select desired ROM, at the moment have 2 choices:

  1. SuperROM
  2. Juffo

6. If using superROM, may opt to install ICS theme from here. –>install via CWM

Posted in Uncategorized.

I have an external HDD that being partitioned with ext3 and ntfs. Ext3 is for ubuntu boot from usb, while ntfs is mainly to store my data.

I can’t see my ntfs partition when i plugged in my external HDD into Buffalo NAS. However, ext3 is visible and mounted in /mnt/usbdisk1 also from samba.

Manual mount. Latest Linkstation firmware support ntfs by default, it just don’t mount all filesystem from the same usb port.

Identify partitions with ntfs

fdisk -l


fdisk -l | grep NTFS

Create mount point

mkdir /mnt/ntfs

Mount ntfs with read write access

mount -t ntfs-3g /dev/sdb3 /mnt/ntfs/

Unmount ntfs

umount /mnt/ntfs/

Goal 2: Installing optware

mkdir /mnt/disk1/tmp 
cd /mnt/disk1/tmp
wget http://goo.gl/G2Q3S
chmod +x ls-mvkw-bootstrap_1.2-7_arm.xsh
sh ./ls-mvkw-bootstrap_1.2-7_arm.xsh
mv /etc/init.d/optware /etc/init.d/rc.optware
ipkg update

Updating package – ipkg update

Upgrading package – ipkg upgrade
Installing package – ipkg install <package name>

Sometime when you reboot the NAS, optware will be gone. Refer to this thread for further detail.
To solve this, edit /etc/init.d/rc.optware file using vi or nano. Add this line of command

#! /bin/sh
mount --bind /mnt/disk1/.optware /opt


Posted in NAS.

With stock firmware, there’s no ssh/telnet capability in the box. We are going to “open” it.

Goal 1: Open the Stock Firmware

Get ACP Commander from here. This is the most useful tools ever created by the community to gain root access. You will need a Java JRE to be installed in your machine.

Verify that current admin password is work.

java -jar acp_commander.jar -t NAS_IP -ip NAS_IP -pw Youradminpassword -c "ls /"

Let’s the fun begin. First we’ll issue a new SSH password for root user

java -jar acp_commander.jar -t NAS_IP -ip NAS_IP -pw Youradminpassword -c "(echo newrootpass;echo newrootpass)¦passwd"

Then we’ll allow root to login using plaintext

java -jar acp_commander.jar -t NAS_IP -ip NAS_IP -pw Youradminpassword -c "sed -i 's/UsePAM yes/UsePAM no/g' /etc/sshd_config"

After that, we’ll need to allow root to SSH

java -jar acp_commander.jar -t NAS_IP -ip NAS_IP  -pw adminpasswordhere -c "sed -i 's/PermitRootLogin no/PermitRootLogin yes/g' /etc/sshd_config"

Restart SSH service

java -jar acp_commander.jar -t NAS_IP -ip NAS_IP -pw Youradminpassword -c "/etc/init.d/sshd.sh restart"

Now you will be able to SSH to your NAS box.


  1. NAS_IP is your Linkstation IP address
  2. Youradminpassword is your Linkstation Web UI password
  3. Newrootpass is your new root account password (for ssh)
  4. Still works with the latest firmware (1.63)
  5. Or you can try the easy way 😛

Another way of doing this (to prevent error during copying above command) is to execute this bash script from your Linkstation.
1. Copy this file, http://dl.advanxer.com/stuff/NAS/open-ls.sh to your computer.
2. From your computer, browse to your NAS shared folder.
3. Copy and paste open-ls.sh file to /share folder.
4. Execute this command from your computer (replace $DISK with disk1 or array1):

java -jar acp_commander.jar -t NAS_IP -ip NAS_IP -pw Youradminpassword -c "sh -x /mnt/$DISK/share/open-ls.txt"