# IPSec setup blues

**URL:** <https://community.ipfire.org/t/ipsec-setup-blues/13382>\
**Category:** IPsec\
**Created:** [29 December 2024 17:17 UTC](https://community.ipfire.org/t/ipsec-setup-blues/13382 "2024-12-29T17:17:30Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![sonic](https://community.ipfire.org/user_avatar/community.ipfire.org/sonic/32/14314_2.png) [@sonic](https://community.ipfire.org/u/sonic)\
**Post date:** [29 December 2024 17:17 UTC](https://community.ipfire.org/t/ipsec-setup-blues/13382/1 "2024-12-29T17:17:30Z")

</div>

I cannot make IPSec to work. I started with this:  
[www.ipfire.org - Host-to-Net Connections (Roadwarrior)](https://www.ipfire.org/docs/configuration/services/ipsec/host-to-net)

I wanted to try first with the PSK, figuring it it’s easier.  
Well, I am stumped by the local ID and remote ID fields. If I leave them empty, or I put in something there, there is no connection.  
On the explanations it says: “See requirement for client”. I am trying this with Android first.

The network field I populated it with 0.0.0.0/0.  
This is the log:

```auto
12:16:04	charon:	10[NET] received packet: from 172.58.240.224[41861] to 108.26.xxx.xxx1[500] (652 bytes)
12:16:04	charon:	10[ENC] parsed IKE_SA_INIT request 0 [SA KE No N(NATD_S_IP) N(NATD_D_IP) N(HASH_ALG) N(REDIR_SUP)]
12:16:04	charon:	10[IKE] 172.58.240.224 is initiating an IKE_SA
12:16:04	charon:	10[IKE] 172.58.240.224 is initiating an IKE_SA
12:16:04	charon:	10[CFG] selected proposal: IKE:AES_GCM_16_256/PRF_HMAC_SHA2_512/ECP_384
12:16:04	charon:	10[IKE] remote host is behind NAT
12:16:04	charon:	10[IKE] DH group MODP_2048_256 unacceptable, requesting ECP_384
12:16:04	charon:	10[ENC] generating IKE_SA_INIT response 0 [N(INVAL_KE)]
12:16:04	charon:	10[NET] sending packet: from 108.26.126.121[500] to 172.58.240.224[41861] (38 bytes)
12:16:04	charon:	15[NET] received packet: from 172.58.240.224[41861] to 108.26.126.121[500] (492 bytes)
12:16:04	charon:	15[ENC] parsed IKE_SA_INIT request 0 [SA KE No N(NATD_S_IP) N(NATD_D_IP) N(HASH_ALG) N(REDIR_SUP)]
12:16:04	charon:	15[IKE] 172.58.240.224 is initiating an IKE_SA
12:16:04	charon:	15[IKE] 172.58.240.224 is initiating an IKE_SA
12:16:04	charon:	15[CFG] selected proposal: IKE:AES_GCM_16_256/PRF_HMAC_SHA2_512/ECP_384
12:16:04	charon:	15[IKE] remote host is behind NAT
12:16:04	charon:	15[IKE] sending cert request for "C=US, ST=VA, L=xxxxxxxxx, O=xxxxx, CN=xxx CA, E=xxxx@xxxx.com"
12:16:04	charon:	15[ENC] generating IKE_SA_INIT response 0 [SA KE No N(NATD_S_IP) N(NATD_D_IP) CERTREQ N(HASH_ALG) N(CHDLESS_SUP) N(MULT_AUTH)]
12:16:04	charon:	15[NET] sending packet: from 108.26.xxx.xxx[500] to 172.58.240.224[41861] (321 bytes)

```

---

<div class="post-metadata">

**Author:** ![bonnietwin](https://community.ipfire.org/user_avatar/community.ipfire.org/bonnietwin/32/12350_2.png) [@bonnietwin](https://community.ipfire.org/u/bonnietwin)\
**Post date:** [29 December 2024 18:05 UTC](https://community.ipfire.org/t/ipsec-setup-blues/13382/2 "2024-12-29T18:05:23Z")

</div>

I think you have not included all the log information.

The log you showed has no error messages but it also has no message indication a successful connection.

There is a message half way down which indicates that the selected DH group was not acceptable for the client and ECP\_384 was requested.

Then the connection flow re-started, this time with ECP\_384 for the DH group and this was accepted.

The last log line is

```auto
12:16:04	charon:	15[NET] sending packet: from 108.26.xxx.xxx[500] to 172.58.240.224[41861] (321 bytes)

```

but there must either be a reply from the client or the server indicating that it timed out but it just stops with that last line.

---

<div class="post-metadata">

**Author:** ![sonic](https://community.ipfire.org/user_avatar/community.ipfire.org/sonic/32/14314_2.png) [@sonic](https://community.ipfire.org/u/sonic)\
**Post date:** [29 December 2024 18:39 UTC](https://community.ipfire.org/t/ipsec-setup-blues/13382/3 "2024-12-29T18:39:23Z")

</div>

It timed out.  
On my Android device it just said “Disconnected”.

> | 12:18:38 | charon: | 08[NET] sending packet: from 108.26.xxx.xxx[500] to 172.58.240.224[38483] (321 bytes) |
> | --- | --- | --- |
> | 12:19:08 | charon: | 11[JOB] deleting half open IKE\_SA with 172.58.240.224 after timeout |
> | 13:36:09 | charon: | 05[NET] received packet: from 172.58.240.88[28187] to 108.26.xxx.xxx[500] (652 bytes) |
> | 13:36:09 | charon: | 05[ENC] parsed IKE\_SA\_INIT request 0 [SA KE No N(NATD\_S\_IP) N(NATD\_D\_IP) N(HASH\_ALG) N(REDIR\_SUP)] |
> | 13:36:09 | charon: | 05[IKE] 172.58.240.88 is initiating an IKE\_SA |
> | 13:36:09 | charon: | 05[IKE] 172.58.240.88 is initiating an IKE\_SA |
> | 13:36:09 | charon: | 05[CFG] selected proposal: IKE:AES\_GCM\_16\_256/PRF\_HMAC\_SHA2\_512/ECP\_384 |
> | 13:36:09 | charon: | 05[IKE] remote host is behind NAT |
> | 13:36:09 | charon: | 05[IKE] DH group MODP\_2048\_256 unacceptable, requesting ECP\_384 |
> | 13:36:09 | charon: | 05[ENC] generating IKE\_SA\_INIT response 0 [N(INVAL\_KE)] |
> | 13:36:09 | charon: | 05[NET] sending packet: from 108.26.xxx.xxx[500] to 172.58.240.88[28187] (38 bytes) |
> | 13:36:09 | charon: | 08[NET] received packet: from 172.58.240.88[28187] to 108.26.xxx.xxx[500] (492 bytes) |
> | 13:36:09 | charon: | 08[ENC] parsed IKE\_SA\_INIT request 0 [SA KE No N(NATD\_S\_IP) N(NATD\_D\_IP) N(HASH\_ALG) N(REDIR\_SUP)] |
> | 13:36:09 | charon: | 08[IKE] 172.58.240.88 is initiating an IKE\_SA |
> | 13:36:09 | charon: | 08[IKE] 172.58.240.88 is initiating an IKE\_SA |
> | 13:36:09 | charon: | 08[CFG] selected proposal: IKE:AES\_GCM\_16\_256/PRF\_HMAC\_SHA2\_512/ECP\_384 |
> | 13:36:09 | charon: | 08[IKE] remote host is behind NAT |
> | 13:36:09 | charon: | 08[IKE] sending cert request for C=US, ST=xx, L=xxx, O=xxx, CN=xxx CA, [E=xxx@xxx.com](mailto:E=xxx@xxx.com) |
> | 13:36:09 | charon: | 08[ENC] generating IKE\_SA\_INIT response 0 [SA KE No N(NATD\_S\_IP) N(NATD\_D\_IP) CERTREQ N(HASH\_ALG) N(CHDLESS\_SUP) N(MULT\_AUTH)] |
> | 13:36:09 | charon: | 08[NET] sending packet: from 108.26.xxx.xxx[500] to 172.58.240.88[28187] (321 bytes) |
> | 13:36:39 | charon: | 06[JOB] deleting half open IKE\_SA with 172.58.240.88 after timeout |

 ![image](https://community.ipfire.org/uploads/default/original/2X/c/c1b5a316c2d670343f04393f9949ba7a062c3494.png)

---

<div class="post-metadata">

**Author:** ![luxskywalker](https://community.ipfire.org/user_avatar/community.ipfire.org/luxskywalker/32/16720_2.png) [@luxskywalker](https://community.ipfire.org/u/luxskywalker)\
**Post date:** [29 December 2024 21:18 UTC](https://community.ipfire.org/t/ipsec-setup-blues/13382/4 "2024-12-29T21:18:52Z")

</div>

Use OpenVPN for your Android Client not IPSec

I am using this for years without Problems

---

<div class="post-metadata">

**Author:** ![sonic](https://community.ipfire.org/user_avatar/community.ipfire.org/sonic/32/14314_2.png) [@sonic](https://community.ipfire.org/u/sonic)\
**Post date:** [30 December 2024 00:18 UTC](https://community.ipfire.org/t/ipsec-setup-blues/13382/5 "2024-12-30T00:18:38Z")

</div>

I am using that, and it works. I was just curious about IPSec.

---

<div class="post-metadata">

**Author:** ![sonic](https://community.ipfire.org/user_avatar/community.ipfire.org/sonic/32/14314_2.png) [@sonic](https://community.ipfire.org/u/sonic)\
**Post date:** [30 December 2024 09:43 UTC](https://community.ipfire.org/t/ipsec-setup-blues/13382/6 "2024-12-30T09:43:31Z")

</div>

> remote host is behind NAT

I am confused by this statement. What NAT? I thought the IPSec resides on the RED network?

---

<div class="post-metadata">

**Author:** ![luxskywalker](https://community.ipfire.org/user_avatar/community.ipfire.org/luxskywalker/32/16720_2.png) [@luxskywalker](https://community.ipfire.org/u/luxskywalker)\
**Post date:** [30 December 2024 10:35 UTC](https://community.ipfire.org/t/ipsec-setup-blues/13382/7 "2024-12-30T10:35:48Z")

</div>

then stick with it.

if you are trying to connect from your IPFire IPSec to your Handy within mobile Network it would not Work. You don’t get a publicly accessible IP on the mobile Network.

---

<div class="post-metadata">

**Author:** ![sonic](https://community.ipfire.org/user_avatar/community.ipfire.org/sonic/32/14314_2.png) [@sonic](https://community.ipfire.org/u/sonic)\
**Post date:** [30 December 2024 10:53 UTC](https://community.ipfire.org/t/ipsec-setup-blues/13382/8 "2024-12-30T10:53:09Z")

</div>

I was using my phone, with wifi off. You can see up different IP’s.

Why would I NOT get a publicly accessible IP from cellular? That’s absurd.

---

<div class="post-metadata">

**Author:** ![luxskywalker](https://community.ipfire.org/user_avatar/community.ipfire.org/luxskywalker/32/16720_2.png) [@luxskywalker](https://community.ipfire.org/u/luxskywalker)\
**Post date:** [30 December 2024 11:14 UTC](https://community.ipfire.org/t/ipsec-setup-blues/13382/9 "2024-12-30T11:14:46Z")

</div>

please read my Post carefully

from IPFire to mobile Network is not possible

from Mobile Network to IPFire it works

most Provider does not use public accessible IPs and routing

> **[Carrier-grade NAT](https://en.wikipedia.org/wiki/Carrier-grade_NAT)**
>
> Carrier-grade NAT (CGN or CGNAT), also known as large-scale NAT (LSN), is a type of network address translation (NAT) used by ISPs in IPv4 network design. With CGNAT, end sites, in particular residential networks, are configured with private network addresses that are translated to public IPv4 addresses by middlebox network address translator devices embedded in the network operator's network, permitting the sharing of small pools of public addresses among many end users. This essentially repeats...

Of course you are online with your phone and can surf  
but you can’t access your phone “from outside”.

---

<div class="post-metadata">

**Author:** ![sonic](https://community.ipfire.org/user_avatar/community.ipfire.org/sonic/32/14314_2.png) [@sonic](https://community.ipfire.org/u/sonic)\
**Post date:** [30 December 2024 11:41 UTC](https://community.ipfire.org/t/ipsec-setup-blues/13382/10 "2024-12-30T11:41:12Z")

</div>

> [@luxskywalker](#):
>
> from IPFire to mobile Network is not possible

I didn’t want THAT.  
I just want to setup a IPSec VPN server on my ipfire device.  
Like I do with OpenVPN.

---

<div class="post-metadata">

**Author:** ![luxskywalker](https://community.ipfire.org/user_avatar/community.ipfire.org/luxskywalker/32/16720_2.png) [@luxskywalker](https://community.ipfire.org/u/luxskywalker)\
**Post date:** [30 December 2024 12:08 UTC](https://community.ipfire.org/t/ipsec-setup-blues/13382/11 "2024-12-30T12:08:24Z")

</div>

I didn’t say that at all, it just shows the problems that can arise

IPSec is completely different in terms of connection setup

You have OpenVPN running so use it…

---

<div class="post-metadata">

**Author:** ![jon](https://community.ipfire.org/user_avatar/community.ipfire.org/jon/32/15363_2.png) [@jon](https://community.ipfire.org/u/jon)\
**Post date:** [30 December 2024 17:33 UTC](https://community.ipfire.org/t/ipsec-setup-blues/13382/12 "2024-12-30T17:33:31Z")

</div>

> [@sonic](#):
>
> ![image](https://community.ipfire.org/uploads/default/original/2X/c/c1b5a316c2d670343f04393f9949ba7a062c3494.png)

This is missing a few fields.

 ![ipsec_connection.png](https://community.ipfire.org/uploads/default/original/2X/a/aed6d97755605a2f319504f8378404ae306edb3f.png)

This might help:

[https://www.ipfire.org/docs/configuration/services/ipsec/host-to-net#creating-a-new-connection](https://www.ipfire.org/docs/configuration/services/ipsec/host-to-net#creating-a-new-connection)

I use IPsec with a Mac or an iPad. (I don’t have an Android device)

---

<div class="post-metadata">

**Author:** ![sonic](https://community.ipfire.org/user_avatar/community.ipfire.org/sonic/32/14314_2.png) [@sonic](https://community.ipfire.org/u/sonic)\
**Post date:** [31 December 2024 11:32 UTC](https://community.ipfire.org/t/ipsec-setup-blues/13382/13 "2024-12-31T11:32:35Z")

</div>

What is that @example.ddn.org and @myLaptop ?

---

<div class="post-metadata">

**Author:** ![bonnietwin](https://community.ipfire.org/user_avatar/community.ipfire.org/bonnietwin/32/12350_2.png) [@bonnietwin](https://community.ipfire.org/u/bonnietwin)\
**Post date:** [31 December 2024 12:46 UTC](https://community.ipfire.org/t/ipsec-setup-blues/13382/14 "2024-12-31T12:46:38Z")

</div>

Those are identifications for your server and for your remote client.

I believe that some clients such as MAC OS expect to have the ID defined. You can use any name for the ID, it just needs to start with an @

I have set up the IPSec RW with PSK for my Linux Laptop, using Network Manager with the Strongswan IPSec plugin.

With that client, I was able to leave the Local and Remote ID’s blank on the server and also on the client. The Network Manager client just uses the name or IP of the server that you specify and the username or hostname.

The IPSec VPN connection worked fine.

I also then added an @ID for the local and remote on the server configuration. If you do that then you must enter those ID values into your client if you want the connection to be made successfully. I added them into my Network Manager client and the IPSec PSK connection was again successfully made.

You need to identify if the client you are using accepts blank ID’s and fills them with default values or if you need to specify them on the server.  
The simplest would be to always specify them.

One thing I have realised while checking some of this is that the bug fix I did for the IPSec PSK in CU190 has a slight bug in it. If you go into the edit page for the PSK connection then if you press the Save button, it should only do a Base 64 Encoding of the password that was previously entered if it is defined as not yet being encoded via a variable.  
That appears not to be working as if you go into the edit page and change nothing but press the Save button, in all cases it converts the PSK via Base 64 Encoding. This means that each time you press the Save button the PSK is changed into another PSK by being Base 64 Encoded again.

So the workaround for this in the short term is that if you go into the edit page and want to press the Save button then before doing so, copy your original PSK back into the PSK entry box and then press the Save button. This way you get the correct Base 64 Encoded PSK saved in the ipsec.config file.

I will raise a bug report for myself to have a look at what is not working right under which situations and fix it.

---

<div class="post-metadata">

**Author:** ![sonic](https://community.ipfire.org/user_avatar/community.ipfire.org/sonic/32/14314_2.png) [@sonic](https://community.ipfire.org/u/sonic)\
**Post date:** [31 December 2024 13:31 UTC](https://community.ipfire.org/t/ipsec-setup-blues/13382/15 "2024-12-31T13:31:19Z")

</div>

I get in the logs:

> remote host is behind NAT

I am confused why.

---

<div class="post-metadata">

**Author:** ![sonic](https://community.ipfire.org/user_avatar/community.ipfire.org/sonic/32/14314_2.png) [@sonic](https://community.ipfire.org/u/sonic)\
**Post date:** [31 December 2024 14:06 UTC](https://community.ipfire.org/t/ipsec-setup-blues/13382/16 "2024-12-31T14:06:10Z")

</div>

I am trying this on my laptop, connected to my cell hotspot.  
Different issues…

> | 09:03:45 | charon: | 13[IKE] 172.58.244.211 is initiating an IKE\_SA |
> | --- | --- | --- |
> | 09:03:45 | charon: | 13[IKE] 172.58.244.211 is initiating an IKE\_SA |
> | 09:03:45 | charon: | 13[CFG] received proposals: IKE:3DES\_CBC/HMAC\_SHA1\_96/PRF\_HMAC\_SHA1/MODP\_1024, IKE:3DES\_CBC/HMAC\_SHA2\_256\_128/PRF\_HMAC\_SHA2\_256/MODP\_1024, IKE:3DES\_CBC/HMAC\_SHA2\_384\_192/PRF\_HMAC\_SHA2\_384/MODP\_1024, IKE:AES\_CBC\_128/HMAC\_SHA1\_96/PRF\_HMAC\_SHA1/MODP\_1024, IKE:AES\_CBC\_128/HMAC\_SHA2\_256\_128/PRF\_HMAC\_SHA2\_256/MODP\_1024, IKE:AES\_CBC\_128/HMAC\_SHA2\_384\_192/PRF\_HMAC\_SHA2\_384/MODP\_1024, IKE:AES\_CBC\_192/HMAC\_SHA1\_96/PRF\_HMAC\_SHA1/MODP\_1024, IKE:AES\_CBC\_192/HMAC\_SHA2\_256\_128/PRF\_HMAC\_SHA2\_256/MODP\_1024, IKE:AES\_CBC\_192/HMAC\_SHA2\_384\_192/PRF\_HMAC\_SHA2\_384/MODP\_1024, IKE:AES\_CBC\_256/HMAC\_SHA1\_96/PRF\_HMAC\_SHA1/MODP\_1024, IKE:AES\_CBC\_256/HMAC\_SHA2\_256\_128/PRF\_HMAC\_SHA2\_256/MODP\_1024, IKE:AES\_CBC\_256/HMAC\_SHA2\_384\_192/PRF\_HMAC\_SHA2\_384/MODP\_1024, IKE:AES\_GCM\_16\_128/PRF\_HMAC\_SHA1/MODP\_1024, IKE:AES\_GCM\_16\_128/PRF\_HMAC\_SHA2\_256/MODP\_1024, IKE:AES\_GCM\_16\_128/PRF\_HMAC\_SHA2\_384/MODP\_1024, IKE:AES\_GCM\_16\_256/PRF\_HMAC\_SHA1/MODP\_1024, IKE:AES\_GCM\_16\_256/PRF\_HMAC\_SHA2\_256/MODP\_1024, IKE:AES\_GCM\_16\_256/PRF\_ |
> | 09:03:45 | charon: | 13[CFG] configured proposals: IKE:CHACHA20\_POLY1305/PRF\_HMAC\_SHA2\_512/CURVE\_448, IKE:CHACHA20\_POLY1305/PRF\_HMAC\_SHA2\_512/CURVE\_25519, IKE:CHACHA20\_POLY1305/PRF\_HMAC\_SHA2\_512/ECP\_521, IKE:CHACHA20\_POLY1305/PRF\_HMAC\_SHA2\_512/ECP\_512\_BP, IKE:CHACHA20\_POLY1305/PRF\_HMAC\_SHA2\_512/ECP\_384, IKE:CHACHA20\_POLY1305/PRF\_HMAC\_SHA2\_512/MODP\_4096, IKE:CHACHA20\_POLY1305/PRF\_HMAC\_SHA2\_512/MODP\_3072, IKE:CHACHA20\_POLY1305/PRF\_HMAC\_SHA2\_384/CURVE\_448, IKE:CHACHA20\_POLY1305/PRF\_HMAC\_SHA2\_384/CURVE\_25519, IKE:CHACHA20\_POLY1305/PRF\_HMAC\_SHA2\_384/ECP\_521, IKE:CHACHA20\_POLY1305/PRF\_HMAC\_SHA2\_384/ECP\_512\_BP, IKE:CHACHA20\_POLY1305/PRF\_HMAC\_SHA2\_384/ECP\_384, IKE:CHACHA20\_POLY1305/PRF\_HMAC\_SHA2\_384/MODP\_4096, IKE:CHACHA20\_POLY1305/PRF\_HMAC\_SHA2\_384/MODP\_3072, IKE:CHACHA20\_POLY1305/PRF\_HMAC\_SHA2\_256/CURVE\_448, IKE:CHACHA20\_POLY1305/PRF\_HMAC\_SHA2\_256/CURVE\_25519, IKE:CHACHA20\_POLY1305/PRF\_HMAC\_SHA2\_256/ECP\_521, IKE:CHACHA20\_POLY1305/PRF\_HMAC\_SHA2\_256/ECP\_512\_BP, IKE:CHACHA20\_POLY1305/PRF\_HMAC\_SHA2\_256/ECP\_384 |
> | 09:03:45 | charon: | 13[IKE] local host is behind NAT, sending keep alives |
> | 09:03:45 | charon: | 13[IKE] remote host is behind NAT |
> | 09:03:45 | charon: | 13[IKE] received proposals unacceptable |
> | 09:03:45 | charon: | 13[ENC] generating IKE\_SA\_INIT response 0 [N(NO\_PROP)] |

---

<div class="post-metadata">

**Author:** ![tphz](https://community.ipfire.org/user_avatar/community.ipfire.org/tphz/32/16551_2.png) [@tphz](https://community.ipfire.org/u/tphz)\
**Post date:** [31 December 2024 14:06 UTC](https://community.ipfire.org/t/ipsec-setup-blues/13382/17 "2024-12-31T14:06:34Z")

</div>

> [@sonic](#):
>
> I am confused why.

You have it explained in the following post

> [@IPSec setup blues](https://community.ipfire.org/t/ipsec-setup-blues/13382/9):
>
> please read my Post carefully from IPFire to mobile Network is not possible from Mobile Network to IPFire it works most Provider does not use public accessible IPs and routing Of course you are online with your phone and can surf but you can’t access your phone “from outside”.

---

<div class="post-metadata">

**Author:** ![sonic](https://community.ipfire.org/user_avatar/community.ipfire.org/sonic/32/14314_2.png) [@sonic](https://community.ipfire.org/u/sonic)\
**Post date:** [31 December 2024 14:08 UTC](https://community.ipfire.org/t/ipsec-setup-blues/13382/18 "2024-12-31T14:08:10Z")

</div>

I don’t understand this. I don’t try to access my phone from “outside”, but to access my ipfire VPN from my phone.  
The server ipfire is on landline fiber.  
Also, the OpenVPN works on my phone data, so why the IPSec VPN won’t work?

---

<div class="post-metadata">

**Author:** ![bonnietwin](https://community.ipfire.org/user_avatar/community.ipfire.org/bonnietwin/32/12350_2.png) [@bonnietwin](https://community.ipfire.org/u/bonnietwin)\
**Post date:** [31 December 2024 15:26 UTC](https://community.ipfire.org/t/ipsec-setup-blues/13382/19 "2024-12-31T15:26:53Z")

</div>

In Core Update 170 (Sept 2022) MODP-2048 was removed from the IPFire IPSec code as that Diffie Hellman group (2048 bits) was at that time considered to be too weak as it was too short.

[https://www.ipfire.org/blog/ipfire-2-27-core-update-170-released](https://www.ipfire.org/blog/ipfire-2-27-core-update-170-released)

In your log from the setup with your laptop you can see that your laptop IPSec client was proposing to use MODP-1024 (1024 bits) with all its ciphers and that is even shorter, and therefore more vulnerable, than the modp-2048, which is also no longer accepted.

Therefore there was no overlap between the proposed groups and ciphers from your laptop and the ones that are available on IPFire.

Is your laptop running with Windows. I have seen other people on this forum having problems with older versions of windows as their DH groups and ciphers have not been updated from the older vulnerable versions.

If you are using Windows, what version are you using?

If it is not Windows, what OS is on your laptop and at what version or update status?

> [@sonic](#):
>
> the OpenVPN works on my phone data, so why the IPSec VPN won’t work?

I suspect because the IPSec client on your Android phone is using older, vulnerable ciphers etc.

Maybe try installing the StrongSwan app on your Android phone. StrongSwan is the IPSec package running in IPFire and that StrongSwan app is kept up to date.

---

<div class="post-metadata">

**Author:** ![jon](https://community.ipfire.org/user_avatar/community.ipfire.org/jon/32/15363_2.png) [@jon](https://community.ipfire.org/u/jon)\
**Post date:** [31 December 2024 15:38 UTC](https://community.ipfire.org/t/ipsec-setup-blues/13382/20 "2024-12-31T15:38:32Z")

</div>

It looks like lots of ciphers are enabled.

Can you post a screenshot of your **Advanced** page?

Each client device has supported ciphers. From the Wiki these are the ones supported by Apple:

 ![Screenshot 2024-12-31 at 9.29.40 AM](https://community.ipfire.org/uploads/default/original/2X/a/a062818726fb494ab6733a84677b4c1a12f1f830.png)

this above is a screenshot from this IPFire Wiki:  
[https://www.ipfire.org/docs/configuration/services/ipsec/host-to-net/apple](https://www.ipfire.org/docs/configuration/services/ipsec/host-to-net/apple)

* * *

And for Windows (from the Wiki):

 ![Screenshot 2024-12-31 at 9.31.36 AM](https://community.ipfire.org/uploads/default/original/2X/7/7b811300a525ac78c9388a031ae832390cc2c95b.png)

this above is a screenshot from this IPFire Wiki:  
[https://www.ipfire.org/docs/configuration/services/ipsec/host-to-net/windows](https://www.ipfire.org/docs/configuration/services/ipsec/host-to-net/windows)

* * *

I do not know the ciphers from an Android device.

We need to match the device ciphers to the **Advanced** WebGUI to make sure things are correct and work.

This is from the Wiki page (and was my original setup for my iPad)

 ![ipsec_advanced_settings](https://community.ipfire.org/uploads/default/original/2X/2/2e059d2b2f1c1a01e91310e24e184f3f2d660321.png)

[Next page](https://community.ipfire.org/t/ipsec-setup-blues/13382.md?page=2)
