Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Dabblar]

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 ...

[jsamuel]

...
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'

[jsamuel]

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)

[ejs]

Is the lantiq_dsl.sh script here 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.

[jsamuel]

Is the lantiq_dsl.sh script here 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)

[ejs]

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:

Code: [Select]

~ # /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)


[jsamuel]

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.

[rp00]

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

[jsamuel]

Nice!

Glad BT finally got round to enabling G.INP on ECI cabs.
..Now for upstream. 

[jsamuel]

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

[jsamuel]

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. 

[ejs]

@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.

[rp00]

@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!!!"

[jsamuel]

Code: [Select]

/**
   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..

[ejs]

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.