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

      ermal, thank you! now it works without local ip.

      roi, how all this related to the topic???

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

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

        @gnhb:

        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

        Don't get it… Isn't Connnect/Disconnect button was there before? And this is a rhetoric question. ;D

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

        1 Reply Last reply Reply Quote 0
        • M
          Micky
          last edited by

          @Ozzik

          I didn't find the opt1 interface in your config, as far as i remember you should assign the physical interface to optx (and set it to DHCP), then create a ppp interface (l2tp) and use the opt1 as its link and only then assign the ppp to wan.
          So there should be an additional OPTx interface.

          @Loke

          No, there was no connect/disconnect button at the interface status page for l2tp.

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

            @Micky:
            OK, I'll try that. Did you get it working with the new snapshots?

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

              ok, time for an update.
              so, of course, Mickey was right and I should've read the instructions more carefully.
              What happens now is that PPTP connects for less than a minute (I can access the web and everything's fine), but then it disconnects. Tried it several times.

              L2TP wouldn't connect at all.
              Another weird thing is that after several connects/disconnects I have to actually reset the modem if I want to renew the dhcp - otherwise it wouldn't give me an IP.

              Here is the system log: (real IP changed to 62.x.x.x)
              Mar 29 11:53:52 php: : Could not find gateway for interface(wan).
              Mar 29 11:53:52 check_reload_status: reloading filter
              Mar 29 11:53:42 apinger: ALARM: WAN(212.25.68.21) *** down ***
              Mar 29 11:53:32 check_reload_status: Rewriting resolv.conf
              Mar 29 11:52:56 check_reload_status: reloading filter
              Mar 29 11:52:46 apinger: ALARM: OPT1(172.29.32.1) *** down ***
              Mar 29 11:52:41 php: : Resyncing OpenVPN instances for interface WAN.
              Mar 29 11:52:35 apinger: Starting Alarm Pinger, apinger(2883)
              Mar 29 11:52:35 check_reload_status: reloading filter
              Mar 29 11:52:34 apinger: Exiting on signal 15.
              Mar 29 11:52:34 php: : ROUTING: change default route to 212.25.68.21
              Mar 29 11:52:34 php: : rc.newwanip: on (IP address: 62.x.x.x) (interface: wan) (real interface: pptp0).
              Mar 29 11:52:34 php: : rc.newwanip: Informational is starting pptp0.
              Mar 29 11:52:34 check_reload_status: rc.newwanip starting pptp0
              Mar 29 11:52:32 check_reload_status: Rewriting resolv.conf
              Mar 29 11:52:32 kernel: ng0: changing name to 'pptp0'
              Mar 29 11:52:29 check_reload_status: Rewriting resolv.conf
              Mar 29 11:52:29 check_reload_status: configuring interface wan
              Mar 29 11:52:29 php: : rc.newwanip: Failed to update wan IP, restarting…
              Mar 29 11:52:29 php: : rc.newwanip: on (IP address: ) (interface: wan) (real interface: pptp0).
              Mar 29 11:52:29 php: : rc.newwanip: Informational is starting pptp0.
              Mar 29 11:52:29 check_reload_status: rc.newwanip starting pptp0
              Mar 29 11:52:28 php: /status_interfaces.php: wan: pptp link configuration failed. No ip address found for gch.bezeqint.net.
              Mar 29 11:52:28 check_reload_status: Rewriting resolv.conf
              Mar 29 11:52:27 kernel: ng0: changing name to 'pptp0'
              Mar 29 11:52:27 php: : The command 'route -q delete -host 212.25.127.2' returned exit code '1', the output was 'route: writing to routing socket: No such process'
              Mar 29 11:52:27 check_reload_status: configuring interface wan
              Mar 29 11:52:27 apinger: Starting Alarm Pinger, apinger(19883)
              Mar 29 11:52:27 php: : interfaces: reloading interfaces dependent on: opt1
              Mar 29 11:52:26 check_reload_status: reloading filter
              Mar 29 11:52:25 apinger: Exiting on signal 15.
              Mar 29 11:52:25 php: : rc.newwanip: on (IP address: 172.29.32.147) (interface: opt1) (real interface: fxp0).
              Mar 29 11:52:25 php: : rc.newwanip: Informational is starting fxp0.
              Mar 29 11:52:25 dhclient[3751]: bound to 172.29.32.147 – renewal in 846084102 seconds.
              Mar 29 11:52:25 check_reload_status: rc.newwanip starting fxp0
              Mar 29 11:52:25 dhclient: Creating resolv.conf
              Mar 29 11:52:25 dhclient: Adding new routes to interface: fxp0
              Mar 29 11:52:25 dhclient: New Routers (fxp0): 172.29.32.1
              Mar 29 11:52:25 dhclient: New Broadcast Address (fxp0): 255.255.255.255
              Mar 29 11:52:25 dhclient: New Subnet Mask (fxp0): 255.255.255.0
              Mar 29 11:52:25 dhclient: New IP Address (fxp0): 172.29.32.147
              Mar 29 11:52:25 dhclient: ifconfig fxp0 inet 172.29.32.147 netmask 255.255.255.0 broadcast 255.255.255.255
              Mar 29 11:52:25 dhclient: Starting add_new_address()
              Mar 29 11:52:25 dhclient: REBOOT
              Mar 29 11:52:25 dhclient[3751]: DHCPACK from 10.18.124.1
              Mar 29 11:52:25 dhclient[3751]: DHCPREQUEST on fxp0 to 255.255.255.255 port 67
              Mar 29 11:52:25 dhclient: PREINIT
              Mar 29 11:52:25 php: /status_interfaces.php: interfaces: bringing down interfaces dependent on: opt1
              Mar 29 11:52:24 php: : wan: pptp link configuration failed. No ip address found for gch.bezeqint.net.
              Mar 29 11:52:24 php: : Resyncing OpenVPN instances for interface OPT1.
              Mar 29 11:52:22 php: /status_interfaces.php: interfaces: bringing down interfaces dependent on: opt1
              Mar 29 11:52:21 dhclient[46225]: exiting.
              Mar 29 11:52:21 dhclient[46225]: exiting.
              Mar 29 11:52:21 dhclient[46225]: connection closed
              Mar 29 11:52:21 dhclient[46225]: connection closed
              Mar 29 11:52:18 check_reload_status: configuring interface wan
              Mar 29 11:52:18 php: : interfaces: reloading interfaces dependent on: opt1
              Mar 29 11:52:18 apinger: Starting Alarm Pinger, apinger(44328)
              Mar 29 11:52:18 check_reload_status: reloading filter
              Mar 29 11:52:17 apinger: Exiting on signal 15.
              Mar 29 11:52:17 php: : rc.newwanip: on (IP address: 172.29.32.147) (interface: opt1) (real interface: fxp0).
              Mar 29 11:52:17 php: : rc.newwanip: Informational is starting fxp0.
              Mar 29 11:52:17 dhclient[50560]: bound to 172.29.32.147 – renewal in 846084111 seconds.
              Mar 29 11:52:17 check_reload_status: rc.newwanip starting fxp0
              Mar 29 11:52:17 dhclient: Creating resolv.conf
              Mar 29 11:52:16 dhclient: Adding new routes to interface: fxp0
              Mar 29 11:52:16 dhclient: New Routers (fxp0): 172.29.32.1
              Mar 29 11:52:16 dhclient: New Broadcast Address (fxp0): 255.255.255.255
              Mar 29 11:52:16 dhclient: New Subnet Mask (fxp0): 255.255.255.0
              Mar 29 11:52:16 dhclient: New IP Address (fxp0): 172.29.32.147
              Mar 29 11:52:16 dhclient: ifconfig fxp0 inet 172.29.32.147 netmask 255.255.255.0 broadcast 255.255.255.255
              Mar 29 11:52:16 dhclient: Starting add_new_address()
              Mar 29 11:52:16 dhclient: Deleting old routes
              Mar 29 11:52:16 dhclient: BOUND
              Mar 29 11:52:16 dhclient[50560]: DHCPACK from 10.18.124.1
              Mar 29 11:52:16 dhclient[50560]: DHCPREQUEST on fxp0 to 255.255.255.255 port 67
              Mar 29 11:52:16 dhclient: ARPCHECK
              Mar 29 11:52:14 login: login on ttyv0 as root
              Mar 29 11:52:14 dhclient: ARPSEND
              Mar 29 11:52:14 dhclient[50560]: DHCPOFFER from 10.18.124.1
              Mar 29 11:52:14 dhclient[50560]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 1
              Mar 29 11:52:14 dhclient: PREINIT
              Mar 29 11:52:14 dhclient: Deleting old routes
              Mar 29 11:52:14 dhclient: EXPIRE
              Mar 29 11:52:00 dhclient[50560]: DHCPREQUEST on fxp0 to 192.168.100.1 port 67
              Mar 29 11:51:49 dhclient[50560]: DHCPREQUEST on fxp0 to 192.168.100.1 port 67
              Mar 29 11:51:45 dhclient[50560]: DHCPREQUEST on fxp0 to 192.168.100.1 port 67
              Mar 29 11:51:43 dhclient[50560]: DHCPREQUEST on fxp0 to 192.168.100.1 port 67
              Mar 29 11:51:20 php: : Resyncing OpenVPN instances for interface OPT1.
              Mar 29 11:51:15 php: : wan: pptp link configuration failed. No ip address found for gch.bezeqint.net.
              Mar 29 11:51:15 check_reload_status: configuring interface wan
              Mar 29 11:51:14 php: : interfaces: reloading interfaces dependent on: opt1
              Mar 29 11:51:14 apinger: Starting Alarm Pinger, apinger(54645)
              Mar 29 11:51:14 check_reload_status: reloading filter
              Mar 29 11:51:13 php: : rc.newwanip: on (IP address: 192.168.100.10) (interface: opt1) (real interface: fxp0).
              Mar 29 11:51:13 php: : rc.newwanip: Informational is starting fxp0.
              Mar 29 11:51:13 dhclient[46021]: bound to 192.168.100.10 – renewal in 30 seconds.
              Mar 29 11:51:13 check_reload_status: rc.newwanip starting fxp0
              Mar 29 11:51:13 dhclient: Creating resolv.conf
              Mar 29 11:51:13 dhclient: Adding new routes to interface: fxp0
              Mar 29 11:51:13 dhclient: New Routers (fxp0): 192.168.100.1
              Mar 29 11:51:13 dhclient: New Broadcast Address (fxp0): 192.168.100.255
              Mar 29 11:51:13 dhclient: New Subnet Mask (fxp0): 255.255.255.0
              Mar 29 11:51:13 dhclient: New IP Address (fxp0): 192.168.100.10
              Mar 29 11:51:13 dhclient: ifconfig fxp0 inet 192.168.100.10 netmask 255.255.255.0 broadcast 192.168.100.255
              Mar 29 11:51:13 dhclient: Starting add_new_address()
              Mar 29 11:51:13 dhclient: BOUND
              Mar 29 11:51:13 dhclient[46021]: DHCPACK from 192.168.100.1
              Mar 29 11:51:12 dhclient[46021]: DHCPREQUEST on fxp0 to 255.255.255.255 port 67
              Mar 29 11:51:12 dhclient: ARPCHECK
              Mar 29 11:51:10 dhclient: ARPSEND
              Mar 29 11:51:10 dhclient[46021]: DHCPOFFER from 192.168.100.1
              Mar 29 11:51:10 dhclient[46021]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 1
              Mar 29 11:51:10 dhclient[46021]: DHCPNAK from 192.168.100.1
              Mar 29 11:51:09 dhclient[46021]: DHCPREQUEST on fxp0 to 255.255.255.255 port 67
              Mar 29 11:51:07 dhclient[46021]: DHCPREQUEST on fxp0 to 255.255.255.255 port 67
              Mar 29 11:51:06 dhclient[46021]: DHCPREQUEST on fxp0 to 255.255.255.255 port 67
              Mar 29 11:51:05 dhclient[46021]: DHCPREQUEST on fxp0 to 255.255.255.255 port 67
              Mar 29 11:51:04 dhclient[46021]: DHCPREQUEST on fxp0 to 255.255.255.255 port 67
              Mar 29 11:51:04 dhclient: PREINIT
              Mar 29 11:51:04 php: : interfaces: bringing down interfaces dependent on: opt1
              Mar 29 11:51:02 php: : HOTPLUG: Configuring interface opt1
              Mar 29 11:51:02 php: : DEVD Ethernet attached event for opt1
              Mar 29 11:51:02 kernel: fxp0: link state changed to UP
              Mar 29 11:51:02 check_reload_status: Linkup starting fxp0
              Mar 29 11:50:35 php: : interfaces: bringing down interfaces dependent on: opt1
              Mar 29 11:50:33 dhclient[39444]: exiting.
              Mar 29 11:50:33 dhclient[39444]: exiting.
              Mar 29 11:50:33 dhclient[39444]: connection closed
              Mar 29 11:50:33 dhclient[39444]: connection closed
              Mar 29 11:50:33 php: : DEVD Ethernet detached event for opt1
              Mar 29 11:50:33 kernel: fxp0: link state changed to DOWN
              Mar 29 11:50:33 check_reload_status: Linkup starting fxp0

              and this is the PPP tab log:
              Mar 29 12:00:27 ppp: [wan] IFACE: Up event
              Mar 29 12:00:25 ppp: [wan] 62.x.x.x -> 212.25.68.21
              Mar 29 12:00:25 ppp: [wan] IPCP: LayerUp
              Mar 29 12:00:25 ppp: [wan] IPCP: state change Ack-Sent –> Opened
              Mar 29 12:00:25 ppp: [wan] SECDNS 192.115.106.35
              Mar 29 12:00:25 ppp: [wan] PRIDNS 62.219.186.7
              Mar 29 12:00:25 ppp: [wan] IPADDR 62.x.x.x
              Mar 29 12:00:25 ppp: [wan] IPCP: rec'd Configure Ack #23 (Ack-Sent)
              Mar 29 12:00:25 ppp: [wan] SECDNS 192.115.106.35
              Mar 29 12:00:25 ppp: [wan] PRIDNS 62.219.186.7
              Mar 29 12:00:25 ppp: [wan] IPADDR 62.x.x.x
              Mar 29 12:00:25 ppp: [wan] IPCP: SendConfigReq #23
              Mar 29 12:00:25 ppp: [wan] SECDNS 192.115.106.35
              Mar 29 12:00:25 ppp: [wan] PRIDNS 62.219.186.7
              Mar 29 12:00:25 ppp: [wan] 62.x.x.x is OK
              Mar 29 12:00:25 ppp: [wan] IPADDR 62.x.x.x
              Mar 29 12:00:25 ppp: [wan] IPCP: rec'd Configure Nak #22 (Ack-Sent)
              Mar 29 12:00:25 ppp: [wan] SECDNS 0.0.0.0
              Mar 29 12:00:25 ppp: [wan] PRIDNS 0.0.0.0
              Mar 29 12:00:25 ppp: [wan] IPADDR 0.0.0.0
              Mar 29 12:00:25 ppp: [wan] IPCP: SendConfigReq #22
              Mar 29 12:00:25 ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
              Mar 29 12:00:25 ppp: [wan] IPCP: rec'd Configure Reject #21 (Ack-Sent)
              Mar 29 12:00:25 ppp: [wan] IPCP: state change Req-Sent –> Ack-Sent
              Mar 29 12:00:25 ppp: [wan] IPADDR 212.25.68.21
              Mar 29 12:00:25 ppp: [wan] IPCP: SendConfigAck #1
              Mar 29 12:00:25 ppp: [wan] 212.25.68.21 is OK
              Mar 29 12:00:25 ppp: [wan] IPADDR 212.25.68.21
              Mar 29 12:00:25 ppp: [wan] IPCP: rec'd Configure Request #1 (Req-Sent)
              Mar 29 12:00:25 ppp: [wan] SECDNS 0.0.0.0
              Mar 29 12:00:25 ppp: [wan] PRIDNS 0.0.0.0
              Mar 29 12:00:25 ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
              Mar 29 12:00:25 ppp: [wan] IPADDR 0.0.0.0
              Mar 29 12:00:25 ppp: [wan] IPCP: SendConfigReq #21
              Mar 29 12:00:25 ppp: [wan] IPCP: state change Starting –> Req-Sent
              Mar 29 12:00:25 ppp: [wan] IPCP: Up event
              Mar 29 12:00:25 ppp: [wan] IPCP: LayerStart
              Mar 29 12:00:25 ppp: [wan] IPCP: state change Initial –> Starting
              Mar 29 12:00:25 ppp: [wan] IPCP: Open event
              Mar 29 12:00:25 ppp: [wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps
              Mar 29 12:00:25 ppp: [wan_link0] Link: Join bundle "wan"
              Mar 29 12:00:25 ppp: [wan_link0] Link: Matched action 'bundle "wan" ""'
              Mar 29 12:00:25 ppp: [wan_link0] LCP: authorization successful
              Mar 29 12:00:25 ppp: [wan_link0] PAP: rec'd ACK #1 len: 5
              Mar 29 12:00:25 ppp: [wan_link0] LCP: LayerUp
              Mar 29 12:00:25 ppp: [wan_link0] PAP: sending REQUEST #1 len: 22
              Mar 29 12:00:25 ppp: [wan_link0] PAP: using authname "citynet2"
              Mar 29 12:00:25 ppp: [wan_link0] LCP: auth: peer wants PAP, I want nothing
              Mar 29 12:00:25 ppp: [wan_link0] LCP: state change Ack-Sent –> Opened
              Mar 29 12:00:25 ppp: [wan_link0] MAGICNUM 2e3e1d30
              Mar 29 12:00:25 ppp: [wan_link0] MRU 1500
              Mar 29 12:00:25 ppp: [wan_link0] ACCMAP 0x000a0000
              Mar 29 12:00:25 ppp: [wan_link0] PROTOCOMP
              Mar 29 12:00:25 ppp: [wan_link0] ACFCOMP
              Mar 29 12:00:25 ppp: [wan_link0] LCP: rec'd Configure Ack #9 (Ack-Sent)
              Mar 29 12:00:25 ppp: [wan_link0] LCP: state change Req-Sent –> Ack-Sent
              Mar 29 12:00:25 ppp: [wan_link0] MAGICNUM 63ec68af
              Mar 29 12:00:25 ppp: [wan_link0] AUTHPROTO PAP
              Mar 29 12:00:25 ppp: [wan_link0] LCP: SendConfigAck #1
              Mar 29 12:00:25 ppp: [wan_link0] MAGICNUM 63ec68af
              Mar 29 12:00:25 ppp: [wan_link0] AUTHPROTO PAP
              Mar 29 12:00:25 ppp: [wan_link0] LCP: rec'd Configure Request #1 (Req-Sent)
              Mar 29 12:00:25 ppp: [wan_link0] MAGICNUM 2e3e1d30
              Mar 29 12:00:25 ppp: [wan_link0] MRU 1500
              Mar 29 12:00:25 ppp: [wan_link0] ACCMAP 0x000a0000
              Mar 29 12:00:25 ppp: [wan_link0] PROTOCOMP
              Mar 29 12:00:25 ppp: [wan_link0] ACFCOMP
              Mar 29 12:00:25 ppp: [wan_link0] LCP: SendConfigReq #9
              Mar 29 12:00:25 ppp: [wan_link0] LCP: state change Starting –> Req-Sent
              Mar 29 12:00:25 ppp: [wan_link0] LCP: Up event
              Mar 29 12:00:25 ppp: [wan_link0] Link: UP event
              Mar 29 12:00:25 ppp: [wan_link0] PPTP call successful
              Mar 29 12:00:25 ppp: [wan_link0] Link: reconnection attempt 2
              Mar 29 12:00:24 ppp: [wan_link0] Link: reconnection attempt 2 in 1 seconds
              Mar 29 12:00:24 ppp: [wan_link0] LCP: Down event
              Mar 29 12:00:24 ppp: [wan_link0] Link: DOWN event
              Mar 29 12:00:24 ppp: [wan_link0] PPTP call failed
              Mar 29 11:59:24 ppp: [wan_link0] Link: reconnection attempt 1
              Mar 29 11:59:20 ppp: [wan_link0] Link: reconnection attempt 1 in 4 seconds
              Mar 29 11:59:20 ppp: [wan_link0] LCP: LayerDown
              Mar 29 11:59:20 ppp: [wan] IPCP: state change Closing –> Initial
              Mar 29 11:59:20 ppp: [wan] Bundle: No NCPs left. Closing links…
              Mar 29 11:59:20 ppp: [wan] IPCP: LayerFinish
              Mar 29 11:59:20 ppp: [wan] IPCP: Down event
              Mar 29 11:59:20 ppp: [wan] IFACE: Down event
              Mar 29 11:59:20 ppp: [wan] IPCP: LayerDown
              Mar 29 11:59:20 ppp: [wan] IPCP: SendTerminateReq #20
              Mar 29 11:59:20 ppp: [wan] IPCP: state change Opened –> Closing
              Mar 29 11:59:20 ppp: [wan] IPCP: Close event
              Mar 29 11:59:20 ppp: [wan] Bundle: Status update: up 0 links, total bandwidth 9600 bps
              Mar 29 11:59:20 ppp: [wan_link0] Link: Leave bundle "wan"
              Mar 29 11:59:20 ppp: [wan_link0] LCP: state change Opened –> Starting
              Mar 29 11:59:20 ppp: [wan_link0] LCP: Down event
              Mar 29 11:59:20 ppp: [wan_link0] Link: DOWN event
              Mar 29 11:59:20 ppp: [wan_link0] PPTP call terminated
              Mar 29 11:58:22 ppp: [wan] IFACE: Up event
              Mar 29 11:58:20 ppp: [wan] 62.x.x.x -> 212.25.68.21
              Mar 29 11:58:20 ppp: [wan] IPCP: LayerUp
              Mar 29 11:58:20 ppp: [wan] IPCP: state change Ack-Sent –> Opened
              Mar 29 11:58:20 ppp: [wan] SECDNS 192.115.106.35
              Mar 29 11:58:20 ppp: [wan] PRIDNS 62.219.186.7
              Mar 29 11:58:20 ppp: [wan] IPADDR 62.x.x.x
              Mar 29 11:58:20 ppp: [wan] IPCP: rec'd Configure Ack #19 (Ack-Sent)
              Mar 29 11:58:20 ppp: [wan] SECDNS 192.115.106.35
              Mar 29 11:58:20 ppp: [wan] PRIDNS 62.219.186.7
              Mar 29 11:58:20 ppp: [wan] IPADDR 62.x.x.x
              Mar 29 11:58:20 ppp: [wan] IPCP: SendConfigReq #19
              Mar 29 11:58:20 ppp: [wan] SECDNS 192.115.106.35
              Mar 29 11:58:20 ppp: [wan] PRIDNS 62.219.186.7
              Mar 29 11:58:20 ppp: [wan] 62.x.x.x is OK
              Mar 29 11:58:20 ppp: [wan] IPADDR 62.x.x.x
              Mar 29 11:58:20 ppp: [wan] IPCP: rec'd Configure Nak #18 (Ack-Sent)
              Mar 29 11:58:20 ppp: [wan] SECDNS 0.0.0.0
              Mar 29 11:58:20 ppp: [wan] PRIDNS 0.0.0.0
              Mar 29 11:58:20 ppp: [wan] IPADDR 0.0.0.0
              Mar 29 11:58:20 ppp: [wan] IPCP: SendConfigReq #18
              Mar 29 11:58:20 ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
              Mar 29 11:58:20 ppp: [wan] IPCP: rec'd Configure Reject #17 (Ack-Sent)
              Mar 29 11:58:20 ppp: [wan] IPCP: state change Req-Sent –> Ack-Sent
              Mar 29 11:58:20 ppp: [wan] IPADDR 212.25.68.21
              Mar 29 11:58:20 ppp: [wan] IPCP: SendConfigAck #1
              Mar 29 11:58:20 ppp: [wan] 212.25.68.21 is OK
              Mar 29 11:58:20 ppp: [wan] IPADDR 212.25.68.21
              Mar 29 11:58:20 ppp: [wan] IPCP: rec'd Configure Request #1 (Req-Sent)
              Mar 29 11:58:20 ppp: [wan] SECDNS 0.0.0.0
              Mar 29 11:58:20 ppp: [wan] PRIDNS 0.0.0.0
              Mar 29 11:58:20 ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
              Mar 29 11:58:20 ppp: [wan] IPADDR 0.0.0.0
              Mar 29 11:58:20 ppp: [wan] IPCP: SendConfigReq #17
              Mar 29 11:58:20 ppp: [wan] IPCP: state change Starting –> Req-Sent
              Mar 29 11:58:20 ppp: [wan] IPCP: Up event
              Mar 29 11:58:20 ppp: [wan] IPCP: LayerStart
              Mar 29 11:58:20 ppp: [wan] IPCP: state change Initial –> Starting
              Mar 29 11:58:20 ppp: [wan] IPCP: Open event
              Mar 29 11:58:20 ppp: [wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps
              Mar 29 11:58:20 ppp: [wan_link0] Link: Join bundle "wan"
              Mar 29 11:58:20 ppp: [wan_link0] Link: Matched action 'bundle "wan" ""'
              Mar 29 11:58:20 ppp: [wan_link0] LCP: authorization successful
              Mar 29 11:58:20 ppp: [wan_link0] PAP: rec'd ACK #1 len: 5
              Mar 29 11:58:20 ppp: [wan_link0] LCP: LayerUp
              Mar 29 11:58:20 ppp: [wan_link0] PAP: sending REQUEST #1 len: 22
              Mar 29 11:58:20 ppp: [wan_link0] PAP: using authname "citynet2"
              Mar 29 11:58:20 ppp: [wan_link0] LCP: auth: peer wants PAP, I want nothing
              Mar 29 11:58:20 ppp: [wan_link0] LCP: state change Ack-Sent –> Opened
              Mar 29 11:58:20 ppp: [wan_link0] MAGICNUM 458ad0c2
              Mar 29 11:58:20 ppp: [wan_link0] MRU 1500
              Mar 29 11:58:20 ppp: [wan_link0] ACCMAP 0x000a0000
              Mar 29 11:58:20 ppp: [wan_link0] PROTOCOMP
              Mar 29 11:58:20 ppp: [wan_link0] ACFCOMP
              Mar 29 11:58:20 ppp: [wan_link0] LCP: rec'd Configure Ack #8 (Ack-Sent)
              Mar 29 11:58:20 ppp: [wan_link0] LCP: state change Req-Sent –> Ack-Sent
              Mar 29 11:58:20 ppp: [wan_link0] MAGICNUM 63ea7ff9
              Mar 29 11:58:20 ppp: [wan_link0] AUTHPROTO PAP
              Mar 29 11:58:20 ppp: [wan_link0] LCP: SendConfigAck #1
              Mar 29 11:58:20 ppp: [wan_link0] MAGICNUM 63ea7ff9
              Mar 29 11:58:20 ppp: [wan_link0] AUTHPROTO PAP
              Mar 29 11:58:20 ppp: [wan_link0] LCP: rec'd Configure Request #1 (Req-Sent)
              Mar 29 11:58:20 ppp: [wan_link0] MAGICNUM 458ad0c2
              Mar 29 11:58:20 ppp: [wan_link0] MRU 1500
              Mar 29 11:58:20 ppp: [wan_link0] ACCMAP 0x000a0000
              Mar 29 11:58:20 ppp: [wan_link0] PROTOCOMP
              Mar 29 11:58:20 ppp: [wan_link0] ACFCOMP
              Mar 29 11:58:20 ppp: [wan_link0] LCP: SendConfigReq #8
              Mar 29 11:58:20 ppp: [wan_link0] LCP: state change Starting –> Req-Sent
              Mar 29 11:58:20 ppp: [wan_link0] LCP: Up event
              Mar 29 11:58:20 ppp: [wan_link0] Link: UP event
              Mar 29 11:58:20 ppp: [wan_link0] PPTP call successful
              Mar 29 11:58:20 ppp: [wan_link0] Link: reconnection attempt 2
              Mar 29 11:58:16 ppp: [wan_link0] Link: reconnection attempt 2 in 4 seconds
              Mar 29 11:58:16 ppp: [wan_link0] LCP: Down event
              Mar 29 11:58:16 ppp: [wan_link0] Link: DOWN event
              Mar 29 11:58:16 ppp: [wan_link0] PPTP call failed
              Mar 29 11:56:46 ppp: [wan_link0] Link: reconnection attempt 1
              Mar 29 11:56:45 ppp: [wan_link0] Link: reconnection attempt 1 in 1 seconds
              Mar 29 11:56:45 ppp: [wan_link0] LCP: state change Stopping –> Starting
              Mar 29 11:56:45 ppp: [wan_link0] LCP: Down event
              Mar 29 11:56:45 ppp: [wan_link0] Link: DOWN event
              Mar 29 11:56:45 ppp: [wan_link0] PPTP call terminated
              Mar 29 11:56:45 ppp: [wan_link0] LCP: LayerDown
              Mar 29 11:56:45 ppp: [wan_link0] LCP: SendTerminateReq #7
              Mar 29 11:56:45 ppp: [wan] IPCP: state change Closing –> Initial
              Mar 29 11:56:45 ppp: [wan] Bundle: No NCPs left. Closing links…
              Mar 29 11:56:45 ppp: [wan] IPCP: LayerFinish
              Mar 29 11:56:45 ppp: [wan] IPCP: Down event
              Mar 29 11:56:45 ppp: [wan] IFACE: Down event
              Mar 29 11:56:45 ppp: [wan] IPCP: LayerDown
              Mar 29 11:56:45 ppp: [wan] IPCP: SendTerminateReq #16
              Mar 29 11:56:45 ppp: [wan] IPCP: state change Opened –> Closing
              Mar 29 11:56:45 ppp: [wan] IPCP: Close event
              Mar 29 11:56:45 ppp: [wan] Bundle: Status update: up 0 links, total bandwidth 9600 bps
              Mar 29 11:56:45 ppp: [wan_link0] Link: Leave bundle "wan"
              Mar 29 11:56:45 ppp: [wan_link0] LCP: state change Opened –> Stopping
              Mar 29 11:56:45 ppp: [wan_link0] LCP: received an invalid magic number
              Mar 29 11:56:45 ppp: [wan_link0] LCP: magic number is wrong: 0x63e724a8 != 0x63e820b3
              Mar 29 11:56:36 ppp: [wan_link0] LCP: no reply to 2 echo request(s)
              Mar 29 11:56:26 ppp: [wan_link0] LCP: no reply to 1 echo request(s)
              Mar 29 11:55:46 ppp: [wan] IFACE: Up event
              Mar 29 11:55:45 ppp: [wan] 62.x.x.x -> 212.25.68.21
              Mar 29 11:55:45 ppp: [wan] IPCP: LayerUp
              Mar 29 11:55:45 ppp: [wan] IPCP: state change Ack-Sent –> Opened

              any ideas?

              1 Reply Last reply Reply Quote 0
              • M
                Micky
                last edited by

                Ozzik, when trying l2tp have you tried hot.bezeqint.net.il, or 212.25.127.15 as the host address?
                (i dont think it's gch.bezeqint.net.il)

                And i didn't tested it yet, i no longer have the atom board i used, and I'm having trouble to set the host-only interface in vmware, so I'll try
                to test it when i resolve it.

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

                  @Micky, you're right as always:)
                  Thank you!
                  only the hostname is hot.bezeqint.net (without the .il)
                  with this hostname (or the IP) l2tp is up and running.
                  But I believe this ISP server is l2tp only. You have to use the gch.bezeqint.net if you want PPTP.
                  And that continues to disconnect.

                  Anyway, like Loke mentioned earlier - the interface doesn't connect after reboot, you have to press the button for that. So I thought that maybe it's because the WAN interface comes up before the OPT1, which has to get the DHCP.
                  So I changed the order, i.e. WAN was assigned to physical interface but disconnected, OPT1 was connected with DHCP+ as before, and OPT2 became the new WAN(l2tp).
                  In this situation the l2tp was up after reboot, but the default route didn't change for some reason and was still 172.x.x.x, so I could ping the ISP server, but no more than that.

                  Anyway to fix this?

                  And guys, thanks a lot! Great job!

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

                    @Micky:

                    @Ozzik

                    I didn't find the opt1 interface in your config, as far as i remember you should assign the physical interface to optx (and set it to DHCP), then create a ppp interface (l2tp) and use the opt1 as its link and only then assign the ppp to wan.
                    So there should be an additional OPTx interface.

                    @Loke

                    No, there was no connect/disconnect button at the interface status page for l2tp.

                    Yes, it was.

                    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

                      Ozzik just go to system->Routing and select the OPTx interface as default gw.

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

                        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!

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

                          Using the hardware above I triad to connect today.

                          2.0-RC1 (i386) built on Fri Apr 1 12:38:39 EDT 2011
                          First I set WAN to DHCP, assighen to interface sk0.
                          Got IP: 172.19.180.19, Gateway 172.19.176.1, Subnet mask 255.255.248.0
                          Got DNS server(s) : 192.168.101.101 & 192.168.101.102
                          Triad Ping : hot.bezeqint.net
                          PING l2tp.i014.net (212.25.127.14) from 172.19.180.19: 56 data bytes
                          3 packets transmitted, 3 packets received, 0.0% packet loss
                          round-trip min/avg/max/stddev = 10.448/13.610/17.584/2.969 ms

                          Until here it's OK.

                          Interfaces >> assign >> PPPs >>
                          Created a new L2TP link.
                          Interface is set to sk0 (wan) and gageway "hot.bezeqint.com

                          Interfaces >> assign >>
                          create a new interface (opt1) with l2tp0 as the Network port.

                          chenged l2tp0's interface to opt1.

                          swaped opt1 & wan.

                          Nothing. it will not connect.
                          Am I doing something wrong ?

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

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

                            @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.

                            2. Assuming you only have WAN and LAN and WAN is connected directly to the modem, go to Interfaces->WAN and set it to DHCP. In a lower section you'll see another checkbox "Enable DHCP+L2TP or DHCP+PPTP." You'll only see it after the gitsync. Check it. Save. Apply.

                            3. Go to Interfaces->(assign). Choose PPPs tab and add new. Choose L2TP, then in "Link interface(s)" choose WAN, not your physical WAN, but just WAN. Type in your username/password and the ISP's VPN server (in this case hot.bezeqint.net). Leave the "Local IP" empty. Save.

                            4. Go to Interfaces->(assign) again and add a new interface (OPT1). Assign the newly created L2TP to it and save.
                            Go to Interfaces->OPT1 and enable it. Save.

                            Time to check.

                            5. If you want the L2TP to connect automatically after reboot you have to make sure that the DHCP interface (WAN in this case) is initiated before the L2TP interface (OPT1 in this case), i.e WAN->LAN->OPT1->OPT2 and so on. It usually takes 10-30 sec for the L2TP to connect after the reboot, but it does so automatically.

                            6. If for some reason you see L2TP connected, but the only thing you can ping is your ISP's VPN server - you have the default route wrong. Go to System->Routes and set the right route (public IP, not the 172.x.x.x) to default.

                            Hope it helps.

                            1 Reply Last reply Reply Quote 0
                            • 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
                                            • First post
                                              Last post