Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: 1 2 [3] 4

Author Topic: ECI model B-FOCuS V-2FUb/I Rev.B Experiences  (Read 18709 times)

custard

  • Member
  • **
  • Posts: 83
    • Geeky Dentist
Re: ECI model B-FOCuS V-2FUb/I Rev.B Experiences
« Reply #30 on: April 18, 2014, 07:51:06 AM »

My ECI/r turned up yesterday. I soldered up and synced in just after midnight. To my surprise the sync has jumped up another 3mb. This is better than I have ever seen on my line even with my old ECI/r.

QLN, Hlog and btagent_arc_version getstat are attached.

The getstat command reports there are 2 sets of data for QLN but I still cannot locate upstream.
Logged

Blackeagle

  • Reg Member
  • ***
  • Posts: 257
Re: ECI model B-FOCuS V-2FUb/I Rev.B Experiences
« Reply #31 on: April 18, 2014, 09:49:56 AM »

Thanks Custard, that's very useful.

Hopefully I'll have some time over the weekend to implement some more features.  Currently, the biggest issue I have is that I cannot guarantee that the response read back from the router will actually be what it's meant to be, or indeed, in the case of a 'hanging' cat /var/........  that there will be any response.  I've added a check for 'nLineState=0x801' being returned, which I've found is usually indicative of a hung 'cat' command.  Program now pops up a message box informing the user that there is probably a hanging command which will need manually killing, and then exits.  I've also implemented a timeout for the read routine to try to eliminate a 'no response' situation.  This still needs testing though.

That btagent_arc_version command on the /r returns a nice amount of data in a format that can easily be parsed, so I'll definitely be using that.

I'm aiming to have a stable enough version for you to test with within the week.
Logged
ASCII stupid question, get a stupid ANSI -- TalkTalk Broadband since 2006

custard

  • Member
  • **
  • Posts: 83
    • Geeky Dentist
Re: ECI model B-FOCuS V-2FUb/I Rev.B Experiences
« Reply #32 on: April 18, 2014, 10:16:41 AM »

Can't wait for the program Blackeagle!

Don't know whether using the straight shell commands would be a better idea so as not to have the hung 'cat' processes. Have you tried that?

Telnet on the ECI/r has just stopped working and there was no hung commands at the time. I've just disabled BTAgent and re-enabled telnet via serial...

You seem well versed in programming. Can you provide any pointers on how I would go about installing  a script to disable and re-enable telnet every few hrs? :)
Logged

Blackeagle

  • Reg Member
  • ***
  • Posts: 257
Re: ECI model B-FOCuS V-2FUb/I Rev.B Experiences
« Reply #33 on: April 18, 2014, 12:23:39 PM »

Interesting question actually !!

The command to find and kill the telnet process would be kill `ps | grep [t]elnetd | cut -f3 -d' '`

What this does, is it evaluates the commands between the `` which find the process id, and then return that to kill, which kills it.  ps shows the running processes.  This is piped with | to grep.  That means the output of ps is the input for the grep command which searches for a line containing telnetd and returns that line.  The [t] bit stops it returning its own process as otherwise we would get two lines.  The output of grep is sent (piped) to the cut command which uses a space as a delimiter (-d' ') and returns the third field (-f3) which is the pid (process id).

To restart we just need to type telnetd

Luckily, the ECI has a sleep command, so the full line would be kill `ps | grep [t]elnetd | cut -f3 -d' '` && sleep 2 && telnetd & which will kill telnet, and restart it two seconds later.

We can write a script that uses this line, then sleeps for a period of time and then repeats, thus restarting telnet after a specified period.

Code: [Select]
#!/bin/sh
while true
do
kill `ps | grep [t]elnetd | cut -f3 -d' '`
sleep 2
telnetd
sleep 14400
done

There is a problem though  :(  The router's filesystem is read-only, so it's impossible to create a script.  It is possible though to write the entire thing on one line  ;)

Code: [Select]
while true;do kill `ps | grep [t]elnetd | cut -f3 -d' '`; sleep 2; telnetd; sleep 14400; done
I have tested this, and it works.  You can adjust the timing by altering the second sleep command as required.  The duration is in seconds so 14400 = 4 hours.  You will be logged out immediately on executing the line obviously.  A reboot will necessitate re-entering the line.
Logged
ASCII stupid question, get a stupid ANSI -- TalkTalk Broadband since 2006

HighBeta

  • Reg Member
  • ***
  • Posts: 175
Re: ECI model B-FOCuS V-2FUb/I Rev.B Experiences
« Reply #34 on: April 18, 2014, 02:39:12 PM »

