May-15th-2019, 06:59 AM
(May-14th-2019, 08:55 AM)Armin@netPI Wrote: Hello,
so your log file looks ok and your netPI is working fine.
Back to the question 1.). I asked if your network has a DHCP server active which gives the netPI an IP address. A DNS server you are referencing is not necessary at all for finding a netPI first of all. The netPI needs an IP address from a DHCP sever, else it cannot work.
In order to get an own IP address the netPI sends out periodically a "DHCP Discover" frame from source ip 0.0.0.0 to destination ip 255.255.255.255
Code:363 27.758019 0.0.0.0 255.255.255.255 DHCP 340 DHCP Discover - Transaction ID 0x2c54930a
My netPI in the office has the MAC address b8:27:eb:d5:07:6 (printed on the label). So I connected my netPI to my notebook ethernet port directly to check if it is sending out these frames. So I connected my netPI to my notebooks ethernet interface and start a wireshark capture. I set a filter to "eth.src == b8:27:eb:d5:07:66" to capture just those frames of interest:
So I see my netPI is sending out these frames. So I checked it is working fine with my netPI. You can do the same just to check your netPI is doing well. As next you can do the very same procedure when you connect back your netPI to your official network. You should see the same frames ... and if you have a DHCP server running it should return a valid IP address back to netPI ... and then instead of using https://NTBxxxxxxx you could easily access your netPI with its ip address received by the DHCP server.
Thx
Hi Armin,
Wire Shark gives me as shown below but I couldn't get into the https://ntbxxxxxxxx/views/landing-page.html by default. Can I access to the webrowser by connecting the netPI and my notebook with an ethernet cable or do I have to add a router in between them?
Thank you!
