Hello,
we would need some functionality on manipulating packets when packet is
exiting outgoing OVS port.
I.e. some actions could be: change/anonymize mac/IPs for src/dst, or remove
some tunnel header (vxlan, gtp, gre), truncate the payload etc.
So, one option can be to write some code than can be
headers before
delivering it to the (monitoring) tool on outgoing port.
thanks,
jm
On Mon, Oct 9, 2017 at 6:31 PM, Ben Pfaff wrote:
> On Sun, Oct 08, 2017 at 11:19:17PM +0200, Juraj Markotic wrote:
> > we would need some functionality on manipulating packets when packet is
> > exiti
help out
> the folks who are working on it.
>
> On Mon, Oct 09, 2017 at 09:35:42PM +0200, Juraj Markotic wrote:
> > Hello,
> > thanks for feedback.
> > I know OVS can truncate payload and that in can modify mac/IPs in header
> > (i.e. like doing NAT).
> > I also kno
he
> header.
>
> On Mon, Oct 09, 2017 at 10:45:10PM +0200, Juraj Markotic wrote:
> > I will check on about GTP ongoing activities (I saw some actitvities on
> > providing capabilities to match on GTP-C/GTP-U packets).
> > maybe dumb question, but any pointer on how to remo
Hello,
I think I saw once a method to match in openflow rule on certain bytes in
payload in order to apply some action.
I can't seem to find it looking at documentation.
I would need to match on incoming GTP packet. Meaning there is some UDP
packet (port 2152). Inside this packet there is GTP head
