WAN ADSL pppoe connection / no PADS received

Software SW help
1

Dear Turris community,

I am currently trying to connect my new Turris Omnia to my ADSL Provider (Deutsche/German Telekom).
So far I have created a wan interface with pppoe. Behind the WAN port I have a DSL Modem with pppoe passthrough. The setup is working fine with an old dd-wrt router.

With the Turris Omnia I get PADI/PADO packets received and PADR sent, but there is no PADS received. Do you have any ideas what the problem might be?

Here is the debug of the pppd:

2017-03-20T08:25:17+01:00 info pppd[2130]: Plugin rp-pppoe.so loaded.
2017-03-20T08:25:17+01:00 info pppd[2130]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
2017-03-20T08:25:17+01:00 notice pppd[2130]: pppd 2.4.7 started by root, uid 0
2017-03-20T08:25:17+01:00 debug pppd[2130]: Send PPPOE Discovery V1T1 PADI session 0x0 length 4
2017-03-20T08:25:17+01:00 debug pppd[2130]:  dst ff:ff:ff:ff:ff:ff  src d8:58:d7:00:35:5f
2017-03-20T08:25:17+01:00 debug pppd[2130]:  [service-name]
2017-03-20T08:25:18+01:00 debug pppd[2130]: Recv PPPOE Discovery V1T1 PADO session 0x0 length 55
2017-03-20T08:25:18+01:00 debug pppd[2130]:  dst d8:58:d7:00:35:5f  src 00:04:0e:0f:37:82
2017-03-20T08:25:18+01:00 debug pppd[2130]:  [AC-name DTMR73-se800-B225E090820317] [AC-cookie  39 4e a0 62 c2 3a b9 64 94 70 be 94 39 89 8e 2c] [service-name]
2017-03-20T08:25:18+01:00 debug pppd[2130]: Send PPPOE Discovery V1T1 PADR session 0x0 length 24
2017-03-20T08:25:18+01:00 debug pppd[2130]:  dst 00:04:0e:0f:37:82  src d8:58:d7:00:35:5f
2017-03-20T08:25:18+01:00 debug pppd[2130]:  [service-name] [AC-cookie  39 4e a0 62 c2 3a b9 64 94 70 be 94 39 89 8e 2c]
2017-03-20T08:25:23+01:00 debug pppd[2130]: Send PPPOE Discovery V1T1 PADR session 0x0 length 24
2017-03-20T08:25:23+01:00 debug pppd[2130]:  dst 00:04:0e:0f:37:82  src d8:58:d7:00:35:5f
2017-03-20T08:25:23+01:00 debug pppd[2130]:  [service-name] [AC-cookie  39 4e a0 62 c2 3a b9 64 94 70 be 94 39 89 8e 2c]
2017-03-20T08:25:28+01:00 debug pppd[2130]: Send PPPOE Discovery V1T1 PADR session 0x0 length 24
2017-03-20T08:25:28+01:00 debug pppd[2130]:  dst 00:04:0e:0f:37:82  src d8:58:d7:00:35:5f
2017-03-20T08:25:28+01:00 debug pppd[2130]:  [service-name] [AC-cookie  39 4e a0 62 c2 3a b9 64 94 70 be 94 39 89 8e 2c]
2017-03-20T08:25:33+01:00 warning pppd[2130]: Timeout waiting for PADS packets
2017-03-20T08:25:33+01:00 err pppd[2130]: Unable to complete PPPoE Discovery
2017-03-20T08:25:33+01:00 info pppd[2130]: Exit.

The ppp options:

debug
noccp
nomppc
noauth
logfile /var/log/pppd.log
noipdefault
noaccomp
nobsdcomp
nodeflate
nopcomp
nomppe
nocrtscts
persist
mtu 1492
mru 1492
default-asyncmap
lock
maxfail 0
lcp-echo-failure 10
lcp-echo-interval 5

The wan config:

config interface 'wan'
option proto 'pppoe'
option username 'xxxxxxx@t-online.de'
option password 'yyyyy'
option ipv6 '1'
option ifname 'eth1'

Any help or ideas for solving the problem would be greatly appreciated as the Turris without internet connection is not that interesting :slight_smile:

Thanks in advance!
Ari

2

Hello Ari,
Do you use vlan tag 7 on your dsl modem?

3

He still seems to be connected to the BRAS platform, which as far as I can tell does not require the use of VLAN7. Also on the new BNG platform without VLAN7 he would encounter problems at the PADI/PADO exchange. But since the whole DTAG network is in flux, maybe this behavior changed. Also sooner or later (rather sooner) he will be switched the the BNG platform and require VLAN7

4

Hello Roland,

thanks for your reply.

vlan tag 7 is not (yet) required.

My old setup (that I am using at the moment) with a several year old dd-wrt router perfectly works just out of the box without vlan tagging. That’s the reason why I am surprised that it doesn’t work with the Turris omnia software.

Best regards,
Ari

5

Hello Ari,
I work for some weeks without problems with adsl from the german telecom. Here are my configuration files:
Turris Firmware: 3.6.1
/etc/config/network:

config interface 'wan’
option ifname 'eth1’
option _orig_ifname 'eth1’
option _orig_bridge 'false’
option proto 'pppoe’
option username ‚xxxxxxxxxxx‘
option password ‚xxxxxxxxxxx‘
option ipv6 ‘1’

/etc/ppp/options.pptpd

auth
name "pptp-server"
lcp-echo-failure 3
lcp-echo-interval 60
default-asyncmap
mtu 1482
mru 1482
nobsdcomp
Fehler
require-mschap-v2
refuse-chap
refuse-mschap
refuse-eap
refuse-pap

6

Hello Roland,

thanks for your configuration settings.
Could you please also provide the contents of your /etc/ppp/options file? (options.pptpd is presumably not used for the ADSL connection).

I will then try to use same configuration and see if it works.

Thanks in advance!

Best regards,
Ari

7

Hello Ari,

here my /etc/ppp/options file:

logfile /dev/null
noipdefault
noaccomp
nopcomp
nocrtscts
lock
maxfail 0
lcp-echo-failure 5
lcp-echo-interval 1

best regards
Roland

8

Hello Roland,

ok. Thanks. I tried it with your settings but still doesn’t work.
I have no idea what the problem could be. Either it is the rp-pppoe plugin that doesn’t like the Telekom AC or it is something hardware based.

Does anyone know if German/Deutsche Telekom AC don’t like it if you disconnect a connection from one pppoe client and shortly after that connect with another (Turris Omnia) client?

Or it could be my old DSL-Modem (very old Fritz!Box) that doesn’t like the Turris Omnia.

With my old dd-wrt there is no problem in connecting via pppoe …

I have no further ideas…

Thanks and best regards,
Ari

9

Hello all,

thanks for your help. I just wanted to let you know that I could ‘solve’ the problem by buying a new DSL-Modem.
It seems that somehow my old FritzBox DSL Modem didn’t like the Turris Omnia and didn’t pass the PADS packets through to the Turris Omnia …

I have finally a working configuration now.

Thanks again and best regards,
Ari