DSL, Telekom: how to configure tagged VLAN in reForis?

I have tried to setup a connection from my MOX via my Draytek Vigor 130 (bridge-mode) to a Vodafone network via Telekom DSL lines.

The helpdesk was not helpful at all, they seem to have no idea…

I did all this in LUCI, as it seems to be better for this?

Attempt to use PPPOE on the router

I removed the WAN connection and added a new one.

  1. New connection, named “DSL”, type PPPOE
  2. Device: added manually, eth0 is WAN, I entered eth0.7 for a tagged VLAN
  3. Enter credentials
  4. Under Firewall set it to WAN

Video of the process

Still not working

I have confirmed that my connection was not blocked but still I dont get any messages from Vodafone, no “wrong credentials” like I got before, just a “USER_REQUEST” error.

They couldnt tell me what the issue is either.

I now have 2 options

  • use the modem not in bridge mode but in the PPPOE passthrough, while it contains the credentials. It had this “7” tag for VLAN preset which seems to work
  • try to configure in reForis which might do something different. But reForis is pretty abstracted and shows an unknown API error occured after I removed the WAN device. @n8mahr could you help me here?

What would be the downsides of using the modem in PPOE passthrough instead of bridge mode?

Attempt to use PPPOE passthrough

I have entered the modem UI and instead enabled PPPOE passthrough there and entered the Vodafone credentials here. The VLAN automatically had the Tag 7.

Doing a pingtest from the modem doesnt return anything and the consoles says this:

> vdsl status

  ---------------------- ATU-R Info (hw: annex B, f/w: annex A/B/C) -----------
   Running Mode            :      17A       State                : SHOWTIME
   DS Actual Rate          :100106000 bps   US Actual Rate       : 39926000 bps
   DS Attainable Rate      :102244256 bps   US Attainable Rate   : 39954000 bps
   DS Path Mode            :        Fast    US Path Mode         :        Fast
   DS Interleave Depth     :        1       US Interleave Depth  :        1
   NE Current Attenuation  :       13 dB    Cur SNR Margin       :        6  dB
   DS actual PSD           :     3. 5 dB    US actual PSD        :    12. 7  dB
   NE CRC Count            :        0       FE CRC Count         :      107
   NE ES Count             :        0       FE  ES Count         :        6
   Xdsl Reset Times        :        0       Xdsl Link  Times     :        1
   ITU Version[0]          : fe004452       ITU Version[1]       : 41590000
   VDSL Firmware Version   : 05-07-03-03-00-07   [with Vectoring support]
   Power Management Mode   : DSL_G997_PMS_L0
   Test Mode               : DISABLE
  -------------------------------- ATU-C Info ---------------------------------
   Far Current Attenuation :       15 dB    Far SNR Margin       :        9  dB
   CO ITU Version[0]       : b5004244       CO ITU Version[1]    : 434dc278
   DSLAM CHIPSET VENDOR    : < BDCM >
> wan status

WAN1: Offline, stall=N
 Mode: PPPoE, Up Time=00:00:00
 IP=---, GW IP=---
 TX Packets=965, TX Rate(Bps)=0, RX Packets=0, RX Rate(Bps)=0
 Primary DNS=176.95.16.250, Secondary DNS=176.95.16.251

So WAN is offline, is this only enabled if a client uses it?

MOX setup with PPPOE passthrough

What should I now setup on the MOX? PPOE will require credentials, which I should not need anymore as the modem handles them.

Static IP?

WAN to DHCP client

I tried with what I think is the default

  • interface name WAN
  • connection eth0
  • type DHCP client
  • firewall zone WAN

LUCI shows me IPv4 connected, IPv6 not.

pingtest to www.turris.cz fails on IPv4, on IPv6 I get “bad address”.

reForisConnection Test spins forever, probably also nothing.

I am doing the thing you shouldnt do, a factory reset, as reForis WAN still showed me the API error.

Lets see…

1 Like

LUCI “better”? yes, of course, if you know what you are doing. reForis is just another UI with less options. Meaning - standard stuff should work with less clicks, chances of user error is lower.
BUT - it will throw out errors if you have configured stuff in LUCI already. So you better start over fresh with reForis, or do not use it at all. It´s rather complicated to edit a config with reForis you set up with LUCI to start with.

I´m by now quite sure it´s a problem with your modem, which is 13 years old.
have you flashed the most recent firmware? and, is it even fit for your dsl? it only supports old vdsl2 standards… just saying…

I didnt know VDSL2 is that old.

The modem has recent firmware from 2023, so I assume that should be not optimal but fine.

If it is an issue with the modem, maybe I should just get one of the EasyBoxes and try to lock that down as much as possible

It is kinda hard finding good modems on ebay, it seems most of them are that old

I think at this point you should try to ping IP address not DNS name

1 Like

true, most of them are. and even if they work, they tend to be less than optimized because of old “blobs” / modem instructions.
try with a device from your phone company and you can later switch to a more recent modem that works.
you seem to have a really unusual set up there . Vodafone on TKom dsl is weird to begin with… and then with a 13 year old device. might work, but, as you see, sometimes it does not.

1 Like

The first VDSL2, or as the ITU calls it -G.993.2 are from 2006:
https://1f8a81b9b0707b63-19211.webchannel-proxy.scarabresearch.com/rec/T-REC-G.993.2-200602-S/en

So VDSL2 would be allowed to vote :wink:

Which firmware did you install? I believe there might be one for deutsche telekom, and that is the one you should use…

Anyway, some vigors automatically add vlan7, so please try to change your wan device to eth0 (so try without VLAN7 on the mox)

