How to connect to Vodafone (DE) VDSL with ALL4781-VDSL2-SFP SFP?

[Starlight]

A few days ago, my Vodafone EasyBox 904 xDSL failed forever. To reduce the amount of devices, I decided to order an Alltech ALL4781-VDSL2-SFP.

It arrived today and I could not connect until I found out that I need to switch to SFP manually with the following command:

ln -sf armada-385-turris-omnia-sfp.dtb dtb

Setting up the network interface, I stuck: Vodafone is not answering my requests or does not get them.
Here the messages log:

Oct  5 00:56:03 turris kernel: [ 7962.470642] mvneta f1034000.ethernet eth2: configuring for inband/1000base-x link mode
Oct  5 00:56:03 turris kernel: [ 7962.478931] mvneta f1034000.ethernet eth2: Link is Up - 1Gbps/Full - flow control off
Oct  4 22:56:03 turris netifd: Interface 'wan' is enabled
Oct  4 22:56:03 turris netifd: Interface 'wan' is setting up now
Oct  4 22:56:03 turris insmod: module is already loaded - slhc
Oct  4 22:56:03 turris insmod: module is already loaded - ppp_generic
Oct  4 22:56:03 turris insmod: module is already loaded - pppox
Oct  4 22:56:03 turris insmod: module is already loaded - pppoe
Oct  4 22:56:03 turris netifd: wan (19465): ppp: warning: Sleeping for '10' seconds
Oct  4 22:56:04 turris odhcpd[3394]: Failed to send to ff02::1%guest_turris@br-guest_turris (Address not available)
Oct  4 22:56:13 turris pppd[19753]: Plugin rp-pppoe.so loaded.
Oct  4 22:56:13 turris pppd[19753]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Oct  4 22:56:13 turris pppd[19753]: pppd 2.4.7 started by root, uid 0
Oct  4 22:56:28 turris pppd[19753]: Timeout waiting for PADO packets
Oct  4 22:56:28 turris pppd[19753]: Unable to complete PPPoE Discovery
Oct  4 22:56:28 turris pppd[19753]: Exit.
Oct  4 22:56:28 turris netifd: Interface 'wan' is now down
Oct  4 22:56:28 turris netifd: Interface 'wan' is disabled
Oct  5 00:56:28 turris kernel: [ 7987.836407] mvneta f1034000.ethernet eth2: Link is Down

Doing the same connecting to Telekom (DE), I get an success (of course no correct credentials):

Oct  5 00:58:56 turris kernel: [ 8135.279725] mvneta f1034000.ethernet eth2: configuring for inband/1000base-x link mode
Oct  5 00:58:56 turris kernel: [ 8135.287767] mvneta f1034000.ethernet eth2: Link is Up - 1Gbps/Full - flow control off
Oct  4 22:58:56 turris netifd: Interface 'wan' is enabled
Oct  4 22:58:56 turris netifd: Interface 'wan' is setting up now
Oct  4 22:58:56 turris insmod: module is already loaded - slhc
Oct  4 22:58:56 turris insmod: module is already loaded - ppp_generic
Oct  4 22:58:56 turris insmod: module is already loaded - pppox
Oct  4 22:58:56 turris insmod: module is already loaded - pppoe
Oct  4 22:58:56 turris netifd: wan (22915): ppp: warning: Sleeping for '10' seconds
Oct  4 22:59:06 turris pppd[23235]: Plugin rp-pppoe.so loaded.
Oct  4 22:59:06 turris pppd[23235]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Oct  4 22:59:06 turris pppd[23235]: pppd 2.4.7 started by root, uid 0
Oct  4 22:59:06 turris pppd[23235]: PPP session is 79
Oct  4 22:59:06 turris pppd[23235]: Connected to 28:8a:1c:e5:fe:71 via interface eth2.7
Oct  5 00:59:06 turris kernel: [ 8145.638908] pppoe-wan: renamed from ppp0
Oct  4 22:59:06 turris pppd[23235]: Renamed interface ppp0 to pppoe-wan
Oct  4 22:59:06 turris pppd[23235]: Using interface pppoe-wan
Oct  4 22:59:06 turris pppd[23235]: Connect: pppoe-wan <--> eth2.7
Oct  4 22:59:06 turris pppd[23235]: Remote message: 0012 PSKLN001 0002762564 test user
Oct  4 22:59:06 turris pppd[23235]: PAP authentication failed
Oct  4 22:59:06 turris pppd[23235]: Modem hangup
Oct  4 22:59:06 turris pppd[23235]: Connection terminated.
Oct  4 22:59:06 turris pppd[23235]: Sent PADT
Oct  4 22:59:06 turris pppd[23235]: Exit.
Oct  4 22:59:07 turris netifd: Interface 'wan' is now down
Oct  4 22:59:07 turris netifd: Interface 'wan' is disabled

Here is my network configuration:

config interface 'wan'
        option proto 'pppoe'
        option password '<password>'
        option ipv6 'auto'
        option username 'vb********69'
        option ifname 'eth2.132'

config interface 'wan6'
        option proto 'pppoe'
        option ipv6 'auto'
        option ifname '@wan'

Turris Version is 5.4.4

Does anyone see my mistake?

[moeller0]

@Starlight

        option ifname 'eth2.132'

Try ‘eth2.7’ instead of ‘eth2.132’, as this is likely a TAL/access link operated by Deutsche Telekom.
See e.g.: https://administrator.de/knowledge/einwahlparameter-verschiedener-deutscher-dsl-provider-mit-vlan-id-516717.html

[Starlight]

Thanks @moeller0, VLAN ID 7 is correct, Vodafone Support confirmed.

However, neither them nor me can figure out why there is no connection established.

Oct 4 22:59:06 turris pppd[23235]: Using interface pppoe-wan
Oct 4 22:59:06 turris pppd[23235]: Connect: pppoe-wan ↔ eth2.7
Oct 4 22:59:06 turris pppd[23235]: Remote message: 0012 PSKLN001 0002762564 test user
Oct 4 22:59:06 turris pppd[23235]: PAP authentication failed
Oct 4 22:59:06 turris pppd[23235]: Modem hangup
Oct 4 22:59:06 turris pppd[23235]: Connection terminated.

Still PAP authentication failed and no connection possible. Username and password are double checked and the technician said, he could not see any failed logins.

Edit
I added a log for PPP. here I also see

Timeout waiting for PADO packets
Unable to complete PPPoE Discovery

Edit
Fixed it myself, Vodafone Technical Support was not aware of the prefix for connecting. Here the current correct network configuration for Vodafone VDSL for reference:

config interface 'wan'
        option proto 'pppoe'
        option ipv6 'auto'
        option username 'vodafone-vdsl.komplett/<username>'
        option password '<password>'
        option ifname 'eth2.7'

[moeller0]

Could you please add this to the wiki site at https://openwrt.org/docs/guide-user/network/wan/isp-configurations
That seems like a decent place to add this documentation.