Wifi AP

[k-os]

Got me a Raspberry Pi 3 and decided to tinker around. I stumbled upon this page to setup a wifi access point (https://learn.adafruit.com/setting-up-a ... l-software). As far as I can tell, I set everything up as stated. When I run the test, my results look a little different (specifically it says it did not start wlan0). See screenshot below. Thoughts on how to troubleshoot what is going on, especially based upon what is listed in this tutorial?

Thanks!

hostapd.JPG (29.49 KiB) Viewed 1222 times

[jamesh]

Try these instructions

https://www.raspberrypi.org/documentati ... s-point.md

I think the Adafruit ones are a bit out of date.

[k-os]

Thanks @jamesh, I'll give those a look. Being new it was/is hard to determine what is out of date and what to try.

[k-os]

Finally had a chance to work through the list. Everything was entered and worked perfectly (I assume) until I got to the section about setting up the Bridge. Or I guess I should say when I finished section 1. I see my SSID I setup on from my phone. I can connect to the SSID but it's not connecting to the internet. I remoted in via VNC and when I bring up the browser it says there is no connection.

So when I try to get the bridge utilities to install, I get an error in putty because it cannot connect to the site:

putty-error-vpin.JPG (37.36 KiB) Viewed 1168 times

Help.

[k-os]

Anyone have any suggestions to troubleshoot?

[SurferTim]

Which type of access point are you trying to install? There are two on that doc page. One is a NAT (first) and the other is a bridge (second).

[k-os]

I thought I needed a bridge. I have the Pi and my regular wireless router. What I was attempting to do is have both broadcast their unique SSID and I can connect to one or the other to get to the Internet. The Pi is connected to my wireless router via Cat5 cable.

And it is my understanding, unless I'm reading it incorrectly, that I would need to do the first part then continue on to make it a bridge. Regardless, I did all of part 1 (NAT) and the Pi doesn't connect to the Internet.

[SurferTim]

I thought I needed a bridge. I have the Pi and my regular wireless router. What I was attempting to do is have both broadcast their unique SSID and I can connect to one or the other to get to the Internet. The Pi is connected to my wireless router via Cat5 cable.

And it is my understanding, unless I'm reading it incorrectly, that I would need to do the first part then continue on to make it a bridge. Regardless, I did all of part 1 (NAT) and the Pi doesn't connect to the Internet.

Use one or the other.
If you want a separate localnet, use the first part only.
If you want a bridge, use the second part only.
Don't try to combine them.

[k-os]

Gotcha. And based on what I said I was attempting to accomplish, do you agree that bridge is the correct way to go?

[SurferTim]

Gotcha. And based on what I said I was attempting to accomplish, do you agree that bridge is the correct way to go?

If you want the same localnet on both the wifi and ethernet interfaces, all wifi and ethernet clients can connect to each other, and use the gateway router for dhcp for all devices, the bridge is the way to go.

If you want a standalone access point, the NAT access point is the best.

[k-os]

I want the Pi to be the default gateway for DHCP. I mean, can I have both the wireless router and the Pi act as DHCP, depending on whether you connect to one or the other? I'm thinking that's what you mean by standalone AP. (Sorry, new to network terminology.) So, if I have my local devices connect to the Pi, the Pi acts as the DHCP. If a visitor connects to my wifi router, the router (with it's own SSID) acts as the DHCP. Is that possible? Is that what you mean by standalone AP? In my mind, that's what standalone AP means.