- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Rif.: New firmware with built in Torrent Client
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: New firmware with built in Torrent Client
Just finished to complete a quick try, vlan setting works fine, the corresponding interface automatically brings up.
Here is the new pppd command line observed:
pppd -c ppp0 -i eth0 -u USERNAME -p PASSWORD -t 1458 -f 0 -m ac853da32039/4a35 -k
I haven't sniffed already but apparently the tag is still missing from the connection. I cannot explain at all what the bolded argument means, it seems something related to acces concentrators but I don't know why it is appearing now as a parameter.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: New firmware with built in Torrent Client
Setting the service name on the web gui just uses the same setting for the service name and host-uniq tag, when I looked running it through tcpdump it seemed to be sending both ok.
from ppd -m is below, but I cant see why thats appearing. On mine I got just -r with the service name set, (nvram "ppp0_service_name"), is that nvram set ok for you?
fprintf(stderr, "usage: %s [-s] [-b] [-d] [-i interface] [-a vcc] [-u username] [-p passwd] [-o idle] [-m prevmac/prevsid] [-A ipaddr] [-t max MTU]
optarg m is 'oldsession' which is :
char oldsession[MAXPATHLEN]=""; /* Mac address and session ID of the previous session */
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: New firmware with built in Torrent Client
Ok I didn't noticed you changed the setting name from the previous build so it was basically connecting without any tag. I filled up the service name setting and it actually sends the host-uniq tag correctly but it is also adding a service name tag to the PADI packet. The pppoe server replies adding the AC-Name tag as expected but the client seems to go into error since it's aborting the connection attempt immediatelly after with a PADT, so the ppp tunnel does not go up at all. Mayby service name should not be set, or something wrong is happening with the received tags, just check what code path makes rppppoe send a PADT after a positive PADO.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: New firmware with built in Torrent Client
I just finisher looking for PADO parsing routines in rp-pppoe 3.12 and I'm pretty confident that the error comes from the mismatch between chosen AC-Name (same as host-uniq in your last build) and the AC-Name set by the server. This afternoon/evening I'll retry setting the correct AC-Name as host-uniq, given that the connection should be ok even with an arbitrary chosen value. Anyway it's clearly a trick and it shoudn't be the way of setting up the connection.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: New firmware with built in Torrent Client
https://mega.nz/#!RQgywIaK!rwpbjtdkpRo6SrGR-pm_9TwF8Fa2bAZSeXDZLdVzKJU
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: New firmware with built in Torrent Client
I put up the 3-19 firmware to try the timezone. I can't change the time zone from Advanced -> Advanced Setup 2 -> NTP/Timezone. I tried changing to Pacific time and It stayed on Mountain time. I tried reboot and still Mountain time. Also don't see a check box to auto adjust to DST, I think there was one when the timezone setting was in the Security section.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: New firmware with built in Torrent Client
Now tags setting is perfect however it still abort the connection as soon as the PADO is received. Try to find out any code path which is exiting with a sendPADT call leaving no message in /var/log/messages after:
Mar 19 01:25:09 DGND3800B daemon.notice pppd[1934]: PPP: Start to connect ...
If you share the code of this pppd/rp-pppoe with patches I could take a look. I've noticed that all PADTs have a random host_uniq tag, but I have no idea if it is something to worry about or not.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: New firmware with built in Torrent Client
Download code from netgear GPL, pppoe bits in
DGND3800B/userspace/public/apps/ppp/pppoe/plugins/pppoe/
Relevant two files are pppoe.c and libpppoe.c.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: New firmware with built in Torrent Client
Good news, the -d option did a nice job, now we have a clue of what's wrong. It is just claiming about a host_uniq tag mismatch, I'm now mailing you the capture and the debug text, I'll also take a look at the sources.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: New firmware with built in Torrent Client
libpppoe.c, line 479+
/* A HOST_UNIQ must be present */ CHECK_TAG(TAG_HOST_UNIQ,1); // from the top of this file: // #define TAG_DATA(type,tag_ptr) ((type *) ((struct pppoe_tag*)tag_ptr)->tag_data) hu_val = *TAG_DATA(struct session* ,p->tags[TAG_HOST_UNIQ]); // in other words: // hu_val = *( (struct session **) ((struct pppoe_tag*)p->tags[TAG_HOST_UNIQ] )->tag_data ); if( hu_val != ses ){ poe_info(ses,"HOST_UNIQ mismatch: %08x %i\n",(int)hu_val,getpid()); return -1; }
ses is something that identify the pppoe session (memory address of the session structure), and is used around line 402 to fill the host_uniq tag if no tag of that type has been found. Since we set it manually this check should take into account that eventuality.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: New firmware with built in Torrent Client
Two things:
Firstly, I recently switch ISP from an ADSL2+ connection to a Zen VDSL2 fibre connection, and I was able to get it working as a PPPoE connection, VLAN tag 101, VC-based. This only works on the Annex A firmware. Despite this, the advanced page says I am using "Mode: VDSL2 Annex B". I don't understand this, but whatever.
Second, since the switch from PPPoA to PPPoE I have noticed a bug where the router sometimes gets two or more PPP daemons running at the same time. Here are relevant log sections:
Mar 31 20:51:41 dgnd3700.lan pppd[5494]: Clear IP addresses. PPP connection DOWN.
Mar 31 20:52:38 dgnd3700.lan pppd[8584]: PPP: Start to connect ...
Mar 31 20:52:38 dgnd3700.lan pppd[8584]: PPP server detected.
Mar 31 20:52:38 dgnd3700.lan pppd[8584]: PPP session established.
Mar 31 20:52:38 dgnd3700.lan pppd[8584]: PPP LCP UP.
Mar 31 20:52:39 dgnd3700.lan pppd[8584]: PPP LCP UP.
Mar 31 23:27:49 dgnd3700.lan pppd[8584]: Clear IP addresses. PPP connection DOWN.
Mar 31 23:27:50 dgnd3700.lan pppd[9044]: PPP: Start to connect ...
Mar 31 23:27:51 dgnd3700.lan pppd[9044]: PPP server detected.
Mar 31 23:27:51 dgnd3700.lan pppd[9044]: PPP session established.
Mar 31 23:27:51 dgnd3700.lan kernel: PPP: couldn't register device ppp0 (-17)
Mar 31 23:27:54 dgnd3700.lan pppd[9044]: PPP: Start to connect ...
Mar 31 23:27:55 dgnd3700.lan pppd[9044]: PPP server detected.
Mar 31 23:27:55 dgnd3700.lan pppd[9044]: PPP session established.
Mar 31 23:27:55 dgnd3700.lan pppd[9044]: PPP LCP UP.
Mar 31 23:27:55 dgnd3700.lan pppd[8584]: PPP: Start to connect ...
Mar 31 23:27:55 dgnd3700.lan pppd[9044]: PPP LCP UP.
Mar 31 23:28:22 dgnd3700.lan pppd[8584]: PPP: Start to connect ...
Mar 31 23:28:49 dgnd3700.lan pppd[8584]: PPP: Start to connect ...
Mar 31 23:29:15 dgnd3700.lan pppd[8584]: PPP: Start to connect ...
Mar 31 23:29:42 dgnd3700.lan pppd[8584]: PPP: Start to connect ...
Mar 31 23:30:09 dgnd3700.lan pppd[8584]: PPP: Start to connect ...
Mar 31 23:30:36 dgnd3700.lan pppd[8584]: PPP: Start to connect ...
PID 5494 stopped and was replaced first by 8584. That failed, then 9044 started and was able to connect. Then in the background, 8584 kept on trying to connect. This didn't cause any noticable problems, until...
Apr 1 20:51:16 dgnd3700.lan pppd[8584]: PPP: Start to connect ...
Apr 1 20:51:43 dgnd3700.lan pppd[8584]: PPP: Start to connect ...
Apr 1 20:52:10 dgnd3700.lan pppd[8584]: PPP: Start to connect ...
Apr 1 20:52:37 dgnd3700.lan pppd[8584]: PPP: Start to connect ...
Apr 1 20:53:03 dgnd3700.lan pppd[8584]: PPP: Start to connect ...
Apr 1 20:53:30 dgnd3700.lan pppd[8584]: PPP: Start to connect ...
Apr 1 20:53:57 dgnd3700.lan pppd[8584]: PPP: Start to connect ...
Apr 1 20:54:09 dgnd3700.lan pppd[9044]: Clear IP addresses. PPP connection DOWN.
Apr 1 20:54:10 dgnd3700.lan pppd[11915]: PPP: Start to connect ...
Apr 1 20:54:10 dgnd3700.lan pppd[11915]: PPP server detected.
Apr 1 20:54:10 dgnd3700.lan pppd[8584]: PPP server detected.
Apr 1 20:54:10 dgnd3700.lan pppd[11915]: PPP session established.
Apr 1 20:54:10 dgnd3700.lan pppd[8584]: PPP session established.
Apr 1 20:54:10 dgnd3700.lan kernel: PPP: couldn't register device ppp0 (-17)
Apr 1 20:54:10 dgnd3700.lan kernel: PPP: couldn't register device ppp0 (-17)
Apr 1 20:54:13 dgnd3700.lan pppd[11915]: PPP: Start to connect ...
Apr 1 20:54:13 dgnd3700.lan pppd[8584]: PPP: Start to connect ...
Apr 1 20:54:15 dgnd3700.lan pppd[9044]: PPP: Start to connect ...
Apr 1 20:54:16 dgnd3700.lan pppd[8584]: PPP server detected.
Apr 1 20:54:16 dgnd3700.lan pppd[11915]: PPP server detected.
Apr 1 20:54:16 dgnd3700.lan pppd[11915]: PPP session established.
Apr 1 20:54:16 dgnd3700.lan pppd[8584]: PPP session established.
Apr 1 20:54:16 dgnd3700.lan pppd[9044]: PPP server detected.
Apr 1 20:54:16 dgnd3700.lan pppd[9044]: PPP session established.
Apr 1 20:54:16 dgnd3700.lan pppd[11915]: PPP LCP UP.
Apr 1 20:54:17 dgnd3700.lan pppd[11915]: PPP LCP UP.
Apr 1 20:54:19 dgnd3700.lan pppd[8584]: PPP: Start to connect ...
Apr 1 20:54:19 dgnd3700.lan pppd[9044]: PPP: Start to connect ...
Apr 1 20:54:22 dgnd3700.lan pppd[8584]: PPP server detected.
Apr 1 20:54:22 dgnd3700.lan pppd[9044]: PPP server detected.
Apr 1 20:54:22 dgnd3700.lan pppd[8584]: PPP session established.
Apr 1 20:54:22 dgnd3700.lan pppd[9044]: PPP session established.
Apr 1 20:54:22 dgnd3700.lan kernel: PPP: couldn't register device ppp0 (-17)
Apr 1 20:54:22 dgnd3700.lan kernel: PPP: couldn't register device ppp0 (-17)
Apr 1 20:54:25 dgnd3700.lan pppd[8584]: PPP: Start to connect ...
Apr 1 20:54:25 dgnd3700.lan pppd[9044]: PPP: Start to connect ...
Apr 1 20:54:28 dgnd3700.lan pppd[9044]: PPP server detected.
Apr 1 20:54:28 dgnd3700.lan pppd[8584]: PPP server detected.
Apr 1 20:54:28 dgnd3700.lan pppd[9044]: PPP session established.
Apr 1 20:54:28 dgnd3700.lan pppd[8584]: PPP session established.
...9044 had a blip and disconnected. A third PPP process started, while the first two kept on trying to connect also. At this point the internet stopped working entirely until I rebooted the router. Full logs available on request.
PS forgot to mention. I am using the Xmas release.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: New firmware with built in Torrent Client
Have you got both WAN1 and WAN2 enabled? (All the PPPoE is stock on xmas release so its either a bug or config setting.)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: New firmware with built in Torrent Client
Not as far as I know. How would I tell? There doesn't seem to be any way to enable or disable them.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: New firmware with built in Torrent Client
Advanced
Setup
ADSL Setting
Drop down WAN
select WAN2 and enable it
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: New firmware with built in Torrent Client
Thanks. It was enabled, so I disabled it. I'll keep an eye on it for a few days and see if it makes any difference.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: New firmware with built in Torrent Client
OKay disabling WAN2 didn't help. Same thing still happens:
Dec 17 01:00:36 dgnd3700.lan pppd[1713]: pppd 2.4.1 started by root, uid 0
Dec 17 01:00:36 dgnd3700.lan pppd[1713]: PPP: Start to connect ...
Dec 17 01:00:36 dgnd3700.lan pppd[1713]: PPP server detected.
Dec 17 01:00:36 dgnd3700.lan pppd[1713]: PPP session established.
Dec 17 01:00:36 dgnd3700.lan pppd[1713]: PPP LCP UP.
Dec 17 01:00:36 dgnd3700.lan pppd[1713]: PPP LCP UP.
Dec 17 01:00:36 dgnd3700.lan pppd[1713]: Received valid IP address from server. Connection UP.
Dec 17 01:00:41 dgnd3700.lan kernel: abNatUnhook(1595) <Warning> not find ppp0 in nat hooked interface list
Apr 3 20:55:42 dgnd3700.lan pppd[1713]: Clear IP addresses. Connection DOWN.
Apr 3 20:55:43 dgnd3700.lan pppd[1713]: Clear IP addresses. PPP connection DOWN.
Apr 3 20:55:52 dgnd3700.lan pppd[1713]: Exit.
Apr 3 20:56:12 dgnd3700.lan pppd[2063]: pppd 2.4.1 started by root, uid 0
Apr 3 20:56:12 dgnd3700.lan pppd[2063]: PPP: Start to connect ...
Apr 3 20:56:12 dgnd3700.lan pppd[2063]: PPP server detected.
Apr 3 20:56:12 dgnd3700.lan pppd[2063]: PPP session established.
Apr 3 20:56:12 dgnd3700.lan pppd[2063]: PPP LCP UP.
Apr 3 20:56:12 dgnd3700.lan pppd[2063]: PPP LCP UP.
Apr 3 20:56:13 dgnd3700.lan pppd[2063]: Received valid IP address from server. Connection UP.
Apr 3 20:56:17 dgnd3700.lan kernel: abNatUnhook(1595) <Warning> not find ppp0 in nat hooked interface list
Apr 3 21:37:32 dgnd3700.lan pppd[2200]: pppd 2.4.1 started by root, uid 0
Apr 3 21:37:32 dgnd3700.lan pppd[2200]: PPP: Start to connect ...
Apr 3 21:37:33 dgnd3700.lan pppd[2200]: PPP server detected.
Apr 3 21:37:33 dgnd3700.lan pppd[2200]: PPP session established.
Apr 3 21:37:33 dgnd3700.lan kernel: PPP: couldn't register device ppp0 (-17)
Apr 3 21:37:36 dgnd3700.lan pppd[2200]: PPP: Start to connect ...
Apr 3 21:37:37 dgnd3700.lan pppd[2200]: PPP server detected.
Apr 3 21:37:37 dgnd3700.lan pppd[2200]: PPP session established.
Apr 3 21:37:37 dgnd3700.lan kernel: PPP: couldn't register device ppp0 (-17)
Apr 3 21:37:40 dgnd3700.lan pppd[2200]: PPP: Start to connect ...
Apr 3 21:37:40 dgnd3700.lan pppd[2200]: PPP server detected.
Apr 3 21:37:40 dgnd3700.lan pppd[2200]: PPP session established.
Apr 3 21:37:40 dgnd3700.lan kernel: PPP: couldn't register device ppp0 (-17)
Apr 3 21:37:43 dgnd3700.lan pppd[2200]: PPP: Start to connect ...
Apr 3 21:37:44 dgnd3700.lan pppd[2200]: PPP server detected.
Apr 3 21:37:44 dgnd3700.lan pppd[2200]: PPP session established.
Apr 3 21:37:44 dgnd3700.lan kernel: PPP: couldn't register device ppp0 (-17)
... internet is now broken
Apr 3 22:52:40 dgnd3700.lan pppd[2200]: PPP: Start to connect ...
Apr 3 22:52:54 dgnd3700.lan pppd[2063]: Clear IP addresses. Connection DOWN.
Apr 3 22:52:54 dgnd3700.lan pppd[2063]: Clear IP addresses. PPP connection DOWN.
Apr 3 22:53:03 dgnd3700.lan pppd[2063]: Exit.
Apr 3 22:53:24 dgnd3700.lan pppd[4677]: pppd 2.4.1 started by root, uid 0
Apr 3 22:53:24 dgnd3700.lan pppd[4677]: PPP: Start to connect ...
Apr 3 22:53:24 dgnd3700.lan pppd[4677]: PPP server detected.
Apr 3 22:53:24 dgnd3700.lan pppd[2200]: PPP server detected.
Apr 3 22:53:24 dgnd3700.lan pppd[4677]: PPP session established.
Apr 3 22:53:24 dgnd3700.lan pppd[2200]: PPP session established.
Apr 3 22:53:24 dgnd3700.lan pppd[2200]: Exit.
Apr 3 22:53:36 dgnd3700.lan pppd[4677]: PPP: Start to connect ...
Apr 3 22:53:36 dgnd3700.lan pppd[4677]: PPP server detected.
Apr 3 22:53:36 dgnd3700.lan pppd[4677]: PPP session established.
Apr 3 22:53:37 dgnd3700.lan pppd[4677]: PPP LCP UP.
Apr 3 22:53:37 dgnd3700.lan pppd[4677]: PPP LCP UP.
Apr 3 22:53:37 dgnd3700.lan pppd[4677]: Received valid IP address from server. Connection UP.
Apr 3 22:53:41 dgnd3700.lan kernel: abNatUnhook(1595) <Warning> not find ppp0 in nat hooked interface list
... eventually 2200 and 2063 decided to exit. 4677 connects okay.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: New firmware with built in Torrent Client
So here is what I think is happening:
First its WLAN2 was a red herring: it's okay for multiple pppoe session to run, as long as they use different vlan tags, and WLAN2 was set to 8, WLAN1 was set to 101. On "ifconfig" I can see the atm0 and atm0.101, and also atm0.8 if WLAN2 is enabled.
What I think happens is the link goes down and another pppoe spawns. It connects, but the previous one does not exit clean and is holding the atm0.101 (or ppp0) device, so the new one can't create it and just retries in a loop.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: New firmware with built in Torrent Client
I found some more stuff in the logs. This shows side by side a clean and failed restart (right click->view image for bigger):
There is exactly one line in the left log that does not appear at all in the right log:
Apr 4 22:37:25 dgnd3700.lan kernel: [SysLog]: [DSL Event] DSL: Down
This kernel message is simply never printed during a failed restart and it is the first point where something different happens in the logs.
Another thing I noticed is that in the clean restart, that message is printed 1 second after the link goes down. In the failed restart, the link is already back to training after 1 second. So perhaps this is a race condition?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: New firmware with built in Torrent Client
I just caught it with two pppds running at the same time:
5465 root 1628 S pppd -c ppp0 -i atm0.101 -u USERNAME -p PASSWORD -t 1492 -f 0 -k
5705 root 1628 S pppd -c ppp0 -i atm0.101 -u USERNAME -p PASSWORD -t 1492 -f 0 -m SOMENUMBERS -k
Here 5465 is the old one and 5705 is the new one which is failing to connect:
Apr 5 20:25:27 dgnd3700.lan pppd[5705]: PPP session established.
Apr 5 20:25:27 dgnd3700.lan kernel: PPP: couldn't register device ppp0 (-17)
I issued a "kill 5465" and 5705 then connected immediately:
Apr 5 20:26:20 dgnd3700.lan pppd[5465]: Exit.
Apr 5 20:26:21 dgnd3700.lan pppd[5705]: PPP LCP UP.
Apr 5 20:26:21 dgnd3700.lan pppd[5705]: Received valid IP address from server. Connection UP.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: New firmware with built in Torrent Client
@richud In another thread it was mentioned that Centurylink is starting to roll out xDSL vectoring. From what I can find this is defined in ITU-T G.993.5 (Vectoring). I was wondering if your firmware supports this? Thanks
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: New firmware with built in Torrent Client
Hi!
Would it be possible to increase the limit of mac addresses of the wifi access control whitelist? Currently the limit is 32 devices...
I know that mac address spoofing is the easiest thing in the world, but you know....Psicologically it helps! 🙂
Thank you very much!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: New firmware with built in Torrent Client
I came up with a workaround for the duplicate processes:
First I copied /bin to /tmp/mnt/storage/bin.
cp -a /bin /tmp/mnt/storage/bin
Then I bind-mounted the copy back over the original:
mount -o bind /tmp/mnt/storage/bin /bin
Then I moved pppd to pppd.real, and put this script in place of pppd:
#!/bin/sh ARGS=$* while [ "$1" != "" ]; do case $1 in -c) DEVICE=$2 ;; -i) INTERFACE=$2 ;; esac shift done logger "Killing stray pppd processes." pkill -f "pppd.real -c $DEVICE -i $INTERFACE" exec pppd.real $ARGS
This script kills any existing copies of pppd.real before launching a new one, but only if they were started on the same devices. This won't work properly if using IPv6 because pppdv6 is a symlink to pppd and it will get confused.
This workaround could be improved if busybox 1.26.0 was available, as it supports exec -a.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: New firmware with built in Torrent Client
Not sure it's already covered - but when running a OpenVPN Client on the router, it appears traffic originating from the LAN side is not being NATed when heading down the tun0 adapter.
Thus when a LAN client pings the internet (e.g. 8.8.8.8) you can see the ping head out tun0, but the source IP is the 192.168.0/24 subnet rather than the router's IP - thus no reply is forthcoming.
Is there any way to create appropriate NAT rules for the tun0 adapter?
[yes, NATing appears to work appropriate in non-vpn operation]
cheers 🙂
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Rif.: New firmware with built in Torrent Client
hi, today my dgnd3700 stop to work...
power led go fixed amber
I used from years with your firmwares, without any problems
last fw charged in my device was 2016-04-10
used for some months, all seems work excelent
today i got the power led amber
turn off some minutes and turn on again various times
led of wi-fi-lan-line go green about a minute, then power led go amber again
reset doesn.'t solve, tried hard reset using back switch some times. but nothing....
any idea?
regards
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Rif.: New firmware with built in Torrent Client
new release: https://mega.nz/#!1JQGhTJD!NgB2RR42Ke1YTrvOWERBIvPSFokhSsWYLViVPzRcSyg
- Working on all 3800 models (hopefully).
- hostname assigning with DHCP fixed
- adblock white/blacklist character limit increased
- NTP timezone sets all system time properly.
- PPPoE modified to add host uniq feature setting. (lucca request)
- minor fixes and updates of software
w3: yes it should if you enable SRA and G.INP in the advanced adsl options
• What is the difference between WiFi 6 and WiFi 7?
• Yes! WiFi 7 is backwards compatible with other Wifi devices? Learn more