On Sun, 27 May 2018 19:06:47 +0900,
Bilal Saleem wrote:
>
> I am using gre header to pass some information that is used by a switch for
> rules, there could be multiple end-nodes and each end node switch will
> strip the header manually(by using code written in c) and forward the
> packet to host.
I am using gre header to pass some information that is used by a switch for
rules, there could be multiple end-nodes and each end node switch will
strip the header manually(by using code written in c) and forward the
packet to host. That is why there are no *gre tunnel start/end point *
address*.*
Hi Yi,
I not sure what will be remote_ip for gre interface configuration can you
help me with that?
On Thu, May 24, 2018 at 5:22 PM, Yi Tseng wrote:
> I believe that you need to config the GRE tunnel manually to your data
> plane first.
>
> For example, you need to setup interface type to *gr
I believe that you need to config the GRE tunnel manually to your data
plane first.
For example, you need to setup interface type to *gre* when you add an
interface to the OvS switch.
*ovs-vsctl add-port br0 gre0*
*ovs-vsctl set interface gre0 type=gre options:remote_ip={another grp
tunnel end po
Hi,
I am working on simple topology as follows:
C
/ | \
Veth ports-S1 -- S2 --- S3 H1
I am sending raw packets cooked with GRE headers on Veth ports. I want to
create rules based on GRE key value like this:
match2 = parser.OFPMat
