Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Vpn goes down…

    Scheduled Pinned Locked Moved
    IPsec
    6
    26
    9.1k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      sullrich
      last edited by

      Just make sure each size matches.  Find the most commonly used lifetime then change the rest to match.

      Make sure phase 1 and phase 2 both match respectively.    IE: each machines phase 1 should match, and phase 2 should match.

      Not sure of the best settings but I generally use 1500 for both phase 1 and 2.  This might not be the best value but so far it works great for me.

      1 Reply Last reply Reply Quote 0
      • C
        covex
        last edited by

        wow this is small. i've never went lower 3600 before. i was going to go with 86400 for phase 1 and 28800 phase 2

        1 Reply Last reply Reply Quote 0
        • H
          hoba
          last edited by

          3600 for both phases works for me without issues.

          1 Reply Last reply Reply Quote 0
          • C
            covex
            last edited by

            i've just noticed two warning messages in the log
            2007-03-17 17:41:16 System3.Info 192.168.1.252 Mar 17 17:41:09 racoon: INFO: @(#)This product linked OpenSSL 0.9.7e-p1 25 Oct 2004 (http://www.openssl.org/)
            2007-03-17 17:41:16 System3.Info 192.168.1.252 Mar 17 17:41:09 racoon: INFO: fe80::1%lo0[500] used as isakmp port (fd=12)
            2007-03-17 17:41:16 System3.Info 192.168.1.252 Mar 17 17:41:09 racoon: INFO: ::1[500] used as isakmp port (fd=13)
            2007-03-17 17:41:16 System3.Info 192.168.1.252 Mar 17 17:41:09 racoon: INFO: 127.0.0.1[500] used as isakmp port (fd=14)
            2007-03-17 17:41:16 System3.Info 192.168.1.252 Mar 17 17:41:09 racoon: WARNING: setsockopt(UDP_ENCAP_ESPINUDP_NON_IKE): Invalid argument
            2007-03-17 17:41:16 System3.Info 192.168.1.252 Mar 17 17:41:09 racoon: INFO: fe80::20e:cff:fec2:c2b7%em1[500] used as isakmp port (fd=15)
            2007-03-17 17:41:16 System3.Info 192.168.1.252 Mar 17 17:41:09 racoon: INFO: xxx.xxx.xxx.xxx[500] used as isakmp port (fd=16)
            2007-03-17 17:41:16 System3.Info 192.168.1.252 Mar 17 17:41:09 racoon: WARNING: setsockopt(UDP_ENCAP_ESPINUDP_NON_IKE): Invalid argument
            2007-03-17 17:41:16 System3.Info 192.168.1.252 Mar 17 17:41:09 racoon: INFO: fe80::20e:cff:fec2:c2c2%em0[500] used as isakmp port (fd=17)
            2007-03-17 17:41:16 System3.Info 192.168.1.252 Mar 17 17:41:09 racoon: INFO: 192.168.1.252[500] used as isakmp port (fd=18)
            2007-03-17 17:41:16 System3.Info 192.168.1.252 Mar 17 17:41:09 racoon: WARNING: setsockopt(UDP_ENCAP_ESPINUDP_NON_IKE): Invalid argument
            2007-03-17 17:41:16 Daemon.Notice 192.168.1.252 Mar 17 17:41:09 pftpx[458]: listening on 127.0.0.1 port 8021
            2

            1 Reply Last reply Reply Quote 0
            • C
              covex
              last edited by

              i've changed all settings to 28800 for phase 1 and 3600 for phase two and it is still going down every day. is there a difference for using mobile-users settings instead of ipsec tunnels for the hardware endpoints?
              also ftp traffic is going one way only. remotes can get on the ftp site at my office but i can't ftp to them

              1 Reply Last reply Reply Quote 0
              • Z
                z00te
                last edited by

                same problem here… approx 40 tunnel with other pfsense and smoothwall...
                please let me know if you found a solution...

                tnx
                Z

                1 Reply Last reply Reply Quote 0
                • H
                  heiko
                  last edited by

                  Hello,
                  i agree with HOBA. Set the lifetime on both phases to 3600. For me it works great!!
                  Greetings Heiko

                  1 Reply Last reply Reply Quote 0
                  • C
                    covex
                    last edited by

                    the only thing i've found so far is this http://securitytracker.com/alerts/2005/Mar/1013433.html. but it looks like it was fixed in 2005

                    1 Reply Last reply Reply Quote 0
                    • C
                      covex
                      last edited by

                      @heiko:

                      Hello,
                      i agree with HOBA. Set the lifetime on both phases to 3600. For me it works great!!
                      Greetings Heiko

                      hey man, how many tunnels you have? mobile users or static endpoints?

                      1 Reply Last reply Reply Quote 0
                      • H
                        heiko
                        last edited by

                        Whe you have static endpoints between Smothwall an pfsense, please set both phases to a lifetime of 3600. We tested it and it works with  pfsense 1.01 (not releng snapshot). Please test it in Phase 2 with 28800.

                        This settings works for pfsense and smothwall (ipcop)

                        This settings works for me:

                        Phase 1 lifetime: 3600 sec.
                        Encrypt. Alg. 3DES
                        HasH. MD5
                        DH Key Group: 2
                        Pre Shared Key: xxxx

                        Phase 2:
                        Protocol: ESP
                        Encrypt. Alg. only 3DES
                        Hash: only MD5
                        PFS Key Group : 2
                        Lifetime: 28800 or 3600 , you must try

                        On Smothwall you must set compression to OFF.

                        Please try

                        Greetings
                        heiko

                        Greetings
                        Heiko

                        1 Reply Last reply Reply Quote 0
                        • E
                          EmL
                          last edited by

                          Hi … i think it should work with both lifetimes (eg. 3600/3600 or 86400/28800). What is suggested in official RFCs you can read here http://www.faqs.org/rfcs/rfc4308.html (search for lifetime).

                          Do you have a crypto card in your box? I have one and have also problems (especially after ip changes dynamic-static VPN) ... without my crypto card the tunnel keeps alive over an ip change ... maybe this can cause your problems?

                          1 Reply Last reply Reply Quote 0
                          • C
                            covex
                            last edited by

                            i don't have crypto card in my box and my problem is that vpn service is going down on the pfsense server completely, not just keep alive function.
                            i have all static ip's and remotes are equiped with either linksys befvp41 or netgear fvs318 routers.
                            i'll try to set everything to 3600 today, but i think the only thing will change is that my server will be going down more often.

                            1 Reply Last reply Reply Quote 0
                            • H
                              hoba
                              last edited by

                              Are you using main or aggressive mode? I think I once helped out a user in the IRC channel with a vpn to a netgear router and the problem was either main mode or aggressive (don't know the details anymore) but if you are currently using the one maybe try the other option.

                              1 Reply Last reply Reply Quote 0
                              • C
                                covex
                                last edited by

                                everything is set to main mode. i'll try 3600 tonight if this wont work i'll move from mobile users setup to ipsec tunnel for each connection, if this wont work either… i guess i'm going to be fired  ;D :(

                                1 Reply Last reply Reply Quote 0
                                • C
                                  covex
                                  last edited by

                                  …still why is ftp traffic going one way only? everything is by default under "rules".

                                  1 Reply Last reply Reply Quote 0
                                  • C
                                    covex
                                    last edited by

                                    ok… looks like "vpn goes down" problem was fixed. the server has been up for more then 24 hours now. but i still can't ftp to remote sites over vpn. pcanywhere (and file transfer) works fine, i can ssh and scp to remote pc's and they can ftp to my office, but i cant ftp to them. does anybody know how to fix this? tnx

                                    p.s. this _If you want to connect to a FTP server you need to add this workaround to your LAN tab.

                                    Proto Source Port Destination Port Gateway TCP LAN net * 127.0.0.1 1 - 65535 *

                                    Now the packets are forwarded correctly and you can connect to an FTP server._ is not helping.

                                    ok… ftp problem was fixed too  8) as they say "if nothing works read the manual"  ;D ::)

                                    1 Reply Last reply Reply Quote 0
                                    • First post
                                      Last post