-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Raspberry Pi 3 #11
Comments
This script works only for Raspberry Pi Zero W. I failed to make it work on Raspberry Pi 3, but if you managed to run AP+client mode simultaneously please share the steps with me and I will integrate into the script. |
Hi @lukicdarkoo Just see my forked project to make it works on rpi3 b+ and rpi3 a+ |
Cool! You brought it to another level! I am not sure whether is a good idea to integrate the changes or just to redirect the users. I guess, for now, all users who need support for Raspberry Pi 3 should check your fork. |
I renamed and pinned the issue, so users can find it more easily. |
@lukicdarkoo is there any script for raspberry pi 4B??? |
hi @Programmingplanet did try this on RPI4B ? => https://github.com/MkLHX/AP_STA_RPI_SAME_WIFI_CHIP I don't have any RPI4 to test it. If you can it will be great to know if it's work on it. |
ok, I will reply after testing it. also, I suggest working on this on an exiting project called raspap-webgui if possible |
@Programmingplanet lol i've tested raspap and this not work well (for me) and i just need shell script for my use case. So you can provide my repo on raspap project to give altenative ;-) Good test. |
getting this ----------- 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Populate /etc/udev/rules.d/70-persistent-net.rules Populate /etc/dnsmasq.conf Populate /etc/hostapd/hostapd.conf Populate /etc/default/hostapd Populate /etc/wpa_supplicant/wpa_supplicant.conf Populate /etc/network/interfaces Populate /bin/manage-ap0-iface.sh Create hostapd ap0 error monitor crontask ----- no success |
as you can read at the end. You need cron on your server and we assume you have an existing crontab . EDIT: |
Hi, Thanks a lot for your work and for the share ! I am trying to make this work on a fresh RPI3B+ with RPI OS Lite. I was getting the exact same error as @Programmingplanet. So I simply created a crontab using Thanks a lot for your help ! |
hi @FunkyKwak |
@MkLHX I've just tested it on the Raspberry Pi 4B, running the Raspbian GNU/Linux 10 (buster) Lite and it's running smoothly. |
@ImanolGo I never get this kind of issue. What's happened when you edit crontab -e? What version of code are you using? |
@MkLHX so the main problem is calling the script as super user using "sudo". "crontab -l" complains "no crontab for root". |
The script need to be run with sudo rights. So that use the sudo crontab and need the crontab exists. Maybe there is a solution to automate it. I haven't time to search and test it for now... |
hi there i've just push a release 1.7 who fix the crontab error https://github.com/MkLHX/AP_STA_RPI_SAME_WIFI_CHIP/releases/tag/1.7.2 |
Hi there!
I forked the repo to make some test with this script.
https://github.com/MkLHX/AP_STA_RPI_SAME_WIFI_CHIP
I have some troubles on RPI3A who run raspbian buster, when i run the configure.sh script with args after reboot i can see the AP ssid and i can use it! But if i reboot the RPI, il loose the AP mode and i can't access on the RPI through ssh.
It's look like in second state....
Then i have to reboot the RPI a second time and the AP reappears.
EDIt: find something
On boot hostapd can't start and give an error. So i chech journalctl -ex and hostapd give:
So i'm looking for any explaination about the errors :
"ctrl_iface exists and seems to be in use - cannot override it
Delete '/var/run/hostapd/ap0' manually if it is not used "
So i have to find where put the command:
sudo rm -rf /var/run/hostapd/ap0
when interface exist cause when i delete it, the hostapd service start.
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: