Sponsored Content
Operating Systems Solaris What's wrong with my ipsec configuration? Post 303030883 by Linusolaradm1 on Monday 18th of February 2019 04:53:03 PM
Old 02-18-2019
What's wrong with my ipsec configuration?

I want a lan encrypted with ipsec.
This is my /etc/inet/ike/config


Code:
p1_xform
  { auth_method preshared oakley_group 5 auth_alg sha256 encr_alg aes }
p2_pfs 2


this is my /etc/inet/secret/ike.preshared


Code:
# ike.preshared on hostA, 192.168.0.21
#...
{ localidtype IP
    localid 192.168.0.21
    remoteidtype IP
    remoteid 192.168.0.119
    key *****...

}


this is my /etc/inet/ipsecinit.conf



Code:
# LAN traffic to and from this host can bypass IPsec.
{laddr 192.168.0.21 dir both} bypass {}

# Lan encrypted
{laddr 10.4.0.0/24 dir both} apply {auth_algs sha256 encr_algs aes sa shared}


Services are actives


Code:
for i in ike ipsec/policy;do svcadm refresh $i; done
svcs -a|grep ipse
disabled       22:12:33 svc:/network/ipsec/manual-key:default
online         22:12:56 svc:/network/ipsec/ipsecalgs:default
online         22:50:34 svc:/network/ipsec/ike:default
online         22:50:34 svc:/network/ipsec/policy:default


Interface is active
Code:
ifconfig  e1000g1
e1000g1: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 3
        inet 10.4.0.1 netmask ffffff00 broadcast 10.4.0.255
        ether SE:CR:ET


But nothing work, no ping,no telnet,nothing.


dmesg said


Code:
[ID 726330 kern.error] ipsec_check_global_policy: Dropping inbound secure datagram because it does not match the policy; Source 010.004.000.001, Destination 010.004.000.001.

 

10 More Discussions You Might Find Interesting

1. Solaris

Solaris 10 IPSec peformance

Hi, does anyone have an experience how many IPSec tunnels Solaris 10 is able manage. A rough estimation would be great. I know it's hardly dependent on the hardware used, so if anyone says on a 490 with 2 CPUs and 4GB RAM a maximum of 1000 IPSec tunnels is possible, that would be great. I... (1 Reply)
Discussion started by: blombo
1 Replies

2. AIX

File Transfer thru AIX IPSEC

Hello, I have configured IPSEC between two AIX Server v5.2 using IKE transport. When I try to transfer a files from one server to another, it is very very slow and the file transfer has been terminated after 25% completes. How to overcome this problem? Please advsie. Thanks (0 Replies)
Discussion started by: srllee
0 Replies

3. IP Networking

IPSec VPN Routing

Hello, I'm trying to setup a gateway VPN between two routers across an unsecured network between two local networks. The routers are both linux and I'm using the ipsec tools, racoon and setkey. So far hosts from either local net can successfully ping hosts on the other local net without issue. ... (0 Replies)
Discussion started by: salukibob
0 Replies

4. Red Hat

ipsec policy not working

Hi, I am trying to set a policy between 2 machines for all the ports except for 22 i.e. for tcp - basically I want to bypass ssh. But my policy doesn't seem to work. Here are the entries spdadd 1.2.3.4 4.3.2.1 any -P out prio 100 ipsec esp/transport//require ah/transport//require; spdadd... (0 Replies)
Discussion started by: ahamed101
0 Replies

5. BSD

Problem on IPSec

Hi, this is my first post...:p Hello Admin :) Can I have an ask for something with my configuration ? I have finished some kind of the tutorial to build ipsec site to site, and the "step" has finished completely. I have a simulation with a local design topology with two PC's (FreeBSD ... (0 Replies)
Discussion started by: aulia
0 Replies

6. UNIX for Advanced & Expert Users

Ipsec implementation

How can i implement Ipsec between two machines in linux_ ubuntu? any link?? suggestion?? (0 Replies)
Discussion started by: elinaz
0 Replies

7. Cybersecurity

IPSEC

hello, after configuration ipsec in ip4 I can not ping between client and server whereas I had success ping before configuration! I also generate different key for AH and ESP as i have shown below. what is my problem and what should i do to have ping and test the configuration? code: ... (0 Replies)
Discussion started by: elinaz
0 Replies

8. AIX

