Configure VDSL - Error: Connection attempt failed

Hi everybody, I'm trying to configure a TP-Link W8970 with a VDSL but after trying many configuration found on this forum I'm still getting error.

Line seems up and sync

Line State:Showtime with TC-Layer sync
Line Mode:G.993.2 (VDSL2, Profile 17a)
Line Uptime:0h 5m 41s
Annex:B
Data Rate:31.494 Mb/s / 3.144 Mb/s
Max. Attainable Data Rate (ATTNDR):65.632 Mb/s / 24.978 Mb/s
Latency:0.13 ms / 0.00 ms
Line Attenuation (LATN):14.8 dB / 23.0 dB
Signal Attenuation (SATN):14.8 dB / 19.1 dB
Noise Margin (SNR):17.5 dB / 22.7 dB
Aggregate Transmit Power (ACTATP):-8.4 dB / 14.4 dB
Forward Error Correction Seconds (FECS):0 / 216
Errored seconds (ES):0 / 11
Severely Errored Seconds (SES):0 / 0
Loss of Signal Seconds (LOSS):0 / 0
Unavailable Seconds (UAS):58 / 58
Header Error Code Errors (HEC):0 / 0
Non Pre-emptive CRC errors (CRC_P):0 / 0
Pre-emptive CRC errors (CRCP_P):0 / 0
ATU-C System Vendor ID:Broadcom 192.22
Power Management Mode:L0 - Synchronized

But interface shows:

Error: Unknown error (USER_REQUEST)

and after a few seconds

Error: Connection attempt failed

I'm using Openwrt version 21.02 and below you can see the configuration

network.wan=interface
network.wan.proto='pppoe'
network.wan.peerdns='0'
network.wan.ipv6='0'
network.wan.keepalive='1000 60'
network.wan.delegate='0'
network.wan.device='dsl0.835'
network.wan.encaps='vc'
network.wan.type='bridge`'
network.wan.username='xxxxxxxxxxx'
network.wan.password='xxxxxxxxxx'

network.dsl=dsl
network.dsl.tone='av'
network.dsl.xfer_mode='ptm'
network.dsl.ds_snr_offset='0'
network.dsl.firmware='/lib/firmware/lantiq-vrx200-b.bin'
network.dsl.annex='b'
network.dsl.line_mode='vdsl'

The provider (TIM - Italy) said I have to use VLAN 835 and provided me username/password.

They gave me the Static IP Address they assigned to me but I don't know how to set them in the configuration.

Any troubleshooting suggestion ?

Think You have wrong WAN setup .As You have synchro.

/etc/config/network
config device
        option name 'dsl0'
        option macaddr 'xx'
        option mtu '1508'

config interface 'wan'
        option device 'dsl0.35'
        option proto 'pppoe'
        option username 'username'
        option password 'password'
        option ipv6 '0'
        option mtu '1500'

config device
        option name 'dsl0.35'
        option type '8021q'
        option ifname 'dsl0'
        option vid '35'

this work for me in router mode. My ISP use VLAN 35

I tried but it still doesn't work, seems that RX / TX are increasing but no connection available

Protocol: PPPoE
MAC: 00:20:DA:86:23:75
RX: 563 B (1 Pkts.)
TX: 64 B (2 Pkts.)
Error: Connection attempt failed

I tried to use a bad username/password but nothing change

Moreover I checked log and I found this

Wed Jan 26 17:33:02 2022 daemon.warn pppd[7570]: Timeout waiting for PADO packets
Wed Jan 26 17:33:02 2022 daemon.err pppd[7570]: Unable to complete PPPoE Discovery
Wed Jan 26 17:33:02 2022 daemon.info pppd[7570]: Exit.
Wed Jan 26 17:33:03 2022 daemon.err insmod: module is already loaded - ppp_generic
Wed Jan 26 17:33:03 2022 daemon.err insmod: module is already loaded - pppox
Wed Jan 26 17:33:03 2022 daemon.err insmod: module is already loaded - pppoe
Wed Jan 26 17:33:03 2022 daemon.info pppd[7677]: Plugin rp-pppoe.so loaded.
Wed Jan 26 17:33:03 2022 daemon.info pppd[7677]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Wed Jan 26 17:33:03 2022 daemon.notice pppd[7677]: pppd 2.4.8 started by root, uid 0
Wed Jan 26 17:33:07 2022 daemon.err pppd[7677]: select (waitForPADO): Interrupted system call
Wed Jan 26 17:33:07 2022 daemon.warn pppd[7677]: Timeout waiting for PADO packets
Wed Jan 26 17:33:07 2022 daemon.err pppd[7677]: Unable to complete PPPoE Discovery
Wed Jan 26 17:33:07 2022 daemon.info pppd[7677]: Exit.
Wed Jan 26 17:33:08 2022 daemon.err insmod: module is already loaded - ppp_generic
Wed Jan 26 17:33:08 2022 daemon.err insmod: module is already loaded - pppox
Wed Jan 26 17:33:08 2022 daemon.err insmod: module is already loaded - pppoe
Wed Jan 26 17:33:08 2022 daemon.info pppd[8123]: Plugin rp-pppoe.so loaded.
Wed Jan 26 17:33:08 2022 daemon.info pppd[8123]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Wed Jan 26 17:33:08 2022 daemon.notice pppd[8123]: pppd 2.4.8 started by root, uid 0
r

This just shows that your router send a pppoe request but failed to get a response, typically that happens if something along the path is incorrect, but the error is quite unspecific and happens from DSL cable not connected to the socket, to wrong VLAN tag, and more in-between the two...

1 Like

Hi moeller0, how can I get deeper on this error ? System log doesn't provide any other detail.

I notice nicefile config use a different MTU from default 1500, I verified it with http://www.letmecheck.it/mtu-test.php but seems 1500.

I would guess MTU not to be an issue since I assume the packets sizes during PPPoE negotiation to be typically << 1500.

The first best candidate is the VLAN tab.

Maybe you can post the content of /etc/config/network, jus make sure to redact PPPoE username and password.

Thank you moeller0, this is the configuration:

config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fd8e:ff4b:4651::/48'

config atm-bridge 'atm'
        option encaps 'llc'
        option payload 'bridged'
        option nameprefix 'dsl'
        option vci '35'
        option vpi '8'

config dsl 'dsl'
        option annex 'b'
        option firmware '/lib/firmware/lantiq-vrx200-b.bin'
        option tone 'av'
        option xfer_mode 'ptm'
        option ds_snr_offset '0'

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'eth0.1'

config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option ipaddr '192.168.1.1'
        option netmask '255.255.255.0'
        option ip6assign '60'

config interface 'wan'
        option proto 'pppoe'
        option peerdns '0'
        option password '**************'
        option keepalive '1000 60'
        option ipv6 '0'
        option device 'dsl0.835'
        option username '*********'

config interface 'wan6'
        option device '@wan'
        option proto 'dhcpv6'

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '1'

config switch_vlan
        option device 'switch0'
        option vlan '1'
        option ports '0 2 4 5 6t'

config interface 'wwan'
        option proto 'dhcp'

config device
        option name 'dsl0.835'
        option ipv6 '0'
        option mtu '1500'

config device
        option name 'dsl0'
        option mtu '1500'

Try adding:

config device
	option type '8021q'
	option ifname 'dsl0'
	option vid '835'
	option name 'dsl0.835'

at least something similar works for me...

you can use /usr/sbin/tcpdump -e -i dsl0 -s 100 to get a on-line print-out of the packets traversing dsl0:

12:43:33.447561 d8:58:d7:00:46:7b (oui Unknown) > 00:31:46:07:15:1f (oui Unknown), ethertype 802.1Q (0x8100), length 79: vlan 7, p 0, ethertype PPPoE S, PPPoE  [ses 0x847] IP (0x0021), length 55: 77.6.145.181.38217 > 128.116.39.20.59416: UDP, length 25

In my case we see vlan 7 in your case you need to see vlan 835 there otherwise the VLAN configuration did not work as designed... in case you did not install tcpdump, opkg update ; opkg install tcpdump should get you started...

I don't have enough space, can I remove something on overlay ?


root@OpenWrt:~# opkg install tcpdump
Installing tcpdump (4.9.3-3) to root...
Collected errors:
 * verify_pkg_installable: Only have 188kb available on filesystem /overlay, pkg tcpdump needs 283
 * opkg_install_cmd: Cannot install package tcpdump

This is the file system usage

root@OpenWrt:~# df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root                 4.0M      4.0M         0 100% /rom
tmpfs                    27.8M      1.1M     26.7M   4% /tmp
/dev/mtdblock4            1.3M    832.0K    448.0K  65% /overlay
overlayfs:/overlay        1.3M    832.0K    448.0K  65% /
tmpfs                   512.0K         0    512.0K   0% /dev

Not sure, this looks quite tight, maybe build a new firmware with tcpdump included? Or use https://openwrt.org/docs/guide-developer/imagebuilder_frontends one of the ASU frontends to build a modified version including tcpdump (not sure what the exact packet name is).

But have you tried adding:

config device
	option type '8021q'
	option ifname 'dsl0'
	option vid '835'
	option name 'dsl0.835'

to /etc/config/network followed by a reboot?

I was able to add TCPDUMP, this is the output

root@OpenWrt:~# /usr/sbin/tcpdump -e -i dsl0 -s 100
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on dsl0, link-type EN10MB (Ethernet), capture size 100 bytes
14:56:35.868715 84:c1:c1:7d:46:9b (oui Unknown) > c8:77:65:10:60:d5 (oui Unknown), ethertype 802.1Q (0x8100), length 60: vlan 835, p 2, ethertype IPv4, 178.239.21.86.46095 > 88.42.111.66.5038: Flags [S], seq 1571923587, win 1024, length 0
14:56:37.224046 84:c1:c1:7d:46:9b (oui Unknown) > c8:77:65:10:60:d5 (oui Unknown), ethertype 802.1Q (0x8100), length 70: vlan 835, p 2, ethertype IPv4, 216.58.206.67.80 > 88.42.111.65.46757: Flags [F.], seq 2903839479, ack 2692897357, win 721, options [nop,nop,TS val 2196138528 ecr 5357616], length 0
14:56:38.329700 00:20:da:86:23:75 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 36: vlan 835, p 0, ethertype PPPoE D, PPPoE PADI [Service-Name] [Host-Uniq 0x000011E3]
14:56:43.577775 00:20:da:86:23:75 (oui Unknown) > 33:33:00:00:00:16 (oui Unknown), ethertype IPv6 (0x86dd), length 130: :: > ff02::16: HBH ICMP6, multicast listener report v2, 3 group record(s), length 68
14:56:43.909864 00:20:da:86:23:75 (oui Unknown) > 33:33:ff:86:23:75 (oui Unknown), ethertype IPv6 (0x86dd), length 86: :: > ff02::1:ff86:2375: ICMP6, neighbor solicitation, who has fe80::220:daff:fe86:2375, length 32
14:56:44.129810 00:20:da:86:23:75 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 36: vlan 835, p 0, ethertype PPPoE D, PPPoE PADI [Service-Name] [Host-Uniq 0x0000130C]
14:56:44.325713 00:20:da:86:23:75 (oui Unknown) > 33:33:00:00:00:16 (oui Unknown), ethertype IPv6 (0x86dd), length 130: :: > ff02::16: HBH ICMP6, multicast listener report v2, 3 group record(s), length 68
14:56:44.934110 00:20:da:86:23:75 (oui Unknown) > 33:33:00:00:00:16 (oui Unknown), ethertype IPv6 (0x86dd), length 130: fe80::220:daff:fe86:2375 > ff02::16: HBH ICMP6, multicast listener report v2, 3 group record(s), length 68
14:56:44.945749 00:20:da:86:23:75 (oui Unknown) > 33:33:00:00:00:16 (oui Unknown), ethertype IPv6 (0x86dd), length 90: fe80::220:daff:fe86:2375 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
14:56:45.253699 00:20:da:86:23:75 (oui Unknown) > 33:33:00:00:00:16 (oui Unknown), ethertype IPv6 (0x86dd), length 130: fe80::220:daff:fe86:2375 > ff02::16: HBH ICMP6, multicast listener report v2, 3 group record(s), length 68
14:56:45.445721 00:20:da:86:23:75 (oui Unknown) > 33:33:00:00:00:16 (oui Unknown), ethertype IPv6 (0x86dd), length 90: fe80::220:daff:fe86:2375 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
14:56:47.693694 84:c1:c1:7d:46:9b (oui Unknown) > c8:77:65:10:60:d5 (oui Unknown), ethertype 802.1Q (0x8100), length 70: vlan 835, p 2, ethertype IPv4, 142.250.180.106.443 > 88.42.111.65.49258: Flags [F.], seq 2218638276, ack 66467291, win 272, options [nop,nop,TS val 2422265828 ecr 2392510987], length 0
14:56:49.133694 00:20:da:86:23:75 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 36: vlan 835, p 0, ethertype PPPoE D, PPPoE PADI [Service-Name] [Host-Uniq 0x0000130C]
14:56:51.101740 84:c1:c1:7d:46:9b (oui Unknown) > c8:77:65:10:60:d5 (oui Unknown), ethertype 802.1Q (0x8100), length 70: vlan 835, p 2, ethertype IPv4, 216.58.198.4.443 > 88.42.111.65.41578: Flags [F.], seq 3234977486, ack 4246561584, win 272, options [nop,nop,TS val 3627404785 ecr 3936325907], length 0
14:56:51.559821 84:c1:c1:7d:46:9b (oui Unknown) > c8:77:65:10:60:d5 (oui Unknown), ethertype 802.1Q (0x8100), length 70: vlan 835, p 2, ethertype IPv4, 216.58.206.67.80 > 88.42.111.65.46757: Flags [F.], seq 0, ack 1, win 721, options [nop,nop,TS val 2196152864 ecr 5357616], length 0
14:56:51.692480 84:c1:c1:7d:46:9b (oui Unknown) > c8:77:65:10:60:d5 (oui Unknown), ethertype 802.1Q (0x8100), length 70: vlan 835, p 2, ethertype IPv4, 216.58.198.4.443 > 88.42.111.65.41578: Flags [F.], seq 0, ack 1, win 272, options [nop,nop,TS val 3627405376 ecr 3936325907], length 0
14:56:52.524417 84:c1:c1:7d:46:9b (oui Unknown) > c8:77:65:10:60:d5 (oui Unknown), ethertype 802.1Q (0x8100), length 70: vlan 835, p 2, ethertype IPv4, 216.58.198.4.443 > 88.42.111.65.41578: Flags [F.], seq 0, ack 1, win 272, options [nop,nop,TS val 3627406208 ecr 3936325907], length 0
14:56:54.124375 84:c1:c1:7d:46:9b (oui Unknown) > c8:77:65:10:60:d5 (oui Unknown), ethertype 802.1Q (0x8100), length 70: vlan 835, p 2, ethertype IPv4, 216.58.198.4.443 > 88.42.111.65.41578: Flags [F.], seq 0, ack 1, win 272, options [nop,nop,TS val 3627407808 ecr 3936325907], length 0
14:56:54.137766 00:20:da:86:23:75 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 36: vlan 835, p 0, ethertype PPPoE D, PPPoE PADI [Service-Name] [Host-Uniq 0x0000130C]
14:56:56.538050 84:c1:c1:7d:46:9b (oui Unknown) > c8:77:65:10:60:d5 (oui Unknown), ethertype 802.1Q (0x8100), length 199: vlan 835, p 2, ethertype IPv4, 64.233.162.95.443 > 88.42.111.65.42708: Flags [FP.], seq 4149094897:4149095026, ack 3087673643, win 281, options [nop,nop,TS val 3367496698 ecr 25331395], length 129
14:56:57.261021 84:c1:c1:7d:46:9b (oui Unknown) > c8:77:65:10:60:d5 (oui Unknown), ethertype 802.1Q (0x8100), length 70: vlan 835, p 2, ethertype IPv4, 216.58.198.4.443 > 88.42.111.65.41578: Flags [F.], seq 0, ack 1, win 272, options [nop,nop,TS val 3627410944 ecr 3936325907], length 0
14:56:59.381786 00:20:da:86:23:75 (oui Unknown) > 33:33:00:00:00:16 (oui Unknown), ethertype IPv6 (0x86dd), length 130: :: > ff02::16: HBH ICMP6, multicast listener report v2, 3 group record(s), length 68
14:56:59.425823 00:20:da:86:23:75 (oui Unknown) > 33:33:00:00:00:16 (oui Unknown), ethertype IPv6 (0x86dd), length 130: :: > ff02::16: HBH ICMP6, multicast listener report v2, 3 group record(s), length 68
14:56:59.437820 00:20:da:86:23:75 (oui Unknown) > 33:33:ff:86:23:75 (oui Unknown), ethertype IPv6 (0x86dd), length 86: :: > ff02::1:ff86:2375: ICMP6, neighbor solicitation, who has fe80::220:daff:fe86:2375, length 32
14:56:59.785735 00:20:da:86:23:75 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 36: vlan 835, p 0, ethertype PPPoE D, PPPoE PADI [Service-Name] [Host-Uniq 0x000013D1]
14:57:00.454169 00:20:da:86:23:75 (oui Unknown) > 33:33:00:00:00:16 (oui Unknown), ethertype IPv6 (0x86dd), length 130: fe80::220:daff:fe86:2375 > ff02::16: HBH ICMP6, multicast listener report v2, 3 group record(s), length 68
14:57:00.465734 00:20:da:86:23:75 (oui Unknown) > 33:33:00:00:00:16 (oui Unknown), ethertype IPv6 (0x86dd), length 90: fe80::220:daff:fe86:2375 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
14:57:00.869761 00:20:da:86:23:75 (oui Unknown) > 33:33:00:00:00:16 (oui Unknown), ethertype IPv6 (0x86dd), length 90: fe80::220:daff:fe86:2375 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
14:57:01.417712 00:20:da:86:23:75 (oui Unknown) > 33:33:00:00:00:16 (oui Unknown), ethertype IPv6 (0x86dd), length 130: fe80::220:daff:fe86:2375 > ff02::16: HBH ICMP6, multicast listener report v2, 3 group record(s), length 68
14:57:03.723793 84:c1:c1:7d:46:9b (oui Unknown) > c8:77:65:10:60:d5 (oui Unknown), ethertype 802.1Q (0x8100), length 70: vlan 835, p 2, ethertype IPv4, 216.58.198.4.443 > 88.42.111.65.41578: Flags [F.], seq 0, ack 1, win 272, options [nop,nop,TS val 3627417408 ecr 3936325907], length 0
14:57:04.789980 00:20:da:86:23:75 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 36: vlan 835, p 0, ethertype PPPoE D, PPPoE PADI [Service-Name] [Host-Uniq 0x000013D1]
14:57:05.587013 84:c1:c1:7d:46:9b (oui Unknown) > c8:77:65:10:60:d5 (oui Unknown), ethertype 802.1Q (0x8100), length 62: vlan 835, p 2, ethertype IPv4, 162.142.125.82.21180 > 88.42.111.64.12104: Flags [S], seq 3269358874, win 1024, options [mss 1460], length 0
^C14:57:07.310297 84:c1:c1:7d:46:9b (oui Unknown) > c8:77:65:10:60:d5 (oui Unknown), ethertype 802.1Q (0x8100), length 62: vlan 835, p 2, ethertype IPv4, 193.163.125.74.56836 > 88.42.111.64.9997: Flags [S], seq 2151201600, win 14600, options [mss 1460], length 0

