apache / apache/cloudstack

With VR + VNF + L2 Network, the VMs in L2 Network cannot be reached from the Internet (But the opposite is possible)

未关闭
#9,791 15 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
type:enhancement
主要语言
Java
星标
3.1k
派生
1.4k
平均合并
6 天 19 小时
30 天内合并 PR
32

描述

##### ISSUE TYPE

* Bug Report

##### COMPONENT NAME

~~~
VR + VNF
~~~

##### CLOUDSTACK VERSION

~~~
4.19.1
~~~

##### CONFIGURATION

Advanced Networking
VPC
VNF + L2 Network

##### OS / ENVIRONMENT

##### SUMMARY

We have 1 VPC and 1 L2 Network connected together with a VNF (PFsense) in between.

Results Summary:
- Test 1: From L2 VM (10.26.8.230) to VPC VM (10.26.1.250) - PASS
- Test 2: From VPC VM (10.26.1.250) to L2 VM (10.26.8.230) - FAILED
- Test 3: From L2 VM (10.26.8.230) to Private Gateway VM (10.88.5.82) - PASS
- Test 4: From Private Gateway VM (10.88.5.82) to L2 VM (10.26.8.230) - FAILED

Background:
We’ve allowed any on the VNF firewall rules as attached in the screenshot below:

![Screenshot 2024-10-14 at 9 03 26 PM](https://github.com/user-attachments/assets/fcddf19d-3c10-4e12-8571-e7144e5a8ea2)

Traffic is allowed any on 10.26.1.254 interface

![Screenshot 2024-10-14 at 9 03 55 PM](https://github.com/user-attachments/assets/b4fe623e-c3f8-42ef-9bfe-f30138b934aa)

Traffic is allowed any on 10.26.8.254

We then run some tests.

Test 1: From L2 VM (10.26.8.230) to VPC VM (10.26.1.250)
![Screenshot 2024-10-14 at 9 04 32 PM](https://github.com/user-attachments/assets/0e003313-9e20-4d48-9da4-9f313a11f2bc)

Results: Ping and traceroute test from 10.26.8.230 to 10.26.1.250 works as expected. (PASS)

![Screenshot 2024-10-14 at 9 05 11 PM](https://github.com/user-attachments/assets/c37a7f27-9a61-49e1-90ca-10dafcf3061a)

Test 2: From VPC VM (10.26.1.250) to L2 VM (10.26.8.230)

![Screenshot 2024-10-14 at 9 05 32 PM](https://github.com/user-attachments/assets/4d9fde56-11c6-411f-9095-53223fe8e3da)

Results: Ping and traceroute test from 10.26.1.250 to 10.26.8.230 is not possible (FAILED)

![Screenshot 2024-10-14 at 9 06 01 PM](https://github.com/user-attachments/assets/8f2d9fa8-a4bf-428d-a82f-fd3f29f1d5a0)

Test 3: From L2 VM (10.26.8.230) to Private Gateway VM (10.88.5.82)
![Screenshot 2024-10-14 at 9 07 42 PM](https://github.com/user-attachments/assets/94cdf87e-7ab1-408d-b22d-36d1dba36e71)
Results: Ping and traceroute test from 10.26.8.230 to 10.88.5.82 works as expected (PASS)

Test 4: From Private Gateway VM (10.88.5.82) to L2 VM (10.26.8.230)
![Screenshot 2024-10-14 at 9 08 14 PM](https://github.com/user-attachments/assets/96a3fd00-2c6a-47d5-a5f6-8fdbf03ededd)

Results: Ping and traceroute test from 10.88.5.82 to 10.26.8.230 does not work (FAILED)
![Screenshot 2024-10-14 at 9 08 36 PM](https://github.com/user-attachments/assets/f2f52757-e0d9-4a5b-beb9-9e084293a244)

We've been trying to debug Tests 2 and 4 for a while now with no sucess. Anyone has any ideas?
Or is Cloudstack designed not to allow this to be possible?

##### STEPS TO REPRODUCE

~~~
NA
~~~

##### EXPECTED RESULTS

~~~
Tests 2 and 4 should be able to work
~~~

##### ACTUAL RESULTS

~~~
Tests 2 and 4 does not work
~~~

贡献指南

打开贡献指南

调研方向

从已记录的 Advanced Networking、VPC、L2 Network 和 VNF (PFsense) 配置开始,然后使用列出的 ping 和 traceroute 路径重现 Tests 2 和 4。完成意味着确定非对称可达性是 CloudStack 缺陷还是预期行为,并记录已确认的 fix 或配置要求;未指定源文件或测试。

由索引模型根据 Issue 内容生成。

评估

领域
cloud, infrastructure, networking
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
活跃
描述清晰度
需要澄清
新手友好度
35/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。