(racoon 689) Multiple clients from one gateway

Mark Lindsay <[email protected]> Thu, 02 Sep 2004 16:12:17 +0100
Newsgroups gmane.network.ipv6.kame.racoon
Organization Icera
Message-ID <1094137937.2605.37.camel@lts>
Hi,
	I have successfully set up a racoon server that happily works with a
client at home that has a dynamic address and uses certificates.

It looks like this:-

192.168.6.181(1st client) -- 172.16.1.35 (home gateway) <-Internet->
217.46.146.25 (office gateway) -- 192.168.1.0/24 (office network)


When I add a second client, the first client still works but the second
client does not see the office network.

It looks like this:-

192.168.6.181(1st client) -- 172.16.1.35 (home gateway) <-Internet->
217.46.146.25 (office gateway) -- 192.168.1.0/24 (office network)

192.168.6.182(2nd client) -- 172.16.1.35 (home gateway) <-Internet->
217.46.146.25 (office gateway) -- 192.168.1.0/24 (office network)

My question, is it possible to have 2 clients coming from behind the
same gateway?

Thanks for reading this far!

Mark ;)



My racoon.conf file looks like this:-
                                                
path include "/etc/racoon";
path pre_shared_key "/etc/racoon/psk.txt";
path certificate "/etc/racoon/certs";
padding
{
        maximum_length 20;
        randomize off;
        strict_check off;
        exclusive_tail off;
}
timer
{
        counter 5;
        interval 20 sec;
        persend 1;
        phase1 90 sec;
        phase2 60 sec;
}                                                           
remote 81.138.205.180
{
        exchange_mode main,aggressive;
        doi ipsec_doi;
        situation identity_only;
        my_identifier asn1dn;
        peers_identifier asn1dn;
        certificate_type x509 "gateway1.crt" "gateway1.key";
        peers_certfile "gateway2.crt";
        nonce_size 16;
        lifetime time 4 hour;
        initial_contact on;
        support_mip6 on;
        proposal_check obey;
        proposal {
                encryption_algorithm 3des;
                hash_algorithm md5;
                authentication_method rsasig ;
                dh_group 2 ;
        }
}                                                                    
remote anonymous
{
        exchange_mode aggressive,main;
        passive on;
        doi ipsec_doi;
        my_identifier asn1dn;
        peers_identifier asn1dn;
        certificate_type x509 "gateway1.crt" "gateway1.key";
        nonce_size 16;
        lifetime time 4 hour;
        initial_contact on;
        generate_policy on;
        proposal_check obey;
        proposal {
                encryption_algorithm 3des;
                hash_algorithm sha1;
                authentication_method rsasig ;
                dh_group 2 ;
        }
}                                                                
sainfo anonymous
{
        pfs_group 2;
        lifetime time 1 hour ;
        encryption_algorithm 3des, des ;
        authentication_algorithm hmac_sha1, hmac_md5 ;
        compression_algorithm deflate ;
}