-
Notifications
You must be signed in to change notification settings - Fork 5.2k
System freeze when make a bridge to the onboard ethernet #1660
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
my pi is : pi 3 mode B |
|
I believe this is now fixed. Please retest with the latest Raspbian, and close if now OK. |
@JamesH65 when i get my new raspi , i will test it |
@JamesH65 i have test it, all my wireless card just can not make a bridge. brctl addbr br0 wlan* always fail. is this the way your fix the bug ? your just block this issue. i do not think bridge to a wlan interface is useless. |
@JamesH65 has been very helpful so far, fixing bugs in multiple drivers and solving bridging problems for many people. If it isn't working for you then there must be something different about your configuration - either hardware or software - that is either responsible for the failure or causing another bug to show itself. We aren't short of users with problems, and most of them have better attitudes than you, so try not to take your frustration out on people who are trying to help. |
The bug fix recently released fixed a coding fault in the wireless and ethernet drivers when used in bridging mode that mean that the ethernet would fail after a random time (could be days). Sounds like your fault might be different. If you follow the known working instructions here on the latest Raspbian (make sure you are up to date) https://www.raspberrypi.org/documentation/configuration/wireless/access-point.md does the bridging work? Do you have any message logs when it fails? |
@JamesH65 OK, i will do a further test. i do not see any error log use dmesg |
@pelwell sorry . i misunderstand the fix is just make bridge to wlan interface do not work . |
@JamesH65 retest it , have all the packages up to date, run rpi-update and reboot. then nothing change
i have test the onboard wlan interface and a extra wireless card . alaway told me "Operation not supported"
report no problem |
rpi-update is not really advised as it may bring in a non-working/testing kernel. Just apt-get update/upgrade should be sufficient. Does the same occur on a new raspbian install? You appear to be logged in as root so clearly it's not standard. A quick google seems to provide a number of different reasons why this error may occur, without knowing more about your setup its difficult to know which it may be. |
Actually, looking at your commands, you should be doing something like this... sudo brctl addbr br0 Please check the instructions I linked earlier. |
@JamesH65 i am do a new install now. download the image from official site and reinstall in a new pi3 board, then the same thing happed. above command are the first command i type on this pi3 board and have not change any config file . newest install with all default config |
@JamesH65 i found the problem. the wlan interface must be put into master mode ,then it become bridgeable .
I didn't notice this before .now i will create a bridge and test how stable it is |
How did it get set to Managed Access Point in the first place - was this something you did? Because by default it should be in master mode I think. |
@JamesH65 No, I reinstall it and do not do any config even connect to a wifi hotspot. and the Manager mode is the default mode. until i run hostapd on the interface , it turn to Master mode. |
test it for 5 hours , it works prefect ! |
@JamesH65 thanks for your fix ! a great work! |
brctl addbr br0
brctl addif br0 eth0
brctl addif br0 wlan2
then the access point can connect to internet ,but after a while ,system will lose response
then i use a usb ethernet connect to the pi , i got : eth1 。when bridge to eth1,all works fine 。
i also test the onboard wifi : wlan0 , have the same issue .
The text was updated successfully, but these errors were encountered: