You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi so I thought I had this working correctly but I can seem get internet traffic to pass through the AP to the internet. For example when I ssh into the RaspPi and ping outside my home network:
lombardo@raspberrypi:~ $ ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=58 time=17.8 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=58 time=21.3 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=58 time=19.8 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=58 time=18.7 ms
Now if I connect my laptop to the RaspPi AP and ping from my laptops terminal:
Fedallahs-MacBook-Pro:~ lombardo$ ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
Request timeout for icmp_seq 0
ping: sendto: No route to host
Request timeout for icmp_seq 1
ping: sendto: No route to host
Request timeout for icmp_seq 2
ping: sendto: No route to host
Request timeout for icmp_seq 3
ping: sendto: No route to host
Request timeout for icmp_seq 4
--- 1.1.1.1 ping statistics ---
6 packets transmitted, 0 packets received, 100.0% packet loss
I ran the script only replacing the the following variables: MyAPmyappassWifiSSIDwifipass. Do you have an idea why the information is not being forwarded from the RaspPi to my home network?
Hi so I thought I had this working correctly but I can seem get internet traffic to pass through the AP to the internet. For example when I ssh into the RaspPi and ping outside my home network:
Now if I connect my laptop to the RaspPi AP and ping from my laptops terminal:
I ran the script only replacing the the following variables:
MyAP
myappass
WifiSSID
wifipass
. Do you have an idea why the information is not being forwarded from the RaspPi to my home network?Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: