Orbi WiFi 7 RBE973
Reply

Re: New firmware with built in Torrent Client

Malpd
Aspirant

Re: New firmware with built in Torrent Client

I finally got a vdsl (fastweb) hopefully tomorrow i will test if it works with this modem 😄
Message 376 of 1,478
sasza
Aspirant

Re: New firmware with built in Torrent Client

Nevermind, I figured out how to copy the output, I'll post the output you requested later on.

/sasza
Message 377 of 1,478
ittroll
Apprentice

Re: New firmware with built in Torrent Client

Joined the forum for the sole purpose of thanking richud for his superb work on this firmware.

I stumbled across this thread when searching for a solution that added support for alternative dynamic DNS services. This firmware of course offers that and so much more. I am already enjoying cross-device ad free browsing and a magical fifth LAN port! I am sure I will play with some of the other added features in the near future.

I expect you may see an increase in downloads in the coming weeks now that DynDNS are shutting down their free service.

I have one quick question. Does the Backup Settings option only backup the standard Netgear settings or does it include any configuration for added extras? I note that the backup file isn't any larger so I suspect the former.
Message 378 of 1,478
sasza
Aspirant

Re: New firmware with built in Torrent Client

Yeah, the VDSL I keep talking about is the extra perk, I originally came for DynDNS replacement 🙂

As for backup - I think it saves them all - ie. added extras as well. I have used it yesterday when changing between VDSL straight/ via bridged modem and it reintroduced entire config.

/sasza
Message 379 of 1,478
Malpd
Aspirant

Re: New firmware with built in Torrent Client

sees like it works, i cant test it because i dont have an active account so i cant surf the web but the modem connects wit a nice bandwith

Message 380 of 1,478
sasza
Aspirant

Re: New firmware with built in Torrent Client

Ok, I got the data

~ # xdslctl info --show
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 10578 Kbps, Downstream rate = 64352 Kbps
Bearer: 0, Upstream rate = 8568 Kbps, Downstream rate = 59764 Kbps

Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 9.1 8.1
Attn(dB): 0.0 0.0
Pwr(dBm): 14.5 -7.6

VDSL2 framing
Bearer 0
MSGc: 18 82
B: 111 31
M: 1 1
T: 44 36
R: 16 10
S: 0.0596 0.1182
L: 17170 2842
😧 539 143
I: 128 42
N: 128 42

Counters
Bearer 0
OHF: 81988 13763
OHFErr: 0 0
RS: 10756301 1154683
RSCorr: 12 0
RSUnCorr: 0 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 18578794 0
Data Cells: 16 0
Drop Cells: 0
Bit Errors: 0 0

ES: 0 0
SES: 0 0
UAS: 43 43
AS: 162

Bearer 0
INP: 2.00 2.00
INPRein: 0.00 0.00
delay: 8 4
PER: 1.96 11.70
OR: 97.55 60.14

Bitswap: 0/29 0/0
Message 381 of 1,478
sasza
Aspirant

Re: New firmware with built in Torrent Client

And ifconfig


~ # ifconfig -a
atm0 Link encap:Ethernet HWaddr A0:21:B7:68:C7:D4
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:94 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:840 (840.0 B) TX bytes:5640 (5.5 KiB)

atm0.35 Link encap:Ethernet HWaddr A0:21:B7:68:C7:D4
UP BROADCAST RUNNING MULTICAST MTU:1500 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)

bcmsw Link encap:Ethernet HWaddr A0:21:B7:68:C7:D3
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:20755 errors:0 dropped:0 overruns:0 frame:0
TX packets:3777 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3297404 (3.1 MiB) TX bytes:2422074 (2.3 MiB)
Interrupt:40 Base address:0x6a00

br0 Link encap:Ethernet HWaddr A0:21:B7:68:C7:D3
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:23654 errors:0 dropped:0 overruns:0 frame:0
TX packets:2040 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4599754 (4.3 MiB) TX bytes:591778 (577.9 KiB)

dsl0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
[NO FLAGS] 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)

