RE: Getting Started with an Old Raspberry Pi 1B : Connecting via Ethernet

ralphjy — Wed, 20 Feb 2019 20:33:53 GMT

I think [mention:b0bc65b9ecdc4307bd967592f00e340a:e9ed411860ed4f2ba0265705b8793d05] has given you all the right suggestions. Hopefully, you have things working by now. Since you are new to network stuff, I thought I would add that because you are obtaining your ipaddress automatically (via DHCP) that the address might change periodically. So, if things stop working you may need to update the ipaddress that you are using in putty.

You can work around this by setting up a static ipaddress in your network configuration but you should get things working with DHCP first. If you're interested later, just Google it or one of us can provide you a link to instructions.

RE: Getting Started with an Old Raspberry Pi 1B : Connecting via Ethernet

shabaz — Wed, 20 Feb 2019 17:34:32 GMT

Hi!

That's great progress. There's a few things you can do (I'm assuming you're running all this without a monitor and keyboard connected, which makes it a bit harder, but still feasible).

Regarding the ssh file, it must have no extension (I've never tried it with an extension, but I believe it won't work). Normally I just right-click in the file explorer, and select New->Text Document, which by default has a .txt suffix, but I delete it. For this to work, the File Explorer options must be set to always display the extension.

[View:/resized-image/__size/620x543/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-274ecce6-ba57-4ea5-89f7-d500437c5b97/5775.contentimage_5F00_190187.png:620:543]

Then the file can be created in the top level of the SD card:

[View:https://players.brightcove.net/1362235890001/NkxiVJdjx_default/index.html?videoId=6004584288001:740:466]

Once you've connected it to the router (best to do this with the Pi unpowered first, otherwise it hangs for ages on boot), you need to find the IP address of the Pi. The info below assumes you've connected to a typical router at home:

Method 1: requires access to the router via a web page (it is nearly always http://192.168.0.254 or http://192.168.1.254 for home routers) to check what IP address the Pi has acquired

Method 2: Try to ping raspberrypi.local

To do this, type the following in a windows command prompt (the -4 is used to force IPv4 pings):

[embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:3ef06e6b-9b7d-4651-b12d-db8be7f5e991:type=text&text=ping+raspberrypi.local+-4]

and look for this response:

[View:/resized-image/__size/620x297/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-274ecce6-ba57-4ea5-89f7-d500437c5b97/2146.contentimage_5F00_190189.png:620:297]

That IP address can now be attempted using your SSH client software, e.g. PuTTY:

[View:/resized-image/__size/436x426/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-274ecce6-ba57-4ea5-89f7-d500437c5b97/1641.contentimage_5F00_190190.png:436:426]

Method 3: Just try to ping random addresses! Figure out if your network is on 192.168.0.xx or 192.168.1.xx, by opening up a windows command prompt and typing:

ipconfig /all

Look for this information:

[View:/resized-image/__size/407x450/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-274ecce6-ba57-4ea5-89f7-d500437c5b97/8507.contentimage_5F00_190191.png:407:450]

Now you can randomly ping stuff until you get a response:

[View:/resized-image/__size/380x210/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-274ecce6-ba57-4ea5-89f7-d500437c5b97/3730.contentimage_5F00_190192.png:380:210]

and then see if it is a Pi by trying to SSH to it using your PuTTY software. There are tools that try to ping all addresses to narrow down the list of choices, but it still takes a while : (. Method 1 or Method 2 is better.