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

    PPTP/L2TP on interfaces

    2.0-RC Snapshot Feedback and Problems - RETIRED
    16
    150
    85.9k
    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.
    • L
      Loke
      last edited by

      God damn! It's already done in last build (with little differences comparing to my changes) with same issue i got ;D No auto-connect after reboot.
      Problem definitely related to local IP. If you don't fill this field connection is not going up after reboot.

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

      1 Reply Last reply Reply Quote 0
      • G
        gnhb
        last edited by

        @Loke => There is already a L2TP configuration option in Interfaces(assign)=>PPPs=>Add/Edit PPP page. You don't need to re-invent. :)

        Okay guys, I committed some fixes to the GUI code today. There is now a "Connect/Disconnect" button in Status=>Interfaces Page for L2TP links.

        Also, you can configure L2TP client from the WAN (or OPTx) pages in the Interfaces menu now (interfaces.php).

        I have (I think) working DHCP+L2TP/PPTP code in my repository. (I think only because I don't have an L2TP remote endpoint.)

        I followed mickey's lead and forced the L2TP/PPTP link down if the DCHP lease is Released (or any time the DHCP interface is brought down by pfSense.) Is this desired behavior? I assume so.

        PM me with your email address and I'll send you new /etc/inc/interfaces.inc and /etc/rc.newwanip files you can put on your box for testing.

        If you guys test it out and it's solid I can ask the lead devs if it's okay to add it into 2.0.

        Please watch out for what happens when the DHCP lease is renewed. I hope it doesn't kill and reload the L2TP/PPTP link, but please check for that.

        If you're savvy with git-sync in pfSense developer shell, the you can git-sync to my repository here:
        http://gitweb.pfsense.org/pfsense/gnhb-clone.git

        Follow instructions here for git-sync but use this URL above:
        http://iserv.nl/files/pfsense/ipv6/

        Let me know what happens

        GB

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

          The problem we have now is L2TP not connecting on reboot if "local IP" field left empty. Also in /etc/inc/interfaces.inc strings set {$type} self {$localips[$pid]} and set {$type} disable windowing are unnecessary for L2TP and local IP is really not necessary at all.
          So i suggest this way:

          
		if ($type == "pptp") {
			$mpdconf .= << <eod<br>set pptp peer {$gateways[$pid]}
	set pptp disable windowing

EOD;
		}

		if ($type == "l2tp") {
			$mpdconf .= << <eod<br>set l2tp peer {$gateways[$pid]}

EOD;
		}</eod<br></eod<br>

          And suggest to remove "Local IP" from configuration page like i did in my version. The only problem is at boot time something apparently needs this single string in config.xml:

          
<localip>0.0.0.0</localip>

          And yes, it can be anything there, even 0.0.0.0

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

          1 Reply Last reply Reply Quote 0
          • G
            gnhb
            last edited by

            To test the code in my repo, set up your DHCP interface (for example on OPT1) and select the "Enable DHCP+" checkbox.

            Set up your L2TP interface using the Interfaces(assign) menue => PPPs tab => Add (+) button.
            Select OPT1 for your Link Interface on that page. You must select OPT1 if you set up OPT1 as the DCHP+ interface.

            Leave Local IP field empty.
            Add your ISP's host name in Remote IP field.
            Add other info you need and Save.

            Then go assign that L2TP link to your WAN interface and Save.

            Go to Status => Interfaces and check link status.
            Go to Diagnostics => Routes and check that the static route to the DHCP gateway is added and also deleted when the L2TP link comes up and then is down again.

            GB

            @Loke => Some users may need the Local IP field so it will stay. mpd5 just ignores the windowing command for L2TP. We might take it out in the future.
            RE: reboot issue. I have no knowledge of your configuration or your ISP setup. Are you trying to use DCHP+L2TP or just plain L2TP? I can't say anything about your reboot issue. Did you already post your config? I haven't seen it.

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

              Loke, than just put 0.0.0.0 at local ip and be done with it.

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

                @ermal:

                Loke, than just put 0.0.0.0 at local ip and be done with it.

                Actually i did this :).
                gnhb, no matter need you local ip or not it must be field or there will be connect to L2TP server on startup. And i've made the same changes you did with some small diff in interfaces.php and it works the same way.

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

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

                  Loke,

                  if it does not startup at boot you better provide logs.

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

                    @ermal:

                    Loke,

                    if it does not startup at boot you better provide logs.

                    The funny thing is there is no errors related to this in logs. Everything seems to be fine, just it's not even trying to connect when there is no localip in config.xml
                    And i didn't found any dependence on this string except set {$type} self {$localips[$pid]} in interfaces.inc. But this problem is not related to this for sure.

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

                    1 Reply Last reply Reply Quote 0
                    • R
                      roi
                      last edited by

                      I am planing to setup a new machine this weekend just for testing this feature.
                      If there is any thing you'd like me to do-to-it-in-it

                      Version 2.0-BETA4 (i386)
                      AMD Athlon™ XP 2000+

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

                        I just pushed the fix to allow empty localip.

                        1 Reply Last reply Reply Quote 0
                        • G
                          gnhb
                          last edited by

                          I just merged Ermal's changes into my repository and added some minor changes to bringing L2TP/PPTP interfaces up and down manually from Status=>Interfaces page.

                          Is anyone testing ???
                          Post feedback!

                          Thanks,
                          GB

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

                            Hi gnhb,
                            I sent you a pm asking for those files you mentioned.

                            thanks.

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

                              ok, testing it now. this is what happens:
                              installed new pfsense 23.3.11 snapshot, cloned gnhb's git and followed his instructions.

                              regular dhcp on WAN: works as usual (gets the cable network pool IP 172.x.x.x)
                              checked the dhcp+pptp or dhcp+l2tp on WAN interface, applied.
                              went to PPPs tab, selected the pptp, the physical WAN interface, typed user/pass, and since I couldn't remember the hostname of the ISP's pptp server - went with the IP. Left the local IP blank. Saved and went back to interface assignment and replaced the physical interface on WAN with the now created pptp. Saved.

                              It gave me an error at the upper side of the page, but couldn't read it as it was overlayed by the menu(but it did contain the interfaces file in it).
                              On interfaces status page the WAN connection was down, but had a "connect" button. After pressing that some sort of connection appeared although it was all zeros. On refresh it went back down.

                              Below are the logs.
                              In addition to that I decided to relive this experiment, so I changed the WAN back to the regular DHCP, but couldn't get a regular IP, so I rebooted the pfsense. To my surprise it came on asking to define the interfaces on the console(like it was a new setup), but after defining only the WAN it came up remembering the LAN address. Kind of weird.

                              Anyway, doing this all over again gave me the same results.
                              Changing PPTP to L2TP did the same.

                              Any ideas?

                              Log:
                              Mar 24 11:53:03 php: /interfaces.php: Creating rrd update script
                              Mar 24 11:53:03 apinger: No usable targets found, exiting
                              Mar 24 11:53:03 apinger: Starting Alarm Pinger, apinger(14804)
                              Mar 24 11:53:03 check_reload_status: reloading filter
                              Mar 24 11:53:02 apinger: Exiting on signal 15.
                              Mar 24 11:53:00 dnsmasq[12671]: read /etc/hosts - 2 addresses
                              Mar 24 11:53:00 check_reload_status: updating dyndns wan
                              Mar 24 11:53:00 dnsmasq[12671]: using nameserver 192.168.101.101#53
                              Mar 24 11:53:00 dnsmasq[12671]: using nameserver 192.168.101.102#53
                              Mar 24 11:53:00 dnsmasq[12671]: reading /etc/resolv.conf
                              Mar 24 11:53:00 dnsmasq[12671]: compile time options: IPv6 GNU-getopt no-DBus I18N DHCP TFTP
                              Mar 24 11:53:00 dnsmasq[12671]: started, version 2.55 cachesize 10000
                              Mar 24 11:52:59 dnsmasq[37582]: exiting on receipt of SIGTERM
                              Mar 24 11:52:59 kernel: ng0: changing name to 'pptp0'
                              Mar 24 11:52:57 php: /interfaces.php: wan: pptp link warning. Can't get gateway ip address for fxp0. No host route added for .
                              Mar 24 11:52:57 php: /interfaces.php: The command 'route -q delete -host 212.143.205.253' returned exit code '1', the output was 'route: writing to routing socket: No such process'
                              Mar 24 11:52:57 php: /interfaces.php: wan: pptp link configuration warning. No ip address configured on fxp0. Using 0.0.0.0 ip!
                              Mar 24 11:52:54 check_reload_status: syncing firewall
                              Mar 24 11:43:42 apinger: /usr/local/bin/rrdtool respawning too fast, waiting 300s.
                              Mar 24 11:42:44 kernel: ng0: changing name to 'pptp0'
                              Mar 24 11:42:42 php: /status_interfaces.php: wan: pptp link warning. Can't get gateway ip address for fxp0. No host route added for .
                              Mar 24 11:42:42 php: /status_interfaces.php: The command 'route -q delete -host 212.143.205.253' returned exit code '1', the output was 'route: writing to routing socket: No such process'
                              Mar 24 11:42:42 php: /status_interfaces.php: wan: pptp link configuration warning. No ip address configured on fxp0. Using 0.0.0.0 ip!
                              Mar 24 11:42:42 apinger: Error while feeding rrdtool: Broken pipe
                              Mar 24 11:42:18 php: /interfaces_assign.php: Creating rrd update script
                              Mar 24 11:42:18 check_reload_status: syncing firewall
                              Mar 24 11:42:18 dnsmasq[37582]: read /etc/hosts - 2 addresses
                              Mar 24 11:42:18 check_reload_status: updating dyndns wan
                              Mar 24 11:42:18 dnsmasq[37582]: using nameserver 192.168.101.101#53
                              Mar 24 11:42:18 dnsmasq[37582]: using nameserver 192.168.101.102#53
                              Mar 24 11:42:18 dnsmasq[37582]: reading /etc/resolv.conf
                              Mar 24 11:42:18 dnsmasq[37582]: compile time options: IPv6 GNU-getopt no-DBus I18N DHCP TFTP
                              Mar 24 11:42:18 dnsmasq[37582]: started, version 2.55 cachesize 10000
                              Mar 24 11:42:17 dnsmasq[33305]: exiting on receipt of SIGTERM
                              Mar 24 11:42:15 kernel: ng0: changing name to 'pptp0'
                              Mar 24 11:42:14 php: /interfaces_assign.php: wan: pptp link warning. Can't get gateway ip address for fxp0. No host route added for .
                              Mar 24 11:42:14 php: /interfaces_assign.php: The command 'route -q delete -host 212.143.205.253' returned exit code '1', the output was 'route: writing to routing socket: No such process'
                              Mar 24 11:42:14 php: /interfaces_assign.php: interfaces: bringing down interfaces dependent on: wan
                              Mar 24 11:42:13 dhclient[14456]: exiting.
                              Mar 24 11:42:13 dhclient[14456]: exiting.
                              Mar 24 11:42:13 dhclient[14456]: connection closed
                              Mar 24 11:42:13 dhclient[14456]: connection closed
                              Mar 24 11:42:05 check_reload_status: syncing firewall
                              Mar 24 11:42:03 check_reload_status: reloading filter
                              Mar 24 11:41:53 apinger: ALARM: WAN(172.24.64.1) *** down ***
                              Mar 24 11:41:42 php: /interfaces.php: Creating rrd update script
                              Mar 24 11:41:42 apinger: Starting Alarm Pinger, apinger(34719)
                              Mar 24 11:41:42 check_reload_status: reloading filter
                              Mar 24 11:41:41 apinger: Exiting on signal 15.
                              Mar 24 11:41:39 check_reload_status: updating dyndns wan
                              Mar 24 11:41:39 dnsmasq[33305]: read /etc/hosts - 2 addresses
                              Mar 24 11:41:39 dnsmasq[33305]: using nameserver 192.168.101.101#53
                              Mar 24 11:41:39 dnsmasq[33305]: using nameserver 192.168.101.102#53
                              Mar 24 11:41:39 dnsmasq[33305]: reading /etc/resolv.conf
                              Mar 24 11:41:39 dnsmasq[33305]: compile time options: IPv6 GNU-getopt no-DBus I18N DHCP TFTP
                              Mar 24 11:41:39 dnsmasq[33305]: started, version 2.55 cachesize 10000
                              Mar 24 11:41:38 dnsmasq[43468]: exiting on receipt of SIGTERM
                              Mar 24 11:41:38 dnsmasq[43468]: using nameserver 192.168.101.101#53
                              Mar 24 11:41:38 dnsmasq[43468]: using nameserver 192.168.101.102#53
                              Mar 24 11:41:38 dnsmasq[43468]: reading /etc/resolv.conf
                              Mar 24 11:41:37 php: : interfaces: reloading interfaces dependent on: wan
                              Mar 24 11:41:37 apinger: Starting Alarm Pinger, apinger(25236)
                              Mar 24 11:41:37 check_reload_status: reloading filter
                              Mar 24 11:41:36 apinger: Exiting on signal 15.
                              Mar 24 11:41:36 php: : ROUTING: change default route to 172.24.64.1
                              Mar 24 11:41:36 php: /interfaces.php: ROUTING: change default route to 172.24.64.1
                              Mar 24 11:41:36 php: : rc.newwanip: on (IP address: 172.24.64.217) (interface: wan) (real interface: fxp0).
                              Mar 24 11:41:35 php: : rc.newwanip: Informational is starting fxp0.
                              Mar 24 11:41:35 dhclient[14419]: bound to 172.24.64.217 – renewal in 1752 seconds.
                              Mar 24 11:41:35 check_reload_status: rc.newwanip starting fxp0
                              Mar 24 11:41:35 dhclient: Creating resolv.conf
                              Mar 24 11:41:35 dhclient: /sbin/route add default 172.24.64.1
                              Mar 24 11:41:35 dhclient: Adding new routes to interface: fxp0
                              Mar 24 11:41:35 dhclient: New Routers (fxp0): 172.24.64.1
                              Mar 24 11:41:35 dhclient: New Broadcast Address (fxp0): 255.255.255.255
                              Mar 24 11:41:35 dhclient: New Subnet Mask (fxp0): 255.255.224.0
                              Mar 24 11:41:35 dhclient: New IP Address (fxp0): 172.24.64.217
                              Mar 24 11:41:35 dhclient: ifconfig fxp0 inet 172.24.64.217 netmask 255.255.224.0 broadcast 255.255.255.255
                              Mar 24 11:41:35 dhclient: Starting add_new_address()
                              Mar 24 11:41:35 dhclient: REBOOT
                              Mar 24 11:41:35 dhclient[14419]: DHCPACK from 10.175.192.1
                              Mar 24 11:41:35 dhclient[14419]: DHCPREQUEST on fxp0 to 255.255.255.255 port 67
                              Mar 24 11:41:35 dhclient: PREINIT
                              Mar 24 11:41:35 php: /interfaces.php: interfaces: bringing down interfaces dependent on: wan
                              Mar 24 11:41:34 php: /interfaces.php: The command '/bin/kill 12928' returned exit code '1', the output was 'kill: 12928: No such process'
                              Mar 24 11:41:34 dhclient[7500]: exiting.
                              Mar 24 11:41:34 dhclient[7500]: exiting.
                              Mar 24 11:41:34 dhclient[7500]: connection closed
                              Mar 24 11:41:34 dhclient[7500]: connection closed
                              Mar 24 11:41:34 dhclient: FAIL
                              Mar 24 11:41:24 check_reload_status: syncing firewall
                              Mar 24 11:41:02 apinger: Error while feeding rrdtool: Broken pipe
                              Mar 24 11:40:22 check_reload_status: reloading filter
                              Mar 24 11:40:12 check_reload_status: reloading filter
                              Mar 24 11:40:12 apinger: ALARM: WAN(172.24.64.1) *** down ***
                              Mar 24 11:40:11 sshlockout[15621]: sshlockout/webConfigurator v3.0 starting up
                              Mar 24 11:40:11 login: login on ttyv0 as root
                              Mar 24 11:40:10 php: : IPSEC: One or more IPsec tunnel endpoints has changed its IP. Refreshing.
                              Mar 24 11:40:10 php: : Resyncing configuration for all packages.
                              Mar 24 11:40:09 php: : Creating rrd update script
                              Mar 24 11:40:07 php: : Resyncing OpenVPN instances for interface WAN.
                              Mar 24 11:40:04 dnsmasq[43468]: read /etc/hosts - 2 addresses
                              Mar 24 11:40:04 dnsmasq[43468]: using nameserver 192.168.101.101#53
                              Mar 24 11:40:04 dnsmasq[43468]: using nameserver 192.168.101.102#53
                              Mar 24 11:40:04 check_reload_status: updating all dyndns
                              Mar 24 11:40:04 dnsmasq[43468]: reading /etc/resolv.conf
                              Mar 24 11:40:04 dnsmasq[43468]: compile time options: IPv6 GNU-getopt no-DBus I18N DHCP TFTP
                              Mar 24 11:40:04 dnsmasq[43468]: started, version 2.55 cachesize 10000
                              Mar 24 11:40:04 php: : ROUTING: change default route to 172.24.64.1
                              Mar 24 11:40:02 apinger: Starting Alarm Pinger, apinger(26066)
                              Mar 24 11:40:02 check_reload_status: reloading filter
                              Mar 24 11:40:01 php: : ROUTING: change default route to 172.24.64.1
                              Mar 24 11:40:01 php: : rc.newwanip: on (IP address: 172.24.64.217) (interface: wan) (real interface: fxp0).
                              Mar 24 11:40:01 php: : rc.newwanip: Informational is starting fxp0.
                              Mar 24 11:40:00 kernel: pflog0: promiscuous mode enabled

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

                                And this is what happens if I type in the ISP's pptp server hostname:

                                Mar 24 12:06:18 php: /status_interfaces.php: wan: pptp link configuration failed. No ip address found for cable.netvision.net.il.
                                Mar 24 12:06:18 php: /status_interfaces.php: wan: pptp link configuration warning. No ip address configured on fxp0. Using 0.0.0.0 ip!
                                Mar 24 12:06:05 check_reload_status: syncing firewall

                                1 Reply Last reply Reply Quote 0
                                • G
                                  gnhb
                                  last edited by

                                  @Ozzik => Yes I can see what is happening. You must select "the OPTx" interface and not the physical interface as your "Link Interface" when you set up the PPTP connection.

                                  GB

                                  1 Reply Last reply Reply Quote 0
                                  • G
                                    gnhb
                                    last edited by

                                    @Ozzik:

                                    And this is what happens if I type in the ISP's pptp server hostname:

                                    Mar 24 12:06:18 php: /status_interfaces.php: wan: pptp link configuration failed. No ip address found for cable.netvision.net.il.
                                    Mar 24 12:06:18 php: /status_interfaces.php: wan: pptp link configuration warning. No ip address configured on fxp0. Using 0.0.0.0 ip!
                                    Mar 24 12:06:05 check_reload_status: syncing firewall

                                    If you want the DNS lookup to work, you have to have an IP address from the ISP already. I can see in your logs that DHCP starts and then fails/quits/gets killed. I think you have a mis-configuration in your setup. Read my instructions again and see it what you did really matches what I described.

                                    GB

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

                                      ok, I did what you suggested.
                                      This brings me to the "fatal trap 12" every time I press connect.
                                      the messages in the log look the same (regarding the routes), but the error I get on the console is this:

                                      stopped at ng_ether_atach+0xdf mol %eax,0x4(%edx)

                                      plus, when I reboot it from there it always comes up fixing some file system errors.

                                      1 Reply Last reply Reply Quote 0
                                      • G
                                        gnhb
                                        last edited by

                                        @Ozzik: Post your config please.

                                        Can you figure out why your DCHP client is bailing out?
                                        Mar 24 11:42:13    dhclient[14456]: exiting.
                                        Mar 24 11:42:13    dhclient[14456]: connection closed

                                        GB

                                        1 Reply Last reply Reply Quote 0
                                        • G
                                          gnhb
                                          last edited by

                                          Ozzik,
                                          See this thread about DHCP client issues: http://forum.pfsense.org/index.php/topic,34791.0.html

                                          Once that is worked out you might not have any problem with the PPTP/L2TP link.

                                          GB

                                          1 Reply Last reply Reply Quote 0
                                          • R
                                            roi
                                            last edited by

                                            After two days this is what I came up with:

                                            Intel P4 2.6Ghz
                                            Asus P4P800-ES Mainboard
                                            3Gb DDR 400 Ram
                                            Nvidia FX5200
                                            Nic's:
                                            1. On board: Marvell Yukon 8001
                                            2. 3Com Etherlink XL 3c905b
                                            3. Compaq NC3120 (Intel 82557 chipset)
                                            4. Realtek 8139D
                                            5. Davicom 9102
                                            Running : pfSense-2.0-RC1-i386-20110325-1028

                                            At the moment the Marvel is set to be WAN and is connected to a ADSL router feeding from another ISP.
                                            One of the Nic's will be connected directly to the Cable modem.
                                            Third will be LAN to a control desktop.

                                            Let the games begine…

                                            CIMG0001.JPG
                                            CIMG0001.JPG_thumb
                                            CIMG0002.JPG
                                            CIMG0002.JPG_thumb

                                            Version 2.0-BETA4 (i386)
                                            AMD Athlon™ XP 2000+

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