Fritz!Box 7530 and 7490 as Modem+Router combo for 35b Supervectoring

Fritzbox 7490 is not supported yet, but work seems to have progressed quite a fair bit. Some people are currently running tests. See https://github.com/openwrt/openwrt/pull/5075. If the first post is still up to date, DECT / ISDN telephony is or will not be supported, but that is fine, as long as you opt to use this device simply as wifi repeater or dump AP.

Fritzbox 7530 looks even more promising. It is supported already. See https://openwrt.org/toh/avm/avm_fritz_box_7530, except DECT / ISBN is also falls flat.

Your plan to keep the 7530 on stock seems a good plan, if you want to make use of DECT / ISBN. If so, then they will only connect to the 7530, therefore the connection of your DECT devices is capped by distance and capabilities of the 7530 and the quality of your other DECT devices. The 7490 will be irrelevant in that regard.

I am less knowledgeable about Modems, so maybe somebody else can comment on that.

Thanks a lot for the answer, this is already very helpful. I think I'll have to play around with both devices for a bit to see how I can get ISDN / DECT to work, but it's good to know that my general plan should work :smiley:

Keep one of them on stock (probably the 7530, as that one likely gets longer OEM firmware support) to deal with the phone stuff, in IPoE mode these can work fine as SIP pbx/ ATA and DECT base behind an OpenWrt router. There is no way to get DECT or the other phone features working on OpenWrt.

I would switch the 7530 to OpenWrt and operate it as modem-router, and use the 7490 on its stock firmware as VoIP/DECT base-station. The 7490's MIPS CPU is getting long in the tooth...

2 Likes

As far as I can tell, OpenWRT for the 7530 doesn't have support for the DSL modem, so I believe I have to keep this on on stock because the 7490 doesn't have support for VDSL2+ supervectoring.

You will need to build your own: see

for instructions.

Thanks a lot, that's how I'll try to do it.

I would like to start by just setting up the DSL connection and basic routing, the phones aren't that important for now. Is there any guide how to set up OpenWRT with an external modem that would work for my case? I remember reading that you should reset the Fritz!Box you want to use as a modem (7530 in my case), disable everything during the setup and set it so that it doesn't try to log in but only forwards the connection so you can set up OpenWRT with the ISPs login data (with PPPoE or something like that?), but I simply can't find where I read that. Do I set one of the 7490s LAN ports to PPPoE and just enter my ISPs login information? What else needs to be configured for internet to be available on all other LAN ports and over WiFi?

Sort of, you remove that port fro br-lan, and use its device/interface name to configure as wan using PPPoE. But, on the danger of repeating myself, your FB 7490 will not be able to do interesting things at your link's 250/40 Mbps, it simply is too old a SoC, sorry.
Also fritzos does, as far as I know, not allow to easily configure modern fritzboxen into bridged-modems (but there likely are work arounds).

I already have the build system set up (since I had to compile the 7490 version myself anyways) - but before I go through the effort of installing OpenWRT on another router: when I compile following this guide you posted, will it have proper support for VDSL2+ (since it"s still in development as far as I can tell)?

I honestly can not tell you, I am still on a profile 17a VDSL2/Vectoring+G.INP link. Reading the linked thread makes me believe it works well enough to b worth testing, as I know that the 7490 is going to be too weak for a 250/40 link.

Personally, I'd get the "router" problem out of the way first - by getting something well supported by OpenWrt that is capable of doing 250/40 MBit/s (without sqm, ipq806x would do - mt7622 probably preferred, ipq807x should also do (as you don't seem to be adverse to building work-in-progress code)), then you can check how far you can get with the 7530 in mere modem duties (it's officially -explicitly- unsupported by AVM, but said to -kind of- work on a totally unconfigured device); the 7490 with stock firmware can be used for all your phone needs (I'm just a little worried about its future OEM support state in this capacity, that's why I was hinting at the 7530 instead (which is still being sold)).

Just for reference, my setup isn't (wasn't) that much different:

  • Draytek Vigor 130b as VDSL2 (vectoring, not super-vectoring, but the vigor 167 would be its modern super-vectoring capable counterpart) modem; I have switched ISPs to fibre now though (so no longer using any VDSL modem, but a Nokia G-010G-P ONT instead)
  • gateprotect GP-7543 (x86_64, Celeron J1900) running OpenWrt as router
  • (smart-)managed rtl8382m based switches running OpenWrt
  • various OpenWrt devices as APs
  • AVM Fritz!Box 7430 in IPoE mode[0], [1], [2] (jailed into its own VLAN/ firewall zone) as SIP pbx, SIP ATA and DECT base

This has been working fine for me since 2017, originally on a 7362sl, now on the 7430 - as this one is going EOL (as well), I'll probably look into 7520/ 7530 or something similar in the future.

--
[0] "Anschluss an externes Modem oder Router", "Wählen Sie diesen Zugang, wenn die FRITZ!Box über "LAN 1" an ein bereits vorhandenes externes Modem oder einen Router angeschlossen ist."
[1] "IP-Client", "Diese FRITZ!Box ergänzt das Heimnetz als IP-Client und benutzt eine vorhandene Internet-Verbindung. Sie erhält vom Router eine IP-Adresse. Die FRITZ!Box wird Teil des vorhandenen Heimnetzes und übernimmt dessen IP-Adressbereich. Die Firewall der FRITZ!Box wird dabei deaktiviert."
[2] "Portweiterleitung des Internet-Routers für Internettelefonie aktiv halten", "Portweiterleitung aktiv halten alle: 30 Sekunden"

