sni-proxy: Anwendungsbeispiel und Funktionsweise #12

Merged
jkimmel merged 2 commits from jkimmel/docs:sni-proxy into master 2023-03-01 21:37:10 +01:00
Owner
No description provided.
jkimmel force-pushed sni-proxy from f64912cfd6 to 530fd1d12f 2023-02-16 22:37:08 +01:00 Compare
jkimmel force-pushed sni-proxy from 530fd1d12f to 442fb7ec4c 2023-02-16 22:41:30 +01:00 Compare
jkimmel force-pushed sni-proxy from 442fb7ec4c to 84c0881fee 2023-02-16 22:49:04 +01:00 Compare
jkimmel force-pushed sni-proxy from 84c0881fee to 58eece7c8e 2023-02-16 23:00:23 +01:00 Compare
SebaBe reviewed 2023-02-24 14:29:50 +01:00
@ -40,3 +54,4 @@
Sind Client und Server IPv6-fähig passiert der Verbindungsaufbau ganz normal direkt über IPv6 ohne extra Proxy.
```mermaid
sequenceDiagram
First-time contributor

DNS -->>- client: 2001:db8::

-> DNS gibt 2001:db8:1:: zurück

DNS -->>- client: 2001:db8:: -> DNS gibt 2001:db8:1:: zurück
Author
Owner

Oh, gut gesehen.

Oh, gut gesehen.
jkimmel marked this conversation as resolved
jkimmel force-pushed sni-proxy from 58eece7c8e to 110b7d76d9 2023-02-24 15:22:23 +01:00 Compare
jkimmel force-pushed sni-proxy from 110b7d76d9 to 56550ee12e 2023-03-01 21:36:49 +01:00 Compare
jkimmel merged commit 56550ee12e into master 2023-03-01 21:37:10 +01:00
Sign in to join this conversation.
No reviewers
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: freifunk-franken/docs#12
No description provided.