Network troubles: only IPv6 pages loading with GL-iNet AX1800 & PPPoE [swapped for FritzBox solved DS-Lite issue]

Hello!
I got myself a Gl.inet AX1800 (Flint) router and a Zyxel VMG3006-D70A modem for my home network, dialing into my ISP via PPPoE. I am able to load 'established websites' like google.com, instagram.com on WiFi and cable connected client devices but only few other sites.
I spent two weeks trying to figure this out by myself but I've to admit that I'm out of my depths here. Last time set up a network manually was a 56kbps modem... :disguised_face:
I intend to set up a basic home network:
Modem <-> Router <-> Client devices (desktop, laptop, smartphones)
I hope I can present this case in a coherent fashion with all relevant details right away.
I appreciate any help as this connection needs to be operational rather soon.
Thank you!

ISP is WinSIM / Drillisch GmbH, recognized by Speedtests as 1&1 Versatel Deutschland GmbH (Guten Tag!)
-- Their settings are:
---- LAN tag 7 [check, set in modem]
---- Native IPv6 [check, set in router]
---- IPv4 pver DS-Lite [I could not find info on how to set this!]
---- I see in their documentation that other Fritz Boxes have a p-bit set to 0, my modem mentions it and shows the Hex table but I don't know if and how I set the p-bit. Is it relevant at all?

Modem is Zyxel VMG3006-D70A
-- Modem is not branded, not from a provider, latest firmware installed from 2022
-- VLAN tag set to 7 for the WAN facing LAN port
-- Default IP tables, 192.168.100.1, Subnet 255.255.255.0

Router is GL.inet AX1800
-- 4.5.16 stable firmware
-- no VLAN tag is set in the PPPoE connection, it dials in
-- IPv6 activated, set to Native as requested by ISP, DNS acquisition method: Automatic
-- MAC address factory default
-- Router IP default: 192.168.8.1 | Netmask default: 255.255.255.0
-- Router DHCP Server enabled, from 192.168.8.50 to 192.168.8.249
-- If I set ethernet Status Track on 'both ipv4 & ipv6' or 'ipv6', the router becomes inaccessible from my desktop and can't ssh into it either through its 192.168.8.1 IP
-- DNS -> override DNS Settings for All Clients can both be Encrypted DNS or Automatic (DNS from Ethernet (IPv6): 2001:1438:2:4::8,2001:1438:2:3::8), yields the same result (=see below, what works)

What works:
-- The router is calling successfully with its PPPoe credentials into the ISP
-- I can open well established websites like google.com, instagram.com (web interface and the app via wifi connected devices) with WiFi and cable connected devices
-- I can run a (Vodafone) speedtest: 272Mbit/s down, 44Mbit, 8ms ping, up which is expected
-- Diagnostic results from Luci's network utilities:
---- IPv4 Ping: PING openwrt.org (64.226.122.113): 56 data bytes | ping: sendto: Network unreachable
---- IPv6 Ping: 5 packets transmitted, 5 packets received, 0% packet loss | round-trip min/avg/max = 7.922/8.328/9.211 ms
---- IPv4 traceroutes: traceroute: can't connect to remote host (64.226.122.113): Network unreachable
---- IPv6 traceroutes: traceroute to openwrt.org (2a03:b0c0:3:d0::1a51:c001), 30 hops max, 64 byte packets
---- NS lookup: Server: 127.0.0.1 | Address: 127.0.0.1#53 | Name: openwrt.org | Address 1: 64.226.122.113 | Address 2: 2a03:b0c0:3:d0::1a51:c001

Here are my blind spot and the things I have not changed:
-- I have not set firewall rules
-- I have not manually entered DNS
-- No Drop-in Gateway
-- I have no set any: port forwards, open ports on router,DMZ
-- No address reservation
-- No static IPs set for client devices
-- I avoided the 'The interface is connected but the internet can't be accessed.' by flipping Multi-WAN -> Ethernet -> to: 'Internet always available when the interface is connected'
-- I see in the logs:
Wed Jul 3 12:19:24 2024 daemon.warn dnsmasq-dhcp[9208]: DHCP packet received on eth0 which has no address
...and I sense that it is important but here is where I can't progress further by myself.

I appreciate any help in this matter! :pray:

Guten Tag :wave:t2:

For me, this sounds like you can only reach IPv6 addresses.
So it's not DNS, but IP instead. Can you please disable IPv6?

1 Like

I have disable IPv6 and attempt a redial, it seems there is no connection established. It fails and loops for ten minutes now:

My logs show this since hangup and new dial:

Wed Jul 3 13:06:36 2024 daemon.notice pppd[5096]: Modem hangup
Wed Jul 3 13:06:36 2024 daemon.notice pppd[5096]: Connection terminated.
Wed Jul 3 13:06:36 2024 daemon.info pppd[5096]: Sent PADT
Wed Jul 3 13:06:36 2024 daemon.info pppd[5096]: Exit.
Wed Jul 3 13:06:36 2024 daemon.notice netifd: Interface 'wan' is now down
Wed Jul 3 13:06:36 2024 daemon.notice netifd: Interface 'wan' is disabled
Wed Jul 3 13:06:36 2024 daemon.notice netifd: Interface 'wan' is enabled
Wed Jul 3 13:06:36 2024 daemon.notice netifd: Interface 'wan' is setting up now
Wed Jul 3 13:06:36 2024 daemon.notice netifd: Network device 'eth0' link is down
Wed Jul 3 13:06:36 2024 daemon.notice netifd: Interface 'wan' has link connectivity loss
Wed Jul 3 13:06:36 2024 daemon.err odhcpd[3391]: setsockopt(SO_BINDTODEVICE): No such device
Wed Jul 3 13:06:36 2024 daemon.err odhcpd[3391]: setsockopt(SO_BINDTODEVICE): No such device
Wed Jul 3 13:06:36 2024 daemon.notice netifd: Interface 'wan' is now down
Wed Jul 3 13:06:36 2024 daemon.notice netifd: Interface 'wan' is disabled
Wed Jul 3 13:06:36 2024 daemon.notice netifd: Interface 'wan' is enabled
Wed Jul 3 13:06:36 2024 daemon.err odhcpd[3391]: setsockopt(SO_BINDTODEVICE): No such device
Wed Jul 3 13:06:36 2024 daemon.err odhcpd[3391]: setsockopt(SO_BINDTODEVICE): No such device
Wed Jul 3 13:06:36 2024 user.notice firewall: Reloading firewall due to ifdown of wan ()
Wed Jul 3 13:06:37 2024 daemon.notice netifd: Network device 'eth0' link is up
Wed Jul 3 13:06:37 2024 daemon.notice netifd: Interface 'wan' has link connectivity
Wed Jul 3 13:06:37 2024 daemon.notice netifd: Interface 'wan' is setting up now
Wed Jul 3 13:06:37 2024 kern.info kernel: [ 9352.783923] nss-dp 3a001000.dp1 eth0: PHY Link up speed: 1000
Wed Jul 3 13:06:37 2024 daemon.err insmod: module is already loaded - slhc
Wed Jul 3 13:06:37 2024 daemon.err insmod: module is already loaded - ppp_generic
Wed Jul 3 13:06:37 2024 daemon.err insmod: module is already loaded - pppox
Wed Jul 3 13:06:37 2024 daemon.err insmod: module is already loaded - pppoe
Wed Jul 3 13:06:37 2024 daemon.info pppd[6067]: Plugin rp-pppoe.so loaded.
Wed Jul 3 13:06:37 2024 daemon.info pppd[6067]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Wed Jul 3 13:06:37 2024 daemon.notice pppd[6067]: pppd 2.4.8 started by root, uid 0
Wed Jul 3 13:06:37 2024 daemon.info pppd[6067]: PPP session is 45885
Wed Jul 3 13:06:37 2024 daemon.warn pppd[6067]: Connected to 18:3d:5e:34:1c:3a via interface eth0
Wed Jul 3 13:06:37 2024 kern.info kernel: [ 9352.987174] pppoe-wan: renamed from ppp0
Wed Jul 3 13:06:37 2024 daemon.info pppd[6067]: Renamed interface ppp0 to pppoe-wan
Wed Jul 3 13:06:37 2024 daemon.info pppd[6067]: Using interface pppoe-wan
Wed Jul 3 13:06:37 2024 daemon.notice pppd[6067]: Connect: pppoe-wan <--> eth0
Wed Jul 3 13:06:37 2024 user.notice kmwan: config json str={ "op": 3, "data": { "cells": [ "wan" ] } }
Wed Jul 3 13:06:41 2024 daemon.info pppd[6067]: Remote message: [UI-SBR:XXXXXX,XXXXX;UI-LINEID:WinSIM.XXXXX;]
Wed Jul 3 13:06:41 2024 daemon.notice pppd[6067]: PAP authentication succeeded
Wed Jul 3 13:06:41 2024 daemon.notice pppd[6067]: peer from calling number XX:XX:XX:XX:XX:XX authorized
Wed Jul 3 13:07:41 2024 daemon.info pppd[6067]: LCP terminated by peer
Wed Jul 3 13:07:41 2024 daemon.notice pppd[6067]: Modem hangup
Wed Jul 3 13:07:41 2024 daemon.notice pppd[6067]: Connection terminated.
Wed Jul 3 13:07:41 2024 daemon.info pppd[6067]: Sent PADT
Wed Jul 3 13:07:41 2024 daemon.info pppd[6067]: Exit.
Wed Jul 3 13:07:41 2024 daemon.notice netifd: Interface 'wan' is now down
Wed Jul 3 13:07:41 2024 daemon.notice netifd: Interface 'wan' is disabled
Wed Jul 3 13:07:41 2024 daemon.notice netifd: Interface 'wan' is enabled
Wed Jul 3 13:07:41 2024 daemon.notice netifd: Interface 'wan' is setting up now
Wed Jul 3 13:07:41 2024 daemon.notice netifd: Network device 'eth0' link is down
Wed Jul 3 13:07:41 2024 daemon.notice netifd: Interface 'wan' has link connectivity loss
Wed Jul 3 13:07:41 2024 daemon.err odhcpd[3391]: setsockopt(SO_BINDTODEVICE): No such device
Wed Jul 3 13:07:41 2024 daemon.err odhcpd[3391]: setsockopt(SO_BINDTODEVICE): No such device
Wed Jul 3 13:07:41 2024 daemon.notice netifd: Interface 'wan' is now down
Wed Jul 3 13:07:41 2024 daemon.notice netifd: Interface 'wan' is disabled
Wed Jul 3 13:07:41 2024 daemon.notice netifd: Interface 'wan' is enabled
Wed Jul 3 13:07:41 2024 daemon.err odhcpd[3391]: setsockopt(SO_BINDTODEVICE): No such device
Wed Jul 3 13:07:41 2024 daemon.err odhcpd[3391]: setsockopt(SO_BINDTODEVICE): No such device
Wed Jul 3 13:07:41 2024 user.notice firewall: Reloading firewall due to ifdown of wan ()
Wed Jul 3 13:07:42 2024 daemon.notice netifd: Network device 'eth0' link is up
Wed Jul 3 13:07:42 2024 daemon.notice netifd: Interface 'wan' has link connectivity
Wed Jul 3 13:07:42 2024 daemon.notice netifd: Interface 'wan' is setting up now
Wed Jul 3 13:07:42 2024 kern.info kernel: [ 9417.782717] nss-dp 3a001000.dp1 eth0: PHY Link up speed: 1000
Wed Jul 3 13:07:42 2024 daemon.err insmod: module is already loaded - slhc
Wed Jul 3 13:07:42 2024 daemon.err insmod: module is already loaded - ppp_generic
Wed Jul 3 13:07:42 2024 daemon.err insmod: module is already loaded - pppox
Wed Jul 3 13:07:42 2024 daemon.err insmod: module is already loaded - pppoe
Wed Jul 3 13:07:42 2024 daemon.info pppd[7044]: Plugin rp-pppoe.so loaded.
Wed Jul 3 13:07:42 2024 daemon.info pppd[7044]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Wed Jul 3 13:07:42 2024 daemon.notice pppd[7044]: pppd 2.4.8 started by root, uid 0
Wed Jul 3 13:07:42 2024 daemon.info pppd[7044]: PPP session is 7638
Wed Jul 3 13:07:42 2024 daemon.warn pppd[7044]: Connected to XX:XX:XX:XX:XX:XX via interface eth0
Wed Jul 3 13:07:42 2024 kern.info kernel: [ 9417.975498] pppoe-wan: renamed from ppp0
Wed Jul 3 13:07:42 2024 daemon.info pppd[7044]: Renamed interface ppp0 to pppoe-wan
Wed Jul 3 13:07:42 2024 daemon.info pppd[7044]: Using interface pppoe-wan
Wed Jul 3 13:07:42 2024 daemon.notice pppd[7044]: Connect: pppoe-wan <--> eth0
Wed Jul 3 13:07:42 2024 user.notice kmwan: config json str={ "op": 3, "data": { "cells": [ "wan" ] } }
Wed Jul 3 13:07:46 2024 daemon.info pppd[7044]: Remote message: [UI-SBR:XXXXXX,XXXXX;UI-LINEID:WinSIM.2GJS6;]
Wed Jul 3 13:07:46 2024 daemon.notice pppd[7044]: PAP authentication succeeded
Wed Jul 3 13:07:46 2024 daemon.notice pppd[7044]: peer from calling number XX:XX:XX:XX:XX:XX authorized