Have enjoyed this thread immensely.

Do remember Asbo highlighting this with the eci/r if it means anything. (not really my area)  :-[
Code: [Select]
# Enable Telnet Daemon
TELNETD_PID=`ps | grep telnetd | grep -v grep |
if [ "$TELNETD_PID" != "" ]; then
kill -9 $TELNETD_PID
fi
util_hkr_mgr msleep 500

/usr/sbin/telnetd 2>&1 &
util_hkr_mgr msleep 500
TELNETD_PID=`ps | grep telnetd | grep -v grep | cut -b 1-5`
echo "Start telnet service (pid :$TELNETD_PID)" > /dev/console
else
echo "Usage : $0 0/1" > /dev/console
exit 1
fi

I'll see if I can find the reference again.

Thanks guys
Logged

Blackeagle

  • Reg Member
  • ***
  • Posts: 257
Re: ECI model B-FOCuS V-2FUb/I Rev.B Experiences
« Reply #35 on: April 18, 2014, 06:53:31 PM »

Hi HighBeta, glad you are enjoying it.  The code you posted looks to me like a built in script on the ECI.

The grep telnetd | grep -v grep bit means search for a line containing the text telnetd
As it stands, this will return 2 lines.  One will be the actual telnetd process, the other will be the 'grep telnetd' process. The grep -v grep part means 'search for lines containing grep, and return the ones that don't'.(Normally grep searches for the text supplied and returns matching lines.  The -v flag tells it to invert this and return lines that don't match).
This will clearly just return the line containing the actual telnetd process.

IMHO grep [t]elnetd is a neater solution, requiring just the one command.  I'm not exactly clear as to why this works, I just know it does.  Others with more Linux experience than me may be able to clarify why it just returns the one line (.....thinks B*cat or Roseway).

Logged
ASCII stupid question, get a stupid ANSI -- TalkTalk Broadband since 2006

HighBeta

  • Reg Member
  • ***
  • Posts: 175
Re: ECI model B-FOCuS V-2FUb/I Rev.B Experiences
« Reply #36 on: April 18, 2014, 07:15:37 PM »

Yes its part of built in script - I think Asbo was pointing it might be the issue causing the lock ups (?)
I can seem to find the post- A lot of his image pics have expired unfortunately. {I keep looking thought)

Shame Luci web* can not  be easy put on with all the openwrt stuff on there.

Back to lurking now :-[ and let the heavy weight linux guys show how its done  ;)

*Luci's  finnally been  patched for dsl control
http://luci.subsignal.org/trac/ticket/620
« Last Edit: April 19, 2014, 03:16:03 AM by HighBeta »
Logged

Blackeagle

  • Reg Member
  • ***
  • Posts: 257
Re: ECI model B-FOCuS V-2FUb/I Rev.B Experiences
« Reply #37 on: April 18, 2014, 07:22:04 PM »

Can't really see that causing lock up's, but anythings possible !!

I think Asbo ultimately decided it was BTAgent causing lock ups of telnet, and killing the btagent processes restored telnet access.

Luci web.  Whats that ??  OpenWrt implementation ??
Logged
ASCII stupid question, get a stupid ANSI -- TalkTalk Broadband since 2006

custard

  • Member
  • **
  • Posts: 83
    • Geeky Dentist
Re: ECI model B-FOCuS V-2FUb/I Rev.B Experiences
« Reply #38 on: April 18, 2014, 08:34:52 PM »

Wow Blackeagle. Didn't take you long to work that command out! Thank you

There is a problem though  :(  The router's filesystem is read-only, so it's impossible to create a script.  It is possible though to write the entire thing on one line  ;)
Haha, that will save me having to enter each line individually.
I should make you aware that peeps on the ECI/r thread were actually writing to flash as its untouched software would not allow shell access via UART. The idea was to interrupt the boot sequence and use the VR9 switch. I have just checked and this is available on the ECI/I aswell.
http://forum.kitz.co.uk/index.php?topic=11818.msg258001#msg258001
So maybe you might still find a way to add it in permanently! ;)

That problem I reported of losing telnet earlier may have actually not occurred.
At the time I was running EDMT for the stats and it was working great.
But what I have found is that I lose telnet access while it is connected, and I lose EDMT access when telnet is connected. So all that may mean is that only one telnet process at a time will work on the ECI/r.




Logged

custard

  • Member
  • **
  • Posts: 83
    • Geeky Dentist
Re: ECI model B-FOCuS V-2FUb/I Rev.B Experiences
« Reply #39 on: April 19, 2014, 11:42:19 AM »

@Blackeagle - I'm having some difficulty getting the telnet command to work on the ECI/r. I've put the command in but the kill command does not seem to locate the right PID. The log does show that the process is attempting to work though. Also once I restart telnet I cannot see any sign of the grep process in the log.

Nb: I changed the sleep times for testing puposes.
Code: [Select]
IFX CPE login: admin
Password:


BusyBox v1.00 (2012.05.25-03:37+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

# ps
  PID  Uid     VmSize Stat Command
    1 root        440 S   init
    2 root            SWN [ksoftirqd/0]
    3 root            SW  [watchdog/0]
    4 root            SW< [events/0]
    5 root            SW< [khelper]
    6 root            SW< [kthread]
   26 root            SW< [kblockd/0]
   39 root            SW  [pdflush]
   40 root            SW  [pdflush]
   41 root            SW< [kswapd0]
   42 root            SW< [aio/0]
   76 root            SW  [mtdblockd]
 1329 root        592 S   /opt/lantiq/bin/dsl_cpe_control -i05_01_04_00_04_01_0
 1330 root        592 S   /opt/lantiq/bin/dsl_cpe_control -i05_01_04_00_04_01_0
 1332 root        592 S   /opt/lantiq/bin/dsl_cpe_control -i05_01_04_00_04_01_0
 1335 root        592 S   /opt/lantiq/bin/dsl_cpe_control -i05_01_04_00_04_01_0
 1336 root        592 S   /opt/lantiq/bin/dsl_cpe_control -i05_01_04_00_04_01_0
 1364 root            SW  [autbtex]
 1365 root            SW  [pmex_ne]
 1366 root            SW  [pmex_fe]
 2100 root        368 S   /sbin/syslogd -s 8 -b 2 -l 8
 3196 root        348 S   /usr/sbin/util_hkr_mgrd
 3487 root            SW< [cfmEntry]
 3488 root            SW< [cfmT]
 3489 root            SW< [cfmC]
 3490 root            SW< [cfmL]
 3491 root            SW< [cfmP]
 3520 root        328 S   /sbin/watchdog -t 90 /dev/ifx_wdt
 3525 root            SWN [jffs2_gcd_mtd3]
 3530 root        472 S   -sh
 4150 root        336 S   /usr/sbin/telnetd
 4154 root        468 S   -sh
 4965 root        212 S   udhcpc -i br0.301
 5293 root        468 S   -sh
 5294 root        448 R   ps
# while true
> do
> kill `ps | grep [t]elnetd | cut -f3 -d' '`
> sleep 30
> telnetd
> sleep 30
> done
kill: 8: Illegal number: root
telnetd: bind: Address already in use
kill: 8: Illegal number: root
telnetd: bind: Address already in use
kill: 8: Illegal number: root
telnetd: bind: Address already in use
kill: 8: Illegal number: root
telnetd: bind: Address already in use
kill: 8: Illegal number: root


And after restarting telnet:

Code: [Select]
IFX CPE login: admin
Password:


BusyBox v1.00 (2012.05.25-03:37+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

# ps
  PID  Uid     VmSize Stat Command
    1 root        440 S   init
    2 root            SWN [ksoftirqd/0]
    3 root            SW  [watchdog/0]
    4 root            SW< [events/0]
    5 root            SW< [khelper]
    6 root            SW< [kthread]
   26 root            SW< [kblockd/0]
   39 root            SW  [pdflush]
   40 root            SW  [pdflush]
   41 root            SW< [kswapd0]
   42 root            SW< [aio/0]
   76 root            SW  [mtdblockd]
 1329 root        592 S   /opt/lantiq/bin/dsl_cpe_control -i05_01_04_00_04_01_0
 1330 root        592 S   /opt/lantiq/bin/dsl_cpe_control -i05_01_04_00_04_01_0
 1332 root        592 S   /opt/lantiq/bin/dsl_cpe_control -i05_01_04_00_04_01_0
 1335 root        592 S   /opt/lantiq/bin/dsl_cpe_control -i05_01_04_00_04_01_0
 1336 root        592 S   /opt/lantiq/bin/dsl_cpe_control -i05_01_04_00_04_01_0
 1364 root            SW  [autbtex]
 1365 root            SW  [pmex_ne]
 1366 root            SW  [pmex_fe]
 2100 root        368 S   /sbin/syslogd -s 8 -b 2 -l 8
 3196 root        348 S   /usr/sbin/util_hkr_mgrd
 3487 root            SW< [cfmEntry]
 3488 root            SW< [cfmT]
 3489 root            SW< [cfmC]
 3490 root            SW< [cfmL]
 3491 root            SW< [cfmP]
 3520 root        328 S   /sbin/watchdog -t 90 /dev/ifx_wdt
 3525 root            SWN [jffs2_gcd_mtd3]
 3530 root        472 S   -sh
 4150 root        336 S   /usr/sbin/telnetd
 4154 root        468 S   -sh
 4965 root        212 S   udhcpc -i br0.301
 5338 root        468 S   -sh
 5339 root        448 R   ps
#
Logged

Blackeagle

  • Reg Member
  • ***
  • Posts: 257
Re: ECI model B-FOCuS V-2FUb/I Rev.B Experiences
« Reply #40 on: April 19, 2014, 01:37:28 PM »

OK, the easiest way to debug this is to just type in this part grep [t]elnetd | cut -f3 -d' ' and see what that returns.  If you get a blank line, or a number that isn't the PID of telnetd, then the cut part of the command may need adjusting.  Normally, I would have cut field 2 (-f2) to return the pid, but this wasn't returning it on my ECI/i and -f3 did.

You won't see the grep process listed under ps.  What you should see I think is /bin/sh  which will be the shell instance running the infinite loop.  You would only see grep if it was actually running when you type ps.

Only one telnet connection is a little limiting  :( 
Logged
ASCII stupid question, get a stupid ANSI -- TalkTalk Broadband since 2006

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: ECI model B-FOCuS V-2FUb/I Rev.B Experiences
« Reply #41 on: April 19, 2014, 02:31:18 PM »

Just a comment (no criticism is implied) but this thread's subject line refers to the V-2FUb/I (the original ECI CPE provided by Openreach), yet the latter posts of this thread are all related to the V-2FUb/r . . .  :-X
Logged
:cat:  100% Linux and, previously, Unix. Co-founder of the ELRepo Project.

Please consider making a donation to support the running of this site.

Blackeagle

  • Reg Member
  • ***
  • Posts: 257
Re: ECI model B-FOCuS V-2FUb/I Rev.B Experiences
« Reply #42 on: April 19, 2014, 03:43:08 PM »

Just a comment (no criticism is implied) but this thread's subject line refers to the V-2FUb/I (the original ECI CPE provided by Openreach), yet the latter posts of this thread are all related to the V-2FUb/r . . .  :-X

That does appear to be the case  :-[

However, the monitor in development is being designed for the ECI/i, with additions available for those using the ECI/r.

As a completely on topic remark, I make the following observations.

The ECI/i is a horrible piece of rubbish compared to the HG612.  Certainly on my line this has proved to be the case, in spite of the fact my DSLAM is also Infineon.  Sync speed is 5Mbps less than the HG612 and interleaving appears to be much higher at 2125ms.  The only positive I have noticed, is that at some points, the ECI is able to utilise the D2 band.  My HG612 completely ignores this band, having as it does an attenuation of 74dB.  The ECI only sometimes manages to use it, reporting an SNR figure of 64dB when not in use

All things being equal, once the development of the monitor is over, I think I shall be switching back to the HG612.  I've seen other posts by people saying their ECI's are better on their lines, but sadly that hasn't been my experience to date.
Logged
ASCII stupid question, get a stupid ANSI -- TalkTalk Broadband since 2006

HighBeta

  • Reg Member
  • ***
  • Posts: 175
Re: ECI model B-FOCuS V-2FUb/I Rev.B Experiences
« Reply #43 on: April 19, 2014, 04:19:41 PM »

I to found the ECI/I the least capable of out of the crop of openreach cpe units when paired to an ECI Msan. {ECI/r v2 the most} On the other hand other users have reported the opposite.
Thanks for the continued development & useful scrips Blackeagle   :)
« Last Edit: April 19, 2014, 05:10:26 PM by HighBeta »
Logged

custard

  • Member
  • **
  • Posts: 83
    • Geeky Dentist
Re: ECI model B-FOCuS V-2FUb/I Rev.B Experiences
« Reply #44 on: April 19, 2014, 07:06:53 PM »

Sorry burakkucat, didn't mean for the thread to veer off topic. :-[

@Bleackeagle - I had a go with changing the telnet commands from f3 to f2 with no joy. I ending up rebooting after multiple attempts at trying to get it to work and then finally losing serial access aswell.
After the reboot I found I could use eDMT and telnet simultaneously....I think i'll leave that testing for now and open a new thread posing the question again in the future if needed.
I'm sorry to hear that the ECI/I is not working for you. Would you not consider trying the ECI/r?
Let me know if you need to test anything further on the ECI/r or the offline ECI/I before the beta test release.

Logged
Pages: 1 2 [3] 4
 

anything