Looks like a similar bug here, but on HP ProLiant DL380p Gen8:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213887
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1013199
Title:
be2net
There are no problems with the drivers and looks like you are facing
configuration issues. Please contact the canonical support team who
might be able to help you out with the configuration issues.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It looks like this has something to do with iptables (even if there are
no iptables rules).
While messing around with something else I tried disabling bridge track
from passing through iptables and that seemed to fix the problem.
sysctl setting:
net.bridge.bridge-nf-call-iptables=0
Your configuration works on our setup without any issues.
auto eth0
iface eth0 inet manual
address 0.0.0.0
auto br0
#iface br0 inet dhcp
iface br0 inet static
address 172.16.17.40
netmask 255.255.0.0
network 172.16.0.1
bridge_ports eth0
bridge_fd 0
Hmm so either something has changed or my testing before was not 100%
accurate.
Using the below configuration I am unable to ping anything. Additionally
I can't talk to any resources via the default gateway (I have confirmed
I can do this without bridging in play), however I just noticed that I
With the below mentioned configuration, bridging works on our setup with
3.2.0-31
auto eth0
iface eth0 inet manual
auto br0
iface br0 inet dhcp
bridge_ports eth0
bridge_fd 9
bridge_hello 2
bridge_maxwait 12
bridge_stp off
Kernel is 3.2.0-31-generic as
Interesting you have a few options set differently then I do. I will try
your options shortly.
My configuration that isn't working is the following (just confirmed it
again):
auto eth1
iface eth1 inet manual
address 0.0.0.0
auto br0
iface br0 inet static
address 10.42.1.28
netmask
OK trying the following had not effect, still not working.
auto eth1
iface eth1 inet manual
address 0.0.0.0
auto br0
iface br0 inet static
address 10.42.1.28
netmask 255.255.254.0
network 10.42.4.0
bridge_ports eth1
bridge_fd 9
bridge_hello 2
bridge_maxwait 12
bridge_stp
I'm not entirely sure this bug is invalid.
We recently upgraded some of our HP blades and bridge networking stopped
working with the the 3.2.0-31 Ubuntu 12.04 LTS Kernel and the be2net
driver. I've tested a number of kernels and distros both with and
without the be2net driver and I can
This isn't about bringing up a bridge interface its about traffic flowing
over the bridged interface that isn't working.
When the interface is bridged - I can not ping another machine on the network.
When I just use the actual interface, I can ping.
--
You received this bug notification because
Repeating the steps to create the information in file does make bridged
network work whereas in OpenStack when it manages the interface doesn't
work. I'll test whether we can create this interface manually like this
for OpenStack to work.
--
You received this bug notification because you are a
@Stefan
I'm accompanying an affected user and we are focusing on a manual
method:
# ip link set dev eth0 down
# brctl addbr br0
# brctl addif br0 eth0
# ip link set dev eth0 up
# ip link set dev br0 up
# ip addr add 10.153.107.142/24 brd + dev br0
# ip route add default via 10.153.107.1
@Stefan
Using the updated bridging instructions provided by Stefan, I was able
to bring up br0 on Precise.
auto eth0
iface eth0 inet manual
auto br0
iface br0 inet static
address 192.168.1.2
netmask 255.255.255.0
network 192.168.1.0
gateway 192.168.1.1
bridge-ports eth0
bridge-stp
** Changed in: linux (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1013199
Title:
be2net driver used by HP BL460c bridge networking not working
To
I have the feeling this is probably not related to the be2net hardware at all.
I believe to remember vaguely that at some point in the past the behaviour if a
bridge interface changed in the way that it will not be up until one of its
ports is up. When I follow the exact description of
@Joe
A Lucid live session was attempted and it resulted in a worse failure: a
normal interface could not be initialised.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1013199
Title:
be2net driver
** Tags added: quantal
** Tags added: kernel-key
** Tags added: lucid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1013199
Title:
be2net driver used by HP BL460c bridge networking not working
bug 717388 is similar. In that bug, the Maverick kernel did not have an
issue. The Maverick, Natty, and Oneiric kernels will be tested to see
if they exhibit this bug. If they do, we can perform a kernel bisect to
find the commit that introduced the regression in Precise.
--
You received
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report at bugzilla.kernel.org [1]? That will allow the upstream
Developers to examine the issue, and may provide a quicker resolution to
the bug.
If you
Also, it would be great if you could test the bridge settings on a prior
release, such as Lucid. That will tell us if this is a regression, and
help figure out when it was introduced.
Do you think you would be able to try some prior kernels to identify
when the bug started happening?
--
You
- #4 same behaviour with a v3.5kernel
- #5 the problem was discovered after installing openstack on precise (compute
nodes build bridge for the vm private network, and this network was not
usable). Bridging has not been try out on a previous release such as Lucid.
-#6 currently it does not
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1013199
Title:
be2net driver used by HP BL460c bridge networking not working
To manage notifications about this bug go to:
We also tested the following kernel without success:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc6-precise/linux-
image-3.4.0-030400rc6-generic_3.4.0-030400rc6.201205061835_amd64.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
this is the involved server:
http://www.ubuntu.com/certification/hardware/201108-8817/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1013199
Title:
be2net driver used by HP BL460c bridge networking
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1013199
Title:
be2net driver used by HP BL460c bridge networking not working
To manage
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.5kernel[0] (Not a kernel in the daily directory) and install both the
linux-image and linux-image-extra .deb packages.
Once you've tested the
@Pierre
Also, do you happen to know if there was a prior release that did not
have this bug, such as Lucid? It would be very helpful to know what
release introduced this bug, if it is in fact a regression.
** Tags added: needs-upstream-testing
--
You received this bug notification because you
@Pierre,
One other question. I haven't tested all of your config settings to
setup the bridge. I was just curious if you tried this config on a
system with a driver other than be2net, just to confirm they are all set
properly?
auto br0
iface br0 inet static
address 192.168.1.10
netmask
28 matches
Mail list logo
