Print

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

[hilaireg]

Finally getting around to reviewing the DIR logs for anomalies ... anyone else seeing tons of these types of entries in their logs?

Cheers,

Code: [Select]

2020-07-02 14:44:37 syslog: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:26 Err:-1 Errno:0 Success
2020-07-02 14:44:37 syslog: dnssd_clientstub DNSServiceRefDeallocate called with NULL DNSServiceRef
2020-07-02 14:44:40 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
2020-07-02 14:44:41 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
2020-07-02 14:44:42 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3

[Valthanis]

Yep... over and over. Not quite sure what that means though.

[FurryNutz]

Does this happen with prior version of FW?

Something to contact D-Link support about....

[hilaireg]

Yep ... been consistent since F/W: 1.01B01, 1.02B03.

Takes too long to reach support and I've yet to ever receive a knowledgeable technician on the line and sadly, yet to ever have a problem resolved ... hence my post to the forums.  BTW, thanks for putting up the forum for the DIR-3040.

Cheers,

[FurryNutz]

Try the chat support if there is one available.

[hilaireg]

The behaviours noted in this thread are *exactly* the anomalies I'm experiencing ...

http://forums.dlink.com/index.php?topic=75268.0

I'm intermittently seeing issues on my MacBook Pro, specifically on google.com and www.google.com not being able to resolve. I've tried setting Cloudflare DNS (1.1.1.1 / 1.0.0.1) and Google DNS (8.8.8.8 / 8.8.4.4) on the router and separately also on the MacBook. This did not help at all. It's not browser related; it happens when I ping said domains, and same result from Chrome / Safari.

I've not had issues on my phone (Google Pixel), except for occasionally reporting that my Wi-Fi doesn't have internet, while the connection seems just fine.

I've restarted the router an hour ago, so far no issues (although the log entries immediately showed up again).

In general, the issues seems to only be around google.com and www.google.com not being able to resolve. Otherwise it works well.

[FurryNutz]

Please let D-Link support know about this.

[hilaireg]

I've disabled UPnP on the DIR and am going to monitor the behaviour to see if that remedies the issues I noted in the previous post.  Still seeing the MDNSD related issues ... I'll see what the root cause is on that afterwards. 

I don't think it's DNS Relay related.

Cheers,


*UPDATE*

Disabling UPnP resulted in no improvement.  Disabled "Energy Efficient Ethernet" on the switch; that seems to have made a noticeable improvement on the MacBook - i.e. haven't seen the intermittent DNS resolve issue or the file hosting download failures.

The Syslog errors are still present however.

[FurryNutz]

Keep in touch with D-Link support about this...

[hilaireg]

*UPDATE*

I've been monitoring the intermittent "fail to resolve webpage" issue and am noticing that it seems to occur when the DIR-3040 appears to be checking for firmware updates ... even though I've disabled the Automatic Firmware Update. 

Although disabling "Green Ethernet" helped with other connectivity related on the MacBook, the "fail to resolve webpage" would still occur - albeit less frequently.  On WinOS, the browser (IE, FireFox, Edge) would "stall" for a moment but finally resolve.

Code: [Select]

2020-08-08 21:34:49 FOTA[28268]: fota_config.c, fota_init_config, 322:
2020-08-08 21:34:49 FOTA[28268]: CA certificate is not set, use default file: /etc_ro/cacert.pem.
2020-08-08 21:34:49 FOTA[28268]: fota_config.c, fota_init_config, 335:
2020-08-08 21:34:49 FOTA[28268]: firmware encryption flag is on.
2020-08-08 21:34:49 FOTA_CONFIG[28269]: mtk/fota_generate_config.c, main, 1063:
2020-08-08 21:34:49 FOTA_CONFIG[28269]: Execute config ACTION: config.
2020-08-08 21:34:49 FOTA_CONFIG[28269]: mtk/fota_generate_config.c, action_config, 778:
2020-08-08 21:34:49 FOTA_CONFIG[28269]: Now start generating the configuration file.
2020-08-08 21:34:49 FOTA_CONFIG[28269]: mtk/fota_generate_config.c, main, 1071:
2020-08-08 21:34:49 FOTA_CONFIG[28269]: Done.
2020-08-08 21:34:49 FOTA[28268]: fota.c, main, 1348:
2020-08-08 21:34:49 FOTA[28268]: Execute ACTION: query.
2020-08-08 21:34:49 FOTA[28268]: fota.c, query_latest_firmware_info, 83:
2020-08-08 21:34:49 FOTA[28268]: Now check with the server for the latest firmware information.
2020-08-08 21:34:50 FOTA[28268]: fota_api_curl.c, get_http_response_code, 167:
2020-08-08 21:34:50 FOTA[28268]: iHttp_code=401.
2020-08-08 21:34:50 FOTA[28268]: fota.c, query_latest_firmware_info, 106:
2020-08-08 21:34:50 FOTA[28268]: Http code: 401, Error code: 111, error message: Invalid access token..
2020-08-08 21:34:50 FOTA[28268]: fota_api.c, refresh_access_token, 214:
2020-08-08 21:34:50 FOTA[28268]: Now REFRESH the access token.
2020-08-08 21:34:50 FOTA[28268]: fota_api_curl.c, get_http_response_code, 167:
2020-08-08 21:34:50 FOTA[28268]: iHttp_code=200.
2020-08-08 21:34:50 FOTA[28268]: fota_api.c, refresh_access_token, 248:
2020-08-08 21:34:50 FOTA[28268]: REFRESH the access token success.
2020-08-08 21:34:50 FOTA[28268]: fota.c, query_latest_firmware_info, 83:
2020-08-08 21:34:50 FOTA[28268]: Now check with the server for the latest firmware information.
2020-08-08 21:34:50 FOTA[28268]: fota_api_curl.c, get_http_response_code, 167:
2020-08-08 21:34:50 FOTA[28268]: iHttp_code=200.
2020-08-08 21:34:50 FOTA[28268]: fota.c, query_latest_firmware_info, 116:
2020-08-08 21:34:50 FOTA[28268]: QUERY the latest firmware information success.
2020-08-08 21:34:50 FOTA[28268]: fota.c, select_firmware_version, 442:
2020-08-08 21:34:50 FOTA[28268]: Now CHOOSE a viable firmware version.
2020-08-08 21:34:50 FOTA[28268]: fota.c, check_enforced_version, 411:
2020-08-08 21:34:50 FOTA[28268]: Now check enforced version.
2020-08-08 21:34:50 FOTA[28268]: fota.c, check_enforced_version, 425:
2020-08-08 21:34:50 FOTA[28268]: 'pEnforced_exist' is null pointer.
2020-08-08 21:34:50 FOTA[28268]: fota.c, select_firmware_version, 488:
2020-08-08 21:34:50 FOTA[28268]: Select upgrade stable firmware.
2020-08-08 21:34:50 FOTA[28268]: fota.c, select_firmware_version, 502:
2020-08-08 21:34:50 FOTA[28268]: No newer firmware is available.
2020-08-08 21:34:50 FOTA[28268]: fota.c, main, 1401:
2020-08-08 21:34:50 FOTA[28268]: The value of 'iRet' is not OK.
2020-08-08 21:34:50 FOTA[28268]: fota.c, main, 1439:
2020-08-08 21:34:50 FOTA[28268]: old hnf=false
2020-08-08 21:34:50 syslog: fota_common.c, fota_unlock, 331:
2020-08-08 21:34:50 syslog: fota lock is uninitialized, no need to unlock.