I've installed OpenWRT on my 7530 now, just to test it. However, I'm stuck on how to configure it. Since almost noone seems to have done this, I can't find any information on which DSL settings I could use. Are you able to help me out in that regard @moeller0?

I can try. I use a BT HomeHub 5A (xrx200 platform) as bridged modem on a VDSL2 profile 17b link so there will be differences. What can you actually do? Can you log in via ssh/http?

There shouldn't be much to configure. If you included LuCI in your build, you should see the DSL status on the front page. If not, you need to run ubus call dsl metrics to show the state. You might get a sync with default settings, at least I get one on profile 17b.

I can log in via ssh and via http (LuCI), no problem. The installation worked and I can sometimes get the DSL to sync. However, it usually disconnects after a few seconds, and I would like to get 35b supervectoring to work, because otherwise it's capped at 100Mbit, right?

The dsl0 interface shows up, and by using dsl0.7 (so with VLAN-ID 7) I can sometimes get it to sync, but it disconnects after a few seconds. Can I somehow see (through the CLI or LuCI) which Annex / Tone etc. the connection is currently using? Because I always select multiples in the GUI.

Try running:
ubus call dsl metrics
on the router's commnd line via SSH and post the results here.
Which DSL-firmware blob are you using?

Let's try to get it to connect stably first and then deal with the "at what speed/profile" question :wink:

The VLAN tag should not matter for syncing or not syncing, it will affect whether you can actually reach your ISPs PPPoE server....

For reference here is my ubus call dsl metrics output, which I expect to look different on your device:

root@OpenWrt:~# ubus call dsl metrics
{
	"api_version": "4.17.18.6",
	"firmware_version": "5.9.1.4.0.7",
	"chipset": "Lantiq-VRX200",
	"driver_version": "1.5.17.6",
	"state": "Showtime with TC-Layer sync",
	"state_num": 7,
	"up": true,
	"uptime": 2364123,
	"atu_c": {
		"vendor_id": [
			181,
			0,
			66,
			68,
			67,
			77,
			194,
			127
		],
		"vendor": "Broadcom 194.127",
		"system_vendor_id": [
			181,
			0,
			66,
			68,
			67,
			77,
			0,
			0
		],
		"system_vendor": "Broadcom",
		"version": [
			118,
			49,
			50,
			46,
			48,
			52,
			46,
			49,
			50,
			55,
			32,
			32,
			32,
			32,
			32,
			0
		],
		"serial": [
			101,
			113,
			32,
			110,
			114,
			32,
			112,
			111,
			114,
			116,
			58,
			51,
			51,
			32,
			32,
			111,
			101,
			109,
			105,
			100,
			32,
			115,
			111,
			102,
			116,
			119,
			97,
			114,
			101,
			114,
			101,
			118
		]
	},
	"power_state": "L0 - Synchronized",
	"power_state_num": 0,
	"xtse": [
		0,
		0,
		0,
		0,
		0,
		0,
		0,
		2
	],
	"annex": "B",
	"standard": "G.993.2",
	"profile": "17a",
	"mode": "G.993.2 (VDSL2, Profile 17a, with down- and upstream vectoring)",
	"upstream": {
		"vector": true,
		"trellis": true,
		"bitswap": true,
		"retx": true,
		"virtual_noise": false,
		"interleave_delay": 0,
		"data_rate": 36999000,
		"latn": 8.300000,
		"satn": 8.200000,
		"snr": 7.800000,
		"actps": -90.100000,
		"actatp": 12.600000,
		"attndr": 42573000
	},
	"downstream": {
		"vector": true,
		"trellis": true,
		"bitswap": true,
		"retx": true,
		"virtual_noise": false,
		"interleave_delay": 140,
		"data_rate": 116797000,
		"latn": 9.800000,
		"satn": 9.800000,
		"snr": 12.800000,
		"actps": -90.100000,
		"actatp": -3.600000,
		"attndr": 141131776
	},
	"errors": {
		"near": {
			"es": 9,
			"ses": 4,
			"loss": 5,
			"uas": 278,
			"lofs": 0,
			"fecs": 0,
			"hec": 0,
			"ibe": 0,
			"crc_p": 0,
			"crcp_p": 0,
			"cv_p": 0,
			"cvp_p": 0,
			"rx_corrupted": 107971,
			"rx_uncorrected_protected": 55226,
			"rx_retransmitted": 0,
			"rx_corrected": 52745,
			"tx_retransmitted": 86095
		},
		"far": {
			"es": 136,
			"ses": 76,
			"loss": 0,
			"uas": 278,
			"lofs": 0,
			"fecs": 87048,
			"hec": 0,
			"ibe": 0,
			"crc_p": 0,
			"crcp_p": 0,
			"cv_p": 0,
			"cvp_p": 0,
			"rx_corrupted": 37121,
			"rx_uncorrected_protected": 0,
			"rx_retransmitted": 0,
			"rx_corrected": 37121,
			"tx_retransmitted": 45374
		}
	},
	"erb": {
		"sent": 32875425,
		"discarded": 0
	}
}

Anything in the logs why it disconnects? I doubt it loses sync.

Should I disable the VLAN-ID 7 again before calling the command or leave it like it is now?

Just run the command as is, then we can figure outvhow to proced.