Il 23/12/2014 16:27, Gurucharan Shetty ha scritto:
I tried 2.3.0+git20140819-3 building it in wheezy with kernel 3.16 from
backports but bridge of my test was still not working:
auto xenbr0
allow-ovs xenbr0
iface xenbr0 inet static
address 192.168.1.90
netmask 255.255.255.0
Il 19/12/2014 17:04, Simon Horman ha scritto:
On Fri, Dec 19, 2014 at 11:43:42PM +0800, Thomas Goirand wrote:
On 12/19/2014 11:32 PM, Thomas Goirand wrote:
On 12/19/2014 10:25 PM, Simon Horman wrote:
On Fri, Dec 19, 2014 at 06:39:39PM +0800, Thomas Goirand wrote:
On 12/19/2014 11:50 AM,
I tried 2.3.0+git20140819-3 building it in wheezy with kernel 3.16 from
backports but bridge of my test was still not working:
auto xenbr0
allow-ovs xenbr0
iface xenbr0 inet static
address 192.168.1.90
netmask 255.255.255.0
network 192.168.1.0
broadcast
On 23 December 2014 at 03:12, Fabio Fantoni fabio.fant...@m2r.biz wrote:
For have it working I had to do service networking restart.
I found probably final solution applying also this patch:
Joe Stringer joestrin...@nicira.com writes:
I agree that this should be treated as a separate bug, yes please (I'm
just following up as it wasn't clear to me whether you're working on
this or not).
Ok, I'll report it as a new bug.
--
Stig Sandbeck Mathisen
--
To UNSUBSCRIBE, email to
On 12/19/2014 11:50 AM, Simon Horman wrote:
On Thu, Dec 18, 2014 at 05:30:42PM -0800, Joe Stringer wrote:
On 18 December 2014 at 01:00, Fabio Fantoni fabio.fant...@m2r.biz wrote:
One maintainer or debian developer can do a new build of ovs with the fix
available in 2.3.1 please?
* Version
On Fri, Dec 19, 2014 at 06:39:39PM +0800, Thomas Goirand wrote:
On 12/19/2014 11:50 AM, Simon Horman wrote:
On Thu, Dec 18, 2014 at 05:30:42PM -0800, Joe Stringer wrote:
On 18 December 2014 at 01:00, Fabio Fantoni fabio.fant...@m2r.biz wrote:
One maintainer or debian developer can do a new
Il 19/12/2014 15:25, Simon Horman ha scritto:
On Fri, Dec 19, 2014 at 06:39:39PM +0800, Thomas Goirand wrote:
On 12/19/2014 11:50 AM, Simon Horman wrote:
On Thu, Dec 18, 2014 at 05:30:42PM -0800, Joe Stringer wrote:
On 18 December 2014 at 01:00, Fabio Fantoni fabio.fant...@m2r.biz wrote:
One
On 12/19/2014 10:25 PM, Simon Horman wrote:
On Fri, Dec 19, 2014 at 06:39:39PM +0800, Thomas Goirand wrote:
On 12/19/2014 11:50 AM, Simon Horman wrote:
On Thu, Dec 18, 2014 at 05:30:42PM -0800, Joe Stringer wrote:
On 18 December 2014 at 01:00, Fabio Fantoni fabio.fant...@m2r.biz wrote:
One
On 12/19/2014 11:32 PM, Thomas Goirand wrote:
On 12/19/2014 10:25 PM, Simon Horman wrote:
On Fri, Dec 19, 2014 at 06:39:39PM +0800, Thomas Goirand wrote:
On 12/19/2014 11:50 AM, Simon Horman wrote:
On Thu, Dec 18, 2014 at 05:30:42PM -0800, Joe Stringer wrote:
On 18 December 2014 at 01:00,
On Fri, Dec 19, 2014 at 11:43:42PM +0800, Thomas Goirand wrote:
On 12/19/2014 11:32 PM, Thomas Goirand wrote:
On 12/19/2014 10:25 PM, Simon Horman wrote:
On Fri, Dec 19, 2014 at 06:39:39PM +0800, Thomas Goirand wrote:
On 12/19/2014 11:50 AM, Simon Horman wrote:
On Thu, Dec 18, 2014 at
One maintainer or debian developer can do a new build of ovs with the
fix available in 2.3.1 please?
* Version 2.3.0+git20140819-2 of openvswitch is marked for
autoremoval from testing on 2015-01-15.
* It is affected by RC bug #771863 https://bugs.debian.org/771863.
Without this fix
On 18 December 2014 at 01:00, Fabio Fantoni fabio.fant...@m2r.biz wrote:
One maintainer or debian developer can do a new build of ovs with the fix
available in 2.3.1 please?
* Version 2.3.0+git20140819-2 of openvswitch is marked for
autoremoval from testing on 2015-01-15.
* It is
On 15 December 2014 at 10:21, Gurucharan Shetty shet...@nicira.com wrote:
On Sat, Dec 13, 2014 at 2:03 AM, Stig Sandbeck Mathisen s...@debian.org
wrote:
I would like to clarify that 2.3.1 does get rid of the check on
$RUNLEVEL which was the original bug description.
That's great, thanks. :)
On Thu, Dec 18, 2014 at 05:30:42PM -0800, Joe Stringer wrote:
On 18 December 2014 at 01:00, Fabio Fantoni fabio.fant...@m2r.biz wrote:
One maintainer or debian developer can do a new build of ovs with the fix
available in 2.3.1 please?
* Version 2.3.0+git20140819-2 of openvswitch is
On Sat, Dec 13, 2014 at 2:03 AM, Stig Sandbeck Mathisen s...@debian.org wrote:
Gurucharan Shetty shet...@nicira.com writes:
I haven't looked at what needs to be done to handle those statements.
I welcome a patch, preferably sent to d...@openvswitch.org after
reading the CONTRIBUTING.md in the
Gurucharan Shetty shet...@nicira.com writes:
I haven't looked at what needs to be done to handle those statements.
I welcome a patch, preferably sent to d...@openvswitch.org after
reading the CONTRIBUTING.md in the openvswitch repo.
I assume the openvswitch repo is at
Control: severity -1 serious
Hello,
Since the service does not start under the new default init, and since
it also does not follow includes from /etc/network/interfaces, I would
think this justifies a serious severity. Updating the severity
accordingly.
(I feel less bad about bumping severity
My previous reply did not do a good job with the context. It made it
look like OVS 2.3.1 handles source or source-directory statements.
That is not correct, it does not handle those statements. I haven't
looked at what needs to be done to handle those statements. I welcome
a patch, preferably sent
19 matches
Mail list logo