eth0 Link encap:Ethernet HWaddr A0:21:B7:68:C7:D4
BROADCAST MULTICAST MTU:1500 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:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

eth1 Link encap:Ethernet HWaddr A0:21:B7:68:C7:D3
UP BROADCAST MULTICAST MTU:1500 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:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)


eth2 Link encap:Ethernet HWaddr A0:21:B7:68:C7:D3
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:20755 errors:0 dropped:0 overruns:0 frame:0
TX packets:3777 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3297404 (3.1 MiB) TX bytes:2422074 (2.3 MiB)


eth3 Link encap:Ethernet HWaddr A0:21:B7:68:C7:D3
UP BROADCAST MULTICAST MTU:1500 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:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)


eth4 Link encap:Ethernet HWaddr A0:21:B7:68:C7:D3
UP BROADCAST MULTICAST MTU:1500 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:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)


ipsec0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
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:10
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

ipsec1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
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:10
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

ipsec2 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
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:10
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

ipsec3 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
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:10
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

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:137 errors:0 dropped:0 overruns:0 frame:0
TX packets:137 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:29046 (28.3 KiB) TX bytes:29046 (28.3 KiB)

sar 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

swc 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

teql0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:1500 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:100
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wl0 Link encap:Ethernet HWaddr A0:21:B7:68:C7:D3
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3815 errors:0 dropped:0 overruns:0 frame:1050
TX packets:4475 errors:138 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2064337 (1.9 MiB) TX bytes:3752634 (3.5 MiB)
Interrupt:21

wl0.1 Link encap:Ethernet HWaddr 62:21:B7:68:C7:D0
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:3815 errors:0 dropped:0 overruns:0 frame:1050
TX packets:4475 errors:138 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2064337 (1.9 MiB) TX bytes:3752634 (3.5 MiB)

wl0.2 Link encap:Ethernet HWaddr 62:21:B7:68:C7:D1
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:3815 errors:0 dropped:0 overruns:0 frame:1050
TX packets:4475 errors:138 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2064337 (1.9 MiB) TX bytes:3752634 (3.5 MiB)

wl0.3 Link encap:Ethernet HWaddr 62:21:B7:68:C7:D2
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:3815 errors:0 dropped:0 overruns:0 frame:1050
TX packets:4475 errors:138 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2064337 (1.9 MiB) TX bytes:3752634 (3.5 MiB)

wl1 Link encap:Ethernet HWaddr A0:21:B7:68:C7:D4
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:171 errors:0 dropped:0 overruns:0 frame:2
TX packets:3364 errors:286 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:29105 (28.4 KiB) TX bytes:3505572 (3.3 MiB)
Interrupt:21

wl1.1 Link encap:Ethernet HWaddr 52:21:B7:68:C7:D5
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:171 errors:0 dropped:0 overruns:0 frame:2
TX packets:3364 errors:286 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:29105 (28.4 KiB) TX bytes:3505572 (3.3 MiB)

wl1.2 Link encap:Ethernet HWaddr 52:21:B7:68:C7:D6
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:171 errors:0 dropped:0 overruns:0 frame:2
TX packets:3364 errors:286 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:29105 (28.4 KiB) TX bytes:3505572 (3.3 MiB)

wl1.3 Link encap:Ethernet HWaddr 52:21:B7:68:C7:D7
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:171 errors:0 dropped:0 overruns:0 frame:2
TX packets:3364 errors:286 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:29105 (28.4 KiB) TX bytes:3505572 (3.3 MiB)
Message 382 of 1,478
ittroll
Apprentice

Re: New firmware with built in Torrent Client

sasza wrote:
Yeah, the VDSL I keep talking about is the extra perk, I originally came for DynDNS replacement 🙂

Interesting, I am not currently of fibre but I expect to be in the near future. So this with this router/firmware combo I can do without with the nasty ISP modem? I am in the UK where I believe they use PTM with VLAN tagging.

If so that is awesome. Can't believe this hardware is still giving out surprises!
Message 383 of 1,478
Malpd
Aspirant

