Problem with Raspberry pi 2 as AP

[789]

Hello.
Recently I'v tried to set up my Rasp. 2 as An AP, with one wifi module being the AP, and another to connect to the internet.
I'm using 2 usb wifi cards of type TL-Wn722n according to this page : http://itsacleanmachine.blogspot.co.il/ ... ry-pi.html

I Have a couple of big problems:
1. When running

Code: Select all

hostapd  /etc/hostapd/hostapd.conf  

, after some time my raspberry becomes unresponsive completely, so its really hard to work like this.At first a though that it might have happened because the Pi needed more AMPs, so I hooked it to the wall instead of my PC. That didn't help much.
2. Even in the short window of time that the PI as AP does work - machines that are connected to the AP, aren't able to connect to the internet, and I have no idea why..

Please guy's I need help this
Thanks!

[epoch1970]

You should use the console and look at syslog and other log files to understand or describe what is going on.
Anything between hostap, networking, firewalling, wifi hardware could be the cause of the issue you see.

[allfox]

Greetings.

Short answer: Check your power supply. What is it? Phone charger is not a right choose.

Long answer:
1 - Powering Pi from a PC USB is just not right, and phone charger is not a good idea either. You need a decent Power Supply Unit, especially when you want to drive Wi-Fi. If you are not sure, get an official PSU. There are a lot of problems could just not exist if you spend some coins on PSU.

2 - Just curious, but how do you plug two TP-LINK 722N into one Pi? In my memory, they are so big, I think you at least need another USB hub? Could you please post an image about your hardware?

3 - I think let's put Internet connectivity down at first, we make a working AP first, then go for Internet. The instruction which you`ve followed is an old one, and the writer was using PPP to connect to internet, so his iptables rule said "-o ppp0". This may be "-o wlan1" for you. Anyway, ignore the Internet first.

4 - The way to configure a static IP is changed during these years, it's no longer /etc/network/interfaces, but /etc/dhcpcd.conf. Note, dhcpcd.conf is not dhcpd.conf. The old way might work somehow, but you should follow the new way.