If you have a specific test in mind to try to define the trigger (type and volume of traffic) and solution, would be happy to assist. So could be right, type and volume of traffic could be causing issues, and perhaps Cisco images are programmed for subset of type and rate of traffic in LAB (and relatively restrictive), similar to VIRL issues cisco has (and features).Īnother indication is that IOL image would segment fault when large volume traffic would be put through them, but this is not very scientific approach (I had Servers attached such as Windows servers etc.). Additional idea is to use separate network card on host and bridge to external switch not carrying local LAN traffic (defeats the purpose of LAN remote access). IOL/IOSv can't handle the rate, perhaps its better to isolate it from "promiscuous" nature, which I tried to do by putting built in switch object between cloud and IOSv.
If traffic volume and types of busy traffic is a problem, i.e.
Reason normally I would do this is to have VLAN 1 in GNS3 IOL/IOSv for management of switches over LAN, makes things much easier to remotely manage topologies and ssh. I have "looked" at the traffic via wireshark, and since its bridged to local LAN of my host PC (Well GNS3 VM bridged to LAN), its everything the host (PC) sees (a lot) connected to local switch for home LAN (its TP Link managed switch).
0 kommentar(er)
