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

    PPTP/L2TP on interfaces

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    150 Posts 16 Posters 90.5k Views
    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.
    • X
      xbipin
      last edited by

      is the below possible

      vr1 - WAN (connects using pppoe for internet)

      is it possible to use pppoe on vr1 and then use pptp to connect to remote pptp server using the internet after the pppoe is connected?

      1 Reply Last reply Reply Quote 0
      • E
        eri--
        last edited by

        xbipin,

        if you create the pptp as an OPTx interface it will try connecting until it can. But really it cannot be supported on 2.0.
        I have plans for such things on 2.1 but will see.

        1 Reply Last reply Reply Quote 0
        • O
          Ozzik
          last edited by

          ermal, so will it be too much asking to include this in the release?

          1 Reply Last reply Reply Quote 0
          • rcfaR
            rcfa
            last edited by

            @Ozzik:

            @roi: yes.
            Here's how you do it:

            1. After installing pfSense connect by SSH or from the console choose 12) pfSense Developer Shell.
            Type: playback gitsync. After it finishes installing all the needed packages type http://gitweb.pfsense.org/pfsense/gnhb-clone.git and answer yes to all questions or just press enter. Reboot.
            After that you may also want to go to System->Firmware and add this link permanently (this section will be shown only after the first gitsync and reboot). This way it will sync after every upgrade.

            How does this interfere with regular updates, e.g. the nightly builds, etc.?
            If I follow these instructions, will I end up on a forked path, or remain on the regular releases just with some extra stuff installed, akin to installing an optional package?

            Thanks!

            1 Reply Last reply Reply Quote 0
            • O
              Ozzik
              last edited by

              Good question.

              1 Reply Last reply Reply Quote 0
              • X
                xbipin
                last edited by

                @ermal:

                xbipin,

                if you create the pptp as an OPTx interface it will try connecting until it can. But really it cannot be supported on 2.0.
                I have plans for such things on 2.1 but will see.

                after playing a lot by creating opt1 interfaces etc i figured it wouldnt be possible but like u said by creating an opt1 interface, i tried that but it never worked nor any log generated at all so i was thinking it might be broken.

                would it be possible to do this in 2.0 if ppl contributed for it as a bounty

                1 Reply Last reply Reply Quote 0
                • E
                  eri--
                  last edited by

                  I think it IS too late for 2.0.
                  But really is not hard because now you can update the firmware images and checkout a branch of your will directly from GUI.
                  Look at Updater-Settings under system->Firmware

                  So you have to wait for this since really there need to be something under the hood to better support this than its done now.

                  1 Reply Last reply Reply Quote 0
                  • L
                    Loke
                    last edited by

                    @Ozzik:

                    gnhb, ermal, sevet, Micky, Loke - you're the best!

                    It works great now. The only two questions I have left are:
                    1. Will these changes make it into 2.0 release? or will we have to manually make the changes?
                    2. It seems that from our ISP's point of view - there's no need for PPTP if you can do L2TP. But I can't speak for others. I think that in Russia they still need that option. Maybe it would be a good idea to try and find out why it keeps on disconnecting every few seconds?

                    Thanks a lot!

                    Ozzik, it's already included in the last builds. But you noticed this right? :) So no changes needed for DHCP+L2TP to work. The only thing need to be done is make possible to set hostname (not IP) as L2TP server. As for PPTP, it's not very popular now. In Russian/Ukraine the biggest provider is Beeline. They use L2TP instead of PPTP now in almost all areas they cover. Yes, it's still needed by some people, but speed and stability of PPTP is really bad (reason they use L2TP now). If i'd had possibility to connect to my provider by PPTP i'd try to see what's the problem, but i don't and i have no free hardware to set-up my own PPTP test server now. I hope left problems will be eliminated in final build, but i'm very happy because this feature already included so i don't need to merge it manually in every new build. ;D

                    This will not be excluded from the final 2.0 right? ;D

                    You need to be a master of tough voodoo to be a guru.

                    1 Reply Last reply Reply Quote 0
                    • O
                      Ozzik
                      last edited by

                      Loke, are you sure? Do you see a checkbox "Enable DHCP+L2TP or DHCP+PPTP."?
                      Besides, the ability to enter the ISP's hostname instead of the IP is a big deal.

                      1 Reply Last reply Reply Quote 0
                      • L
                        Loke
                        last edited by

                        @Ozzik:

                        Loke, are you sure? Do you see a checkbox "Enable DHCP+L2TP or DHCP+PPTP."?
                        Besides, the ability to enter the ISP's hostname instead of the IP is a big deal.

                        You don't need a checkbox "Enable DHCP+L2TP or DHCP+PPTP." to really use this feature, but if you want it, you can uncomment few lines in intefaces.php
                        You just need to set your WAN interface as L2TP and that's all. If you want to see both interfaces (L2TP and DHCP) you just need to add OPT interface and set it up like DHCP.
                        It will look like this.

                        interfaces_l2tp.png
                        interfaces_l2tp.png_thumb

                        You need to be a master of tough voodoo to be a guru.

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

                          Hi Guyz im from israel using pfsense for few years now.
                          at the last month i started using pfsense in in my work for a router to my servers.
                          i connected using HOT and bezeqint in L2TP connection i did the instruction on that thread which created OPT1 Interface (L2TP) and WAN (what i recive from the modem) internet in working and default routing is configured to OPT1  but i have 1 problem that i cannot define Inbound NAT i have an exchange server on 192.168.230.1 and my LAN port is set to 192.168.230.5  in Nat : Port forwording like the picture.
                          and cant seems to open that port from outside computer i cant get to one of the opened ports
                          in the picture you see exchange (that an alias to 192.168.230.1) and mailServer it's and alias for (25,80,443,51)

                          i hope someone can try helping me to solve it.
                          thanks

                          NAT.jpg
                          NAT.jpg_thumb

                          1 Reply Last reply Reply Quote 0
                          • O
                            Ozzik
                            last edited by

                            did u check the firewall rule?

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

                              @Ozzik:

                              did u check the firewall rule?

                              what should be on a firewall rule ?
                              the NAT automaticlly Create a Firewall rule

                              1 Reply Last reply Reply Quote 0
                              • O
                                Ozzik
                                last edited by

                                well, then I guess it's fine (it should allow from any to Exchange on any port -TCP/UDP) on OPT1 interface.
                                what's with the LAN port? Do u mean the LAN interface?

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

                                  @Ozzik:

                                  well, then I guess it's fine (it should allow from any to Exchange on any port -TCP/UDP) on OPT1 interface.
                                  what's with the LAN port? Do u mean the LAN interface?

                                  Yea i mean lan interface

                                  1 Reply Last reply Reply Quote 0
                                  • O
                                    Ozzik
                                    last edited by

                                    so how come you're accessing web gui through 230.7?

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

                                      firewall rules SS

                                      Rules.jpg
                                      Rules.jpg_thumb

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

                                        @Ozzik:

                                        so how come you're accessing web gui through 230.7?

                                        funny me :-)
                                        iwas wrong im on 230.7 :-)

                                        230.5 is connected using the same MODEM but in dial up gets a different IP

                                        because i want the exchange to use different external IP than the office computers

                                        1 Reply Last reply Reply Quote 0
                                        • O
                                          Ozzik
                                          last edited by

                                          let me get this straight, u have 230.5 and 230.7 both on the same machine, just as different interfaces? same subnet? are they bridged? i'm not sure u can do that.

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

                                            @Ozzik:

                                            let me get this straight, u have 230.5 and 230.7 both on the same machine, just as different interfaces? same subnet? are they bridged? i'm not sure u can do that.

                                            it's irrelevent to the problem but ill try to explain what i did.

                                            i have 2 machines 2 different machines.

                                            i have 2 ISP users from the ISP  (2 Public Ip's Perminent)  and 1 Cable Modem so i put a hub after the modem and both pfsense (230.5, 230.7) Dials Differently and recive each own Ip.
                                            230.5 will serve the offices while 230.7 will be for exchange use only.

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.