cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1381
Views
0
Helpful
9
Replies

BT Infinity with 887VA

Steve Ashton
Level 1
Level 1

Hi

I have a new 887VA this router works with BT Infinity on my companies line but does work on my home line although it is a BT Business account.

I currently use a RV220 with the BT white modem box but I intend to replace it with the Cisco 887VA replacing both the white modem and the RV220.

I currently run this config:

 description **BT INFINITY**
 mtu 1492
 ip address negotiated
 no ip redirects
 no ip unreachables
 no ip proxy-arp
 ip nbar protocol-discovery
 ip flow ingress
 ip nat outside
 ip virtual-reassembly in
 encapsulation ppp
 ip tcp adjust-mss 1452
 dialer pool 1
 dialer idle-timeout 0
 dialer-group 1
 keepalive 30
 ppp authentication chap pap callin
 ppp chap hostname REDACTED@hg39.btclick.com
 ppp chap password 0 REDACTED             
 ppp pap sent-username REDACTED@hg39.btclick.com password 0 REDACTED
 ppp ipcp dns request
 ppp ipcp mask request
 ppp ipcp route default
 ppp ipcp address accept
 no cdp enable

I know these login credentials work because I am using them in the RV220 the debug logs produce this, which seems to be authentication problems, I have tried pap chap, pap on it's own, chap on it's own, any ideas what I'm doing wrong

