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

Azure Virtual Gateway not using Route table

· 52CE 我爱测

In Azure, I have set up a virtual network and a gateway which is connected to an on-premise gateway. I have also set up a VM running OpenVPN Access Server. I have added a user-defined route to route traffic to the OpenVPN access …

问题原文

原帖链接 · Hein Gustavsen · CC BY-SA 4.0

In Azure, I have set up a virtual network and a gateway which is connected to an on-premise gateway. I have also set up a VM running OpenVPN Access Server. I have added a user-defined route to route traffic to the OpenVPN access server. Still, traffic from the on-premise gateway does not reach the openvpn access server.

Network diagram

I need to reach the OpenVPN client from the IPSec client, but I can't. I've used tcpdump on the OpenVPN server and I cannot see any traffic reaching it when trying to ping the OpenVPN client from the IPSec client.

IPSec client -> OpenVPN server = OK
IPSec client -> Azure VM = OK
IPSec client -> OpenVPN client = NOT WORKING
Azure VM -> OpenVPN client = OK
Azure VM -> IPSec client = OK

It seems to me like the Azure Virtual Gateway is not using the route table and the user-defined route, but the Azure VM does. Is there a reason why the azure gateway does not use the user-defined route?

The Azure Virtual Gateway is basic SKU.

已采纳解答

原帖链接 · Hein Gustavsen · CC BY-SA 4.0

I found that the problem was in the OpenVPN Access Server configuration. The iptables configuration did not allow traffic from external subnets to the VPN clients. I solved this by adding the subnet behind the IPSec client to Routing under VPN Settings in OpenVPN Access Server.

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

资料来源与适用范围

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

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

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