Skip to content
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

Rpi Wireless Access Point bridge setup documentation improvement #1397

Closed
jpcornil-git opened this issue Feb 11, 2020 · 5 comments
Closed

Rpi Wireless Access Point bridge setup documentation improvement #1397

jpcornil-git opened this issue Feb 11, 2020 · 5 comments

Comments

@jpcornil-git
Copy link

Reference: https://github.com/raspberrypi/documentation/blob/master/configuration/wireless/access-point.md (bridge section)

  • Remove the following section (this step is not required; it just creates a bridge using the command line but related configuration is not persistent nor a preliminary step for anything):

Add a new bridge, which in this case is called br0.

sudo brctl addbr br0

Connect the network ports. In this case, connect eth0 to the bridge br0.

sudo brctl addif br0 eth0


  • Given the above you can also remove the bridge-utils installation and replace

sudo apt install hostapd bridge-utils


with:


sudo apt install hostapd


  • In order to handle systems running/conflict with networking.service, I suggest to replace:

Finally, restart systemd-networkd:

sudo systemctl restart systemd-networkd

You can also use the brctl tool to verify that a bridge br0 has been created.


with:


Finally, (re)start systemd-networkd:

sudo systemctl disable networking.service
sudo systemctl enable systemd-networkd
sudo systemctl restart systemd-networkd

You can also use the bridge tool to verify that a bridge br0 has been created.

bridge -d link


@JamesH65
Copy link
Contributor

This would be much better submitted as a pull request.

@jpcornil-git
Copy link
Author

Indeed/agree, just created #1398

@lurch
Copy link
Contributor

lurch commented Feb 12, 2020

Probably better to wait until after #1333 has been merged?

@jpcornil-git
Copy link
Author

Sure, not a big deal to rework this on top of it

@jpcornil-git
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants