On 6/11/07, lonely wolf <[EMAIL PROTECTED]> wrote:
lonely wolf wrote: Chiar merge direct rebuild: [EMAIL PROTECTED] --rebuild /home/wolfy/rpm/SRPMS/openswan-2.4.7-1.src.rpm [...] Provides: config(openswan) = 2.4.7-1 ipsec-userland Requires(interp): /bin/sh /bin/sh /bin/sh Wrote: /home/wolfy/rpm/RPMS/i386/openswan-2.4.7-1.i386.rpm Wrote: /home/wolfy/rpm/RPMS/i386/openswan-doc-2.4.7-1.i386.rpm
Pai asa i-am dat si eu (am scris asta in emailul anterior): rpmbuild -ta --clean --target=i686 openswan-2.4.8.tar.gz Wrote: /home/alex/rpm/SRPMS/openswan-2.4.8-1.src.rpm Wrote: /home/alex/rpm/RPMS/i686/openswan-2.4.8-1.i686.rpm Wrote: /home/alex/rpm/RPMS/i686/openswan-doc-2.4.8-1.i686.rpm Am insa mai multe neclaritati: Din documentatie inteleg ca sunt 2 variante de instalare pentru kernel 2.6.x : a) fara recompilare de kernel dar cu compilare de openswan - utilizind suportul "built in" in kernel 2.6 pentru IPsec stack (NETKEY). Super nice! Adica varianta care ai aplicat-o tu si eu cind am dat rpmbuild -ta --clean --target=i686 openswan-2.4.8.tar.gz si rpm -ivh openswan-2.4.8-1.i686.rpm. Corect? In acest caz, binarul de openswan obtinut & kernelul din centos4.5 ( 2.6.9-55.EL) suporta NAT-TRANSVERSAL? Ei spun in documentatie ca pe RHEL3 functioneaza by default, dar de RHEL4/centos4 nu spun nimic (see http://wiki.openswan.org/index.php/Openswan/RHEL) . b) cu recompilare de kernel si de Openswan folosind modulul klips (sau openswan KLIPS stack cum spun ei), caz in care ai si NAT-T Am inteles corect? Daca e asa, varianta a doua nu ma intereseaza decit in cazul in care cu varianta a) nu se poate face NAT-T. Pina la urma cum e cu NAT-TRANSVERSAL in prima varianta? Alx _______________________________________________ RLUG mailing list [email protected] http://lists.lug.ro/mailman/listinfo/rlug