*Dec 14 09:42:10.460: %DIALER-6-BIND: Interface Vi2 bound to profile Di1
*Dec 14 09:42:10.464: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
*Dec 14 09:42:10.464: Vi2 PPP: Sending cstate UP notification
*Dec 14 09:42:10.464: Vi2 PPP: Processing CstateUp message
*Dec 14 09:42:10.464: PPP: Alloc Context [E7E8D0C]
*Dec 14 09:42:10.464: ppp13 PPP: Phase is ESTABLISHING
*Dec 14 09:42:10.464: Vi2 PPP: Using dialer call direction
*Dec 14 09:42:10.464: Vi2 PPP: Treating connection as a callout
*Dec 14 09:42:10.464: Vi2 PPP: Session handle[100000D] Session id[13]
*Dec 14 09:42:10.464: Vi2 LCP: Event[OPEN] State[Initial to Starting]
*Dec 14 09:42:10.464: Vi2 PPP: No remote authentication for call-out
*Dec 14 09:42:10.464: Vi2 LCP: O CONFREQ [Starting] id 1 len 14
*Dec 14 09:42:10.464: Vi2 LCP:    MRU 1492 (0x010405D4)
*Dec 14 09:42:10.464: Vi2 LCP:    MagicNumber 0xF3B2C439 (0x0506F3B2C439)
*Dec 14 09:42:10.464: Vi2 LCP: Event[UP] State[Starting to REQsent]
*Dec 14 09:42:10.504: Vi2 LCP: I CONFREQ [REQsent] id 158 len 19
*Dec 14 09:42:10.504: Vi2 LCP:    MRU 1492 (0x010405D4)
*Dec 14 09:42:10.504: Vi2 LCP:    AuthProto CHAP (0x0305C22305)
*Dec 14 09:42:10.504: Vi2 LCP:    MagicNumber 0x78201854 (0x050678201854)
*Dec 14 09:42:10.504: Vi2 LCP: O CONFACK [REQsent] id 158 len 19
*Dec 14 09:42:10.504: Vi2 LCP:    MRU 1492 (0x010405D4)
*Dec 14 09:42:10.504: Vi2 LCP:    AuthProto CHAP (0x0305C22305)
*Dec 14 09:42:10.504: Vi2 LCP:    MagicNumber 0x78201854 (0x050678201854)
*Dec 14 09:42:10.504: Vi2 LCP: Event[Receive ConfReq+] State[REQsent to ACKsent]
*Dec 14 09:42:10.508: Vi2 LCP: I CONFACK [ACKsent] id 1 len 14
*Dec 14 09:42:10.508: Vi2 LCP:    MRU 1492 (0x010405D4)
*Dec 14 09:42:10.508: Vi2 LCP:    MagicNumber 0xF3B2C439 (0x0506F3B2C439)
*Dec 14 09:42:10.508: Vi2 LCP: Event[Receive ConfAck] State[ACKsent to Open]
*Dec 14 09:42:10.520: Vi2 PPP: Queue CHAP code[1] id[1]
*Dec 14 09:42:10.528: Vi2 PPP: Phase is AUTHENTICATING, by the peer
*Dec 14 09:42:10.528: Vi2 CHAP: Redirect packet to Vi2
*Dec 14 09:42:10.528: Vi2 CHAP: I CHALLENGE id 1 len 68 from "acc-aln1.hil"
*Dec 14 09:42:10.528: Vi2 PPP: Sent CHAP SENDAUTH Request
*Dec 14 09:42:10.528: Vi2 LCP: State is Open
*Dec 14 09:42:10.528: Vi2 PPP: Received SENDAUTH Response FAIL
*Dec 14 09:42:10.528: Vi2 CHAP: Using hostname from interface CHAP
*Dec 14 09:42:10.528: Vi2 CHAP: Using password from interface CHAP
*Dec 14 09:42:10.528: Vi2 CHAP: O RESPONSE id 1 len 45 from "REDACTED@hg39.btclick.com"
*Dec 14 09:42:10.628: Vi2 CHAP: I FAILURE id 1 len 31 msg is "CHAP authentication failure"
*Dec 14 09:42:10.628: Vi2 PPP DISC: We failed authentication
*Dec 14 09:42:10.628: Vi2 PPP: Sending Acct Event[Down] id[1A]
*Dec 14 09:42:10.628: PPP: NET STOP send to AAA.
*Dec 14 09:42:10.628: Vi2 LCP: I TERMREQ [Open] id 159 len 4
*Dec 14 09:42:10.628: Vi2 PPP: Phase is TERMINATING
*Dec 14 09:42:10.628: Vi2 LCP: O TERMACK [Open] id 159 len 4
*Dec 14 09:42:10.628: Vi2 LCP: Event[Receive TermReq] State[Open to Stopping]
*Dec 14 09:42:10.648: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up
*Dec 14 09:42:10.648: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di1
*Dec 14 09:42:10.648: Vi2 PPP: Block vaccess from being freed [0x10]
*Dec 14 09:42:10.648: Vi2 LCP: Event[DOWN] State[Stopping to Starting]
*Dec 14 09:42:10.648: Vi2 PPP: Unlocked by [0x10] Still Locked by [0x0]
*Dec 14 09:42:10.648: Vi2 PPP: Free previously blocked vaccess
*Dec 14 09:42:10.648: Vi2 PPP: Phase is DOWN
*Dec 14 09:42:10.652: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down
*Dec 14 09:42:10.652: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down
*Dec 14 09:42:32.780: %DIALER-6-BIND: Interface Vi2 bound to profile Di1
*Dec 14 09:42:32.788: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
*Dec 14 09:42:32.788: Vi2 PPP: Sending cstate UP notification
*Dec 14 09:42:32.788: Vi2 PPP: Processing CstateUp message
*Dec 14 09:42:32.788: PPP: Alloc Context [E7E8D0C]
*Dec 14 09:42:32.788: ppp14 PPP: Phase is ESTABLISHING
*Dec 14 09:42:32.788: Vi2 PPP: Using dialer call direction
*Dec 14 09:42:32.788: Vi2 PPP: Treating connection as a callout
*Dec 14 09:42:32.788: Vi2 PPP: Session handle[7F00000E] Session id[14]
*Dec 14 09:42:32.788: Vi2 LCP: Event[OPEN] State[Initial to Starting]
*Dec 14 09:42:32.788: Vi2 PPP: No remote authentication for call-out
*Dec 14 09:42:32.788: Vi2 LCP: O CONFREQ [Starting] id 1 len 14
*Dec 14 09:42:32.788: Vi2 LCP:    MRU 1492 (0x010405D4)
*Dec 14 09:42:32.788: Vi2 LCP:    MagicNumber 0xF3B31B7B (0x0506F3B31B7B)
*Dec 14 09:42:32.788: Vi2 LCP: Event[UP] State[Starting to REQsent]
*Dec 14 09:42:32.828: Vi2 LCP: I CONFREQ [REQsent] id 163 len 19
*Dec 14 09:42:32.828: Vi2 LCP:    MRU 1492 (0x010405D4)
*Dec 14 09:42:32.828: Vi2 LCP:    AuthProto CHAP (0x0305C22305)
*Dec 14 09:42:32.828: Vi2 LCP:    MagicNumber 0x25F4EBA1 (0x050625F4EBA1)
*Dec 14 09:42:32.828: Vi2 LCP: O CONFACK [REQsent] id 163 len 19
*Dec 14 09:42:32.828: Vi2 LCP:    MRU 1492 (0x010405D4)
*Dec 14 09:42:32.828: Vi2 LCP:    AuthProto CHAP (0x0305C22305)
*Dec 14 09:42:32.828: Vi2 LCP:    MagicNumber 0x25F4EBA1 (0x050625F4EBA1)
*Dec 14 09:42:32.828: Vi2 LCP: Event[Receive ConfReq+] State[REQsent to ACKsent]
*Dec 14 09:42:32.828: Vi2 LCP: I CONFACK [ACKsent] id 1 len 14
*Dec 14 09:42:32.828: Vi2 LCP:    MRU 1492 (0x010405D4)
*Dec 14 09:42:32.828: Vi2 LCP:    MagicNumber 0xF3B31B7B (0x0506F3B31B7B)
*Dec 14 09:42:32.828: Vi2 LCP: Event[Receive ConfAck] State[ACKsent to Open]
*Dec 14 09:42:32.832: Vi2 PPP: Phase is AUTHENTICATING, by the peer
*Dec 14 09:42:32.832: Vi2 LCP: State is Open
*Dec 14 09:42:32.844: Vi2 CHAP: I CHALLENGE id 1 len 52 from "acc-aln1.hil"
*Dec 14 09:42:32.844: Vi2 PPP: Sent CHAP SENDAUTH Request
*Dec 14 09:42:32.844: Vi2 PPP: Received SENDAUTH Response FAIL
*Dec 14 09:42:32.844: Vi2 CHAP: Using hostname from interface CHAP
*Dec 14 09:42:32.844: Vi2 CHAP: Using password from interface CHAP
*Dec 14 09:42:32.844: Vi2 CHAP: O RESPONSE id 1 len 45 from "REDACTED@hg39.btclick.com"
*Dec 14 09:42:32.928: Vi2 CHAP: I FAILURE id 1 len 31 msg is "CHAP authentication failure"
*Dec 14 09:42:32.928: Vi2 PPP DISC: We failed authentication
*Dec 14 09:42:32.928: Vi2 PPP: Sending Acct Event[Down] id[1B]
*Dec 14 09:42:32.928: PPP: NET STOP send to AAA.
*Dec 14 09:42:32.928: Vi2 LCP: I TERMREQ [Open] id 164 len 4
*Dec 14 09:42:32.928: Vi2 PPP: Phase is TERMINATING
*Dec 14 09:42:32.932: Vi2 LCP: O TERMACK [Open] id 164 len 4
*Dec 14 09:42:32.932: Vi2 LCP: Event[Receive TermReq] State[Open to Stopping]
*Dec 14 09:42:32.948: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up
*Dec 14 09:42:32.948: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di1
*Dec 14 09:42:32.948: Vi2 PPP: Block vaccess from being freed [0x10]
*Dec 14 09:42:32.948: Vi2 LCP: Event[DOWN] State[Stopping to Starting]
*Dec 14 09:42:32.948: Vi2 PPP: Unlocked by [0x10] Still Locked by [0x0]
*Dec 14 09:42:32.948: Vi2 PPP: Free previously blocked vaccess
*Dec 14 09:42:32.948: Vi2 PPP: Phase is DOWN
*Dec 14 09:42:32.952: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down
*Dec 14 09:42:32.952: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down

 

 

