Difference between revisions of "Connecting to the Pi"
(→Ad hoc: more content) |
m (→Arch Linux: fix code formatting) |
||
| Line 23: | Line 23: | ||
First, make sure your network interface (i.e. network card) doesn't have anything running on it. In the examples below, <code>dev wlp4s0</code> is used as the name of the interface. If your interface name is different (get the interface name with <code>iw dev</code>, and it'll be after the word "Interface"), replace as necessary. If you use netctl, the following command will stop the current connection: | First, make sure your network interface (i.e. network card) doesn't have anything running on it. In the examples below, <code>dev wlp4s0</code> is used as the name of the interface. If your interface name is different (get the interface name with <code>iw dev</code>, and it'll be after the word "Interface"), replace as necessary. If you use netctl, the following command will stop the current connection: | ||
| − | + | netctl stop $(netctl list | grep '^\*' | cut -d'*' -f2) | |
Now, while your interface is down, change it over to IBSS (the type for ad-hoc data): | Now, while your interface is down, change it over to IBSS (the type for ad-hoc data): | ||
| − | + | iw dev wlp4s0 set type ibss | |
After that, join the ad-hoc network. '''Replace ''FREQUENCY''''' with an actual frequency. Choose the frequency from [https://en.wikipedia.org/wiki/List_of_WLAN_channels#2.4_GHz_(802.11b/g/n/ax) this table]. You'll probably use 2.4 GHz (802.11b/g/n/ax) channels 1 or 2, which are 2412 and 2417 MHz respectively, so you would replace ''FREQUENCY'' with <code>2412</code> or <code>2417</code>. | After that, join the ad-hoc network. '''Replace ''FREQUENCY''''' with an actual frequency. Choose the frequency from [https://en.wikipedia.org/wiki/List_of_WLAN_channels#2.4_GHz_(802.11b/g/n/ax) this table]. You'll probably use 2.4 GHz (802.11b/g/n/ax) channels 1 or 2, which are 2412 and 2417 MHz respectively, so you would replace ''FREQUENCY'' with <code>2412</code> or <code>2417</code>. | ||
| − | + | iw dev wlp4s0 ibss join RPiwireless ''FREQUENCY'' | |
Now, register an IP address: (I haven't figured out if this next command is strictly necessary) | Now, register an IP address: (I haven't figured out if this next command is strictly necessary) | ||
| − | + | ip addr add 192.168.1.2/255.255.255.0 dev wlp4s0 | |
And try to connect: (you may have to wait a minute or so before this starts working) | And try to connect: (you may have to wait a minute or so before this starts working) | ||
| − | + | ssh pi@192.168.1.1 | |
The username (the <code>pi@</code> part) is important because otherwise ssh may try to use your current username, which will almost certainly not be <code>pi</code>). | The username (the <code>pi@</code> part) is important because otherwise ssh may try to use your current username, which will almost certainly not be <code>pi</code>). | ||
Revision as of 05:10, 2 April 2019
Here's how to connect to the Pi.
Ad hoc
OS X
Connect to RPiwireless from the WiFi dropdown menu, then ssh pi@192.168.1.1. Doesn't work? Try arp -a at a terminal. If an IP address associated with the hostname pehuen-pi[1] comes up, use that in the SSH command instead. Otherwise, keep trying 192.168.1.1 (192.168.2.2 sometimes works).
Dylan's laptop
Disconnect from all WiFi networks. Open the program Windows Powershell from the Start menu. In the terminal that appears, run netsh wlan connect RPiwireless.
If that worked, the laptop should now be connected to RPiwireless, and complain about no Internet access. This is sensible, since the Pi doesn't have any other way to connect to the Internet.
You may now use an SSH client (either PuTTY or MobaXterm) to connect to pi@192.168.1.1. Not sure which one to use? MobaXterm is easier; open the program using the shortcut on the desktop, then click "New Session", select "SSH", enter 192.168.1.1 as the IP and pi as the username, then connect.
Arch Linux
These instructions will use the tools ip and iw. Make sure you have them installed before proceeding. Also, you might have to do some of these commands with sudo.
Helpful background information: the Arch Wiki's articles on wireless network configuration and ad-hoc networking.
First, make sure your network interface (i.e. network card) doesn't have anything running on it. In the examples below, dev wlp4s0 is used as the name of the interface. If your interface name is different (get the interface name with iw dev, and it'll be after the word "Interface"), replace as necessary. If you use netctl, the following command will stop the current connection:
netctl stop $(netctl list | grep '^\*' | cut -d'*' -f2)
Now, while your interface is down, change it over to IBSS (the type for ad-hoc data):
iw dev wlp4s0 set type ibss
After that, join the ad-hoc network. Replace FREQUENCY with an actual frequency. Choose the frequency from this table. You'll probably use 2.4 GHz (802.11b/g/n/ax) channels 1 or 2, which are 2412 and 2417 MHz respectively, so you would replace FREQUENCY with 2412 or 2417.
iw dev wlp4s0 ibss join RPiwireless FREQUENCY
Now, register an IP address: (I haven't figured out if this next command is strictly necessary)
ip addr add 192.168.1.2/255.255.255.0 dev wlp4s0
And try to connect: (you may have to wait a minute or so before this starts working)
ssh pi@192.168.1.1
The username (the pi@ part) is important because otherwise ssh may try to use your current username, which will almost certainly not be pi).
Warning! The ssh connection produced by this method is almost unusably slow at times. I (Daniel, April 2019) am trying to fix this.
Notes/references
- ↑ Pehuen Moure was on the team in (at least) 2017
