Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
iSu10
Participant
Jump to solution

80.40 vpn for linux client setup

Hi all

 

We are now using 77.30 and all working fine. We are in middle of a new project and need to upgrade Security Gateways and have stumbled on a bump which have not yet figured out. We have linux clients (some of out tech team) which use Linux as their workstation and use SNX client (build 800010003) to connect via VPN and all works great.

 

But, for 80.40 we have yet to figure out how these linux clients will connect via VPN. SNX not working. This is a huge bump, cause other Firewalls provide clients for linux machines and we need a solution on Checkpoint (our prefered Gateway) before any decision is made on purchasing new hardware.

 

Any thoughts, help on how to achieve this??

 

Sincerely.

0 Kudos
1 Solution

Accepted Solutions
PhoneBoy
Admin
Admin

SNX should still work from Linux to R80.40.
Any debugging or log messages you can provide that might provide a clue?

If you’re looking for a different option, upgrade to R81 and use StrongSWAN, which is a supported configuration.

View solution in original post

6 Replies
PhoneBoy
Admin
Admin

SNX should still work from Linux to R80.40.
Any debugging or log messages you can provide that might provide a clue?

If you’re looking for a different option, upgrade to R81 and use StrongSWAN, which is a supported configuration.

iSu10
Participant

Here the last lines with the debug flag (-g) while running snx.. It stays here without completing connections nor receiving IP:

[ 46678 -141123520]@clinfois[16 Jan 17:53:06] ssl_tunnel::send_slim_protocol: working link is 098a1fd0
[ 46678 -141123520]@clinfois[16 Jan 17:53:06] ssl_link:: send_packet: Entering for 255 bytes
[ 46678 -141123520]@clinfois[16 Jan 17:53:06] fwasync_connbuf_realloc: reallocating 0 from 0 to 1287
[ 46678 -141123520]@clinfois[16 Jan 17:53:06] fwasync_mux_out: 7: sent 0 of 263 bytes == 263 bytes to send
[ 46678 -141123520]@clinfois[16 Jan 17:53:06] ckpSSL_do_write: write 263 bytes
[ 46678 -141123520]@clinfois[16 Jan 17:53:06] fwasync_mux_out: 7: managed to send 263 of 263 bytes
[ 46678 -141123520]@clinfois[16 Jan 17:53:06] fwasync_mux_out: 7: call: 80fa8f0 with 3
[ 46678 -141123520]@clinfois[16 Jan 17:53:06] ssl_link_fwasync_client_handler: after sending packet, vola 2
[ 46678 -141123520]@clinfois[16 Jan 17:53:06] fwasync_mux_out: 7: rc=1, next: 80fa8f0 with 3, req: 8r, 0w
[ 46678 -141123520]@clinfois[16 Jan 17:53:06] fwasync_mux_in: 7: rc=1, next: 80fa8f0 with 3, req: 8r, 0w
0 Kudos
the_rock
Legend
Legend

Is that output from connecting to R80.40?

 

Andyu

0 Kudos
iSu10
Participant

Yes.
These are the last lines of the snx.elg debug file created while connecting to the new R80.40.

0 Kudos
the_rock
Legend
Legend

Message me offline, we can do remote session and check.

0 Kudos
iSu10
Participant

SNX build 800010003 worked!

Thanks

0 Kudos

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    Tue 23 Apr 2024 @ 11:00 AM (EDT)

    East US: What's New in R82

    Thu 25 Apr 2024 @ 11:00 AM (SGT)

    APAC: CPX 2024 Recap

    Tue 30 Apr 2024 @ 03:00 PM (CDT)

    EMEA: CPX 2024 Recap

    Thu 02 May 2024 @ 11:00 AM (SGT)

    APAC: What's new in R82

    Tue 23 Apr 2024 @ 11:00 AM (EDT)

    East US: What's New in R82

    Thu 25 Apr 2024 @ 11:00 AM (SGT)

    APAC: CPX 2024 Recap

    Tue 30 Apr 2024 @ 03:00 PM (CDT)

    EMEA: CPX 2024 Recap

    Thu 02 May 2024 @ 11:00 AM (SGT)

    APAC: What's new in R82
    CheckMates Events