If you wanna try Immunity Canvas but have no much money to buy it so probably you’ll try Immunity Canvas product which was leak on internet (by somebody called ‘ikex’?), and if  you’re using Snow Leopard then probably you’ll face same problem with me.

As we know, Immunity Canvas 6.23 required libglade and pygtk (no idea of latest release, sorry). Under documentation directory there’s note about how to install it on Mac OSX:

# NOTE:
# If you install python before, or install the ports in different order and the GUI
# is not working for you, try uninstalll all the port and install it in the right order

[o] Install XcodeTools:
        -> Sometimes, the installer is on your HD already:
	 Applications->Installers->Xcode Tools->XcodeTools.mpkg
        -> Or find it on the Tiger DVD
        -> Or download it from apple.com website

[o] Download and install Darwinports :

http://www.darwinports.org/getdp/

	The usual: ./configure && make && sudo make install
	once they are installed:
	(change PATH to /opt/local/bin)

	If you are behind an http_proxy, you would probably need:
	$ sudo -s
	# export RSYNC_PROXY=192.168.1.1:3128
	# export ftp_proxy=192.168.1.1:3128
	# export http_proxy=192.168.1.1:3128
	# port -d selfupdate

	or just
	$ sudo port -d selfupdate

[o] Install libglade and pygtk
	$ sudo port install libglade2 py-gtk2

