Friday, November 21, 2008

Saturday, October 11, 2008

UBNT Wispstation - default config

UBNT: WispStation board - 22 dBm AP/klient (5 GHz)

Default IP
Default name ubnt
Default password ubnt

Friday, October 10, 2008

System Information for Windows

SIW is an advanced System Information for Windows tool that gathers detailed information about your system properties and settings and displays it in an extremely comprehensible manner.

This tool is extremely useful when you need to get your activation code from already installed Windows OS. When this tool does not work you can try KeyFinder

Sunday, August 24, 2008

Thursday, July 24, 2008


Virustotal is a service that analyzes suspicious files and facilitates the quick detection of viruses, worms, trojans, and all kinds of malware detected by antivirus engines. More information...

Wednesday, June 25, 2008

Understanding and fixing VMware ESX problems without pulling the plug

Understanding and fixing VMware ESX problems without pulling the plug
Eric Siebert, Contributor

Wednesday, June 04, 2008

VMware: configuring a static MAC address in a VM

Original article from

Sometimes it can be necessary to configure a static MAC address in a VM. A typical issue during P2V is an application that has its licensing based on the MAC address.

VMware has defined that VirtualCenter does not use the following range: 00:50:56:00:00:00 to 00:50:56:3F:FF:FF where 00:50:56 is the OUI.

The steps:

1. Power off & remove the server from the VirtualCenter inventory. This is a necessary step, because VC will overwrite your settings during Power On!
2. Edit the .vmx file and locate the following generated MAC address:
Ethernet0.addressType =
Ethernet0.generatedAddress =
3. Change the value for ethernet0.addressType from “vpx” to “static”
4. Change ethernet0.GeneratedAddress to ethernet0.Address
5. Change the current MAC to a MAC address in the following range:
6. In VirtualCenter, select an ESX host and go to storage
7. Browse the data store & locate your VM
8. Right-click on the .vmx file, and select Add to inventory
9. Power On the server. Issue the command ipconfig /all and locate the VMware NIC. Your manually assigned MAC address should be there.

I know you can set your MAC address inside Windows, but I would avoid this.

Monday, June 02, 2008

DELL Professional Services aneb GICS

Presne 15.5.2006 jsem nastoupil do DELLu a psal jsem o tom, ze DELL krome produktu nabizi i profesionalni konzultanty, architekty a inzenyry. Viz.

Presne 15.5.2008 jsem se stal clenem byvaleho DPS - DELL Professional Services, ktere se dnes jmenuje GICS - Global Infrastructure Consulting Services. Moje zamereni je primarne na serverovou konsolidaci a virtualizaci, nicmene jelikoz jsem zatim prvni Solution Architect DELLu v Ceske Republice, tak mam na starosti i enterprise storage a networking.

Wednesday, April 16, 2008

Friday, March 21, 2008

ESX Server, NIC Teaming, and VLAN Trunking

Following article is from

There are actually two different pieces described in this article. The first is NIC teaming, in which we logically bind together multiple physical NICs for increased throughput and increased fault tolerance. The second is VLAN trunking, in which we configure the physical switch to pass VLAN traffic directly to ESX Server, which will then distribute the traffic according to the port groups and VLAN IDs configured on the server. I wrote about ESX and VLAN trunking a long time ago and ran into some issues then; here I’ll describe how to work around the issues I ran into at that time.

Full article:

Other useful technical paper about VLAN on ESX is at

Friday, March 14, 2008

How to Set up VNC on Debian GNU/Linux

Installation and usage

You've just installed Debian, but your wife wants her monitor back. That's OK, you were planning on running it headless, anyway. But, wouldn't it be nice to check out some of those groovy GUI apps? Don't fret, VNC will let you interact with a desktop environment from just about any platform available.

Install vncserver (as root):
apt-get install vncserver

Choose your desired window size and color depth, then, as an ordinary user, open a terminal and type:
vncserver -geometry 1024x768 -depth 24
vncserver -geometry 1024x768 -depth 24 -pixelformat rgb565

This will prompt you to create a password:

You will require a password to access your desktops.


The server will start and tell you where to access it:

New 'X' desktop is foobar:1

