Print

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

[Lil-Koby]

@shdf
Just wanted to let you know that i've found the reason for the high LAN Ping (>1ms)... it seems to be related to the "CPU speed adjustment", Gateway >> ECO Settings.
If I set CPU Speed to 1 (highest clock) i do get stable pingtimes under <1ms... still a bit higher than with my other wired Network equipment but "stable" and below 1ms.

Code: [Select]

root@LEDE:~# ping 192.168.254.254 -c5
PING 192.168.254.254 (192.168.254.254): 56 data bytes
64 bytes from 192.168.254.254: seq=0 ttl=64 time=0.790 ms
64 bytes from 192.168.254.254: seq=1 ttl=64 time=0.809 ms
64 bytes from 192.168.254.254: seq=2 ttl=64 time=0.746 ms
64 bytes from 192.168.254.254: seq=3 ttl=64 time=0.839 ms
64 bytes from 192.168.254.254: seq=4 ttl=64 time=0.792 ms
CPU Speed 1:

Code: [Select]

root@VDSL_Bridge:~# cat /proc/cpuinfo
Processor       : ARMv7 Processor rev 1 (v7l)
processor       : 0
BogoMIPS        : 1990.65

processor       : 1
BogoMIPS        : 1990.65

Features        : swp half thumb fastmult edsp tls
CPU Speed auto:

Code: [Select]

root@VDSL_Bridge:~# cat /proc/cpuinfo
Processor       : ARMv7 Processor rev 1 (v7l)
processor       : 0
BogoMIPS        : 398.13

processor       : 1
BogoMIPS        : 398.13

Features        : swp half thumb fastmult edsp tls
But to be honest it's just a visual thing... the internet ping times wont get better because of the lower LAN ping.
I think overall it will just produce more heat and the only noticeable ‎advantage in bridge mode is a snappier GUI.
But it might make a slight difference in router mode...

Didn't tested any other Eco settings, but I can remember that I had a problem where the DGA device or better said odhcpd manually added a local IP and the ping time to that IP was stable below 0.5ms. So a value below 0.8ms is also possible with automatic adjustment of the CPU speed.

I kinda wish a true (and stable) openwrt version with original Luci GUI would come out for the DGA4130... do you think it will ever come to this point ?
Man I would even donate for this !

[shdf]

Hello !
nice find  so the cpu is somewhat underclocked then...My ISP box (Livebox 4) is also using a bcm63138, and the ping latency is always lower than 1ms...idle or not. the cpu speed is probably set to 1 then ?!
i think i'm going to set it to 1 in the DGA.

About a true Openwrt for the DGA, i don't know if it will happen as there are only 2 person working on it. The big problem is the bootloader checking for a signed firmware, if this can be bypassed (i don't know how) then this can be added in the Lede/openwrt project as other Lantiq based Modem/router (BT HomeHub 5.0 Type A). But we need more skilled people on this project...

[Lil-Koby]

Maybe the cpu driver is just behaving different in the Livebox 4...
Normally auto adjustment should work fine and the cpu will clock to its full potential under load.

I would really like to help with openwrt but sadly i'm not skilled enough, hopefully someone will find a way to unlock or bypass the bootloader.

[Lil-Koby]

@bilbokitz
Did you get rid of your bridge mode problem ?

I found out that you don't need to enable pure bridge mode to be able to establish the pppoe/pppoa connection with another router.
So let me know if you are still facing the problem, maybe it can be fixed with my new bridge config...

[bilbokitz]

@Lil-Koby

No I did not.

I do have the DGA4130 in bridgemode and it is working but I had to swap out my main router (new Asus ac86u) during the holidays and the ppp connection would not establish again so I had to plug my HG612 back in which connected fine.

I then turned off the HG612 and turned on the DGA4130 and all is okay again. Very strange. The connection is PPPoE.

What is your config? Half bridge or something?

[Lil-Koby]

Well I think it was some sort of half bridge... 
I came up with this as i was trying to set up bridge mode with the original tim gui 1.0.3 (it worked btw).
But I couldn't get telnet to work so i updated to 3.36 and disabled the bridge mode and after a reboot I found out that my main router was still connection via pppoe.

Than i edited the network config and replaced some stuff with my old full bridge config but leaving wan_mode default:

Code: [Select]

config config 'config'
option wan_mode 'pppoe'
Now the login screen will say it's in bridge mode... but Broadband will report a "green connected", just like in router mode.
Before i had the "grey bridge disabled bug" (with gui version 3.36+) every time, even if everything was fine and working.

So first of all i would do a full reset (with remove root), before doing so make sure your running fw 1.0.3, than use the unlock tool to gain ssh access (dont tick any options!) and than install gui 3.36 via ssh. Finally do a reboot and clear your browser cache.
After the reboot + clear browser cache setup everything via custom GUI.

1. Turn pppoe OFF
2. Under Broadband set Using VLAN to OFF
3. Disable/Turn OFF all the other stuff you dont need (Samba, DLNA, Mobile, DLNA telephony, CWMPD, aso.)
4. Reboot, and check if you Router is able to establish a pppoe connection
(if your router is able to establish a pppoe connection check if your problem with the timeout still exist)

I didn't make a config backup using the above described mode but here is the main part of my new network config:
(keep in mind that with this config the Login screen will report bridge mode and i'm using VLAN: ON, VID: 835)

Code: [Select]

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 'none'
option default_ps '0'

config device 'waneth4'
option type '8021q'
option name 'waneth4'
option macaddr '10:13:31:XX:XX:XX'
option ifname 'eth4'
option vid '835'
option ipv6 '0'

config device 'wanptm0'
option type '8021q'
option name 'wanptm0'
option macaddr '10:13:31:XX:XX:XX'
option ifname 'ptm0'
option vid '835'
option ipv6 '0'

config interface 'wan'
option proto 'pppoe'
option demand '0'
option username 'blub@blub'
option password 'blub'
option macaddr '10:13:31:XX:XX:XX'
option ipv6 '0'
option peerdns '1'
option reqopts '1 3 6 15 33 42 51 121 249'
option keepalive_adaptive '0'
option dns_metric '0'
option enabled '0'
option ifname 'wanptm0'
option auto '0'

config config 'config'
option wan_mode 'pppoe'

config interface 'wwan'
option auto '1'
option proto 'mobiled'
option session_id '0'
option profile '1'
option enabled '0'

config interface 'wan6'
option proto 'dhcpv6'
option reqopts '12 21 22 23 24 25 31 56 64 67 82 83'
option noslaaconly '1'
option iface_464xlat '0'
option auto '0'
option dns_metric '20'
option ifname '@wan_ipv6'
option enabled '0'

config interface 'lan'
option type 'bridge'
option proto 'static'
option netmask '255.255.255.0'
option ip6assign '64'
option force_link '0'
option ipv6 '0'
option ipaddr '192.168.254.254'
option pppoerelay '<set by script>'
list ifname 'eth0'
list ifname 'eth1'
list ifname 'eth2'
list ifname 'eth3'
list ifname 'eth5'
list ifname 'wanptm0'

config switch 'bcmsw'
option reset '1'
option enable_vlan '0'
option qosimppauseenable '0'
option jumbo '0'
I've also disabled a lot of init.d stuff but im not sure if it will brake something in the long run.
But i would recommend to stop and disable Mobiled, wansensing, watchdog, igmpproxy and cwmpd.
I could also imagine that wansensing or watchdog is responsible for your timeout problem...

Code: [Select]

/etc/init.d/igmpproxy stop
/etc/init.d/igmpproxy disable
/etc/init.d/mobiled stop
/etc/init.d/mobiled disable
/etc/init.d/wansensing stop     
/etc/init.d/wansensing disable
/etc/init.d/watchdog-tch stop
/etc/init.d/watchdog-tch disable
/etc/init.d/cwmpd stop
/etc/init.d/cwmpd disable
/etc/init.d/cwmpdboot disable
Hopefully it will fix your weird timeout problem...

Btw, you run official firmware on your AC86U ?
I would highly recommend to use merlin's fw on this device: https://www.snbforums.com/threads/asuswrt-merlin-custom-firmware-for-asus-routers.7846/
You can also gain access your modem GUI (modem on a different subnet) when using pppoe with your Asus Router, if you didn't know that already.

[shdf]

i can see on Ebay for a price that is reasonable, a brand new Technicolor TG800vac which is the same as the DGA4130, with a better wifi (Broadcom 4366 vs Quantenna) + CatIQ DECT support + NFC chip.
https://www.ebay.co.uk/itm/Latest-Telstra-Technicolor-TG800vac-Fibre-Wireless-NBN-Connection-Kit-Modem-264/352231865066

Some people here in the comments have successfully rooted the TG800:
https://www.crc.id.au/hacking-the-technicolor-tg799vac-and-unlocking-features/

Note:
the access to the ACS servers is working for everyone, even if you're not on the NBN network. We can download the 16.3 Firmware:
http://fwstore.bdms.telstra.net/Technicolor_vant-y_CRF690-16.3.7567-660-RD/vant-y_CRF690-16.3.7567-660-RD.rbi
So it is important to disable the CWMP.

[Lil-Koby]

@shdf
Thanks for letting us know about this device.
I'm tempting to buy a TG800vac for myself but it's a little more pricey than the good old DGA4130 (which doesn't seem to be available at the moment)...

[shdf]

it's more expensive, but there are more features, i think the wifi is faster if it's a bcm 4366 and There is a DECT support, + NFC
But if it is intended to be used as bridge, of course that's useless...

[Lil-Koby]

@shdf
Do you have any idea how i can remove those static guest-wifi routes (wl0_1,wl1_1)?

Code: [Select]

root@VDSL_Bridge:~# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.168.0   *               255.255.255.128 U     0      0        0 wl0_1
192.168.168.128 *               255.255.255.128 U     0      0        0 wl1_1
192.168.254.0   *               255.255.255.0   U     0      0        0 br-lan

Code: [Select]

root@VDSL_Bridge:~# ping 192.168.168.1 -c3
PING 192.168.168.1 (192.168.168.1): 56 data bytes
64 bytes from 192.168.168.1: seq=0 ttl=64 time=0.705 ms
64 bytes from 192.168.168.1: seq=1 ttl=64 time=0.409 ms
64 bytes from 192.168.168.1: seq=2 ttl=64 time=0.406 ms

root@VDSL_Bridge:~# ping 192.168.168.129 -c3
PING 192.168.168.129 (192.168.168.129): 56 data bytes
64 bytes from 192.168.168.129: seq=0 ttl=64 time=0.766 ms
64 bytes from 192.168.168.129: seq=1 ttl=64 time=0.412 ms
64 bytes from 192.168.168.129: seq=2 ttl=64 time=0.402 ms

edit: I think that i've got it done with "ip route del" but im pretty sure these static routes will come back after a restart (can't test atm)...

Code: [Select]

root@VDSL_Bridge:~# ip route del 192.168.168.0/25
root@VDSL_Bridge:~# ip route del 192.168.168.128/25
root@VDSL_Bridge:~# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.254.0   *               255.255.255.0   U     0      0        0 br-lan


Code: [Select]

root@VDSL_Bridge:~# grep -r "192.168.168.1" /etc
/etc/config/dhcp:       list dhcp_option '6,192.168.168.1'
/etc/config/dhcp:       list dhcp_option '6,192.168.168.129'
/etc/config/firewall:   option dest_ip '192.168.168.1'
/etc/config/firewall:   option dest_ip '192.168.168.1'
/etc/config/firewall:   option dest_ip '192.168.168.129'
/etc/config/firewall:   option dest_ip '192.168.168.129'
/etc/config/network:    option ipaddr '192.168.168.1'
/etc/config/network:    option ipaddr '192.168.168.129'

[shdf]

i think that as long as the interface exists in /etc/config/network and/or /etc/config/wireless then the route is created...if you don't need the guest wifi, just disable/delete it from both files
Do a backup of the files first 

[Lil-Koby]

Thanks shdf, it worked ! I just deleted interface 'wlnet_b_24' + interface 'wlnet_b_5' from /etc/config/network and the static routes went away after reboot.

So there is no need do delete them via "ip route delete" in the first place as they will come back after a reboot/network restart.

[shdf]

so you deleted all wifi, not just the guest wifi ?

maybe just a :
   option enabled '0'
would be enough to disable the interface, that way you keep your setings if one day you want to enable the wifi.

[Lil-Koby]

Yes, these were the only ones that i had in my network config...
I always duplicate the file via wscp an name it *.orig before i make any changes.
So in case i want to enable wifi one day i just put back my old config and restart the network.
Anyway i'll try it with option enabled '0'.

edit: It works !
option enabled '0' under each wifi interface + /etc/init.d/network restart

[shdf]