Thread Info
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SSL VPN with IPv4 but message TCPv6_SERVER: Connection timed out (code=110) and Broken pipe (code=32)

LHerzog

We have a user that is complaining repeatedly about disconnecting SSL VPN (TCP) with Connect Client 2.2.90

SFOS is 19.5.2

I assume his ISP uses IPv4 sharing / DS-Lite.

Nevertheless, when he connects, he is connecting with an IPv4 address and that is written in the sslvpn.log.

XG is not communicating with IPv6 to the outside world.

User is using MFA.

Authentication is successful after the second attempt and the routes are pushed to the client.

Then in the logs IPv6 Server messages appear and finally the connections is no longer working and timing out.

The user assured, he can access all internet sites normally or watch videos online when his SSL VPN disconnects.

full XG log:

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
2023-07-31 05:56:37Z [26682] username@domain.de/82.207.250.180:20622 Is IPv4 :1
2023-07-31 05:56:37Z [26682] username@domain.de/82.207.250.180:20622 SENT CONTROL [username@domain.de]: 'PUSH_REPLY,route-gateway 10.242.254.1,sndbuf 0,rcvbuf 0,ping 45,ping-restart 180,route 172.1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx,dhcp-option DOMAIN domain.de,ifconfig 10.242.254.10 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
2023-07-31 05:56:37Z [26682] username@domain.de/82.207.250.180:20622 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
2023-07-31 05:56:37Z [26682] username@domain.de/82.207.250.180:20622 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
2023-07-31 09:36:35Z [26682] TCP connection established with [AF_INET6]::ffff:82.207.250.180:20837
2023-07-31 09:36:35Z [26682] 82.207.250.180:20837 TLS: Initial packet from [AF_INET6]::ffff:82.207.250.180:20837, sid=9d129e4b 8a60abb8
2023-07-31 09:36:35Z [26682] 82.207.250.180:20837 VERIFY OK: depth=0, hidden-CA-Details, CN=username@domain.de_170BF773AB0, emailAddress=mailaddress@domain.de
2023-07-31 09:36:35Z [26682] 82.207.250.180:20837 VERIFY OK: depth=1, hidden-CA-Details, CN=firewallname.domain.de, emailAddress=mailaddress@domain.de
2023-07-31 09:36:35Z [26682] 82.207.250.180:20837 VERIFY OK: depth=1, hidden-CA-Details, CN=firewallname.domain.de, emailAddress=mailaddress@domain.de
2023-07-31 09:36:35Z [26682] 82.207.250.180:20837 VERIFY OK: depth=0, hidden-CA-Details, CN=username@domain.de_170BF773AB0, emailAddress=mailaddress@domain.de
2023-07-31 09:36:35Z [26682] 82.207.250.180:20837 peer info: IV_VER=2.5.6
2023-07-31 09:36:35Z [26682] 82.207.250.180:20837 peer info: IV_PLAT=win
2023-07-31 09:36:35Z [26682] 82.207.250.180:20837 peer info: IV_PROTO=6
2023-07-31 09:36:35Z [26682] 82.207.250.180:20837 peer info: IV_NCP=2
2023-07-31 09:36:35Z [26682] 82.207.250.180:20837 peer info: IV_CIPHERS=AES-256-GCM:AES-128-GCM
2023-07-31 09:36:35Z [26682] 82.207.250.180:20837 peer info: IV_LZ4=1
2023-07-31 09:36:35Z [26682] 82.207.250.180:20837 peer info: IV_LZ4v2=1
2023-07-31 09:36:35Z [26682] 82.207.250.180:20837 peer info: IV_LZO=1
2023-07-31 09:36:35Z [26682] 82.207.250.180:20837 peer info: IV_COMP_STUB=1
2023-07-31 09:36:35Z [26682] 82.207.250.180:20837 peer info: IV_COMP_STUBv2=1
2023-07-31 09:36:35Z [26682] 82.207.250.180:20837 peer info: IV_TCPNL=1
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Client log:

Any idea what could cause the gateway reset here?



This thread was automatically locked due to age.