Kitz Forum
Broadband Related => Broadband Hardware => Topic started by: jsamuel on August 09, 2015, 05:42:21 PM
-
Hi there. I thought I would share with you my OpenWrt image. It's been quite stable and there are some fixes which aren't currently in the trunk.
The configuration is setup much like an unlocked HG612 is setup, ie:
Set the router's IP to 192.168.1.2
The modem, by default is set to 192.168.1.1
LAN1 -> WAN port on the router
LAN2 -> LAN port on the router, configured with a gateway to the router so the modem has internet access for OPKG. And of course access to the modem itself via 192.168.1.1.
I've had to make some modifications to get this working, and since the switch driver is still broken there's no VLANs so LAN1 and LAN2 are back to separate ports like you might have seen in previous images. eth0/eth1
Lan2 led has been fixed too.
Graphs: see this follow up post (http://forum.kitz.co.uk/index.php/topic,15918.msg298767.html#msg298767)
I've also modified lantiq_dsl.sh with the help of Kronos' additions to it last year, but I've added a few more things.
LuCI's status page has been changed to reflect this.
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FJoW5Sn2.png&hash=bae2ccce61a1f1e39c6f7fa66e683677ccaa98d0)
Nano is preinstalled, too. This image requires no additional configuration. Hopefully I've helped someone who wants to install openwrt on their ECI/r in an HG612-like setup without losing hair.
v1: openwrt-lantiq-xrx200-VG3503J-squashfs.image (http://vanquishsolutions.co.uk/openwrt/)
v2: openwrt-lantiq-xrx200-VG3503J_V2-squashfs.image (http://vanquishsolutions.co.uk/openwrt/)
Remember the SoC on the ECI /r v1 is labelled "v1.1" and on the v2 it's labelled "v1.2"
Don't put the image for the v2 on a v1 otherwise your ethernet ports won't work effectively leaving you with a bricked unit.
If there's any stats missing, let me know.
Flashing procedure for those who aren't familiar with these modems:
Buy a USB to TTL UART connector. I used one with a CP2102 chip.
Buy a 1mm drillbit
Buy some right angle 0.1" 2.54mm header pins
carefully drill the four serial holes (see this previous post on Kitz (http://forum.kitz.co.uk/index.php?topic=11818.msg226712#msg226712)) connect the pins to the PCB and dab some flux core solder on the bottom of the pins.
See the above image on how to connect the serial header to RXD, TXD & GND.
If on Linux use something like picocom, eg: $ sudo picocom -b 115200 -l -r /dev/ttyUSB0 115200,cs8,-parenb,cstopb,-hupcl
If on Windows use PuTTY Tray (https://puttytray.goeswhere.com/) to connect to the serial and enter the following:
Serial line: COM3
Speed: 115200
Connection type: Serial
Click the dropdown at Connection and select Serial.
Databits: 8
Stop bits: 1
Parity: None
Flow control: None
Save your session under something like "UART" for future reference.
Now connect to the serial and connect LAN1 to the ethernet port on your PC.
If using Linux, mkdir /tftpImage, copy your squashfs image into it and setup tftp:
ifconfig eth0 192.168.1.1 netmask 255.255.255.0 up
/usr/sbin/dnsmasq --listen-address="192.168.1.1" \
--no-daemon \
--dhcp-range="192.168.1.100,192.168.1.150,12h" \
--interface="eth0" \
--no-negcache \
--enable-tftp \
--log-queries \
--domain="my.lan" \
--bind-interfaces \
--log-facility=- \
--tftp-root=/tftpImage/,eth0 \
--log-dhcp \
--stop-dns-rebind \
--no-hosts
If using Windows, see: http://tftpd32.jounin.net/ (http://tftpd32.jounin.net/)
Interrupt the bootloader by pressing CTRL+C
Enter the following commands at the VRx prompt:
set ipaddr 192.168.1.100
set serverip 192.168.1.1
set bootfile openwrt-lantiq-xrx200-VG3503J-squashfs.image
set bootcmd cp.b 0xb0020000 0x80002000 0x400000\; go 0x80002000
set preboot ping 1.1.1.1\;run bootcmd
set update_openwrt erase 0xb0020000 0xb073ffff\;tftp 0x81000000 openwrt-lantiq-xrx200-VG3503J-squashfs.image\;cp.b 0x81000000 0xb0020000 \$(filesize)
saveenv
If your modem is a v2, change:
set bootfile openwrt-lantiq-xrx200-VG3503J-squashfs.image
[.............]
set update_openwrt erase 0xb0020000 0xb073ffff\;tftp 0x81000000 openwrt-lantiq-xrx200-VG3503J-squashfs.image\;cp.b 0x81000000 0xb0020000 \$(filesize)
to
set bootfile openwrt-lantiq-xrx200-VG3503J_V2-squashfs.image
[.............]
set update_openwrt erase 0xb0020000 0xb073ffff\;tftp 0x81000000 openwrt-lantiq-xrx200-VG3503J_V2-squashfs.image\;cp.b 0x81000000 0xb0020000 \$(filesize)
Now run:
run update_openwrt
reset
All should be good.
-
Many thanks for the post, I will give it try next week after a holiday. Do you trust the error stats? they look odd to me with the SES nearly half the ES and no CRC reported? Is that just a start up burst of errors or ongoing. Perhaps doubly odd with interleaving on.
Finally have you any idea of the dsl drivers G.INP status?
-
Those errors are due to DLM currently lowering my sync speed. I'm not quite sure what it's doing since it isn't interleaved on downstream. it may be due to an existing fault.
For the past week I've been upsetting DLM, so it's time to let it settle. :D
As you might have heard some manufacturers have G.INP support in their drivers, but to get that to work on this it'll need a firmware update too which I have yet to do.
-
Many thanks for the post, I will give it try next week after a holiday. Do you trust the error stats? they look odd to me with the SES nearly half the ES and no CRC reported? Is that just a start up burst of errors or ongoing. Perhaps doubly odd with interleaving on.
Finally have you any idea of the dsl drivers G.INP status?
They're spot on when compared with the stats my HG612 put out.
Latest 15 minutes time = 6 min 47 sec
FEC: 0 0
CRC: 0 0
ES: 0 382
SES: 0 150
-
If it is the same on an HG612 is must be some sort of strange startup issue on your line. I don't get ES and SES on startup with an HG612 so hopefully I won't with this firmware and the ECI/r.
-
Line profiles were missing (17a, 30a, etc) so I've added those in lantiq_dsl.sh/LuCI's admin page and updated the squashfs images.
What I'd really like is some fancy graphs.
-
that is indeed massive progress for ECI owners,
This was done by someone else a few years back as well but his work was never released, so it remained as just a proof of concept test all this time.
-
I'll keep it updated and add more things to it, I'll also try and get it compiled with the newer lantiq firmware for G.INP support, I'm working on some graphing on the LuCI backend too. so fingers crossed it'll come out where the HG612 currently is ;D
I'm surprised it's took this long tbh, it seems everyone just pushed the ECI away and are focussing on the HG612.
-
2 main reasons I expect are, the difficulty in flashing the eci and that the hg612 has the better dsl chipset.
But still this will be helpful I expect. As many people still use the ECI but operate blind.
-
I'm surprised it's took this long tbh, it seems everyone just pushed the ECI away and are focussing on the HG612.
True, I just got an ECI for £1 on Ebay.
-
2 main reasons I expect are, the difficulty in flashing the eci and that the hg612 has the better dsl chipset.
But still this will be helpful I expect. As many people still use the ECI but operate blind.
I'm not quite sure either of them are better than one or another. But I do prefer the Lantiq over Broadcom because atleast they reveal more source and without that we would have no firmware or drivers, so no OpenWrt to work with.
Granted, it needs more work to pull stats better.
-
It appears I'm having some luck with the latest Lantiq drivers, which is good news ECI owners.
lib_ifxos 1.5.19
ltq-vdsl-vr9-mei 1.4.8.4 (old one was 1.2.0, oh my goodness!)
ltq-vdsl-vr9 4.16.2.4
I'm using the latest vdsl.bin I can find - 4.16.2.4
the one everyone else is using (and the one on the factory firmware) - 4.11.4
I can confirm this is syncing perfectly, it's stable and giving me some room for DLM to restore my line.
DSL_CPE#>lfcg 1
nReturn=0 nDirection=1 bTrellisEnable=1 bBitswapEnable=1 bReTxEnable=1 bVirtualNoiseSupport=1 b20BitSupport=0
DSL_CPE#>lfcg 0
nReturn=0 nDirection=0 bTrellisEnable=1 bBitswapEnable=1 bReTxEnable=0 bVirtualNoiseSupport=1 b20BitSupport=0
These are the configuration values for the modem. G.INP is available on downstream, and virtual noise support is available on both.
I can't, however, test G.INP is actually working since I'm on an ECI cab although it should be working quite well.
Please test this and post your results.
I've updated the squashfs images at the start of this thread to reflect the changes.
-
/* ReTx is only valid for downstream direction */
pContext->lineFeatureDataCfg[DSL_UPSTREAM].bReTxEnable = DSL_FALSE;
pContext->lineFeatureDataCfg[DSL_DOWNSTREAM].bReTxEnable = DSL_TRUE;
:hmm:
-
btw is there a special kind of DSL truth?
:lol:
silly of me, I know. Just in a daft mood. :-)
(I didn't assume it was your code, no offence meant at all. ;-) )
-
btw is there a special kind of DSL truth?
:lol:
silly of me, I know. Just in a daft mood. :-)
(I didn't assume it was your code, no offence meant at all. ;-) )
:P well, I was pondering if I should change DSL_FALSE to DSL_TRUE on the upstream. and then a few other bits.. and then, perhaps we'd have ReTX on upstream too? That way it would be compatible with Huawei cabs (in my thinking, or perhaps I'm just being too over zealous)
Tidying up the lantiq_dsl.sh, I notice I don't have bitswap enabled. erm?
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FB8OrdGe.png&hash=9b0e4ab2f0add83e3bf1fc860f3bdd636e633baf)
-
I've got a Huawei cabinet so let me know if you want anything testing in regards to G.INP (it is currently disabled but I expect will be turned back on soon).
-
I was pondering if I should change DSL_FALSE to DSL_TRUE on the upstream.
ejs is probably the best man to ask. I think he may have been dabbling in that area. It may also depend on if the hardware is capable - like it was with the TD-W9980's.
-
I've got a Huawei cabinet so let me know if you want anything testing in regards to G.INP (it is currently disabled but I expect will be turned back on soon).
Would you be able to test this test image if you have G.INP re-enabled?
On this image G.INP is allowed on the upstream but I have no idea if it works properly. I think the hardware is capable of it though. I'm not sure which version of ECI /r you have so I've just built images for the two, and if it works it can replace the current images linked at the start of the topic.
> /openwrt/testing/ (http://vanquishsolutions.co.uk/openwrt/testing)
Others with Huawei cabs feel free to test too :)
In a previous post I said I noticed bitswap was off but now I notice it turns itself on but only on upstream, is this normal behaviour? does the cab turn it off when it's not needed? I'm going to leave this setup for about a week and monitor any changes.
When using the HG612 bitswap was always on and I find it strange. Perhaps the cab is talking to something in the lantiq code.
-
Bitswapping is on now, on both downstream and upstream.
It seems to turn on at night, and sometimes during the day it'll turn it on for upstream. Very strange, must be the cabinet doing that.
-
Hi,
I've just awaiting some solder so I can solder my header pins to the ECI.
I haven't even broken into it yet which I believe requires drilling so I'll probably do that at some point tomorrow.
-
Hi,
I've just awaiting some solder so I can solder my header pins to the ECI.
I haven't even broken into it yet which I believe requires drilling so I'll probably do that at some point tomorrow.
No worries, fingers crossed it's stable on your Huawei cab. :fingers:
-
I am thinking of giving this a try. Will any revision of the modem do or do I need to be careful? Have issues with pressing enter during boot to get prompt working and being able to telnet in at same time as being connected? Thanks
-
Switch it off, keep the UART connected and when you plug it back in keep pressing CTRL + C
you'll then get into the uboot prompt.
There's two revisions, v1 and v2. If you read the first post in this thread you'll be able to identify which version you have. :)
-
By the way, I don't think the COM port will necessarily be COM3 :)
-
By the way, I don't think the COM port will necessarily be COM3 :)
Sometimes it's COM5, but usually it's always COM3 :)
If in doubt, see Device Manager > Ports
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FecgiViq.png&hash=5fd07848e65a3299aac86480cb57ee0dd3a01fdf)
-
By the way, I don't think the COM port will necessarily be COM3 :)
That is only of relevance to persons using Billy Gates' Ware. :P
-
By the way, I don't think the COM port will necessarily be COM3 :)
Sometimes it's COM5, but usually it's always COM3 :)
If in doubt, see Device Manager > Ports
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FecgiViq.png&hash=5fd07848e65a3299aac86480cb57ee0dd3a01fdf)
My UART is always COM19 :)
-
Due to the new driver updates, we have a total of 600KB free space left on the flash to work with. :silly:
Before, we had over 1MB.. not much room left if we want graphs, but I'll see what I can do. :D
It would be nice if the dslstats program for the HG612 had customizable commands to retrieve the stats and also SSH support. Perhaps there's another program?
-
Yes I would also like some embedded stats monitoring :D
In regards to bitswapping, I notice it all the time on the various Broadcom modems/routers I use so it will be interesting to see how the ECI performs with your firmware :)
-
Yes I would also like some embedded stats monitoring :D
In regards to bitswapping, I notice it all the time on the various Broadcom modems/routers I use so it will be interesting to see how the ECI performs with your firmware :)
At first I was worried bitswapping was broken :doh: in the new drivers since it was off for a while, and then it gradually turned itself on beginning with upstream in the afternoon and then on DS at around 10pm. Hopefully it works alright on Huawei cabs, it should.
It seems likely lantiq DSLAMs can toggle line features if the CPE supports it, but I've never heard of that before. :D
-
As stats are available now has anyone asked if dslstats could include support for this modem? even if it is just the basic information that would be great. Does the eci have qln and DB per tone?
-
I wonder if it will allow the generation of an Hlog graph too...
-
;D
DSL_CPE#>g997dsnrg 1 1
nReturn=0 nDirection=1 nDeltDataType=1 nMeasurementTime=256 nGroupSize=8 nNumData=512
nFormat=(nToneIndex(dec),nSnr(dec)) nData="
(0000,255) (0001,255) (0002,255) (0003,255) (0004,255) (0005,159) [.../snip]"
DSL_CPE#>g997dsnrg 0 1
nReturn=15 nDirection=0 nDeltDataType=1 nMeasurementTime=256 nGroupSize=8 nNumData=240
nFormat=(nToneIndex(dec),nSnr(dec)) nData="
(0000,255) (0001,086) (0002,093) (0003,101) (0004,107) (0005,111) (0006,116) [../snip]"
DSL_CPE#>g997dhlogg 1 1
nReturn=0 nDirection=1 nDeltDataType=1 nMeasurementTime=128 nGroupSize=8 nNumData=512
nFormat=(nToneIndex(dec),nHlog(dec)) nData="
(0000,1023) (0001,1023) (0002,1023) (0003,1023) (0004,1023) [.../snip]"
DSL_CPE#>g997dhlogg 0 1
nReturn=0 nDirection=0 nDeltDataType=1 nMeasurementTime=128 nGroupSize=8 nNumData=512
nFormat=(nToneIndex(dec),nHlog(dec)) nData="
(0000,1023) (0001,0140) (0002,0091) (0003,0088) (0004,1023) [....../snip]"
DSL_CPE#>g997dqlng 1 1
nReturn=0 nDirection=1 nDeltDataType=1 nMeasurementTime=4 nGroupSize=8 nNumData=512
nFormat=(nToneIndex(dec),nQln(dec)) nData="
(0000,255) (0001,255) (0002,255) (0003,255) [../snip]"
DSL_CPE#>g997dqlng 0 1
nReturn=0 nDirection=0 nDeltDataType=1 nMeasurementTime=1024 nGroupSize=8 nNumData=8704
nFormat=(nToneIndex(dec),nQln(dec)) nData="
(0000,255) (0001,191) (0002,183) (0003,177) (0004,255) (0005,255) (0006,255) (0007,255) (0008,255) (0009,255) [.../snip]"
-
g997amdpfcg, G997_AlarmMaskDataPathFailuresConfigGet
g997amdpfcs, G997_AlarmMaskDataPathFailuresConfigSet
g997amlfcg, G997_AlarmMaskLineFailuresConfigGet
g997amlfcs, G997_AlarmMaskLineFailuresConfigSet
g997bang, G997_BitAllocationNscGet
g997bansg, G997_BitAllocationNscShortGet
g997cdrtcg, G997_ChannelDataRateThresholdConfigGet
g997cdrtcs, G997_ChannelDataRateThresholdConfigSet
g997csg, G997_ChannelStatusGet
g997dpfsg, G997_DataPathFailuresStatusGet
g997dfr, G997_DeltFreeResources
g997dhling, G997_DeltHLINGet
g997dhlinsg, G997_DeltHLINScaleGet
g997dhlogg, G997_DeltHLOGGet
g997dqlng, G997_DeltQLNGet
g997dsnrg, G997_DeltSNRGet
g997fpsg, G997_FramingParameterStatusGet
g997gang, G997_GainAllocationNscGet
g997gansg, G997_GainAllocationNscShortGet
g997lstg, G997_LastStateTransmittedGet
g997lacg, G997_LineActivateConfigGet
g997lacs, G997_LineActivateConfigSet
g997lfsg, G997_LineFailureStatusGet
g997lisg, G997_LineInitStatusGet
g997lig, G997_LineInventoryGet
g997listrg, G997_LineInventorySTRingGet
g997lis, G997_LineInventorySet
g997lsg, G997_LineStatusGet
g997lspbg, G997_LineStatusPerBandGet
g997ltsg, G997_LineTransmissionStatusGet
g997lpmcg, G997_LowPowerModeConfigGet
g997lpmcs, G997_LowPowerModeConfigSet
g997pmsft, G997_PowerManagementStateForcedTrigger
g997pmsg, G997_PowerManagementStatusGet
g997racg, G997_RateAdaptationConfigGet
g997racs, G997_RateAdaptationConfigSet
g997sang, G997_SnrAllocationNscGet
g997sansg, G997_SnrAllocationNscShortGet
g997upbosg, G997_UsPowerBackOffStatusGet
g997xtusecg, G997_XTUSystemEnablingConfigGet
g997xtusecs, G997_XTUSystemEnablingConfigSet
g997xtusesg, G997_XTUSystemEnablingStatusGet
-
has anyone asked if dslstats could include support for this modem?
I'm sorry, but I won't have the time to do this.
-
To give roseway a manageable task I think a script would have be added to the firmware to generate output that identically or very closely followed the HG612 output for the needed commands. A script for the main stats (as from xdslcmd info --stats) alone would be well worth it - it would alow snr and error and status monitoring, then bit loading and snr/tones would be my second priorities. If you needed Hlog or QLN which are only updated at sync you could get them manually.
-
To give roseway a manageable task I think a script would have be added to the firmware to generate output that identically or very closely followed the HG612 output for the needed commands. A script for the main stats (as from xdslcmd info --stats) alone would be well worth it - it would alow snr and error and status monitoring, then bit loading and snr/tones would be my second priorities. If you needed Hlog or QLN which are only updated at sync you could get them manually.
That was in my thinking, cloning of the HG612's xdslcmd. However, I believe this program only supports telnet and not SSH?
I could of course recompile the images with busybox login support for telnet. Telnet is supported, but only if no password is set. When a password is set SSH is enabled. Not setting a password will only leave it open for the network, not the outside world of course since by default the outside world doesn't have access to the modem.
I'll setup my HG612 and make an alias for the differences.
-
I've always found it weird that OpenWRT insists on using SSH.
OpenWRT does use BusyBox, the same as HG612, so I'm wondering if perhaps it might work via SSH? I really haven't researched it in much depth though.
-
I'm currently flashing OpenWRT on my ECI v2 (very slowly). I didn't even need to solder: I just held the header pins over the pin ports on the board.
-
I've always found it weird that OpenWRT insists on using SSH.
OpenWRT does use BusyBox, the same as HG612, so I'm wondering if perhaps it might work via SSH? I really haven't researched it in much depth though.
The Windows version of dslstats would need to bundle a ssh client like PuTTY which I very much doubt it does. It won't take long to rebuild with full telnet support though.
-
Telnet isn't supported by default because most consider it a security risk, ie easily sniffed. It's quite an old protocol and has no encryption support due to the excessive packets and overheads.
-
I've always found it weird that OpenWRT insists on using SSH.
OpenWRT does use BusyBox, the same as HG612, so I'm wondering if perhaps it might work via SSH? I really haven't researched it in much depth though.
it isnt weird, its for security reasons.
In the modern world telnet is obselete, but its still used by routers as most router vendors are about a decade behind on security and technology.
-
Right I've tried to flash OpenWRT three times now and each time it gets the file via TFTP fine but when I reboot the modem it fails to boot :(
-
Right I've tried to flash OpenWRT three times now and each time it gets the file via TFTP fine but when I reboot the modem it fails to boot :(
What are the errors you're getting?
I assume you've used the V2 image, but did you remember to change the uboot variables accordingly?
set ipaddr 192.168.1.100
set serverip 192.168.1.1
set bootfile openwrt-lantiq-xrx200-VG3503J_V2-squashfs.image
set bootcmd cp.b 0xb0020000 0x80002000 0x400000\; go 0x80002000
set preboot ping 1.1.1.1\;run bootcmd
set update_openwrt erase 0xb0020000 0xb073ffff\;tftp 0x81000000 openwrt-lantiq-xrx200-VG3503J_V2-squashfs.image\;cp.b 0x81000000 0xb0020000 \$(filesize)
saveenv
run update_openwrt
reset
-
Silly me, I'd forgotton the saveenv line! :P
I've flashed the non-G.INP image. If I want to flash the G.INP image I assume I just follow the same process?
Just out of interest, if you flashed the V1 image onto the V2 (I didn't! ;)), you say it would effectively brick the modem. Could this be undone or is this permanent?
-
Panic over! :D
The next time you want to flash an image, just setup tftp and run "run update_openwrt" and "reset" since the variables are now saved.
Yes, it can be undone but by "bricking it" i mean OpenWrt will boot, but your ethernet ports won't work and you'll need to dabble with the serial again to fix it. The v2 image vs v1 has just a phy driver change :)
-
Line Mode: G.993.2 (VDSL2) Annex B Profile 17a
Status & Uptime: UP 2h 43m 14s
Line State: showtime_tc_sync [0x801]
Power Mode: L0 - Synchronized
DSLAM/MSAN VID: IFTN
Alignment: Downstream Upstream
Attainable Line Speed: 100.285 Mb/s 22.225 Mb/s
Actual Line Speed: 48.994 Mb/s 11.993 Mb/s
Trellis: D: ON U: ON
Bitswap: D: OFF U: OFF
G.INP: D: Not Enabled U: Not Available
Virtual Noise Support: D: Not Supported U: Not Supported
Interleave Depth: 1 381
Interleave Block: 255 32
Interleave Delay: 0ms 4ms
NFEC: 255 32
RFEC: 16 16
LSYMB: 13147 6096
LPATH: 0 0
INP: 0.0 4.0
Line Attenuation: 9.0 dB 10.3 dB
Noise Margin/SNR: 20.7 dB 13.1 dB
Transmit Power: -2.-3 dB 12.6 dB
Errors
ES: 0 1
SES: 0 0
UAS: 0 1
FEC: 0 214
CRC_P: 0 0
CRCP_P: 0 0
Hopefully DLM removes the cap on my IP profile soon as I have yet to test the throughput. I really wish we could disable this rubbish for situations like hardware testing!
-
All setup - unfortunately syncing about 7Mb lower than my Billion 8800NL.
How would I configure the ECI to act as a router as well as a modem? :)
-
All setup - unfortunately syncing about 7Mb lower than my Billion 8800NL.
How would I configure the ECI to act as a router as well as a modem? :)
Hopefully within time it might sort itself out :)
You can connect LAN2 and use it that way, though it requires you set a static IP. If you want DHCP re-enabled,
login via SSH and nano /etc/config/dhcp
Change
config dhcp 'lan'
option interface 'lan'
option ignore '1'
to something like
config dhcp 'lan'
option 'interface' 'lan'
option 'start' '100'
option 'limit' '150'
option 'leasetime' '12h'
option ra server
option dhcpv6 server
and
/etc/init.d/dhcp restart
-
Oh is there an adjustment period when you change the chipset? I've only ever used Broadcom so I've never had a chance to test it.
I had interleaving reduced to a depth of 1 on the upstream today so I've got a couple of Mb back but the ECI is still 2Mb slower than the Broadcom modems I've used :(
So the way you've described will allow me to plug a device into LAN2 and Internet will work via this port?
-
There is I believe, and the DSLAM might resync and realize the CPE has a different chipset but I don't know. Or it could be that you've switched the modems too quickly and the DSLAM has lowered it a tad, but will fix itself.
Sorry, lack of sleep :-[
The way I've set it up by default is LAN1 > Router WAN, LAN2 > Router LAN.
I assume the way you want it setup is
LAN1 > Router WAN
LAN2 > PC?
That configuration _should_ work out of the box too.
-
Well actually I wanted both ports to go to a PC :)
-
I think I have killed my ECI /r V 1.1 attempting to install OpenWRT
I had an old spare ECI which I had attached the UART header to some time ago.
Well i ran all the instructions up to and including the run update_openwrt but when this
got to the copy to flash part it just kept coming up with something about protected
At this stage I thought that if I had any issues I would be able to use UBoot and try again
so I went ahead and did the reset as I could think of no other way to get past the issue.
Now I can get UBoot but there is no images in the flash as I guess the erase command from the
update_openwrt has wiped them (just get bad magic number messages)
Problem is I don't appear to be able to get the VR9 switch to operate anymore, no lights when ping etc
and cable disconnected on the laptop. Tried alternate RJ45 cables but no joy.
Am I correct in thinking that UBoot does is not enough environment to actually use the VR9 switch ports native?
When I try a ping it says using VR9 Switch device and then a while later comes up with host is not alive
(no lights on the LAN port come on).
Oh well you win some and you lose some ..... it was only a cheap spare that I never use as I have 2 HG612's
and a Billion 8800NL for connection, just liked OpenWRT which I ran on the homehub 2 some years back with ADSL.
-
When you turn on the ECI modem with the UART connected, what do you see?
Could you post the output?
-
Well I found I had another ECI modem hiding away in the cupboard, this one a V 1.2
It also had a header from UART in place as I had looked at an unlock some time ago.
So off I went with all the instructions again (remembering to use the V2 test image this time)
and hey presto it has worked and I now have OpenWRT running.
Now the new setup has the modem on IP address 192.168.1.1 which clashes with my ASUS RT-AC87U router
I can see the WAN bridge and LAN settings page (when plugged into LAN 2 with a static of 192.168.1.100
on the laptop) but not sure how to best change this to say 192.168.2.1
I could change the ASUS to operate on the 192.168.2.x subnet I guess as an alternate option.
At present I have an additional interface on the ASUS eth0.1 which uses 192.168.2.253 and an IPTABLES
command to route all traffic for this subnet down the WAN link allowing me to access the router (HG612) via a single
cable running both PPPoE and LAN. The HG612 is on address 192.168.2.254 and has the PPPoE vlan unbound from
LAN port 1.
Can the ECI with OpenWRT be made to operate in the same way ?
I plan to try the ECI on the line tomorrow (I am on a Huawei cab with G.Inp enabled so can see if it is picked up ok)
Just spotted your reply AlecR while creating the above post .....
Then other (broken) ECI displays the following at startup
ROM VER: 1.0.5
CFG 01
DDR Access auto data-eye tuning Rev 0.3a
DDR size from 0xa0000000 - 0xa1ffffff
DDR check ok... start booting...
U-Boot 1.0.4 (Oct 18 2010 - 16:20:02)
CLOCK CPU 333M RAM 166M
DRAM: 32 MB
relocate_code start
relocate_code finish.
FLASH MANUFACT: c2
FLASH DEVICEID: cb
Flash: 8 MB
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: fw_addr=0xa0200000
Internal phy(FE) firmware version: 0xffff
vr9 Switch
Type "run flash_flash" to mount root filesystem over flash
Hit 'Esc' key to stop autoboot: 0
## Booting image from active region 1 at 80800000 ...
Check RSA image magicBad Magic Number
Retry another region
## Booting image from active region 2 at b03f0000 ...
Check RSA image magicBad Magic Number
VR9 #
VR9 # ping 192.168.1.100
Using vr9 Switch device
ping failed; host 192.168.1.100 is not alive
VR9 #
-
So you can't type anything next to VR9 #?
-
Yes I can type anything , above I tried a ping 192.168.1.100 (the laptop connected to LAN1 port)
but no port lights (amber or green) and a cable disconnected showing on laptop then router
gives not alive response after about 15-20 seconds.
-
Then you should be able to follow the instructions to flash OpenWRT again and it should work perfectly :)
-
I have tried a couple of times but with the LAN link down the TFTP never
connects and downloads the image, it just keeps displaying T T T T then
times out and repeats over and over.
I will have another go at it tomorrow but now I have a working V1.2 ECI I am
less bothered about the V1.1 broken one (I think something may have gone
on the electronics to the LAN ports that just happened to be at the same time I was
working on the device.
-
I believe you might have flashed the V2 image on the V1 as previously jsamuel said the ethernet ports not working was a symptom of this :)
He also said it should be recoverable so I suspect he can provide assistance soon :)
-
Well actually I wanted both ports to go to a PC :)
You could have both connect to a PC and just have the modem do PPPoE.
this would result in a /etc/config/network change to something like:
config interface 'wan'
option _orig_ifname 'eth0'
option _orig_bridge 'true'
option ifname 'eth0'
option proto 'pppoe'
option username 'user@isp'
option password 'password'
config interface 'wan6'
option ifname '@wan'
option proto 'dhcpv6'
config interface 'lan'
option ifname 'eth1'
option type 'bridge'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'
I think I have killed my ECI /r V 1.1 attempting to install OpenWRT
I had an old spare ECI which I had attached the UART header to some time ago.
Well i ran all the instructions up to and including the run update_openwrt but when this
got to the copy to flash part it just kept coming up with something about protected
At this stage I thought that if I had any issues I would be able to use UBoot and try again
so I went ahead and did the reset as I could think of no other way to get past the issue.
Now I can get UBoot but there is no images in the flash as I guess the erase command from the
update_openwrt has wiped them (just get bad magic number messages)
Problem is I don't appear to be able to get the VR9 switch to operate anymore, no lights when ping etc
and cable disconnected on the laptop. Tried alternate RJ45 cables but no joy.
Am I correct in thinking that UBoot does is not enough environment to actually use the VR9 switch ports native?
When I try a ping it says using VR9 Switch device and then a while later comes up with host is not alive
(no lights on the LAN port come on).
Oh well you win some and you lose some ..... it was only a cheap spare that I never use as I have 2 HG612's
and a Billion 8800NL for connection, just liked OpenWRT which I ran on the homehub 2 some years back with ADSL.
That sounds rather strange to me :( I'm not sure what has happened.
Did you change any of the variables, or do anything differently?
ping 1.1.1.1 host not alive should always be the case as that's just there so the bootloader has time to see your break command to get into uboot.
Just after it displays lines of "........." to indicate it's wiping those partitions you could try setting up tftpd at that point as sometimes the modem won't recognize any connections until then. Are you using Linux or Windows?
-
What I meant was, I'd like the ECI modem to do the routing (i.e the PPPoE - DHCP in my case as I use TalkTalk Fibre) and for the router to get a local IP from the ECI and thus have Internet :)
-
What I meant was, I'd like the ECI modem to do the routing (i.e the PPPoE - DHCP in my case as I use TalkTalk Fibre) and for the router to get a local IP from the ECI and thus have Internet :)
The above will be able to do that, and then my DHCP change from earlier on if you need it :)
Well I found I had another ECI modem hiding away in the cupboard, this one a V 1.2
It also had a header from UART in place as I had looked at an unlock some time ago.
So off I went with all the instructions again (remembering to use the V2 test image this time)
and hey presto it has worked and I now have OpenWRT running.
Now the new setup has the modem on IP address 192.168.1.1 which clashes with my ASUS RT-AC87U router
I can see the WAN bridge and LAN settings page (when plugged into LAN 2 with a static of 192.168.1.100
on the laptop) but not sure how to best change this to say 192.168.2.1
I could change the ASUS to operate on the 192.168.2.x subnet I guess as an alternate option.
At present I have an additional interface on the ASUS eth0.1 which uses 192.168.2.253 and an IPTABLES
command to route all traffic for this subnet down the WAN link allowing me to access the router (HG612) via a single
cable running both PPPoE and LAN. The HG612 is on address 192.168.2.254 and has the PPPoE vlan unbound from
LAN port 1.
Can the ECI with OpenWRT be made to operate in the same way ?
I plan to try the ECI on the line tomorrow (I am on a Huawei cab with G.Inp enabled so can see if it is picked up ok)
Just spotted your reply AlecR while creating the above post .....
Then other (broken) ECI displays the following at startup
ROM VER: 1.0.5
CFG 01
DDR Access auto data-eye tuning Rev 0.3a
DDR size from 0xa0000000 - 0xa1ffffff
DDR check ok... start booting...
U-Boot 1.0.4 (Oct 18 2010 - 16:20:02)
CLOCK CPU 333M RAM 166M
DRAM: 32 MB
relocate_code start
relocate_code finish.
FLASH MANUFACT: c2
FLASH DEVICEID: cb
Flash: 8 MB
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: fw_addr=0xa0200000
Internal phy(FE) firmware version: 0xffff
vr9 Switch
Type "run flash_flash" to mount root filesystem over flash
Hit 'Esc' key to stop autoboot: 0
## Booting image from active region 1 at 80800000 ...
Check RSA image magicBad Magic Number
Retry another region
## Booting image from active region 2 at b03f0000 ...
Check RSA image magicBad Magic Number
VR9 #
VR9 # ping 192.168.1.100
Using vr9 Switch device
ping failed; host 192.168.1.100 is not alive
VR9 #
Sorry, I just saw this post. It seems I'm not getting emails for newer posts until I read the previous one.
Set the Asus to 192.168.1.2 as by default that's the gateway. Or you can edit /etc/config/network and change
option ipaddr '192.168.1.1'
option gateway 192.168.1.2
to
option ipaddr '192.168.2.254'
option gateway 192.168.2.1 # router
The above indicates there's no squashfs image and that you've wiped the partitions. it seems like it's not been loaded properly and you are having trouble with tftpd.
-
Sorry, I just saw this post. It seems I'm not getting emails for newer posts until I read the previous one.
Go to your profile > modify profile > Notifications. Make sure you dont have "only for the first reply" set.
-
From the small amount of "breaking and fixing" I have done today, it seems quite difficult to truly brick one of these modems.
-
Thanks, Kitz. All fixed ;D
AlecR, I managed to brick two when learning. :-[
Note, always make sure it can ping something on boot, even if the host doesn't exist otherwise you won't be able to get back into the uboot prompt for some strange reason.
-
But what I mean is, you seem to always recover it via UART.
-
Except in the situation above, UART becomes useless and you'd need to JTAG. :D
PN are sending out an Openreach engineer to reset my IP profile at the cab and check external wiring, hopefully my line will stabilize after that. Atleast I have a few more days of tinkering with the ECI to clone xdslcmd output and I shouldn't care if I upset DLM anymore than I already have :)
-
Does JTAG use the same pins?
It would be useful to know for future reference :)
-
The JTAG pins are below the serial :)
Very similar to the old ECI /i
(https://hackingecibfocusv2fubirevb.files.wordpress.com/2012/07/eci_012.jpg)
-
So many pins...
-
Is your sync getting better? :)
-
VDSL2User
After some hours of sleep I have noticed this is an ECI /i
This isn't supported by OpenWrt unfortunately.
ROM VER: 1.0.5
CFG 01 ...
DDR size from 0xa0000000 - 0xa1ffffff
ROM VER: 1.0.5
DDR size from 0xa0000000 - 0xa3ffffff
-
Yes you are spot on it is an ECI /I ... how silly of me not to spot that on the label earlier ...
oh well that explains why it did not work, still it was only an old spare so no problems really
As for the other ECI /R V1.2 that I got to work I moved my ASUS to 192.168.1.2 and plugged it up.
It got sync OK but is the LAN1 LED (the WAN link to router) meant to blink at rapid pace non stop all the time ?
Also I had to connect a second cable to LAN 2 in order to access 192.168.1.1 for browser to work, need to see
if this can be done down the single LAN1 PPPoE cable link
It was only on the line for a few minutes as it was showing massive number of ES - it racked
up 542 in under 5 minutes and also almost 5300 FEC in same time.
The HG612 has been reconnected for 21 minutes and has zero ES and only 54 FEC, it never gets ES on DL now
with G.INP
The ECI did show G.INP enabled on DL but not on UL (same as HG612 on my line) however it showed interleave as 1
for both UL and DL but HG612 has DL showing at INT 8 with G.INP
Maybe the stats from ECI are not totally correct .....
I need to leave HG612 in place now for a while to ensure I don't upset DLM but will continue to look at the ECI
config offline ....
-
Yes you are spot on it is an ECI /I ... how silly of me not to spot that on the label earlier ...
oh well that explains why it did not work, still it was only an old spare so no problems really
As for the other ECI /R V1.2 that I got to work I moved my ASUS to 192.168.1.2 and plugged it up.
It got sync OK but is the LAN1 LED (the WAN link to router) meant to blink at rapid pace non stop all the time ?
Also I had to connect a second cable to LAN 2 in order to access 192.168.1.1 for browser to work, need to see
if this can be done down the single LAN1 PPPoE cable link
It was only on the line for a few minutes as it was showing massive number of ES - it racked
up 542 in under 5 minutes and also almost 5300 FEC in same time.
The HG612 has been reconnected for 21 minutes and has zero ES and only 54 FEC, it never gets ES on DL now
with G.INP
The ECI did show G.INP enabled on DL but not on UL (same as HG612 on my line) however it showed interleave as 1
for both UL and DL but HG612 has DL showing at INT 8 with G.INP
Maybe the stats from ECI are not totally correct .....
I need to leave HG612 in place now for a while to ensure I don't upset DLM but will continue to look at the ECI
config offline ....
LAN1 led blinking all the time is intended as it'll be sending data to your router's WAN all the time. Since LAN1 goes to WAN on your router, you can't access the modem using just LAN1 :( that's why you need to connect LAN2 to your routers LAN port.
Showing FEC errors is good and it means your CPE is trying to correct the errrors on your line. This should return to normal after 24 hours. It's good that G.INP works on downstream but have you tried the test image?
G.INP is enabled on the upstream. Can you also post your stats from calling
killall cat;killall dsl_control;/etc/init.d/dsl_control extra
:)
http://vanquishsolutions.co.uk/openwrt/testing/
-
Yes I was using the test image but on my Huawei cabinet my profile appears to now be set
to have G.INP on DL and Fastpath on UL.
It's a shame about the need for a second cable as this is now one of the nice features of
the HG612 now which runs on a single cable with WAN PPPoE and a LAN subnet operating over it.
I run the HG612 on subnet 192.168.2.x and just add an alias interface to the ASUS for this subnet
over the WAN interface then using IPTABLES route all traffic for the subnet to the alias.
I don't really have any spare LAN ports on the router and would need to use a switch to run 2 cables.
The FEC are OK but if those reported error seconds were correct then there is no way I can run an ECI on my line as it would hit DLM hard.
-
Yes I was using the test image but on my Huawei cabinet my profile appears to now be set
to have G.INP on DL and Fastpath on UL.
It's a shame about the need for a second cable as this is now one of the nice features of
the HG612 now which runs on a single cable with WAN PPPoE and a LAN subnet operating over it.
I run the HG612 on subnet 192.168.2.x and just add an alias interface to the ASUS for this subnet
over the WAN interface then using IPTABLES route all traffic for the subnet to the alias.
I don't really have any spare LAN ports on the router and would need to use a switch to run 2 cables.
The FEC are OK but if those reported error seconds were correct then there is no way I can run an ECI on my line as it would hit DLM hard.
If fastpath is on UL your cab hasn't enabled G.INP for upstream :)
I'm probably wrong about the second cable thing, I was always under the impression most routers weren't capable of doing this on WAN.
You could of course try editing the network configuration file, SSH into your modem and
nano /etc/config/network
Locate
config interface 'wan'
option ifname 'eth0'
option force_link '1'
Change to
config interface 'wan'
option ifname 'eth0'
option force_link '1'
option proto 'static'
option ipaddr '192.168.2.1'
option gateway 192.168.1.2
option netmask '255.255.255.0'
option ip6assign '60'
option dns '208.67.222.222 208.67.220.220'
Remove
config interface 'lan'
option ifname 'eth1'
option force_link '1'
option proto 'static'
option ipaddr '192.168.1.1'
option gateway 192.168.1.2
option netmask '255.255.255.0'
option ip6assign '60'
option dns '208.67.222.222 208.67.220.220'
Let me know how to get on :)
-
And don't forget to restart the interfaces or reboot failing that.
/etc/init.d/network restart
-
A note of warning on the new MEI firmware
When running
vdsl_cpe_control --c
the line goes down and resyncs. Please don't call this command as it could severely wreck havoc on DLM.
I'm working on a fix.
-
Here's some fixes/additions, updated the main images and removed /testing since they're not needed :)
drv_dsl_cpe_api.c - G.INP upstream enabled (thanks to TP-Link) applied to main image since tests on Huawei cabinets passed. The ECI /r is fully G.INP compatible now and vectoring will be too in about a month. Hopefully BT sort their ltq cabs out soon..
lantiq_dsl.sh - Fixed dbt() where expr for ACTATP would output negatives for numerics following decimals eg: -2.-8 dB should really be -2.8 dB.
Added a few more extras to dsl_control/LuCI and there's no real need to run vdsl_cpe_control, I did plan to redesign the bootstrap theme to make it look less messy but it'll do for now.
These will be my last changes for a while, or until a firmware is found with vectoring support unless either
A. I decide to put time into making the LuCI boostrap theme better.
B. I figure out a way to graph remotely and pull from the modem (other than munin-node, I want something Windows users can enjoy too) or
C. someone finds some bugs.. because to me it looks pretty complete minus graphing, unfortunately I won't be able to have time to make this compatible with dslstats because to be quite honest I've looked through the source for it and I wouldn't know where to begin so I gave up on that part, sorry. :( It would've been nice to have though, perhaps someone else can have a look into this if it's needed.
Have fun testing! Now I must call the engineer to fix my IP Profile from all of these manual disconnections and let DLM settle :lol: Until next time..
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FLsWBK4R.png&hash=1a8d1aa7cef720c63226dba1ff6b7d023ab9ccb5)
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FWQoFJWo.png&hash=98917e449672214f407e1db6985424adf62f6a33)
-
Thank you, jsamuel, for all your excellent work.
-
These will be my last changes for a while, or until a firmware is found with vectoring support unless either
A. I decide to put time into making the LuCI boostrap theme better.
B. I figure out a way to graph remotely and pull from the modem (other than munin-node, I want something Windows users can enjoy too) or
C. someone finds some bugs.. because to me it looks pretty complete minus graphing, unfortunately I won't be able to have time to make this compatible with dslstats because to be quite honest I've looked through the source for it and I wouldn't know where to begin so I gave up on that part, sorry. :( It would've been nice to have though, perhaps someone else can have a look into this if it's needed.
If you were interested in converting the output data to the same format as the output data from a Huawei HG612 modem & saving it to plain text file(s), even if dummy or blank data is used in places, then the graphing programs from HG612 Modem Stats would work as they are for Windows users.
This could be either for snapshot data and/or if collected every minute, for ongoing data.
FWIW, Plink is the command line 'sister' version to PuTTY & can be run via a script (Linux bash script or Windows batch file) to harvest the data whenever required.
-
I have some dumb questions, I'm just about to destroy ... I mean solder, some pins onto my ECI modem so I can get some stats. Would you recommend OpenWrt over other options? Also how do I tell the difference between ECI/r v1 or v2?
-
Openwrt is a great option and makes the modem a treat to use, I would recommend
it over the other 'hacking' options for the ECI /r
You will find the version printed on the main chip on the modem motherboard
either V1.1 or V1.2
A big thank you to jsamuel for all the hard work done on this.
-
A big thank you to jsamuel for all the hard work done on this.
All techno-kittehs will whole-heartedly second that "thank you" to jsamuel. :thumbs: :drink:
[Request to our leader, Kitz: Could this thread be granted "sticky" status, please?]
-
Thank you guys. But I couldn't have done it without the help of some posts contributed by Kitz users I've come across during this feast. :) I'll do my best to keep it and the lantiq drivers/firmware updated and see about those lovely graphs we all crave..
-
That is interesting Bald_Eagle1 I've never come across those programs until now!
I'll have a tinker and post my findings :)
-
Managed, despite my third rate soldering ability, to get this done last night :yay:
Initial impressions are that this is great, so well done jsamuel. :clap:
EDIT:
Might be useful for people not too keen about drilling the circuit board, or who don't have the equipment, you can use this method to solder your serial header pins - http://www.instructables.com/id/Soldering-headers-without-drilling-holes/?ALLSTEPS
-
You'll have to be extra careful doing it that way, since the solder pads are thin tin layered on copper tracers and it's possible to tear them off by accident requiring more than a headache to fix. :'(
Then again, what am I even talking about. The pads are solid on this and you need to drill through them to even get through. It's the BT HH5A my sleep deprived brain is rethinking of. :-X
-
That is interesting Bald_Eagle1 I've never come across those programs until now!
I'll have a tinker and post my findings :)
See the attached example of the snapshot graph montage.
The Plink log file contains the data needed to generate the graphs.
-
That is interesting Bald_Eagle1 I've never come across those programs until now!
I'll have a tinker and post my findings :)
See the attached example of the snapshot graph montage.
The Plink log file contains the data needed to generate the graphs.
Oh my :-[
Those tones will be a nightmare to duplicate. Broadcoms xdslcmd is much neater at doing those than lantiq is with vdsl_cpe_control
Everything else would be surprisingly easy to do though.
Is the xdslcmd info --stats output all that is required to generate graphs?
I see, the whole shebang is there :) I'll try and see what I can do. Thank you for this.
-
No. The tone data is also needed (Bits, SNR, QLN, Hlog).
I have a vague memory that Asbokid wrote a Linux script a long time ago to obtain/provide such data via an ECI modem in order to generate the same graphs.
I'll see if I can find it as it may be of some assistance.
-
Main stats: xdslcmd info --stats
Bitloading: xdslcmd info --Bits
pbParams: xdslcmd info --pbParams
SNR per tone: xdslcmd info --SNR
QLN: xdslcmd info --QLN
Hlog: xdslcmd info --Hlog
Those are the main commands. On VDSL2 systems the pbParams output is needed to determine the band plan which is in use. This is necessary for the correct presentation of the "per tone" graphs.
[Edit - corrected the pbParams command]
-
jsamuel if I send you an ECI would you flash it for me? I will cover postage both ways, and is there a fee if you do this?
Thanks
-
I don't know if this might help to get started:-
Band Boundary Status for the ECI /r
# # band boundary status get (upstream)
# echo "bbsg 0" > /tmp/pipe/dsl_cpe0_cmd ; cat /tmp/pipe/dsl_cpe0_ack
nFormat=(nBandIndex, (nLimit_firstToneIndex, nLimit_lastToneIndex), (nBorder_firstToneIndex, nBorder_lastToneIndex)) nData="
(00,(0007,0032),(0008,0031))
(01,(0871,1205),(0880,1196))
(02,(1972,2696),(0000,0000))
"
# # band boundary status get (downstream)
# echo "bbsg 1" > /tmp/pipe/dsl_cpe0_cmd ; cat /tmp/pipe/dsl_cpe0_ack
nReturn=0 nDirection=1 nNumData=3
nFormat=(nBandIndex, (nLimit_firstToneIndex, nLimit_lastToneIndex), (nBorder_firstToneIndex, nBorder_lastToneIndex)) nData="
(00,(0033,0859),(0033,0859))
(01,(1216,1961),(1216,1916))
(02,(2793,3863),(3131,3732))
"
#
Band Boundary Status for the ECI /I
# # band boundary status get (upstream)
Alpha # echo "bbsg 0" > /tmp/pipe/dsl_cpe0_cmd ; cat /tmp/pipe/dsl_cpe0_ack
nReturn=0 nDirection=0 nNumData=3
nFormat=(nBandIndex, (nLimit_firstToneIndex, nLimit_lastToneIndex), (nBorder_firstToneIndex, nBorder_lastToneIndex)) nData="
(00,(0010,0031),(0010,0031))
(01,(0882,1193),(0882,1193))
(02,(1984,2770),(1984,2770))
"
# # band boundary status get (downstream)
Alpha # echo "bbsg 1" > /tmp/pipe/dsl_cpe0_cmd ; cat /tmp/pipe/dsl_cpe0_ack
nReturn=0 nDirection=1 nNumData=3
nFormat=(nBandIndex, (nLimit_firstToneIndex, nLimit_lastToneIndex), (nBorder_firstToneIndex, nBorder_lastToneIndex)) nData="
(00,(0033,0857),(0033,0857))
(01,(1218,1959),(1218,1959))
(02,(2795,3950),(2795,3935))
"
-
jsamuel if I send you an ECI would you flash it for me? I will cover postage both ways, and is there a fee if you do this?
Thanks
You could potentially have mine if you want it. It's a V2.1 flashed with OpenWRT.
-
Only replicating xdslcmd info --stats via telnet on its own would I think be great step and should enable a small mod of dslstats to provide basic data. This would allow you to monitor the connection even if tones and etc. were not visible.
-
& combined with the equivalent of xdslcmd info --pbParams data, the attached 'ongoing' graphs (plus others) could be generated via HG612 Modem Stats.
The first example is without G.INP & the second is what it could look like once G.INP is available for ECI DSLAMS/Modems
-
To add to that. If a particular value is not available then a zero value that preserves the format should suffice.
-
Anyone having any problems with the Status->Overview menu option? When the modem first starts up the stats look mostly believable but when I start visiting the page again things either don't load(stuck collecting data) or I get an image like the one attached.
I've tried doing a "Reset to defaults" under System->Backup/Flash Firmware->Flash Operations but stats still are not displaying/properly(the modem is up though stats say it's down).
-
Problem solved, stats back,I think. Not clear whether it was my fault or not - edited lantiq_dsl.sh so that XDSL_CTRL always equals "vdsl_cpe_control" to solve my issue.
-
I can confirm this does happen sometimes, I haven't figured out how to fix it so far.
This happens when /tmp/pipe/dsl_cpe0_ack is locked up, preventing any data to be collected. It happens when dsl_control is run from both LuCI and your terminal at the same time. To fix it you need to killall cat or sometimes killall dsl_control
-
jsamuel if I send you an ECI would you flash it for me? I will cover postage both ways, and is there a fee if you do this?
Thanks
You could potentially have mine if you want it. It's a V2.1 flashed with OpenWRT.
You can flash this version in this thread?
-
I can confirm this does happen sometimes, I haven't figured out how to fix it so far.
This happens when /tmp/pipe/dsl_cpe0_ack is locked up, preventing any data to be collected. It happens when dsl_control is run from both LuCI and your terminal at the same time. To fix it you need to killall cat or sometimes killall dsl_control
Ah, right, I assumed it wasn't getting any data but didn't really understand why - I know nothing about this software ... :hmm:
-
Depending If AlecR gives you his, yes I could do it for free minus shipping back and forth.
AlecR
I'm guessing the ECI /r didn't stabilize on your line then? :(
-
once this openwrt version is on the ECI can further flashes be done normally over Ethernet? e.g. if you do updates.
-
I'm guessing the ECI /r didn't stabilize on your line then? :(
Sync speed is still lower than the 8800NL unfortunately :(
I've got another one coming anyway so I really don't need two!
-
once this openwrt version is on the ECI can further flashes be done normally over Ethernet? e.g. if you do updates.
From OpenWrt's wiki:
Bootloader contains TFTP server
The basic procedure of using a tftp client to upload a new firmware to your router:
Unplug the power to your router
Plug the Ethernet connection from your computer (acting as tftp client) into a LAN port on your model. See your model's OpenWRT wiki for details on which port to use
Start your tftp client on your computer
Give it the router's address (specific to model and bootloader, see your model's wiki page)
Set mode to octet/binary
Tell the client to resend the file until it succeeds
"put" the file
Plug-in your router while having the tftp client running and constantly probing for a connection
The tftp client will receive an ack from the bootloader and starts sending the firmware
-
ok so ethernet works, but still seems a messy process, other firmwares you can just update from the gui normally.
-
All techno-kittehs will whole-heartedly second that "thank you" to jsamuel. :thumbs: :drink:
[Request to our leader, Kitz: Could this thread be granted "sticky" status, please?]
Done :)
-
Done :)
Purrfect! ;)
-
I'm glad I could be of some help :)
I'm currently dabbling around with RRDTool (https://oss.oetiker.ch/rrdtool/gallery/index.en.html), a program that runs on the modem end. Data to make the graphs can be pulled from "data sets" stored from a file, a file which cronjob runs commands into /tmp/pipe/dsl_cpe0_cmd, and then grepping /tmp/pipe/dsl_cpe0_ack into the file every 5 seconds or so. With 500kb to spare, there's enough room to log stats and graphs for atleast a year. I can also utilize the ECI /r's spare 16MB of ram to its full potential. This will be done with perl.
We can make pretty graphs like this.
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi.imgur.com%2Fp9bMJKH.png&hash=72ece891aa10cf8b4abe731bc2bd732dd7fe9f4e)
which can then be viewed from the LuCI frontend.
I'll follow up with updates and of course share my work.
-
That looks really promising - excellent work! :D
-
This will be done with perl.
Into each life some rain must fall ... ;)
-
This will be done with perl.
Into each life some rain must fall ... ;)
:lol:
-
I've read this thread with interest and decided to try the openwrt prepared by jsamuel - thanks! Like many others with an ECI on a Huawei cabinet I suffered when G.INP was enabled and bought a HG612 off Ebay which fixed the very high latency with the ECI. But it would be good to have the ECI as a functional backup with G.INP enabled.
I tried the /etc/config/network changes suggested in post #76 but don't think they'll work. At least not for me. The modem isn't connected to the VDSL line which make make a difference. Although the ipaddress is correctly assigned to eth0 after reboot, no traffic flows when pinging a local address. I can also change the config interface 'lan' to reference eth0 instead of eth1 and then assign an ip address. Both correctly assign an address to eth0 after boot but neither work until removing eth0 from the wan bridge and re-adding it.
If you simply remove eth0 from the modem wan bridge interface
brctl delif br-wan_bridge eth0
and then add it again
brctl addif br-wan_bridge eth0
it still doesn't work. But if you ping a local address in between adding and removing then it does - strange!
I wanted to do this so I could access the administrative interface on the modem from a single interface, for logging via the PPPOE router which has a masquerading rule configured to allow it. Although I can get the modem config to work from the command line, I haven't got it to survive a reboot.
Steve
-
Hi :) Sorry for the few updates lately, I've had a big case of flu these past few weeks and it's been really hard to concentrate. (boohoo) :(
I've fixed a few more things in lantiq_dsl.sh
The most annoying one was our dsl_cpe0_* pipe getting "locked up" when LuCI's status page ("lucistat") and "status" were running simultaneously.
This would cause the status page to stop working, and effectively stop us from grabbing data for graphs.
The simple fix to this was changing lucistat to use its own pipe, it now uses /tmp/pipe/dsl_cpe1_* where as all the rest use /tmp/pipe/dsl_cpe0_*
I also tinkered with LuCI's status page some more.
opkg feeds have been updated to only use packages compiled for the current firmware build so packages aren't accidentally broken. OpenWrt's trunk is updated all the time.
For those of you who already have the image and don't want to reflash for a few file changes, SSH into your modem and run this simple script.
wget http://vanquishsolutions.co.uk/openwrt/VG3503J/update.sh && chmod +x update.sh && ./update.sh
This will apply the new above and below changes and tell you what files have changed.
Graphing situation
I figured it would be pointless having graphs on the modem itself, since they will be gone after a reboot anyway. We don't really need the extra CPU usage either since LuCI takes care of that :lol:
I started looking into a few dedicated methods to store and generate graphs, but in the end I went with Munin (http://munin-monitoring.org/) since it has already been done before (http://forum.kitz.co.uk/index.php?topic=11818.400;wap2).
I did make a few modifications, however.
I've added muninlite to the image with a munin-node script to grab stats from a cronjob-induced text file which is saved to /tmp every five minutes.
This will be used by Munin Master to generate graphs.
If you're not familiar with munin or if you're on Auld Wullies OS, or just want something dedicated for Munin to run on then I've created a VirtualBox disk which runs out of the box with Munin Master setup for you to play about with.
By default the networking on this is set to a static IP of 192.168.1.3, so once it's setup you can access your graphs at http://192.168.1.3/
Windows
1. Download VirtualBox for Windows (5.0.3) (https://www.virtualbox.org/download/testcase/VirtualBox-5.0.3-102322-Win.exe)
2. Grab MuninMaster.zip (370MB) (http://vanquishsolutions.co.uk/openwrt/VG3503J/MuninMaster.zip) - extract and place the "Munin Master" folder in "C:\Users\%USERNAME%\VirtualBox VMs"
3. Run VirtualBox and start the Munin Master VM
You might need to change some settings before you start the VM, such as the Network Adapter (see Network > Name)
If everything has went to plan, try it out at http://192.168.1.3/ - if not, check no other machines are using this IP or check your DHCP pool range on your router.
Tips:
You might prefer the VM to run in the background to minimize resource usage. Simply go to Command Prompt and run
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" startvm "Munin Master" --type headless
You can also use this to run the VM on startup.
There won't be any GUI since it's running in the background. If you need that, just start VirtualBox and click Show. You'll be greeted with a tty prompt as there isn't any desktop. The default user & password is: root root
SSH is available, but only from other devices in your internal network.
If you want to access SSH from anywhere else other than 192.168.1.* I recommend you first change the password by running "passwd root" and then proceed to edit /etc/hosts.deny
If you want to change the IP from 192.168.1.3, simply edit the eth0 int in /etc/networking/interfaces and reload (/etc/init.d/networking restart).
Here's a demo of Munin graphing my ECI /r (http://studio.boxlabs.uk/)
I've been quite pleased with this so far. Perhaps the graphs need some more tinkering with though to make them look pretty.
-
That's genius :D
I wonder if we could add MDWS support...
-
Bought a spare ECI and going to give this a try assuming I do not break it opening case or soldering (hoping the clothes peg trick will work however). Never done anything like this before so just getting some output via Putty whilst booting will be fun. Main stumpling block is MDWS support as you can guarantee a problem with my line when it is not recording stats.
-
Bought a spare ECI and going to give this a try assuming I do not break it opening case or soldering (hoping the clothes peg trick will work however).
Once you have removed the two screws, it is possible to gently persuade the lid to open by inserting a plastic implement at the long edge of the lid and levering. If you take a close look of the pictures that Ronski posted after had performed the drilling trick to get that initial /r modem open you should see where to lever and the two major clips at the short sides.
Unfortunately the "clothes peg trick" is not applicable to the B-FOCuS /r as the solder pads are in a totally different position to those of the B-FOCuS /I. :no:
-
wget http://vanquishsolutions.co.uk/openwrt/VG3503J/update.sh && chmod +x updates.sh && ./updates.sh
Small typo... change updates.sh to update.sh
Steve
-
ah, well spotted :)
-
If you can hold down the header pins, you don't actually need to do any soldering at all.
-
Any ideas on getting jsamuel's OpenWRT system to assign a working static IP address on eth0/LAN1? My last post on the subject looks a little garbled! :P
I can edit /etc/config/network and assign a static IP to 'lan' using eth0
config interface 'lan'
option ifname 'eth0'
option force_link '1'
option proto 'static'
option ipaddr '192.168.1.3'
option gateway 192.168.1.1
option netmask '255.255.255.0'
option ip6assign '60'
option dns '208.67.222.222 208.67.220.220'
and the IP address applies correctly following a reboot, but no IP traffic will flow across eth0.
If I remove eth0 from the bridge using the consolebrctl delif br-wan_bridge eth0I can then ping successfully and access the Luci web interface via eth0/LAN1.
Having done so I can then add eth0 back to the bridge brctl addif br-wan_bridge eth0 and it still all works correctly!
If I assign a static address to the wan bridge interface 'wan_bridge'
config interface 'wan_bridge'
option 'type' 'bridge'
option 'proto' 'static'
option 'ifname' 'eth0 ptm0.101'
option 'auto' '1'
option ipaddr '192.168.1.3'
option gateway 192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'
option dns '208.67.222.222 208.67.220.220'
then the assignment succeeds and the modem is immediately accessible via eth0 after booting. But I don't know which interface will be assigned the wan IP address when PPPoE starts up. Is it wan_bridge or ptm0.101? If anyone has their ECI configured and working in this fashion could could they report back the results of 'ifconfig'? I'd rather not disconnect my HG612 for a while.
If I can get it working I'll check the resultant inbound security from the Internet.
Steve
-
I'm not entirely sure what you want to do? :'( sorry.
can you paste your whole config?
-
Your default OpenWRT config has the PPPoE connection to the router on LAN1/eth0, and administration access on LAN2/eth1/192.168.1.1 thus requiring a second Ethernet connection. I have masquerade rules configured on my router that would allow access from my LAN through the router via the same interface as used for PPPoE.
I've had this working successfully on the original (well slightly modified) ECI firmware.
However for the purpose of testing admin connectivity, I've simply connected the modem LAN1 connection to my house LAN without the VDSL cable attached. The attached files are two of the various /etc/config/network configurations I've been trying.
'lan1.txt' results in an IP address assigned to eth0, but eth0 IP traffic doesn't flow until eth0 is removed from the wan bridge using the console cli. This is as I described before. Your config suggestion in post #76 results in exactly the same behaviour both regarding ip assignment and no-worky.
'lan2.txt' assigns an address to the wan bridge device instead, and does allow immediate admin access via eth0 following reboot, but I didn't want to interfere with any PPPoE daemon wan IP address assignment.
Oops - just realised that the PPPoE endpoint is on the router so shouldn't be an issue with WAN IP allocation.
The console cli is simply a serial port connection. I hope that's clearer?
Steve
-
I've been wondering how to implement currytop's setup too and thus far have been unable to do so :(
-
Ah. I see what you mean now.
Can you try this?
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fd88:f59f:8b1e::/48'
config interface 'wan'
option ifname 'eth0'
option force_link '1'
option proto 'static'
option ipaddr '192.168.1.1'
option gateway 192.168.1.2
option netmask '255.255.255.0'
option ip6assign '60'
option dns '208.67.222.222 208.67.220.220'
config interface 'wan_bridge'
option 'type' 'bridge'
option 'proto' 'none'
option 'ifname' 'eth0 ptm0.101'
option 'auto' '1'
config interface 'lan'
option ifname 'eth1'
option force_link '1'
config vdsl 'dsl'
option annex 'a'
option firmware '/lib/firmware/vdsl.bin'
option tone 'av'
option xfer_mode 'ptm'
Also check your /etc/config/firewall
config zone
option name lan
list network 'lan'
option input ACCEPT
option output ACCEPT
option forward ACCEPT
config zone
option name wan
list network 'wan'
list network 'wan6'
option input ACCEPT
option output ACCEPT
option forward ACCEPT
option masq 1
option mtu_fix 1
config forwarding
option src lan
option dest wan
-
I've been wondering how to implement currytop's setup too and thus far have been unable to do so :(
Try a version of the above attached lan2.txt to suit your network and it might work. I think I gave some example masquerade rules for a typical router a few months ago. To prove the point you could try it on a ECI already synced but move the ethernet cable coming from LAN1 onto your house LAN. That will test without needing masquerade rules. You'll lose Internet connectivity but not disturb the DLM/sync.
On the ECI either via serial or telnet/ssh on LAN2:-
ifconfig eth0 192.168.1.3
brctl delif br-wan_bridge eth0
and then from a machine on your LAN
ping 192.168.1.3
Adjust addresses to suit your LAN.
Restore the wan bridge:-
brctl addif br-wan_bridge eth0
and I think it should still work.
Either reboot the ECI to restore normal functionality or I can give cli commands to do it.
Make sure you don't have overlapping addresses on LAN1/LAN2. I simply temporarily disabled LAN2 for testing by setting eth1 to 0.0.0.0
Steve
-
Posts crossed!
jsamuel - your last suggestion is the same as you mentioned in post #76 and I've already tried it. The ip address gets correctly assigned to eth0, but no ip traffic will flow through it.
Simply removing eth0 from the wan_bridge using the cli gets things working using the already assigned address. Restore eth0 to the wan_bridge and it still works as needed. That's why I haven't looked at the firewall since things work after doing this.
It's as if eth0 needs to have an address assigned before adding to the bridge in order to get routing via eth0.
lan2.txt shows an address assigned directly to the bridge interface and that does work, although I haven't tried it on a live system with a functioning VDSL connection.
Steve
-
My apologies.
There's no wan_bridge in the firewall, which is probably why it works that way too. although it does seem strange it would work given it's bridged to the PTM vlan. :o
Both eth1/eth0 have different drivers, so you may experience put through issues if you're switching eth* around.
eth0 uses phy11
eth1 uses phy13
-
There's no wan_bridge in the firewall, which is probably why it works that way too. although it does seem strange it would work given it's bridged to the PTM vlan. :o
Thanks for looking. :)
Both eth1/eth0 have different drivers, so you may experience put through issues if you're switching eth* around.
eth0 uses phy11
eth1 uses phy13
OK - although not a problem in this case since eth1 won't be used. Only tiny issue is that eth0 carries both PPPoE traffic and administration/monitoring traffic, but unless you're trying to max out a 100Mbs line I can't see it mattering.
I feel that my lan2.txt experiment might well work as I want, since I had completely forgotten the PPPoE link is terminated within the router. i.e. the WAN address is assigned to the router ethernet interface. I'll try it when I get time - not for a while though.
Steve
-
I get an out of memory error trying to run the update script -
Signature check passed.
Installing muninlite (1.0.4-6) to root...
Downloading http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/packages/muninlite_1.0.4-6_lantiq.ipk.
Collected errors:
* xsystem: wget: vfork: Out of memory.
* opkg_download: Failed to download http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/packages/muninlite_1.0.4-6_lantiq.ipk, wget returned -1.
* opkg_install_pkg: Failed to download muninlite. Perhaps you need to run 'opkg update'?
* opkg_install_cmd: Cannot install package muninlite.
Connecting to vanquishsolutions.co.uk (104.28.28.73:80)
munin-node 100% |***************************************************| 28549 0:00:00 ETA
muninlite: Updated /usr/sbin/munin-node
root@OpenWrt:~#
root@OpenWrt:~# opkg update
Downloading http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/base/Packages.gz.
Downloading http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/base/Packages.sig.
Signature check failed.
Remove wrong Signature file.
Downloading http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/luci/Packages.gz.
Downloading http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/luci/Packages.sig.
Signature check failed.
Remove wrong Signature file.
Downloading http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/management/Packages.gz.
Downloading http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/management/Packages.sig.
Signature check failed.
Remove wrong Signature file.
Downloading http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/packages/Packages.gz.
Downloading http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/packages/Packages.sig.
Signature check failed.
Remove wrong Signature file.
Downloading http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/routing/Packages.gz.
Downloading http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/routing/Packages.sig.
Signature check failed.
Remove wrong Signature file.
Downloading http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/telephony/Packages.gz.
Downloading http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/telephony/Packages.sig.
Signature check failed.
Remove wrong Signature file.
Collected errors:
* xsystem: wget: vfork: Out of memory.
* opkg_download: Failed to download http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/base/Packages.gz, wget returned -1.
* xsystem: wget: vfork: Out of memory.
* opkg_download: Failed to download http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/base/Packages.sig, wget returned -1.
* xsystem: wget: vfork: Out of memory.
* opkg_download: Failed to download http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/luci/Packages.gz, wget returned -1.
* xsystem: wget: vfork: Out of memory.
* opkg_download: Failed to download http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/luci/Packages.sig, wget returned -1.
* xsystem: wget: vfork: Out of memory.
* opkg_download: Failed to download http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/management/Packages.gz, wget returned -1.
* xsystem: wget: vfork: Out of memory.
* opkg_download: Failed to download http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/management/Packages.sig, wget returned -1.
* xsystem: wget: vfork: Out of memory.
* opkg_download: Failed to download http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/packages/Packages.gz, wget returned -1.
* xsystem: wget: vfork: Out of memory.
* opkg_download: Failed to download http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/packages/Packages.sig, wget returned -1.
* xsystem: wget: vfork: Out of memory.
* opkg_download: Failed to download http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/routing/Packages.gz, wget returned -1.
* xsystem: wget: vfork: Out of memory.
* opkg_download: Failed to download http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/routing/Packages.sig, wget returned -1.
* xsystem: wget: vfork: Out of memory.
* opkg_download: Failed to download http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/telephony/Packages.gz, wget returned -1.
* xsystem: wget: vfork: Out of memory.
* opkg_download: Failed to download http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/telephony/Packages.sig, wget returned -1.
root@OpenWrt:~#
-
I get an out of memory error trying to run the update script -
Just a thought - I think there is a memory leak which gradually eats up available memory, maybe in the Luci web server which reports gradually reducing available memory on the status page. In my case it may well be because no VDSL line is attached so there are repeated errors reported. I haven't investigated it.
A reboot would fix it temporarily.
Steve
-
I have oddly seen this before too. Simply rerunning the script (opkg update) will sort it.
currytop that is the case, when there's no VDSL connected it will notify you every second until it is, probably eating memory in the process.
[283543.300000] /home/dev/firmware/openwrt/build_dir/target-mips_34kc+dsp_musl-1.1.10/linux-lantiq_xrx200/ltq-ptm-vr9/ifxmips_ptm_vdsl.c:281:ptm_hard_start_xmit: not in showtime
[283543.316000] /home/dev/firmware/openwrt/build_dir/target-mips_34kc+dsp_musl-1.1.10/linux-lantiq_xrx200/ltq-ptm-vr9/ifxmips_ptm_vdsl.c:281:ptm_hard_start_xmit: not in showtime
[283543.460000] enter showtime
[283543.468000] enter showtime
There's some issues with LuCI that I know of such as Lua hogging CPU on the status page, but I've yet to come across memory issues except with those for opkg.
-
To double check phi2008 can you show me the status of
free
and also
df
:)
-
root@OpenWrt:~# free
total used free shared buffers
Mem: 27456 21844 5612 568 1628
-/+ buffers: 20216 7240
Swap: 0 0 0
root@OpenWrt:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 1344 272 1072 20% /
/dev/root 3072 3072 0 100% /rom
tmpfs 13728 568 13160 4% /tmp
/dev/mtdblock3 1344 272 1072 20% /overlay
overlayfs:/overlay 1344 272 1072 20% /
tmpfs 512 0 512 0% /dev
root@OpenWrt:~#
-
Indeed strange, You have plenty of memory and spare space in /overlay so this looks like it's the work of opkg's bugs as above :no:
Have you tried rerunning the script? or same outcome?
As this is built on OpenWrt's Bleeding Edge there may be some bugs but it's stable enough for most uses. I'll test another build and see if this goes away.
-
Tried re-running again, gives out of memory error -
root@OpenWrt:~# wget http://vanquishsolutions.co.uk/openwrt/VG3503J/update.sh && chmod +x update.sh
&& ./update.sh
Connecting to vanquishsolutions.co.uk (104.28.29.73:80)
update.sh 100% |***************************************************| 1058 0:00:00 ETA
Connecting to vanquishsolutions.co.uk (104.28.28.73:80)
index.htm 100% |***************************************************| 18626 0:00:00 ETA
LuCI Status: Updated /usr/lib/lua/luci/view/admin_status/index.htm
Connecting to vanquishsolutions.co.uk (104.28.29.73:80)
root 100% |***************************************************| 59 0:00:00 ETA
Crontab: Added /etc/crontabs/root
Connecting to vanquishsolutions.co.uk (104.28.28.73:80)
dsl_control 100% |***************************************************| 1744 0:00:00 ETA
dsl_control: Updated /etc/init.d/dsl_control
Connecting to vanquishsolutions.co.uk (104.28.29.73:80)
lantiq_dsl.sh 100% |***************************************************| 18711 0:00:00 ETA
lantiq_dsl.sh: Updated /lib/functions/lantiq_dsl.sh
Connecting to vanquishsolutions.co.uk (104.28.28.73:80)
distfeeds.conf 100% |***************************************************| 645 0:00:00 ETA
opkg feeds: Updated /etc/opkg/distfeeds.conf
Downloading http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/base/Packages.gz.
Updated list of available packages in /var/opkg-lists/chaos_calmer_base.
Downloading http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/base/Packages.sig.
Signature check passed.
Downloading http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/luci/Packages.gz.
Updated list of available packages in /var/opkg-lists/chaos_calmer_luci.
Downloading http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/luci/Packages.sig.
Signature check passed.
Downloading http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/management/Packages.gz.
Updated list of available packages in /var/opkg-lists/chaos_calmer_management.
Downloading http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/management/Packages.sig.
Signature check passed.
Downloading http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/packages/Packages.gz.
Updated list of available packages in /var/opkg-lists/chaos_calmer_packages.
Downloading http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/packages/Packages.sig.
Signature check passed.
Downloading http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/routing/Packages.gz.
Updated list of available packages in /var/opkg-lists/chaos_calmer_routing.
Downloading http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/routing/Packages.sig.
Signature check passed.
Downloading http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/telephony/Packages.gz.
Updated list of available packages in /var/opkg-lists/chaos_calmer_telephony.
Downloading http://vanquishsolutions.co.uk/openwrt/VG3503J/packages/telephony/Packages.sig.
Signature check passed.
Collected errors:
* gz_open: fork: Out of memory.
* pkg_hash_add_from_file: Failed to open /var/opkg-lists/chaos_calmer_routing: Out of memory.
Connecting to vanquishsolutions.co.uk (104.28.29.73:80)
munin-node 100% |***************************************************| 28549 0:00:00 ETA
muninlite: Updated /usr/sbin/munin-node
root@OpenWrt:~#
EDIT:
OK a reboot seems to have resulted in a successful script execution, I was just avoiding rebooting the modem until I really had to.
-
Do you perhaps have LuCI open atall? Try closing it and try 'opkg update;opkg install muninlite' again when closed, or rerun ./update.sh
LuCI does have some performance issues, One of OpenWrt's dev's has confirmed but yet to investigate.
-
The Netgear D7800 source code release contains some newer Lantiq sources:
drv_dsl_cpe_api_vrx-4.16.5.4.tar.gz
drv_mei_cpe-1.4.9.7.tar.gz
dsl_cpe_control_vrx-4.16.5.4.tar.gz
The D7800 is VR10 / VRX320, but it looks like those Lantiq sources can be built for different devices. The changelog entries didn't sound particularly important, they are mostly to support the newer chip.
-
Thank you ejs
I'll have a dig into it, I wonder where OEMs get the sources from. perhaps Lantiq give them updates directly?
-
Does anyone know how the interaction with tftp should work. I need to run tftp on windows but what command initiates the update or does the ctrl-c bit do the update and then you type the commands listed? Thanks
-
Does anyone know how the interaction with tftp should work. I need to run tftp on windows but what command initiates the update or does the ctrl-c bit do the update and then you type the commands listed? Thanks
The ECI has a monitor program that runs on boot. It's default behaviour is to listen on the serial port for a few seconds for a Ctrl-C indicating a person is trying to interact with it. Upon receiving it, it enters an interactive session which supports a series of commands. The commands listed define tftp server addresses in the environment etc and then saves them for the future. If your TFTP server on Windows is setup correctly, the correct LAN port connected and the ECI binary image stored in the right folder then the transfer is initiated over Ethernet by typing run update_openwrt into the terminal program connected to the ECI serial port. That runs a command you setup earlier.
Hope that helps,
Steve
-
Does anyone have the set-up to use this with BT TV/YouView which requires multicast? I have a router that works fine with BT TV/multicast using a standard HG612 modem but ECI with OpenWRT appears to need some tweaking before it'll work. ???
-
It should work fine out of the box ???
-
Doesn't seem to work, tried a flash reset with no apparent effect - as I said the unlocked HG612 works OK. I've tried playing/faffing around with WRT and the best I can manage to do is sometimes get a garbled image on my BT/YouView box - my ethernet switch activity LEDs suggest multicast traffic is sometimes coming through the modem which gives cause for hope I suppose. My "OpenWRT-fu" is close to zero, and my knowledge of multicast IPTV is less than zero, so basically I don't have much of a clue. :-\
-
Hi all i am also now in this OpenWRT crew on the modem after spending nearly 3 hours trying to get a Serial connection on the board to which i ended up drilling the pads as direct heat or even a heated pin didn't melt the solder on the pads.
Now i have a question with the OpenWRT image stock settings can one fire up a PPPOE connection via a direct connection on the PC/Laptop like a normal BT VDSL router (For ASDL) with just making a new connection and dial via the PC/Laptop a PPPOE connection.
If not how does one make the modem act like the normal BT Firmware on OpenWRT.
Also whats the best way to connect via a the DSL-AC68U and its WAN port with the LAN2 port connected.
Whats the best Monitoring software as well for an OpenWRT'd ECI modem. Thanks in advance.
-
phi2008
I'm sorry :( I don't have a clue how those YouView boxes work, perhaps someone else can chime in?
I found this: http://wiki.openwrt.org/doc/howto/udp_multicast
hacktrix2006
I recommend setting up the modem to handle the PPP connection and not the PC.
Requires a change in /etc/config/network
http://forum.kitz.co.uk/index.php?topic=15918.60
-
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi.imgur.com%2F7F4deKr.png&hash=4db87a25e6386ed61b34b33194cd9b73c662c96f)
Original image courtesy of Zen
-
@jsamuel
Thank you for the Image and Settings will sort the change out, All i have to do next is find my WAN port on the ASUS DSL-AC68U this should be fun!!
OpenWRT is great as well. Just one question is CoDel now default in OpenWRT for Bufferbloat?
-
Yes CoDel has been in OpenWrt since Barrier Breaker. Just install:
luci-app-sqm sqm-scripts
and have a flick through http://wiki.openwrt.org/doc/howto/sqm
-
@jsamuel - btw, thanks for that link, very useful reading.
-
Hey there, anyone know how I can get back in to u boot after installing openwrt (I installed one of the v2 squahfs.image from http://downloads.openwrt.org/chaos_calmer/15.05/lantiq/xrx200/) as I am no longer getting the prompt to interrupt the boot up, have tried mashing ctrl + c whilst I power on the eci as well as many other keys but nothing stops the boot.
I cant seem to change the firmware from within openwrt either from the gui it gives an error about
'the uploaded image file does not contain a supported format. Make sure you choose the generic image format for your platform'
Have tried with jsmauels build and the original/modified eci ones from the focus r thread on here but nothing will flash.
I cant get it to connect via tftp either to upload a firmware that way have tried both windows and linux.
Have uploaded firmware to /tmp using scp in linux on the eci but it wont flash using the commands mentioned on the openwrt wiki, do I need to specify erase and write values like the op mentions for flashing from uboot
'erase 0xb0020000 0xb073ffff\;tftp 0x81000000 openwrt-lantiq-xrx200-VG3503J_V2-squashfs.image\;cp.b 0x81000000 0xb0020000 \$(filesize)'
Anyone got any ideas?
Edit: I must have not set it to ping something on start up by the looks of it so can't get back in to U boot with out Jtag it seems.
Anyone have recommendation of a Jtag cable for the ECI
-
Doesn't seem to work, tried a flash reset with no apparent effect - as I said the unlocked HG612 works OK. I've tried playing/faffing around with WRT and the best I can manage to do is sometimes get a garbled image on my BT/YouView box - my ethernet switch activity LEDs suggest multicast traffic is sometimes coming through the modem which gives cause for hope I suppose. My "OpenWRT-fu" is close to zero, and my knowledge of multicast IPTV is less than zero, so basically I don't have much of a clue. :-\
Have you managed to work this one out? Plan to unlock and flash openwrt on my v2 /r modem but don't want to waste my time if multicast/iptv will not work? Require this myself too so may just give it a try and see whats what
Is there many settings in openwrt you may have missed? Most common is igmp or multicast settings on wan and lan port sections or occasionally in firewall settings on some routers
-
Doesn't seem to work, tried a flash reset with no apparent effect - as I said the unlocked HG612 works OK. I've tried playing/faffing around with WRT and the best I can manage to do is sometimes get a garbled image on my BT/YouView box - my ethernet switch activity LEDs suggest multicast traffic is sometimes coming through the modem which gives cause for hope I suppose. My "OpenWRT-fu" is close to zero, and my knowledge of multicast IPTV is less than zero, so basically I don't have much of a clue. :-\
Have you managed to work this one out? Plan to unlock and flash openwrt on my v2 /r modem but don't want to waste my time if multicast/iptv will not work? Require this myself too so may just give it a try and see whats what
Is there many settings in openwrt you may have missed? Most common is igmp or multicast settings on wan and lan port sections or occasionally in firewall settings on some routers
Looking into this myself now and its prob an easy solution but I'm not too good at this
Basically it works if you take away the router lan to modem port 2 (the cable used to access the modem on 192.168.1.1)
So it seems that adding in this extra cable is causing some sort of flooding and interrupting the stream
So I think there must only be a few options here
1. Maybe there is a way to setup the modem so that we can access it on 192.168.1.1 through the 1 cable from routers wan to lan port 1 on modem?
2. Maybe we need to block multicast traffic on the lan port of the router that's connected to the modem
3. Maybe we need to block multicast traffic on lan port 2 of the modem
Someone with more experience can help maybe?
-
Good job folks, just enabled my ECI V2 box, only minor issue is i lose 2Mbps on the DS compared to a stock ECI V2 item. May updated firmware might help
-
Looking into this myself now and its prob an easy solution but I'm not too good at this
Basically it works if you take away the router lan to modem port 2 (the cable used to access the modem on 192.168.1.1)
So it seems that adding in this extra cable is causing some sort of flooding and interrupting the stream
So I think there must only be a few options here
1. Maybe there is a way to setup the modem so that we can access it on 192.168.1.1 through the 1 cable from routers wan to lan port 1 on modem?
2. Maybe we need to block multicast traffic on the lan port of the router that's connected to the modem
3. Maybe we need to block multicast traffic on lan port 2 of the modem
Someone with more experience can help maybe?
Ah, progress, I noticed when I was shooting in the dark that multicast(as evidenced by switch LEDs) seemed to really slow the OpenWrt like molasses so I suspect your flooding suspicion may be on the right track - I may now spend some time investigating. I'd switched over to the HG612 for the time being simply because I'd already spent hours debugging multicast with various routers/modems that day and was worn out. ???
-
Can someone please paste the output of 'ifconfig' from the HG612?
Then I'll get a better picture of what's different between the two. ;D
telnet
sh
ifconfig
-
Can someone please paste the output of 'ifconfig' from the HG612?
Then I'll get a better picture of what's different between the two. ;D
19 Oct 2015 02:27:13
ifconfig
br0 Link encap:Ethernet HWaddr 88:53:D4:6F:D8:F2
inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:500506955 errors:0 dropped:0 overruns:0 frame:0
TX packets:500917487 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2196392648 (2.0 GiB) TX bytes:3246366396 (3.0 GiB)
br2 Link encap:Ethernet HWaddr 88:53:D4:6F:D8:F2
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:42 (42.0 B) TX bytes:0 (0.0 B)
eth0 Link encap:Ethernet HWaddr 88:53:D4:6F:D8:F2
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1086240733 errors:0 dropped:0 overruns:0 frame:0
TX packets:1051794897 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1377537456 (1.2 GiB) TX bytes:876867257 (836.2 MiB)
Interrupt:40 Base address:0x6a00
eth0.4 Link encap:Ethernet HWaddr 88:53:D4:6F:D8:F2
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:500507059 errors:0 dropped:0 overruns:0 frame:0
TX packets:500917484 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2615595017 (2.4 GiB) TX bytes:975010761 (929.8 MiB)
eth0.5 Link encap:Ethernet HWaddr 88:53:D4:6F:D8:F2
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:585733674 errors:0 dropped:0 overruns:0 frame:0
TX packets:550877413 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3056909735 (2.8 GiB) TX bytes:4196823792 (3.9 GiB)
imq0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16000 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:11000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
imq1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16000 Metric:1
RX packets:585733674 errors:0 dropped:0 overruns:0 frame:0
TX packets:585733674 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:11000
RX bytes:3056909735 (2.8 GiB) TX bytes:3056909735 (2.8 GiB)
imq2 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16000 Metric:1
RX packets:585733674 errors:0 dropped:0 overruns:0 frame:0
TX packets:585369504 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:11000
RX bytes:3056909735 (2.8 GiB) TX bytes:2884510096 (2.6 GiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:127 errors:0 dropped:0 overruns:0 frame:0
TX packets:127 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:12426 (12.1 KiB) TX bytes:12426 (12.1 KiB)
pktcmf_sa Link encap:UNSPEC HWaddr FE-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00
UP NOTRAILERS RUNNING NOARP MTU:0 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:50 Base address:0x5220
pktcmf_sw Link encap:UNSPEC HWaddr FE-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00
UP NOTRAILERS RUNNING NOARP MTU:0 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:42 Base address:0x6a40
ptm1 Link encap:Ethernet HWaddr 88:53:D4:6F:D8:F3
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:555974652 errors:0 dropped:0 overruns:0 frame:0
TX packets:585369503 errors:0 dropped:1 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4294967295 (3.9 GiB) TX bytes:2861617242 (2.6 GiB)
ptm1.101 Link encap:Ethernet HWaddr 88:53:D4:6F:D8:F3
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:550877413 errors:0 dropped:0 overruns:0 frame:0
TX packets:585733674 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:777944442 (741.9 MiB) TX bytes:3056909735 (2.8 GiB)
#
-
how odd, I'm afraid I can't even test anything. I did come across this post on openwrt's forum, perhaps this will help.
Because the IPTV traffic isn't sent across your ISP's PPPoE connection (it's injected from the fibre cabinet) you need to add an IP address to your WAN port underneath the PPP connection.
Edit /etc/config/network and add a new interface:
config interface 'iptv'
option ifname 'eth0'
option proto 'static'
option ipaddr '10.22.22.1'
option netmask '255.255.255.0'
While you're editing /etc/config/network enable IGMP Snooping for your "lan" interface:
config interface 'lan'
...
option igmp_snooping '1'
Install the igmpproxy package and edit /etc/config/igmpproxy:
config igmpproxy
option quickleave 1
config phyint
option network iptv
option direction upstream
list altnet 109.159.247.0/24
config phyint
option network lan
option direction downstream
Edit /etc/config/firewall and add the new "iptv" interface to your existing "wan" zone:
config zone
option name 'wan'
...
option network 'wan wan6 iptv'
Also add new firewall rules to the end of /etc/config/firewall to allow the multicast traffic:
config rule
option src 'wan'
option proto 'igmp'
option target 'ACCEPT'
option name 'IGMP (IPTV)'
option enabled '1'
config rule
option src 'wan'
option proto 'udp'
option dest 'lan'
option dest_ip '224.0.0.0/4'
option target 'ACCEPT'
option family 'ipv4'
option name 'Multicast'
option enabled '1'
Run:
/etc/init.d/network restart
/etc/init.d/igmpproxy start
/etc/init.d/igmpproxy enable
Try opening a network stream to rtp://234.81.130.4:5802 in VLC or using your Youview box.
ps. opkg install igmpproxy since it's not installed by default on my build. If you can get this working, I'll update the default configuration so we shouldn't have anymore issues with multicasting.
-
Great work @jsamuel, everything seems much more stable than when I was using it on Barrier Breaker - have reflashed both of my ECI modems with your firmware - pleased to see the Munin hacky script I posted previously came of some use, would be good to get line uptime and interleaving level graphs as well.
To those who report slower speeds using this, my general experience with the stock ECI on ECI DSLAM (and when using OpenWRT on ECI, the same occurred/occurs for me) was that the sync speed is less than the HG612, but it potentially gave the ability to restore fast path as opposed to interleaving. After 10 days or so previously when running OpenWRT Barrier Breaker on the ECI mode it did restore fast path for me.
For me, the best all out sync speed was when using the Zen supplied TG589 (can use it in bridge mode), HG612 second and ECI slowest. But, when using the TG589/HG612 I can leave it on my ECI DSLAM line(s) and never gets fast path restored, even after 2-3 months of continuous sync time - well past the supposed 64 day maximum DLM caution counter, likely due to the increased errors that are reported/seen when using a non-ECI modem on an ECI DSLAM.
Thanks again,
-
Looks like the interleaving code is still there, just perhaps a typo in the changes you made. Change "dsl" to "xdsl" to fit with your changes, in /usr/sbin/munin-node:
fetch_dsl_int_dep() {
echo "dsl_dw_int_dep.value" $(grep ^"Interleave Depth" /tmp/dsl.txt |cut -d: -f2|cut -d\ -f1)
echo "dsl_up_int_dep.value" $(grep ^"Interleave Depth" /tmp/dsl.txt |cut -d: -f2|cut -d\ -f3)
}
config_dsl_int_dep() {
echo 'graph_title Interleave Depth'
echo 'graph_args --base 1000'
echo 'graph_vlabel Interleave Depth'
echo "graph_category network"
echo 'graph_scale no'
echo 'dsl_dw_int_dep.label Downstream'
echo 'dsl_dw_int_dep.draw LINE'
echo 'dsl_up_int_dep.label Upstream'
echo 'dsl_up_int_dep.draw LINE'
}
Change to:
fetch_xdsl_int_dep() {
echo "dsl_dw_int_dep.value" $(grep ^"Interleave Depth" /tmp/dsl.txt |cut -d: -f2|cut -d\ -f1)
echo "dsl_up_int_dep.value" $(grep ^"Interleave Depth" /tmp/dsl.txt |cut -d: -f2|cut -d\ -f3)
}
config_xdsl_int_dep() {
echo 'graph_title Interleave Depth'
echo 'graph_args --base 1000'
echo 'graph_vlabel Interleave Depth'
echo "graph_category network"
echo 'graph_scale no'
echo 'dsl_dw_int_dep.label Downstream'
echo 'dsl_dw_int_dep.draw LINE'
echo 'dsl_up_int_dep.label Upstream'
echo 'dsl_up_int_dep.draw LINE'
}
Then add to the plugins line:
PLUGINS="cpu if_ if_err_ load memory processes netstat uptime irqstats xdsl_speeds xdsl_errors xdsl_line_att xdsl_noise xdsl_tran_pwr xdsl_int_dep"
-
Looks like the below change to the lantiq_dsl.sh script enables line uptime in seconds, making it much easier to graph this - will put something together:
https://dev.openwrt.org/browser/trunk/target/linux/lantiq/base-files/lib/functions/lantiq_dsl.sh?rev=46917
UPDATE:
1. Modify /lib/functions/lantiq_dsl.sh (line_uptime) inline with the changes in the recent update to include uptime in seconds:
https://dev.openwrt.org/browser/trunk/target/linux/lantiq/base-files/lib/functions/lantiq_dsl.sh
2. Add xdsl_line_up to the PLUGINS line in /usr/sbin/munin-node
3. Add the below to munin-node in the PLUGINS section:
config_xdsl_line_up() {
echo "graph_title Line Uptime"
echo "graph_args --base 1000 -l 0 "
echo "graph_vlabel uptime in days"
echo "xdsl_line_up.label uptime"
echo "xdsl_line_up.draw AREA"
}
fetch_xdsl_line_up() {
echo "xdsl_line_up.value" $(grep ^"Line Uptime Seconds" /tmp/dsl.txt|cut -d: -f2| awk '{print $1/86400}')
}
-
One thing I have noticed, is that despite PPP being version 2.4.7 (higher than the required 2.4.6) RFC4638 doesn't seem to work - this seems to be more down to the NIC/interface drivers not supporting it, MTU of 1500 is the max they understand you cannot set 1508 on any interface.
root@OpenWrt:~# ifconfig eth1 mtu 1508
ifconfig: SIOCSIFMTU: Invalid argument
root@OpenWrt:~# ifconfig eth1 mtu 1500
root@OpenWrt:~#
-
Hi jsamuel,
I've just bought one of these units on eBay ;), and would like to be able to tinker with the builds.
I can see you've got a .config file on http://vanquishsolutions.co.uk/openwrt/VG3503J/config (http://vanquishsolutions.co.uk/openwrt/VG3503J/config), but I'd like to white-box it a little. That is, rather than use make menuconfig to create the .config file, I do something similar to the following BASH script:
### Create the .CONFIG file (this WILL survive a make clean)
VER=trunk; cd ~/openwrt/${VER}/
cat << 'EOF' > .config
CONFIG_TARGET_lantiq=y
CONFIG_TARGET_lantiq_xrx200=y
CONFIG_TARGET_lantiq_xrx200_VG3503J=y
...
EOF
### Finally, populate the config file...
make defconfig
Could you help an old man out? This unit hasn't arrived yet, but I am already playing with a build!
-
Nice work iMX - not sure how I missed that typo. :D
zxdavb I'm not quite sure what you mean to do? My apologies. :(
The .config there is one I made specifically for these images using menuconfig - I tried to keep it at a minimum, with the exception of the following packages: luci, muninlite & nano
-
By using a script rather than the user interface to create the config file, we have something that is much easier to deal with, change control being one such example.
For example, to add luci, nano & muninlite:
## Create the .config file...
VER=trunk; cd ~/openwrt/${VER}/
cat << 'EOF' > .config
CONFIG_TARGET_lantiq=y
CONFIG_TARGET_lantiq_xrx200=y
CONFIG_TARGET_lantiq_xrx200_VG3503J=y
CONFIG_PACKAGE_luci=y
CONFIG_PACKAGE_nano=y
CONFIG_PACKAGE_muninlite=y
EOF
### Then, populate the config file...
make defconfig
### Finally...
make -j 5
After creating the .config file, you then do a make defconfig, and all the other crap you see in your .config file (which is currently 6 lines long) get automatically put in (and becomes 100's of lines). Try it! The end result is the same as doing it via make menuconfig.
For me, it would help to understand the actual difference between your build and other builds I use.
I am not familar with muninlite, but it is a standard package. To see what I mean, start make menuconfig and type the slash key, and type 'munin' and hit enter. It should show you something like PACKAGE_muninlite which becomes CONFIG_PACKAGE_muninlite.
I notice you have modulised (i.e. <M> via the UI, or =m via my method) a whole bunch of packages. Why? I suggest (to keep it simple) you only do it for the ones you need. Or you can use https://downloads.openwrt.org/snapshots/trunk/lantiq/xrx200/packages/ (https://downloads.openwrt.org/snapshots/trunk/lantiq/xrx200/packages/)?
-
I guess other packages I'd defo be looking at installing are: dnsmasq, ddns-scripts, and sqm-scripts.
Optional packages might include: OpenSSH.
And then it's just a matter of seeing what the hardware will manage.
-
Hi guys
I have a v1.1, flashed the image, it went well but now the modem boots up with green/red flashing power light, then finally ends with power and DSL light permanently lit (the modem isn't connected to an active line!). I cannot ping/access 192.168.1.1 via LAN2. Serial access appears to work still.
Any advice appreciated.
-
I thought I'd reflash the modem which I was able to do, but still no joy. The final output from serial is below
[ 90.232000] DSL[00]: Reboot on training timeout (60)!!!
[ 156.424000] DSL[00]: Reboot on training timeout (60)!!!
[ 184.288000] /home/dev/firmware/openwrt/build_dir/target-mips_34kc+dsp_musl-1.1.10/linux-lantiq_xrx200/ltq-ptm-vr9/ifxmips_ptm_vdsl.c:281:ptm_hard_start_xmit: not in showtime
[ 184.300000] /home/dev/firmware/openwrt/build_dir/target-mips_34kc+dsp_musl-1.1.10/linux-lantiq_xrx200/ltq-ptm-vr9/ifxmips_ptm_vdsl.c:281:ptm_hard_start_xmit: not in showtime
[ 221.716000] DSL[00]: Reboot on training timeout (60)!!!
I've also attached a complete log file to this post
-
Hello all
my first post on this forum.
from the first post in this thread:
Don't put the image for the v2 on a v1 otherwise your ethernet ports won't work effectively leaving you with a bricked unit.
Maybe try flashing it with v2 firmware? it's safe as long as bootloader is fine.
-
But if the LAN gets screwed how would I change to another firmware after that? I cba with a JTAG, and my chipset definitely says v1.1
-
http://forum.kitz.co.uk/index.php/topic,15918.msg296860.html#msg296860
ethernet port will still work in bootloader.
-
Okay, so I flashed image V2 to my v1.1 and ethernet port now works! Thanks, and very odd eh?
DSL light is still permanently on even though it's not connected to an active line, is this normal?
-
yup
I've just checked on my spare modem. power and dsl on, lan1,lan2 off
-
Yes, the DSL light always on is "normal" operation (by normal, that's the way I left it) :lol:
Some GPIO-led tweaking is needed to fix it, but it never did bother me that much to warrant a fix.
It's odd that the v2 image will work on the v1.1, are you sure it's not a v2.1 SoC? :)
-
The little chip says v1.1, shame I didn't take a picture as I've put the modem back together now and it was a nightmare getting it apart!
I wonder how difficult it would be to get the DSL light working correctly? I plan on using this modem at work and a working LED would be good for diagnosis from others when I'm not there (my manager wouldn't be able to handle web based management ;-) )
-
Oh also, am I right when I say I'll be able to replace our HG612 (connected to an Huwaei cab) with this unlocked ECI and I'll retain G.INP?
-
I never investigated it to be honest, since it's always usually connected, but it requires a change in the profile and a firmware recompile if I recall correctly. it's why I just left it :'(
Yes, G.INP will work. :fingers:
-
Nice.
Thank you rp00 and jsamuel, you've both been very helpful :)
-
I just had to check the modem again, and the chip does say v1.2 ... I was looking at the smaller chip beside it originally :-[ Woops!
-
Is there any way to get everything down the same lan port ( viewable through DD-WRT router), just like the stock ECI modems, or, the HG612 or any other good bit of hardware containing a vdsl modem. my router and modem are separated by a long ethernet cable. Without sticking a network switch on both ports of the modem?
-
You could always use a pair of Cat 5 splitters, for example http://www.ebay.co.uk/itm/2-x-Cat5e-Ethernet-Network-Splitter-Economiser-Adapters-CAT-5e-RJ45-/290335345691
The modems only have a 100mb port anyway so you wouldn't be losing anything
[edit] you'd need a pair of cat5 joiners also (if you're usin a straight through cat5 lead and not a patch panel) and 2 pairs of small rj45 leads, but you get the point
-
You could assign eth1 192.168.1.1 in /etc/config/network
I would've set it up like this by default, but WAN ports on most consumer routers (caused by dodgy firmware) don't support it.
-
Thanks Jsamuel. Should of known better, OpenWRT is nice and configurable.
-
should have known better
;D
Best wishes
-
What was the solution to the IPTV multicast "flooding"(?)/2nd network port issue?
-
Hi, has anyone been able to successfully configure the ECI/r running @jsamuel's OpenWRT build on Sky Fibre? I've tried unsuccessfully using a variety of info, such as following the setup of HG612 via separate OpenWRT sending Option 60/61 data (having extracted my SR102 User ID and password), but can't get it working (I can see in the logs it just does "Sending Discover" 3 times, but it never gets a connection established). If anyone has been able to do this I'd appreciate a few screen grabs of the setup, or pointers of how to configure.
-
Hi Jordan
Just saying hello and look forward to getting my eci modem back when you have completed the install of openwrt.
Russ - I am on sky fibre along with ECI cabinet so worth maybe sending Jsamuel a PM as he mentioned its needs some specific settings to make it work ???
Cheers
Hi, has anyone been able to successfully configure the ECI/r running @jsamuel's OpenWRT build on Sky Fibre? I've tried unsuccessfully using a variety of info, such as following the setup of HG612 via separate OpenWRT sending Option 60/61 data (having extracted my SR102 User ID and password), but can't get it working (I can see in the logs it just does "Sending Discover" 3 times, but it never gets a connection established). If anyone has been able to do this I'd appreciate a few screen grabs of the setup, or pointers of how to configure.
-
One thing I have noticed, is that despite PPP being version 2.4.7 (higher than the required 2.4.6) RFC4638 doesn't seem to work - this seems to be more down to the NIC/interface drivers not supporting it, MTU of 1500 is the max they understand you cannot set 1508 on any interface.
root@OpenWrt:~# ifconfig eth1 mtu 1508
ifconfig: SIOCSIFMTU: Invalid argument
root@OpenWrt:~# ifconfig eth1 mtu 1500
root@OpenWrt:~#
Good to know, as presumably this also means it will not work in bridge mode with a router capable of a 1500 MTU either?
Although I still don't understand how the HG612 handles this as I currently have pfSense (with the RFC4638 patch) connected to a HG612 and that still claims all interfaces have a 1500 MTU, despite PPP working perfectly with a 1500 MTU.
-
Havin a crack at this on my v1.2 ECi but I can't get it to pull the file.
This is what my TFTP looks like:
LAN port lights aren't flashing but the LAN 1 light at the front of the board, next to the Power light is.
Any help would be greatly received.
Thanks,
Paul
-
First you need to open the case and connect to the serial port pins.
After that, your computer is the tftp server with the IP address of its Ethernet port set to 192.168.1.1. You could pick a different address if you change the commands you enter over the serial connection to the bootloader accordingly.
-
First you need to open the case and connect to the serial port pins.
After that, your computer is the tftp server with the IP address of its Ethernet port set to 192.168.1.1. You could pick a different address if you change the commands you enter over the serial connection to the bootloader accordingly.
Yes, modem is connected to the UART and all commands have been entered and saved on to the modem, exactly as they appeared in the guide on page 1.
It's the image transfer I'm having issues with, once I've executed the run update_openwrt command, Kitty just shows T T T T then times out and starts 'waiting' for the file again. It's as though it can't communicate with the Tftp tool.
The guide for the Tftp tool states, to use the Tftp client (as seen in image) I only need to enter the Host name and the file name (path seen in image) and click 'Put'.
So to avoid ambiguity:
1. Should I be using the Tftp client? Or should I use the Tftp server?
2. If it's the client, what should I enter in:
a. The Host field?
b. The Local file field?
3. Where should I save the image file on my PC? Does it matter?
4. If it's the Tftp server I should be using, what values do I need to put in which fields?
5. Do I need to manually set the IP address of the ethernet port on my laptop?
Thanks in advance,
Paul
-
Seems the issue is that I've knobbled the ethernet ports... So I now need to un-brick it somehow. ::)
Paul
-
My first post!
Thanks for all the work that's been done to crack this ECI.
VDSL isn't due in my area for some months, so I've been trying to make the ECI into a spare ADSL router that I can connect directly to a PC. However, I'm lost among the WANs LANs and BRIDGES of OpenWrt, and I can't connect PC browser -> Internet.
Status indicates that the ECI can see the ADSL line:
ECI_OpenWrt
Hostname
ECI_OpenWrt
Model
BT OpenReach VDSL Modem
Firmware Version
OpenWrt Chaos Calmer r46559 / LuCI Master (git-15.216.69575-bb7ea3e)
Kernel Version
3.18.19
Local Time
Sun Mar 6 20:18:55 2016
Uptime
0h 12m 43s
Load Average
1.79, 1.39, 0.80
xDSL Status
Retrieve more information
Line Mode: G.992.5 (ADSL2+) Annex A Profile unknown
Status & Uptime: UP 10m 45s Resyncs: 2
Line State: showtime_tc_sync [0x801]
Power Mode: L0 - Synchronized
Downstream Upstream
Attainable Line Speed: 11.420 Mb/s 1.116 Mb/s
Actual Line Speed: 11.477 Mb/s 1.020 Mb/s
Trellis: D: ON U: ON
Bitswap: D: ON U: OFF
G.INP: D: Not Enabled U: Not Enabled
Virtual Noise Support: D: Not Supported U: Not Supported
Interleave Depth: 64 1
Interleave Block: 255 146
Interleave Delay: 11.25 ms 1.25 ms
INP: 0.3 0.0
NFEC: 255 146
RFEC: 4 0
LSYMB: 2917 257
LPATH: 0 0
Line Attenuation: 29.9 dB / 12.2 dB
Noise Margin/SNR: 5.8 dB / 9.5 dB
Transmit Power: 11.7 dBm / 20.3 dBm
Errors Since Line Up
FECS: 1815 0
ES: 5 0
SES: 0 0
LOSS: 0 4
UAS: 61 61
HEC: 0 14
CRC_P: 0 0
CRCP_P: 0 0
Errors in 15 Minutes
Code Violations: 2 0
FECS: 349 0
Errors in 1 Day
Code Violations: 8 64
FECS: 1816 0
Total Available
Free
Buffered
Active Connections
IPv4 WAN Status
Not connected
IPv6 WAN Status
Not connected
Hostname
IPv4-Address
MAC-Address
Leasetime remaining
There are no active leases.
Hostname
IPv6-Address
DUID
Leasetime remaining
There are no active leases.
Powered by LuCI Master (git-15.216.69575-bb7ea3e) / OpenWrt Chaos Calmer r46559
But the System Log seems to say that it can't connect:
Sun Mar 6 20:08:42 2016 daemon.info pppd[3928]: Exit.
Sun Mar 6 20:08:42 2016 daemon.notice netifd: Interface 'wan' is now down
Sun Mar 6 20:08:42 2016 daemon.notice netifd: Interface 'wan' is setting up now
Sun Mar 6 20:08:43 2016 daemon.info pppd[3951]: Plugin pppoatm.so loaded.
Sun Mar 6 20:08:43 2016 daemon.info pppd[3951]: PPPoATM plugin_init
Sun Mar 6 20:08:43 2016 daemon.info pppd[3951]: PPPoATM setdevname_pppoatm - SUCCESS:0.0.38
Sun Mar 6 20:08:43 2016 daemon.notice pppd[3951]: pppd 2.4.7 started by root, uid 0
Sun Mar 6 20:08:43 2016 daemon.err pppd[3951]: connect(0.0.38): No such device
Sun Mar 6 20:08:43 2016 daemon.info pppd[3951]: Exit.
My Network parameters:
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fd88:f59f:8b1e::/48'
config interface 'wan'
option _orig_ifname 'eth0'
option _orig_bridge 'true'
option ifname 'eth0'
option proto 'pppoa'
option username '0123456789@talktalk.net'
option password '************'
option encaps 'vc'
option atmdev '0'
option vci '38'
option vpi '0'
option mtu '1432'
option ipv6 'auto'
config interface 'wan6'
option ifname '@wan'
option proto 'dhcpv6'
config interface 'lan'
option ifname 'eth1'
option type 'bridge'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'
I haven't dared trying to fiddle (!) with anything else. But I've attached an archive of all the config files in case the problem lies with them ...
-
...
config interface 'wan'
option _orig_ifname 'eth0'
option _orig_bridge 'true'
option ifname 'eth0'
option proto 'pppoa'
option username '0123456789@talktalk.net'
option password '************'
option encaps 'vc'
option atmdev '0'
option vci '38'
option vpi '0'
option mtu '1432'
option ipv6 'auto'
config interface 'wan6'
option ifname '@wan'
option proto 'dhcpv6'
config interface 'lan'
option ifname 'eth1'
option type 'bridge'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'[/color]
..
Try:
option payload 'bridged'
option encaps 'llc'
option vci '32'
option vpi '8'
-
config vdsl 'dsl'
option fwannex 'a'
option annex 'a2p'
option firmware '/lib/firmware/vdsl.bin'
is missing from your network config file.
(ignore the name of vdsl.bin - it's firmware for both adsl and vdsl)
-
Is the lantiq_dsl.sh script here (http://vanquishsolutions.co.uk/openwrt/VG3503J/files/lib/functions/) the current version?
I think the command to get the DSLAM vendor is wrong. "g997listrg 0" gets the near end vendor, so it will always say IFTN, because the Lantiq VRX268 identifies itself as IFTN. It should be "g997listrg 1" to get the far end vendor string.
-
Is the lantiq_dsl.sh script here (http://vanquishsolutions.co.uk/openwrt/VG3503J/files/lib/functions/) the current version?
I think the command to get the DSLAM vendor is wrong. "g997listrg 0" gets the near end vendor, so it will always say IFTN, because the Lantiq VRX268 identifies itself as IFTN. It should be "g997listrg 1" to get the far end vendor string.
In this case, both 1 and 0 displays the same SystemVendorID string which is always going to be the vendor at the cab. (correct me if I'm wrong)
-
That's because your cab is also IFTN, which happens to give the same ID as the ECI modem. Here's some saved output from my TP-Link TD-W8970, on ADSL2, my exchange vendor ID is TSTC:
~ # /firmware/dsl_cpe_pipe.sh g997listrg 0
nReturn=0 nDirection=0 G994VendorID=IFTNTD SystemVendorID=IFTN VersionNumber=0123456789012345 SerialNumber=01234567890123456789012345678901 SelfTestResult=0 XTSECapabilities=(05,00,04,00,4C,01,04,00)
~ # /firmware/dsl_cpe_pipe.sh g997listrg 1
nReturn=0 nDirection=1 G994VendorID=TSTC SystemVendorID=0000 VersionNumber= SerialNumber=00000000000000000000000000000000 SelfTestResult=0 XTSECapabilities=(00,00,04,00,0C,00,00,00)
-
I see, Thanks for letting me know. I've updated the files.
I'll apply it to the firmware squashfs images too when I update the Lantiq firmware.
-
I think ejs might be right.
dsl_cpe_pipe.sh g997listrg 0
nReturn=0 nDirection=0 G994VendorID=IFTNWC SystemVendorID=IFTN VersionNumber=0123456789012345 SerialNumber=01234567890123456789012345678901 SelfTestResult=0 XTSECapabilities=(00,00,00,00,00,00,00,07)
dsl_cpe_pipe.sh g997listrg 1
nReturn=0 nDirection=1 G994VendorID=IFTN SystemVendorID=ECI tele VersionNumber= SerialNumber=5502511454 SelfTestResult=0 XTSECapabilities=(00,00,00,00,00,00,00,00)
btw. if you guys didn't notice
G.INP: D: Enabled / U: Not Enabled
ECI modem on ECI cab :)
-
Nice!
Glad BT finally got round to enabling G.INP on ECI cabs.
..Now for upstream. ;D
-
rp00
From your information, g997listrg 1 is telling you ECI tele is your modem.
Now I'm confused. ???
Okay, I should be displaying the value of G994VendorID not SystemVendorID
-
Has anyone had any luck with YouView multicasting?
If so, do share and I'll add the changes to my next build. Unfortunately I'm unable to test it myself, I have a few theories. but if they'll work or not who knows. I don't want to add my changes to the build for them to turn out they don't work. :lol:
-
@jsamuel - you might want to wait for this change in the dsl_cpe_control configure script switches to be tested, to see if we can get it reporting more sensible values for NFEC, RFEC etc. with G.INP active:
Perhaps also add --with-channels-per-line=2 - the default value is 1, which may explain the issue with the framing parameter reporting.
Increasing the number of channels per line supported by the dsl_cpe_control program probably makes it use more memory.
-
@jsamuel - you might want to wait for this change in the dsl_cpe_control configure script switches to be tested, to see if we can get it reporting more sensible values for NFEC, RFEC etc. with G.INP active:
Perhaps also add --with-channels-per-line=2 - the default value is 1, which may explain the issue with the framing parameter reporting.
Increasing the number of channels per line supported by the dsl_cpe_control program probably makes it use more memory.
With this option enabled. my build fails with error: #error "DSL_CHANNELS_PER_LINE > 1 feature not released yet!!!"
-
/**
If number of used bearer channels is not set choose default value of '1'
*/
#ifndef DSL_CHANNELS_PER_LINE
#define DSL_CHANNELS_PER_LINE 1
#ifdef _MSC_VER
#pragma message("WARNING: DSL_CHANNELS_PER_LINE not specified, chossing default '1'")
#else
#warning "WARNING: DSL_CHANNELS_PER_LINE not specified, chossing default '1'"
#endif
#else
#if (DSL_CHANNELS_PER_LINE > 2)
#error "ERROR: DSL_CHANNELS_PER_LINE has to be in range of '0..1'"
#elif (DSL_CHANNELS_PER_LINE > 1)
#error "DSL_CHANNELS_PER_LINE > 1 feature not released yet!!!"
#endif
#endif
What a mess..
-
Yes, DSL_CHANNELS_PER_LINE is also in the driver, not just the control application. We'll have to wait for some newer versions from Lantiq.
-
Dumb question I'm sure, I've got OpenWRT running on my ECI/r v1, but for some reason it looks like outbound DNS queries are being blocked. I can ping internet hosts and also managed a telnet to a external server so it looks like routing is fine, as far as I can tell it's just DNS queries that are not working.
Tried server 8.8.8.8 etc, still no good. The moment I swap back to my original unhacked ECI/r everything works fine. Just seems to be an issue with OpenWRT.
Any help appreciated.
-
Which build are you using?
-
The v1 image linked in the first post of this thread
http://vanquishsolutions.co.uk/openwrt/openwrt-lantiq-xrx200-VG3503J-squashfs.image
-
I see. I wondered if you were using another build that wasn't mine as DNS works fine.
Would you mind showing us your /etc/config/network file?
-
Thanks for your assistance ;D
cat /etc/config/network
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fd88:f59f:8b1e::/48'
config interface 'wan'
option ifname 'eth0'
option force_link '1'
config interface 'wan_bridge'
option type 'bridge'
option proto 'none'
option ifname 'eth0 ptm0.101'
option auto '1'
config interface 'lan'
option ifname 'eth1'
option _orig_ifname 'eth1'
option _orig_bridge 'false'
option proto 'static'
option ipaddr '192.168.0.52'
option netmask '255.255.255.0'
option gateway '192.168.0.1'
option dns '8.8.8.8'
config vdsl 'dsl'
option annex 'a'
option firmware '/lib/firmware/vdsl.bin'
option tone 'av'
option xfer_mode 'ptm'
-
I see you've added these?
option _orig_ifname 'eth1'
option _orig_bridge 'false'
I believe this fixes our Multicast problem, thanks. :)
I'm not sure why DNS isn't working as expected though, have you changed any other files?
-
I believe this fixes our Multicast problem, thanks. :)
I'd love to claim credit but I didn't change very much from the original image, only the LAN IP address really.
I just wondered if there was any sort of smart DNS proxy that intercepted DNS requests and proxied them for some strange reason (e.g. like a DHCP relay). The only other thing that occurred to me is the firewall but that appears to be disabled.
-
@jsamuel
Does your OpenWRT build include the dsl_cpe_pipe.sh utility program? It might be useful for people who want to access particular stats from the command line, or it might be more reliable for stats monitoring. It's no longer actually a shell script (although it's still named dsl_cpe_pipe.sh some vendor firmwares). The source code is in the dsl_cpe_control source tarball, under the tools/pipe/ directory.
-
Hi, I'm trying to do this from a win7 machine and I think I have an issue with tftpd32. All is OK until I issue the run update_wrt command, the modem then does the erase and comes back with this:-
VR9 # tftpboot - boot k using TFTP protocol
tftpboot - boot image via network using TFTP protocol
Usage:
tftpboot [loadAddress] [[hostIPaddr:]bootfilename]
VR9 #
Can anyone help with the setup of tftpd32?
Thanks
-
Hi, I'm trying to do this from a win7 machine and I think I have an issue with tftpd32. All is OK until I issue the run update_wrt command, the modem then does the erase and comes back with this:-
VR9 # tftpboot - boot k using TFTP protocol
tftpboot - boot image via network using TFTP protocol
Usage:
tftpboot [loadAddress] [[hostIPaddr:]bootfilename]
VR9 #
Can anyone help with the setup of tftpd32?
Thanks
I don't think this is an issue with tftpd
It looks more like a typo somewhere.
show the output of "printenv"
-
Printenv below:-
VR9 # printenv
bootdelay=3
baudrate=115200
mem=31M
phym=32M
netdev=eth0
console=ttyS0
baudrate=115200
tftppath=
loadaddr=0x80800000
rootpath=/mnt/full_fs
rootfsmtd=/dev/mtdblock1
nfsargs= setenv bootargs root=/dev/nfs rw nfsroot=$(serverip):$(rootpath)
ramargs=setenv bootargs root=/dev/ram rw
addip=setenv bootargs $(bootargs) ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname):$(netdev):on
addmisc=setenv bootargs $(bootargs) console=$(console),$(baudrate) ethaddr=$(ethaddr) phym=$(phym) mem=$(mem) panic=1 mtdparts=$(mtdparts) init=/etc/preinit vpe1_load_addr=0x81f00000 vpe1_mem=1M ethwan=$(ethwan)
flash_nfs=run nfsargs addip addmisc;bootm $(kernel_addr)
net_nfs=tftp $(loadaddr) $(tftppath)$(bootfile);run nfsargs addip addmisc;bootm
net_flash=tftp $(loadaddr) $(tftppath)$(bootfile); run flashargs addip addmisc; bootm
net_ram=tftp $(loadaddr) $(tftppath)$(bootfile); run ramargs addip addmisc; bootm
u-boot=u-boot.ifx
releaseimg=releaseImg.bin
btagent=ap_jffs2.img
flashargs1=setenv bootargs root=/dev/mtdblock8 ro rootfstype=squashfs
flashargs2=setenv bootargs root=/dev/mtdblock9 ro rootfstype=squashfs
commit_img_1=setenv bootargs $(bootargs) commit_img=1 LD_LIBRARY_PATH=/btagent/lib
commit_img_2=setenv bootargs $(bootargs) commit_img=2 LD_LIBRARY_PATH=/btagent/lib
flash_flash_1=run flashargs1 addip addmisc commit_img_1; bootm $(f_pri_kernel_addr)
flash_flash_2=run flashargs2 addip addmisc commit_img_2; bootm $(f_sec_kernel_addr)
update_uboot_only=tftpboot $(loadaddr) $(u-boot);prot off 0xb0000000 0xb001ffff;erase 0xb0000000 0xb001ffff;upgrade uboot $(loadaddr) $(filesize) 0
update_uboot=tftpboot $(loadaddr) $(u-boot);prot off all;erase all;upgrade uboot $(loadaddr) $(filesize) 0
update_pri_img=tftpboot $(loadaddr) $(releaseimg);upgrade pri_img $(loadaddr) $(filesize) 0
update_sec_img=tftpboot $(loadaddr) $(releaseimg);upgrade sec_img $(loadaddr) $(filesize) 0
update_btagent=tftpboot $(loadaddr) $(btagent);upgrade btagent $(loadaddr) $(filesize) 0
boot_img_idx=0
reset_sys_config=prot off 0xB07E0000 0xB07EFFFF; erase 0xB07E0000 0xB07EFFFF
reset_bt_config=prot off 0xB07C0000 0xB07DFFFF; erase 0xB07C0000 0xB07DFFFF
reset_all_config=run reset_sys_config; run reset_bt_config
reset_uboot_config=prot off $(f_ubootconfig_addr) $(f_ubootconfig_end); erase $(f_ubootconfig_addr) $(f_ubootconfig_end)
reset_ddr_config=prot off $(f_ddrconfig_addr) $(f_ddrconfig_end); erase $(f_ddrconfig_addr) $(f_ddrconfig_end)
mtdparts=ifx_nor0:128k@0(uboot),3648k@128k(pri_image),3648k@3776k(sec_image),512k@7424k(btagent),64k@7936k(pri_bfocus_cfg),64k@8000k(sec_bfocus_cfg),64k@8064k(sysconfig),64k@8128k(misc_cfg),2624k@1152k(pri_rootfs),2624k@4800k(sec_rootfs),8192k@0(all_flash)
part0_begin=0xB0000000
part1_begin=0xB0020000
part2_begin=0xB03B0000
part3_begin=0xB0740000
part4_begin=0xB07C0000
part5_begin=0xB07D0000
part6_begin=0xB07E0000
part7_begin=0xB07F0000
total_part=8
flash_end=0xB07FFFFF
data_block0=uboot
data_block1=pri_img
data_block2=sec_img
data_block3=btagent
data_block4=pri_bfocus_cfg
data_block5=sec_bfocus_cfg
data_block6=sysconfig
data_block7=ubootconfig
data_block8=fwdiag
total_db=9
f_uboot_addr=0xB0000000
f_uboot_size=0x00020000
f_ubootconfig_addr=0xB07F0000
f_ubootconfig_size=0x0000F000
f_ubootconfig_end=0xB07FEFFF
f_pri_img_addr=0xB0020000
f_pri_img_size=0x390000
f_pri_img_end=0xB03AFFFF
f_pri_kernel_addr=0xB0020000
f_pri_kernel_size=0x100000
f_pri_kernel_end=0xB011FFFF
f_pri_rootfs_addr=0xB0120000
f_pri_rootfs_size=0x00290000
f_pri_rootfs_end=0xB03AFFFF
f_sec_img_addr=0xB03B0000
f_sec_img_size=0x390000
f_sec_img_end=0xB073FFFF
f_sec_kernel_addr=0xB03B0000
f_sec_kernel_size=0x00100000
f_sec_kernel_end=0xB04AFFFF
f_sec_rootfs_addr=0xB04B0000
f_sec_rootfs_size=0x00290000
f_sec_rootfs_end=0xB073FFFF
f_btagent_addr=0xB0740000
f_btagent_size=0x00080000
f_btagent_end=0xB07BFFFF
f_pri_bfocus_cfg_addr=0xB07C0000
f_pri_bfocus_cfg_size=0x00010000
f_pri_bfocus_cfg_end=0xB07CFFFF
f_sec_bfocus_cfg_addr=0xB07D0000
f_sec_bfocus_cfg_size=0x00010000
f_sec_bfocus_cfg_end=0xB07DFFFF
f_all_flash_addr=0xB0000000
f_all_flash_size=0x00800000
f_all_flash_end=0xB07FFFFF
f_sysconfig_addr=0xB07E0000
f_sysconfig_size=0x00010000
f_fwdiag_addr=0xB07FF000
f_fwdiag_size=0x400
f_calibration_addr= IFX_CFG_FLASH_CALIBRATION_START_ADDR
f_calibration_size=IFX_CFG_FLASH_CALIBRATION_CFG_SIZE
f_ddrconfig_addr=0xB07FF400
f_ddrconfig_size=0x100
f_ddrconfig_end=0xB07FF4FF
ethact=vr9 Switch
ethaddr=88:03:55:76:CE:C9
bootfile=openwrt-lantiq-xrx200-VG3503J_v2-squashfs.image
bootcmd=cp.b 0xb0020000 0x80002000 0x400000; go 0x80002000
stdin=serial
stdout=serial
stderr=serial
ipaddr=192.168.1.100
serverip=192.168.1.1
boofile=openwrt-lantiq-xrx200-VG3503j_v2_squashfs.image
preboot=ping 1.1.1.1;run bootcmd
update_openwrt=erase 0xb0020000 0xb073ffff;tftp 0x81000000 openwrt-lantiq-xrx200-VG3503J_v2 -squashfs.image;cp.b 0x81000000 0xb0020000 $(filesize)
Environment size: 4867/61436 bytes
VR9 #
-
Printenv below:-
update_openwrt=erase 0xb0020000 0xb073ffff;tftp 0x81000000 openwrt-lantiq-xrx200-VG3503J_v2 -squashfs.image;cp.b 0x81000000 0xb0020000 $(filesize)
Environment size: 4867/61436 bytes
VR9 #
you have a "space" between v2 and -squashfs :)
try fixing it first.
-
Yep, spotted that and fixed, was using a text file for copy/paste which had picked up the extra space. Fixed that and now saying "tftp error - file not found.
I'll try again from a fresh start shortly.
Thanks for your help, it's greatly appreciated.
-
OK, this is starting to do my head in now.
Modem trying to tftp firmware gives this error:-
TFTP from server 192.168.1.1; our IP address is 192.168.1.100
Filename 'openwrt-lantiq-xrx200-VG3503J_v2-squashfs.image'.
Load address: 0x81000000
Loading: *
TFTP error: 'File not found' (1)
Tftpd32 log entries show:-
Connection received from 192.168.1.100 on port 3814 [30/03 18:16:44.573]
Read request for file <openwrt-lantiq-xrx200-VG3503J_v2-squashfs.image>. Mode octet [30/03 18:16:44.573]
File <openwrt-lantiq-xrx200-VG3503J_v2-squashfs.image> : error 2 in system call CreateFile The system cannot find the file specified. [30/03 18:16:44.573
The correct file is in a folder tftpimage which is set as the base folder in tftpd32.
Any ideas?
-
The correct file is in a folder tftpimage which is set as the base folder in tftpd32.
Any ideas?
Can you set the same folder in the main window as "Current directory" ?
-
Yep, done that. I've also copied the file to the tftpd32 root folder and set it to that - same result.
-
Sorted! In it's ultimate wisdom Win7 downloaded the image file as .image.htm then proceeded to hide the .htm extension.
I spent the final 10 years of my career as a Microsoft MCSE but a couple of years ago I switched my personal computing to the Apple world and now hate Windows with a passion!
-
Reflashed the modem and my previous issue seems to be resolved.
I noticed earlier that someone had applied the latest modem firmware to the OpenWRT build, can someone please give me a very brief guide on how to do this? Would be much appreciated!
-
I see you've added these?
option _orig_ifname 'eth1'
option _orig_bridge 'false'
I believe this fixes our Multicast problem, thanks. :)
I'm not sure why DNS isn't working as expected though, have you changed any other files?
I'm using YouView/BT and those additions don't seem to produce any difference. I added them and issued "/etc/init.d/network reload".
config interface 'wan'
option ifname 'eth0'
option force_link '1'
config interface 'wan_bridge'
option type 'bridge'
option proto 'none'
option ifname 'eth0 ptm0.101'
option auto '1'
config interface 'lan'
option ifname 'eth1'
option _orig_ifname 'eth1'
option _orig_bridge 'false'
option force_link '1'
option proto 'static'
option netmask '255.255.255.0'
option ip6assign '60'
option ipaddr '192.168.1.50'
option gateway '192.168.1.1'
option dns '8.8.8.8 8.8.4.4'
-
Reflashed the modem and my previous issue seems to be resolved.
I noticed earlier that someone had applied the latest modem firmware to the OpenWRT build, can someone please give me a very brief guide on how to do this? Would be much appreciated!
the vdsl firmware location is specified in /etc/config/network
config vdsl 'dsl'
option annex 'a'
option firmware '/lib/firmware/vdsl.bin'
option tone 'av'
option xfer_mode 'ptm'
You can find latest releases here:
https://xdarklight.github.io/lantiq-xdsl-firmware-info/
-
Thanks - I don't suppose you'd have the extracted bin for 5.7.5.5.1.7 that you could make available to me? I'm having nightmares trying to make unsquashfs4-lzma-avm-be as I'm not that familiar with *nix
Cheers.
-
hi,
would someone mind helping a newbie please.. There are 2 chips on my eci modem one large one being 1.2 and the smaller one being a 1.1 - which version should I use as per the original post in step one as I don't really want to brick it..
am I v1 or v2 image
Many thanks
-
The big chip must be labelled VRX268, that's the main chip, so I suppose you want the v2 image.
(The smaller chip is probably the VRX208, which is described as the "Analog Front-End and line driver".)
I think it may also be possible to tell from a line in the boot log, it either says "GPHY FW load for A1x !!" or "GPHY FW load for A2x !!" depending on the chip version.
-
Thanks making some progress and pins must work but must have something wrong as when the loading TTTT retry count is exceeded.
edit: ok my bad, image loaded and appears to be working fine, now to test it on my vdsl connection ::)
-
jsamuel before I order your ebay service can you make it so the image has 2 vlan's? meaning one can use just one lan cable for wan and stat traffic.
second vlan been on 192.168.2.x.
-
... the System Log seems to say that it can't connect:
Sun Mar 6 20:08:42 2016 daemon.info pppd[3928]: Exit.
Sun Mar 6 20:08:42 2016 daemon.notice netifd: Interface 'wan' is now down
Sun Mar 6 20:08:42 2016 daemon.notice netifd: Interface 'wan' is setting up now
Sun Mar 6 20:08:43 2016 daemon.info pppd[3951]: Plugin pppoatm.so loaded.
Sun Mar 6 20:08:43 2016 daemon.info pppd[3951]: PPPoATM plugin_init
Sun Mar 6 20:08:43 2016 daemon.info pppd[3951]: PPPoATM setdevname_pppoatm - SUCCESS:0.0.38
Sun Mar 6 20:08:43 2016 daemon.notice pppd[3951]: pppd 2.4.7 started by root, uid 0
Sun Mar 6 20:08:43 2016 daemon.err pppd[3951]: connect(0.0.38): No such device
Sun Mar 6 20:08:43 2016 daemon.info pppd[3951]: Exit.
Thank you to those who made suggestions, but various combinations failed to get any internet connection :(
However, I may have discovered why: My ISP uses pppoa and, according to https://forum.openwrt.org/viewtopic.php?id=63240 (https://forum.openwrt.org/viewtopic.php?id=63240), the pppoa packages need to be installed separately. It will take some effort to install on a device with no internet connection, and it's a big package (so might not fit into the ECI).
I'm giving up! I've learned a lot getting this far, but I think that now this ECI is destined for eBay ...
-
It looks like the necessary components for PPPoA are included in jsamuel's OpenWrt builds. You also probably need to change the xfer_mode option from "ptm" to "atm" for ADSL / PPPoA use.
-
Thanks, ajs, but the ECI continues to frustrate my attempts to connect it to my ADSL2+ line. I've tried to understand the documentation. If someone else wants to take on the project, then I've included below the final log entries and my unsuccessful /etc/config/network file.
I wanted a simple internet connection with LAN1 and LAN2 connected directly to the PC.
OpenWRT system log:
Mon Aug 31 21:04:34 2015 daemon.err pppd[4154]: connect(0.0.38): No such device
Mon Aug 31 21:04:34 2015 daemon.info pppd[4154]: Exit.
Mon Aug 31 21:04:35 2015 daemon.notice netifd: Interface 'wan' is now down
Mon Aug 31 21:04:35 2015 daemon.notice netifd: Interface 'wan' is setting up now
Mon Aug 31 21:04:35 2015 daemon.info pppd[4177]: Plugin pppoatm.so loaded.
Mon Aug 31 21:04:35 2015 daemon.info pppd[4177]: PPPoATM plugin_init
Mon Aug 31 21:04:35 2015 daemon.info pppd[4177]: PPPoATM setdevname_pppoatm - SUCCESS:0.0.38
Mon Aug 31 21:04:35 2015 daemon.notice pppd[4177]: pppd 2.4.7 started by root, uid 0
Mon Aug 31 21:04:35 2015 daemon.err pppd[4177]: connect(0.0.38): No such device
Mon Aug 31 21:04:35 2015 daemon.info pppd[4177]: Exit.
=======================================
root@OpenWrt:~# cat /etc/config/network
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fd88:f59f:8b1e::/48'
config interface 'wan'
option _orig_bridge 'true'
option _orig_ifname 'eth0'
option ifname 'eth0'
option proto 'pppoa'
option vci '38'
option vpi '0'
option atmdev '0'
option encaps 'vc'
option mtu '1432'
option username 'name@isp.net'
option password '***********'
option ipv6 'auto'
option defaultroute '0'
config interface 'wan6'
option ifname '@wan'
option proto 'dhcpv6'
config interface 'lan'
option ifname 'eth1'
option type 'bridge'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'
option dns '208.67.222.222 208.67.220.220'
config vdsl 'dsl'
option annex 'a2p'
option fwannex 'a'
option firmware '/lib/firmware/vdsl.bin'
option xfer_mode 'atm'
root@OpenWrt:~#
-
I'm not sure what I'm doing wrong, but I can't get the image file across via TFTP.
I have connected LAN1 to my MAC. I have given static IP of 192.168.1.169 to my MAC, and IP of 192.168.1.101 to the modem.
I type:-
VR9 # ping 192.168.1.169
and get response:-
host 192.168.1.169 is alive
I have a tftpserver running on my Mac, however, one I run the "run update_openwrt" command, it times out transferring the image from TFTP. In the tftpserver log, I get the error "tftpd: write: No route to host" followed by multiple lines of "tftpd: write: Host is down"
Do I need to set a subnet mask or anything in the router?
-
Hi.
If you are using the guide at the start of the post
being
set ipaddr 192.168.1.100 (modem)
set serverip 192.168.1.1 (your pc etc)
I set my pc to 192.168.1.1 and the flash was fine using tftp Once it completed I then set my pc to 192.168.1.3 for example so I could access the modem after it rebooted
Go with address's as specified in the guide to get the image on.
Once it reboots the modem will be on 192.168.1.1
Cheers
-
Well, as it happens, I went away to cook dinner, came back and at some point during that hour or so, the tftp kicked in and the image went across. I have no idea why it took so long!
A quick question. I haven't yet plugged it into my VDSL as the connection is in the loft. I know that since rebooting, the modem is on IP 192.168.1.1. Should it be issuing DHCP addresses, and should the Web interface be working (both without connecting to broadband)?
-
Fas as I know its just a modem. You need a router behind it to do your isp authentication and dhcp to your lan. Well I did/have done with the as listed image.
The interface on 192.168.1.1 will be viewable if you plug a pc or mac into port 2 and configure the pc or mac with a static of 192.168.1.3 for example so its in the same network as the modem, you could plug port 2 it in to your router on the lan side provided your router isnt using 192.168.1.1
The interface is viewable without the vdsl being active. The image will make the router use 192.168.1.1 as its given ip address on port2 for the interface
-
Ah! I see. Thanks :-)
-
You might (or might not, I don't know) be interested to know that I am using this version of the OpenWRT firmware to integrate these devices into Solarwinds Network Performance Monitor. I work for a mid-sized company who support a handful (31) of external workers on DSL lines. They don't make us enough money to put enterprise grade kit in place, so I'm trying to make the best of a bad situation and use the ISP provided equipment. However it's preferable for our helpdesk to have access to stats when troubleshooting problems, which is where Solarwinds NPM comes in. The rest of the 4000+ nodes on our network are in there, so these DSL lines should be too.
At the moment I'm using SSH scripts to log in to the ECI modem remotely and scrape stats (via /etc/init.d/dsl_control lucistat as it's very machine readable) and then powershell at the server side to populate some information about the interfaces (NPM can retrieve the interface usage data via SNMP but not negotiated speeds, so I scrape them from the dsl_control output then powershell them into the database via the Solarwinds API).
Ideally as the devices are remote I'd like to use SNMPv3 to query them. I know that the version of snmpd you provide available via opkg claims to support SHA and DES (not ideal but better than plaintext SNMPv2) but I'm having a bit of difficulty getting it to work. I wonder if perhaps snmpd is lying and isn't compiled against openssl at all, so has no encryption capabilities.
Also your dsl_control script has inconsistent outputs - when referring to values that have an up and down value you suffix each var with _up or _down except signal attenuation, which has a _up but no _down :)
Either way I'm very grateful for your OpenWRT images as my attempts to build my own, either via the full toolstack tree or the image builder would never boot the device!
-
So, further investigation with snmpd shows that it isn't compiled against openssl. This doesn't come as a surprise in a restricted environment like SoC devices. The red herring here is that if you ask snmpd if it supports encryption, it says that it does!
root@OpenWrt:/usr/lib/snmp# snmpd -H 2>&1 | grep -e 'def.*Type'
defAuthType MD5|SHA
defPrivType DES (AES support not available)
That should indicate that MD5 and SHA hashing is available for authentication, and DES (yuck) is available for encryption, but not AES. However...
root@OpenWrt:/usr/lib/snmp# snmpwalk -u Orion -A xxxxxxxx -a SHA -X xxxxxxxx -x DES -l authPriv -v3 127.0.0.1
MIB search path: /root/.snmp/mibs:/usr/share/snmp/mibs
Encryption support not enabled.
snmpwalk: USM encryption error
So I guess I'm on a hiding to nothing.
Sorry, this has turned into a more generic OpenWRT conversation than an ECI/r one!
-
So...
http://imgur.com/a/1RJ2z
I've killed him?
-
Those messages will only appear if your cable isn't connected, or some other error on your line.
-
Mhm, so what can I do?
I maked reboot but it start again
-
Connect the cable ;D
-
/# /etc/init.d/dsl_control status
Chipset: Lantiq XWAY VRX268
Firmware Version: 5.7.1.8.0.1
API Version: 4.16.2.4
MEI Version: 1.4.8.4
Power Management Mode: L0 - Synchronized
Line State: UP [0x801: showtime_tc_sync]
Line Uptime: 2m 34s
Resyncs: 4
DSLAM/MSAN VID: IFTN
XTSE Capabilities: 0x0, 0x0, 0x0, 0x0, 0x0, 0x1, 0x0, 0x0
Annex: A
Line Mode: G.992.5 (ADSL2+)
Profile: unknown
Trellis: D: ON / U: ON
Bitswap: D: ON / U: OFF
G.INP: D: Not Enabled / U: Not Enabled
Virtual Noise Support: D: Not Supported / U: Not Supported
Attain Data Rate: 15.316 Mb/s / 1.088 Mb/s
Actual Data Rate: 14.681 Mb/s / 1.087 Mb/s
Impulse Noise Prot: 0.0 sym / 0.0 sym
Interleave Delay: 0.25 ms / 0.25 ms
NFEC: 255 / 34
RFEC: 0 / 0
LSYMB: 3672 / 274
Interleave Depth: 1 / 1
Interleave Block: 255 / 34
LPATH: 0 / 0
Line Attenuation: 27.5dB / 11.7dB
Signal Attenuation: 25.6dB / 12.0dB
Noise Margin: 4.0dB / 6.8dB
Transmit power: 11.3dBm / 20.3dBm
FECS: 0 / 0
ES: 1 / 0
SES: 1 / 0
LOSS: 1 / 3
UAS: 334 / 334
HEC: 0 / 14
CRC_P: 0 / 0
CRCP_P: 0 / 0
15m Code Violations: 0 / 49
15m FEC Errors: 0 / 0
1d Code Violations: 137 / 81
1d FEC Errors: 0 / 0
So it's ok?
-
ADSL2+ usually uses ATM, not PTM, so those messages have have been something to do with the configuration for ADSL or the auto selection of ATM vs. PTM.
-
So what I have to do?
Now I can just connect router to LAN1 port and set up pppoe connection?
I have BT line. In router I have OpenWRT too.
-
Hi,
I need help, please :(
I've connected Belkin router to LAN1 ECI port, on Belkin I've set up a pppoe connection providing username and password - but it's not working, it show con connected info.
In ECI greed led is not blinking, only orange is lighting.
What is going one?
-
Has it been confirmed if jsamuel's firmware supports G.INP on the US and the DS?
-
When my eci cab had g.inp and I used an unlocked eci modem using jsamuels firmware on my link it had g.inp on ds only.
-
the lantiq chipset inside doesn't support g.inp on the upstream. no firmware can remedy that.
-
If j0hn was referring to the ECI cabinet, that might be true.
If j0hn was referring to the ECI modem, that's not true.
And thus the eternal confusion between the capabilities of the ECI cabinets and modems continues.
"Is it a limitation of the ECI cabinets or modems?"
"Yes."
-
I was notified some time ago G.INP was working on both paths on a Huawei cab.
-
I'll have to give it a test at some point. Be interesting to see how it deals with DS + US G.INP and vectoring (I'm one of the few) :)
Using TalkTalk's HG633 at present which gives essentially no stats at all, helpfully ::)
Older firmware (on the HG633) was very weird with G.INP. it seemed to somewhat work in that the sync was not reduced like it was when I used a non-G.INP compatible modem but then with the storm last night, the sync then dropped 10Mb like it does on said non-compatible modems. Then DLM removed it all together this morning.
Got an update from TT today that fully supports it apparently so maybe it will get re-enabled tomorrow morning. Then I might try this again. I've got too sitting there gathering dust. I'm just looking for something to reduce my error counts a bit.
I've found the problem with G.INP at least on my line is that I get a lot of large latency bursts presumably because G.INP is running a lot of the time.
Edit: apologies for going off topic somewhat.
-
Lantiq VDSL2 firmware versions that end in 6 do not support vectoring. So the 5.7.4.3.0.6 firmware contained in these OpenWRT images does not support vectoring.
Firmware versions that end in 7 do support vectoring. 5.7.4.3.0.7 can be extracted from the TP-Link VR200 firmware, or newer firmware versions (http://xdarklight.github.io/lantiq-xdsl-firmware-info/) could be extracted from FritzBox firmware or even the Netgear DM200. The FritzBox Lantiq DSL .bin files appear to be slightly customised specially for FritzBox.
-
Completely beyond me I'm afraid :(
-
I hope this is clearer then: the current OpenWRT images do not support vectoring.
-
I hope this is clearer then: the current OpenWRT images do not support vectoring.
I meant, how would one go about fixing the images to support vectoring.
-
I think OpenWRT has a writable filesystem, so you should be able to replace the vdsl.bin file by copying a new file onto the device using sftp.
-
Ah, I can do that! :)
-
If j0hn was referring to the ECI cabinet, that might be true.
If j0hn was referring to the ECI modem, that's not true.
And thus the eternal confusion between the capabilities of the ECI cabinets and modems continues.
I was half asleep in bed, but in all honesty I thought that was the case for both. Shouldn't surprise me that OpenReach provide CPE that supports technology the DSLAM doesn't. Does the ECI V41 support upstream G.INP?
-
How is anyone going to know if the ECI V41 supports upstream G.INP? I'd guess that as it apparently uses the same line cards as the M41 and other ECI things, it would have the same limitations regarding G.INP.
If BT are somehow unaware that support for upstream retransmission was added in Lantiq VDSL2 firmware versions >= 5.7.X.X.X.X, that would explain why the BT HomeHub 5A and the ECI modems never seemed to get a firmware update for it.
-
Where would I find a new vdsl.bin file? :)
-
There are instructions on how to extract the firmware from various other devices' firmware on http://xdarklight.github.io/lantiq-xdsl-firmware-info/
I don't think the vectoring firmwares can be legally redistributed, as it says at the bottom of that page.
The 5.8.1.5.0.7 firmware can also be found within the Netgear GPL source code (http://kb.netgear.com/app/answers/detail/a_id/2649) released for the DM200. I don't think anyone has actually confirmed if that firmware works on the VRX268 (the DM200 uses the newer VRX220 chip).
-
5.8.1.5.0.7-5.8.0.9.0.1 - it says the IDSN version includes vectoring support?
-
A successful extraction has been made of the 5.8.1.5.0.7-5.8.0.9.0.1 bin file. Now to test it on my vectoring-enabled line :)
-
Yes I know it's a bit weird, but all the VDSL2 versions say "VDSL over ISDN" or "VDSL over ISDN with vectoring". None of the VDSL2 firmwares have 5 for the last digit, which in theory indicates VDSL over POTS.
I've also just spotted DM200 firmware 1.0.0.36, which contains:
dsl_vr9_firmware_xdsl-05.07.09.05.01.07_05.07.03.0F.00.01.bin
They've apparently downgraded from 5.8.1.5.0.7 to 5.7.9.5.1.7.
-
How would I go about accessing the modem and using the bridge all on one LAN port? Tried editing the config as per this thread but the modem becomes inaccessible :(
With the HG612, I added another interface on the WAN side on my OpenWrt router and I was able to connect to the HG612 and use it all as a bridge, all through the one cable. The HG612 would have an IP on a 192.168.2.x subnet and the OpenWrt router would be on the 192.168.1.x subnet.
How do I achieve that here? :)
-
Hi,
I've just flashed my V2 device and it seems to have worked fine. One question, which I notice was touched upon earlier in the thread was RF4638 (Baby Jumbo). Is this not supported at present? If not, is it a hardware issue or OpenWRT build issue?
Thanks
Tom
-
Hey folks,
Managed to tftp the v1.2 openwrt image on to my ECI /r v1.2 and booted openwrt successfully but only once. After issuing "reboot" in openwrt it will no longer fire up and I get the message below repeated on the serial console and no access to the bootloader.
ROM VER: 1.1.4
CFG 0c
Anyway to recover from this or I have bricked it? Tried ctrl + c, ctrl + break, long reset but no joy.
Cheers
-
Is anyone able to help out with a mirror of the images as the original links are not working? I need v1. Thanks
-
Thanks for letting me know, recently changed web server software so directory listing was messed up.
Fixed.
-
I managed to re-image my modem and configure it to connect to my ISP (TalkTalk). However when I connect the laptop to the WAN port (labeled LAN 1 and associated with the interface eth0) I am not able to browse the web.
I had a few tries in configuring the interface but obviously I am doing something wrong as nothing works...
Here is the network configuration file:
root@OpenWrt:~# cat /etc/config/network
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fd88:f59f:8b1e::/48'
config interface 'wan'
option ifname 'eth0'
option _orig_ifname 'eth0'
option _orig_bridge 'false'
option proto 'dhcp'
config interface 'wan_bridge'
option type 'bridge'
option _orig_ifname 'eth0 ptm0.101'
option _orig_bridge 'true'
option proto 'dhcp'
option delegate '0'
option ifname 'eth0 eth0.101 ptm0 ptm0.101'
config interface 'lan'
option ifname 'eth1'
option force_link '1'
option proto 'static'
option ipaddr '192.168.1.1'
option gateway '192.168.1.2'
option netmask '255.255.255.0'
option ip6assign '60'
option dns '208.67.222.222 208.67.220.220'
config vdsl 'dsl'
option annex 'a'
option firmware '/lib/firmware/vdsl.bin'
option tone 'av'
option xfer_mode 'ptm'
Anyone able to help?
-
You've left a lot of information out such as whether you have ADSL/VDSL PPPoE or other. There seems to be a lot missing. If you're intending to connect a PC direct to the modem I would expect to see NAT enabled on the modem or at least routing rather than bridging when using a private address. In the UK we typically have PPPoE provision with the endpoint connection on a separate router. The Chaos Chalmer firmware can however provide routing if required with a PPPoE termination internal.
Perhaps you could explain how you intend your setup to work.
-
Thanks for your reply, currytop.
After imaging the modem with OpenWrt (Chaos Calmer) using jsamuel's excellent instructions (link (http://forum.kitz.co.uk/index.php/topic,15918.msg296169.html#msg296169)), I went through the following:
- changed the password for SSH and web access
- set up the VDSL2 link to TalkTalk (described below)
- backed-up the settings
- as described in my previous message, I tried different settings for the eth0 interface (WAN, or LAN 1 as its label states)
To set up the VDSL2 fibre link to TalkTalk:
From the Network drop-down list I chose 'Interfaces' then from the 'Interface Overview' I clicked on the 'Edit' button for the WAN_BRIDGE network where i set up the following:
In the 'General Setup' tab:
- protocol: select DHCP Client then click on the 'Switch protocol' button (unlike other ISP's, TalkTalk does NOT use the PPoE protocol for their fibre optic service)
- no change in the 'Hostname to send when requesting DHCP' field
In the 'Advanced Settings' tab:
- all I did was to un-tick the 'Use builtin IPv6-management' box and left all other settings untouched
In the 'Physical Settings' tab:
- I created two new custom interfaces (VLAN's): ptm0.101 and eth0.101 and bridged the ptm0 and the eth0 interfaces as shown in the attached screen capture.
In the 'Firewall Settings' tab:
- I left all the settings as they were
Then I clicked on the 'Save and Apply' button.
To verify my settings I selected 'Diagnostics' from the drop-down 'Network' list and performed all three tests (also attached). To be 100% the link works I successfully pinged Google after establishing a terminal SSH session to the modem:
BusyBox v1.23.2 (2015-08-05 16:53:44 BST) built-in shell (ash)
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
CHAOS CALMER (Bleeding Edge, r46559)
-----------------------------------------------------
* 1 1/2 oz Gin Shake with a glassful
* 1/4 oz Triple Sec of broken ice and pour
* 3/4 oz Lime Juice unstrained into a goblet.
* 1 1/2 oz Orange Juice
* 1 tsp. Grenadine Syrup
-----------------------------------------------------
root@OpenWrt:~# ping www.google.com
PING www.google.com (216.58.208.132): 56 data bytes
64 bytes from 216.58.208.132: seq=0 ttl=56 time=6.039 ms
64 bytes from 216.58.208.132: seq=1 ttl=56 time=6.400 ms
64 bytes from 216.58.208.132: seq=2 ttl=56 time=5.902 ms
64 bytes from 216.58.208.132: seq=3 ttl=56 time=6.122 ms
64 bytes from 216.58.208.132: seq=4 ttl=56 time=5.926 ms
64 bytes from 216.58.208.132: seq=5 ttl=56 time=5.823 ms
64 bytes from 216.58.208.132: seq=6 ttl=56 time=6.287 ms
64 bytes from 216.58.208.132: seq=7 ttl=56 time=5.771 ms
64 bytes from 216.58.208.132: seq=8 ttl=56 time=5.756 ms
^C
--- www.google.com ping statistics ---
9 packets transmitted, 9 packets received, 0% packet loss
round-trip min/avg/max = 5.756/6.002/6.400 ms
Then I backed up all the settings ('System' -> 'Backup / Flash Firmware' -> 'Generate archive').
I didn't configure NAT or any static routes.
Any help will be greatly appreciated. Thank you!
-
I'm not at home so reading on my phone, but I don't see whether you're using all static addresses or DHCP for local clients. If static then have you set a default gateway on your client? Clearly you have a working internet connection. Don't forget the firewall.
-
Since my first post, I deleted all the configuration from the eth0 (WAN, labeled LAN 1) interface. The plan is to configure the interface with a static IP.
The eth1 interface (LAN, labeled LAN 2) is configured with the 192.168.1.1 static IP (used for web and SSH access), whereas the gateway (modem) IP is 192.168.1.2 (these are the defaults built into the OpenWRT image). I wonder, what static IP and default gateway to use for the eth0 interface?
In the near future, to this port, I intend to connect a Meraki MX64 Security Appliance but for now (testing purposes) all I need to connect is the Ethernet port of my laptop.
I am afraid I won't have much time for this experiment until next weekend but I will try then again to configure the interface and a default route.
Thanks again for your help.
-
Good Morning,
I've had this thread bookmarked for a while, waiting to get around to this. I got myself a spare modem locally and managed to get through the whole guide (thank you jsamuel).
I've adjusted my LAN addressing to suit that of your recommended (Router 1.2 and the modem by default is 1.1).
My setup before was a stock ECI Openreach Modem & a Draytek 2830 dialing with PPPoE. Doing a straight swap (other than an additional cable from LAN2 to the LAN on my Draytek) for my new OpenWRT modem doesn't seem to work - I get a response of "No response from server side" on the Draytek.
I can get into the OpenWRT web interface on 1.1 and get the output below...... Does this mean the modem is connected, but the router is unable to dial out a connection?
Any help would be hugely appreciated.
Line Mode: G.993.2 (VDSL2) Annex B Profile 17a
Status & Uptime: UP 4m 54s Resyncs: 1
Line State: showtime_tc_sync [0x801]
Power Mode: L0 - Synchronized
Downstream Upstream
Attainable Line Speed: 66.666 Mb/s 24.568 Mb/s
Actual Line Speed: 58.555 Mb/s 20.000 Mb/s
Trellis: D: ON U: ON
Bitswap: D: ON U: OFF
G.INP: D: Not Enabled U: Not Enabled
Virtual Noise Support: D: Not Supported U: Not Supported
Interleave Depth: 853 1
Interleave Block: 85 255
Interleave Delay: 8.0 ms 0.0 ms
INP: 3.0 0.0
NFEC: 85 255
RFEC: 16 16
LSYMB: 18117 5410
LPATH: 0 0
Line Attenuation: 18.3 dB / 20.3 dB
Noise Margin/SNR: 5.7 dB / 9.2 dB
Transmit Power: 6.8 dBm / 6.6 dBm
Errors Since Line Up
FECS: 18 1428089
ES: 0 2231
SES: 0 8
LOSS: 0 35
UAS: 34 34
HEC: 0 0
CRC_P: 0 0
CRCP_P: 0 0
Errors in 15 Minutes
Code Violations: 0 23961
FECS: 18 1428089
Errors in 1 Day
Code Violations: 0 23961
FECS: 18 1428089
-
Welcome to the Kitz forum. :)
Having looked through the output that you have attached, I read it as the modem has, indeed, synchronised with the DSLAM but it appears that a PPPoE session has not been established.
As I know very little about the usage of OpenWRT with the ECI B-FOCuS modems, I am unable to make any suggestions. Hopefully another of our members will be able to assist . . .
-
Add me to the list of frustrated users that just can't seem to get this thing going :no:
Up until this morning my draytek 2820 was handling modem duties on adsl. As soon as the adsl dropped and the vdsl was switched on i powered up the ECI modem and updated the firmware to openwrt CHAOS CALMER (15.05.1, r48532).
I had expected that after updating to openwrt i could perhaps use the modem on its own and dispense with the 2820, or at the very least plug the modem into the wan2 port on the draytek.
I've been swearing at this thing for a while now and no matter what i do i cannot get the damned thing to do anything other than power up and say that there is a vdsl signal.
Edit:
As a last resort i re-flashed and it now mostly works. The GUI asks for the login password very often, but other than that i have an internet connection :)
BvB
-
I don't know if this is relevant or useful, but I believe the ethernet driver on this and the BTHH5 are the same (lantiq).
I proposed a change to allow mini-jumbo frames on the ethernet, see:
https://forum.lede-project.org/t/lantiq-vrx200-pppoe-1500-bytes/4087/2
but was unable to test as the ECI was limited to 1500 also.
Maybe someone who builds LEDE for ECI may like to try?
Should enable you to use full 1500 mtu on the pppoe connection with any UK ISP using BT Openreach (assuming the router you are using with the ECI also supports frames of 1508 on the ethernet link).
-
Has anyone managed to get this going with ADSL instead of VDSL?
I am currently still on the official firmware, I switched to ADSL using
/usr/sbin/vg3503j_bt_xml_modify.sh WAN_CFG_GROUP_T_00 media_type ADSL
The line syncs, but I still get no traffic on the nas interface...any idea?
Should it work straight away if I flash a non-modified OpenWrt?
How can I backup the current squashfs, considering the modem has no internect connection and does not seem to ship with ssh?
-
Welcome to the Kitz forum. :)
Has anyone managed to get this going with ADSL instead of VDSL?
I am currently still on the official firmware, I switched to ADSL using
/usr/sbin/vg3503j_bt_xml_modify.sh WAN_CFG_GROUP_T_00 media_type ADSL
The line syncs, but I still get no traffic on the nas interface...any idea?
I suspect you have not changed the device's configuration from packet transfer mode (PTM) to asynchronous transfer mode (ATM). That would result in exactly the symptoms you have described.
Unfortunately I do not have any experience of using the modem/router and so will not be able to help you.
-
Welcome to the Kitz forum. :)
I suspect you have not changed the device's configuration from packet transfer mode (PTM) to asynchronous transfer mode (ATM). That would result in exactly the symptoms you have described.
Unfortunately I do not have any experience of using the modem/router and so will not be able to help you.
thanks for getting back to me :)
The device seems to be on ATM. The line syncs, and I get download/upload rates.
"DSL_STATUS Notification
Negotiated DSL Mode = ADSL
Negotiated TC Mode = ATM
>> DSL data rate: US 888 kbps, DS 14494 kbps.
>> DSL link up, time 76, handshake elapsed time 76"
But then udhcpc is started, and it doesn't get any reply.
I'm not sure how to proceed from there, the Asus router fails to connect over PPPoE reporting "Timeout waiting for PADO packets"
-
Nothing...I backed up, flashed with the 15.05.1 from OpenWRT's website.
I can't even get this one to sync the line.
I edited /etc/config/network to use annex a (tried b and j too) and atm
But the DSL led doesn't come on at all, and dsl_control reports the line as "Idle"
Any clue?
-
Hi folks,
I'm currently using a BT HH5A running LEDE on my VDSL link. I am going to update a router with a much fast CPU so I can run OpenVPN on it without crippling throughput.
As I'll be running LEDE/OpenWRT on the new router, I'll likely need to dust off the BT ECI V2 modem the BT Openreach enginieer left when they put me onto VDSL (I had an HH 5A then so just used it). Or would I be better off with the Huawei HG612?
Apart from the "I have control" issue that all we techies love, what are the benefits of flashing this modem with OpenWRT?
Oh yes, while I'm here, How do I found out what type of DSLAM is in my cabinet?
** Update ** Thanks to post from Dray below, I've found out I'm on a Hauwei cabinet
Thanks
Dave
-
http://www.kitz.co.uk/adsl/cabinet-lookup.htm
-
Hi Everyone,
After a fair bit of reading ( ??? ) - one question...Is the best way to get the top off these things still by following the advice to drill a 2mm hole in the sides (http://forum.kitz.co.uk/index.php?topic=11818.msg225850 Reply #7)?
Thanks
-
Welcome to the Kitz forum. :)
It is possible to open the /r ECI devices by using a number of plastic implements to gently distort the casing and ease off the lid. Start from the long side which has the fixing screws and gradually work around towards the back. Once the first clip has been released then task then becomes easier.
-
Drilling method worked for me numerous times... dremmel worked a treat..
As you are on a huawei cab I would stick with a broadcom device which would give you easy access to stats too
-
Drilling method worked for me numerous times... dremmel worked a treat..
As you are on a huawei cab I would stick with a broadcom device which would give you easy access to stats too
Thanks - one metal spudger, 10 mins later and I was in, serial header fitted and OpenWrt installed! Yay!
With regards to the cab, it's just gone live with FTTC and I am waiting for my order to activate on 13th Sept. I currently have a Draytek 2830n doing the ADSL biz and I will be using the Openreach modem on the WAN port (so any pointers to guides for that would be good!). I am debating getting a Vigor 130, but thought I'd give the Openreach modems a go first as I managed to obtain a couple of 'unwanted' ones.
Sidenote: For fitting the serial port header, I've seen mention elsewhere of using a 1mm drill bit to clear the solder from the PCB holes (especially the end ones as they are attached to the power and ground planes and a bit of a bugger to clear) - 'in the trade' a 0.8mm bit is generally used as there is less chance of taking out the through-hole plating.
So - where to next - any tweaks I should now go do to get ready for VDSL?
-
Sidenote: For fitting the serial port header, I've seen mention elsewhere of using a 1mm drill bit to clear the solder from the PCB holes (especially the end ones as they are attached to the power and ground planes and a bit of a bugger to clear) - 'in the trade' a 0.8mm bit is generally used as there is less chance of taking out the through-hole plating.
A good tip. Thank you for mentioning it.
-
I have successfully installed OpenWrt on my ECI V2 by following the excellent guide on the first post.
I have encountered a recurring problem, after ever 10 or so days, I am unable to browse the internet unless I power-cycle the modem. I was using a Asus N66U router and now a Plusnet Hub with the same issue.
I wanted to upgrade OpenWrt with this file: openwrt-15.05-lantiq-xrx200-VG3503J_V2-squashfs.image Unfortunately, I was unable to load it via the webgui update (LuCI) page and also failed with sysupgrade via ssh.
Any help with this would be appreciated.
Thanks.
-
Help please adjust the work with the profile 17a
At the moment the modem is synchronized with the profile 8b
I downloaded the file https://www.openreach.co.uk/orpg/home/products/super-fastfibreaccess/super-fastfibreaccess/landrgnu/downloads/code/ECI_Arcadyan_VDSL_modem.zip,
Using Arc, I unzipped the xcpe_hw.bin file from the dsl_vr9_firmware_xdsl-05.04.07.09.01.06_05.04.04.04.01.01 archive, renamed it to vdsl.bin, copied it to the / lib / firmware /
The following line is added to the / etc / config / network file.
option firmware '/lib/firmware/vdsl.bin'
The modem can not be synchronized
What am I doing wrong?
root@LEDE:~# /etc/init.d/dsl_control status
ATU-C Vendor ID: Broadcom 177.174
ATU-C System Vendor ID: Broadcom
Chipset: Lantiq-VRX200 Unknown
Firmware Version: 5.4.7.9.1.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: 8d
Line State: UP [0x801: showtime_tc_sync]
Forward Error Correction Seconds (FECS): Near: 0 / Far: 0
Errored seconds (ES): Near: 0 / Far: 20
Severely Errored Seconds (SES): Near: 0 / Far: 5
Loss of Signal Seconds (LOSS): Near: 0 / Far: 4
Unavailable Seconds (UAS): Near: 171 / Far: 171
Header Error Code Errors (HEC): Near: 0 / Far: 0
Non Pre-emtive CRC errors (CRC_P): Near: 1 / Far: 0
Pre-emtive CRC errors (CRCP_P): Near: 0 / Far: 0
Power Management Mode: L0 - Synchronized
Latency / Interleave Delay: Down: Interleave (6.0 ms) / Up: Interleave (4.0 ms)
Data Rate: Down: 7.556 Mb/s / Up: 572 Kb/s
Line Attenuation (LATN): Down: 10.9dB / Up: 0.0dB
Signal Attenuation (SATN): Down: 15.5dB / Up: 0.0dB
Noise Margin (SNR): Down: 14.2dB / Up: 36.3dB
Aggregate Transmit Power (ACTATP): Down: 9.4dB / Up: 3.9dB
Max. Attainable Data Rate (ATTNDR): Down: 15.723 Mb/s / Up: 2.812 Mb/s
Line Uptime Seconds: 12
Line Uptime: 12s
my Belgacom provider This is the data from my Fritz.Box modem.
Negotiated Connection Properties
Receive Direction Send Direction
Max. DSLAM throughput kbit/s 50000 10000
Min. DSLAM throughput kbit/s 14568 0
Attainable throughput kbit/s 88803 15236
Current throughput kbit/s 49997 9998
Seamless rate adaptation off off
Latency fast fast
Impulse Noise Protection (INP) 32 42
G.INP on on
Signal-to-noise ratio dB 17 10
Bitswap off on
Line attenuation dB 16 25
Profile 17a
G.Vector full full
Carrier record B43 B43
-
Firmware Version: 5.4.7.9.1.6
There are two problems:
1. This is a very old firmware version.
2. The firmware does not support vectoring.
The profile and bandwidth have probably been restricted due to the lack of vectoring support.
Find a later firmware that supports vectoring:
http://xdarklight.github.io/lantiq-xdsl-firmware-info/
-
Unfortunately on this page only Firmware Version: 5.4.7.9.1.6
fresh for my modem there I did not find.
-
You can take the vdsl.bin file from the firmware for a different device and use it with the ECI modem. Try a .bin file extracted from the Netgear DM200 firmware.
-
Thank you very much, everything turned out with the firmware
dsl_vr9_firmware_xdsl-05.07.09.05.01.07_05.07.03.0F.00.01 (http://)
connect stat with Home Hub 5a
root@LEDE:~# /etc/init.d/dsl_control status
ATU-C Vendor ID: Broadcom 177.174
ATU-C System Vendor ID: Broadcom
Chipset: Lantiq-VRX200 Unknown
Firmware Version: 5.7.9.5.1.7
API Version: 4.17.18.6
XTSE Capabilities: 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x2
Annex: B
Line Mode: G.993.5 (VDSL2 with down- and upstream vectoring)
Profile: 17a
Line State: UP [0x801: showtime_tc_sync]
Forward Error Correction Seconds (FECS): Near: 0 / Far: 35801
Errored seconds (ES): Near: 0 / Far: 24
Severely Errored Seconds (SES): Near: 0 / Far: 5
Loss of Signal Seconds (LOSS): Near: 0 / Far: 4
Unavailable Seconds (UAS): Near: 122 / Far: 122
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: Down: Fast (0.18 ms) / Up: Fast (0.0 ms)
Data Rate: Down: 50.064 Mb/s / Up: 15.064 Mb/s
Line Attenuation (LATN): Down: 18.3dB / Up: 21.7dB
Signal Attenuation (SATN): Down: 18.3dB / Up: 21.5dB
Noise Margin (SNR): Down: 12.6dB / Up: 6.5dB
Aggregate Transmit Power (ACTATP): Down: 1.4dB / Up: 13.6dB
Max. Attainable Data Rate (ATTNDR): Down: 92.778 Mb/s / Up: 22.052 Mb/s
Line Uptime Seconds: 18
Line Uptime: 18s
-
Thank you very much, everything turned out with the firmware
dsl_vr9_firmware_xdsl-05.07.09.05.01.07_05.07.03.0F.00.01 (http://)
Can you share the new connecting stats?
-
B-FOCus V-2FUb/r Rev B
root@LEDE:~# /etc/init.d/dsl_control status
ATU-C Vendor ID:
ATU-C System Vendor ID:
Chipset: Lantiq-VRX200 Unknown
Firmware Version: 5.7.9.5.1.7
API Version: 4.17.18.6
XTSE Capabilities: 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x2
Annex: B
Line Mode: G.993.5 (VDSL2 with down- and upstream vectoring)
Profile: 17a
Line State: UP [0x801: showtime_tc_sync]
Forward Error Correction Seconds (FECS): Near: 0 / Far: 35804
Errored seconds (ES): Near: 0 / Far: 24
Severely Errored Seconds (SES): Near: 0 / Far: 5
Loss of Signal Seconds (LOSS): Near: 0 / Far: 4
Unavailable Seconds (UAS): Near: 127 / Far: 127
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: Down: Fast (0.18 ms) / Up: Fast (0.0 ms)
Data Rate: Down: 50.064 Mb/s / Up: 15.064 Mb/s
Line Attenuation (LATN): Down: 18.3dB / Up: 21.5dB
Signal Attenuation (SATN): Down: 18.3dB / Up: 21.5dB
Noise Margin (SNR): Down: 13.0dB / Up: 6.5dB
Aggregate Transmit Power (ACTATP): Down: 1.1dB / Up: 13.6dB
Max. Attainable Data Rate (ATTNDR): Down: 94.251 Mb/s / Up: 22.063 Mb/s
Line Uptime Seconds: 9
Line Uptime:
-
Although I don't have a ECI/r modem, I do have a Zyxel with the same chipset. I hope you guys are willing to help me with the following problem with seems to be similar to the discussion in this thread.
I have installed LEDE/OpenWRT on my Zyxel with a Lantiq VRX chipset and I am able to connect to my ISP via VDSL2. However, I can't get the same speed as with the stock modem from my ISP. It's the same Zyxel, and I also rooted that modem to get to the Lantiq firmware that my ISP is using. However, I'm still only getting 22/2Mbps on my LEDE modem, where I should be getting 30/3Mbps.
I noted one difference in the line features, namely that bitswap is enabled on both up- and downstream on the stock modem, but on the LEDE modem, it is not enabled on the downstream. How can I enable bitswap on the downstream?
I saw this command on page 1 of the thread, but where do I run it? Should I build a new LEDE image or can I configure these options while the modem is running?
DSL_CPE#>lfcg 1
nReturn=0 nDirection=1 bTrellisEnable=1 bBitswapEnable=1 bReTxEnable=1 bVirtualNoiseSupport=1 b20BitSupport=0
DSL_CPE#>lfcg 0
nReturn=0 nDirection=0 bTrellisEnable=1 bBitswapEnable=1 bReTxEnable=0 bVirtualNoiseSupport=1 b20BitSupport=0
Below is my dsl_control status for reference:
Chipset: Lantiq▒ XWAY▒ VRX268
Firmware Version: 5.7.5.6.1.7
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 Seconds: 2275
Line Uptime: 37m 55s
Resyncs: 1
ATU-C Vendor ID: Broadcom 177.28
ATU-C System Vendor ID: Broadcom
XTSE Capabilities: 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x2
Annex: B
Line Mode: G.993.5 (VDSL2 with down- and upstream vectoring)
Profile: 17a
Trellis: D: ON / U: ON
Bitswap: D: OFF / U: ON
G.INP: D: Enabled / U: Enabled
Virtual Noise Support: D: Supported / U: Not Supported
Attain Data Rate: 82.487 Mb/s / 52.455 Mb/s
Data Rate: Down: 22.400 Mb/s / Up: 2.152 Mb/s
NFEC: 32 / 32
RFEC: 16 / 16
LSYMB: 16 / 16
Interleave Depth: 1 / 1
Interleave Block: 32 / 32
LPATH: 0 / 0
Line Attenuation (LATN): Down: 10.1dB / Up: 9.3dB
Signal Attenuation (SATN): Down: 10.1dB / Up: 10.5dB
Noise Margin (SNR): Down: 20.0dB / Up: 29.2dB
Aggregate Transmit Power (ACTATP): Down: -12.2dB / Up: 12.7dB
Max. Attainable Data Rate (ATTNDR): Down: 82.487 Mb/s / Up: 52.455 Mb/s
Forward Error Correction Seconds (FECS): Near: 0 / Far: 57
Errored seconds (ES): Near: 0 / Far: 27
Severely Errored Seconds (SES): Near: 0 / Far: 18
Loss of Signal Seconds (LOSS): Near: 0 / Far: 18
Unavailable Seconds (UAS): Near: 75 / Far: 75
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
15m Code Violations: 0 / 0
15m FEC Errors: 0 / 0
1d Code Violations: 0 / 80
1d FEC Errors: 0 / 57
-
I'm trying to get a DSL driver out of the Fritz-Box7490 firmware:
7z e FRITZ.Box_7490.en-de-es-it-fr-pl.113.06.53.image -r filesystem.image
7z e filesystem.image filesystem_core.squashfs
unsquashfs4-lzma-avm-be filesystem_core.squashfs -e lib / modules / dsp_vr9 /
Please tell me how to unpack filesystem_core.squashfs?
When executing the command:
unsquashfs4-lzma-avm-be filesystem_core.squashfs -e lib / modules / dsp_vr9 /
I get a message:
bash: unsquashfs4-lzma-avm-be: command not found
System:
Linux HPLINUX 4.9.0-4-amd64 # 1 SMP Debian 4.9.65-3 (2017-12-03) x86_64 GNU / Linux
p7zip version 16.02
Thank you.
-
Please tell me how to unpack filesystem_core.squashfs?
When executing the command:
unsquashfs4-lzma-avm-be filesystem_core.squashfs -e lib / modules / dsp_vr9 /
I get a message:
bash: unsquashfs4-lzma-avm-be: command not found
System:
Linux HPLINUX 4.9.0-4-amd64 # 1 SMP Debian 4.9.65-3 (2017-12-03) x86_64 GNU / Linux
p7zip version 16.02
Thank you.
Download and compile freetz tools, clone from https://github.com/Freetz/freetz.git. You only need to 'make tools', unsquashfs4-lzma-avm-be will be in the tools folder. NOTE, you may need to change umask to 0022 in order to compile.
[Moderator edited to remove an invalid link.]
-
It has been a very long time since I've posted on this forum, so hi again.
I have just installed the OpenWRT 18.06 RC1 on an ECI/r v2 modem, it boots fine and I can connect over the ethernet connection, all good so far. What I can't seem to do is get the DSL connection working, rendering the device somewhat useless. My line syncs okay with the ECI /i I have been running for years, but under the ECI /r it just cycles between handshake, full_sync, exception, idle request and silent. I'm not really sure what is going on. It did sync once, just after installing OpenWRT, having configured the VDSL settings but without a reboot, since, nothing. Is there a sifferent firmware I should be trying? I'm a little confused.
EDIT: Just flashed back it's stock firmware, starting to think I've been sold a brick unfortunately. Even on stock, after a reset, I'm getting the same 0x1 exception line state :(
EDIT2: Hm no, my bad. On stock it didn't work initially but after doing a reset with the button on the back it appears to sync up. Then switching back to OpenWRT broke it. Does 18.06 actually work on this device?
-
fwiw, I had OpenWRT 18.06 Snapshot working fine on an ECI/r v2 modem when I briefly tested it last month. I haven't tried RC1 or RC2 though which shouldn't be any different imho.
Are you sure you configured OpenWRT correctly?
I used the Bridge modem LuCI setup instructions found in the 'Install guide for HH5A'.
https://openwrt.ebilan.co.uk/viewtopic.php?f=7&t=266 (https://openwrt.ebilan.co.uk/viewtopic.php?f=7&t=266)
Have you tried LEDE 17.01.4 which also works just fine?
(I notice 18.06 allows you to adjust the downstream noise margin in LuCI, but I've not test it as I get full line sync speed)
-
Hello, I am quite confused right now.
I've got the UART connected, i am pretty certain I have a V1.2. I've got my PC configured using a usb ethernet adapter as 192.168.1.1.
I am not too sure how to set up TFTP on windows but I think it's fine as it has the correct IP.
The main issue is it says this:
Using vr9 Switch device
TFTP from server 192.168.1.1; our IP address is 192.168.1.100
Filename 'openwrt-lantiq-xrx200-VG3503J_V2-squashfs.image'.
Load address: 0x81000000
Loading: T T T T T
and when I ping 192.168.1.1 (my PC) it times out from the modem:
VR9 # ping 192.168.1.1
Using vr9 Switch device
ping failed; host 192.168.1.1 is not alive
The Lan1 light is on but the ethernet lights are not but windows recognises it being there.
any help?
Is it somehow bricked? If so, how can I reverse this.
-
Some suggestions.
Edit: use 'server' mode in TFTPD, not 'client' mode.
Whenever I have used TFTPD32/64 in Windows, try placing the VG3503J file in the same program folder as TFTPD*.exe. Also check the Windows Firewall settings are not blocking the server.
Try a different PC/laptop with a built in ethernet LAN port.
If you are not sure if you have a v1 or v2 modem, there are some internal pics of the Lantiq SoC here
https://openwrt.org/toh/bt/vg3503j (https://openwrt.org/toh/bt/vg3503j)
-
Hi,
The large chip is a Lanti(a/q) V1.2
I've even tried the internal ethernet port and tried following the steps on OpenWRT.org. When doing so I was able to ping the modem from the PC but not the other way around. It still will not grab the TFTP file.
Not sure if it matters, but when it boots it says "ping failed; host 1.1.1.1 is not alive" and could it be an issue that mine seems like it is already erased or something where in the guides they are starting with the existing firmware fully running?
-
TBH, I don't know if the ping command actually works from VR9 prompt, or whether your Windows firewall is blocking replies to pings. Unfortunately, I can't check ping on an ECI modem.
Unless you got as far as executing the 'Erase' command, I think the original ECI firmware is still intact.
Referring to the upgrading from OpenWRT CC15 to LEDE steps in the OpenWRT wiki, I wonder if these commands would be sufficient to reinstate booting the original ECI firmware?
run reset_uboot_config
reset
setenv ethaddr AA:BB:CC:DD:EE:FF (use MAC address printed on back of modem)
saveenv
-
If I let it boot it says:
Abort
ping failed; host 1.1.1.1 is not alive
Hit any key to stop autoboot: 0
## Checking CFG Image at b07c0000 ...
## Check Primary System Image ...
## Primary System Image Checksum Error !!
## Check Secondary System Image ...
## Secondary System Image Checksum Error !!
## Both Images Corrupted: Please contact with your vendor ##
I will try another PC now. But just to make sure is this how I am meant to setup TFTP (i'm using the OpenWRT link in this test) do I press put? https://imgur.com/sRFOaos
Hang on, I used TFTP server with windows firewall and any possible conflicting program uninstalled. Renamed the newest lede file to match what i had pasted and it seems to be working so far me thinks. Maybe it actually was the damn firewall? It's taking its time at 1350bytes/sec so I'll feedback if it works.
-
I amended my earlier reply before I realised you had posted a response, but sounds like you have got TFTPD working.
The TFTP transfer should be completed in mere seconds. I vaguely recall when I encountered TFTP taking an eternity to transfer on one occasion, the installation subsequently failed. I can't remember what I did afterwards, but I did successfully install LEDE 17.01.4 by trying again and the TFTP transfer was completed in seconds.
Note that install steps for LEDE 17.01.4 ARE DIFFERENT To OpenWRT CC15 (Jsamuel).
ie. I wouldn't like to say what would happen if you used LEDE file by using the instructions for old Chaos Calmer..... LEDE probably won't boot.
-
hm, I am using the LEDE 17 firmware and following those steps However, i am using a TFTP Server I think. It's found the file ending with .bin and is transferring but at bytes/sec. Is it better just to halt it right now?
-
hmm, I think I've always left both 'server' and 'client' enabled in TFTPD settings.
I think you could be right, it should be using TFTP server, not client. Please disregard my comments about configuring TFTPD client. Sorry for the confusion.
No changes will be made until you execute the Erase command.
-
Hmmm, still not sure why it is going at bytes/sec. I have had to leave the house and even though I have USB Wi-Fi plugged in teamviewer is offline - guess it is using the wrong NIC? So I'll have to wait until I return to see if it has worked.
If this hopefully works I can just access LEDE normally and follow some guide for setting up VDSL? Is there a noticeable reduction in sync speed by using this firmware?
-
fwiw, is 192.168.2.1 selected under 'Server interfaces' in TFTPD?
I can't think of any other reason why the transfer is so slow.
As the original ECI firmware is locked, it is difficult to compare sync speeds, but based on speed tests, I've not personally observed much difference to cause concern.
yes, you can use the LEDE install guide for Home Hub 5A to help configure VDSL connection accordingly. I've only used the modem in 'bridge mode' because I understand the performance may not be very good in 'router' mode.
Reminder the two LAN ports are transposed when viewed in switch menu in LuCI in 17.01.4.
-
Also to note that I was able to get both WAN and LAN over the one cable by tagging both VLAN 1 & 2 on LAN1 and doing the same on my LEDE Router's WAN port. (where VLAN 1 is my LAN, VLAN 2 contains WAN & VLAN 3 is my Guest network but is off for this port). Then on my router under DHCP I set a random hex value due to Sky requirements and everything works fine.
-
I've been experimenting with the various firmware at: https://xdarklight.github.io/lantiq-xdsl-firmware-info/ with my HH5A
With the standard openwrt firmware I can get 17-20 down and 3-4Mbps up. I then tried the various DM200 firmwares as they include vectoring support (not sure whether the local DSLAM supports it as I haven't yet identified it - though have found the PCP).
With the firmware from the V34 or V52 of the bundle (5.8.1.5.0.7 and 5.7.11.5.0.7 respectively) I get 24-27Mbps down and 1Mbps upm with the firmware from the V36 GPL bundle (5.7.9.5.1.7) I get something more akin to the stock openwrt firmware.
I don't see evidence of vectoring being used in any case - so I assume that my local DSLAM doesn't support it?
-
I've been experimenting with the various firmware at: https://xdarklight.github.io/lantiq-xdsl-firmware-info/ with my HH5A
I don't see evidence of vectoring being used in any case - so I assume that my local DSLAM doesn't support it?
You should see Vectoring on the openwrt status page: https://code.dopame.me/veonik/openwrt-mirror/commit/ec1b121769a4095a76321e9317faf1e803e101d0
if [ $((xtse8 & 7)) != 0 ]; then
- line_mode_s="$line_mode_s G.993.2 (VDSL2),"
+ dsmsg=$(dsl_cmd dsmsg)
+ vector_s=$(dsl_val "$dsmsg" eVectorStatus)
+
+ case "$vector_s" in
+ "0") line_mode_s="$line_mode_s G.993.2 (VDSL2)," ;;
+ "1") line_mode_s="$line_mode_s G.993.5 (VDSL2 with downstream vectoring)," ;;
+ "2") line_mode_s="$line_mode_s G.993.5 (VDSL2 with down- and upstream vectoring)," ;;
+ *) line_mode_s="$line_mode_s unknown," ;;
-
not sure whether the local DSLAM supports it as I haven't yet identified it - though have found the PCP
You can find your cabinet location, DSLAM model, and even if it is a BDUK funded cabinet, by using this guide:
https://forum.kitz.co.uk/index.php/topic,15409.0.html
Vectoring is only deployed on a small number of BDUK funded Huawei cabinets.
It isn't available on any ECI cabinets.
If you found the PCP you could also compare the DSLAM's cabinet to the photos on kitz FTTC cabinets page.
https://kitz.co.uk/adsl/fttc-cabinets.htm#fttc_street_cabinet
The DSLAM will be within 100m of the PCP, usually much closer.
-
I've been experimenting with the various firmware at: https://xdarklight.github.io/lantiq-xdsl-firmware-info/ with my HH5A
With the standard openwrt firmware I can get 17-20 down and 3-4Mbps up. I then tried the various DM200 firmwares as they include vectoring support (not sure whether the local DSLAM supports it as I haven't yet identified it - though have found the PCP).
With the firmware from the V34 or V52 of the bundle (5.8.1.5.0.7 and 5.7.11.5.0.7 respectively) I get 24-27Mbps down and 1Mbps upm with the firmware from the V36 GPL bundle (5.7.9.5.1.7) I get something more akin to the stock openwrt firmware.
I don't see evidence of vectoring being used in any case - so I assume that my local DSLAM doesn't support it?
I'm using 5.7.B.5.0.7-5.7.5.4.0.1 from the dm200 firmware v61
-
Hello to All,
First post on this brilliant forum.
I use Chaos Calmer r46559 which is the most stable FW (tried latest openwrt 18.06.4- not usable), and modem is rock solid with good connection speed. The only one problem I have is that I can't use eDMT software, I type there my modem address and correct login details and always end up with pop up window "Incorrect credentials" any tips how to make it work?
-
Hi there. I'll be releasing an update with latest OpenWrt in the coming days.
-
What will be in new update? I tested latest openwrt 18.06.4 and modem was so unstable, keep breaking connection, re-sync several times within few hours, internet was so unstable that sometimes impossible to use. Also stats on new openwrt are less detailed and configuration to use in bridge modem (as your recent fw is setup) is so complicated (have to use detailed instruction from Hub 5 found online)..... ??? I'm really scarred to try something based on latest openwrt release.
After few hours I back to stable release and so far happy again, flashing procedure (with opening modem) take just about 5 mins now ;D.
Only problem (if ) is that then I have to flash back ori FW to get openwrt then flash back ori to flash back Chaos Calmer r46559, will be possible to upgrade from current FW without reverting back to stock, or even via Luci, also will there be option to revert back straightaway to previous version or exercises with back to original FW will be necessary?
BTW
Thanks for grate work.
-
Hi. Did you update the modem and firmware to latest version? This will need updated too, perhaps extracted from the latest version of a tplink w9980 or other lantiq based router with an open source firmware (german brand, i can't quite remember) but I'll work on it
Also the stats page is modified on my version which shows more information. You'll need to copy this over.
-
I flash original FW then o top of that OpenWrt 18.06.4, I though in OpenWrt is already latest modem FW.
Also forgot to mention that main reason for latest openwrt FW was ability to tweak SNR which doesn't work for me in bridge mode.
-
Openwrt 19.07 will be the final release for 4mb rom and 32mb ram devices.
https://forum.openwrt.org/t/432-warning-infobox-update/38763 (https://forum.openwrt.org/t/432-warning-infobox-update/38763)
Would anyone be interesting in helping me make a bridge mode firmware for the ECI with the latest g.inp/retx firmware like iamacarpet has done for the netgear dm200?
https://github.com/a1comms/openwrt-netgear-dm200-bridge (https://github.com/a1comms/openwrt-netgear-dm200-bridge)
-
From this what @jsamuel wrote on previous page he already working on latest openwrt. FW from first post is fully configured for using in UK so after is flashed to modem is ready to use.
-
Hi there. I'll be releasing an update with latest OpenWrt in the coming days.
Have you seen the replacement of the lzma loader?
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=17094e9e642ffca19c6b6681766d2bcbb8e6e565
Use the new image build code and remove the lzma loader. The lzma
loader was used to cheat the signature validation of the bootloader and
I found another way to do this.
To migrate boards already using LEDE/OpenWrt to the new image the
following steps need to be done once:
VR9 # run reset_uboot_config
VR9 # reset
VR9 # setenv ethaddr AA:BB:CC:DD:EE:FF
VR9 # setenv preboot ping 1.1.1.1\;bootm 0xb001f000
VR9 # saveenv
VR9 # tftp 0x81000000 lede-lantiq-xrx200-VG3503J-squashfs-sysupgrade.bin
VR9 # erase 0xb0020000 $(filesize)
VR9 # cp.b 0x81000000 0xb0020000 $(filesize)
The mac address is printed on the label at the bottom of the case.
The following steps are need to be done during first install:
VR9 # setenv preboot ping 1.1.1.1\;bootm 0xb001f000
VR9 # saveenv
VR9 # tftp 0x81000000 lede-lantiq-xrx200-VG3503J-squashfs-sysupgrade.bin
VR9 # erase 0xb0020000 $(filesize)
VR9 # cp.b 0x81000000 0xb0020000 $(filesize)
The image uses the uImage firmware splitter now instead of hardcoded
kernel and rootfs partitions. The firmware partition size was extended
to use flash space that was reserved for partitions required only by
the ECI firmware.
Due to the changes an upgrade to a later LEDE revision from a running
LEDE is supported now.
A default switch config was added and the device uses the same MAC
addresses as the ECI firmware now instead of the same for all VG3503J.
-
From this what @jsamuel wrote on previous page he already working on latest openwrt. FW from first post is fully configured for using in UK so after is flashed to modem is ready to use.
any idea how to build from the packages?
-
Hi @jsamuel
Is there any news when/if new version will be available for eci modem?
-
sorry i did not get round to this :( i no longer have vdsl and went with virgin as soon as they dug up my street and would be unable to do further testing of new firmware however I'll keep everything here and also the files on the website
-
No worries, thanks for great work.
-
Hi All,
Does anyone remember commands for adjusting snr on eci modem with chaos Calmer fw? I had somewhere commands but lost them ???
-
I have the V1 model, is this image better to use for me on talktalk than say the latest compatible version on openwrt ?
-
would it be a tall order for someone to update this firmware with the latest openwrt ?
-
You can try latest openwrt 19.07 on it but you definitely need to configure switch for vlan if you want to use it as bridge modem, also the stats page is less detailed than in this fw. When I tried version 18.06 it was very unstable but I didn't change anything apart of set up vlan switch, then I find out that vdsl fw on openwrt may not be the latest version and is actually necessary to upgrade it to proper one. Due to instability on 18.06 I go back to this one as is rock solid.
-
You can try latest openwrt 19.07 on it but you definitely need to configure switch for vlan if you want to use it as bridge modem, also the stats page is less detailed than in this fw. When I tried version 18.06 it was very unstable but I didn't change anything apart of set up vlan switch, then I find out that vdsl fw on openwrt may not be the latest version and is actually necessary to upgrade it to proper one. Due to instability on 18.06 I go back to this one as is rock solid.
Yes the newer versions are a lot more laggy i hear. So is LEDE a different version of openwrt or are they the same thing ?, i want to get a few of these modems and knock them out but want to know what is best to install, im being advised not to use older third party firmware, my idea is that i or others can use this on talktalk or the like and then use it as a pure modem so you can utilise your own router. when you say bridge mode, does that refer to openWrt/LEDE installation guide for HH5A for the later firmwares but doesnt need to be done with this version ?....very inforamtive quote below from a reply on the openwrt forum, the poster really cleared things up for me but want to know how you feel about using the older firmware on these modems...
The JSamuel version on kitz forum is indeed a custom version based on very old version of Openwrt 15 chaos calmer. It contains modified code which also offers more DSL statistics in LuCI web interface not found in current OpenWrt/LEDE. But it does not include any patches for xrx200 Lantiq chipset introduced since 2015. JSamuel doesn't provide any support and recent posts suggest there are no plans to update it as OP is now on cable broadband.
The openwrt wikipage was last updated in 2018 when LEDE 17.01.4 was the current version at the time (17.01.6 was last official stable version). It also requires you to complete the instructions for setting up 'bridge' mode described in section 9.8 within OpenWrt/LEDE installation guide for HH5A.
There is nothing stopping you installing LEDE 17.01.4 now as per wiki page, and later choosing to upgrade to LEDE 17.01.6, OpenWrt 18 or 19 using LuCI web UI btw. Otherwise, if you wish to go straight to OpenWrt 19, then you simply have to substitute the lede-17.01.4-lantiq-xrx200-VG3503J-squashfs-sysupgrade.bin with openwrt-19.07.0-lantiq-xrx200-arcadyan_vg3503j-squashfs-sysupgrade.bin for example when following the wiki instructions. As OpenWrt 19 stable has only recently been announced, I'd personally use proven OpenWrt 18.06.4 or LEDE 17.01.6 releases.
With regards to LAN1/LAN2 being transposed in LEDE 17, it is just a cosmetic bug. It does not mean you MUST use OpenWrt 18 or 19.
penWrt/LEDE installation guide for HH5A
-
Bridge mode is when eci modem working purely as modem and your username and password came from router to modem for connection authentication.
This fw is maybe old but is nothing wrong with it, vdsl fw support g.inp where possible, and other types of connection. This fw is dedicated to use in UK as there are pre set wan bridges. I tried newer version 18.06 and also on different modem I tried 19.07, apart of newer kernel and fresh packages in 19.07 there is no more futures than in this fw. If you will use this modem in bridge mode all firewall stuff will be done by your router so there is no big issues if some packages are outdated (in my opinion). Also bear in mind that this particular fw was tweaked for use on eci modem and is really damn stable. If you planing to use eci bt modem this is the best way for it. Of course you can try newest Openwrt but you will came back to this one at the end as I did. Don't buy bulk quantity, get one eci modem flash this fw and see yourself if it suit you.
-
would it be a tall order for someone to update this firmware with the latest openwrt ?
not really, I have two v-2fub/r Rev B versions already flashed to openwrt.
I just need to convert @jsamuels work so it is compatible with the openwrt imagebuilder, in it's current format you need to sync the repository, when you should just be able to drop a files package into imagebuilder.
-
not really, I have two v-2fub/r Rev B versions already flashed to openwrt.
I just need to convert @jsamuels work so it is compatible with the openwrt imagebuilder, in it's current format you need to sync the repository, when you should just be able to drop a files package into imagebuilder.
Does Openwrt actually have the modem firmware? The Wiki suggested the modem firmware is not included due to it being copyrighted.
Also, did you compare if sync is different between stock and Openwrt?
-
Does Openwrt actually have the modem firmware? The Wiki suggested the modem firmware is not included due to it being copyrighted.
Also, did you compare if sync is different between stock and Openwrt?
Openwrt sources of modem firmware
http://mirror2.openwrt.org/sources/dsl_vr9_firmware_xdsl-05.07.03.03.00.06_05.07.01.0C.00.02_osc.tar.gz
http://mirror2.openwrt.org/sources/dsl_vr9_firmware_xdsl-05.08.01.08.01.06_05.08.00.0B.01.01_osc.tar.gz
It's included, though the latest is 5.9.1.4.0.7
No difference in sync between stock eci and stock openwrt
-
Openwrt sources of modem firmware
http://mirror2.openwrt.org/sources/dsl_vr9_firmware_xdsl-05.07.03.03.00.06_05.07.01.0C.00.02_osc.tar.gz
http://mirror2.openwrt.org/sources/dsl_vr9_firmware_xdsl-05.08.01.08.01.06_05.08.00.0B.01.01_osc.tar.gz
It's included, though the latest is 5.9.1.4.0.7
No difference in sync between stock eci and stock openwrt
Is that basically identical to the HH5A? The number seems to match the latter.
rw-r--r-- 1 root root 898952 Jan 6 16:47 xcpe_581816_580B11.bin
-rw-r--r-- 1 root root 253635 Jan 6 16:47 xcpe_581816_580B11_to_579906_574402.bspatch
Also, any idea what that patch is about?
-
patch for fw is: /lib/firmware
-
Is that basically identical to the HH5A? The number seems to match the latter.
rw-r--r-- 1 root root 898952 Jan 6 16:47 xcpe_581816_580B11.bin
-rw-r--r-- 1 root root 253635 Jan 6 16:47 xcpe_581816_580B11_to_579906_574402.bspatch
Also, any idea what that patch is about?
Patch is for annex a to annex b
-
Hi, all!
How to get access to that Resyncs counter through dsl_cpe_control utility?
-
Hi, all!
How to get access to that Resyncs counter through dsl_cpe_control utility?
Hi,
It's ran from this script: https://vanquishsolutions.co.uk/openwrt/VG3503J/files/lib/functions/
-
I have unlocked my ECI modem, installed the firmware from JSamuel and attempting to add the modem as a node to my new munin server but it does not show up in the web GUI with the other server node after adding to the munin.conf on server.
[MuninMaster.lan]
address 127.0.0.1
use_node_name yes
[ECI-Modem.lan]
address 192.168.2.251
user_node_name yes
I have netcat the modem and got positive responses to the plugins and version of muninlite, I have also observed the temp file 'dsl.txt' being created and updated in the modem filesystem.
# munin node at ECI-Modem.lan
list
cpu load memory processes uptime irqstats xdsl_speeds xdsl_errors xdsl_line_att xdsl_noise xdsl_tran_pwr
version
munins node on ECI-Modem.lan version: 1.0.4 (munin-lite)
quit
I cannot ascertain what else is needed from looking at the example server VM posted by JSamuel, can anyone clarify additional config required? I will note I am yet to connect the DSL and LAN1 ports of the modem as my current setup is still in situ, although I struggle to see how this could be a cause.
Thanks and take care,
Alex.
-
I have unlocked my ECI modem, installed the firmware from JSamuel and attempting to add the modem as a node to my new munin server but it does not show up in the web GUI with the other server node after adding to the munin.conf on server.
[MuninMaster.lan]
address 127.0.0.1
use_node_name yes
[ECI-Modem.lan]
address 192.168.2.251
user_node_name yes
I have netcat the modem and got positive responses to the plugins and version of muninlite, I have also observed the temp file 'dsl.txt' being created and updated in the modem filesystem.
# munin node at ECI-Modem.lan
list
cpu load memory processes uptime irqstats xdsl_speeds xdsl_errors xdsl_line_att xdsl_noise xdsl_tran_pwr
version
munins node on ECI-Modem.lan version: 1.0.4 (munin-lite)
quit
I cannot ascertain what else is needed from looking at the example server VM posted by JSamuel, can anyone clarify additional config required? I will note I am yet to connect the DSL and LAN1 ports of the modem as my current setup is still in situ, although I struggle to see how this could be a cause.
Thanks and take care,
Alex.
It appears the issue was caused by my foolishness of including "user_node_name yes" variable on the modem node in munin.conf. May others learn by my mistake.
Regards, Alex.
-
Found a bunch of dsl firmwares here to try with my ECI/r https://cloud.mail.ru/public/4Ljp/2auEVG4kB
-
Tried to update mine to the latest OpenWRT but its not taking it. All goes well until I press Proceed, it reboots, flashed the power LED green and amber a few times then boots back into the old firmware.
Guess there's no good reason to use it over the HH5a anyway, I just liked the idea of putting it back on the wall vs the HH5a which constantly tries to fall over from the force of the ethernet cable in the back.
-
Tried to update mine to the latest OpenWRT but its not taking it. All goes well until I press Proceed, it reboots, flashed the power LED green and amber a few times then boots back into the old firmware.
Guess there's no good reason to use it over the HH5a anyway, I just liked the idea of putting it back on the wall vs the HH5a which constantly tries to fall over from the force of the ethernet cable in the back.
https://openwrt.org/toh/bt/vg3503j
Chaos Calmer is v15, to upgrade to version 17 or later:
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=17094e9e642ffca19c6b6681766d2bcbb8e6e565
use the new image build code and remove the lzma loader. The lzma
loader was used to cheat the signature validation of the bootloader and
I found another way to do this.
To migrate boards already using LEDE/OpenWrt to the new image the
following steps need to be done once:
VR9 # run reset_uboot_config
VR9 # reset
VR9 # setenv ethaddr AA:BB:CC:DD:EE:FF
VR9 # setenv preboot ping 1.1.1.1\;bootm 0xb001f000
VR9 # saveenv
VR9 # tftp 0x81000000 lede-lantiq-xrx200-VG3503J-squashfs-sysupgrade.bin
VR9 # erase 0xb0020000 $(filesize)
VR9 # cp.b 0x81000000 0xb0020000 $(filesize)
The mac address is printed on the label at the bottom of the case.
The following steps are need to be done during first install:
VR9 # setenv preboot ping 1.1.1.1\;bootm 0xb001f000
VR9 # saveenv
VR9 # tftp 0x81000000 lede-lantiq-xrx200-VG3503J-squashfs-sysupgrade.bin
VR9 # erase 0xb0020000 $(filesize)
VR9 # cp.b 0x81000000 0xb0020000 $(filesize)
The image uses the uImage firmware splitter now instead of hardcoded
kernel and rootfs partitions. The firmware partition size was extended
to use flash space that was reserved for partitions required only by
the ECI firmware.
Due to the changes an upgrade to a later LEDE revision from a running
LEDE is supported now.
A default switch config was added and the device uses the same MAC
addresses as the ECI firmware now instead of the same for all VG3503J.
You may need to grab a serial cable ;)
-
Well I did end up having to use this again as my Plusnet Hub is no longer able to sync for some reason.
Seems more trouble than its worth to upgrade the firmware, guess I should just leave it alone and impatiently await FTTP.
-
Upgraded mine to 19.07.7
Off to learn the new switch interface :-\
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '2 4 6t'
looking at https://openwrt.org/toh/bt/homehub_v5a
lan port1 is tagged 2, lan port2 is tagged4, cpu is 6t.
-
I'd update mine but I think maybe my Plusnet Hub didn't die after all as the HH5a is having the same issue where sometimes it just wont sync on a fresh boot on my Plusnet line and has to be booted again.
-
I'd update mine but I think maybe my Plusnet Hub didn't die after all as the HH5a is having the same issue where sometimes it just wont sync on a fresh boot on my Plusnet line and has to be booted again.
When I had that happen it was because Plusnet had a PPP gateway down - they run them in round robin pairs so it's pot luck which you get at the point of auth. It would either take 50+ attempts to auth or a reboot (or two) to get on. See what your PPPoE logs look like on the device behind the ECI modem, or on it if that's how your setup is laid out.
-
When I had that happen it was because Plusnet had a PPP gateway down - they run them in round robin pairs so it's pot luck which you get at the point of auth. It would either take 50+ attempts to auth or a reboot (or two) to get on. See what your PPPoE logs look like on the device behind the ECI modem, or on it if that's how your setup is laid out.
No its actual sync that is failing, I suspect a G.INP bug or OpenWRT issue. Once it comes up, its fine and even if it drops so far it comes back fine, its just after initial power up.
-
Has anyone had any luck updating jsamuels 15.05 build to something newer like 19.07 or even 21.02? Or a similarly configured custom build with out the box support for bridge mode?
Upgraded mine to 19.07.7
Off to learn the new switch interface :-\
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '2 4 6t'
looking at https://openwrt.org/toh/bt/homehub_v5a
lan port1 is tagged 2, lan port2 is tagged4, cpu is 6t.
meritez, any builds you can share?
-
This device is NOT RECOMMENDED for future use with OpenWrt due to low flash/ram.
-
This device is NOT RECOMMENDED for future use with OpenWrt due to low flash/ram.
I believe that the 8MB flash is large enough for the 21.02 build and surely using the device purely as a bridge mode modem would result in lower memory usage than using it as a full router? Probably could remove some unused packages to make a modem only image specifically for bridge mode as well.
I think the main changes in jsamuels 15.05 builds are just the preconfigured configs for bridge mode, improved stats and the included config for Munin?
-
This device is NOT RECOMMENDED for future use with OpenWrt due to low flash/ram.
I agree.
Newer versions are quite bloated compared to CC, I've tried and it's rather sluggish. But CC seems stable enough so I haven't bothered to slim it down and release an update
-
I agree.
Newer versions are quite bloated compared to CC, I've tried and it's rather sluggish. But CC seems stable enough so I haven't bothered to slim it down and release an update
Plus there actually is still an official image anyway https://firmware-selector.openwrt.org/?version=21.02.0&target=lantiq%2Fxrx200&id=arcadyan_vg3503j The problem is you can't flash from 15.05 to newer firmwares without doing it from serial again which is a pain.
Plus the HomeHub5a are quite cheap and get you the same chipset that does comfortably handle current releases. Of course the drawback is they can't be wall mounted.
I went back to my ECI for a while as I thought my Plusnet Hub had died, but it turns out that line is just a bit odd as it doesn't always sync on first boot.
But overall, I notice no actual difference in performance between the ECI on 15.05 and the HH5A on 21.02, other than the UI responds quicker on the HH5A and there's space to install other software.
-
Has anyone had any luck updating jsamuels 15.05 build to something newer like 19.07 or even 21.02? Or a similarly configured custom build with out the box support for bridge mode?
meritez, any builds you can share?
I've had no luck updating jsamuels build as every device using this build is given the same MAC address, which gives further complications.
If you're willing to attach a serial cable and fix the bootloader issue, 19.07.8 runs fine and a custom bridge mode image can be built using the openwrt imagebuilder for lantiq which is suitable for ADSL and VDSL.
I'm ignoring 21.02 until the DSA merge that replaces switchconfig is introduced.
To run openwrt comfortably, it's going to be worth removing the web interface going forward as there's no need in bridge mode.
-
I've had no luck updating jsamuels build as every device using this build is given the same MAC address, which gives further complications.
If you're willing to attach a serial cable and fix the bootloader issue, 19.07.8 runs fine and a custom bridge mode image can be built using the openwrt imagebuilder for lantiq which is suitable for ADSL and VDSL.
I'm ignoring 21.02 until the DSA merge that replaces switchconfig is introduced.
To run openwrt comfortably, it's going to be worth removing the web interface going forward as there's no need in bridge mode.
Yeah totally happy to attach the serial cable and go through the reflash. How would I go about building an image using the imagebuilder that is pre configured for bridge mode? I need to include the "network" file pre configured in the image right?
-
@jaimbo welcome to Kitz forum by the way.
I used the following as a guide : https://github.com/rcannizzaro/openwrt-netgear-dm200-bridge
The above is for a Netgear dm200 stripped down to bridge mode, also a lantiq chipset, only differences are 64mb ram and a single ethernet port.
In the if you change the profile in the Build.sh from netgear_dm200 to arcadyan_vg3503j it builds and is flashable to the eci
make image FILES=files/ PROFILE=arcadyan_vg3503j PACKAGES="-dsl-vrx200-firmware-xdsl-a -dsl-vrx200-firmware-xdsl-b-patch luci-mod-admin-full luci-app-statistics collectd-mod-uptime luci-proto-ipv6 luci-proto-ppp luci-theme-bootstrap uhttpd"
That's what I'm working with, there's also network files to adjust.
-
@jaimbo welcome to Kitz forum by the way.
I used the following as a guide : https://github.com/rcannizzaro/openwrt-netgear-dm200-bridge
The above is for a Netgear dm200 stripped down to bridge mode, also a lantiq chipset, only differences are 64mb ram and a single ethernet port.
In the if you change the profile in the Build.sh from netgear_dm200 to arcadyan_vg3503j it builds and is flashable to the eci
make image FILES=files/ PROFILE=arcadyan_vg3503j PACKAGES="-dsl-vrx200-firmware-xdsl-a -dsl-vrx200-firmware-xdsl-b-patch luci-mod-admin-full luci-app-statistics collectd-mod-uptime luci-proto-ipv6 luci-proto-ppp luci-theme-bootstrap uhttpd"
That's what I'm working with, there's also network files to adjust.
Thanks for the welcome :)
So I tried as you suggested, used the files in that github repo, slightly modified to change the IP addresses of the network file to match my IP ranges so I could access the UI etc. (Changed "option ipaddr" for "config interface mgmt" to an IP within my range)
Managed to flash using the instructions here: https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=17094e9e642ffca19c6b6681766d2bcbb8e6e565 (though the instructions in that post are slightly wrong, the command "erase 0xb0020000 $(filesize)" should actually be "erase 0xb0020000 +$(filesize)", but figured that out and got there in the end)
Could see the OpenWrt boot process through the serial console and it looked okay to me. LAN1 stopped working, LAN2 appeared to be working, but no matter what I tried, I couldn't connect to LUCI and just leaving everything plugged in as it should be, the line never seemed to connect :( (Also either the power LED or DSL LED was flashing green at the time)
Anything you can think that I am missing? Back on jsamuels build for the time being, but would like to give a newer builld another try!
-
Other than being bloated, is there any reason not to use the official OpenWRT images?
-
Other than being bloated, is there any reason not to use the official OpenWRT images?
they're often just generic autobuilds with mismatching firmware and never actually checked by a person. If it worked properly I'd be surprised.
-
they're often just generic autobuilds with mismatching firmware and never actually checked by a person. If it worked properly I'd be surprised.
Might have to give it a try seeing as I'm not using it right now. Just not 100% where my USB serial adapter is.
-
Took another crack at things today with a fresh head and managed to get a 19.07.8 build with out of the box bridge mode working. Seems to be working well and my "Max. Attainable Data Rate (ATTNDR)" has gone up from about 79-81Mb ish to currently 91Mb, but my rate is still at 66Mb. I don't fully understand exactly what this implies but it still seems to be an improvement over the previous build.
(https://i.imgur.com/MdEXmsX.png)
Will see how stable things are over the next few days, but I am hopefull! :)
Will also do some more digging on default included packages etc. and see if I can trim some packages to save some space/RAM. Happy to share the image and instructions to flash if anyone wants them :)
-
Took another crack at things today with a fresh head and managed to get a 19.07.8 build with out of the box bridge mode working. Seems to be working well and my "Max. Attainable Data Rate (ATTNDR)" has gone up from about 79-81Mb ish to currently 91Mb, but my rate is still at 66Mb. I don't fully understand exactly what this implies but it still seems to be an improvement over the previous build.
(https://i.imgur.com/MdEXmsX.png)
Will see how stable things are over the next few days, but I am hopefull! :)
Will also do some more digging on default included packages etc. and see if I can trim some packages to save some space/RAM. Happy to share the image and instructions to flash if anyone wants them :)
Did you perhaps accidentally set the SNRm offset? The attainable seems to be based on the modems target SNRm as I can make it REALLY high by setting unrealistic offsets (my lines seem to both be banded so it has zero impact on anything).
Actually I tell a lie, my worse line is banded slightly faster than it can do on 6dB SNRm so I do get some gain. This is with a -3dB offset so targeting 3dBm.
Attain Data Rate: 75.582 Mb/s / 18.493 Mb/s
Actual Data Rate: 66.919 Mb/s / 18.797 Mb/s
Noise Margin: 5.2dB / 6.0dB
-
Your line has been capped (banded) by the DLM.
It won't sync above that figure.
The DLM usually applies banding due to too many resyncs in a short time period.
-
Is the upstream fastpath? Thats not good at all. Errors on the upstream ?
-
Hmm, I am not sure. I have been having quite a lot of issues with my network at the moment (a lot of disconnects and I've been hit by DLM pretty badly). Have an Openreach Engineer coming tomorrow actually!
I decided to get a Home Hub 5 and stick OpenWrt on it for a bit more power so I could install monitoring and other packages on. Pulled this from the CLI DSL metrics in case it answers your question.
(https://i.imgur.com/XjSsJDw.png)
-
Looks like the downstream is capped (banded) with high Interleaving (12ms delay) and the upstream is banded with low Interleaving (8ms delay).
You need to stress to the OpenReach engineer that the line needs a DLM reset AFTER he/she has done any work on the line.
The BT HH5 from the single snapshot of stats looks to perform much worse than the previous modem.
-
Thanks for the advice j0hn. To clarify, the stats from the two screenshots do appear to show the HH5A being worse, but the screenshot from the ECI Modem was from before I started experiencing the line issues.
The line issues started happening about 3 weeks after that screenshot. Part of the reason I bought the HH5A was in case the ECI modem was dying as I really couldn't figure out what was causing my issues. An hour or two into an outtage I decided to test with a few different devices/firmwares and I couldn't get DSL connected at all on either my build of OpenWrt 19.07, jsamuels 15.05 build or even the stock NowTV hub until eventually it started to connect a few hours later. Some mornings the line would drop after 10-15 minutes and wouldn't be back up for like 30-45 mins. It would continue doing this for like 4-5 hours at times, really annoying.
Well at least now with the HH5A I can have fancy graphs for historic stats! :)
(https://i.imgur.com/pyAEmAP.png)
-
Looking further the line attenuation (latn) reported by both modems is very similar at 10.1dB and 10.2dB.
The attainable rates (attndr) are dramatically different. They have dropped from 91/24 to 74/15.
The attainable rate is usually exaggerated when Interleaving is enabled but as Interleaving is enabled in both instances it shows the scale of the drop.
Such a drop in the lines potential can be from a physical fault but it can simply be due to crosstalk (interference from new subscribers lines that run alongside your line in the main cable bundles).
Such large drops in attainable due to crosstalk are all too common unfortunately.
Hopefully the engineer finds a physical fault on the line somewhere and fixes the cause of the disconnections. With a DLM reset on top the sync rates should improve considerably.
-
Fingers crossed, will update tomorrow morning after I speak to the engineer.
Any information you suggest I have ready for the engineer? Anything I should to do to prepare to make things as easy as possible for them to find the problem?
-
So the engineer came around yesterday and potentially identified some internal issues with the wiring of the master socket and extension which he resolved and then done a bunch of tests with his tester which apparently all passed.
Then double checked that my modem could still get sync, I pointed out that there were still errors on the upstream which he said he "wasn't worried about" and he was only worried about errors on the downstream? After that he done a DLM reset which has left me with this:
(https://i.imgur.com/VTDLuPb.png)
(https://i.imgur.com/16hdrKX.png)
(https://www.speedtest.net/result/12258294893.png)
Very happy with these speeds. Fingers crossed I don't see more instability and get hit by DLM!
-
Just an FYI. The upstream ES/SES in your stats are old errors reported by the DSLAM.
They don't reset when the modem is restarted line the downstream does.
It looks like an excellent result. Stability is key now so keep the modem in sync and enjoy the connection.
-
Thanks for the advice j0hn. To clarify, the stats from the two screenshots do appear to show the HH5A being worse, but the screenshot from the ECI Modem was from before I started experiencing the line issues.
The line issues started happening about 3 weeks after that screenshot. Part of the reason I bought the HH5A was in case the ECI modem was dying as I really couldn't figure out what was causing my issues. An hour or two into an outtage I decided to test with a few different devices/firmwares and I couldn't get DSL connected at all on either my build of OpenWrt 19.07, jsamuels 15.05 build or even the stock NowTV hub until eventually it started to connect a few hours later. Some mornings the line would drop after 10-15 minutes and wouldn't be back up for like 30-45 mins. It would continue doing this for like 4-5 hours at times, really annoying.
Well at least now with the HH5A I can have fancy graphs for historic stats! :)
(https://i.imgur.com/pyAEmAP.png)
If you still around? Do you mind posting how you got those graphs working and in which build of OpenWRT, I have worked on the same thing and ended up giving up due to LUA errors.