VDSL connection on the flint 2 using the allnet all-bm100vdsl2v Modem

Router
1

Hello Dear Forum,

i recently bought a Flint 2 Router to use in combination with the Allnet All-bm100VDSL2V Modem. I just moved and chose NetCologne as a provider, using VDSL. I have configured the Modem in Bridge Mode and used PPPoE with the Username and Password my provider provided as well as the required VLAN-Tag. After trying to connect for around 20-30 seconds the process gets discarded and then starts anew. I have talked with my provider and on their system all of the connection attempts have been marked as successful, so the dialing has worked as intended using PPPoE. I have not put in the authentications nor the Vland-Tag into the modem directly, so the transmission from the Router must work.

So there seems to be a problem with the handshake between the router and the modem.

I have tried both wan ports on the router with no success, putting a network switch between the router and the modem as well as reducing MTU to 1480, all of which did not impact the process.

I know the Modem is pretty old and buying a good modern one (like the DrayTek Vigor167) would fix it, but if anyone has an idea how to get it to work with the Allnet modem i would really appreciate it :slight_smile: (ps: I only have a 100mbit line anyway, so the modem is enough for my needs, if i get it to work).

Thanks in advance to anyone taking time to read or reply to this post, i wish you a great rest of the day.

Here are the Logs of the Flint 2, running Firmware version 4.11.0:

Thu Oct  1 23:38:49 2026 daemon.notice netifd: Interface 'secondwan' is now down
Thu Oct  1 23:38:49 2026 kern.info kernel: [179065.809208] mt7530 mdio-bus:1f lan1: Link is Down
Thu Oct  1 23:38:49 2026 daemon.info avahi-daemon[10106]: Interface lan1.IPv6 no longer relevant for mDNS.
Thu Oct  1 23:38:49 2026 daemon.info avahi-daemon[10106]: Leaving mDNS multicast group on interface lan1.IPv6 with address fe80::9683:c4ff:feda:abfa.
Thu Oct  1 23:38:49 2026 daemon.info avahi-daemon[10106]: Withdrawing address record for fe80::9683:c4ff:feda:abfa on lan1.
Thu Oct  1 23:38:49 2026 daemon.notice netifd: Interface 'secondwan' is disabled
Thu Oct  1 23:38:49 2026 kern.info kernel: [179065.823085] mt7530 mdio-bus:1f lan1: configuring for phy/sgmii link mode
Thu Oct  1 23:38:49 2026 kern.info kernel: [179065.830181] 8021q: adding VLAN 0 to HW filter on device lan1
Thu Oct  1 23:38:49 2026 daemon.notice netifd: Interface 'secondwan' is enabled
Thu Oct  1 23:38:49 2026 daemon.notice netifd: Interface 'secondwan' is setting up now
Thu Oct  1 23:38:49 2026 daemon.notice netifd: VLAN 'lan1.7' link is down
Thu Oct  1 23:38:49 2026 daemon.notice netifd: Interface 'secondwan' has link connectivity loss
Thu Oct  1 23:38:49 2026 daemon.notice netifd: Network device 'lan1' link is down
Thu Oct  1 23:38:49 2026 daemon.notice netifd: Interface 'secondwan' is now down
Thu Oct  1 23:38:49 2026 daemon.notice netifd: Interface 'secondwan' is disabled
Thu Oct  1 23:38:49 2026 kern.info kernel: [179065.922556] mt7530 mdio-bus:1f lan1: configuring for phy/sgmii link mode
Thu Oct  1 23:38:49 2026 kern.info kernel: [179065.929677] 8021q: adding VLAN 0 to HW filter on device lan1
Thu Oct  1 23:38:49 2026 daemon.notice netifd: Interface 'secondwan' is enabled
Thu Oct  1 23:38:50 2026 user.notice kmwan: config json str={ "op": 3, "data": { "cells": [ "secondwan" ] } }
Thu Oct  1 23:38:50 2026 user.notice firewall: Reloading firewall due to ifdown of secondwan ()
Thu Oct  1 23:38:50 2026 daemon.info dnsmasq[16366]: read /etc/hosts - 12 names
Thu Oct  1 23:38:50 2026 daemon.info dnsmasq[16366]: read /tmp/hosts/dhcp.cfg01411c - 4 names
Thu Oct  1 23:38:50 2026 daemon.info dnsmasq-dhcp[16366]: read /etc/ethers - 0 addresses
Thu Oct  1 23:38:52 2026 kern.info kernel: [179068.316339] mt7530 mdio-bus:1f lan1: Link is Up - 1Gbps/Full - flow control rx/tx
Thu Oct  1 23:38:52 2026 kern.info kernel: [179068.323936] IPv6: ADDRCONF(NETDEV_CHANGE): lan1: link becomes ready
Thu Oct  1 23:38:52 2026 daemon.notice netifd: Network device 'lan1' link is up
Thu Oct  1 23:38:52 2026 daemon.notice netifd: VLAN 'lan1.7' link is up
Thu Oct  1 23:38:52 2026 daemon.notice netifd: Interface 'secondwan' has link connectivity
Thu Oct  1 23:38:52 2026 daemon.notice netifd: Interface 'secondwan' is setting up now
Thu Oct  1 23:38:53 2026 daemon.info avahi-daemon[10106]: Joining mDNS multicast group on interface lan1.IPv6 with address fe80::9683:c4ff:feda:abfa.
Thu Oct  1 23:38:53 2026 daemon.info avahi-daemon[10106]: New relevant interface lan1.IPv6 for mDNS.
Thu Oct  1 23:38:53 2026 daemon.info avahi-daemon[10106]: Registering new address record for fe80::9683:c4ff:feda:abfa on lan1.*.
Thu Oct  1 23:39:22 2026 daemon.err insmod: module is already loaded - slhc
Thu Oct  1 23:39:22 2026 daemon.err insmod: module is already loaded - ppp_generic
Thu Oct  1 23:39:22 2026 daemon.err insmod: module is already loaded - pppox
Thu Oct  1 23:39:22 2026 daemon.err insmod: module is already loaded - pppoe
Thu Oct  1 23:39:22 2026 daemon.info pppd[7739]: Plugin rp-pppoe.so loaded.
Thu Oct  1 23:39:22 2026 daemon.info pppd[7739]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Thu Oct  1 23:39:22 2026 daemon.notice pppd[7739]: pppd 2.4.8 started by root, uid 0
Thu Oct  1 23:39:37 2026 daemon.warn pppd[7739]: Timeout waiting for PADO packets
Thu Oct  1 23:39:37 2026 daemon.err pppd[7739]: Unable to complete PPPoE Discovery
Thu Oct  1 23:39:37 2026 daemon.info pppd[7739]: Exit.
2