9 Replies 9

timweldo
Level 1
Level 1

Steve,

I have the same router on BT Infinity Business, without any issues. Your dialer config is practically the same as mine except I don't have these lines:

no ip redirects
no ip unreachables
no ip proxy-arp
ip nbar protocol-discovery

ppp ipcp mask request
ppp ipcp address accept

Presumably you've got int E0 and int E0.101 configured correctly for the pppoe?

Tim

Tim this is my E0 and E0.101

interface Ethernet0
 no ip address
!
interface Ethernet0.101
 encapsulation dot1Q 101
 pppoe enable group global
 pppoe-client dial-pool-number 1
!

 

Steve,

eo and .101 look fine

under the dialer interface, get rid of:

ppp pap sent-username REDACTED@hg39.btclick.com password 0 REDACTED

and change :

ppp authentication chap pap callin

to

ppp authentication chap callin

HTH

Tim

I think I've tried this change, but I'll give it a whirl again and produce logs.

 

It would be interesting to see your debug ppp nego and debug ppp authen so I could compare it to mine looking at the log

hase is AUTHENTICATING, by the peer
*Dec 14 09:42:10.528: Vi2 CHAP: Redirect packet to Vi2
*Dec 14 09:42:10.528: Vi2 CHAP: I CHALLENGE id 1 len 68 from "acc-aln1.hil"
*Dec 14 09:42:10.528: Vi2 PPP: Sent CHAP SENDAUTH Request
*Dec 14 09:42:10.528: Vi2 LCP: State is Open
*Dec 14 09:42:10.528: Vi2 PPP: Received SENDAUTH Response FAIL
*Dec 14 09:42:10.528: Vi2 CHAP: Using hostname from interface CHAP
*Dec 14 09:42:10.528: Vi2 CHAP: Using password from interface CHAP
*Dec 14 09:42:10.528: Vi2 CHAP: O RESPONSE id 1 len 45 from "REDACTED@hg39.btclick.com"
*Dec 14 09:42:10.628: Vi2 CHAP: I FAILURE id 1 len 31 msg is "CHAP authentication failure"

