Kitz Forum
Broadband Related => Broadband Hardware => Topic started by: Chrysalis on February 16, 2022, 03:38:59 PM
-
Hopefully Alex or someone else can help here.
Trying to configure this as a bridge device, MTU 1508 so 1500 can be used on PPPoE.
-
I think the 1508 mtu wont be possible without a custom firmware and usb ethernet device, I posted here.
https://forum.kitz.co.uk/index.php/topic,23744.msg449369.html#msg449369
Probably means I wont be trying this setup but would still appreciate information on the bridge so I can check what I have configured is valid.
-
Ah yes, I stopped bothering about baby jumbo ages ago as I found:
1) it makes sod-all real world difference in speed, reducing the SNRm however can make a HUGE difference
2) It actually breaks things when load balancing with mobile connections
-
Alex do you mind either posting your /etc/config/network here or a screenshot of the dsl interface, as I did try it once, but it just looped trying to sync.
On the openwrt forums and documentation the information is all over the place with different people saying different annex type etc. Also I have no options for G993, only G992 which is odd.
---
It is synced now i had to disable the ATM bridge that was auto generated even in PTM mode.
However it behaves like the fritzbox I tried several years ago, it syncs a "lot" lower than broadcom modems at the same SNRM.
6db target interleaved, broadcom approx 73500, lantiq approx 64000
4db target lantiq approx 77000 (I thought this would be an easy 80mbit, since broadcom is hitting 74ish at 6db)
Error rates dont seem to be working properly on the reporting, 6200ES with no FEC on upstream when freshly synced, no FEC reported when in thousands every minute on broadcom.
-
Another theory would be its behaving better as its synced lower and a matching chipset. ;)
I'd be tempted to leave it just to see if this has any effect on DLM.
-
The FEC is still there, I have confirmed via cli commands, the DSL stats UI just seems whacked.
I have left it as is for now anyway as had other stuff to do.
normal status output below. If these are accurate, the US FEC are much higher. with similar SNRM and same sync speed. However this still shows the 6200 ES which appeared immediately (impossible).
ATU-C Vendor ID: Infineon 178.6
ATU-C System Vendor ID: 45,43,49,20,74,65,6C,65
Chipset: Lantiq-VRX200
Firmware Version: 5.7.9.9.0.6
API Version: 4.17.18.6
XTSE Capabilities: 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x2
Annex: B
Line Mode: G.993.2 (VDSL2)
Profile: 17a
Line State: UP [0x801: showtime_tc_sync]
Forward Error Correction Seconds (FECS): Near: 1409347 / Far: 8874266
Errored seconds (ES): Near: 0 / Far: 6213
Severely Errored Seconds (SES): Near: 0 / Far: 0
Loss of Signal Seconds (LOSS): Near: 0 / Far: 184
Unavailable Seconds (UAS): Near: 35 / Far: 35
Header Error Code Errors (HEC): Near: 0 / Far: 0
Non Pre-emtive CRC errors (CRC_P): Near: 0 / Far: 0
Pre-emtive CRC errors (CRCP_P): Near: 0 / Far: 0
Power Management Mode: L0 - Synchronized
Latency [Interleave Delay]: 8.0 ms [Interleave] 0.0 ms [Fast]
Data Rate: Down: 77.520 Mb/s / Up: 20.000 Mb/s
Line Attenuation (LATN): Down: 13.9 dB / Up: 14.6 dB
Signal Attenuation (SATN): Down: 14.0 dB / Up: 14.5 dB
Noise Margin (SNR): Down: 3.8 dB / Up: 9.2 dB
Aggregate Transmit Power (ACTATP): Down: 3.7 dB / Up: 3.8 dB
Max. Attainable Data Rate (ATTNDR): Down: 89.176 Mb/s / Up: 26.679 Mb/s
Line Uptime Seconds: 18479
Line Uptime: 5h 7m 59s
Other data
local dsl={}
dsl.atuc_vendor_id="Infineon 178.6"
dsl.atuc_system_vendor_id="45,43,49,20,74,65,6C,65"
dsl.chipset="Lantiq-VRX200"
dsl.firmware_version="5.7.9.9.0.6"
dsl.api_version="4.17.18.6"
dsl.xtse1=0x0
dsl.xtse2=0x0
dsl.xtse3=0x0
dsl.xtse4=0x0
dsl.xtse5=0x0
dsl.xtse6=0x0
dsl.xtse7=0x0
dsl.xtse8=0x2
dsl.xtse_s="0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x2"
dsl.annex_s="B"
dsl.line_mode_s="G.993.2 (VDSL2)"
dsl.profile=6
dsl.profile_s="17a"
dsl.line_state_num=0x801
dsl.line_state_detail="showtime_tc_sync"
dsl.line_state="UP"
dsl.errors_fec_near=1410626
dsl.errors_fec_far=8874266
dsl.errors_es_near=0
dsl.errors_es_far=6213
dsl.errors_ses_near=0
dsl.errors_ses_far=0
dsl.errors_loss_near=0
dsl.errors_loss_far=184
dsl.errors_uas_near=35
dsl.errors_uas_far=35
dsl.errors_hec_near=0
dsl.errors_hec_far=0
dsl.errors_crc_p_near=0
dsl.errors_crc_p_far=0
dsl.errors_crcp_p_near=0
dsl.errors_crcp_p_far=0
dsl.power_mode_num=0
dsl.power_mode_s="L0 - Synchronized"
dsl.latency_down="8000"
dsl.latency_up="0"
dsl.latency_num_down="8.0 ms"
dsl.latency_num_up="0.0 ms"
dsl.latency_s_down="Interleave"
dsl.latency_s_up="Fast"
dsl.data_rate_down=77520000
dsl.data_rate_up=20000000
dsl.data_rate_down_s="77.520 Mb"
dsl.data_rate_up_s="20.000 Mb"
dsl.line_attenuation_down="13.9"
dsl.line_attenuation_up="14.6"
dsl.noise_margin_down="4.1"
dsl.noise_margin_up="9.2"
dsl.signal_attenuation_down="14.0"
dsl.signal_attenuation_up="14.5"
dsl.actatp_down="3.7"
dsl.actatp_up="3.8"
dsl.max_data_rate_down=90431496
dsl.max_data_rate_up=26682566
dsl.max_data_rate_down_s="90.431 Mb"
dsl.max_data_rate_up_s="26.682 Mb"
dsl.line_uptime=18491
dsl.line_uptime_s="5h 8m 11s"
-
Take the ES with a pinch of salt, it always seems to register those during sync.
I'm currently sitting at:
Chipset: Lantiq™ XWAY™ VRX268
Firmware Version: 5.7.9.9.0.6
API Version: 4.17.18.6
MEI Version: 1.5.17.6
Power Management Mode: L0 - Synchronized
Line State: UP [0x801: showtime_tc_sync]
Line Uptime: 63d 10h 39m 23s
Resyncs: 5
DSLAM/MSAN VID:
XTSE Capabilities: 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x2
Annex: B
Line Mode: G.993.2 (VDSL2)
Profile: 17a
Trellis: D: ON / U: ON
Bitswap: D: ON / U: ON
G.INP: D: Not Enabled / U: Not Enabled
Virtual Noise Support: D: Not Supported / U: Not Supported
Attain Data Rate: 86.613 Mb/s / 24.826 Mb/s
Actual Data Rate: 79.995 Mb/s / 20.000 Mb/s
Impulse Noise Prot: 0.0 sym / 0.0 sym
Interleave Delay: 0.0 ms / 0.0 ms
NFEC: 255 / 255
RFEC: 16 / 16
LSYMB: 21451 / 5410
Interleave Depth: 1 / 1
Interleave Block: 255 / 255
LPATH: 0 / 0
Line Attenuation: 11.8dB / 13.4dB
Signal Attenuation: 11.8dB / 13.2dB
Noise Margin: 4.1dB / 8.9dB
Transmit power: 13.9dBm / 3.3dBm
FECS: 769993 / 40894
ES: 5586 / 36834
SES: 0 / 17
LOSS: 6 / 0
UAS: 145 / 145
HEC: 0 / 0
CRC_P: 0 / 0
CRCP_P: 0 / 0
15m Code Violations: 0 / 1
15m FEC Errors: 0 / 2
1d Code Violations: 70 / 170
1d FEC Errors: 772 / 791
I'm kinda expecting things could go badly over the next couple of weeks as they are working on the ducting that runs to my DP (though not the actual bit from there to my DP annoyingly) in preparation for FTTP. ;D
-
Now I am curious why do you have a different chipset and stat layout to me, we both supposedly on the same modems, assuming plusnet hub's are identical hardware wise to HH5A. O_o.
Lantiq™ XWAY™ VRX268 vs Lantiq-VRX200
It seems you have tinkered, as in the post here, can you please your config details? Your stat layout is different order, different wording, stats not visible on mine etc.
https://forum.kitz.co.uk/index.php?topic=25544.60
That firmware version makes no sense, its using stock OpenWRT which is xcpe_581816_580B11.bin which was reported correctly on the Plusnet Hub before I replaced the firmware and was on Zen too AFAIK until the latest OpenWRT update.
-
I meant to mention but got sidetracked. I copied dsl_control and lantiq_dsl.sh from the ECI OpenWRT firmware into /root (so updating OpenWRT wont break anything). Added that folder to the "keep files after upgrade" section on OpenWRT.
Then I created a file called /www/cgi-bin/dsl that contains (also added to keep files list):
#!/bin/sh
echo "Content-Type: text/plain"
echo ""
/root/dsl_control status
I then have a PHP script on my NAS that acts as a proxy to download http://192.168.1.240/cgi-bin/dsl to display on a web page.
I also had to disable redirect_https in /etc/config/uhttpd so that would work.
-
Ok do you mind sharing those scripts then please, as I dont have a the older ECI openwrt firmware.
I have been working on trying to get the dsl stats on collectd, I think I am going to have to do a support request on the OpenWRT forum though as its a lua issue, and I have no knowledge of LUA.
The RRD files are been generated correctly, just I cannot get the Luci stats page to work.
/usr/lib/lua/luci/statistics/rrdtool.lua:77: attempt to index local 'list' (a nil value)
stack traceback:
/usr/lib/lua/luci/statistics/rrdtool.lua:77: in function '_forcelol'
/usr/lib/lua/luci/statistics/rrdtool.lua:554: in function 'render'
.../luci/controller/luci_statistics/luci_statistics.lua:170: in function <.../luci/controller/luci_statistics/luci_statistics.lua:114>
The command that generates the stats tmp file is this in cron.
* * * * * /etc/init.d/dsl_control lucistat > /tmp/dslstat.txt
-
* * * * * /etc/init.d/dsl_control lucistat > /tmp/dslstat.txt
I just checked and lucistat does not work on that old script on current OpenWRT and the normal version is now called dslstat, so not sure what build you are using.
/etc/init.d/dsl_control dslstat
{
"api_version": "4.17.18.6",
"firmware_version": "5.7.9.9.0.6",
"chipset": "Lantiq-VRX200",
"driver_version": "1.5.17.6",
"state": "Showtime with TC-Layer sync",
"state_num": 7,
"up": true,
"uptime": 5589727,
"atu_c": {
"vendor_id": [
181,
0,
73,
70,
84,
78,
208,
134
],
"vendor": "Infineon 208.134",
"system_vendor_id": [
67,
69,
32,
73,
101,
116,
101,
108
],
"version": [
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0
],
"serial": [
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0
]
},
"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)",
"upstream": {
"vector": false,
"trellis": true,
"bitswap": true,
"retx": false,
"virtual_noise": false,
"interleave_delay": 0,
"data_rate": 20000000,
"latn": 13.400000,
"satn": 13.200000,
"snr": 9.000000,
"actps": -90.100000,
"actatp": 13.900000,
"attndr": 24957960
},
"downstream": {
"vector": false,
"trellis": true,
"bitswap": true,
"retx": false,
"virtual_noise": false,
"interleave_delay": 0,
"data_rate": 79995000,
"latn": 11.800000,
"satn": 11.800000,
"snr": 4.000000,
"actps": -90.100000,
"actatp": 3.300000,
"attndr": 86486344
},
"errors": {
"near": {
"es": 5647,
"ses": 0,
"loss": 6,
"uas": 145,
"lofs": 0,
"fecs": 17741,
"hec": 0,
"ibe": 0,
"crc_p": 2661,
"crcp_p": 0,
"cv_p": 84879,
"cvp_p": 0
},
"far": {
"es": 36975,
"ses": 17,
"loss": 0,
"uas": 145,
"lofs": 0,
"fecs": 8829400,
"hec": 0,
"ibe": 0,
"crc_p": 0,
"crcp_p": 0,
"cv_p": 0,
"cvp_p": 0
}
}
}
-
19.07 and was previously using 20.x , I downgraded as the openwrt documentation hasnt been updated for the new network structure and I couldnt configure the bridge interface with the outdated documentation.
That script you got from a very old firmware, so why would it be designed only for the script in 20.x?
-
Yeah I don't understand the switch configuration in LuCI on 21.01 either, fortunately it automagically converts if you configure on the older version first then upgrade.
Ironically I think its easier to understand in the configuration file now than it is in the UI.
/etc/config/network
config interface 'loopback'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
option device 'lo'
config globals 'globals'
option ula_prefix 'fd76:9236:9ad3::/48'
config dsl 'dsl'
option xfer_mode 'ptm'
option line_mode 'vdsl'
option ds_snr_offset '-35'
option annex 'b'
option tone 'a'
config interface 'lan'
option proto 'static'
option netmask '255.255.255.0'
option gateway '192.168.1.254'
list dns '192.168.1.254'
option ipaddr '192.168.1.240'
option stp '1'
option device 'br-lan'
config device 'lan_dev'
option name 'eth0.1'
option macaddr '18:1e:78:23:5a:3e'
config interface 'wan'
option proto 'none'
option device 'br-wan'
config device 'wan_dev'
option macaddr '18:1e:78:23:5a:3f'
option name 'dsl0'
option mtu '1508'
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option vid '1'
option ports '0 1 2 4 5t 6t'
config switch_vlan
option device 'switch0'
option vlan '2'
option vid '2'
option ports '5 6t'
config device
option name 'br-lan'
option type 'bridge'
list ports 'eth0.1'
option igmp_snooping '1'
config device
option name 'br-wan'
option type 'bridge'
list ports 'eth0.2'
list ports 'dsl0.101'
VLAN1 bridges DSL straight onto the WAN port.
VLAN2 (LAN) is tagged on the WAN as well as untagged to all the LAN ports. This allows me a single cable solution to bridge it back onto the actual LAN from pfSense.
-
ok so the main change seems to be the switch to 'list ports' syntax, thanks.
-
On a lower noise margin target now, still no CRC/ES. Assuming those metrics are accurate the high far FEC/ES due to the sync stat bug, since uptime the actual far FEC/ES is 4 FEC/0 ES on upstream.
root@OpenWRT-HH5A:~# /etc/init.d/dsl_control status
ATU-C Vendor ID: Infineon 178.6
ATU-C System Vendor ID: 45,43,49,20,74,65,6C,65
Chipset: Lantiq-VRX200
Firmware Version: 5.7.9.9.0.6
API Version: 4.17.18.6
XTSE Capabilities: 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x2
Annex: B
Line Mode: G.993.2 (VDSL2)
Profile: 17a
Line State: UP [0x801: showtime_tc_sync]
Forward Error Correction Seconds (FECS): Near: 99335503 / Far: 8874420
Errored seconds (ES): Near: 0 / Far: 6234
Severely Errored Seconds (SES): Near: 0 / Far: 0
Loss of Signal Seconds (LOSS): Near: 0 / Far: 190
Unavailable Seconds (UAS): Near: 63 / Far: 63
Header Error Code Errors (HEC): Near: 0 / Far: 0
Non Pre-emtive CRC errors (CRC_P): Near: 0 / Far: 0
Pre-emtive CRC errors (CRCP_P): Near: 0 / Far: 0
Power Management Mode: L0 - Synchronized
Latency [Interleave Delay]: 7.0 ms [Interleave] 0.0 ms [Fast]
Data Rate: Down: 79.994 Mb/s / Up: 20.000 Mb/s
Line Attenuation (LATN): Down: 13.9 dB / Up: 14.5 dB
Signal Attenuation (SATN): Down: 14.0 dB / Up: 14.4 dB
Noise Margin (SNR): Down: 3.6 dB / Up: 10.4 dB
Aggregate Transmit Power (ACTATP): Down: 3.5 dB / Up: 3.8 dB
Max. Attainable Data Rate (ATTNDR): Down: 95.377 Mb/s / Up: 28.170 Mb/s
Line Uptime Seconds: 7496
Line Uptime: 2h 4m 56s
I never did figure out the LUA, not sure if I am bothered enough to spend more time on it as I expect to have FTTP later in the year and not even sure if sticking to this modem, Plus if I get 21.x configured, the native exec.js may work out of the box, I have set it up also as a 2nd AP in my home for the living room as my firetv stick struggled. Interesting that this internal antennae device has a stronger signal than the C7. (when comparing in opposite rooms).
-
Experiment over? DLM it seems didnt like me staying too far below 6db, line just got banded.
-
Shame, but I admit I am kinda waiting to see if that happens here. I really wouldn't have thought it would do so with low errors though, but its probably more tetchy with an interleaved line?
Line Uptime: 73d 23h 35m 13s
Attain Data Rate: 86.972 Mb/s / 25.109 Mb/s
Actual Data Rate: 79.995 Mb/s / 20.000 Mb/s
Impulse Noise Prot: 0.0 sym / 0.0 sym
Interleave Delay: 0.0 ms / 0.0 ms
NFEC: 255 / 255
RFEC: 16 / 16
LSYMB: 21451 / 5410
Interleave Depth: 1 / 1
Interleave Block: 255 / 255
LPATH: 0 / 0
Line Attenuation: 11.8dB / 13.4dB
Signal Attenuation: 11.8dB / 13.2dB
Noise Margin: 4.1dB / 9.0dB
Transmit power: 13.9dBm / 3.3dBm
FECS: 1171091 / 47560
ES: 6182 / 38072
SES: 0 / 17
LOSS: 6 / 0
UAS: 145 / 145
HEC: 0 / 0
CRC_P: 0 / 0
CRCP_P: 0 / 0
15m Code Violations: 0 / 0
15m FEC Errors: 14 / 9
1d Code Violations: 54 / 57
1d FEC Errors: 628 / 281
-
Shame, but I admit I am kinda waiting to see if that happens here. I really wouldn't have thought it would do so with low errors though, but its probably more tetchy with an interleaved line?
Line Uptime: 73d 23h 35m 13s
Attain Data Rate: 86.972 Mb/s / 25.109 Mb/s
Actual Data Rate: 79.995 Mb/s / 20.000 Mb/s
Impulse Noise Prot: 0.0 sym / 0.0 sym
Interleave Delay: 0.0 ms / 0.0 ms
NFEC: 255 / 255
RFEC: 16 / 16
LSYMB: 21451 / 5410
Interleave Depth: 1 / 1
Interleave Block: 255 / 255
LPATH: 0 / 0
Line Attenuation: 11.8dB / 13.4dB
Signal Attenuation: 11.8dB / 13.2dB
Noise Margin: 4.1dB / 9.0dB
Transmit power: 13.9dBm / 3.3dBm
FECS: 1171091 / 47560
ES: 6182 / 38072
SES: 0 / 17
LOSS: 6 / 0
UAS: 145 / 145
HEC: 0 / 0
CRC_P: 0 / 0
CRCP_P: 0 / 0
15m Code Violations: 0 / 0
15m FEC Errors: 14 / 9
1d Code Violations: 54 / 57
1d FEC Errors: 628 / 281
I am still going to be using it for an AP, this thing has much better wifi without ugly antennae's. My noise margin was going as low as 2.2db, so I think that freaked DLM out. The last time I got banded it also occurred on a sub 4b noise margin.
-
I am still going to be using it for an AP, this thing has much better wifi without ugly antennae's. My noise margin was going as low as 2.2db, so I think that freaked DLM out. The last time I got banded it also occurred on a sub 4b noise margin.
That's interesting as I found the HH5A has awful WiFi, but then I immediately gave up on it when I realised it became CPU bound accessing the LAN getting half the performance on 5Ghz that it should do, I didn't really test the range. That's still well above 80Mbit mind you, so for Internet use only its probably indeed fine.
-
Since i can see Home Hub 5A been used, I Just thought ill add the fritzbox 7530 on OpenWrt with VDSL 2 working (When i did) but swap it due to my local cabinet been Hauwei but this was my stats on TalkTalk (none wholesale)
Edit
Forgot to mention that is not in the OpenWRT snapshot/release, you have to compile from janh's github https://github.com/janh/openwrt
root@7530:~# /etc/init.d/dsl_control dslstat
"api_version": "4.21.3",
"firmware_version": "8.13.1.10.1.7",
"chipset": "Lantiq-VRX500",
"driver_version": "1.9.3",
DSL Status
Line State:Showtime with TC-Layer sync
Line Mode:G.993.2 (VDSL2, Profile 17a)
Line Uptime:22h 17m 45s
Annex:B
Data Rate:48.847 Mb/s / 8.407 Mb/s
Max. Attainable Data Rate (ATTNDR):49.727 Mb/s / 8.414 Mb/s
Latency:0.15 ms / 0.00 ms
Line Attenuation (LATN):17.8 dB / 28.4 dB
Signal Attenuation (SATN):17.1 dB / 28.0 dB
Noise Margin (SNR):5.1 dB / 6.1 dB
Aggregate Transmit Power (ACTATP):13.4 dB / 7.0 dB
Forward Error Correction Seconds (FECS):321 / 240801
Errored seconds (ES):0 / 244510
Severely Errored Seconds (SES):0 / 38068
Loss of Signal Seconds (LOSS):0 / 0
Unavailable Seconds (UAS):28 / 28
Header Error Code Errors (HEC):0 / 0
Non Pre-emptive CRC errors (CRC_P):0 / 0
Pre-emptive CRC errors (CRCP_P):0 / 0
ATU-C System Vendor ID:Broadcom 164.161
Power Management Mode:L0 - Synchronized
-
That's interesting as I found the HH5A has awful WiFi, but then I immediately gave up on it when I realised it became CPU bound accessing the LAN getting half the performance on 5Ghz that it should do, I didn't really test the range. That's still well above 80Mbit mind you, so for Internet use only its probably indeed fine.
At close range its similar to the C7, but through wall's its in a different league.
I only use wifi for internet or light LAN use, if I need it for fast LAN, then I always use ethernet.
The C7 to my firestick was about 5-10mbit downstream, with dongle hanging on a hdmi extender, with it in TV directly about 2mbit/sec. (upstream was fine). On the HH5A it maxes the line rate even with the HH5A in same place as C7. Not sure what these external antennae's are doing. The C7 was also better than the Asus AC68 it replaced. The devices get better as they progressively get cheaper. :)
-
That makes sense, as I only compared it to the C7 in close range, I pretty much never need to use WiFi outside of the room my AP is in.
It does make sense though, there are losses in the antenna pigtails and connectors so internal antennas especially when etched or soldered on the PCB directly will theoretically be both a stronger signal and more sensitive for reception.
A friend of mine has my old WDR3600 in his loft and the signal is completely gone on the ground floor so there's a HH5B there doubling as a switch. In comparison the Virgin Superhub DID reach the ground floor but was too weak to be very usable, so we put it in bridge mode so the 3600 could apply AQM.
I assume its all been working as I haven't checked on the setup in years. All I know is with VM upgrades he has hit the limit of the 3600 CPU now so it bottlenecks. Was going to replace it with the C7 but then pandemic. Probably end up with the Fritzbox 7530 instead at some point, if its ever safe for me to do it.
-
3600 CPU now so it bottlenecks. Was going to replace it with the C7 but then pandemic. Probably end up with the Fritzbox 7530 instead at some point, if its ever safe for me to do it.
If your talking about the tp-link's then the 3600 only has a single core @ 560mhz and the c7 is singe core @ 720mhz. The HH5A is a dual core but i believe is something to do wit that CPU is limited on that device! I believe the LANs/WiFI are limited to 150Mb max! Shame really but thats Lantiq/intel i guess ;)
Take a look at Bill888, He has a graph for speeds however not sure on the 21.02.x builds of openwrt yet
https://forum.openwrt.org/t/18-06-4-speed-fix-for-bt-homehub-5a/23643/23
Good news thought, The Fritzbox 7530 is a quad core armv7 but since is flat and have no antenna's, The WiFI range will be a issue but for switch or routing wise would be pretty solid :baby: also remember there is a broadcom AX 7530! https://en.avm.de/products/fritzbox/fritzbox-7530-ax/technical-specifications/ same stuff but with WiFi 6/AX
-
I should add I never tested the HH5A for LAN performance, so when I say same as C7 close range, I meant internet throughput.
The 7530 might be good on range, as currently no antennae's wins for me on range. ;)
-
Yeah the 7530 is much faster WiFi to LAN (the HH5A is heavily CPU bottlenecked) but both I'd expect to match on Internet.
also remember there is a broadcom AX 7530! https://en.avm.de/products/fritzbox/fritzbox-7530-ax/technical-specifications/ same stuff but with WiFi 6/AX
Problems is Broadcom = no OpenWRT. :( FritzOS is great for the average person, but as a techie I hated it.
-
Yeah the 7530 is much faster WiFi to LAN (the HH5A is heavily CPU bottlenecked) but both I'd expect to match on Internet.
the HH5A indeed is heavily CPU bottlenecked even though it has a dual core CPU lol :-\
Problems is Broadcom = no OpenWRT. :( FritzOS is great for the average person, but as a techie I hated it.
Few BCM devices are supported via OpenWrt https://downloads.openwrt.org/snapshots/targets/bcm63xx/smp but limited to either there WiFi drivers such as the B43 drivers what isn't open sauced,
Sky SR102 (Back) https://downloads.openwrt.org/snapshots/targets/bcm63xx/smp/openwrt-bcm63xx-smp-sky_sr102-squashfs-cfe.bin is supported based on BCM63xx however no DSL/WiFI such due to no open source drivers, however the SR102 takes an mini pci express wifi card so you can get atheros card and install the drivers inside the Luci webinterface for driver support.
FritzOS is great but settings up thinkbroadnand's and f8lure's BQM isn't good, only if you like seeing your Broadband in Red :-\