大网数据广告活动
服务器运维问答

How do VPN servers/clients avoid routing their own remote connection packets through themself?

· 52CE 我爱测

I am trying to conceptualise how networking works under the hood for linux VPNs which use TUN interfaces. My current best guess is as follows (please correct me): Connection established to remote client/server. TUN interface crea…

问题原文

原帖链接 · 64bit_twitchyliquid · CC BY-SA 3.0

I am trying to conceptualise how networking works under the hood for linux VPNs which use TUN interfaces.

My current best guess is as follows (please correct me):

  1. Connection established to remote client/server.
  2. TUN interface created and brought up
  3. Routing table updated to set default gateway to the TUN interface

But wouldn't the packets destined for the remote client/server end up going into the TUN interface and forming a loop of sorts? How do VPN systems solve this? What is the gap in my understanding?

已采纳解答

原帖链接 · Jeremy Gibbons · CC BY-SA 3.0

You are correct that with purely destination-based routing this is a problem, if the destinations you are reaching through the tunnel overlap with routing needed for tunnel establishment, etc....

The way I have usually seen this done, and done it myself on various routers, is to use policy routing :

  • The router acting as a VPN endpoint keeps its default route pointing to the Internet through its ISP link
  • It also has a Policy Route with a source-based rule saying that traffic coming from the subnets behind it, whatever their destination, should be sent through the tunnel.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-01-11)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。