When connecting to VPN from a network that blocks or mangles UDP, you need to always wait for the "Reconnect with TCP" to happen automatically. If you already know that you are on a network where UDP won't work, you always need to wait for the online detection to complete. Showing the button right away allows you to reduce the time until you can get it working.
Always show "Reconnect with TCP" if available #673
Closed
opened 2025年11月20日 09:29:26 +01:00 by fkooman
·
3 comments
fkooman
commented 2025年11月20日 09:29:26 +01:00
When connecting to VPN from a network that blocks or mangles UDP, you need to always wait for the "Reconnect with TCP" to happen automatically. If you already know that you are on a network where UDP won't work, you always need to wait for the online detection to complete. Showing the button right away allows you to reduce the time until you can get it working.
fkooman
added the 2025年11月20日 09:29:26 +01:00
enhancement
label
dsteuer
commented 2025年11月20日 10:10:43 +01:00
+1
+1
jwijenbergh
self-assigned this 2025年11月20日 10:49:03 +01:00
jwijenbergh
commented 2025年11月20日 10:58:11 +01:00
in my opinion: We should go one step further, maybe have a "connect with TCP" button, or remember which networks block UDP. Even if we show the button during connecting, it would still be a reconnect. If you already know UDP won't work, reconnecting is still a waste
in my opinion: We should go one step further, maybe have a "connect with TCP" button, or remember which networks block UDP. Even if we show the button during connecting, it would still be a reconnect. If you already know UDP won't work, reconnecting is still a waste
jwijenbergh
referenced this issue from a commit 2026年02月24日 14:46:46 +01:00
jwijenbergh
commented 2026年02月24日 14:49:20 +01:00
fix has been committed, will be in a new version this week
fix has been committed, will be in a new version this week
jwijenbergh
closed this issue 2026年02月24日 14:49:21 +01:00
jwijenbergh
referenced this issue from a commit 2026年03月16日 11:16:45 +01:00
Sign in to join this conversation.
No Branch/Tag specified
master
upstream-deb
openvpn-persistent
1.x
4.7.2
4.7.1
4.7.0
4.6.0
4.5.1
4.5.0
4.4.99.0
4.4.0
4.3.1
4.3.0
4.2.99.1
4.2.99.0
4.2.1
4.2.0
4.1.99.0
4.1.3
4.1.2
4.1.1
4.1.0
3.1.1
4.0.1
4.0.0
pr-3.3.1
pr-3.3.0
pr-3.2.0
3.1.0
3.0.0
2.2.1
2.2.0
2.1.0
2.0.0
1.1
1.0.3
1.0.2
1.0.1
1.0rc17
1.0rc16
1.0rc15
1.0rc14
1.0rc13
1.0rc12
1.0rc11
1.0rc10
1.0rc9
1.0rc8
1.0rc7
1.0rc6
1.0rc5
1.0rc4
1.0rc3
1.0rc2
1.0rc1
0.8
0.7.2
0.7.1
0.7
0.6.1
0.6
0.5.1
0.5
0.3
0.2.1
0.2
0.1.1
0.1
Labels
No labels
bug
documentation
duplicate
enhancement
has-fix
help wanted
high priority
invalid
low priority
maybe
new-release
onhold
packaging
planned-go
question
wireguard
wontfix
work in progress
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 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
eduVPN/linux-app#673
Loading...
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?