1 Like

Some dsl routers allow a bridge mode (some drayteks, some speedports, no recent Fritzboxen though) and hence can act as “modem”… and I believe this is also true for the vigor130…

1 Like

The Vigor was used in germany and had the latest normal firmware update.

Nothing language specific.

Yes I set it up on the Vigor now and try to get the MOX to connect to that, as it seems as if it works?

Would the modem be able to do pingtests if it is in PPPoE passthrough mode? Because it wasnt.

And what would I setup on the MOX when it is in passthrough?

Yes but I gave up on that. There were some but I dont know how to find how old they are, and if they dont have similar issues.

If this doesnt work I just get a Fritzbox or the cheap easybox for rental and disable Wifi somehow, even if I need to wrap it in tinfoil.

I tried the vigor in bridge mode, which is what I explained above. But that didnt work either

Mmmh, what ever version that is, in regards to VLAN7. IMHO the likely issue is whether the vigor expects or accepts VLAN tags on its ethernet port and whether it passes these onto the DSL side.

Well bridge mode is conceptually simpler, but what ever works…

the vdsl statusshows that you seem to have established DSAL sync, which is the first challenge…

1 Like

I reset my MOX from the reForis GUI and now cant access it anymore lol.

Might be because I set the static IP to connect to the modem, but I already changed that to be

192.168.1.100/24

Maybe I need to set it to dynamic. The router is there but I cannot connect.

So currently I have no idea if it works as my MOX is not usable XD yay

Well, your PPPoE credentials (make sure to not configure these inside the modem, as most ISPs will not allow a credential set connect multiple times concurrently. But the elephant in the room is still the “who sets the required VLOAN tag”, the modem or the mox? And that is something you likely need to figure out…

BTW since you renamed the wan interface, you might need to add DSL to the wan firewall zone, or better undo that rename and go back to the default (IIRC that would be wan).

1 Like

The issue is I cannot enable the PPPoE Passthrough mode (which may create the VLAN) without entering credentials…

I will see if I can get a newer modem.

The “FRITZ!Box 7530 AX” is the one Vodafone currently offers, and at least the FRITZ!Box 7530 has OpenWRT support. I may be able to add the DSL blob and use that as a router or modem?

(Not a rented router of course)

Or just use a normal router with double NAT.

Well, at that point the modem consumed your one concurrent login at your ISP… you could try entering invalid credentials, which might or might not work, depending on how deep the error is located.

No the 7530AX is a completely different beast from the 7530 without the AX, only the unadorned 7530 is compatible with OpenWrt, the AX IMHO uses a broadcom DSL SoC that is not supported by linux upstream.

Sure, that is always an option… at that point the vigor 130 might work as well and you already own that… other than that, I have an older zyxel vmg1312 BA30 that might work as bridged modem, if you are interested…

2 Likes

The video is a hell of an effort. Thank you very much. I think you might miss a step. In my similar configuration, (PPPoE, HUAWEI-Modem, last mile by telekom, but a differnt ISP, VLAN 7) I created a new device first.

Luci → Network → Interfaces → Devices → “Add Device Configuration” button at the bottom.

My working config looks like this:

After I created this interface, I could choose it in the dropdown-menu for the PPPoE Interface

EDIT:
Your modem says:

State                : SHOWTIME

This means it synchronized with the DSLAM of the telekom. There is no problem on the DSL-Signal.

Bridge-Mode should be the way to go.

This indeed might be an issue.

But: This page says it is supported: Vigor 130 - Using VLAN tag on Router instead of Modem

Maybe, VLAN-tag-insertion also works in bridge-mode? So, the mox just creates the pppoe-connection on an untagged eth0 port which is connected to the lan-port of the modem.

For the purpose of documentation: One can find the manuals for this modem here: Index of /Vigor130/Manual

2 Likes

Thanks!

Update: I reset my MOX and was able to get into the WebUI again.

The initial reForis setup makes setting up such a DSP connection very easy.

But neither in bridge-mode nor in the standard PPPoE passthrough mode was I able to get a connection.

I am not sure what to do. I could just get a Vodafone Easybox, use a standard DHCP WAN and call it a day. Or I get a newer DSL modem and tinker with it again.

Tbh on the modem side this should be fine.

But I am honestly overasked. I made many screenshots of the modem WebUI

Since the modem apparently managed to sync, the biggest hurdle should be solved already, and it is all about VLAN…

I would likely try the following receipe:

and just see how to deal with the VLAN issues. The options I see that might work are:

  1. Modem: set VLAN 7 for VDSL2 under Internet Access >> General Setup
    MOX: set no VLAN for the wan interface

  2. Modem: disable VLAN for VDSL2 under Internet Access >> General Setup
    MOX: set VLAN7 for the wan interface…

as far as I understand one of these alternatives should work…

I would however reset the MOX to defaults as I am not sure renaming the wan interface is a good idea, at least without also making sure the DSL interface also lives in the wan firewall zone.

2 Likes

Update: I got it working, kinda.

Bought a Fritzbox 7590PN, it has presets for all the weird things that providers do. The “modem installationscode” did not work, but username + password worked.

username: vodafone-vdsl.komplett/vbXXXXX
password: the password

I had changed the password (absolutely no reason to do that, they store it in plain text) so I needed to use that.

Now I have the issue that the FB only has 1Gbps LAN ports, i.e. 125 MB/s which is half of what I have.

But if I dont want to use the FB itself…

And disabling wifi on the FB works easily, prioritizing the MOX in LAN works, and the MOX works too.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.