Print

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

[FurryNutz]

Firmware: v1.20 B06   07/10/2019
Revision Info
Problems Resolved:   
- 1. Fixed the problem that SG CountryCode Code Setting Operator's Preservation is not effective
- 2. Fixed the problem that EU VLAN of IPTV and VOIP Interfaces cannot be set to bridge mode.
- 3. The latest SKU tables incorporating Indian country code

- 1. WEB GUI is updated to SVN1449.
- 2. Support the Vlan function of China Telecom.
- 3. Solve the problem that the long lease period of DHCPv6 server on d-track device leads to abnormal radvd process and the client can't get the IPv6
address.
- 4. Solve a quickvpn problem raised by D-trace. When SPI is turned on, the quickvpn dialing of IOS mobile phone fails.
- 5. Remove device startup and send igmpv2 message to solve the problem of IPTV playback in Singapore
- 6.Modify the channel list corresponding to the IN country code according to the document <PSD-001-01009_D-Link Wi-FI frequency
table_20190102.pdf>
- 7.Resolve the problem of IPTV stop broadcasting after 5 minutes in Vietnam

Enhancements:
A. 160Mhz channel width support added on 5Ghz. 
- 1. WEB GUI is updated to SVN1196.
- 2. Support the Vlan function of China Telecom.
- 3. Support for new spec functionality


Known Issues:
None.

Get it here: NA Region
DIR-882-US

Please follow the> FW Update Process to ensure a good FW upgrade is performed.

Let us know how it works for you...

Note: You MUST reset the router after the firmware upgrade since there were a lot of code changes. If you are experiencing slow speeds and connection drops, reset the router.

[__fastcgi]

Hello there

Recently I've updated to this version and I got this small issue:

[FurryNutz]

Link>Welcome!

• What region are you located?

Interesting.
What browser are you using?

• Has a Factory Reset been performed?

Hello there

Recently I've updated to this version and I got this small issue:

[FurryNutz]

Are you still seeing this? I checked mine and didn't see this.

Hello there

Recently I've updated to this version and I got this small issue:

[GreenBay42]

I got word back from HQ. They decided to take the Captcha feature out of 1.20. I did not get a specific reason but in any case it is no longer there.

They also stated users need to reset the router after installing 1.20.  I wish they would have put that in the release notes....

[FurryNutz]

Was that when v1.20 first appeared in the FW update on the router when it was removed?

Ya, I presume lingering code may have been still present. Of I didn't see this at all when v1.20 first appeared so maybe the update I did cleared it all out as I did the update via UI and continued and did not factory reset till later on.

I got word back from HQ. They decided to take the Captcha feature out of 1.20. I did not get a specific reason but in any case it is no longer there.

They also stated users need to reset the router after installing 1.20.  I wish they would have put that in the release notes....

[2kreative]

Has anyone noticed a crazy amount of DNS requests being generated by the 882 on the new firmware? It's pretty much causing a DoS on my PiHole server.


The drop off on the graph is me reverting back to 1.11, the spike is back on 1.20 and back again to 1.11.

Here is a sample of the requests, it seems to be generating DNS queries for wpad.dlinkrouter and all the local devices constantly

Aug  2 19:17:01 dnsmasq[8644]: query[A] wpad.dlinkrouter from 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: forwarded wpad.dlinkrouter to 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: query[AAAA] wpad.dlinkrouter from 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: forwarded wpad.dlinkrouter to 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: query[AAAA] wpad.dlinkrouter from 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: forwarded wpad.dlinkrouter to 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: query[A] wpad.dlinkrouter from 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: forwarded wpad.dlinkrouter to 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: query[A] wpad.dlinkrouter from 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: forwarded wpad.dlinkrouter to 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: query[PTR] 125.0.168.192.in-addr.arpa from 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: forwarded 125.0.168.192.in-addr.arpa to 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: query[AAAA] wpad.dlinkrouter from 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: forwarded wpad.dlinkrouter to 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: query[PTR] 125.0.168.192.in-addr.arpa from 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: forwarded 125.0.168.192.in-addr.arpa to 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: query[A] wpad.dlinkrouter from 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: forwarded wpad.dlinkrouter to 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: query[AAAA] wpad.dlinkrouter from 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: forwarded wpad.dlinkrouter to 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: query[A] wpad.dlinkrouter from 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: forwarded wpad.dlinkrouter to 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: query[PTR] 137.0.168.192.in-addr.arpa from 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: forwarded 137.0.168.192.in-addr.arpa to 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: query[A] wpad.dlinkrouter from 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: forwarded wpad.dlinkrouter to 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: query[A] wpad.dlinkrouter from 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: forwarded wpad.dlinkrouter to 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: query[AAAA] wpad.dlinkrouter from 192.168.0.1
Aug  2 19:17:01 dnsmasq[8644]: forwarded wpad.dlinkrouter to 192.168.0.1

