PPPoE connection problem: don´t receive PADS

sluangsay · ‎04-05-2011

Hi,

I am new to Cisco and to network issues so please excuse me if I may say irrelevant stuffs or information.

I have an issue to establish an internet access between my router 887V and my ISP Jazztel that provides me an VDSL connection.

I believe that this is not an ISP issue because I manage to get internet if I use the Comtrend router that gave me Jazztel.

Here is how I configured the router for the WAN parts (I´ll paste later the whole configuration):

interface Ethernet0
description $ETH-WAN$
no ip address
pppoe-client dial-pool-number 1
!

interface Dialer0
ip address negotiated
ip mtu 1452
encapsulation ppp
dialer pool 1
dialer-group 1
ppp authentication chap pap callin
ppp chap hostname myuser
ppp chap password 0 mypassword
ppp pap sent-username myuser password 0 mypassword
no cdp enable

Enabling logs, I can see the following pppoe packets been sent: PADI, PADO, PADR and PADT.

For what I understand from PPPoE, server should send to my router a PADS packet, shouldn´t it?

Another problem that bothers me is the following message I get:

"PPPoe: Unsolicited PADO, Invalid session state"

Here are the whole logs I receive:

*Mar 31 12:57:59.390: Sending PADI: Interface = Ethernet0
*Mar 31 12:57:59.390: pppoe_send_padi:
contiguous pak, size 60
         FF FF FF FF FF FF 50 3D E5 0B 3F 8E 88 63 11 09
         00 00 00 10 01 01 00 00 01 03 00 08 5B 00 00 01
         00 00 19 7A 00 00 00 00 00 00 00 00 00 00 00 00
         00 00 00 00 00 00 00 00 00 00 00 00
*Mar 31 12:58:01.438: PPPOE: we've got our pado and the pado timer went off
*Mar 31 12:58:01.438: OUT PADR from PPPoE Session
contiguous pak, size 60
         00 25 9E 5E 20 E0 50 3D E5 0B 3F 8E 88 63 11 19
         00 00 00 20 01 01 00 00 01 03 00 08 5B 00 00 01
         00 00 19 7A 01 02 00 0C 52 41 53 30 31 2D 48 4D
         41 44 30 31 00 00 00 00 00 00 00 00
*Mar 31 12:58:01.482: %DIALER-6-BIND: Interface Vi1 bound to profile Di1
*Mar 31 12:58:01.482: PPPoE: Virtual Access interface obtained.
*Mar 31 12:58:01.482: PPPoE : encap string prepared
contiguous pak, size 20
         00 25 9E 5E 20 E0 50 3D E5 0B 3F 8E 88 64 11 00
         52 AF 00 00
*Mar 31 12:58:01.482: [0]PPPoE 21167: data path set to PPPoE Client
*Mar 31 12:58:01.486: %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to up
*Mar 31 12:58:01.486: [0]PPPoE 21167: O
contiguous pak, size 12
         C0 21 01 01 00 0A 05 06 3E DB 65 90
*Mar 31 12:58:01.522: [0]PPPoE 21167: I R:0025.9e5e.20e0 L:503d.e50b.3f8e Et0
particle pak, size 12
         C0 21 02 01 00 0A 05 06 3E DB 65 90
*Mar 31 12:58:02.446: PPPoe: Unsolicited PADO, Invalid session state
*Mar 31 12:58:03.474: [0]PPPoE 21167: O
contiguous pak, size 12
         C0 21 01 02 00 0A 05 06 3E DB 65 90
*Mar 31 12:58:03.506: [0]PPPoE 21167: I R:0025.9e5e.20e0 L:503d.e50b.3f8e Et0
particle pak, size 12
         C0 21 02 02 00 0A 05 06 3E DB 65 90
*Mar 31 12:58:04.462: [0]PPPoE 21167: I R:0025.9e5e.20e0 L:503d.e50b.3f8e Et0
particle pak, size 21
         C0 21 01 01 00 13 01 04 05 D4 03 05 C2 23 05 05
         06 02 00 4B 50
*Mar 31 12:58:04.462: [0]PPPoE 21167: O
contiguous pak, size 10
         C0 21 03 01 00 08 01 04 05 DC