The log fails during PPPoE discovery, before username/password authentication: Flint 2 sends discovery requests but receives no PADO response. MTU changes will not affect this stage.

Check where VLAN 7 is applied. It must normally be handled once:

  1. If the Allnet bridge inserts VLAN 7, remove the VLAN ID from Flint 2’s PPPoE settings.
  2. If the Allnet bridge transparently passes Ethernet frames, keep VLAN 7 on Flint 2 and ensure the modem’s bridge/PTM configuration permits tagged frames rather than filtering or adding another tag.

Testing these two configurations separately will determine whether this is a VLAN placement/double-tagging issue. If neither receives PADO, please provide the Flint 2 firmware version and clarify whether VLAN 7 is configured anywhere in the Allnet modem; those details determine the next diagnostic step.

This reply was generated by AI. Please verify its accuracy.

GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.

4

Hi,

Thank you for sharing the detailed information and logs.

From the logs, the Flint 2 is not receiving a PADO response during PPPoE discovery, so the connection cannot proceed to the authentication stage.

Would you mind trying the following configuration to see if it helps?

  1. Configure VLAN 7 on the ALLNET modem in Bridge Mode.
    You can refer to this ALLNET guide for your modem model:
    https://www.allnet.de/ftp-downloads/joerg/BM100%2B126AS3_Bridge%2BVLAN.pdf

  2. Remove VLAN ID 7 from the Flint 2 PPPoE settings, while keeping your PPPoE username and password unchanged, Then try connecting again.

Thank you for your patience and cooperation.