This (my) repository has been written against OpenWrt from four years and at least two major versions ago. In the meantime, LuCI's and collectd's JS framework has changed. If someone feels the urge to adapt it to current LuCI, I wholeheartedly welcome forks, and I'm not opposed to even hand over development to someone else. I myself can't do it anymore; where I live now I couldn't even get DSL if I wanted to.
Hey @takimata, thank you very much for your hard work and effort. - I was not really sure, if I need that to collect the errors and send these information to the DSLAM (MSAN) for a better working vectoring-network. I have still complete cuts at least once a day and the snr is drifting the whole day. Wireguard-Connections for live-tv streaming for my enigma2 Receivers are often laggy. So I still try since 10 years to get a stable performant and sufficent internet-connection. I am actually very deperated about the whole situation at me. I tried diffrent devices: BT5 Hub 5A, FritzBox3370, 7360, EasyBox 904 (Arcadyan device).
Unfortunately I canāt get a stable situation and have also newer devices like NBG7815, Asus AX6000 and MT7621 devices which was the idea could do the calculating stuff or would love to use this as main router. Unfortunately especially because of port-forwarding and double nat there is always the situation that I need to use the old devices with the integrated DSL-modem.
So I use a FB7520 under OpenWrt configured as bridged-modem, with an OpenWrt router behind and no double NAT....
I would urgently recommend upgrading to at least 23.05 (you should go for 24.10 really, especially if you're using the device as an edge router). 21.02 does not yet contain important fixes that prevent vectoring lines from deteriorating.
3 Likes
+1! That is spot on.
To quote from the top post:
Update 2022
If you're using a DSL line with vectoring, make sure that your're using at least 22.03-rc4 (or a current master build), before testing different firmware versions. Recent OpenWrt versions have the Lantiq vectoring driver built in, which is needed for a stable vectoring connection.
1 Like
Can you explain the bridge-mode more in detail? - I donāt understand how to prevent double-nat. Maybe I can use the box just as modem. If itās to much off topic, I would love to get a PM. - Thanks a lot guys.
I would update, but it has to work from remote. I have access from WAN and LAN to the 3370, but I canāt be in presence at the place for a while. I can remotly switch off the power supply, but canāt hold any buttons on the device.
Easy, the modem simply operates as L2-Bridge between DSL0.7 and eth0.7 and may router is connected to eth0 via its own eth2.7 and handles my ISP's PPPoE (but that would be similar for DHCP or ds-lite).
An L2-bridge is essentially a switch, and NAT is an L3/L4 function, so the brodge simply does not touch the ip headers at all.
Likely yes, but really update it to beyond OpenWrt22 to get vectoring operational as it should be.
I would update, but it has to work from remote. I have access from WAN and LAN to the 3370, but I canāt be in presence at the place for a while. I can remotly switch off the power supply, but canāt hold any buttons on the device.
Well, to update the firmware I would definitively recommend feet on the ground and eyes and hands that you can instruct from remote. Especially if you want to switch from full router mode to bridged modem mode...
Do you think I can update to openwrt 23.05 or 24.10 from remote? I have a second dsl-access over LAN2/WAN to the device and the wireguard-tunnel through DSL. - So I have at least one fallbackā¦
Or can we fix the vectoring-issue within the old firmware?
I would caution against that... in principle updating OpenWrt mostly works well in place, but since OpenWrt21 quite some things have changed so I would recommend a fresh start with a clean OpenWrt24 and that likely will not work remotely.
Hrm, so if this allows you to reliably reach one of the LAN ports of the modem you are considerung to update that would help a bit, but personally I still would not do this remotely.
I do not think this is easily possible as the issue sits in a kernel driver.
When is the next time you can/want to visit that site and how far is it away, if I might ask?
Hey @moeller0 thanks a lot!
I plan to go there in two weeks, maybe earlier, but not planned yet. - By the way, as mentioned I also use an EasyBox904 on an other DSL with Vectoring 100/40 from a local provider called Habnet. Unfortunately the dual-stack ipv6 is there not workingā¦ I use the builds of @Zuzia , but I guess he tries to prevent dual-stack issues. 
- Also I have a bunch of BT Hub 5 Type A. - Maybe I can already prepare a bunch of devices for that go. - Also there are two 7412, a 7360v2, 7560 in my old boxes here aroundā¦
Especially the BT 5 Hub Type A have old images like 18.06 @maurer and an openwrt 19.07. I stuck with that because I read a lot of performance issues and DSA-troubleā¦ So if you can give me good instructions how to proceedā¦ PM is also very welcome for off-topics. - Thanks a lot!
Yes that should be achievable...
BTW, here is the /etc/config/network from y old BTHH5a that implements bridge-mode. Note I used the red port of the BTHH5a to connect to my real router, and on that router I used VLAN7 for internet access and VLAN2 for accessing the LAN side of the BTHH5a...
This config likely is a bit crufty and I am not using it for a few years now, but it should illustrate how to proceed to achieve a bridged-modem:
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 'fdd7:1458:e823::/48'
config atm-bridge 'atm'
option vpi '1'
option vci '32'
option encaps 'llc'
option payload 'bridged'
option nameprefix 'dsl'
config dsl 'dsl'
option annex 'b'
option xfer_mode 'ptm'
option line_mode 'vdsl'
option ds_snr_offset '0'
option tone 'bv'
option firmware '/etc/config/vr9-B-dsl.fb7490-07.28-5.9.1.4.0.7.bin'
config device
option name 'br-lan'
option type 'bridge'
list ports 'dsl0.7'
list ports 'lan1'
list ports 'lan2'
list ports 'lan3'
list ports 'lan4'
list ports 'wan'
config device
option name 'lan1'
option macaddr 'c8:91:f9:30:88:88'
config device
option name 'lan2'
option macaddr 'c8:91:f9:30:88:88'
config device
option name 'lan3'
option macaddr 'c8:91:f9:30:88:88'
config device
option name 'lan4'
option macaddr 'c8:91:f9:30:88:88'
config interface 'lan'
option proto 'static'
option netmask '255.255.255.0'
option ip6assign '60'
option ipaddr '192.168.100.1'
option device 'br-lan.2'
config interface 'wan'
option device 'dsl0'
option proto 'none'
config interface 'wan6'
option device '@wan'
option proto 'dhcpv6'
config device
option type 'bridge'
option name 'br-modem2wan'
option bridge_empty '1'
list ports 'br-lan.7'
config interface 'modem'
option proto 'none'
option device 'br-modem2wan'
option force_link '1'
option defaultroute '0'
option peerdns '0'
option delegate '0'
config bridge-vlan
option device 'br-lan'
option vlan '2'
list ports 'lan1'
list ports 'lan2'
list ports 'lan3'
list ports 'lan4'
list ports 'wan:t'
config bridge-vlan
option device 'br-lan'
option vlan '7'
list ports 'dsl0.7:u*'
list ports 'wan:t'
config bridge-vlan
option device 'br-modem2wan'
option vlan '7'
list ports 'br-lan.7:t*'
config device
option type '8021q'
option ifname 'wan'
option vid '7'
option name 'wan.7'
config device
option type '8021q'
option ifname 'dsl0'
option vid '7'
option name 'dsl0.7'
1 Like
May I ask why we use openwrt for just a āmodemā instead of using the fritzbox or any ordinary OEM-device to connect to the internet? If there is a DMZ you can put that WAN-IP of the actual openwrt-device, donāt you? And does your config handle dual-stack (IPv4 and IPv6)?
I can only speak for myself here, I like openwrt on the modem because FritzOS lost the capability years ago to be easily configured as bridged-modem.
And yes, that L2 bridge does not care about L3 and I have this working with O2's dual stack on a telekom dsl link.
1 Like
L3 managed switch ,AP with fast roaming , DSL modem with support from mini jumbo frames. All in same time like you won't find that in OEM
The F!B7412 and EB904xDSL are better avoided, the F!B7560 isn't supported in the first place. The bthub5a and the F!B 7360 should be fine, the bthub5a being the best of this bunch (best wireless, not relevant as mere modem though).
Why I used it as a modem: The XRX200 modem is fairly capable, but its CPU is not. I remember my nominal 100 mbit line having been qualitatively high and slightly overprovisioned, it synched at something like 108 mbit, and the FritzBox had no problem bridging that full speed it to the connected x86 router. Had I used it as a router, though, it would not have been able to even route the nominal 100 mbit and would have tapped out somewhere slightly above 90 mbit.
1 Like