July 21, 2018 at 12:27 am #1225
I have logged a few requests for help, but still having issues with my OG device. It worked great for some time but now very unresponsive – best to describe it is if you were right on the edge of your Wifi signal and having a huge packet loss.
Nothing has changed and when it was working – it was great and stable. Now it cannot even connect to Blynk and if I use it on the local network is feels like I described earlier.
Anyway. I decided to do a tcpdump on my wifi router to see what is going on with it.
See below for the few snippets of the output:
13:19:35.858743 IP 192.168.1.201.4096 > resolver1.opendns.com.domain: 193+ A? time.nist.org. (31)
13:19:35.859119 IP resolver1.opendns.com.domain > 192.168.1.201.4096: 198* 1/0/0 A 10.0.0.1 (47)
13:19:41.033358 IP 192.168.1.201.4096 > resolver1.opendns.com.domain: 29+ A? blynk-cloud.com. (33)
13:19:41.033912 IP resolver1.opendns.com.domain > 192.168.1.201.4096: 29* 1/0/0 A 10.0.0.1 (49)
13:19:41.035558 IP 192.168.1.201.21502 > 10.0.0.1.8442: Flags [S], seq 6035785, win 5840, options [mss 1460], length 0
192.168.1.201 is the IP address as it is set on the OG as a static address. OG does not have an option to set DNS server IP, and it tries to connect to resolver1.opendns.com. But how does it know what IP address is that? And why does it get 10.0.0.1 as a returned IP? Is the the default if it fails?
Ray, can you check it out?August 17, 2018 at 3:09 pm #1237
We can probably add an option to customize the DNS IP as well. But generally we don’t recommend setting static IP on Opengarage — I know this is provided as an option, but we recommend you to use the DHCP reservation feature on your router to assign a fixed IP to the device. This way the DNS IP is assigned by the router and you don’t have to put it in manually on Opengarage.August 20, 2018 at 10:01 pm #1266
I usually do set to DHCP, but when things have issues with router/wifi compatibility you’d want to set it to manual. If you can add it to the next release that would be great! Maybe also add the NTP settings too.
Not everyone runs it internet connected and if it cannot get to somewhere it keeps trying, which makes it very unresponsiveAugust 28, 2018 at 3:24 pm #1279
You said “Not everyone runs it internet connected” — but I don’t understand the point of using OpenGarage if it’s not Internet connected — I mean, without the ability to remotely monitor and control the door, how is this different from a standard, non-WiFi based garage door remote?August 28, 2018 at 5:14 pm #1282
I suspect “internet connected” means to the internet at large as opposed to just the local home network. I use mine this way sandboxed in an isolated vlan where it can respond to local net requests but not initiate them. The one exception is I allow it to the internet for dest port 123 so it can get the time. I could run a local NTP server but there is no way to specify that to the OG which I think fokcuk is referencing.
You must be logged in to reply to this topic.