Allow port range using IPsec?

Hi Guys, Please could you tell me if it is possible to have a single rule/filter to allow a certain port range instead of a separate rule for each port? I'm sure it must be possible but I am unable to find the syntax. Thanks Chris (4 Replies)
Discussion started by: chrisstevens
4 Replies

9. Shell Programming and Scripting

Why result is wrong here ? whether break statement is wrong ?

Hi ! all I am just trying to check range in my datafile pls tell me why its resulting wrong admin@IEEE:~/Desktop$ cat test.txt 0 28.4 5 28.4 10 28.4 15 28.5 20 28.5 25 28.6 30 28.6 35 28.7 40 28.7 45 28.7 50 28.8 55 28.8 60 28.8 65 28.1... (2 Replies)
Discussion started by: Akshay Hegde
2 Replies

10. IP Networking

VPN IPSec Openswan

Hi all, I have installed Openswan and configured IPSec and works perfect, but for some unknown reasons it stop working. I see that the tunnels are up and established. The route to the destination are added. Everything by the book seems to be ok. But somehow when i start to ping the other side (... (4 Replies)
Discussion started by: ivancd
4 Replies
in.iked(1M)						  System Administration Commands					       in.iked(1M)

NAME
in.iked - daemon for the Internet Key Exchange (IKE) SYNOPSIS
/usr/lib/inet/in.iked [-d] [-f filename] [-p level] /usr/lib/inet/in.iked -c [-f filename] DESCRIPTION
in.iked performs automated key management for IPsec using the Internet Key Exchange (IKE) protocol. in.iked implements the following: o IKE authentication with either pre-shared keys, DSS signatures, RSA signatures, or RSA encryption. o Diffie-Hellman key derivation using either 768, 1024, or 1536-bit public key moduli. o Authentication protection with cipher choices of AES, DES, Blowfish, or 3DES, and hash choices of either HMAC-MD5 or HMAC-SHA-1. Encryption in in.iked is limited to the IKE authentication and key exchange. See ipsecesp(7P) for information regarding IPsec protection choices. in.iked is managed by the following smf(5) service: svc:/network/ipsec/ike This service is delivered disabled because the configuration file needs to be created before the service can be enabled. See ike.config(4) for the format of this file. See "Service Management Facility" for information on managing the smf(5) service. in.iked listens for incoming IKE requests from the network and for requests for outbound traffic using the PF_KEY socket. See pf_key(7P). in.iked has two support programs that are used for IKE administration and diagnosis: ikeadm(1M) and ikecert(1M). The ikeadm(1M) command can read the /etc/inet/ike/config file as a rule, then pass the configuration information to the running in.iked daemon using a doors interface. example# ikeadm read rule /etc/inet/ike/config Refreshing the ike smf(5) service provided to manage the in.iked daemon sends a SIGHUP signal to the in.iked daemon, which will (re)read /etc/inet/ike/config and reload the certificate database. The preceding two commands have the same effect, that is, to update the running IKE daemon with the latest configuration. See "Service Man- agement Facility" for more details on managing the in.iked daemon. Service Management Facility The IKE daemon (in.iked) is managed by the service management facility, smf(5). The following group of services manage the components of IPsec: svc:/network/ipsec/ipsecalgs (See ipsecalgs(1M)) svc:/network/ipsec/policy (See ipsecconf(1M)) svc:/network/ipsec/manual-key (See ipseckey(1M)) svc:/network/ipsec/ike (see ike.config(4)) The manual-key and ike services are delivered disabled because the system administrator must create configuration files for each service, as described in the respective man pages listed above. The correct administrative procedure is to create the configuration file for each service, then enable each service using svcadm(1M). The ike service has a dependency on the ipsecalgs and policy services. These services should be enabled before the ike service. Failure to do so results in the ike service entering maintenance mode. If the configuration needs to be changed, edit the configuration file then refresh the service, as follows: example# svcadm refresh ike The following properties are defined for the ike service: config/admin_privilege Defines the level that ikeadm(1M) invocations can change or observe the running in.iked. The acceptable values for this property are the same as those for the -p option. See the description of -p in OPTIONS. config/config_file Defines the configuration file to use. The default value is /etc/inet/ike/config. See ike.config(4) for the format of this file. This property has the same effect as the -f flag. See the description of -f in OPTIONS. config/debug_level Defines the amount of debug output that is written to the debug_logfile file, described below. The default value for this is op or operator. This property controls the recording of information on events such as re-reading the configuration file. Acceptable value for debug_level are listed in the ikeadm(1M) man page. The value all is equivalent to the -d flag. See the description of -d in OPTIONS. config/debug_logfile Defines where debug output should be written. The messages written here are from debug code within in.iked. Startup error messages are recorded by the smf(5) framework and recorded in a service-specific log file. Use any of the following commands to examine the logfile property: example# svcs -l ike example# svcprop ike example# svccfg -s ike listprop The values for these log file properties might be different, in which case both files should be inspected for errors. config/ignore_errors A boolean value that controls in.iked's behavior should the configuration file have syntax errors. The default value is false, which causes in.iked to enter maintenance mode if the configuration is invalid. Setting this value to true causes the IKE service to stay online, but correct operation requires the administrator to configure the running daemon with ikeadm(1M). This option is provided for compatibility with previous releases. These properties can be modified using svccfg(1M) by users who have been assigned the following authorization: solaris.smf.value.ipsec PKCS#11 token objects can be unlocked or locked by using ikeadm token login and ikeadm token logout, respectively. Availability of private keying material stored on these PKCS#11 token objects can be observed with: ikeadm dump certcache. The following authorizations allow users to log into and out of PKCS#11 token objects: solaris.network.ipsec.ike.token.login solaris.network.ipsec.ike.token.logout See auths(1), ikeadm(1M), user_attr(4), rbac(5). The service needs to be refreshed using svcadm(1M) before a new property value is effective. General, non-modifiable properties can be viewed with the svcprop(1) command. # svccfg -s ipsec/ike setprop config/config_file = /new/config_file # svcadm refresh ike Administrative actions on this service, such as enabling, disabling, refreshing, and requesting restart can be performed using svcadm(1M). A user who has been assigned the authorization shown below can perform these actions: solaris.smf.manage.ipsec The service's status can be queried using the svcs(1) command. The in.iked daemon is designed to be run under smf(5) management. While the in.iked command can be run from the command line, this is dis- couraged. If the in.iked command is to be run from the command line, the ike smf(5) service should be disabled first. See svcadm(1M). OPTIONS
The following options are supported: -c Check the syntax of a configuration file. -d Use debug mode. The process stays attached to the controlling terminal and produces large amounts of debugging output. This option is deprecated. See "Service Management Facility" for more details. -f filename Use filename instead of /etc/inet/ike/config. See ike.config(4) for the format of this file. This option is deprecated. See "Service Management Facility" for more details. -p level Specify privilege level (level). This option sets how much ikeadm(1M) invocations can change or observe about the running in.iked. Valid levels are: 0 Base level 1 Access to preshared key info 2 Access to keying material If -p is not specified, level defaults to 0. This option is deprecated. See "Service Management Facility" for more details. SECURITY
This program has sensitive private keying information in its image. Care should be taken with any core dumps or system dumps of a running in.iked daemon, as these files contain sensitive keying information. Use the coreadm(1M) command to limit any corefiles produced by in.iked. FILES
/etc/inet/ike/config Default configuration file. /etc/inet/secret/ike.privatekeys/* Private keys. A private key must have a matching public-key certificate with the same filename in /etc/inet/ike/publickeys/. /etc/inet/ike/publickeys/* Public-key certificates. The names are only important with regard to matching private key names. /etc/inet/ike/crls/* Public key certificate revocation lists. /etc/inet/secret/ike.preshared IKE pre-shared secrets for Phase I authentication. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
svcs(1), coreadm(1M), ikeadm(1M), ikecert(1M), svccfg(1M), svcadm(1M), ike.config(4), attributes(5), smf(5), ipsecesp(7P), pf_key(7P) Harkins, Dan and Carrel, Dave. RFC 2409, Internet Key Exchange (IKE). Network Working Group. November 1998. Maughan, Douglas, Schertler, M., Schneider, M., Turner, J. RFC 2408, Internet Security Association and Key Management Protocol (ISAKMP). Network Working Group. November 1998. Piper, Derrell, RFC 2407, The Internet IP Security Domain of Interpretation for ISAKMP. Network Working Group. November 1998. SunOS 5.11 27 Jan 2009 in.iked(1M)
All times are GMT -4. The time now is 07:31 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy