PPPOE Client with VLAN7 - Deutsche Telekom Viperoptic

General questions
1

I have the problem that I cannot establish a PPPOE connection on eth5 with vlan7. Here as first the Config.

show interfaces ethernet eth5
hw-id 40:62:31:0c:0f:1d
vif 7 {
description Internet_Telekom
}

show interfaces pppoe pppoe1
authentication {
password xxxxxxxxxx
user xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx#0001@t-online.de
}
default-route none
source-interface eth5.7

So very simple Config.

Now the log file:

Jan 22 15:12:21 ml-koenigsheide-120 pppd[12616]: Send PPPOE Discovery V1T1 PADT session 0x2951 length 20
Jan 22 15:12:21 ml-koenigsheide-120 pppd[12616]: dst 28:8a:1c:5b:d8:83 src 40:62:31:0c:0f:1d
Jan 22 15:12:21 ml-koenigsheide-120 pppd[12616]: [AC-cookie c1 54 0b 41 ae 3f 09 47 41 c2 b0 73 3c ea bd e7]
Jan 22 15:12:21 ml-koenigsheide-120 pppd[12616]: Sent PADT
Jan 22 15:12:51 ml-koenigsheide-120 pppd[12616]: Send PPPOE Discovery V1T1 PADI session 0x0 length 4
Jan 22 15:12:51 ml-koenigsheide-120 pppd[12616]: dst ff:ff:ff:ff:ff:ff src 40:62:31:0c:0f:1d
Jan 22 15:12:51 ml-koenigsheide-120 pppd[12616]: [service-name]
Jan 22 15:12:56 ml-koenigsheide-120 pppd[12616]: Send PPPOE Discovery V1T1 PADI session 0x0 length 4
Jan 22 15:12:56 ml-koenigsheide-120 pppd[12616]: dst ff:ff:ff:ff:ff:ff src 40:62:31:0c:0f:1d
Jan 22 15:12:56 ml-koenigsheide-120 pppd[12616]: [service-name]
Jan 22 15:13:06 ml-koenigsheide-120 pppd[12616]: Send PPPOE Discovery V1T1 PADI session 0x0 length 4
Jan 22 15:13:06 ml-koenigsheide-120 pppd[12616]: dst ff:ff:ff:ff:ff:ff src 40:62:31:0c:0f:1d
Jan 22 15:13:06 ml-koenigsheide-120 pppd[12616]: [service-name]
Jan 22 15:13:26 ml-koenigsheide-120 pppd[12616]: Timeout waiting for PADO packets
Jan 22 15:13:26 ml-koenigsheide-120 pppd[12616]: Unable to complete PPPoE Discovery
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: Send PPPOE Discovery V1T1 PADI session 0x0 length 4
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: dst ff:ff:ff:ff:ff:ff src 40:62:31:0c:0f:1d
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: [service-name]
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: Recv PPPOE Discovery V1T1 PADO session 0x0 length 34
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: dst 40:62:31:0c:0f:1d src 28:8a:1c:5b:d8:83
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: [AC-name FFMJ09] [service-name] [AC-cookie c1 54 0b 41 ae 3f 09 47 41 c2 b0 73 3c ea bd e7]
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: Send PPPOE Discovery V1T1 PADR session 0x0 length 24
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: dst 28:8a:1c:5b:d8:83 src 40:62:31:0c:0f:1d
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: [service-name] [AC-cookie c1 54 0b 41 ae 3f 09 47 41 c2 b0 73 3c ea bd e7]
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: Recv PPPOE Discovery V1T1 PADS session 0x2951 length 34
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: dst 40:62:31:0c:0f:1d src 28:8a:1c:5b:d8:83
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: [service-name] [AC-name FFMJ09] [AC-cookie c1 54 0b 41 ae 3f 09 47 41 c2 b0 73 3c ea bd e7]
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: PADS: Service-Name: ‘’
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: PPP session is 10577
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: Connected to 28:8a:1c:5b:d8:83 via interface eth5.7
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: using channel 20
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: Renamed interface ppp0 to pppoe1
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: Using interface pppoe1
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: Connect: pppoe1 ↔ eth5.7
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: sent [LCP ConfReq id=0x1f <mru 1492> <magic 0xe3177110>]
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: rcvd [LCP ConfReq id=0xba <mru 1492> <magic 0x40f5f456>]
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: sent [LCP ConfAck id=0xba <mru 1492> <magic 0x40f5f456>]
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: rcvd [LCP ConfAck id=0x1f <mru 1492> <magic 0xe3177110>]
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: sent [LCP EchoReq id=0x0 magic=0xe3177110]
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: sent [PAP AuthReq id=0x10 user=“xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx” password=]
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: rcvd [LCP EchoRep id=0x0 magic=0x40f5f456]
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: rcvd [PAP AuthNak id=0x10 “0012 PSMUN004 0001828992 test user”]
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: Remote message: 0012 PSMUN004 0001828992 test user
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: PAP authentication failed
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: sent [LCP TermReq id=0x20 “Failed to authenticate ourselves to peer”]
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: rcvd [LCP TermReq id=0x9c]
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: sent [LCP TermAck id=0x9c]
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: rcvd [LCP TermAck id=0x20]
Jan 22 15:13:56 ml-koenigsheide-120 pppd[12616]: Connection terminated.

Clearly the password and username were checked. Interestingly, there was a Ubiquiti Edgerouter on this connection before, with which this worked.

show version

Version: VyOS 1.3-rolling-202101071430
Release Train: equuleus

Built by: autobuild@vyos.net
Built on: Thu 07 Jan 2021 14:30 UTC
Build UUID: 710ade27-8981-49da-ac27-47acc9b4f413
Build Commit ID: 432f3f96927a54

Architecture: x86_64
Boot via: installed image
System type: bare metal

Hardware vendor: Default string
Hardware model: Default string
Hardware S/N: Default string
Hardware UUID: 03000200-0400-0500-0006-000700080009

Copyright: VyOS maintainers and contributors

Installed on the system is the latest 1.3 rolling release.

Does anyone know the problem or have an idea?

Thanks for the answers.

regards

Christian

1 Like
2

Hello @it-service-ml, your ISP can use MAC verification as an additional authentification step. Try to set old mac address to vif7

set interfaces ethernet eth5 vif 7 mac X:X:X:X:X:X
3

I have taken over the MAC address of the old firewall. Unfortunately this has no effect.

Jan 22 16:15:44 ml-koenigsheide-120 pppd[16206]: Connect: pppoe1 ↔ eth5.7
Jan 22 16:15:44 ml-koenigsheide-120 pppd[16206]: sent [LCP ConfReq id=0x5 <mru 1492> <magic 0x9669dcb8>]
Jan 22 16:15:44 ml-koenigsheide-120 pppd[16206]: rcvd [LCP ConfReq id=0x21 <mru 1492> <magic 0x3016bed2>]
Jan 22 16:15:44 ml-koenigsheide-120 pppd[16206]: sent [LCP ConfAck id=0x21 <mru 1492> <magic 0x3016bed2>]
Jan 22 16:15:44 ml-koenigsheide-120 pppd[16206]: rcvd [LCP ConfAck id=0x5 <mru 1492> <magic 0x9669dcb8>]
Jan 22 16:15:44 ml-koenigsheide-120 pppd[16206]: sent [LCP EchoReq id=0x0 magic=0x9669dcb8]
Jan 22 16:15:44 ml-koenigsheide-120 pppd[16206]: sent [PAP AuthReq id=0x3 user=“xxxxxxxxxxxxxxxxxxxx” password=]
Jan 22 16:15:44 ml-koenigsheide-120 pppd[16206]: rcvd [LCP EchoRep id=0x0 magic=0x3016bed2]
Jan 22 16:15:44 ml-koenigsheide-120 pppd[16206]: rcvd [PAP AuthNak id=0x3 “0012 PSMUN004 0001915096 test user”]
Jan 22 16:15:44 ml-koenigsheide-120 pppd[16206]: Remote message: 0012 PSMUN004 0001915096 test user
Jan 22 16:15:44 ml-koenigsheide-120 pppd[16206]: PAP authentication failed
Jan 22 16:15:44 ml-koenigsheide-120 pppd[16206]: sent [LCP TermReq id=0x6 “Failed to authenticate ourselves to peer”]
Jan 22 16:15:44 ml-koenigsheide-120 pppd[16206]: rcvd [LCP TermReq id=0x9d]
Jan 22 16:15:44 ml-koenigsheide-120 pppd[16206]: sent [LCP TermAck id=0x9d]
Jan 22 16:15:44 ml-koenigsheide-120 pppd[16206]: rcvd [LCP TermAck id=0x6]
Jan 22 16:15:44 ml-koenigsheide-120 pppd[16206]: Connection terminated.
Jan 22 16:15:44 ml-koenigsheide-120 pppd[16206]: Send PPPOE Discovery V1T1 PADT session 0x2952 length 20
Jan 22 16:15:44 ml-koenigsheide-120 pppd[16206]: dst 28:8a:1c:5b:d8:83 src 74:83:c2:71:1e:02
Jan 22 16:15:44 ml-koenigsheide-120 pppd[16206]: [AC-cookie ff 0b 04 e2 81 fe 25 11 de bd 1b a2 66 69 b0 b8]
Jan 22 16:15:44 ml-koenigsheide-120 pppd[16206]: Sent PADT

