Unfortunately, in my case, whatever I do, DNS stops working after 10 to 20 minutes.
So for example changing DNS to 188.8.131.52 is a very temporary solution. It seems that any network change (disconnecting cable, changing IP etc.) restores DNS temporarily.
Sense _was_ working nicely for a couple of weeks. In desperation I first connected Sense to my existing Wifi network and the also connected WAN port to my cable modem. In my opinion, that could at best mess things up, but surprisingly Sense worked perfectly. Could have been some other reason for that...
Yesterday I changed back to 'normal' configuration.
Clients I have used: Samsung S8+, Huawei P8 Lite, Huawei Mediapad M3 Lite, Microsoft Surface Pro 4 (cable connection and Wifi)
Luckily I only have the issue with the Garmin watch, and I can sync it via Bluetooth, but it is still frustrating as that is not as convient as the WLAN syncing.
I'm still pretty convinced that it is related to ARP, since if you look at my previous dump, the Garmin responds to ARP requests but SENSE continues to request the MAC address:
09:44:44.628486 ARP, Request who-has 192.168.71.1 tell 192.168.71.110, length 28 09:44:44.629365 ARP, Reply 192.168.71.1 is-at f0:27:45:00:5e:71 (oui Unknown), length 46 09:44:44.631492 ARP, Request who-has 192.168.71.1 tell 192.168.71.110, length 28 09:44:44.632042 ARP, Reply 192.168.71.1 is-at f0:27:45:00:5e:71 (oui Unknown), length 46 09:44:44.633193 IP 192.168.71.110.50731 > 192.168.71.1.domain: 16275+ A? time-c.nist.gov. (33) 09:44:44.958584 ARP, Request who-has 192.168.71.110 (Broadcast) tell 192.168.71.1, length 46 09:44:45.055437 ARP, Reply 192.168.71.110 is-at 14:8f:21:d8:0a:b6 (oui Unknown), length 28
The SENSE wouldn't do that it if gets the ARP reply and it updates its ARP table.
I believe I could figure out the difference between the watch and other devices with a few hours of work, but then I would hope to get compensated if I succeed. ;-)
Sure, I get it.
But the thing is, as you said, this could be figured out in a matter of hours if put some effort to it.
But I literally have no interest nor energy to put my time to this. I'm working as a systems specialist/administrator, so I have to investigate these things at work anyway.
I do not want to do that when I get home, and I paid for the device and service and I expect to get support for this.
So what I expect from F-Secure is to get some support personnel to tell me which commands to run and then I will mindlessly copy-paste them and send the output to them, so they can do the same work as I do every day at the office, which I get paid for :)
If I would still have time for this, as I used to when studying, I would be still running dd-wrt. But I don't, and that's why I invested into this product. Sad to see that the support level seems to in par with other F-Secure products. Please, prove me wrong.
Thanks for the extensive investigation and apologies, this has somehow fallen between the cracks. I'll raise the priority of this. I cannot promise a solution will make the next firmware release which is coming 'soon', but once we are able to reproduce the problem we can attempt to fix it for the next one.
Simo / SENSE QA Lead
My situation is as described earlier:
- connect directly to WAN with cable: DNS does not work after about 10 minutes
- connect as a Wifi extender to existing home Wifi: DNS stops working after about 10 minutes
- connect first as a Wifi extender and then also connect WAN cable: DNS works as it should.
Cannot explain why the last setup works, but I'm done with experimenting. Sense has been online with Wifi/WAN config for about a week.
Thanks for the additional information,
We made an improvement / fix to the DNS discovery logic and handling of upstream DNS servers. While we have not yet reproduced the exact issue, hopefully it helps your scenario. This should still make it for the next firmware release which goes into release testing very soon.
We'll continue looking into the reported ARP problem.
Simo / SENSE QA Lead
Could this possibly be the cause of the Arlos disconnecting all the time that F-Secure has been ignoring?
This topic has been closed due to inactivity. If you would like to discuss this topic further, please start a new post.
You can reference this topic in your post by adding this link:
Visit the Community
Check our Forums or How-to & FAQs for advice or answers
View User Guides
Refer to our getting started guides and product manuals
Talk to our Support and get answers to your questions