Hi Roberto,
I'm very interested in helping you with Open vSwitch.
Please, just tell me how I can git clone, or svn check out, that
branch you are working on.
I can do tests with some Buffalo and TP-Link routers.
Thanks ...
On 02/10/2014 11:32 AM, Roberto Riggio wrote:
> On 10/0
On Mon, Feb 10, 2014 at 2:32 PM, Roberto Riggio
wrote:
> On 10/02/14 11:49, Helmut Schaa wrote:
>> What did you change to get this working now?
>
> I started from a clean build. In the previous version I played
> a little bit with verious version of OVS and some hack to the
> netidf script. Everyt
On 10/02/14 11:49, Helmut Schaa wrote:
> What did you change to get this working now?
I started from a clean build. In the previous version I played
a little bit with verious version of OVS and some hack to the
netidf script. Everything worked as expected on new image built
from scratch.
BTW the
On Fri, Feb 7, 2014 at 4:45 PM, Roberto Riggio
wrote:
> On 29/11/13 16:24, Helmut Schaa wrote:
>> I'd appreciate any testing beside my own :D
>
> Hi, I did some testing on some alix boards. The config
> I'm using is the following:
>
> config device
> option name br-ovs
> option typ
ok, excuse the ignorance, i see the patch, i see the git branch, hows this
branch get integrated to openwrt ?
On Tue, Feb 4, 2014 at 4:31 AM, Helmut Schaa wrote:
> On Tue, Feb 4, 2014 at 9:16 AM, Roberto Riggio
> wrote:
> > On 04/02/14 09:09, Helmut Schaa wrote:
> What if you write the con
On 29/11/13 16:24, Helmut Schaa wrote:
> I'd appreciate any testing beside my own :D
Hi, I did some testing on some alix boards. The config
I'm using is the following:
config device
option name br-ovs
option type ovs
list ifname eth0
config interface wan
option if
On 04/02/14 10:31, Helmut Schaa wrote:
> But it works if you create it manually with ovs-vsctl?
Yes the manual workflow works fine: create bridge, add interfaces
set cotnroller.
R.
--
Roberto Riggio, Ph.D.
CREATE-NET
Network & Security S
On Tue, Feb 4, 2014 at 9:16 AM, Roberto Riggio
wrote:
> On 04/02/14 09:09, Helmut Schaa wrote:
What if you write the config file after boot and run /etc/init.d/network
reload?
Does it also end up in a loop?
>>>
>>> Just tried, no, it does not loop.
>>
>> Ok, this helps a lot I gues
On 04/02/14 09:09, Helmut Schaa wrote:
>>> What if you write the config file after boot and run /etc/init.d/network
>>> reload?
>>> Does it also end up in a loop?
>>
>> Just tried, no, it does not loop.
>
> Ok, this helps a lot I guess.
> Maybe OVS is not up and running yet during boot or not yet
On Mon, Feb 3, 2014 at 6:03 PM, Ronaldo Zacarias Afonso
wrote:
> I'm trying to build a fresh OpenWRT and didn't find that Open vSwitch
> patch you mentioned.
>
> Can you please point me where it is?
It's just an RFC for now but you can find a current version here:
https://github.com/hscha
On Mon, Feb 3, 2014 at 6:53 PM, Roberto Riggio
wrote:
> On 03/02/14 16:57, Helmut Schaa wrote:
>> What if you write the config file after boot and run /etc/init.d/network
>> reload?
>> Does it also end up in a loop?
>
> Just tried, no, it does not loop.
Ok, this helps a lot I guess.
Maybe OVS is
On 03/02/14 16:57, Helmut Schaa wrote:
> What if you write the config file after boot and run /etc/init.d/network
> reload?
> Does it also end up in a loop?
Just tried, no, it does not loop. However I noticed that by running
/etc/init.d.network restart
I get:
Command failed: not found
and in
Hi,
I'm trying to build a fresh OpenWRT and didn't find that Open vSwitch
patch you mentioned.
Can you please point me where it is?
I have a Buffalo and a TP-Link router here and I can help doing some
tests.
Thanks ...
On 02/03/2014 01:57 PM, Helmut Schaa wrote:
> Hi Roberto,
>
>
Hi Roberto,
On Sun, Feb 2, 2014 at 9:01 PM, Roberto Riggio
wrote:
> Hi,
>
> I'm testing your patch with this configuration in /etc/config/network
>
> config device
> option name 'ovs'
> option type 'ovs'
> list ifname 'eth0'
>
> config interface
> option ifname 'ov
Hi,
I'm testing your patch with this configuration in /etc/config/network
config device
option name 'ovs'
option type 'ovs'
list ifname 'eth0'
config interface
option ifname 'ovs'
option proto 'dhcp'
However at boot the router enters in an infinite loop:
Add a new device type "ovs" to define openvswitch (pseudo-) bridges.
For setting up oppenvswitch bridges the "ovs-vsctl" utility is used
within system-ovs.* and might be replaced with plain JSON-RPC in the
future.
Signed-off-by: Helmut Schaa
---
This is a first RFC of openvswitch integration in
16 matches
Mail list logo
