Print

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

[hacktrix2006]

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

[jsamuel]

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

[Weaver]

@jsamuel   - btw, thanks for that link, very useful reading.

[garmanarnar]

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

[liamstears]

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

[liamstears]

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?

[doughnut]

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

[phi2008]

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.   

[jsamuel]

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.   

telnet

sh
ifconfig

[loonylion]

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.   

Code: [Select]

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)

#


[jsamuel]

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.

[iMx]

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,

[iMx]

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:

Code: [Select]

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:

Code: [Select]

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:

Code: [Select]

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"

[iMx]

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}')
}

[iMx]

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.

Code: [Select]

root@OpenWrt:~# ifconfig eth1 mtu 1508
ifconfig: SIOCSIFMTU: Invalid argument
root@OpenWrt:~# ifconfig eth1 mtu 1500
root@OpenWrt:~#