setkey makes program not running anymore

Bug #147118 reported by Zenigata
4
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

Since the las few days I have a problem with Gutsy (amd64)

When using setkey and racoon to set up an ipsec connection to a wifi network, after loading the ipsec.conf file, I am unable to run _any_ other program, meaning that I am unable to log on TTY1 (unable to run a shell) but the programs that were running are still running and responding.

Here is my configuration for ipsec :

racoon.conf :

path pre_shared_key "/etc/racoon/psk.txt";

remote 192.168.0.1
{
        exchange_mode main;
        proposal {
                encryption_algorithm 3des;
                hash_algorithm sha1;
                authentication_method pre_shared_key;
                dh_group modp1024;
        }
        generate_policy off;
}

sainfo address 192.168.1.2 any address 0.0.0.0/0 any
{
        pfs_group modp1024;
        encryption_algorithm rijndael, blowfish, 3des;
        authentication_algorithm hmac_sha1, hmac_md5;
        compression_algorithm deflate;
}

ipsec.conf
#!/usr/sbin/setkey -f

spdflush;

spdadd 192.168.1.2[68] 0.0.0.0/0[67] any -P out ipsec
  esp/tunnel/192.168.1.2-192.168.0.1/use;
spdadd 0.0.0.0/0[67] 192.168.1.2[68] any -P in ipsec
  esp/tunnel/192.168.0.1-192.168.1.2/use;
spdadd 192.168.1.2 0.0.0.0/0 any -P out ipsec
  esp/tunnel/192.168.1.2-192.168.0.1/require;
spdadd 0.0.0.0/0 192.168.1.2 any -P in ipsec
  esp/tunnel/192.168.0.1-192.168.1.2/require;

and here are the command I used to type in order to initiate the tunnel :

modprobe esp4
setkey -F
setkey -P -F
dhclient eth1
setkey -f /etc/ipsec.conf
/etc/init.d/racoon restart

The problem now occurs just after the line setkey -f /etc/ipsec.conf

I know that there is probably a lot of information missing, but now I just don'nt know where to seek for it, event thought I would suspect a problem in the kernel.

Revision history for this message
Doooh_Head (doooh-head) wrote :

I think I have a similar problem, but I've discovered it in a different way. My specific problem is related to KVpnc and using it to connect to my company vpn. The problem is that the authentication method "hmac_sha1" is now (in Gutsy) no longer available (from where ever). In the code posted, I notice that you are attempting to use the same authentication method.

Revision history for this message
Craig Maloney (craig-decafbad) wrote :

Have you had any luck with this under Hardy?

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.