Really a straightforward setup for the most part, the question I have is why do you have TWO ethernet ports going to the hypervisor on the left??
You only need one port going to a smart switch for example if it was there instead of the hyper visor.
Thus I would need to understand what the hypervisor is doing>>> I would be afraid of some connection between those hypervisor ports and looping etc..............
Concur, with bpwl AND THE LINK!!! One bridge, all vlans with interface bridge, and bridge does no DHCP.
The one that struck me is there should be a trusted vlan to all smart devices ( and all smart devices should get an IP on that vlan).
I dont see that as the hypervisor left side and right side dont have a common vlan. Vlans are cheap LOL.
Once you have answered the questions in both posts, I will have a bit better understanding to tackle the config.
+++++++++++++++++++++++++++
By the way to comment coherently on your config, the whole export minus router serial number, public WANIP info, keys etc would be needed.
For example I dont see any FW rules, interface lists etc...... A config is the sum of many integrated parts!!!
Thanks for your time and effort answering and trying to understand my perhaps a bit odd usecase and setup. I have submitted an answer to bpwl, please have a look if possible. I hope I have answered most of your questions in that reply. I will add some answers here as well just so I feel I have done my best to provide the required information.
Sorry for late reply. I have been away for most of the weekend.
Thus I would need to understand what the hypervisor is doing>>> I would be afraid of some connection between those hypervisor ports and looping etc..............
The hypervisors are terminating the trunk connections routing the vlans to the intended VM's. Each device on the each vlan on the right hand side hypervisor has no other connections. I far as I can see there do not seen very likely for any risk of loops. The hypervisor on the left holds two VM's that should have access to VLAN10 and VLAN20 only over port 8080 and 443 (TCP). Else these VM's have also access to another network not part of this concept and schematics, but will be needed in the future. There of why I like to limit their access to these vlans. The intention is for these VM's to set up the physical test machines, trigger tests and gather test results. Why they need to share a trunk port is due to the lack of physical port on the router. BUT I really like to understand how this can be achieved as I see the possibility to share physical trunk ports among multiple bridges quite useful in the future.
I have considered buying a separate vlan aware switch to get around this need of sharing a trunk port.
The one that struck me is there should be a trusted vlan to all smart devices ( and all smart devices should get an IP on that vlan).
I have seen this option for marking a bridge port as "trusted" but I have yet not looked into it. Will do that right after finishing these replies.
I will have to look up the possibility to make a vlan also trusted when I find out what "trusted" actual means.I dont see that as the hypervisor left side and right side dont have a common vlan. Vlans are cheap LOL.
Don't know what you are thinking of here, but it got me thinking of how to actual trigger these tests on the VM's on machines marked with A, B, C,and D from the VM's on the left hypervisor marked with J and K. Thanks for pushing me there.
Probably need a separate vlan for trigger the tests. As stated vlans are cheep!Do u feel like I have answered all questions of have I missed out on any? most answers are probably in the answer to pbwl. Perhaps more questions have popped up?
I really do appreciate the effort you put into my learning.
Thanks!Statistics: Posted by mr2web — Mon Jan 22, 2024 6:13 pm