Meh, so the ISP needs IPv6 for real... but they should provide you some IPv4 address (maybe behind CGNAT) as well.

Can you try to set IPv6 to NAT?

you mean:


?

This is what ISP says in their documentation, I had IPv6 to Native and DNS acquisition to Automatic thusfar.

This is what the logs show - I xxxxxxxxx a bunch of IPs, not sure how sensitive they are at this point. I highlighted a line that sounds important to me and that I have looked up in forums already but I couldn't relate any topic to my case:

ed Jul 3 13:28:14 2024 daemon.info pppd[27289]: PPP session is 56428
Wed Jul 3 13:28:14 2024 daemon.warn pppd[27289]: Connected to 18:3d:5e:34:1c:3a via interface eth0
Wed Jul 3 13:28:14 2024 kern.info kernel: [10650.083568] pppoe-wan: renamed from ppp0
Wed Jul 3 13:28:14 2024 daemon.info pppd[27289]: Renamed interface ppp0 to pppoe-wan
Wed Jul 3 13:28:14 2024 daemon.info pppd[27289]: Using interface pppoe-wan
Wed Jul 3 13:28:14 2024 daemon.notice pppd[27289]: Connect: pppoe-wan <--> eth0
Wed Jul 3 13:28:15 2024 kern.info kernel: [10651.092631] br-lan: port 5(wlan1) entered forwarding state
Wed Jul 3 13:28:16 2024 kern.info kernel: [10651.212630] br-guest: port 1(wlan1-1) entered forwarding state
Wed Jul 3 13:28:17 2024 kern.info kernel: [10652.812600] br-lan: port 3(eth3) entered forwarding state
Wed Jul 3 13:28:18 2024 daemon.info pppd[27289]: Remote message: [UI-SBR:xxxxxxxxx;UI-LINEID:WinSIM.xxxxxxxxx;]
Wed Jul 3 13:28:18 2024 daemon.notice pppd[27289]: PAP authentication succeeded
Wed Jul 3 13:28:18 2024 daemon.notice pppd[27289]: peer from calling number xxxxxxxxx authorized
Wed Jul 3 13:28:18 2024 daemon.notice pppd[27289]: local LL address fe80::xxxx:xxxx:xxxx:xxxx
Wed Jul 3 13:28:18 2024 daemon.notice pppd[27289]: remote LL address fe80::xxxx:xxxx:xxxx:xxxx
Wed Jul 3 13:28:18 2024 daemon.info avahi-daemon[4196]: Joining mDNS multicast group on interface pppoe-wan.IPv6 with address fe80::xxxx:xxxx:xxxx:xxxx
Wed Jul 3 13:28:18 2024 daemon.info avahi-daemon[4196]: New relevant interface pppoe-wan.IPv6 for mDNS.
Wed Jul 3 13:28:18 2024 daemon.info avahi-daemon[4196]: Registering new address record for fe80::xxxx:xxxx:xxxx:xxxx on pppoe-wan..
Wed Jul 3 13:28:18 2024 daemon.info avahi-daemon[4196]: Leaving mDNS multicast group on interface pppoe-wan.IPv6 with address fe80::xxxx:xxxx:xxxx:xxxx.
Wed Jul 3 13:28:18 2024 daemon.info avahi-daemon[4196]: Joining mDNS multicast group on interface pppoe-wan.IPv6 with address 2001:xxxx:xxxx:xxxx:xxxx..
Wed Jul 3 13:28:18 2024 daemon.info avahi-daemon[4196]: Registering new address record for 2001:xxxx:xxxx:xxxx:xxxx. on pppoe-wan.
.
Wed Jul 3 13:28:18 2024 daemon.info avahi-daemon[4196]: Withdrawing address record for fe80::xxxx:xxxx:xxxx:xxxx. on pppoe-wan.
Wed Jul 3 13:28:18 2024 daemon.notice netifd: Network device 'pppoe-wan' link is up
Wed Jul 3 13:28:18 2024 daemon.notice netifd: Interface 'wan6' is enabled
Wed Jul 3 13:28:18 2024 daemon.notice netifd: Network alias 'pppoe-wan' link is up
Wed Jul 3 13:28:18 2024 daemon.notice netifd: Interface 'wan6' has link connectivity
Wed Jul 3 13:28:18 2024 daemon.notice netifd: Interface 'wan6' is setting up now
Wed Jul 3 13:28:18 2024 daemon.notice netifd: Interface 'wan' is now up
Wed Jul 3 13:28:18 2024 kern.err kernel: [10653.276511] ICMPv6: RA: ndisc_router_discovery failed to add default route
Wed Jul 3 13:28:18 2024 user.notice firewall: Reloading firewall due to ifup of wan (pppoe-wan)
Wed Jul 3 13:28:19 2024 daemon.warn odhcpd[26086]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Wed Jul 3 13:28:21 2024 daemon.notice netifd: Interface 'wan6' is now up
Wed Jul 3 13:28:21 2024 daemon.info dnsmasq[27212]: reading /tmp/resolv.conf.d/resolv.conf.auto
Wed Jul 3 13:28:21 2024 daemon.info dnsmasq[27212]: using only locally-known addresses for domain test
Wed Jul 3 13:28:21 2024 daemon.info dnsmasq[27212]: using only locally-known addresses for domain onion
Wed Jul 3 13:28:21 2024 daemon.info dnsmasq[27212]: using only locally-known addresses for domain localhost
Wed Jul 3 13:28:21 2024 daemon.info dnsmasq[27212]: using only locally-known addresses for domain local
Wed Jul 3 13:28:21 2024 daemon.info dnsmasq[27212]: using only locally-known addresses for domain invalid
Wed Jul 3 13:28:21 2024 daemon.info dnsmasq[27212]: using only locally-known addresses for domain bind
Wed Jul 3 13:28:21 2024 daemon.info dnsmasq[27212]: using only locally-known addresses for domain lan
Wed Jul 3 13:28:21 2024 daemon.info dnsmasq[27212]: using nameserver 2001:xxxx:xxxx:xxxx:xxxx.
Wed Jul 3 13:28:21 2024 daemon.info dnsmasq[27212]: using nameserver 2001:xxxx:xxxx:xxxx:xxxx.
Wed Jul 3 13:28:21 2024 daemon.warn dnsmasq[27212]: ignoring nameserver 2001:xxxx:xxxx:xxxx:xxxx. - local interface
Wed Jul 3 13:28:21 2024 user.notice firewall: Reloading firewall due to ifup of wan6 (pppoe-wan)
Wed Jul 3 13:28:22 2024 daemon.warn odhcpd[26086]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Wed Jul 3 13:28:22 2024 daemon.info avahi-daemon[4196]: Leaving mDNS multicast group on interface br-lan.IPv6 with address fe80::xxxx:xxxx:xxxx:xxxx..
Wed Jul 3 13:28:22 2024 daemon.info avahi-daemon[4196]: Joining mDNS multicast group on interface br-lan.IPv6 with address 2001:xxxx:xxxx:xxxx:xxxx..
Wed Jul 3 13:28:22 2024 daemon.info avahi-daemon[4196]: Registering new address record for 2001:xxxx:xxxx:xxxx:xxxx. on br-lan.*.
Wed Jul 3 13:28:22 2024 daemon.info avahi-daemon[4196]: Withdrawing address record for fe80::9683:c4ff:fe18:8edc on br-lan.
Wed Jul 3 13:28:22 2024 daemon.info dnsmasq[27212]: read /etc/hosts - 4 addresses
Wed Jul 3 13:28:22 2024 daemon.info dnsmasq[27212]: read /tmp/hosts/odhcpd - 0 addresses
Wed Jul 3 13:28:22 2024 daemon.info dnsmasq[27212]: read /tmp/hosts/dhcp.cfg01411c - 5 addresses
Wed Jul 3 13:28:22 2024 daemon.info dnsmasq-dhcp[27212]: read /etc/ethers - 0 addresses
Wed Jul 3 13:30:00 2024 daemon.info dnsmasq-dhcp[27212]: DHCPREQUEST(br-lan) 192.168.8.117 xxxx:xxxx:xxxx:xxxx.
Wed Jul 3 13:30:00 2024 daemon.info dnsmasq-dhcp[27212]: DHCPACK(br-lan) 192.168.8.117 xxxx:xxxx:xxxx:xxxx. b550
Wed Jul 3 13:30:04 2024 daemon.info dnsmasq[27212]: exiting on receipt of SIGTERM
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq[29098]: Connected to system UBus
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq[29098]: started, version 2.85 cachesize 150
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq[29098]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth cryptohash DNSSEC no-ID loop-detect inotify dumpfile
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq[29098]: UBus support enabled: connected to system bus
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq-dhcp[29098]: DHCP, IP range 192.168.9.100 -- 192.168.9.249, lease time 12h
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq-dhcp[29098]: DHCP, IP range 192.168.8.50 -- 192.168.8.249, lease time 12h
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq[29098]: using only locally-known addresses for domain test
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq[29098]: using only locally-known addresses for domain onion
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq[29098]: using only locally-known addresses for domain localhost
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq[29098]: using only locally-known addresses for domain local
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq[29098]: using only locally-known addresses for domain invalid
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq[29098]: using only locally-known addresses for domain bind
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq[29098]: using only locally-known addresses for domain lan
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq[29098]: reading /tmp/resolv.conf.d/resolv.conf.auto
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq[29098]: using only locally-known addresses for domain test
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq[29098]: using only locally-known addresses for domain onion
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq[29098]: using only locally-known addresses for domain localhost
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq[29098]: using only locally-known addresses for domain local
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq[29098]: using only locally-known addresses for domain invalid
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq[29098]: using only locally-known addresses for domain bind
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq[29098]: using only locally-known addresses for domain lan
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq[29098]: using nameserver 2001:xxxx:xxxx:xxxx:xxxx.
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq[29098]: using nameserver 2001:xxxx:xxxx:xxxx:xxxx.
Wed Jul 3 13:30:07 2024 daemon.warn dnsmasq[29098]: ignoring nameserver 2001:xxxx:xxxx:xxxx:xxxx. - local interface
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq[29098]: read /etc/hosts - 4 addresses
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq[29098]: read /tmp/hosts/odhcpd - 0 addresses
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq[29098]: read /tmp/hosts/dhcp.cfg01411c - 5 addresses
Wed Jul 3 13:30:07 2024 daemon.info dnsmasq-dhcp[29098]: read /etc/ethers - 0 addresses
Wed Jul 3 13:31:35 2024 daemon.notice hostapd: Station a0:00:00:a0:0a:a0 trying to disassociate, but it is not associated

Do you know if they offer IPv4 communication at all?

Good call, I looked this up just now:
https://www.reddit.com/r/de_EDV/comments/1d8navk/seit_5gumstellung_von_winsim11_probleme_ipv4_geht/?rdt=33131
...and:
https://www.computerbase.de/forum/threads/ds-lite-bei-drillisch-adresse-vom-aftr-gateway-gesucht.2178745/

  • Drillisch hat kein "echtes" Dual Stack, IPv4-Verbindung wird über das DS-Lite-Tunnel aufgebaut
  • DS-Lite Tunnel wird zw. AFTR-Gateway beim Provider und einem Gerät auf der User-Seite augebaut
  • Speedport kann kein DS-Lite, d.h. hier sind nur IPv6-Verbindungen möglich
  • OpenWRT (TP-Link) kann DS-Lite und braucht die Adresse des AFTR-GW, um sich damit zu verbinden
  • AFTR-Adresse wird per DHCP verteil, wobei DHCP-Client ist die Speedport
  • AFTR-Adresse kommt also nich am TP-Link an und muss dort händisch eingetragen werden

For our english readers:

  • Drillisch does not have a "real" dual stack, IPv4 connection is established via the DS-Lite tunnel
  • DS-Lite tunnel is established between the AFTR gateway at the provider and a device on the user side
  • Speedport cannot do DS-Lite, i.e. only IPv6 connections are possible here
  • OpenWRT (TP-Link) can do DS-Lite and needs the address of the AFTR-GW to connect to it
  • AFTR address is distributed via DHCP, whereby the DHCP client is the Speedport
  • AFTR address therefore does not reach the TP-Link and must be entered there manually