4

How can I narrow down the error? Is it possibly due to PAP/CHAP authentication?

5

I think auth type PAP/CHAP choices correctly.

Do you have special characters on your username or password?
Can you share it without deleting special characters but mixing with other alphabet chars?

Also, try to compare carefully your credentials in this configuration file

sudo cat /etc/ppp/peers/pppoe1
6

The login data are rantominized, but of the same type.
The data in /etc/ppp/peers/pppoe1 is 100% correct.

 ### Autogenerated by interfaces-pppoe.py ###
 
 
 # Require peer to provide the local IP address if it is not
 # specified explicitly in the config file.
 noipdefault
 
 # Don't show the password in logfiles:
 hide-password
 
 # Standard Link Control Protocol (LCP) parameters:
 lcp-echo-interval 20
 lcp-echo-failure 3
 
 # RFC 2516, paragraph 7 mandates that the following options MUST NOT be
 # requested and MUST be rejected if requested by the peer:
 # Address-and-Control-Field-Compression (ACFC)
 noaccomp
 
 # Asynchronous-Control-Character-Map (ACCM)
 default-asyncmap
 
 # Override any connect script that may have been set in /etc/ppp/options.
 connect /bin/true
 
 # Don't try to authenticate the remote node
 noauth
 
 # Don't try to proxy ARP for the remote endpoint. User can set proxy
 # arp entries up manually if they wish.  More importantly, having
 # the "proxyarp" parameter set disables the "defaultroute" option.
 noproxyarp
 
 # Unlimited connection attempts
 maxfail 0
 
 plugin rp-pppoe.so
 eth5.7
 persist
 ifname pppoe1
 ipparam pppoe1
 debug
 mtu 1492
 mru 1492
 
 user 004568262727535203262514#0001@t-online.de
 password 33577204
 
 usepeerdns
7

I think I know the reason, I will create a bug report on phabricator.
Client trying to authorize with the wrong username, because config generate username without quotes, it makes sense if in the username you have special characters.

@it-service-ml, please try manually edit sudo nano /etc/ppp/peers/pppoe1 and add double quotes

user "004568262727535203262514#0001@t-online.de"

Then reset pppoe

disconnect interface pppoe0
connect interface pppoe0
8

Thank you that worked! I had already tried to specify it with quotes when setting up the interface. Unfortunately the quotes were not taken over into the Config.

9

You can track bug issue on ⚓ T3251 PPPoE client trying to authorize with the wrong username

1 Like
10

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.