Skip to content

Commit 7de77e9

Browse files
committed
Address review
1 parent 9b85123 commit 7de77e9

1 file changed

Lines changed: 9 additions & 12 deletions

File tree

src/pages/how-to/browser-client.mdx

Lines changed: 9 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -50,9 +50,9 @@ When connecting via SSH:
5050
<img src="/docs-static/img/how-to-guides/browser-client/ssh-credentials-modal.png" alt="ssh-credentials-modal" className="imagewrapper-big"/>
5151
</p>
5252

53-
4. Adjust the SSH username in the credentials modal if required
54-
5. Click **Connect**
55-
6. A terminal window will open in your browser with your SSH session
53+
3. Adjust the SSH username in the credentials modal if required
54+
4. Click **Connect**
55+
5. A terminal window will open in your browser with your SSH session
5656

5757
<p>
5858
<img src="/docs-static/img/how-to-guides/browser-client/ssh-terminal-connected.png" alt="ssh-terminal-connected" className="imagewrapper-big"/>
@@ -137,6 +137,12 @@ The Browser Client maintains NetBird's security standards:
137137
- Windows 11 and Windows Server 2025 are currently not supported for RDP connections
138138
- Use Windows 10 or earlier Windows Server versions for RDP access
139139

140+
**Browser Client Constraints**
141+
- **Relay-only connections**: No direct P2P connections (may increase latency)
142+
- **Advanced features**: Some SSH/RDP features are not available (SFTP, sound, file shares, etc.)
143+
- **Concurrent connections**: Browser resource limits may affect multiple simultaneous sessions
144+
- **RDP resolution changes**: Require reconnection (not seamless)
145+
140146
## Technical Implementation
141147

142148
For technical details on the Browser Client architecture, see the [Browser Client Technical Architecture](/about-netbird/browser-client-architecture) documentation.
@@ -158,15 +164,6 @@ The RDP implementation is 100% client-side using:
158164
- **RDCleanPath proxy**: IronRDP's rdp proxy reimplemented to make use of NetBird
159165
- Both components are compiled to WebAssembly and run entirely in the browser
160166

161-
## Limitations
162-
163-
The Browser Client has some limitations compared to native clients:
164-
165-
- **Relay-only connections**: No direct P2P connections (may increase latency)
166-
- **Advanced features**: Some SSH/RDP features are not available (SFTP, sound, file shares, etc.)
167-
- **Concurrent connections**: Browser resource limits may affect multiple simultaneous sessions
168-
- **RDP resolution changes**: Require reconnection (not seamless)
169-
170167
## Security Considerations
171168

172169
When using the Browser Client:

0 commit comments

Comments
 (0)