OK, that looks like the VLAN configuration worked. What does
logread | grep ppp
show?

Also you could try to enable debug in /etc/ppp/options and maybe even store into an existing logfile:

root@turris:~# cat /etc/ppp/options
debug
logfile /srv/pppd_logs/ppp.log
noipdefault
noaccomp
nopcomp
nocrtscts
lock
maxfail 0

but that is not very likely to result in better diagnostics, simply because the initial PPPoE packet exchange does not work.

Tue Feb  1 20:23:22 2022 daemon.err insmod: module is already loaded - ppp_generic
Tue Feb  1 20:23:22 2022 daemon.err insmod: module is already loaded - pppox
Tue Feb  1 20:23:22 2022 daemon.err insmod: module is already loaded - pppoe
Tue Feb  1 20:23:22 2022 daemon.info pppd[2877]: Plugin rp-pppoe.so loaded.
Tue Feb  1 20:23:22 2022 daemon.info pppd[2877]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Tue Feb  1 20:23:22 2022 daemon.notice pppd[2877]: pppd 2.4.8 started by root, uid 0
Tue Feb  1 20:23:22 2022 daemon.debug pppd[2877]: Send PPPOE Discovery V1T1 PADI session 0x0 length 12
Tue Feb  1 20:23:22 2022 daemon.debug pppd[2877]:  dst ff:ff:ff:ff:ff:ff  src 00:20:da:86:23:75
Tue Feb  1 20:23:22 2022 daemon.debug pppd[2877]:  [service-name] [host-uniq  00 00 0b 3d]
Tue Feb  1 20:23:27 2022 daemon.debug pppd[2877]: Send PPPOE Discovery V1T1 PADI session 0x0 length 12
Tue Feb  1 20:23:27 2022 daemon.debug pppd[2877]:  dst ff:ff:ff:ff:ff:ff  src 00:20:da:86:23:75
Tue Feb  1 20:23:27 2022 daemon.debug pppd[2877]:  [service-name] [host-uniq  00 00 0b 3d]
Tue Feb  1 20:23:32 2022 daemon.debug pppd[2877]: Send PPPOE Discovery V1T1 PADI session 0x0 length 12
Tue Feb  1 20:23:32 2022 daemon.debug pppd[2877]:  dst ff:ff:ff:ff:ff:ff  src 00:20:da:86:23:75
Tue Feb  1 20:23:32 2022 daemon.debug pppd[2877]:  [service-name] [host-uniq  00 00 0b 3d]
Tue Feb  1 20:23:37 2022 daemon.warn pppd[2877]: Timeout waiting for PADO packets
Tue Feb  1 20:23:37 2022 daemon.err pppd[2877]: Unable to complete PPPoE Discovery
Tue Feb  1 20:23:37 2022 daemon.info pppd[2877]: Exit

