Wifi issues

[Jwenger17]

I have recently been given a raspberry pi 3 model b for Christmas. I was able to set up Raspian and can access bluetooth and Wifi however, when i enter my password for my home Wifi nothing happens. I am able to connect to a personal hotspot running from my phone but i cannot seem to connect to anything else. I am new to all of this and it would be much appreciated if someone could lend me a hand.

[DougieLawson]

Is your WiFi SSID hidden?
Is your network using WEP (which is 100% insecure and not supported by the GUI)?

[Jwenger17]

Is your WiFi SSID hidden?
Is your network using WEP (which is 100% insecure and not supported by the GUI)?

I am not sure but i do believe that i am using WEP

[fruitoftheloom]

Is your WiFi SSID hidden?
Is your network using WEP (which is 100% insecure and not supported by the GUI)?

I am not sure but i do believe that i am using WEP

Change your Router to WPA, WEP is insecure

[Jwenger17]

Is your WiFi SSID hidden?
Is your network using WEP (which is 100% insecure and not supported by the GUI)?

I am not sure but i do believe that i am using WEP

Change your Router to WPA, WEP is insecure

I have switched it to WPA 2 but i still cannot connect through my RPI 3

[DougieLawson]

Open an lxterminal window and type in these arcane incantations, putting in your ssid / psk as needed.

sudo -i
cd /etc/wpa_supplicant
wpa_passphrase yourSSIDgoeshere passwordforthatSSIDgoeshere >> wpa_supplicant.conf
reboot

[Jwenger17]

Open an lxterminal window and type in these arcane incantations, putting in your ssid / psk as needed.

sudo -i
cd /etc/wpa_supplicant
wpa_passphrase yourSSIDgoeshere passwordforthatSSIDgoeshere >> wpa_supplicant.conf
reboot

It now shows that I have connected however i cannot connect to google or the raspberry help forums through the chromium web browser

[DougieLawson]

Then we need to look deeper at your network.

ip addr
ip route
sudo ping $(ip route|awk '/default/ {print $3}')
sudo ping 8.8.8.8
sudo ping Google.com
cat /etc/resolv.conf

[jbudd]

Just a small suggested tweek to those commands:

Code: Select all

ip addr
ip route
sudo ping -c 3 $(ip route|awk '/default/ {print $3}')
sudo ping -c 3 8.8.8.8
sudo ping -c 3 Google.com
cat /etc/resolv.conf

(ping will carry on until you interrupt it, ping -c 3 stops after sending 3 packets)

[Jwenger17]

Just a small suggested tweek to those commands:

Code: Select all

ip addr
ip route
sudo ping -c 3 $(ip route|awk '/default/ {print $3}')
sudo ping -c 3 8.8.8.8
sudo ping -c 3 Google.com
cat /etc/resolv.conf

(ping will carry on until you interrupt it, ping -c 3 stops after sending 3 packets)

I used a image to text application to copy over the code I fixed errors but i may have missed one

pi@ragiberrypi:- $ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOwn group defaul
t qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOW
N group default qlen 1000
link/ether b8:27:eb:06:46:fa brd ff:ff:ff:ff:ff:ff
inet6 fe80::bfba:dd43:32ed:3d4/64 scope link tentative
valid_lft forever preferred_lft forever
3: wlanO: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP g
roup default qlen 1000
link/ether b8:27:eb:53:13:af brd ff:ff:ff:ff:ff:ff
inet 108.52.28.104/8 brd 108.255.255.255 scope global wlan0
valid_lft forever preferred_lft forever
inet6 fe80::3b58:9578:d1bc:331f/64 scope link
valid_lft forever preferred_lft forever
pi@raspberrypi:- $ ip route
108.0.0.0/8 dev wlan0 proto kernel scope link src 108.52.28.104 metric 303
pi@raspberrypi:- $ sudo ping -c 3 $(ip route 1 awk 'idefault/ {print $3}')
Usage: ping [-aAbBdDfhLn0qrRUvV] [-c count] [-i interval] [-I interface]
[-m mark] [-M pmtudisc_option] [-l preload] [-p pattern] [-Q tos]
[-s packetsize] [-S sndbuf] [-t ttl] [-T timestamp_option]
[-w deadline] [-W timeout] [hop1 ...] destination
pi@raspberrypi:- sudo ping -c 3 8.8.8.8
connect: Network is unreachable
pi@raspberrypi:- sudo ping -c 3 Google.com
ping: unknown host Google.com
pitibraspberrypi:- cat /etc/resolv.conf
# Generated by resolvconf
search 71.252.0.12
nameserver 71.242.0.12