Re: New firmware with built in Torrent Client

http://www.speedtest.net/my-result/3440972833


Goes like the wind !


a little sidenote :

On the provider website where they tell how to configure the router/modem They say you have to set it as ATM instead to make it work i had to set it as PTM
Message 384 of 1,478
Malpd
Aspirant

Re: New firmware with built in Torrent Client





forgot the two pics
Message 385 of 1,478
robi69
Aspirant

Re: New firmware with built in Torrent Client

@richud
In the next firmware release, if possible, you should do the update dlna who has problems with the samsung tv
thanks
Message 386 of 1,478
richud
Apprentice

Re: New firmware with built in Torrent Client

sasza: you have a physical link up, but I cannot see any pppoe/pppoa connection? does /var/log/messages show anything from pppd ? Without any definitive ISP settings it is rather hard to work out the problem. Also, I am not 100% sure the VLAN tagging is correct/working as I cannot test it - and no one else has reported back about using it.

malp: cool!

robi: can you please post any problem with miniDLNA (Readyshare) to the developers site here http://sourceforge.net/p/minidlna/bugs/
(There often seem to be things posted there about Samsung tv's.)
[the last firmware release I made was up to date (on that day) with the latest git pull.]
Message 387 of 1,478
sasza
Aspirant

Re: New firmware with built in Torrent Client

richud wrote:
sasza: you have a physical link up, but I cannot see any pppoe/pppoa connection? does /var/log/messages show anything from pppd ? Without any definitive ISP settings it is rather hard to work out the problem. Also, I am not 100% sure the VLAN tagging is correct/working as I cannot test it - and no one else has reported back about using it.


Re: ISP settings. I've done my google and general agreement is VLAN ID 35 and 802.11q enabled. I did VLAN, but I don't see any option to enable 802.11q...

I'll report back on log later.
Message 388 of 1,478
sasza
Aspirant

Re: New firmware with built in Torrent Client

All I get from /var/log/messages is:

Jan 1 00:02:37 (none) daemon.notice pppd[1268]: PPP: Start to connect ...

several times, than it tries to resolve google.com, fails and tries to connect again and again.

Oh, don't know if that matters, but some people said they had to turn on Multi-VLAN option as well (configuring some other modem/ routers with Neostrada VDSL).

Please excuse me if my comments don't make much sense. I've enough skill to try to configure it/ ask about why it won't work, but I don't really understand most of the things here 😞
Message 389 of 1,478
ali1234
Aspirant

Re: New firmware with built in Torrent Client

richud wrote:
@ali: not really but you can set a cron job as a hook in. e.g. @reboot and will run when cron starts.


Today I installed your firmware and tried this, but it didn't work. busybox cron does not support @reboot: https://dev.openwrt.org/ticket/12438

My suggestion would be to simply add something in /etc/init.d/rcS near the end - directly before the sleep 5 would be perfect - which checks a param eg "user_startup" and if it contains a filename which exists and is executable, it executes that file.


if [ -x $(param get user_startup) ] ; then $(param get user_startup) & fi
Message 390 of 1,478
ali1234
Aspirant

Re: New firmware with built in Torrent Client

It would also be handy to place a similar hook in to wan-up.sh.
Message 391 of 1,478
CFB
Aspirant
Aspirant

Re: New firmware with built in Torrent Client

Is ext4 supported as FS for the USB drive?
reading the changelog I'd say yes

Changelog 2014-03-15

Additions:

e2fsprogs 1.42.9 - cant format/check ext2/3/4 file system directly on DGND3700 (mke2fs/e2fsck/badblocks etc. Usage example under 'transmission' here


but my ext4 formatted pendrive is mounted as jfffs
and samba doesn't work (works flawlessy instead, for instance, with vfat...)
Message 392 of 1,478
w3wilkes
Prodigy

Re: New firmware with built in Torrent Client

I wasn't able to get ext4 working reliably. ext3 works fine.
Message 393 of 1,478
burt35
Aspirant

Re: New firmware with built in Torrent Client

hi richud just installed your firmware with a view to using it with sky fibre in a week when it goes live. just wondering if it supports mer or if anyone has had any success connecting to sky fibre in uk. cheers.
Message 394 of 1,478
regenade
Aspirant

Re: New firmware with built in Torrent Client

Hi Richud,

Just wanted to point out that there are some new firmwares for the German DGND3800B router(which is essentially the same as DGND3700 v1 with official VDSL support.

Here are the firmware links :

http://www.downloads.netgear.com/files/GDC/DGND3800B/DGND3800B-V3.0.0.12_3.0.12.zip

Full FTP repository : ftp://updates1.netgear.com/dgnd3800/de/

The last 2 firmwares were quite recent and there are change logs as well. Also looks like the modem firmware might have been updated as well.

Looking forward for some integration if possible, will be very happy to be a test mule and may be some guys with VDSL can also pitch in.

Thanks again for the great work.
Message 395 of 1,478
Malpd
Aspirant

Re: New firmware with built in Torrent Client

This firmware already supports vdsl and it works very well (using it right now).


I wanted to signal an interesting function i would love to have integrated in this 🙂

http://dnscrypt.org/

https://github.com/opendns/dnscrypt-proxy


itsa basicly a ssh encrypted opendns.

From what i understand it can be installed on the router (open wrt has it) or there is a windows/mac interface https://github.com/opendns/dnscrypt-win-client




then i have a question :
how can i use cron to delay the automatic rss to start after wan goes live ? , like lets say start it 2 mins after router boot.
Message 396 of 1,478
imbalancedzero
Aspirant

Re: New firmware with built in Torrent Client

Using DGND3700 just as a bridge is very broken for some reason. WLAN is fine but LAN is very hit and miss.

Initally to get WLAN working i plugged in from Other router to WAN port after enabling WAN to LAN. Then realised that LAN connections weren't getting assigned IP addresses correctly :S

So I plugged i unplugged from WLAN to LAN port 1 and now LAN and WLAN are connected.

Are there any benefits to changing resolv.conf to nameserver 192.168.0.1 (as this is other router connecting to internet)?

Also I'm running brctl stp br0 on and running route add default gw 192.168.0.1

I can now ping google.com and get back and timesync will work, however when I try and perform hostlookup from gui the DNS server shows 0.0.0.0

Anything I'm doing wrong? Is there a way to fix the hit and miss side for setting up DGND3700 just as a bridge?
Message 397 of 1,478
imbalancedzero
Aspirant

Re: New firmware with built in Torrent Client

DGND3700 is very broken when trying to set up as a bridge only. Everything is a bit hit and miss.

Initially I had the LAN cable plugged from other router into one of the LAN sockets on DGND3700, but WLAN did not get an internet connection.

I then plugged LAN cable from other router into WAN socket after enabling WAN2LAN service and WLAN worked, but LAN connections to other devices did not! Eventually reverted back to the LAN socket and it worked :S

I've been checking a few settings via ssh and added:
nameserver 192.168.0.1
to resovl.conf (192.168.0.1 address of other router connecting to Internet)

I also ran:
brctl br0 stp on
and:
route add default gw 192.168.0.1

i could now ping google.com with a response, however in the gui, performing a dnslookup returns nothing and dns server shows as 0.0.0.0. Any ideas why this is happening? timesync works after initially setting the date and time.

Is there a need for me to run any of the above? Or should I run this on reboot?
Message 398 of 1,478
burt35
Aspirant

Re: New firmware with built in Torrent Client

richud just looking at various posts on how to set this router up with fibre and one option that pops up is that sky fibre requires dhcp opt 61 where do you input this figure im a bit baffled as to where this goes is there a setting for this? thanks for your time.
Message 399 of 1,478
Malpd
Aspirant

Re: New firmware with built in Torrent Client

if i understood right you should just enter you skyID in the "account name" field under basic settings

but not sure since i didnte quite get ho this SKY fiber works ( MER protocol )
Message 400 of 1,478
Top Contributors
Announcements

Orbi WiFi 7