.

Plugin rp-pppoe.so loaded.
RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Send PPPOE Discovery V1T1 PADI session 0x0 length 12
 dst ff:ff:ff:ff:ff:ff  src 00:20:da:86:23:75
 [service-name] [host-uniq  00 00 0d 62]
Send PPPOE Discovery V1T1 PADI session 0x0 length 12
 dst ff:ff:ff:ff:ff:ff  src 00:20:da:86:23:75
 [service-name] [host-uniq  00 00 0d 62]
Send PPPOE Discovery V1T1 PADI session 0x0 length 12
 dst ff:ff:ff:ff:ff:ff  src 00:20:da:86:23:75
 [service-name] [host-uniq  00 00 0d 62]
Timeout waiting for PADO packets
Unable to complete PPPoE Discovery

I also notice the following in the tcpdump:

21:01:56.284305 84:c1:c1:7d:46:9b (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 60: vlan 835, p 2, ethertype ARP, Request who-has x.x.x.x tell x.x.x.y, length 42

I contacted my provider and the told me to set WAN IP address with x.x.x.y / 255.255.255.254 do you know how can I do it ?

I think I'm making some progress... I setup the wan interface with a static IP and now from TCPDUMP seems that something has been transmitted over the network

config interface 'wan'
        option keepalive '1000 60'
        option device 'dsl0.835'
        option proto 'static'
        option ipaddr 'x.x.x.x'
        option netmask '255.255.255.254'

The provider also gave me a pool of static IP address different from the WAN Address, is it correct to set this way ?

config interface 'wan6'
        option device '@wan'
        option proto 'static'
        option netmask '255.255.255.252'
        option gateway 'x.y.z.w'
        option ipaddr 'x.y.z.j'

How to translate an IPv4 address to an IPv6 address...

Did they tell you to use 255.255.255.252 for IPv6?

This would imply you are on a fixed/static public IPv4 which effortlessly explains why PPPoE negotiation did not succeed (if no server on the ISPs end expects/serves your link via PPPoE you will get exactly what you saw, no response to the PADI requests). And I can ping your address from my side, so your router has internet connectivity.

That looks somewhat wrong, 255.255.255.252 is clearly an IPv4 netmask which will not work for IPv6 (IPv6 addresses/masks are 128bit, IPv4 ones only 32bit)...

I would suggest you redact your static (and very public) IPv4 WAN address in your posts above.

There is also a post that quotes it as well.

Makes you vulnerable to a DDoS attack.

1 Like

While I do not think that security by obscurity generally works, here the true IP seems not really required or helpful, so I edited my citation. If the issue is solved and your internet is working now, and you are concerned about exposing IPs, maybe we should ask the admins to delete a few posts completely and just put a summary post at the end describing the issue and eventual solution?

I asked the mods to redact them.

2 Likes