I've performed a factory reset and upgraded via router UI.

[FurryNutz]

Is DNS relay enabled on the 882?

What is this app your using to see this?

[2kreative]

Yes relay is enabled

This is my PiHole DNS server. Do you have a DIR-882 running firmware 1.20?

[me_iauras]

https://en.wikipedia.org/wiki/Web_Proxy_Auto-Discovery_Protocol requests is more likely generated by your local LAN clients and the router is just forwarding those requests since you have DNS relay activated.
I too am doing basic AdBlocking with a PiHole on my LAN but I've turned off DNS relay so the DNS server of my clients is the PiHole VM not the router , therefore I can monitor/see the requests of each client individually .
Are you using the PiHole as the DHCP server also because that is when the clients (mostly Windows) normally make requests for the WPAD configuration file . Also from your screenshot there is a strange thing ; clients seem to be doing DNS queries to both the router ( since you have so many dlinkrouter entries)  but also many queries directly from the clients. In my case (router is DHCP server but DNS relay is off , PiHole is the DNS server of each individual client) the router has barely any DNS queries (<10) compared to many from the clients (hundreds or thousands depending on the client (10.10.10.1 is the router)

https://imgur.com/CLROjyj

Also on a totally unrelated note even though I have the <Auto Upgrade> feature turned off this is what my SysLog server receives every night at the same time :
2019-08-03 03:47:57 FOTA[19052]: fota_config.c, fota_init_config, 322:
2019-08-03 03:47:57 FOTA[19052]: CA certificate is not set, use default file: /etc_ro/cacert.pem.
2019-08-03 03:47:57 FOTA[19052]: fota_config.c, fota_init_config, 335:
2019-08-03 03:47:57 FOTA[19052]: firmware encryption flag is on.
2019-08-03 03:47:57 FOTA_CONFIG[19062]: mtk/fota_generate_config.c, main, 1060:
2019-08-03 03:47:57 FOTA_CONFIG[19062]: Execute config ACTION: config.
2019-08-03 03:47:57 FOTA_CONFIG[19062]: mtk/fota_generate_config.c, action_config, 779:
2019-08-03 03:47:57 FOTA_CONFIG[19062]: Now start generating the configuration file.
2019-08-03 03:47:57 FOTA_CONFIG[19062]: mtk/fota_generate_config.c, main, 1068:
2019-08-03 03:47:57 FOTA_CONFIG[19062]: Done.
2019-08-03 03:47:57 FOTA[19052]: fota.c, main, 1357:
2019-08-03 03:47:57 FOTA[19052]: Execute ACTION: auto.
2019-08-03 03:47:57 FOTA[19052]: fota.c, query_latest_firmware_info, 83:
2019-08-03 03:47:57 FOTA[19052]: Now check with the server for the latest firmware information.
2019-08-03 03:47:58 FOTA[19052]: fota_api_curl.c, get_http_response_code, 167:
2019-08-03 03:47:58 FOTA[19052]: iHttp_code=401.
2019-08-03 03:47:58 FOTA[19052]: fota.c, query_latest_firmware_info, 106:
2019-08-03 03:47:58 FOTA[19052]: Http code: 401, Error code: 111, error message: Invalid access token..
2019-08-03 03:47:58 FOTA[19052]: fota_api.c, refresh_access_token, 214:
2019-08-03 03:47:58 FOTA[19052]: Now REFRESH the access token.
2019-08-03 03:47:59 FOTA[19052]: fota_api_curl.c, get_http_response_code, 167:
2019-08-03 03:47:59 FOTA[19052]: iHttp_code=200.
2019-08-03 03:47:59 FOTA[19052]: fota_api.c, refresh_access_token, 248:
2019-08-03 03:47:59 FOTA[19052]: REFRESH the access token success.
2019-08-03 03:47:59 FOTA[19052]: fota.c, query_latest_firmware_info, 83:
2019-08-03 03:47:59 FOTA[19052]: Now check with the server for the latest firmware information.
2019-08-03 03:48:00 FOTA[19052]: fota_api_curl.c, get_http_response_code, 167:
2019-08-03 03:48:00 FOTA[19052]: iHttp_code=200.
2019-08-03 03:48:00 FOTA[19052]: fota.c, query_latest_firmware_info, 116:
2019-08-03 03:48:00 FOTA[19052]: QUERY the latest firmware information success.
2019-08-03 03:48:00 FOTA[19052]: fota.c, automatic_firmware_update, 863:
2019-08-03 03:48:00 FOTA[19052]: Automatic firmware download is not enable.
2019-08-03 03:48:00 FOTA_OUTPUT[19087]: mtk/fota_output.c, main, 324:
2019-08-03 03:48:00 FOTA_OUTPUT[19087]: Now processing the result of ACTION: auto.
2019-08-03 03:48:01 FOTA_OUTPUT[19087]: mtk/fota_output.c, handle_action_auto, 85:
2019-08-03 03:48:01 FOTA_OUTPUT[19087]: 'pUpdate_done_notify' is null pointer.
2019-08-03 03:48:01 FOTA_OUTPUT[19087]: mtk/fota_output.c, main, 329:
2019-08-03 03:48:01 FOTA_OUTPUT[19087]: The value of 'iRet' is not OK.
2019-08-03 03:48:01 FOTA[19052]: fota.c, fota_output_action, 1323:
2019-08-03 03:48:01 FOTA[19052]: Child fail! Exit code 255.
2019-08-03 03:48:01 FOTA[19052]: fota.c, main, 1419:
2019-08-03 03:48:01 FOTA[19052]: The value of 'iRet' is not OK.

The router incorrectly checks every night @ 00:47 UTC for a firmware update even though that option is not enabled in the settings . It doesn't really cause any issues but it's still a bug and it should be taken into account for future builds as to be fixed .

[2kreative]

My screenshot is showing Relay Off as you can see each of the individual clients, relay on occurred after I did a factory reset of settings and you can see the second spike of requests just after midnight.

It's possible I'm on a sightly different firmware as I've a DIR-882 UK/EU router?

[me_iauras]

As I've said the WPAD request are from LAN clients not the router itself (or so it should be); I suggest that after you turn off the DNS relay feature to monitor the individual clients in the PiHole log to see whichever one is responsible for them .
I too am on the EU side of the pond and there is a single v1.20 version available worldwide as far as I am aware of ; you can verify it by going to < https://dlinkrouter.local/version.txt > (after you've logged in to the router obviously) and I'll bet it's < Firmware Internal Version:    V1.20B06 >

Personally I don't seem to be having this kind of requests  ( only 2 win10 clients on my network though ):
xxxxxxx@pi-hole:~$ cat /var/log/pihole.log | grep wpad >> the result is empty (if you're monitoring a different .log file tell me because as far as I'm aware this is the default pihole dnsmasq file)

Also I've monitored a Win 10 build 1809 VM boot up and Edge browser launch with no WPAD request whatsoever .

[2kreative]

So... FW 1.11, factory reset, enable PPPoE, enable VLAN 10,  grabbed new firmware (decided to do the manual update).

Firmware Externel Version   V1.20
Firmware Internal Version:   V1.20B06
Date:   2019-05-16 13:06:37
Checksum   7CC28308

Flashed, factory reset, enable PPPoE, enable VLAN 10, enabled Wifi. Disabled DNS relay, flushed logs in PiHole and getting bombarded with requests from the Dlink again





edit: after a few mins



Sample of requests

Aug  4 00:18:42 dnsmasq[17979]: forwarded 125.0.168.192.in-addr.arpa to 192.168.0.1
Aug  4 00:18:42 dnsmasq[17979]: query[PTR] 72.0.168.192.in-addr.arpa from 192.168.0.1
Aug  4 00:18:42 dnsmasq[17979]: forwarded 72.0.168.192.in-addr.arpa to 192.168.0.1
Aug  4 00:18:42 dnsmasq[17979]: query[PTR] 72.0.168.192.in-addr.arpa from 192.168.0.1
Aug  4 00:18:43 dnsmasq[17979]: forwarded 72.0.168.192.in-addr.arpa to 192.168.0.1
Aug  4 00:18:43 dnsmasq[17979]: query[PTR] 125.0.168.192.in-addr.arpa from 192.168.0.1
Aug  4 00:18:43 dnsmasq[17979]: forwarded 125.0.168.192.in-addr.arpa to 192.168.0.1
Aug  4 00:18:43 dnsmasq[17979]: query[PTR] 71.0.168.192.in-addr.arpa from 192.168.0.1
Aug  4 00:18:43 dnsmasq[17979]: forwarded 71.0.168.192.in-addr.arpa to 192.168.0.1
Aug  4 00:18:43 dnsmasq[17979]: query[PTR] 134.0.168.192.in-addr.arpa from 192.168.0.1
Aug  4 00:18:43 dnsmasq[17979]: forwarded 134.0.168.192.in-addr.arpa to 192.168.0.1
Aug  4 00:18:43 dnsmasq[17979]: query[PTR] 71.0.168.192.in-addr.arpa from 192.168.0.1
Aug  4 00:18:43 dnsmasq[17979]: forwarded 71.0.168.192.in-addr.arpa to 192.168.0.1
Aug  4 00:18:43 dnsmasq[17979]: query[PTR] 125.0.168.192.in-addr.arpa from 192.168.0.1
Aug  4 00:18:43 dnsmasq[17979]: forwarded 125.0.168.192.in-addr.arpa to 192.168.0.1
Aug  4 00:18:50 dnsmasq[17979]: query[PTR] 72.0.168.192.in-addr.arpa from 192.168.0.1
Aug  4 00:18:50 dnsmasq[17979]: forwarded 72.0.168.192.in-addr.arpa to 192.168.0.1
Aug  4 00:18:50 dnsmasq[17979]: query[PTR] 72.0.168.192.in-addr.arpa from 192.168.0.1
Aug  4 00:18:50 dnsmasq[17979]: forwarded 72.0.168.192.in-addr.arpa to 192.168.0.1
Aug  4 00:18:50 dnsmasq[17979]: query[PTR] 125.0.168.192.in-addr.arpa from 192.168.0.1
Aug  4 00:18:50 dnsmasq[17979]: forwarded 125.0.168.192.in-addr.arpa to 192.168.0.1
Aug  4 00:18:50 dnsmasq[17979]: query[PTR] 71.0.168.192.in-addr.arpa from 192.168.0.1
Aug  4 00:18:50 dnsmasq[17979]: forwarded 71.0.168.192.in-addr.arpa to 192.168.0.1
Aug  4 00:18:50 dnsmasq[17979]: Maximum number of concurrent DNS queries reached (max: 150)

[me_iauras]

Yea , so your configuration mimics mine exactly except for the VLAN part ; I assume that the VLAN 10 is for IPTV  or VoIP service purposes( otherwise I see no rational reason whatsoever to have a VLAN enabled if only Internet service is provided on the WAN interface link ).
Only other source I might think would generate such traffic would be your smart assistants  (those amazon devices I will presume that are Amazon Alexa enabled speakers) ; one role of PiHole is to block phone home/tracking URLs ( which again considering Amazon's business model I presume are doing a lot off data mining to make their pricing of these devices make sense ) so my supposition is that they're doing WINS requests to the router to map the network ( what clients are .71 , .72 and .105 >> .71/72 seem to be static allocations as they are out of the DHCP server IP range which is served to DHCP clients ). There's also that client which doesn't really identifies itself to the router (MAC address one 09aa01.. , probably a chinesium smart IoT device) which I suspect might be doing some not OK requests (due to it being apparently so badly configured as to not having a hardware vendor specific MAC address ).
Anyhoo in my own situation ( router is DHCP server with PiHole DNS server and : 2 Win clients , 3 Android devices , 1 "Smart TV" , 1 NAS  , 1 Ubuntu x86 VM based PiHole ) I don't seem to be having the same requests so maybe by process of elimination you might identify your culprit.

[2kreative]

VLAN 10 is required by my ISP for Internet services - otherwise no connectivity.
The crux of the matter is that traffic is not generated on any firmware version up to 1.11. Only 1.20 seems to have the aforementioned result.

I guess next step is process of elimination,