Each VPN *must* be configured to use # a hardcoded/persistent tun device by explicitly adding the line "dev tunX" # to its configuration (e.g., /etc/openvpn/nf) where X in tunX is a # unique number between 0 and your lucky number of choice. description = Spain, Europe # The tun device hardcoded for this VPN. # Can be used to for example describe the country where this VPN ends up. name = vpn0 # The description of this VPN which will be displayed in the web interface. The name is represented by the filepath to the # configuration file, e.g., cuckoo would represent /etc/openvpn/nf # Note that you can't assign the names "none" and "internet" as those would # conflict with the routing section in nf. # Are VPNs enabled? enabled = yes # Comma-separated list of the available VPNs. Routes all traffic through one of perhaps Which provides fake services - running on the Routes all traffic to an InetSim instance. Including traffic within the VMs’ subnet.įull internet access as provided by the given Therefore also the default routing option). Not require the Cuckoo Rooter to be run (and No routing whatsoever, the only option that does Since then various bugs have been resolvedĪnd more network routing options have been added.įollowing is the list of available routing options. Interface we will now walk through the dynamic network routing components thatĪllow for much more granular network routing.Īs outlined in the introduction for this chapter of the documentation it hasīeen possible since Cuckoo 2.0-rc1, when we introduced the Cuckoo Rooter, Having discussed the old school method for routing analyses through a network
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |