Install issue: no local ip issued during install


#1

What is the problem?
I cannot acquire a local ip address after install of 0.15.1 on a new microSD card.

What did you already try to solve it?
I recently replaced my pi cam with a Logitech C920. The added weight of the cable made my raspberry pi 3 enclosure topple over constantly. I powered down and moved the pi to its stock enclosure. It would not power up afterwards. I powered down, removed the microsd card only to find that Windows 7 would not read the card.

  1. I replaced the card since it was unreadable; can't format either, gives error.
  2. Formatted the new card to FAT (default choice)
  3. Flashed to the latest version of Octopi
  4. Followed the instructions to update the network file but realized this is a mistake because I am trying to setup as an ethernet connection. I then changed the file back to default and saved.
  5. After powering up with microsd card back in pi, I then checked Angry ip scanner and Fing. The new device does not show up. I can see the blinking green light, constant red light, and the lights of the ethernet outlet are all blinking so technically the device is working.
  6. I try Octopi.local- I get a timed out screen. I assume this is because it's trying to reach the old ip.
  7. I try to ping octopi.local. Response is there's no pi.
  8. I log into my ISP router, I see the device has ipv4 and ipv6 addresses.
  9. In the ISP router I also input the ipv4 and ipv6 addresses to the port forwarding entry.
  10. I reset all devices but nothing changed.
  11. I decided to try and input my ipv4 address into my web browser.
  12. Octoprint boots right up, so I start the setup process.
  13. I decide to reset instead of a completing the setup.

Still can't find the local ip. I am assuming I need the local ip before I can start the SSH portion of the setup. I'm also wondering if it's possible to just reformat the microsd and start over.

Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, octoprint.log, serial.log or output on terminal tab, ...)

Octopi Version- 0.15.1 (attempting)
OctoPi version- N/A
Printer- Prusa i3 MK2S
Raspberry Pi- Raspberry Pi 3 v1.2
OS- Windows 7
Method- ethernet (as was previous setup)
MicroSD card- 16GB Sandisk (previous failed was Transcend 16GB)


#2

Hi @BuddyLee,

Neither OctoPi nor OctoPrint generate a IP address.

The Raspberry Pi gets its IP address form the router with DHCP activated (for automatic assigning IP addresses) or you assign a IP address manually. But that can be rather complicated.

If you have a HDMI monitor, you can connect it to the Pi. When your Pi is connected to your LAN and the boot sequence is completed, at the end of the start protocol you should see your Raspberry Pi IP address.


#3

This is actually a Windows thing since it doesn't out-of-the-box have Bonjour. More


#4

But when even Fing does not find it... (assuming he has Fing as a smartphone app)


#5

Yup, checked via my phone. What's interesting is that when I changed the perimeter to search via the ISP router then the pi showed up but as an ipv4 address which makes me wonder if at some point during my 2016 install, if I had the pi connected to another router and that's why it was assigned an address. I was under the impression that in order for it to be reachable outside of the LAN it has to be hardwired to the ISP router. So to clarify, there's the ISP router then a general router for the rest of my gadgets that's connected to the ISP router. The raspberry pi 3 is just connected directly to the ISP router so that it could be port forwarded.


#6

Hmm now I wonder if I tried to connect it to the normal router if it would assign an ip. That makes sense because everything under this router is assigned an ip via DHCP but everything connected to the ISP router is just ipv4 IDs. Hmm but then I guess the question is if I left the raspberry pi on the normal router would it still be able to port forward?