Starting applications specified in /etc/X11/Xsession
Log file is /home/jorey/.vnc/foobar:1.log

Open the VNC viewer on your remote machine, enter the hostname:screen and password (use a hostname or IP that your client machine understands), and your Linux desktop will open in a window! Network speed and processor power will affect performance, but it's amazing how many apps will run fine under VNC. You might not be able to play Frozen Bubble, but you can use productivity applications without any trouble.

To kill the server enter a command similar to this, using the appropriate settings:
vncserver -kill :1

The reason for killing the session is that you may need to edit the default configuration file that vncserver creates for you, for example to get the vncserver to run the K desktop environment instead of twm, you may want to edit the $HOME/.vnc/xstartup file to replace the line:

twm &

with this line is you use KDE:

startkde &

and with this line if you use GNOME:

gnome-session &

before launching the vncserver again using:

vncserver :1 -geometry 1024x768 -depth 16 -pixelformat rgb565

VNC over OpenSSH

The following is just a summary of the full explanation. To use VNC over OpenSSH, first you need to run an ssh session on the machine where you will be running the vncviewer, to request that ssh listen on a particular port on your local machine, and forward communication on that port down the secure connection to a port on the machine running the vncserver.

For example:

ssh -L x:localhost:y vncserver_machine

means "Start an SSH connection to the vncserver_machine, and also listen on port x on my machine, and forward any connections there to port y on the vncserver_machine."

Now, the VNC protocol normally uses port 59xx, where xx is the display number of the server. So a VNC server on a Windows machine, which normally uses display number 0, will listen on port 5900. The first VNC server on linux will probably use display number 1, and subsequent servers would use 2, 3, etc. and so the vncservers on linux will be listening on ports 5901, 5902 and so forth. By forwarding these ports to a remote machine running vncserver, you can make the remote VNC server appear to be a server running on your local machine. So, imagine you had a VNC server running as display :1 on vncserver_machine, and you wanted a secure connection to it from your local machine. You could start the ssh session using:

ssh -CL 5902:localhost:5901 vncserver_machine

After that, starting up the vncviewer as follows on your local machine: vncviewer -encodings "copyrect hextile" localhost:2 would actually connect to display :1 on the vncserver_machine.

Note that the above OpenSSH command-line is deliberately meant to accept incoming connections only from the local machine. This means that to use the ssh connection that we have just set up, we must connect to it from the same machine, using the special name localhost, rather than using the local machine's own unique name.

This article is compiled from following resources:

X Window Servers

"X Server" for Windows XP and Vista

X Ming "X Server"

"X Server" for Mac OS X

Tuesday, February 26, 2008


Paolo Conti wrote how to hack VMware tools to work on linux kernels 2.6.18


Well, VMWare tools sometimes fails to install into a Linux guest with recent kernel.

The error is something like this: The directory of kernel headers (version @@VMWARE@@ UTS_RELEASE) does not match your running kernel (version Even if the module were to compile successfully, it would not load into the running kernel.

With this bug you cannot sync the time with your hosting server, automate shutdown tasks, etc… This problem exist because the kernel source code structure is changed in recent kernels (I guess > 2.6.18). The VMWare tools installation script is looking for the string “#define UTS_RELEASE $kernel_number” into /usr/src/kernels/$(uname -r)*/include/linux/version.h but the UTS_RELEASE variable is now into the file utsrelease.h.

To fix this, you can patch the VMWare tools installation script or just add the content of utsrelease.h to version.h. I suppose the second solution is the fastest one :)

To do this:

cd /usr/src/kernels/$(uname -r)*/include/linux
cat utsrelease.h >> version.h

Happy virtualization folks! :)

Saturday, February 23, 2008

Eth0 disappears after cloning

When I used VMWare Cloning of Debian Gold image everything was OK except networking. Eth0 disappeared and Eth1 came up. It's due to MAC address persistent association in /etc/udev/rules.d/z25_persistent-net.rules. Solution is to avoid persistent association. If you open this file you'll see that old MAC address is associated with eth0 so you can change this MAC address. However, the easiest solution is just delete file /etc/udev/rules.d/z25_persistent-net.rules. File will be created after next reboot but with MAC address of current network card.

Sunday, January 06, 2008