Thank you for replying.
Output of logread | grep ppp:
Sep 15 20:37:26 turris insmod: module is already loaded - ppp_generic
Sep 15 20:37:26 turris insmod: module is already loaded - pppox
Sep 15 20:37:26 turris insmod: module is already loaded - pppoe
Sep 15 20:37:26 turris netifd: wan (8867): ppp: warning: Sleeping for ‘10’ seconds
Sep 15 20:37:36 turris pppd[9199]: Plugin rp-pppoe.so loaded.
Sep 15 20:37:36 turris pppd[9199]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Sep 15 20:37:37 turris pppd[9199]: pppd 2.4.7 started by root, uid 0
Sep 15 20:37:52 turris pppd[9199]: Timeout waiting for PADO packets
Sep 15 20:37:52 turris pppd[9199]: Unable to complete PPPoE Discovery
Sep 15 20:37:52 turris pppd[9199]: Exit.
What strikes me as odd is the time. Last line was actually at 22:37:52. In Foris timezone is set as Europe/Berlin. As far as I know, non-matching time data is never a good thing.
Here’s the output of cat /etc/config/network:
config interface ‘loopback’
option ifname ‘lo’
option proto ‘static’
option ipaddr ‘127.0.0.1’
option netmask ‘255.0.0.0’
config globals ‘globals’
option ula_prefix ‘fd35:5642:7aa0::/48’
config interface ‘lan’
option type ‘bridge’
option proto ‘static’
option netmask ‘255.255.255.0’
option ip6assign ‘60’
option bridge_empty ‘1’
option ipaddr ‘192.168.2.1’
list ifname ‘lan0’
list ifname ‘lan1’
list ifname ‘lan2’
list ifname ‘lan3’
list ifname ‘lan4’
config interface ‘wan’
option ifname ‘eth1.7’
option proto ‘pppoe’
option password ‘XXX’
option ipv6 ‘auto’
option username ‘YYY’
config interface ‘guest_turris’
option enabled ‘1’
option type ‘bridge’
option proto ‘static’
option ipaddr ‘10.111.222.1’
option netmask ‘255.255.255.0’
option bridge_empty ‘1’
config route6
option target ‘2001:4dd0:af0e:230d:ca0e:14ff:fe07:b312’
option interface ‘wan’
option gateway '2001:4dd0:230d::/48`
And these are my ISPs requirement:
Data VLAN 10 with IP-Distribution via PPPoE (PAP)
Voice VLAN 20 with IP-Distribution via DHCP
VDSL2 ITU-T G.993.2, Annex-B/-J
Vectoring ITU-T G.993.5 (> 50 Mbit/s)
VDSL-Profile 17A
VDSL-Profile 30A (> 50 Mbit/s)
Dual-Stack Lite nach RFC-6333
DHCPv6 Option for Dual-Stack Lite nach RFC-6334
Unfortunately, I cannot ssh to my TO. Process /usr/sbin/sshd -D is running and my PC is all set - I can ssh to my laptop and back. Yet ssh root@192.168.1.1 returns
kex_exchange_identification: read: Connection reset by peer
Connection reset by 192.168.1.1 port 22