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

    PPPOE Login Lock

    General pfSense Questions
    1
    2
    1.7k
    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.
    • W
      werty1st
      last edited by

      for german readers: http://forum.pfsense.org/index.php/topic,49444.0.html

      hello,

      for days i am now trying to setup a DSL pppoe connection with pfsense. but i allways get an error about a "login lock".

      i called my local provider and asked him to remove the lock, which occures after 9 wrong login attempts with the wrong password.

      who knows how to avoid this? why can this happen? does pfsense try to connect bevore i setup the pppoe username + login?

      is there a difference between the two setup options: interface(em1)->wan->pppoe OR interface->ppp->pppoe->em1/wan ?

      i tried "Configure a NULL Service name"

      thanks in advance.

      
      May 15 10:03:35	ppp: [wan_link0] LCP: parameter negotiation failed
      May 15 10:03:35	ppp: [wan_link0] LCP: authorization failed
      May 15 10:03:35	ppp: [wan_link0] MESG: 0023 LSHNO004 0113648215 login lock
      May 15 10:03:35	ppp: [wan_link0] PAP: rec'd NAK #1 len: 40
      May 15 10:03:35	ppp: [wan_link0] LCP: LayerUp
      May 15 10:03:35	ppp: [wan_link0] PAP: sending REQUEST #1 len: 53
      May 15 10:03:35	ppp: [wan_link0] PAP: using authname "XXXXXXXXXXXXXXXXXXX@t-online.de"
      May 15 10:03:35	ppp: [wan_link0] LCP: auth: peer wants PAP, I want nothing
      May 15 10:03:35	ppp: [wan_link0] LCP: state change Ack-Sent --> Opened
      
      
      1 Reply Last reply Reply Quote 0
      • W
        werty1st
        last edited by

        after doing some further research i found out that the wrong password attemps happen near the time of the periodic reset.

        manual reconnects do not cause this behaviour.

        i will now try to capture a periodic rest with wireshark.

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