Talk Talk Fiber Broadband via BT Openreach modem in PPPoE - No Connection - UK



  • Hi,

    I've been trying to get my new Fiber connection working all day but have had no luck.
    It works ok with the TalkTalk router.
    The pfSense box was previously connected to an ADSL modem in half-bridge mode using PPPoE.
    Talk Talk apparently doesn't need a username and password for PPPoE so I have entered talktalk in both to keep pfSense happy.
    I called their automated password service which provides username and password and it confirmed that no username or password is required for TalkTalk fiber.

    I've tried rebooting the modem and the pfSense box with no change.
    I also deleted the interfaces 'PPPs' connections which were there and tried to re-configure the PPPoE connection again.

    I also tried using both a crossover cable and a standard network cable with no change.

    Can anyone help me with this please?

    ppp log:

    ppp: [wan_link0] PPPoE: Connecting to ''
    Sep 13 21:11:05	ppp: PPPoE: rec'd ACNAME "npe001.car-B22"
    Sep 13 21:11:05	ppp: [wan_link0] PPPoE: connection successful
    Sep 13 21:11:05	ppp: [wan_link0] Link: UP event
    Sep 13 21:11:05	ppp: [wan_link0] LCP: Up event
    Sep 13 21:11:05	ppp: [wan_link0] LCP: state change Starting --> Req-Sent
    Sep 13 21:11:05	ppp: [wan_link0] LCP: SendConfigReq #82
    Sep 13 21:11:05	ppp: [wan_link0] PROTOCOMP
    Sep 13 21:11:05	ppp: [wan_link0] MRU 1492
    Sep 13 21:11:05	ppp: [wan_link0] MAGICNUM fb69ed38
    Sep 13 21:11:05	ppp: [wan_link0] LCP: rec'd Configure Request #111 (Req-Sent)
    Sep 13 21:11:05	ppp: [wan_link0] MRU 1492
    Sep 13 21:11:05	ppp: [wan_link0] AUTHPROTO CHAP MD5
    Sep 13 21:11:05	ppp: [wan_link0] MAGICNUM 331a3329
    Sep 13 21:11:05	ppp: [wan_link0] LCP: SendConfigAck #111
    Sep 13 21:11:05	ppp: [wan_link0] MRU 1492
    Sep 13 21:11:05	ppp: [wan_link0] AUTHPROTO CHAP MD5
    Sep 13 21:11:05	ppp: [wan_link0] MAGICNUM 331a3329
    Sep 13 21:11:05	ppp: [wan_link0] LCP: state change Req-Sent --> Ack-Sent
    Sep 13 21:11:05	ppp: [wan_link0] LCP: rec'd Configure Reject #82 (Ack-Sent)
    Sep 13 21:11:05	ppp: [wan_link0] PROTOCOMP
    Sep 13 21:11:05	ppp: [wan_link0] LCP: SendConfigReq #83
    Sep 13 21:11:05	ppp: [wan_link0] MRU 1492
    Sep 13 21:11:05	ppp: [wan_link0] MAGICNUM fb69ed38
    Sep 13 21:11:05	ppp: [wan_link0] LCP: rec'd Configure Ack #83 (Ack-Sent)
    Sep 13 21:11:05	ppp: [wan_link0] MRU 1492
    Sep 13 21:11:05	ppp: [wan_link0] MAGICNUM fb69ed38
    Sep 13 21:11:05	ppp: [wan_link0] LCP: state change Ack-Sent --> Opened
    Sep 13 21:11:05	ppp: [wan_link0] LCP: auth: peer wants CHAP, I want nothing
    Sep 13 21:11:05	ppp: [wan_link0] LCP: LayerUp
    Sep 13 21:11:05	ppp: [wan_link0] CHAP: rec'd CHALLENGE #1 len: 31
    Sep 13 21:11:05	ppp: [wan_link0] Name: "npe001.car"
    Sep 13 21:11:05	ppp: [wan_link0] CHAP: Using authname "talktalk"
    Sep 13 21:11:05	ppp: [wan_link0] CHAP: sending RESPONSE #1 len: 29
    Sep 13 21:11:05	ppp: [wan_link0] CHAP: rec'd FAILURE #1 len: 43
    Sep 13 21:11:05	ppp: [wan_link0] MESG: CHAP authentication failure, unit 23546
    Sep 13 21:11:05	ppp: [wan_link0] LCP: authorization failed
    Sep 13 21:11:05	ppp: [wan_link0] LCP: parameter negotiation failed
    Sep 13 21:11:05	ppp: [wan_link0] LCP: state change Opened --> Stopping
    Sep 13 21:11:05	ppp: [wan_link0] LCP: SendTerminateReq #84
    Sep 13 21:11:05	ppp: [wan_link0] LCP: LayerDown
    Sep 13 21:11:05	ppp: [wan_link0] LCP: rec'd Terminate Request #112 (Stopping)
    Sep 13 21:11:05	ppp: [wan_link0] LCP: SendTerminateAck #85
    Sep 13 21:11:06	ppp: [wan_link0] PPPoE: connection closed
    Sep 13 21:11:06	ppp: [wan_link0] Link: DOWN event
    Sep 13 21:11:06	ppp: [wan_link0] LCP: Down event
    Sep 13 21:11:06	ppp: [wan_link0] LCP: state change Stopping --> Starting
    Sep 13 21:11:06	ppp: [wan_link0] Link: reconnection attempt 22 in 3 seconds
    

    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 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 "talktalk"
            set auth password talktalk
            set pppoe service ""
            set pppoe iface vr0
            open^M
    

  • Netgate Administrator

    What modem do Talktalk provide?
    Do you need to enter a service name?

    Can you check to see what credentials the talktalk router sends?

    Can edit the authname to "" ?

    Steve



  • Hi,
    Thanks for replying.
    Talk Talk provide a router. I have a D-Link DSL-3780.
    The telecoms engineer provided the modem - HG612 Huawei branded BT openreach.
    I downloaded a backup of the rom file from the router via the gui and there doesn't appear to be any authentification, other than for ADSL use.
    I don't see a service name either.
    I've tried the ADSL details but without any change.
    I changed the authname to "" but it still doesn't connect.


  • Netgate Administrator

    Hmm, do the logs show it trying to connect with ""?

    It's hard to know quite what to expect here, perhaps hit a talktalk forum to find out what other people are doing.

    I have a FTTC connection from BT also using the HG612 modem. I lifted the username from the BT supplied homehub, it's the same for all homehubs, and used a random password. Connected no problems. However although talktalk will be using a lot Openreach's equipment they probably have their own authentication servers so your connection setup would differ.

    default:
    pppoeclient:
    	create bundle static opt4
    	set iface name pppoe1
    	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
    	#log -bund -ccp -chat -iface -ipcp -lcp -link
    
    	create link static opt4_link0 pppoe
    	set link action bundle opt4
    	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 "bthomehub@btbroadband.com"
    	set auth password 1234
    	set pppoe service "BTInfinity"
    	set pppoe iface fxp5
    	open
    
    

    Steve



  • Out of interest, did you get this fixed?
    It sounds like it's a similar problem to http://status.aa.net.uk/1854 - there isn't much on that page, more will be added soon (I work for A&A). Also related is http://community.plus.net/forum/?topic=119045.msg1031260


  • Netgate Administrator

    Ah, interesting. Thanks for those links.
    If I wasn't already with Plusnet I'd probably be with A&A. Your reputation for supporting technically aware users precedes you.  ;)

    This issue clearly predates any recent firmware updates so I don't believe it's related. Not sure about the tunnel though. How does that function in the firebrick? Do A&A terminate that tunnel? I wasn't aware that Talktalk did anything like that.

    Steve



  • OK, maybe it's not related :-)

    We're doing more testing at the moment, and hope to get some more info up on out status page about it later today. The problem isn't tunnel specific, we're sending UDP packets and can reproduce the problem of packets not getting through.


Log in to reply