[o] Install X11?
       If you dont have X11 (Tiger OSX users can find it on the DVD, go to "Optional Installs)) you can download it from the Apple website:

http://www.apple.com/downloads/macosx/apple/x11formacosx.html

	Download X11User.dmg and install it 

[o] Run X11
   Having X11 doesn't mean your GUI will change at all, it will simply open an xterm where you will be able to run the CANVAS gui.
   $ /Applications/Utilities/X11.app/Contents/MacOS/X11 &

[o] run canvas 
 /opt/local/bin/python ./runcanvas.py

Unfortunately, I found this error when time come to run CANVAS (of course, I am using python2.4 to run it):

bash-3.2$ /opt/local/bin/python2.4 ./runcanvas.py
Traceback (most recent call last):
  File "./runcanvas.py", line 15, in ?
    from canvasengine import canvasmain
  File "/Applications/Immunity Canvas/canvasengine.py", line 38, in ?
    from libs.daveutil import dmkdir
  File "/Applications/Immunity Canvas/libs/daveutil.py", line 14, in ?
    import spkproxy
  File "/Applications/Immunity Canvas/libs/spkproxy.py", line 23, in ?
    from libs.tlslite.api import *
  File "/Applications/Immunity Canvas/libs/tlslite/api.py", line 61, in ?
    from integration.TLSAsyncDispatcherMixIn import TLSAsyncDispatcherMixIn
  File "/Applications/Immunity Canvas/libs/tlslite/integration/TLSAsyncDispatcherMixIn.py", line 5, in ?
    import asyncore
  File "/opt/local/lib/python2.4/asyncore.py", line 55, in ?
    from errno import EALREADY, EINPROGRESS, EWOULDBLOCK, ECONNRESET, \
ImportError: cannot import name ESHUTDOWN

I am not a python guru, so what I can guess is Snow Leopard not support ESHUTDOWN as stated on lib/python2.4/asyncore.py. I tried to take a look at python2.5 but still similar call exist there. So, the dirty patch to make this version of Immunity Canvas work is by removing ESHUTDOWN from asyncore.py. Then the problem will disappear and you can have Immunity Canvas GUI running on Snow Leopard.

Btw, asyncore was imported by Immunity Canvas to handle async socket.

Found these error:

compiling openssl
gcc -I. -I../../.ext/include/i686-darwin10.2.0 -I../.././include -I../.././ext/openssl -DRUBY_EXTCONF_H=\"extconf.h\"    -fno-common -g -O2 -pipe -fno-common   -o openssl_missing.o -c openssl_missing.c
In file included from openssl_missing.c:22:
openssl_missing.h:119: error: conflicting types for ‘BN_rand_range’
/usr/include/openssl/bn.h:411: error: previous declaration of ‘BN_rand_range’ was here
openssl_missing.h:120: error: conflicting types for ‘BN_pseudo_rand_range’
/usr/include/openssl/bn.h:412: error: previous declaration of ‘BN_pseudo_rand_range’ was here
make[1]: *** [openssl_missing.o] Error 1
make: *** [all] Error 1

The error was caused by conflicting declaration of BN_rand_range and BN_pseudo_rand_range function defined on /usr/include/openssl/bn.h (Snow Leopard) and ext/openssl/openssl_missing.h (ruby ext).

file: /usr/include/openssl/bn.h
...
int	BN_rand_range(BIGNUM *rnd, const BIGNUM *range);
int	BN_pseudo_rand_range(BIGNUM *rnd, const BIGNUM *range);
...

file: ext/openssl/openssl_missing.h
...
int BN_rand_range(BIGNUM *r, BIGNUM *range);
int BN_pseudo_rand_range(BIGNUM *r, BIGNUM *range);
...

Commenting those 2 function on either file will solve the problem. This problem already solved on Ruby.1.9.1, so there will be no such problem compiling and installing that version of ruby on Snow Leopard. Just in case you found similar problem and you NEED to use 1.9.0.0, then above solution will solve it. Just for my personal record anyway.

Seringkali terjadi diskusi menarik di milis parakontel (para kontraktor telekomunikasi indonesia), umumnya yang sering menjadi polemik adalah hal-hal non-teknis seperti masalah berapa rate salary yang tepat saat overseas. Dan diskusi tersebut baru-baru ini muncul di milis. Sebagai pendatang baru (newbie) hal tersebut biasanya menjadi masalah, terutama sekarang-sekarang ini. Saat saya mulai overseas dulu (tahun 2007) memang kabar yang terdengar rate untuk “ngagen” (istilah engineer-engineer telekomunikasi yang mengerjakan project overseas via agency) berkisar 7k (usd / eur). Namun pada kenyataannya tiap project tidak selalu sama.

Akhir-akhir ini beberapa project mengalami penurunan drastis, sehingga rate yang ditawarkan jauh dibawah 7k tersebut. Dan diskusi menarik tersebut muncul ketika salah satu peserta milis mempertanyakan hal tersebut dimana dia heran melihat project-project yang ditawarkan nilainya jauh dibawah rumor yang selama ini dia dengar. Berhubung saat itu project di georgia sudah selesai dan saya dalam masa tenggang menunggu project di armenia, maka saya coba buat sedikit summary mengenai masalah rate salary ke milis parakontel.

Milis parakontel saat ini sifatnya eksklusif, dalam arti pendatang baru yang ingin join harus menggunakan referensi dari anggota yang sudah join untuk bisa di approve. Jadi summary yang saya buat akan ditulis kembali disini dengan harapan bisa menjadi sedikit bekal informasi bagi para newbie yang kebetulan belum bisa mengakses milis / group parakontel.

Read the rest of this entry »

HLRd system use SUN machines for its HLR-FE, and recent SUN’s machine has ALOM (Advanced Lights Out Manager) to manage the server. Recently, 3 HLR-FE had problem with ALOM NET MGMT interface, thus I can’t connect to ALOM using network connection. The only way is using default connection, it require serial cable to connect.

I am using MacBook, and like recent common laptop there’s no serial port. So the only way to use usb-to-serial cable for connecting to serial port on SUN’s machine. The cable already packaged with driver for Linux, OSX, and Windows. It’s very easy to install, but if you don’t have the driver or it’s lost, you can try to use prolific driver.

The driver wouldn’t create permanent link to device via /dev filesystem, but it will automatically create when we connect the serial connection to peer port. In my macbook, it create /dev/tty.usbserial file. We can connect through ZTerm, but since default OSX terminal application support ASCII communication, I can just use terminal.app to connect to ALOM serial management interface using:

$ screen /dev/tty.usbserial 9600

And it just simply connected to ALOM.

Ah ya, regarding problem of NET MGMT interface is not enabled even though configuration already applied on ALOM, it will be solved by resetting the ALOM (resetting the ALOM won’t reboot the host server, thus safe to be done in live system). A friend of mine from Fujitsu told me sometime ALOM is like hanging (??!@?!) and reset is necessary to make it work properly again.

I used to operate Solaris server at work, and sometimes I need to use Desktop application from that server. I learned for the first time at Siemens Indonesia using export display from solaris machine into local machine (laptop) which run M$ Windows, at that time we have exceeds application inside laptop which can be used to retrieve X session from solaris. Exceeds act just like Xserver for Microsoft Windows.

This method is used until few months ago. I admit it was easy using exceeds especially for XDMCP Query or XDMCP broadcast protocol, using that protocol we can retrieve login session and log into that solaris machine. Unfortunately, I am using Mac OSX. And to do that, I had to fire-up my Windows under Virtual Machine or reboot and log into Microsoft Windows as my second boot OS. Usually it’s not a big problem, because what usually important is playing with “nwadmin”, it’s a window based administration tools for networker application. Networker application itself is a software for backup&restore within @vantage platform which I am handling at work.

While working in Georgia, the network is quite restricted. Somehow I can’t use my Windows virtual machine to run “nwadmin” remotely using “export display”. I have to reboot OSX and log into windows just to manage B&R window. It’s annoying. Later I tried to look another way retrieving solaris window application from my OSX.

I tried to follow using old method, that is using export display. But it was failed due to authentication. I already start X11 on my OSX, and perform “remote DISPLAY=<OSX_IP_ADDR:0.0>”, but it show error:

Xlib: Invalid MIT-MAGIC-COOKIE-1 key os x

That error appear on console of solaris, while from OSX it said client connection was rejected. I was trying to dig deeper about this “MIT-MAGIC-COOKIE” thing but unfortunately my attention was go to some statement on one forum which said it’s better to use SSH X Forwarding, it’s more secure. Well, system within HLRD these days also give more restriction for security, like hardening the operating system, using SSH instead of telnet or rlogin, etc. So I think it’s better to use SSH-X-Forwarding to get “nwadmin” windows.

Configuration is pretty easy. From solaris server just modify sshd configuration (/etc/ssh/sshd_config) to enable X11 Forwarding:

X11Forwarding yes
X11DisplayOffset 10
X11UseLocalhost yes

Restart sshd on solaris.

From X11 application on OSX, start terminal (xterm), and ssh using -X option to that server:

bash$ ssh -X root@[B&R_IP_ADDR]
root@B&R# nwadmin

Just run some X application, it will immediately show the window on our OSX Desktop.