PPPoE connection with Vodafone VDSL over Allnet ALL4781-VDSL-SFP doesn't work

General discussion
1

Hello there, I recently bought a Turris Omnia router and the ALL4781-VDSL-SFP module and tried to connect it to the Internet using a Vodafone Business 50Mbit VDSL connection.
Unfortunately,that doesn’t work at all.
I tried it with correct and incorrect login data (to see what happens),with or without VLAN Tagging,using the Turris Omnia directly or with the Turris Omnia in bridge mode to establish the PPPoE connection using Windows Vista,Windows RT or Linux.
Nothing works.
No matter how I change the settings in the Turris Omnia,I always get the following messages in the log:

Nov  4 20:42:31 turris pppd[9571]: Send PPPOE Discovery V1T1 PADI session 0x0 length 4
Nov  4 20:42:31 turris pppd[9571]:  dst ff:ff:ff:ff:ff:ff  src d8:58:d7:01:1a:ff
Nov  4 20:42:31 turris pppd[9571]:  [service-name]
Nov  4 20:42:36 turris pppd[9571]: Timeout waiting for PADO packets
Nov  4 20:42:36 turris pppd[9571]: Unable to complete PPPoE Discovery
Nov  4 20:42:36 turris pppd[9571]: Exit.
Nov  4 20:42:36 turris netifd: Interface 'wan' is now down
Nov  4 21:42:36 turris kernel: [10095.741612] mvneta f1034000.ethernet eth2: Link is Down
Nov  4 20:42:36 turris netifd: Interface 'wan' is disabled
Nov  4 21:42:36 turris kernel: [10095.755274] mvneta f1034000.ethernet eth2: configuring for 802.3z/1000base-x link mode
Nov  4 21:42:36 turris kernel: [10095.763345] mvneta f1034000.ethernet eth2: Link is Up - 1Gbps/Full - flow control off
Nov  4 20:42:36 turris netifd: Interface 'wan' is enabled
Nov  4 20:42:36 turris netifd: Interface 'wan' is setting up now
Nov  4 20:42:36 turris insmod: module is already loaded - slhc
Nov  4 20:42:36 turris insmod: module is already loaded - ppp_generic
Nov  4 20:42:36 turris insmod: module is already loaded - pppox
Nov  4 20:42:36 turris insmod: module is already loaded - pppoe
Nov  4 20:42:36 turris pppd[9776]: Plugin rp-pppoe.so loaded.
Nov  4 20:42:36 turris pppd[9776]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Nov  4 20:42:36 turris pppd[9776]: pppd 2.4.7 started by root, uid 0
Nov  4 20:42:36 turris sshd[9719]: Accepted password for root from 192.168.1.101 port 44498 ssh2
Nov  4 20:42:36 turris pppd[9776]: Send PPPOE Discovery V1T1 PADI session 0x0 length 4
Nov  4 20:42:36 turris pppd[9776]:  dst ff:ff:ff:ff:ff:ff  src d8:58:d7:01:1a:ff
Nov  4 20:42:36 turris pppd[9776]:  [service-name]
Nov  4 20:42:37 turris kresd[9830]: [system] bind to '0.0.0.0@53' Address in use
Nov  4 20:42:41 turris pppd[9776]: Send PPPOE Discovery V1T1 PADI session 0x0 length 4
Nov  4 20:42:41 turris pppd[9776]:  dst ff:ff:ff:ff:ff:ff  src d8:58:d7:01:1a:ff
Nov  4 20:42:41 turris pppd[9776]:  [service-name]
Nov  4 20:42:46 turris pppd[9776]: Send PPPOE Discovery V1T1 PADI session 0x0 length 4
Nov  4 20:42:46 turris pppd[9776]:  dst ff:ff:ff:ff:ff:ff  src d8:58:d7:01:1a:ff
Nov  4 20:42:46 turris pppd[9776]:  [service-name]

I can confirm that the SFP Module is being used as enabling or disabling the PPPoE connection or setting it into bridge mode results in differences how the LEDs are blinking.
I can not confirm,however,that the VDSL connection is working at all as I’m new in this flat and I have no other router to try it with.
I just ordered a used Speedport to finally get at least some working internet connection,even if it’s not 100% free and open-source :frowning:
When it arrives,I will be able to confirm if the VDSL line is working as it should.
In the meantime,it would be really helpful if anyone had some ideas what I can try to further investigate the connection using the Turris Omnia.
I really want to get this thing working,I’m pretty experienced with Linux but absolutely not with networking as that’s my first open-source router and before that,what I’ve done from the Linux-side was just the Wifi connection.
Please help! :cry:

2

It seems that the VDSL service is not active yet.

3

Hm, that should hopefully not be the case as my DSL connection should have been enabled at the 15th October when a technician was here and switched some cables.
Can’t this error come from some wrong config on the software-side?
Otherwise I’ll have to wait for the Speedport to confirm.

4

Are you sure you don’t need to perform any VLAN tagging on the wan interface? Check this with your service provider. Can you paste here the output of uci show network.wan please?

5

No, I’m not sure if I need VLAN tagging or not.
That’s why I tried it without VLAN, with VLAN 7 as suggested in the Vodafone Forum ( VDSL50 - VLAN ID erforderlich für Router Konfigura... - Vodafone Community ) and with VLAN 848 as suggested in another Turris Forum thread ( Pppoe issue over SFP GPON with Timeout waiting for PADO packets - #3 by FruhMi ).
Unfortunately that doesn’t change anything, the error always stays the same.
Here is my current uci show network.wan with VLAN 848:

network.wan=interface
network.wan.proto='pppoe'
network.wan.password='********'
network.wan.ipv6='1'
network.wan.keepalive='0'
network.wan.ifname='eth2.848'
network.wan.username='ak**********-static'
6

VLAN 848 is specific for the Czech Republic. Please consult your service provider for network connection requirements.

7

Thank you very much for your help.
I found a list of VLAN IDs of German providers now ( VDSL2 - VLAN-Tags verschiedener Internet-Provider (Update) - BOC IT-Security GmbH ) and there it states that it’s 132 for Vodafone.
I tried it and it works!
A first ping to 1.1.1.1 (Cloudflare DNS) succeeds.
I will do further tests after having my lunch, but I think I have a fully functional internet connection now.

2 Likes
8

I can now confirm that everything works as expected.
Thanks again for the help.
The problem is now solved.

1 Like
9

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