Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

67 Excellent

About okovwvrv

  • Rank
    Junior Member

Recent Profile Visitors

72 profile views
  1. great discussion as well. Could you pm me your file? I can not make out Q38, and do not have the referred to diagram.
  2. I took the exam last month and passed. I used the Cisco Platinum Library material, the coding packets tut to stand up my own lab, and read the Cisco Press SD-WAN book that is on OReilly, plus he material and labs from Cisco Live, the certified guide material from cisco ie. the ones post viptela documentation. I learnt alot through the process. Some of the exam questions I would say are subjective. At least one I'd say there is no 'most' correct answer. I was probably over prepared because I was interested in exactly how to use the technology.
  3. On rereading I believe you are correct. A is not part of the CICD pipeline as it is deployment and there for incorrect. So a step withing the pipeline will be C.
  4. The pipeline question is looking for an understanding between continuous delivery and continuous deployment. The question is essentially is continuous deployment part of continuous integration and delivery.
  5. Start of October question count is 110 apparently. There is not too much material available on this topic.
  6. Anyone sat this exam lately? Is it stable?
  7. Seems vceplus is now offline as well. Unsure if it's related but would not be surprised. Seems there will be only one supplier of VCE software.
  8. A+ VCE is no longer in play store or the Microsoft store. Lots of complaints and requests for refunds if you Google. Seems the client contacts what used to be the A+ backend servers to open a file. Now those servers are gone no new files can be opened. If you have a previous file that can be opened. The only other option is avanset.
  9. I've created a couple of containers and linked them to Dcker Hub for automated build CI/CD. The first is a generic base container based upon Phusion 18.04 that implements xorgxrdp and includes the PulseAudio modules for sound across the remote desktop. The example provided in the run script will give you a lxterminal session if you build against it. The second is an example of implementing firefox upon the base-xrdp build. I'll add a wireshark build when I get the chance but this should be relatively easy upon the base. Outside of this there would be a need to add the wireshark instance into eve-community edition monitoring via feeding the xrdp session into guacamole such that it displays in html5. Github Repo [Hidden Content]
  10. I should have said that if deploying to Azue you need D3 hardware from memory. It may have changed since but D3 supports nested virtualisation (not available on AWS) which enables you to use eve on Azure. You of course then still need a way to reach outside of Azure and hence the pnet9 as nat cloud. If I get time today I'll look at finishing the docker file to support apps. Last problem that i had was really that firefox/chrome actually required a greater shared memory because otherwise there was some failure when opening multiple tabs but I have since lost my notes when I was working on it. Given spare time I'll see what I can do. I may also get some time to try and replace the monitoring of ports with a internal wireshark container instead of external such that it also functions with Azure.
  11. There is an update to Eve-NG community version that enables containers. [Hidden Content]. Last I used this it seemed to work and I joined to cSRX firewalls together and they could ping. You can also turn pnet9 into a NAT cloud such that you can install eve-ng on azure. Turn pnet9 to be a NAT cloud for external NAT access and supply DHCP to internal management interfaces like in pro. Edit /etc/network/interfaces for pnet9 change to iface eth9 inet manual auto pnet9 iface pnet9 inet static bridge_ports eth9 bridge_stp off bridge_hw 00:00:00:00:00:01 #required to ensure bridge is selected address #must match with DHCP server netmask network Save file Install DHCP server $> sudo apt-get install isc-dhcp-server Configure the DHCP server to be attached to Cloud9. $>sudo vi /etc/default/isc-dhcp-server Scroll to the bottom and edit the line below: $> INTERFACES=”pnet9” Configure the DHCP by $> sudo vi /etc/dhcp/dhcpd.conf Comment out or delete the existing lines and create the following: Authoritative; # EVE-NG NAT Interface subnet netmask { range; interface pnet9; default-lease-time 600; max-lease-time 7200; option domain-name "eve-ng.com"; option domain-name-servers; option broadcast-address; option subnet-mask; option routers; } Attach devices to pnet for NAT address in range with DHCP enabled. You may need to enable iptables on the host to push pnet9 through pnet0 essentially. ----- I had a docker file for using 18.04 phusion as the baseimage and deploying apps nto this for eve-ng as well....i'll try and find it today some time. I never completely finished that really....but would be easy enough to add whatever you wanted into it. Oh and some where else I had a 16 port openswitch in a container as well running on Eve....i wa looking at trying to get Sonic to run but did not have enough time and could not resolve in my head how to address the vol sharing parts from a user aspect.
  12. Have you created a license? Assuming you have I did have a similar issue when I first started it and I think the license may have been in the wrong place. Hve a look and see if thats the issue and/or run fixpermissions. If I've still got the image here some where I'll run it and and try. The chinese fork has alot f work done on the php components and enabling items that just are not in the Pro version and covers alot of what Pro does such as multiple accounts, docker support, hot linking etc. Its not bad but I don't like the font format changes etc but the upcoming text changes etc look ok as well. It certainly goes a long way to filling between Pro and community.
  13. Never had that problem with the chinese community version. They are developing the version and there is the preview for the next version up. Its good as the formal community version has stalled for any features for some time. I'm waiting qwig to come out as breakintheweb was the person who seemed to first try and take eve to the next level and then had to go his own way. Should be good.
  14. If your deploying to Azure then this change is also handy to give your lab access to the internet. [Hidden Content] Turns pnet9 into a NAT Cloud. If you want internet access from pnet9 then use iptables on the host to enable traffic between pnet9 and pnet0 and your done. Azure supports nested virtualisation on D3 machines so eve works on there but you need to do this to get inetrent access into the lab thats running.
  15. Sorry no ESXi to try upon. That ova does work on a VMWare workstation or used to I've not fired it up since when it was originally released.
  • Create New...