steptail.com

How many light bulbs does it take to change a penguin?

User Tools

Site Tools


guides:virtual_modem:section_3

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
guides:virtual_modem:section_3 [2020-12-17 04:05]
omolini [Physical connections]
guides:virtual_modem:section_3 [2022-12-17 19:37] (current)
omolini [Skip to other sections]
Line 29: Line 29:
     - Connect a Micro USB power cable to the Raspberry Pi. The system should will start booting up immediately.     - Connect a Micro USB power cable to the Raspberry Pi. The system should will start booting up immediately.
  
 +Note: you may choose to connect the Raspberry Pi over Wi-fi to simplify connections,​ but for the sake of the tutorial, we'll work with wired connections for now. If you do decide to switch over to WLAN, there are instructions on the next section how to do so. 
 ==== Powering up the Raspberry Pi ==== ==== Powering up the Raspberry Pi ====
   - It could take up to five minutes to boot. Watch the blinking green activity light on the Raspberry Pi indicating that the Raspberry is booting up (see image below with the red arrow). Once the blinking stops, wait another 15-30 seconds before proceeding. If the activity light of Raspberry does not blink at all after powering up, the MicroSD card may not be properly inserted, it may not have been properly flashed or the image used was corrupted. You may need to retrace your steps up to this point. \\ {{ :​guides:​pics:​raspberry_activity.jpg?​500 |}}   - It could take up to five minutes to boot. Watch the blinking green activity light on the Raspberry Pi indicating that the Raspberry is booting up (see image below with the red arrow). Once the blinking stops, wait another 15-30 seconds before proceeding. If the activity light of Raspberry does not blink at all after powering up, the MicroSD card may not be properly inserted, it may not have been properly flashed or the image used was corrupted. You may need to retrace your steps up to this point. \\ {{ :​guides:​pics:​raspberry_activity.jpg?​500 |}}
Line 42: Line 43:
  
 ==== Connect over SSH ==== ==== Connect over SSH ====
-  * Once you've figured out the IP address of the Raspberry Pi, connect to it via SSH. You can use any SSH client to log into the Raspberry. I choose to use PuTTY for this tutorial, which can be obtained from: \\ https://​www.chiark.greenend.org.uk/​~sgtatham/​putty/​latest.html+  * Once you've figured out the IP address of the Raspberry Pi, you can connect to it via SSH. SSH server is now enabled, because we saved the SSH.TXT file on the root of the boot file system on the earlier step. You can use any SSH client to log into the Raspberry. I use PuTTY for this tutorial, which is highly recommended and can be obtained from: \\ https://​www.chiark.greenend.org.uk/​~sgtatham/​putty/​latest.html
   * Upon first connection, you will receive a warning message. This is normal. Click on Yes to add the security key to the local cache. \\ {{ :​guides:​pics:​putty_security_alert_yes.png?​300 |}}   * Upon first connection, you will receive a warning message. This is normal. Click on Yes to add the security key to the local cache. \\ {{ :​guides:​pics:​putty_security_alert_yes.png?​300 |}}
   * It will prompt to log on. Username is ''​pi'',​ password is ''​raspberry''​. Everything is case sensitive.   * It will prompt to log on. Username is ''​pi'',​ password is ''​raspberry''​. Everything is case sensitive.
Line 50: Line 51:
  
 ==== Basic configuration and network settings ==== ==== Basic configuration and network settings ====
-  * For ease of access through SSH, you may want to configure a static IP address for your Raspberry Pi so that you can connect to the same IP address without always checking your router for the correct IP address. Later on you may want to reverse this change, if you want the Raspberry to auto-configure to be used in any network. In the latest ​version of Raspbian, you can set a static IP by editing **/​etc/​dhcpcd.conf** and uncommenting the example static configuration. ​+  * For ease of access through SSH, you may want to configure a static IP address for your Raspberry Pi so that you can connect to the same IP address without always checking your router for the correct IP address. Later onyou can optionally ​reverse this change, if you want the Raspberry to auto-configure to be used in any network. In the version of Raspbian ​OS (2018 as of time of writing), you can set a static IP by editing **/​etc/​dhcpcd.conf** and uncommenting the example static configuration. ​
     * I prefer Nano for quick file edits. \\ ''​**sudo nano /​etc/​dhcpcd.conf**''​     * I prefer Nano for quick file edits. \\ ''​**sudo nano /​etc/​dhcpcd.conf**''​
-    * Here's an example of my static IP configuration. As you can see, I'​ve ​set my IP as **10.0.16.50** and router to **10.0.16.1**. ​Usually ​the router can also double as a domain name server, but for portability I've told Raspberry to just use the Google name server, **8.8.4.4**. ​For simplicity, ​I won't use any other name servers at this time, but if you want to use more, you can add them to the same line, just separate them with a space.+    * Here's an example of my static IP configuration. As you can see, in my network ​need to set my IP as **10.0.16.50** and router to **10.0.16.1**. ​Please use the values that suit your network configuration. Quite often your router can also double as a domain name server, but for portability I've told Raspberry to just use the Google name server, **8.8.4.4**. I won't use any other name servers at this time, but if you want to use more, you can add them to the same line, just separate them with a space.
 <code c++> <code c++>
 # Example static IP configuration:​ # Example static IP configuration:​
Line 63: Line 64:
     * To exit, press CTRL+X     * To exit, press CTRL+X
   * Disconnecting and reconnecting the Ethernet cable should be sufficient to update the IP address. In my case my new IP updated to **10.0.16.50**,​ so I will reconnect PuTTY on this new IP address. ​   * Disconnecting and reconnecting the Ethernet cable should be sufficient to update the IP address. In my case my new IP updated to **10.0.16.50**,​ so I will reconnect PuTTY on this new IP address. ​
 +
 +----
  
 Go ahead and continue to the next part of this guide, where I will show you how to install the Virtual Modem script! Go ahead and continue to the next part of this guide, where I will show you how to install the Virtual Modem script!
Line 72: Line 75:
   * [[Guides:​Virtual Modem|Section 1 - Introduction]]   * [[Guides:​Virtual Modem|Section 1 - Introduction]]
   * [[Guides:​Virtual Modem:​Section 2|Section 2 - Shopping list]]   * [[Guides:​Virtual Modem:​Section 2|Section 2 - Shopping list]]
-  * [[Guides:​Virtual Modem:​Section 3|Section 3 - Setting up Raspbian]] << You are here+  ​* **[[Guides:​Virtual Modem:​Section 3|Section 3 - Setting up Raspbian]] << You are here**
   * [[Guides:​Virtual Modem:​Section 4|Section 4 - Setting up Virtual Modem]]   * [[Guides:​Virtual Modem:​Section 4|Section 4 - Setting up Virtual Modem]]
 +  * [[Guides:​Virtual Modem:​Section 5|Section 5 - Using Virtual Modem]]
 +
 +  * [[Guides:​Connecting Windows 3.1 to the Internet]]
 +  * [[Guides:​Connecting Windows 9x to the Internet]]
 +  * [[Guides:​Connecting Windows 2000 to the Internet]]
 +
  
 ---- ----
 +==== Get In Touch With Us! ====
 +Share your thoughts and report bugs on Discord. \\
 +[[https://​discord.gg/​4w6CpZ8|{{:​images:​social-discord.png?​nolink|}}]] ​
  
-Questions? Comments? [[:Contact Information|Contact Me!]]+{{tag>​Guides Guides:Networking}}
  
guides/virtual_modem/section_3.1608177948.txt.gz · Last modified: 2020-12-17 04:05 by omolini