*Mar 31 12:58:04.498: [0]PPPoE 21167: I R:0025.9e5e.20e0 L:503d.e50b.3f8e Et0
particle pak, size 21

         C0 21 01 02 00 13 01 04 05 DC 03 05 C2 23 05 05
         06 02 00 4B 50
*Mar 31 12:58:04.498: [0]PPPoE 21167: O
contiguous pak, size 21
         C0 21 02 02 00 13 01 04 05 DC 03 05 C2 23 05 05
         06 02 00 4B 50
*Mar 31 12:58:04.534: [0]PPPoE 21167: I R:0025.9e5e.20e0 L:503d.e50b.3f8e Et0
particle pak, size 23
         C2 23 01 01 00 15 10 31 80 1C B7 99 C0 67 34 A0
         0A 33 C7 C1 17 37 7E
*Mar 31 12:58:04.534: [0]PPPoE 21167: O
contiguous pak, size 38
         C2 23 02 01 00 24 10 6B 2F 9C 49 1B 60 54 C4 20
         D1 DC 46 21 03 FA 3A 6F 7A 69 63 31 38 37 30 40
         61 64 73 6C 69 70
*Mar 31 12:58:04.646: [0]PPPoE 21167: I R:0025.9e5e.20e0 L:503d.e50b.3f8e Et0
particle pak, size 6
         C2 23 03 01 00 04
*Mar 31 12:58:04.646: [0]PPPoE 21167: I R:0025.9e5e.20e0 L:503d.e50b.3f8e Et0
particle pak, size 12
         80 21 01 01 00 0A 03 06 57 D8 10 01
*Mar 31 12:58:04.646: [0]PPPoE 21167: O
contiguous pak, size 6
         C0 21 05 03 00 04
*Mar 31 12:58:04.646: PPPoE : Shutting down client session
*Mar 31 12:58:04.646: [0]PPPoE 21167: O PADT R:0025.9e5e.20e0 L:503d.e50b.3f8e Et0
contiguous pak, size 60
         00 25 9E 5E 20 E0 50 3D E5 0B 3F 8E 88 63 11 A7
         52 AF 00 00 00 00 00 00 00 00 00 00 00 00 00 00
         00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
         00 00 00 00 00 00 00 00 00 00 00 00
*Mar 31 12:58:04.650: PPPoE: Failed to add PPPoE switching subblock
*Mar 31 12:58:04.650: %DIALER-6-UNBIND: Interface Vi1 unbound from profile Di1
*Mar 31 12:58:04.654: %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to down
*Mar 31 12:58:04.654: PPPoE: Unexpected Event!. PPPoE switching Subblockdestroy called

And my configuration is the following one:

yourname#sh startup-config
Using 2432 out of 262136 bytes
!
! Last configuration change at 08:36:02 UTC Thu Mar 31 2011 by admin
!
version 15.1
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname yourname
!
boot-start-marker
boot-end-marker
!
!
logging buffered 51200 warnings
enable secret 5 $1$ToUQ$SrGRlQyP0wEn6l.eTe4zP.
enable password cisco
!
no aaa new-model
memory-size iomem 10
crypto pki token default removal timeout 0
!
crypto pki trustpoint TP-self-signed-1273694396
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-1273694396
revocation-check none
!
!
crypto pki certificate chain TP-self-signed-1273694396
certificate self-signed 01 nvram:IOS-Self-Sig#2.cer
ip source-route
!
!
!
ip dhcp excluded-address 10.10.10.1
!
ip dhcp pool ccp-pool
   import all
   network 10.10.10.0 255.255.255.248
   default-router 10.10.10.1
   lease 0 2
!
!
ip cef
no ip domain lookup
ip domain name yourdomain.com
no ipv6 cef
!
!
license udi pid CISCO887V-K9 sn FCZ1504CD2K
!
!
username admin privilege 15 secret 5 $1$1kEz$uax1SvwP6MV6Xkq18oKHu0
username sourygna privilege 0 view root secret 5 $1$l.m6$AXs9q0e.jRB0w3DMKGbk6.
!
!
!
!
controller VDSL 0
!
!
!
!
!
!
!
!
interface Ethernet0
description $ETH-WAN$
no ip address
pppoe-client dial-pool-number 1
!
interface BRI0
no ip address
encapsulation hdlc
shutdown
isdn termination multidrop
!
interface FastEthernet0
!
interface FastEthernet1
!
interface FastEthernet2