[FurryNutz]

IF it's anything similar to this:
http://forums.dlink.com/index.php?topic=75430.0

Please make contact and email D-Link support.

[hilaireg]

IF it's anything similar to this:
http://forums.dlink.com/index.php?topic=75430.0

Please make contact and email D-Link support.

Yep, the errors that appear in SYSLOG certainly are although I'm not experiencing the restart issues ... mind you, WiFi on the DIR-3040 is disabled as I use AP's.

I was unable to resolve "www.google.com" at approximately 21:34 on 08/08/2020 and noticed that the log contained the entries that I posted.  So I'm not going to bother as I just don't have that much time available these days.  IMHO, D-Link Support should be actively reviewing these forums.

As for contacting D-Link Support, the results are pretty much as the OP posted in his/her thread - useless and not worth the aggravation; phone or chat.  It's too bad you don't work at D-Link engineering ... I'd have more confidence the issue would be addressed. 

[FurryNutz]

I would send the email to the support address I posted and let them know what you're seeing. The more users post or let D-Link know about it, the more apt they will take action. Hopefully they will get it fixed in next FW update.

[FurryNutz]

Here is what I got from D-Link support about these log entries:
"Date of Reply: 8/10/2020 2:54:17 PM

Products: DIR-2680-US

I have been told that it is just some debugging info that is leaked into the syslog that will be removed in the next firmware release. It is nothing to be concerned about. "

[hmatrix]

Just got the DIR-3040 and observed like most people here the famous error "Syslog:..."

As a dev, I went and see where that error is coming from as the code used by Dlink is from open source.  I found Dlink uses mdnsResponder
you can see when looking at messages file you downloaded
20150 admin     1324 S    mDNSResponder -b -i br0 -f /tmp/mdns_resp.conf -e dl

In mDNSResponder is Apple implementation of their Bonjour thing, you know all the mDNS stuff that flood your network 8-)
From one of github for mDNSResponder like https://github.com/freenas/mDNSResponder
So the error is coming from the file
https://github.com/freenas/mDNSResponder/blob/freenas/master/mDNSShared/dnssd_clientstub.c

it looks like the mdnsresponder is trying to connect to another daemon locally 'mdnsd' which is not there thus the error is printed out.

The usual linux distro like Ubuntu, Redhat... they don't use mDNSResponder, they use a newer implementation of Bonjour/DNS-SD under the name of 'avahi-daemon', in fact people recommend to use avahi instead of mdnsresponder, the fact that Ubuntu is using it gives a good level of confidence.

I read elsewhere in this thread that Dlink will remove that error message as a fix 8-) LoL.

Anyhow, mDNS stuff is used by Chromecast, which I have an issue now, after sometime the phone or ipad stop seeing the chromecast icon, to recover I have to change something on the wifi and save to kick out all clients and reconnect, so clients can now see chromecast back, kind of suck as work around for now.

If any of you use chromecast and notice anything suspicious please chime in.

And lastly, the DIR-3040 has 3 radios, which is great but again create issue if all radio use the same ssid and chromecast connect to a radio but the clients elsewhere, chromecast will not show up, after many days I found chromecast must be on the same radio as the clients who which to cast to it, again sucky problem, I end up creating 3 differents ssid 8-( 

Cannot believe this router has not been tested that well, and this router is not cheap one.

Amen.