So, here’s how it goes. I have an old Linksys router which I have my raspberry pi connected to via Ethernet. I SSH to it via my laptop or phone by connecting to my router via WiFi. I want to be able to use the WiFi chip on the Pi to connect to a nearby router which is connected to the internet so that I can download packages or whatever I may need on the pi while at the same time using the Ethernet connection to my offline router so I can SSH to it.
Here is the output of ifconfig
Download & Changelog. Useful links. RetroPie Tutorial for Raspberry Pi 2. Build Your own Raspberry Pi Retro Gaming Rig. The RetroPie Project Official Site. The RetroPie Project Forum. Where do you find ROMs for your RetroPie (self.RetroPie) submitted 4 years ago by curciogm. Mar 18, 2017 Now you can connect to your WiFi pressing the WiFi icon in the top right corner (you’ll need a WiFi adapter for this to work on the Raspberry Pi 2), find your WiFi network and enter your WiFi.
When I run
I get this
So to me it looks like I should be connected to the internet, so I test that with a ping
And I get
Here’s the output of
So I’m not sure what the next step is, because the internet isn’t working even though it says it’s connected to the WiFi.If you need more info let me know!
Can Raspberry Pi Download Game Roms From The Internet Through Wifi Connection
2 Answers
You still haven't explained how you set up networking, but you have 2 default routes, and the Ethernet has higher priority.
Can Raspberry Pi Download Game Roms From The Internet Through Wifi Pc
As Ethernet isn't connected to internet you can disable this by adding the following at the bottom of :- /etc/dhcpcd.conf
Ideally you should properly configure the router to not advertise.
I'm noticing your WiFi has a /23 netmask but your wired network uses /24.
Is there a compelling reason why you used a /23 netmask on one of the networks. They should probably both agree (and probably should be /24).
The reason for this is that the network stack uses the netmask to determine if a remote host is on the same subnet vs. a different subnet (in which case it will need to send packets to a router to forward to the remote host). But with your particular network numbers and masks, it will end up getting confused into thinking they are not he same subnet ... when in reality they are not.
Your network configuration is unclear (and possibly unnecessarily complicated). I suspect you may be able to simplify he setup. WiFi and wired clients can be mixed on the same subnet ... and I'm wondering if you thought they needed to be separated.
Basically one of your computers thinks both machines are on the same subnet. The other machine thinks they are both on different subnets.
Comments are closed.