Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Bridged VPN scenario descriptions. #1749

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

abergmann
Copy link

@abergmann abergmann commented Jul 4, 2024

PR creator: Description

The 3 bridged VPN scenarios are currently not explained.

PR creator: Are there any relevant issues/feature requests?

This issue/question came up during a Slack chat conversation. No bug or Jira ticket involved.

PR creator: Which product versions do the changes apply to?

When opening a PR, check all versions of the documentation that your PR applies to.

  • SLE 15/openSUSE Leap 15.x

    • SLE 15 next/openSUSE Leap next (current main, no backport necessary)
    • SLE 15 SP6/openSUSE Leap 15.6
    • SLE 15 SP5/openSUSE Leap 15.5
    • SLE 15 SP4/openSUSE Leap 15.4
    • SLE 15 SP3/openSUSE Leap 15.3
    • SLE 15 SP2/openSUSE Leap 15.2
  • SLE 12

    • SLE 12 SP5

PR reviewer only: Have all backports been applied?

The doc team member merging your PR will take care of backporting to older documents.
When opening a PR, do not set the following check box.

  • all necessary backports are done

@taroth21 taroth21 requested a review from Amrita42 August 9, 2024 14:21
@taroth21
Copy link
Contributor

taroth21 commented Aug 9, 2024

Thanks a lot @abergmann ! @Amrita42 : As guide maintainer, could you take a look please and merge? Many thanks!

@Amrita42
Copy link
Contributor

Thanks , I will take a look this week as I was unwell last week!

(Machine 1) side is bridged to the <systemitem>eth1</systemitem>
network interface connected to LAN 1. Layer 2 traffic reaching
<systemitem>tap0</systemitem> via the bridge
<systemitem>br0</systemitem> will be forwarded via the VPN bridge
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you please rephrase , will be to is forwarded

On both sides, the Server (Machine 1) and Client (Machine 2), the
TAP device <systemitem>tap0</systemitem> is bridged to a local
network interface <systemitem>eth1</systemitem>. Layer 2 traffic
from the client network LAN 2 will be forwarded to the server
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is forwarded

@Amrita42
Copy link
Contributor

Minor nitpits , otherwise looks good. Could you please make the changes and then I can merge @abergmann , thanks

Samba or WINS server. Bridged VPN uses network TAP devices, that
simulate a link layer between the VPN endpoints and operate in layer
2 carrying Ethernet frames. This makes it possible to use non-IP
protocols (such as IPX) or applications relying on network
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes it possible to use non-IP protocols such as IPX or applications (i know this is existing content , if you can please make this change)

@Amrita42 Amrita42 self-assigned this Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants