Hey all quick question, when creating a tunnel port in OVS using the set
interface=gre does this connect to a preexisting tun or does OVS make it's
own? For example I have a tun0 device that I want to attach to my OVS port,
and it cannot be added (incompatible device), so I thought that I merely
ne
Yeah have gone down that route, but kinda defeats the purpose of SDN.
On Fri, Jul 26, 2013 at 12:25 PM, Ben Pfaff wrote:
> IP forwarding?
>
> On Fri, Jul 26, 2013 at 12:24:23PM -0700, Cali Ente wrote:
> > Gotcha, is there a known workaround to get OVS to communicated with
nd OVS only supports Ethernet (L2) devices.
>
> On Fri, Jul 26, 2013 at 12:05:21PM -0700, Cali Ente wrote:
> > Ahh no, I am having issues connecting a tun to OVS. I have been perusing
> > the documentation to see if it due to an improperly formatted
> > command/setup. I had t
e:
>
> https://drive.google.com/a/fiu.edu/?tab=mo#my-drive
>
>
>
>
> On Fri, Jul 26, 2013 at 2:23 PM, Cali Ente
> wrote:
>
>> Created tunnels using tunctl, but getting back to the original question
>> posted, when I asked about using GRE with tunnels, it was stated that OVS
x27;m sure,
what is the correct answer?
Thanks,
Cal
On Fri, Jul 26, 2013 at 11:19 AM, Dmita Levy wrote:
> How did you create the pre-existing tunnel? I would like to duplicate the
> issue you're having here on my test hosts.
>
>
> On Fri, Jul 26, 2013 at 2:16 PM, Cali Ente
>
? What does your topology look like?
>
> On Fri, Jul 26, 2013 at 2:05 PM, Cali Ente
> wrote:
>
>> Are you referring to something like this?
>> ifconfig
>>tun0 Link encap:UNSPEC HWaddr
>> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
>>
tap to tap VM's into the
> bridge?
>
> On Fri, Jul 26, 2013 at 1:33 PM, Cali Ente
> wrote:
>
>> As I thought, in that case, does anyone know of a way to connect a linux
>> tun device to OVS?
>>
>>
>> On Fri, Jul 26, 2013 at 9:19 AM, Jesse Gross wr
As I thought, in that case, does anyone know of a way to connect a linux
tun device to OVS?
On Fri, Jul 26, 2013 at 9:19 AM, Jesse Gross wrote:
> On Fri, Jul 26, 2013 at 8:54 AM, Cali Ente
> wrote:
> > Hey all quick question, when creating a tunnel port in OVS using the set
>
Hey all quick question, when creating a tunnel port in OVS using the set
interface=gre does this connect to a preexisting tun or does OVS make it's
own? For example I have a tun0 device that I want to attach to my OVS port,
and it cannot be added (incompatible device), so I thought that I merely
ne
Does anyone know why OVS removed this method from 1.10.0? I see in the
notes that ether_mac_random or something along those lines is supposed to
replace it, but there is still a reference to the method in
vport-internal_dev.c. I've circumvented the compiler error it throws by
adding the method into
27, 2013 at 10:29:13AM -0700, Cali Ente wrote:
> > Hey ben thanks again for the help. Just hoping to run my current
> > understanding of brcompat through you. Please let me know if this
> incorrect.
>
> Your logs show that you are using Open vSwitch 1.10.0. Open vSwitch
Sorry, I've been switching back and forth from 1.9 to 1.10, and now I'm
deciding if 1.9's brcompat capabilities are even necessary.
Thanks.
On Thu, Jun 27, 2013 at 10:31 AM, Ben Pfaff wrote:
> On Thu, Jun 27, 2013 at 10:29:13AM -0700, Cali Ente wrote:
> > Hey ben t
this level of stuff (so I dont have to continue pestering
you), probably the kernel and ovs kernel module?
Thanks again for the help, it is greatly appreciated.
Chris
On Wed, Jun 26, 2013 at 10:45 AM, Ben Pfaff wrote:
> On Wed, Jun 26, 2013 at 10:18:31AM -0700, Cali Ente wrote:
> > Ok
AM, Ben Pfaff wrote:
> On Wed, Jun 26, 2013 at 07:23:19AM -0700, Cali Ente wrote:
> > I'm working on porting over openvswitch to a MIPS based platform, and I
> > have run into an interesting issue. I have correctly compiled openvswitch
> > and it's kernel module, and hav
Hey all,
I'm working on porting over openvswitch to a MIPS based platform, and I
have run into an interesting issue. I have correctly compiled openvswitch
and it's kernel module, and have installed both. I can run all the
openvswitch executables and can even run the add-br and add-port commands.
Ho
Would the lack of the Linux bridge-utilities package cause these errors? Do
you know of any kernel requirements/configurations I should have enabled to
make sure OVS will run as expected?
On Mon, Jun 24, 2013 at 10:32 AM, Ben Pfaff wrote:
> On Mon, Jun 24, 2013 at 10:25:10AM -0700, Cali E
h to act as a compatible drop-in replacement for
> the Linux bridge, for environments where that was desirable.
>
> On Mon, Jun 24, 2013 at 10:00:53AM -0700, Cali Ente wrote:
> > So what was it's purpose? I was under the impression it helped facilitate
> > the bridging.
>
So what was it's purpose? I was under the impression it helped facilitate
the bridging.
On Mon, Jun 24, 2013 at 9:58 AM, Ben Pfaff wrote:
> On Mon, Jun 24, 2013 at 09:55:01AM -0700, Cali Ente wrote:
> > Hey everybody, just had a quick question regarding the br-compat module
>
Hey everybody, just had a quick question regarding the br-compat module
that I couldn't seem to find answered. I know in versions =<1.9.0 br-compat
is included, but 1.10.0 and on it has been removed. Does this mean that
br-compat is no longer needed by openvswitch to function?
Thanks,
Bob
_
19 matches
Mail list logo
