Archive for the 'linux' Category

vpnc error ISAKMP_N_AUTHENTICATION_FAILED(24)

Sunday, January 28th, 2007

for those who wants use vpnc and converting cisco .pcf configuration file to vpnc config file, whatch for this pitfall. because of my impatient to setup vpnc on my brand new debian etch, i copy and paste decoded enc_GroupPwd from cisco vpnclient password decoder. and that’s true as suggested in that mailing list conversation, there are trailing spaces that caused me an ISAKMP_N_AUTHENTICATION_FAILED(24):
IPSec secret mypasswordforcisco3000 $

debian etch 20061230 with ipw3945

Sunday, January 28th, 2007

at last i got change to have a journey back with debian. after very long delay (until now i think) for new release of stable debian, i became unpatient, and i need new debian on my presario v5000 notebook. so on last dec 30 2006, i download daily etch netinst cd, and began the installation process. took about 4 hours to install base operating system, my downlink only 256kbs, so throughput around 160kbps, really slow for net install. after installation, i looked at the pci list:

creating openldap2.3 deb package on debian 3.1r1 - pthread_create problem

Sunday, January 28th, 2007

i need to have syncrepl on my ldap implementation to substitute slurpd, but the server running debian 3.1r1 with openldap 2.2 which is not have syncrepl capability. so i get debian source of openldap 2.3, and began debian package creation. but at very last stage of package creation, it stoped. it complaints that pthreat_create can not be resolved. how the thell can it be? as far as i know glibc on debian 3.1r1 supports pthread. after some searching, i found this on openldap devel mailing list. i applied the the fixes and restarted the process, and it worked! funny thing i found later that the converstion on that list was on 2003, for openldap prior to 2.2 for sure. how come openldap developer still forget to include this fix on 2.3? anyway, i got openldap 2.3 deb package now, waiting for testing and implementation…. real hard work to come….

it was archived! thank you waybackmachine!

Friday, January 26th, 2007

back in late 1999/early 2000, it was pre RedHat 6.0 era, and i’ve been using RedHat 5.2 for almost a year. my RH 5.2 was heavily patched, i upgrade almost everything to become 6.0, even libc recompiled to statisfy some depedency. Gnome 1.0, was still in the very early stage of appearence, Enlightenment was already on 0.16.3 (currently it’s still 0.16.7.2 on my Ubuntu). i put my notes (in Indonesian) on them in my personal site called eworld, and yes, it’s dead now. too bad i don’t keep them, it was lost from my documents when i changed pc several times. i have contacted my former provider to beg for the archive, but they said they didn’t keep it. i feel terrible because i think it is a prove of my desire to blog in the era (i don’t recall term blog ever heard that day).

123 ssh tunneling, LDAP traffic

Thursday, January 25th, 2007

here is the scenario: i got LDAP host located on an isp in the private network, i got one of my application server (i call it nakula) located on the same ISP and luckily designed to have private ip and public ip. so this one will not have a problem talking to LDAP server. but my other application server (and let’s call this one sadewa) is located on the other side of the world somewhere. these applications heavily dependant on directory entries kept in that LDAP server. nakula has 2 network interface, one is for serving it’s application to public therefore assigned public ip, and the other one is for talking to LDAP server, so private ip assigned to it. the problem is on sadewa, it has no physical connection to my LDAP server.