!
interface FastEthernet3
!
interface Vlan1
description $ETH-SW-LAUNCH$$INTF-INFO-HWIC 4ESW$
ip address 10.10.10.1 255.255.255.248
ip tcp adjust-mss 1412
!
interface Dialer0
ip address negotiated
ip mtu 1452
encapsulation ppp
dialer pool 1
dialer-group 1
ppp authentication chap pap callin
ppp chap hostname xxxx
ppp chap password 0 xxxx
ppp pap sent-username xxxx password 0 xxxxx
no cdp enable
!
ip forward-protocol nd
ip http server
ip http access-class 23
ip http authentication local
ip http secure-server
ip http timeout-policy idle 60 life 86400 requests 10000
!
ip route 0.0.0.0 0.0.0.0 Dialer0
!
logging esm config
access-list 23 permit 10.10.10.0 0.0.0.7
dialer-list 1 protocol ip permit
no cdp run

!
!
!
!
!
control-plane
!
banner exec ^C^C
banner login ^C^C
!
line con 0
login local
no modem enable
line aux 0
line vty 0 4
access-class 23 in
privilege level 15
login local
transport input telnet ssh
!
end

Any hint would be greatly appreciated.

Regards,

Sluan

paolo bevilacqua · ‎04-05-2011

Take "debug ppp negotiation" and "debug ppp authentication".

Note, IP MTU must be 1492, not 1452, that is mss-adjust value.

sluangsay · ‎04-05-2011

Hi Paolo,

Thanks, I have just changed MTU to 1492.

I have also activated "debug ppp negotiation" and "debug ppp authentication" but it shows me no log/message.

The only warning I got is the one I mentioned before:

yourname#
*Apr 5 13:29:28.292: %DIALER-6-BIND: Interface Vi1 bound to profile Di0
*Apr 5 13:29:28.296: %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to up
*Apr 5 13:29:31.484: %DIALER-6-UNBIND: Interface Vi1 unbound from profile Di0
*Apr 5 13:29:31.488: %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to down
yourname#

(I previously removed pppoe debug)

Sluan

paolo bevilacqua · ‎04-05-2011

Possibly the VDSL router is not set correctly for bridge mode , as no PPPoE packets are received by the Cisco.

sluangsay · ‎04-05-2011

Hi Paolo,

I feel a bit confused. Do I really need to set the router in "bridge mode"?

I though it should be in router mode since I intend to do NAT. Can´t it work in "router mode"?

As for PPPoE, I think the Cisco router receives some PPPoE packets (PADO is a packet I receive from my ISP, isn´t it?).

Could it be that I don´t receive any PPP packet (thus seeing nothing with "debug ppp *") because PPPoE discovery isn´t completed (I mean: my

router should receive the PADS packet)?

paolo bevilacqua · ‎04-05-2011

You need to set the VDSL router as pure bridge. Not the Cisco.

gersoto · ‎04-05-2011

Sluan,

You are right. The router is not getting a PADS packet from the ISP router. You want to engage your ISP to check what's going on on their side. Show them the outputs you attached to this post.

PPP won't kick in until PPPoE receives a PADS and a PPPoE session gets established "show pppoe session"

Do you have a VDSL modem to test connectivity with it? If you don't, configure the Cisco router as dumb bridge, then plug a Windows XP computer on the LAN interface and run Window's PPPoE wizard (New connection Wizard). If you get connectivity on the PC then we can tell the problem is specific to the Cisco's PPPoE client functionality and you should open a TAC case for that.

Dumb bridge configuration:

Ethernet interface (WAN)

bridge-group 1

no pppoe-client dial-pool-number 1

VLAN interface (LAN)

bridge-group 1

Global config:

no ip routing

bridge 1 protocol ieee

paolo bevilacqua · ‎04-05-2011

gersoto wrote:

Do you have a VDSL modem to test connectivity with it? If you don't, configure the Cisco router as dumb bridge, then plug a Windows XP computer on the LAN interface and run Window's PPPoE wizard (New connection Wizard). If you get connectivity on the PC then we can tell the problem is specific to the Cisco's PPPoE client functionality and you should open a TAC case for that.

There is no need to configure Cisco as bridge in order to test PPPoE with a PC. Just connect the PC Ethernet to the ISP modem/bridge Ethernet.