Windows Server如果源IP未绑定到发送NIC,则不会发送IP数据包
我正在远程Linux服务器和本地Windows Server之间构建IP-IP隧道。
Windows Server不支持RAW IP-IP隧道,因此我开发了一个简单的应用程序,使Wintun使用。
说本地Windows Server绑定到IP_LOCAL,远程Linux服务器绑定到IP_Remote,并且隧道IP是IP_TUN。
当前,Windows Server可以从隧道中的远程Linux服务器中接收传入的数据包(IP_Remote-> ip_local,Inner Ip_client-> ip_tun)。
对于传出数据包(ip_tun-> ip_client),如果我将数据包路由到TUN NIC,则可以将数据包发送出去。
但是,如果我将数据包路由到Real NIC,则忽略了数据包。
因此,当源IP不绑定到相应的NIC时,似乎可以阻止数据包的发送。 (在上述情况下,由于IP_TUN不绑定到真正的NIC,因此即将发出的数据包被忽略。)
是否有任何可以禁用此类机制的配置? 感谢您的帮助。
I am constructing an ip-ip tunnel between remote linux server and the local windows server.
The windows server does not support raw ip-ip tunnel so I develop a simple app which makes usage of wintun.
Said the local windows server is bound to ip_local, the remote linux server is bound to ip_remote, and the tunnel ip is ip_tun.
Currently, the windows server can receive the incoming packet (outer ip_remote->ip_local, inner ip_client->ip_tun) from the remote linux server in the tunnel.
For the outgoing packet (ip_tun->ip_client), if I route the packet to the tun NIC, the packet can be sent out.
However, if I route the packet to the real NIC, the packet is ignored.
Thus there seems a mechanism that blocks the sending of packets when the source ip is not bound to the corresponding NIC.
(In the above case, because ip_tun is not bound to the real NIC, the outgoing packet is ignore.)
Is there any configuration that can disable such mechanism?
Thanks for any help.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
在注册表中启用IP路由,然后一切正常。
Enable ip routing in registry then everything ok.