It would suggest my credentials are wrong yet, I have checked and even used the same credentials on my RV220 which works a treat, although the only difference is the RV220 works through the white modem.

 

ghostinthenet
Level 7
Level 7

Are you using this PPPoE account simultaneously at any other location? Many ISPs will limit connections to a single instance and fail authentication for any subsequent ones.

No this is the only PPPoE account at this location.

 

Are the same credentials bein used at any other location? If so, that still counts as multiple logins to the same system. Our ISPs here allow for up to two, but BT may be more restrictive.

Amit Goyal
Level 1
Level 1

Hi Steve,

For sure this is failing at authentication phase.

ISP is using CHAP hence PAP is not required.

*Dec 14 09:42:32.828: Vi2 LCP: I CONFREQ [REQsent] id 163 len 19<<Inbound
*Dec 14 09:42:32.828: Vi2 LCP:    MRU 1492 (0x010405D4)
*Dec 14 09:42:32.828: Vi2 LCP:    AuthProto CHAP (0x0305C22305)
<<<<

Can you please try following?

1. Remove below commands from the config.

 ppp authentication chap pap callin
 ppp chap hostname REDACTED@hg39.btclick.com
 ppp chap password 0 REDACTED   

2. Add

ppp chap hostname <please type the string and do not use copy/paste>

ppp chap password <please type the string and do not use copy/paste>

HTH

-Amit

 

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: