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

    Pppoe not working - "CHAP: sending RESPONSE #1" loop

    Scheduled Pinned Locked Moved General pfSense Questions
    6 Posts 4 Posters 2.4k 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.
    • M
      machinery
      last edited by

      Hello!

      I am trying to set up a PPPoE connection on WAN using pfSense and a DrayTek Vigor 130 modem.

      I know the modem works and it is properly configured, because I can successfully connect with PPPoE through it from a Linux computer.

      With pfSense, instead, I get this:

      
Oct 28 01:14:43 	ppp 		[wan_link0] Link: reconnection attempt 11
Oct 28 01:14:43 	ppp 		[wan_link0] PPPoE: Connecting to ''
Oct 28 01:14:43 	ppp 		PPPoE: rec'd ACNAME "crk-ar1"
Oct 28 01:14:43 	ppp 		[wan_link0] PPPoE: connection successful
Oct 28 01:14:43 	ppp 		[wan_link0] Link: UP event
Oct 28 01:14:43 	ppp 		[wan_link0] LCP: Up event
Oct 28 01:14:43 	ppp 		[wan_link0] LCP: state change Starting --> Req-Sent
Oct 28 01:14:43 	ppp 		[wan_link0] LCP: SendConfigReq #34
Oct 28 01:14:43 	ppp 		[wan_link0] PROTOCOMP
Oct 28 01:14:43 	ppp 		[wan_link0] MRU 1492
Oct 28 01:14:43 	ppp 		[wan_link0] MAGICNUM 0x7ea1ac93
Oct 28 01:14:43 	ppp 		[wan_link0] LCP: rec'd Configure Request #1 (Req-Sent)
Oct 28 01:14:43 	ppp 		[wan_link0] MRU 1492
Oct 28 01:14:43 	ppp 		[wan_link0] AUTHPROTO CHAP MD5
Oct 28 01:14:43 	ppp 		[wan_link0] MAGICNUM 0x3eabbd16
Oct 28 01:14:43 	ppp 		[wan_link0] LCP: SendConfigAck #1
Oct 28 01:14:43 	ppp 		[wan_link0] MRU 1492
Oct 28 01:14:43 	ppp 		[wan_link0] AUTHPROTO CHAP MD5
Oct 28 01:14:43 	ppp 		[wan_link0] MAGICNUM 0x3eabbd16
Oct 28 01:14:43 	ppp 		[wan_link0] LCP: state change Req-Sent --> Ack-Sent
Oct 28 01:14:43 	ppp 		[wan_link0] LCP: rec'd Configure Ack #34 (Ack-Sent)
Oct 28 01:14:43 	ppp 		[wan_link0] PROTOCOMP
Oct 28 01:14:43 	ppp 		[wan_link0] MRU 1492
Oct 28 01:14:43 	ppp 		[wan_link0] MAGICNUM 0x7ea1ac93
Oct 28 01:14:43 	ppp 		[wan_link0] LCP: state change Ack-Sent --> Opened
Oct 28 01:14:43 	ppp 		[wan_link0] LCP: auth: peer wants CHAP, I want nothing
Oct 28 01:14:43 	ppp 		[wan_link0] LCP: LayerUp
Oct 28 01:14:43 	ppp 		[wan_link0] CHAP: rec'd CHALLENGE #1 len: 28
Oct 28 01:14:43 	ppp 		[wan_link0] Name: "crk-ar1"
Oct 28 01:14:43 	ppp 		[wan_link0] CHAP: Using authname "digiweb@nga.digiweb.ie"
Oct 28 01:14:43 	ppp 		[wan_link0] CHAP: sending RESPONSE #1 len: 43
Oct 28 01:14:45 	ppp 		[wan_link0] CHAP: sending RESPONSE #1 len: 43
Oct 28 01:14:47 	ppp 		[wan_link0] CHAP: sending RESPONSE #1 len: 43
Oct 28 01:14:49 	ppp 		[wan_link0] CHAP: sending RESPONSE #1 len: 43
Oct 28 01:14:51 	ppp 		[wan_link0] CHAP: sending RESPONSE #1 len: 43
Oct 28 01:14:53 	ppp 		[wan_link0] CHAP: sending RESPONSE #1 len: 43
Oct 28 01:14:55 	ppp 		[wan_link0] CHAP: sending RESPONSE #1 len: 43
Oct 28 01:14:57 	ppp 		[wan_link0] CHAP: sending RESPONSE #1 len: 43
Oct 28 01:14:59 	ppp 		[wan_link0] CHAP: sending RESPONSE #1 len: 43 
Oct 28 01:15:01 	ppp 		[wan_link0] CHAP: sending RESPONSE #1 len: 43
Oct 28 01:15:03 	ppp 		[wan_link0] CHAP: sending RESPONSE #1 len: 43
Oct 28 01:15:05 	ppp 		[wan_link0] CHAP: sending RESPONSE #1 len: 43
Oct 28 01:15:07 	ppp 		[wan_link0] CHAP: sending RESPONSE #1 len: 43
Oct 28 01:15:09 	ppp 		[wan_link0] CHAP: sending RESPONSE #1 len: 43 
Oct 28 01:15:11 	ppp 		[wan_link0] CHAP: sending RESPONSE #1 len: 43
Oct 28 01:15:13 	ppp 		[wan_link0] CHAP: sending RESPONSE #1 len: 43
Oct 28 01:15:15 	ppp 		[wan_link0] CHAP: sending RESPONSE #1 len: 43
Oct 28 01:15:17 	ppp 		[wan_link0] CHAP: sending RESPONSE #1 len: 43
Oct 28 01:15:19 	ppp 		[wan_link0] CHAP: sending RESPONSE #1 len: 43 
Oct 28 01:15:21 	ppp 		[wan_link0] CHAP: sending RESPONSE #1 len: 43
Oct 28 01:15:23 	ppp 		[wan_link0] LCP: authorization timer expired
Oct 28 01:15:23 	ppp 		[wan_link0] LCP: authorization failed
Oct 28 01:15:23 	ppp 		[wan_link0] LCP: parameter negotiation failed
Oct 28 01:15:23 	ppp 		[wan_link0] LCP: state change Opened --> Stopping
Oct 28 01:15:23 	ppp 		[wan_link0] LCP: SendTerminateReq #35
Oct 28 01:15:23 	ppp 		[wan_link0] LCP: LayerDown
Oct 28 01:15:24 	ppp 		[wan_link0] rec'd proto CHAP during terminate phase
Oct 28 01:15:24 	ppp 		[wan_link0] rec'd proto IPCP during terminate phase
Oct 28 01:15:25 	ppp 		[wan_link0] LCP: SendTerminateReq #36
Oct 28 01:15:25 	ppp 		[wan_link0] LCP: rec'd Terminate Ack #36 (Stopping)
Oct 28 01:15:25 	ppp 		[wan_link0] LCP: state change Stopping --> Stopped
Oct 28 01:15:25 	ppp 		[wan_link0] LCP: LayerFinish
Oct 28 01:15:25 	ppp 		[wan_link0] PPPoE: connection closed
Oct 28 01:15:25 	ppp 		[wan_link0] Link: DOWN event
Oct 28 01:15:25 	ppp 		[wan_link0] LCP: Down event
Oct 28 01:15:25 	ppp 		[wan_link0] LCP: state change Stopped --> Starting
Oct 28 01:15:25 	ppp 		[wan_link0] LCP: LayerStart
Oct 28 01:15:25 	ppp 		[wan_link0] Link: reconnection attempt 12 in 3 seconds
Oct 28 01:15:28 	ppp 		[wan_link0] Link: reconnection attempt 12

      This happens over and over again… Any idea? Thanks a lot for any help!

      I've tried everything I could think of to fix it, and I still did not manage. I know there is a separate thread with similar logs where some users report that pfSense cannot reconnect after a disconnection unless it's rebooted, but in my case it never connects, no matter how many times I reboot/reset the modem, so I believe it's a separate issue.

      1 Reply Last reply Reply Quote 0
      • GrimsonG
        Grimson Banned
        last edited by

        If you are using pfSense 2.4.1 see here: https://forum.pfsense.org/index.php?topic=138804.0

        If so, your choices are:

        • Make a fresh install of 2.4.0.

        • Upgrade to 2.4.2 Beta.

        • Let the Vigor insert the VLAN tag.

        If you aren't running 2.4.1 post actual details about your configuration.

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

          Hi Grimson, Thanks for replying!

          I am using 2.4.1, but I haven't configured the VLAN in pfSense, only in the Vigor 130. I saw that thread, and I was wondering if it affects even configurations where the VLAN is set by the modem?

          My configuration for the WAN is PPPoE, standard settings (essentially, I just enter the username and password). Service name is empty, and everything else is empty/default. I've tried with or without the options to discard bogons/local IPs, but neither work, so that shouldn't be the issue.

          I haven't touched any of the Advanced Configuration options in the PPP tab.

          Is there anything else that might be useful to post?

          My /var/etc/mpd_wan.conf:

          startup:
	# configure the console
	set console close
	# configure the web server
	set web close

