Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in
Toggle navigation
M
master-thesis
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Service Desk
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Packages & Registries
Packages & Registries
Package Registry
Container Registry
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Nico Schottelius
master-thesis
Commits
5a42c3ec
Commit
5a42c3ec
authored
Aug 22, 2019
by
Nico Schottelius
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Minor grammar change
parent
dac376e8
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
doc/Design.tex
doc/Design.tex
+2
-2
No files found.
doc/Design.tex
View file @
5a42c3ec
...
...
@@ -286,7 +286,7 @@ both support cleaning up old session entries,
our P4 based solution does not support this feature at the moment.
In figure
\ref
{
fig:p4switchstateful
}
we show the flow of a packet for
stateful translation in a P4 switch in detail. A
s can be seen an IPv6
stateful translation in a P4 switch in detail. A
n IPv6 only
host emits a packet that should be translated to IPv4. On a new
connection there will be no table entry in the P4 switch to
match. Thus the table mismatch causes the P4 switch to forward the
...
...
@@ -295,7 +295,7 @@ creates a table entry for the session and reinjects the packet into
the P4 switch. The P4 switch then processes the packet again, however
this time it finds a matching table entry. This entry causes
translation to happen to a specific IPv4 address, including higher
level protocol changes. After processing the IPv6 packet is output as
level protocol changes. After processing the IPv6 packet i
t i
s output as
a translated IPv4 packet. A second packet of the same session will
directly take the second path via table match, as the session ID will
stay the same.
\footnote
{
We use the quintuple (source address,
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment