February-7th-2018, 06:56 PM
Initially, when I connected my new NetPI3 to my LAN, I wasn't able to access it by the described instructions (opening the browser and enter the "name" mentioned on the sticker). I also couldn't "ping" it because the "name" could not be resolved.
After some debugging, I could resolve the issue by reconfiguring my router (pfsense): The DHCP-Server didn't automatically update the DNS entries. I can't remember the very details, because already some days past since then, but may claim is: I think that the way to initially access the NetPI3 is not working under all circumstances (possibly including some "pretty popular" ones, as my "pfsense" setup was quite virgin).
Question: Are you aware of that? If not, would it help if I reproduce the issue and provide more information on this?
Another possibly related question: In one of the forum posts you mention the Tcp/Udp ports opened by the NetPI3. According to that post, bonjour is running as well. Why? Can it be used as another option to initially access the NetPI3?
After some debugging, I could resolve the issue by reconfiguring my router (pfsense): The DHCP-Server didn't automatically update the DNS entries. I can't remember the very details, because already some days past since then, but may claim is: I think that the way to initially access the NetPI3 is not working under all circumstances (possibly including some "pretty popular" ones, as my "pfsense" setup was quite virgin).
Question: Are you aware of that? If not, would it help if I reproduce the issue and provide more information on this?
Another possibly related question: In one of the forum posts you mention the Tcp/Udp ports opened by the NetPI3. According to that post, bonjour is running as well. Why? Can it be used as another option to initially access the NetPI3?
