Print

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

[shdf]

Which modem do I pick in dslstats? Can't see this one listed in 6.1.

This is my configuration :

[roseway]

Which modem do I pick in dslstats? Can't see this one listed in 6.1.

Just leave it showing "Select modem/router model" and fill in the details:-

IP address: 192.168.1.1 (unless you've changed it)
Username/password: root/root
CLI command prefix: xdslctl

Don't check the option "Modem/router is Thomson/Technicolor model"

[Lil-Koby]

My DGA4130 arrived today...
It came with fw 1.0.2 and unlocking was quite easy.
I'm using gui version 3.25 at the moment.
Even bridge mode with vlan tag is working, i'm very happy so far...
Big thanks to Ansuel, your unlock tool and GUI are working very well !!!

The only thing which doesnt work for me is DSL stats Tool, it doesnt return any data, not even syncrate or Uptime.
Got telnet enabled (confirmed working) and i doesnt get any error message when pressing the Play button in DSL stats.
All i can see on top is "No data returned in lastest sample".

Log:

Code: [Select]

05 Dez 2017 19:35:03 Reset the current month's traffic
05 Dez 2017 19:35:03 Configuration files stored in C:\Users\workstation03\AppData\Local\dslstats\
05 Dez 2017 19:35:03 Snapshot folder is C:\Users\workstation03\AppData\Local\dslstats\
05 Dez 2017 19:35:48 Recording started
05 Dez 2017 19:36:03 Timeout while retrieving stats
05 Dez 2017 19:36:03 No stats received

05 Dez 2017 19:36:34 Timeout while retrieving stats
05 Dez 2017 19:36:34 No stats received
05 Dez 2017 19:37:04 Timeout while retrieving stats
05 Dez 2017 19:37:04 Unable to collect stats 3 or more times in succession
05 Dez 2017 19:37:04 No stats received
05 Dez 2017 19:37:34 Timeout while retrieving stats
05 Dez 2017 19:37:34 No stats received
05 Dez 2017 19:38:03 Timeout while retrieving stats
05 Dez 2017 19:38:04 No stats received
05 Dez 2017 19:38:34 Timeout while retrieving stats
05 Dez 2017 19:38:34 No stats received
05 Dez 2017 19:39:04 Timeout while retrieving stats
05 Dez 2017 19:39:04 No stats received
05 Dez 2017 19:39:33 Timeout while retrieving stats
05 Dez 2017 19:39:34 No stats received
05 Dez 2017 19:40:04 Timeout while retrieving stats
05 Dez 2017 19:40:04 No stats received
05 Dez 2017 19:40:34 Timeout while retrieving stats
05 Dez 2017 19:40:34 No stats received
05 Dez 2017 19:40:46 Recording stopped
Does it not work cause im using bridge mode ? Pls help.

[roseway]

I can't see any reason why bridge mode should make any difference. Are you sure that you've set the CLI command prefix to 'xdslctl' in the DSLstats login configuration?  Can you log in by telnet using Putty (or some other telnet client) and send the command:

xdslctl info --stats

Which should return a stream of data.

[Lil-Koby]

I really dont know why but its working now !
I've typed "xdslctl info --stats" in a normal telnet session and it was working fine.
Only thing i did was unchecking "Modem/Router is Thompson/Technicolor model"...

Well thanks for this sweet tool roseway, it will help me alot !

[kitzuser87430]

My set-up wizard is not working, I have unlocked, upgraded to 1.03 and installed GUI 3.25.

is anybody's setup wiz working on 3.25?

can users confirm what GUI the setup wiz is working on please.

Ian

[roseway]

Only thing i did was unchecking "Modem/Router is Thompson/Technicolor model"...

Ah yes, perhaps I should make that a bit clearer. That option applies to  the majority of Technicolor modems, which don't enable access to the full Broadcom stats, but instead provide a custom CLI via the telnet interface. In the case of the DGA4130, the unlocking procedure enables access to the full stats, so it doesn't need that option to be checked.

[Lil-Koby]

What do you exactly mean with "not working" ?
Not starting at all or config doesnt get trough ?

Btw, my log has some weired entries. Maybe someone knows how to get rid of these errors/warnings...
They are constantly spamming my log...

Code: [Select]

......
Nov 20 08:33:57 daemon.warn dnsmasq-dhcp[3540] no address range available for DHCP request via br-lan
Nov 20 08:33:54 daemon.warn dnsmasq-dhcp[3540] no address range available for DHCP request via br-lan
Nov 20 08:33:34 daemon.notice transformer [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Nov 20 08:33:31 daemon.warn dnsmasq-dhcp[3540] no address range available for DHCP request via br-lan
Nov 20 08:33:28 daemon.warn dnsmasq-dhcp[3540] no address range available for DHCP request via br-lan
Nov 20 08:33:25 daemon.warn dnsmasq-dhcp[3540] no address range available for DHCP request via br-lan
Nov 20 08:33:02 daemon.warn dnsmasq-dhcp[3540] no address range available for DHCP request via br-lan
Nov 20 08:33:00 cron.info crond[2457] USER root pid 14856 cmd /sbin/trafficdata.lua
Nov 20 08:32:59 daemon.warn dnsmasq-dhcp[3540] no address range available for DHCP request via br-lan
Nov 20 08:32:56 daemon.warn dnsmasq-dhcp[3540] no address range available for DHCP request via br-lan
Nov 20 08:32:34 daemon.notice transformer [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Nov 20 08:32:33 daemon.warn dnsmasq-dhcp[3540] no address range available for DHCP request via br-lan
Nov 20 08:32:30 daemon.warn dnsmasq-dhcp[3540] no address range available for DHCP request via br-lan
Nov 20 08:32:27 daemon.warn dnsmasq-dhcp[3540] no address range available for DHCP request via br-lan
Nov 20 08:32:13 daemon.err igmpproxy[4434] IGMP report received with src 192.168.1.252 which cannot be mapped on intf br-lan
Nov 20 08:32:13 daemon.notice igmpproxy[4434] IGMP report received from 192.168.1.252 on intf br-lan
Nov 20 08:32:06 daemon.notice igmpproxy[4434] Send IGMP packet to group 224.0.0.1 on intf br-lan
Nov 20 08:32:04 daemon.warn dnsmasq-dhcp[3540] no address range available for DHCP request via br-lan
Nov 20 08:32:01 daemon.warn dnsmasq-dhcp[3540] no address range available for DHCP request via br-lan
Nov 20 08:31:58 daemon.warn dnsmasq-dhcp[3540] no address range available for DHCP request via br-lan
Nov 20 08:31:35 daemon.warn dnsmasq-dhcp[3540] no address range available for DHCP request via br-lan
Nov 20 08:31:34 daemon.notice transformer [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
......

1. Im not using DHCP (its disabled via GUI). How to get rid these dnsmasq-dhcp entries ?
2. IGMP proxy doesnt make sense in bridge mode. How to disable it completly ?

My DHCP config:

Code: [Select]

root@vdsl-bridge:~# cat /etc/config/dhcp

config dnsmasq
        option domainneeded '1'
        option boguspriv '1'
        option filterwin2k '0'
        option localise_queries '1'
        option rebind_protection '1'
        option rebind_localhost '1'
        option local '/lan/'
        option expandhosts '1'
        option nonegcache '0'
        option authoritative '1'
        option readethers '1'
        option leasefile '/tmp/dhcp.leases'
        option resolvfile '/tmp/resolv.conf.auto'
        option strictorder '1'
        option dhcpscript '/lib/dnsmasq/dhcp-event.sh'
        list hostname 'dsldevice'
        option allservers '1'
        option domain 'homenet.VDSL.Bridge'

config odhcpd 'odhcpd'
        option leasefile '/tmp/hosts/odhcpd'
        option leasetrigger '/usr/sbin/odhcpd-update'
        option maindhcp '0'

config dhcp 'lan'
        option interface 'lan'
        option start '2'
        option dhcpv6 'server'
        option ra 'server'
        option ra_management '0'
        option ra_mininterval '200'
        option ra_maxinterval '600'
        option ra_lifetime '1800'
        option ra_hoplimit '64'
        option ra_max_mtu '1500'
        option force '1'
        option ignore '1'
        option limit '252'
        list dhcp_option 'tag:cpewan-id,vi-encap:3561,6,"4130"'
        list dhcp_option 'tag:cpewan-id,vi-encap:3561,5,"CP"'
        list dhcp_option 'tag:cpewan-id,vi-encap:3561,4,""'
        list dhcp_option ''
        list dhcp_option ''
        list dhcp_option ''
        list dhcp_option '6,192.168.254.254'
        option dhcpv4 'disabled'
        option leasetime '24h'

config dhcp 'wlnet_b_24'
        option interface 'wlnet_b_24'
        option start '2'
        option leasetime '1h'
        option force '1'
        option dhcpv6 'server'
        option ra 'server'
        option ra_management '0'
        option ra_mininterval '200'
        option ra_maxinterval '600'
        option ra_lifetime '1800'
        option ra_hoplimit '64'
        option ra_max_mtu '1480'
        option limit '125'

config dhcp 'wlnet_b_5'
        option interface 'wlnet_b_5'
        option start '130'
        option leasetime '1h'
        option force '1'
        option dhcpv6 'server'
        option ra 'server'
        option ra_management '0'
        option ra_mininterval '200'
        option ra_maxinterval '600'
        option ra_lifetime '1800'
        option ra_hoplimit '64'
        option ra_max_mtu '1480'
        option limit '125'

config dhcp 'wan'
        option interface 'wan'
        option ignore '1'

config dhcp 'wan6'
        option interface 'wan'
        option ignore '1'

config dhcp 'wwan'
        option interface 'wwan'
        option ignore '1'

config opassthrud 'opassthrud'
        option passthruscript '/lib/dhcpopassthrud/dnsmasq.sh'
        option options_needed '0'


[shdf]

if you want to disable the igmpproxy logs, set option trace '0' in /etc/config/igmpproxy

if you want to stop the daemon :
/etc/init.d/igmpproxy stop
/etc/init.d/igmpproxy disable

to restart it :
/etc/init.d/igmpproxy start
/etc/init.d/igmpproxy enable

About your DHCP problem, i think you have to set a DHCP range in the GUI before stoping it ? Try to go into the Local Network tab and click 'Show Advanced', set the DHCP, Save your settings and then disable the DHCP.
if it doesn't change anything then maybe try to set : option ignore '0' in your config dhcp 'lan' in the file /etc/config/dhcp

[Lil-Koby]

@shdf, thanks a bunch !

Disabling igmp proxy worked like a charm...

And you're right, I've changed the DHCP settings when I set up another modem IP ...
DHCP gave me some error so i adjusted the settings.
Anyway, your solution seems to work, I have activated and deactivated DHCP again and set the "option ignore 0" in the config.
The only thing left now is "daemon.notice transformer [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)", whatever that means.

What also drives me a bit crazy is that the ping times to the modem are always over 1ms on my wired network. I think that's a bit unusual ?
If I ping any other wired device within my local network I always get ping times under >1ms...
Btw, compared to my Vigor 130 the online ping times have increased by about 2ms.

In addition, the @ LED is always flashing red and the info LED is solid red... But I suspect this is normal for bridge mode ?

Code: [Select]

Main Router > Modem

root@LEDE:~# ping 192.168.10.10 -c5
PING 192.168.10.10 (192.168.10.10): 56 data bytes
64 bytes from 192.168.10.10: seq=0 ttl=64 time=1.196 ms
64 bytes from 192.168.10.10: seq=1 ttl=64 time=1.097 ms
64 bytes from 192.168.10.10: seq=2 ttl=64 time=1.074 ms
64 bytes from 192.168.10.10: seq=3 ttl=64 time=1.042 ms
64 bytes from 192.168.10.10: seq=4 ttl=64 time=1.040 ms

Code: [Select]

AP > Modem

root@AP1:/tmp/home/root# ping 192.168.10.10 -c5
PING 192.168.10.10 (192.168.10.10): 56 data bytes
64 bytes from 192.168.10.10: seq=0 ttl=63 time=1.241 ms
64 bytes from 192.168.10.10: seq=1 ttl=63 time=1.332 ms
64 bytes from 192.168.10.10: seq=2 ttl=63 time=1.413 ms
64 bytes from 192.168.10.10: seq=3 ttl=63 time=1.381 ms
64 bytes from 192.168.10.10: seq=4 ttl=63 time=1.398 ms

Code: [Select]

Main Router > AP

root@LEDE:~# ping 192.168.100.2 -c5
PING 192.168.100.2 (192.168.100.2): 56 data bytes
64 bytes from 192.168.100.2: seq=0 ttl=64 time=0.343 ms
64 bytes from 192.168.100.2: seq=1 ttl=64 time=0.341 ms
64 bytes from 192.168.100.2: seq=2 ttl=64 time=0.356 ms
64 bytes from 192.168.100.2: seq=3 ttl=64 time=0.339 ms
64 bytes from 192.168.100.2: seq=4 ttl=64 time=0.332 ms

Code: [Select]

Client via Modem LAN port

Source address is 192.168.10.1; using ICMP echo-request, ID=2810
Pinging 192.168.10.10 [192.168.10.10]
with 32 bytes data (60 bytes IP):
From 192.168.10.10: bytes=60 seq=0001 TTL=64 ID=e3fe time=1.269ms
From 192.168.10.10: bytes=60 seq=0002 TTL=64 ID=e3ff time=1.203ms
From 192.168.10.10: bytes=60 seq=0003 TTL=64 ID=e400 time=1.218ms
From 192.168.10.10: bytes=60 seq=0004 TTL=64 ID=e401 time=1.161ms
From 192.168.10.10: bytes=60 seq=0005 TTL=64 ID=e402 time=1.153ms

[shdf]

"daemon.notice transformer [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)", whatever that means.

i think this is related to the ability of the modem to manage 4G usb key modems. it just says that it doesn't find any device. It should disapear from your log if you disable the MOBILE tab in the GUI. Btw disable everything that you don't use (telefony, assistance, mobile, content sharing, printer, cwmp, parental control, etc...) this will make your logs more clear.

About the ping latency over 1ms, i know, i already reported that to the italian forum, there is something strange here but it is related to the Broadcom drivers...

About the LEDs, yes for the @ should be RED in bridge mode, but not the "i".
After the GUI 3.25 Ansuel added a bit of code in the file /etc/ledfw/stateMachines.lua which makes a RED "i" for me too. To fix this problem i copy the original file located at /rom/etc/ledfw/stateMachines.lua and i overwrite the te one at /etc/ledfw/stateMachines.lua
After a reboot it fixes the problem, the "i"becomes green again.

[atkinsong]

@shdf, in a post on page 4 of this thread you mentioned that you had configured your router for IPTV, presumably via IGMP. Could you let me know what you needed to do and how you did it please?
Thanks

[shdf]

Well, it depends on how it works with your ISP.
With Orange in France we need to create 2 new interfaces in 2 different VLAN in /etc/config/network
1 interface for the Video on demand which needs a special athentication methode by sending DHCP options. Vlan ID = 838
1 interface for the TV. Vlan ID = 840

so here is what i added in my /etc/network file

config interface 'replay'
   option ifname 'ptm0.838'
   option proto 'dhcp'
   option peerdns '1'
   option broadcast '1'
   option vendorid 'sagem'
   option reqopts '1 3 42 72 121'
   option sendopts '0x4D:xxxxxxxxxxx 0x3D:xxxxxxxx'
   option mtu '1500'

config interface 'tvorange'
   option proto 'static'
   option ifname 'ptm0.840'
   option ipaddr '192.168.255.254'
   option netmask '255.255.255.255'
   option gateway '192.168.255.254'

The igmp proxy is already well configured so there is nothing to change here.

EDIT:
I forgot to say that these 2 new interfaces i created (replay and tvorange) have to be added in the firewall /etc/config/firewall in the wan zone.

config zone
   option name 'wan'
   list network 'wan'
   list network 'replay'
   list network 'tvorange'
   list network 'wan6'
   list network 'wwan'
   option input 'DROP'
   option output 'ACCEPT'
   option forward 'DROP'
   option masq '1'
   option conntrack '1'
   option mtu_fix '1'
   option wan '1'

[Lil-Koby]

@shdf
Hopefully this ping stuff will/could get fixed, i feel like it's adding some unnecessary latency to the line.
To be honest, the red info LED isn't a real peoblem for me as long it's not indicating any error. Btw im using GUI 3.25 and fw 1.0.2.
I don't have the mobile tab anymore in bridge mode but if i remember right i did disable it in router mode (but i'm not 100% sure).

But there is something I would really like to know... Is there any xdsl driver that will return my old "Interleaving Depth 1/1, Path Mode: Fast/Fast", which I had before with the Vigor modem ?
The DGA4130 reports "Interleave 8/4", but i'm not even sure if this can be set by the CPE via driver but i'm quite sure that my port isn't forcing this Interleave depth.
Any advice which xdsl driver i should try ?

Beside of this the modem seems to be a great piece of hardware.
My upload speed went from 34800 up to 41000kbit/s, which is great improvement for me.
All CRC are gone as well, didn't even had one error within 16 hours...
And what i really love is the ability to monitor my line with DSL stats tool. That's really a very handy program !

[shdf]

you are with firmware 1.0.2 so first of all i would recommend you to upgrade because no one is using this old firmware and everything is now developed for firmware 1.0.3 / 1.0.4
Take it from here : http://repository.ilpuntotecnicoeadsl.com/files/Ansuel/AGTEF/AGTEF_1.0.3_CLOSED.rbi
And from the GUI do the update.

The xDSL driver is the same in both firmware (1.0.2/1.0.3), but you can test the one from the firmware 1.0.4 it is in my mega account :
https://mega.nz/#F!TFdF0Y4A!cI1TOh8kpw4jpTp8Q69fpQ

with winscp overvrite the file here : /etc/adsl/adsl_phy.bin
then from putty, type :
xdslctl connection --down
xdslctl stop
xdslctl start
xdslctl connection --up

In my case the driver from 1.0.3 makes a better sync.
You can also try the one from the Asus 1.10.03 wich is reported to work well by some italian users.