Opened 6 years ago
Last modified 6 years ago
#17475 closed defect
connect to bridge cause panic — at Version 1
Reported by: | Meno Abels | Owned by: | |
---|---|---|---|
Component: | network/hostif | Version: | VirtualBox 5.2.6 |
Keywords: | kernel bridge | Cc: | |
Guest type: | other | Host type: | other |
Description (last modified by )
Hello,
there are a lot of open issues about bridge but non of them seams to match to my problems. I use private bridges like the automatic created dockerbridge on linux or on macos a small script like this:
ifconfig bridge0 create ifconfig bridge0 10.24.1.1/24 up ifconfig bridge0 inet6 fd00::10:24:1:1/64 up sysctl net.inet.ip.forwarding=1
than i use the bridge device from virtualbox like:
<Network> <Adapter slot="0" enabled="true" MACAddress="0800273B3B52" type="82540EM"> <DisabledModes> <InternalNetwork name="intnet"/> <NATNetwork name="NatNetwork"/> </DisabledModes> <BridgedInterface name="br0"/> </Adapter> </Network>
now on both platforms linux as macos the host system is send to kernel stalls(panics). This behavior was occures since Version 5. My setups works perfect on VirutualBox 4. I would like to provide some crashlogs but on both platforms there is nothing written in to the log files and i not started to invest more time into it. On macos the OS Crashscreen is shown an reboot is triggered. On linux the system stop's and sysrq seams not work either.
Is there any chance to get this feature back working?
thx in advance
meno
I assume the examples are copied from different machines and that
br0
andbridge0
are the same bridge.When you say this started with version 5, what is the actual version you tried? Have you upgraded from version 4 straight to 5.2.6 (or have you just left the bug tracker's default unchanged)?