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 the
> > device? Perhap
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 the
> device? Perhaps using a middleman to bounce the comms back and forth?
> Thanks
>
>
> On Fri, Jul 26, 2013 at 12:18 PM, Ben Pfaff wrote:
>
> > Yo
Gotcha, is there a known workaround to get OVS to communicated with the
device? Perhaps using a middleman to bounce the comms back and forth?
Thanks
On Fri, Jul 26, 2013 at 12:18 PM, Ben Pfaff wrote:
> You can't attach a tun to an OVS bridge because it is an IP (L3)
> device and OVS only suppor
You can't attach a tun to an OVS bridge because it is an IP (L3)
device and 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 impr
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 the idea in my head that I needed to specify GRE for
the tun in order for OVS properly attach, but alas I misread the wiki.
On Fri, Jul 26, 2
OVS creates its own GRE tunnel so there is no need to have a pre-existing
adapter or create an additional adapter as far as I know. I only suggested
you use tunctl because I thought you would need to TAP a bridge like I do
here:
https://drive.google.com/a/fiu.edu/?tab=mo#my-drive
On Fri, Jul 26
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
creates it's own GRE tunnel to communicate, and does not use preexisting
tunnels, it seems like now you are contradicting this, so just so I'm sure,
what
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 wrote:
> tun0 is a preexisting tunnel, so what I'm trying to do is get OVS to
> communicate with this preexisting tunnel.
>
>
> On Fri, J
tun0 is a preexisting tunnel, so what I'm trying to do is get OVS to
communicate with this preexisting tunnel.
On Fri, Jul 26, 2013 at 11:14 AM, Dmita Levy wrote:
> I'm still a little confused as to what it is you're trying to accomplish;
> if you create a GRE port like this
>
> # ovs-vsctl ad
I'm still a little confused as to what it is you're trying to accomplish;
if you create a GRE port like this
# ovs-vsctl add-port br0 tun0 -- set interface tun0 type=gre
options:remote_ip=192.168.1.10
the tunnel should work with no problems. From what you're saying, it seems
like you're creatin
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
UP BROADCAST POINTOPOINT RUNNING NOARP MULTICAST MTU:1424
Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets
Hello Cali,
Have you tried using tunctl to create the tunnel adapter and then adding
that adapter to the bridge the gre port is assigned to? That being said,
what are you using the tun adapter for - is it tun/tap to tap VM's into the
bridge?
On Fri, Jul 26, 2013 at 1:33 PM, Cali Ente wrote:
> As
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
> > interface=gre d
On Fri, Jul 26, 2013 at 06:19:59PM +0530, Prashant Chougule wrote:
> when adding new action the length in ofpacts_format of variable is i found
> 0 so it always set it to drop. anybody help am i doing or forgot to add
> something to do ?
No idea. Show us your code.
___
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
when adding new action the length in ofpacts_format of variable is i found
0 so it always set it to drop. anybody help am i doing or forgot to add
something to do ?
--
Thanks &Regards,
Prashant Chougule
___
discuss mailing list
discuss@openvswitch.org
ht
hi,
I am trying to add new action to ovs i stuck with when it enters in
compose_output_action it will not go for decode_openflow10 i declared in
action type in openflow-1.0.h and all necessary files. but always it takes
the drop action when i added my action with the flow.
--
Thanks &Regards,
P
17 matches
Mail list logo