[DougieLawson]

There's an awful lot that's screwy there.

What's the address of your gateway router, because you're missing a route to it?

Is your ISP Verizon? As they own that 108.0.0.0/8 network block.
Can you ping your resolver 71.242.0.12?
Why do you have "search" set to an IP address rather than a domain name?

What does the IP stuff on your Windows machine look like? Take a look with ipconfig /all in a cmd.exe window.

What do you have in /etc/network/interfaces?
What do you have in /etc/dhcpcd.conf?

[jbudd]

Are you connected to your router?
The nameserver listed in /etc/resolv.conf looks like a Verizon one. I don't know why it isn't working, but you could try adding this to the bottom of /etc/dhcpcd.conf

Code: Select all

interface wlan1
static domain_name_servers=8.8.8.8 8.8.4.4

Edit - no that won't work since you can't ping 8.8.8.8

I used a image to text application to copy over the code I fixed errors but i may have missed one

Is there some reason you can't use simple copy and paste?
Your software seems to have read the pipe symbol ( | ) as the digit 1. It's purpose is to take the output of "ip route" and pass it on to another program "awk" for more filtering.

[Jwenger17]

There's an awful lot that's screwy there.

What's the address of your gateway router, because you're missing a route to it?

Is your ISP Verizon? As they own that 108.0.0.0/8 network block.
Can you ping your resolver 71.242.0.12?
Why do you have "search" set to an IP address rather than a domain name?

What does the IP stuff on your Windows machine look like? Take a look with ipconfig /all in a cmd.exe window.

What do you have in /etc/network/interfaces?
What do you have in /etc/dhcpcd.conf?

If by gateway router you mean my ssid it is NNJ25. I do have a verizon router but my personal computer is a mac and the codes you gave me do not translate over into terminal. I am not well versed in any sorts of computer coding so what is set on the raspberry is mostly due to my attempts to follow fix it guides that i have found.

[Jwenger17]

Are you connected to your router?
The nameserver listed in /etc/resolv.conf looks like a Verizon one. I don't know why it isn't working, but you could try adding this to the bottom of /etc/dhcpcd.conf

Code: Select all

interface wlan1
static domain_name_servers=8.8.8.8 8.8.4.4

Edit - no that won't work since you can't ping 8.8.8.8

I used a image to text application to copy over the code I fixed errors but i may have missed one

Is there some reason you can't use simple copy and paste?
Your software seems to have read the pipe symbol ( | ) as the digit 1. It's purpose is to take the output of "ip route" and pass it on to another program "awk" for more filtering.

I have my raspberry connected to a monitor and theres no way to transfer a copy and paste over to my computer. I'm not sure if id be able to open up the os on my laptop so that i would be able to do that. ( again i have a mac so screen capturing is not possible)

[DougieLawson]

You need to scrub all of the changes in your /etc/network/interfaces and /etc/dhcpcd.conf files back to the original versions.

interfaces file

Code: Select all

# interfaces(5) file used by ifup(8) and ifdown(8)

# Please note that this file is written to be used with dhcpcd
# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'

# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d

auto lo
iface lo inet loopback

iface eth0 inet manual

allow-hotplug wlan0
iface wlan0 inet manual
    wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

allow-hotplug wlan1
iface wlan1 inet manual
    wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

dhcpcd.conf file

Code: Select all

# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.

# Allow users of this group to interact with dhcpcd via the control socket.
#controlgroup wheel

# Inform the DHCP server of our hostname for DDNS.
hostname

# Use the hardware address of the interface for the Client ID.
clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
#duid

# Persist interface configuration when dhcpcd exits.
persistent

# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit

# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Most distributions have NTP support.
option ntp_servers
# Respect the network MTU.
# Some interface drivers reset when changing the MTU so disabled by default.
#option interface_mtu

# A ServerID is required by RFC2131.
require dhcp_server_identifier

# Generate Stable Private IPv6 Addresses instead of hardware based ones
slaac private

# A hook script is provided to lookup the hostname if not set by the DHCP
# server, but it should not be run by default.
nohook lookup-hostname

Reboot and see what happens with your Raspberry connected with a cable to your router.