parent
0044bde391
commit
765f4cf311
|
@ -0,0 +1,21 @@
|
||||||
|
{
|
||||||
|
"comments": [
|
||||||
|
{
|
||||||
|
"unresolved": true,
|
||||||
|
"key": {
|
||||||
|
"uuid": "dff29800_37c3725c",
|
||||||
|
"filename": "specs/2023.2/erspan-for-tap-as-a-service.rst",
|
||||||
|
"patchSetId": 1
|
||||||
|
},
|
||||||
|
"lineNbr": 360,
|
||||||
|
"author": {
|
||||||
|
"id": 8313
|
||||||
|
},
|
||||||
|
"writtenOn": "2023-05-03T13:28:08Z",
|
||||||
|
"side": 1,
|
||||||
|
"message": "I still miss the part how the tunnel is created, and what will be the source IP of it. In my env it is the first interface\u0027s IP, but I doubt that this is something users can count on.\nBence (rubasov) suggested to have some kind of cfg option for this, but at the moment I don\u0027t know how to force OVN or OVS to use specific address.\nFor OVN it is more difficult as OVN always creates the OVS mirror port on br-int.",
|
||||||
|
"revId": "963071c2469948e3e045b2c50f9c3dfec9bc70d0",
|
||||||
|
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
|
||||||
|
}
|
||||||
|
]
|
||||||
|
}
|
Loading…
Reference in New Issue