In short, after reading those reports from users:

Do I need a FritzBox to use this connection?!
I was all about going full open source with OpenWRT etc. I did not know what I don't know regarding however you call this

Urgh, ich hasse DS-Lite... (Urgh, I hate DS-Lite)

For me this looks like it's not possible out of the box because GL does not have a lot of experience with DS-Lite (@alzhao). You need to manually try to get it working, maybe using this advice: [OpenWrt Wiki] ISP Configurations

1 Like

@admon there's a detailed thread here, DS-Lite configuration; IPv4 NAT & Firewall - Network and Wireless Configuration - OpenWrt Forum

trying to work out if all of that can be applied via the GL-iNet GUI

1 Like

I see.
I found https://openwrt.org/docs/guide-user/network/wan/isp-configurations#vdsl_ds-lite ...a couple of days ago while reading up on ds-lite and I spliced in some of those settings into the router.

Do you think its worthwhile to copy all this, as is, over into /etc/config/network and give it a spin? Obviously entering my own credientials for WinSIM / 1&1

config interface 'wan'
option ifname 'eth0.7'
option proto 'pppoe'
option password 'test123'
option username '1und1/ui1234-567@t-online.de'
option ipv6 '1'

config interface 'wan6'
option proto 'dhcpv6'
option reqaddress 'try'
option reqprefix 'auto'
option ifname 'pppoe-wan'

config interface 'wan4'
option proto 'dslite'
option peeraddr '::'
option ifname 'wan'
option encaplimit 'ignore'
option mtu '0'
option tunlink 'wan6'

I don't think copying everything will work. Not sure tho.

I can't test because my Telekom VDSL is without DS-Lite.
Tomorrow (yey) my connection will be migrated to 1&1, maybe I will get DS-Lite there and maybe I need to fiddle around as well.

1 Like

:heart: I'm happy to see you posting this thread, I saw it myself just yesterday. It means I was on the right track, I just couldn't puzzle it together. I give it a read now

1 Like

If you need anything checked or double checked please let us know, DS-Lite can be a pain.

I went over the r´thread again but I'm not sure what finally fixed the problem (if the issue is the same as mine):

Set the MTU to 1492 instead of default 1500 on IPv6

I did this just now to my WAN pppoe-wan and, for good measures, rebooted the router:

I checked just now, it doesn't change the behaviour, I still only receive IPv6 website traffic.

I don't see a wan6_4 interface janh mentions, and no other interface offers to set/change MTU. They write that firewall settings are not an issue. What am I missing?

-> I'm sorry but at this point I'm a script kiddie again, copy pasting without much comprehension.

cat /etc/config/network < at the bottom

config device
option name 'ds-wan6_4'
option mtu '1452'
option mtu6 '1452'

1 Like

That device wasn't there before. I added it to the network config, here it shows up:


(not showing up under interfaces)

Issue remains.
Should I continue editing the wan and wan6 interfaces, filling in missing options?

I have made these changes, the experience is neither better nor worse. Still no ipv4 available.
Shouldn't the new ds-wan6_4 device be somehow implemented? It's dangling there, not being referenced right now.

Guys, thank you for the help. I cut my losses here and got myself a FritzBox 7590, the connection was up and running within 3 minutes, DS-Lite recognized and set up automatically.
Thank you and good luck!

Well, I have got VDSL by 1&1 now … but they don't DS-Lite' me. :sweat_smile:

1 Like

all the best to you. its looking like this in fritzland:

image

1 Like