0

So I have the Raspberry Pi 4 connected to the internet via ethernet cable. I then set it up as an access point so I can connect to it wirelessly through a laptop.

The SSID does indeed show up on my lap, which I am able to connect to. But when I am connected it says "connected, no internet".

How do I go about fixing this? I need this step so I can analyze the packages going through the network.

Thanks in advance.

EDIT: This is the response to the first reply:

pi@raspberrypi:~ $ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether dc:a6:32:19:63:1a brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.57/24 brd 192.168.0.255 scope global dynamic noprefixroute eth0
       valid_lft 86371sec preferred_lft 75571sec
    inet6 2600:8806:100:26c1:12f9:d375:7571:e93e/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 86399sec preferred_lft 86399sec
    inet6 fe80::7dfe:1646:881c:acdd/64 scope link 
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether dc:a6:32:19:63:1c brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.23/24 brd 192.168.1.255 scope global deprecated noprefixroute wlan0
       valid_lft forever preferred_lft forever
    inet6 fe80::eda6:1950:84b7:4eb6/64 scope link 
       valid_lft forever preferred_lft forever
pi@raspberrypi:~ $ ip r
default via 192.168.0.1 dev eth0 proto dhcp src 192.168.0.57 metric 200 
192.168.0.0/24 dev eth0 proto dhcp scope link src 192.168.0.57 metric 200
Milliways
  • 62,573
  • 32
  • 113
  • 225
zevbda
  • 3
  • 2

1 Answers1

1

The tutorial you have used should do. But it seems you have missed something. There is a problem with the routing table you have given with ip r (or less cryptic ip route show). There is no entry for the network of the access point, so the kernel does not know where to send ip packages from the access point. That's causing the error ".., no internet". Your routing table should at least look similar to this:

pi@raspberrypi:~ $ ip route show
default via 192.168.0.1 dev eth0 proto dhcp src 192.168.0.57 metric 200
192.168.0.0/24 dev eth0 proto dhcp scope link src 192.168.0.57 metric 200
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.23 metric 300

So you should check your setup again with focus on the wifi setup.

You can also try another setup which does not need additional helper programs and may have things easier. Have a look at Setting up a Raspberry Pi as an access point - the easy way using section ♦ Setting up an access point and with eth0, with NAT (recommended).

Ingo
  • 42,961
  • 20
  • 87
  • 207