-
Notifications
You must be signed in to change notification settings - Fork 1
Unable to set up on Raspberry Pi #2
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
Comments
|
Hi, changing IGNORE_MODE to 1 had no effect. Got this error again: Is there a folder issue? |
re: 1) If you're cutting and pasting from the wiki text, the '/etc/init.d' dirspec was missing a trailing slash. Most folk would automatically work around that during tab-completion, but cut-n-paste would miss it. I've added it. re: 2) sorry, /etc/bridgeap/bridgeap.conf (staging version has /etc/default as an option) - |
Got a little further. The problem is that the command as written symlinks the folder instead of script. I needed to symlink as follows: I should mention that raspbian did not have radvd, hostapd, or isc-dhcp-client installed, so I used their package manager to install them. So the update-rc.d completes without error. I've set IGNORE_MODE to 1, and now get this: Starting bridgeap interface bridging If you think you have received this message due to a bug rather exiting. |
Ah, fixed the wiki for that missing tail. d'oh! If you run the bridgeap script with debugging ( bash -x bridgeap start ) what does the full dhcp command look like? Different distros have different support for different options, so i'm wondering if it's a strangeness with your version of raspian... |
Here's what I got: `sudo bash -x /usr/local/sbin/bridgeap start
If you think you have received this message due to a bug rather exiting.
|
Hrm... apparently raspbian recompiled the dhcp server to remove the user/group options for your build, which means that DHCP won't drop privileges after starting (bad security design) I'll drop an option into the config file to ignore DHCP user/group (run as root) which you'll be able to use to bypass that error. |
the DHCP issue should be resolvable by unsetting the two options in the bridgeap config file: DHCP_USER and DHCP_GROUP. comment them out, and the server -should- start up. |
Ok, commenting those out, here is the output: `Starting bridgeap interface bridging If you think you have received this message due to a bug rather exiting. |
Okay, so if it fails, always send post the logs in bash debug mode, or else it's really not useful text. Another thing to check is your apparmor logs. That's going to be something that you might need to adjust, if you're running apparmor, or selinux. I don't have any way to help you, since I don't use them on my APs |
Oops, sorry about that: pi@bwrsd-pi-001:~ $ sudo bash -x /usr/local/sbin/bridgeap start
If you think you have received this message due to a bug rather exiting.
|
Try re-pulling - you don't have the latest commit. |
And, done. This is fantastic; thanks for the extra time to get this working! |
Actually, one last question: I assumed with the presence of update-rc.d that it should start automatically, but that's not the case. No big deal, just wondering if there's anything there I can help troubleshoot before we close this. |
Hrm.. it may be that your systemd configuration is not supporting the legacy /etc/init.d/ startup files. I suppose i should look at creating a systemd-compatible unit file |
If you do, let me know if I can help troubleshoot in some way. Everything else is working perfectly, so I'll leave it up to you as to whether to keep the issue open. Thanks again for all your help. |
I have a wired connection that I am trying to share via wifi on a Raspberry Pi 3, running latest Raspbian. Following the installation instructions in the wiki:
update-rc.d bridgeap defaults gives the error: update-rc.d: error: initscript does not exist: /etc/init.d/bridgeap
ignoring that and continuing, sudo /usr/local/sbin/bridgeap start gives:
Starting bridgeap interface bridging
Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; Invalid argument.
failed to set Master mode
The text was updated successfully, but these errors were encountered: