Skip to main content
msuluhan
msuluhan
New Member
December 1, 2023
Question

FortiNet VPN freezes Ubuntu 22.04 LTS

  • December 1, 2023
  • 1 reply
  • 2611 views

Hello

I am using Ubuntu LTS 22.04.3 as notebook operating system and "forticlient/now 7.0.7.0246 amd64" for FortiNet based VPN connections.


After connections establishment with VPN gateway, my network connections both FortiNet VPN gateway and public network/internet freezes about 5-10 seconds every couple of minutes. Lots of my customers using FortiNet for VPN connectivity and I am facing with this problem with every customer.

While network connection freezes I can not ping, connect anywhere.

In other situations I mean if there is no FortiNet VPN connections there is no problem.


I also tested with Windows VM guest@VirtualBox on same computer, there is not any problem like above.

So it's obviously clear that this is Fortinet Linux client and/or Ubuntu operating system problem but could not solve the problem yet. I am using Ubuntu LTS 22.04 since initial release date and I have same problem


Is there any recommendation and/or idea about the problem

 

Thanks

msuluhan

1 reply

ezhupa
Staff
ezhupa
Staff
December 1, 2023

Hello msuluhan, 

Your situation seems very similar to another Support Forum post:
https://community.fortinet.com/t5/Support-Forum/VPN-connection-not-working-after-update-to-Ubuntu-22-04/m-p/213824
Solution would be as below:

https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/comments/32 

Hope this resolves your issue!

    msuluhan
    msuluhanAuthor
    New Member
    December 11, 2023

    Hello ezhupa

    Thanks for your reply

    But it did not help me


    My problem is bold chars in following lines. What did I do to generate this issue
    --> Connected anyone of the FortiVPN GW (As I wrote before I have lots of customers with FortiVPN GW)
    --> After connection established, ping www.google.com


    This problem occurs when my FortiClient is active. When problem starts any site/connection/ssh/rdp freezes 7-9 seconds and then started to working. After every 100-110 pings, problem occurs, distinctly. So it is not comfortable to hard with this problem

     


    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5686 ttl=120 time=39.0 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5687 ttl=120 time=38.5 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5688 ttl=120 time=39.6 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5689 ttl=120 time=39.1 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5690 ttl=120 time=38.6 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5691 ttl=120 time=38.4 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5692 ttl=120 time=39.2 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5693 ttl=120 time=38.5 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5694 ttl=120 time=38.3 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5695 ttl=120 time=40.0 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5696 ttl=120 time=39.4 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5697 ttl=120 time=39.2 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5698 ttl=120 time=38.0 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5699 ttl=120 time=218 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5700 ttl=120 time=39.0 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5701 ttl=120 time=38.6 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5702 ttl=120 time=41.2 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5703 ttl=120 time=38.9 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5704 ttl=120 time=38.3 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5705 ttl=120 time=38.9 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5706 ttl=120 time=39.5 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5707 ttl=120 time=40.2 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5708 ttl=120 time=10155 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5709 ttl=120 time=9145 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5710 ttl=120 time=8123 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5711 ttl=120 time=7099 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5712 ttl=120 time=6075 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5713 ttl=120 time=5048 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5714 ttl=120 time=4029 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5715 ttl=120 time=3016 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5716 ttl=120 time=1990 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5717 ttl=120 time=967 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5718 ttl=120 time=40.0 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5719 ttl=120 time=39.1 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5720 ttl=120 time=39.5 ms
    64 bytes from sof02s46-in-f4.1e100.net (142.250.187.164): icmp_seq=5721 ttl=120 time=39.0 ms

     

    When I check SSLVPN log I see following lines (there is no error or warning about the session)

    20231211 12:18:01.029 [sslvpn:DEBG] dns:149 Restart DNS service successfully.
    20231211 12:18:11.037 [sslvpn:DEBG] dns:164 Run command 'flush DNS cache' failed.
    20231211 12:20:00.799 [sslvpn:DEBG] dns:1017 Reset DNS
    20231211 12:20:01.036 [sslvpn:DEBG] dns:149 Restart DNS service successfully.
    20231211 12:20:11.044 [sslvpn:DEBG] dns:159 Flush DNS cache successfully.
    20231211 12:22:00.797 [sslvpn:DEBG] dns:1017 Reset DNS
    20231211 12:22:01.049 [sslvpn:DEBG] dns:149 Restart DNS service successfully.
    20231211 12:22:11.057 [sslvpn:DEBG] dns:164 Run command 'flush DNS cache' failed.
    20231211 12:24:00.797 [sslvpn:DEBG] dns:1017 Reset DNS
    20231211 12:24:00.000 [sslvpn:DEBG] dns:149 Restart DNS service successfully.
    20231211 12:24:11.008 [sslvpn:DEBG] dns:159 Flush DNS cache successfully.

     

     

    Thanks

    msuluhan

    Terms & ConditionsAccessibility statement