default:
pppoeclient:
	create bundle static wan
	set bundle enable ipv6cp
	set iface name pppoe0
	set iface route default
	set iface disable on-demand
	set iface idle 0
	set iface enable tcpmssfix
	set iface up-script /usr/local/sbin/ppp-linkup
	set iface down-script /usr/local/sbin/ppp-linkdown
	set ipcp ranges 0.0.0.0/0 0.0.0.0/0
	set ipcp enable req-pri-dns
	set ipcp enable req-sec-dns
	#log -bund -ccp -chat -iface -ipcp -lcp -link

	create link static wan_link0 pppoe
	set link action bundle wan
	set link disable multilink
	set link keep-alive 10 60
	set link max-redial 0
	set link disable chap pap
	set link accept chap pap eap
	set link disable incoming
	set link mtu 1492
	set auth authname "digiweb@nga.digiweb.ie"
	set auth password digiweb
	set pppoe service ""
	set pppoe iface em0
	open
          1 Reply Last reply Reply Quote 0
          • ?
            Guest
            last edited by

            It did not affect mine.

            However, a clean install of 2.4.2 would not hurt, it's working perfectly well.

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

              Wait, was pppoe connect with "." vlans been fixed in 2.4.2?

              1 Reply Last reply Reply Quote 0
              • GrimsonG
                Grimson Banned
                last edited by

                @maverick_slo:

                Wait, was pppoe connect with "." vlans been fixed in 2.4.2?

                Yes.

                @machinery
                I just saw that you posted the log from the 11th connect attempt. Please see if you can find the first one and post it. It's not uncommon for ISPs to ignore consecutive login attempts after a few failures, your log looks just like that.

                You can try to disconnect the pfSense box from the modem, check that PPPoE password and username are correct, wait an hour or so and then try again.

                Another possibility:
                If your ISP isn't validating connections based on the username/password combination but based on the port id in the DSLAM, and you made the first connection from the Linux computer, then it's possible that it (for a time) expects new connections to come from the same MAC address. Similiar to how cable works for many ISPs. In that case you can try to use the MAC from the Linux computer for the PPPoE connection on the pfSense.

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