Physical guest is not getting internet during analysis when internet routing is used about capev2 HOT 5 CLOSED

hello, that is not how physical routing works. cape can't control routing of physical machines, so you need to handle that on your switch/router

from capev2.

Thanks for responding. Im confused my understanding of Cape router is that it routes traffic from the dirty line to the interface going to the guest machine temporarily. Both devices can seen each other fine. The analysis and re-imaging with FOG both work fine. Why do you think its a physical routing issue?

Below is a diagram of my lab network.

from capev2.

yes it does but for the VMs that are on CAPE server, not for the physical host. Physical hosts network is managed by router/managed switch, we can't hack each router and forward traffic, that is your task to set some firewall that will route all traffic from that machine to specific exit node, but if that just internet than it should works out of the box with basic windows configuration. So if you configured your fog client with internet, it will have internet, but we can't do nothing there

from capev2.

I think I figured out a solution and wanted to post it here for other people. My CAPE guest machine only has one NIC going to the managed switch back to the CAPE host. I can add another NIC to the CAPE guest and using VLANs on the switch connect to the 4g router in an isolated manner. On my switch I can enable port mirroring and send that back to the CAPE host with an additional NIC on the CAPE host for this. In the Auxiliary conf I can tell tcpdump to monitor that NIC and see the network traffic from the guest host.

from capev2.

thanks for details, and glad that you solved it

from capev2.