<commit_before>package vix

import (
	"fmt"
	"net"
	"strconv"
	"strings"
)

// VMware Fusion and Workstation
// come with predefined virtual switches,
// tailored for the most common uses cases.
//
// This type defines the common networking
// scenarios available for you to choose from,
// when adding network adapters to your virtual
// machines.
type NetworkType string

const (
	// Host-only networking provides a network
	// connection between the virtual machine
	// and the host computer, using a virtual
	// Ethernet adapter that is visible to the
	// host operating system. This approach can
	// be very useful if you need to set up an
	// isolated virtual network.
	//
	// If you use host-only networking, your
	// virtual machine and the host-only
	// adapter are connected to a private TCP/IP
	// network. Addresses on this network are
	// provided by the VMware DHCP server.
	//
	// Source: https://www.vmware.com/support/ws55/doc/ws_net_configurations_hostonly.html
	NETWORK_HOSTONLY NetworkType = "hostonly"

	// If you want to connect to the Internet
	// or other TCP/IP network using the host
	// computer's dial-up networking or broadband
	// connection and you are not able to give your
	// virtual machine an IP address on the external
	// network, NAT is often the easiest way to give
	// your virtual machine access to that network.
	//
	// If you use NAT, your virtual machine does not
	// have its own IP address on the external network.
	// Instead, a separate private network is set up
	// on the host computer. Your virtual machine gets
	// an address on that network from the VMware virtual
	// DHCP server. The VMware NAT device passes network
	// data between one or more virtual machines and
	// the external network. It identifies incoming
	// data packets intended for each virtual machine
	// and sends them to the correct destination.
	//
	// If you select NAT, the virtual machine can use
	// many standard TCP/IP protocols to connect to
	// other machines on the external network.
	// For example, you can use HTTP to browse Web
	// sites, FTP to transfer files and Telnet to
	// log on to other computers. In the default
	// configuration, computers on the external network
	// cannot initiate connections to the virtual machine.
	// That means, for example, that the default
	// configuration does not let you use the virtual
	// machine as a Web server to send Web pages to
	// computers on the external network.
	//
	// The NAT device is connected to the VMnet8 virtual switch.
	// Virtual machines connected to the NAT network also use
	// the VMnet8 virtual switch.
	//
	// The NAT device acts as a DNS server for the virtual
	// machines on the NAT network. Actually, the NAT device
	// is a DNS proxy and merely forwards DNS requests
	// from the virtual machines to a DNS server that is
	// known by the host. Responses come back to the NAT
	// device, which then forwards them to the virtual machines.
	//
	// Source: https://www.vmware.com/support/ws55/doc/ws_net_configurations_nat.html
	NETWORK_NAT NetworkType = "nat"

	// If your host computer is on an Ethernet network,
	// this is often the easiest way to give your virtual
	// machine access to that network. Linux and Windows
	// hosts can use bridged networking to connect to
	// both wired and wireless networks.
	//
	// If you use bridged networking, your virtual machine
	// needs to have its own identity on the network.
	// For example, on a TCP/IP network, the virtual
	// machine needs its own IP address. Your network
	// administrator can tell you whether IP addresses
	// are available for your virtual machine and what
	// networking settings you should use in the guest
	// operating system. Generally, your guest operating
	// system may acquire an IP address and other network
	// details automatically from a DHCP server, or you may
	// need to set the IP address and other details manually
	// in the guest operating system.
	//
	// If you use bridged networking, the virtual machine is
	// a full participant in the network. It has access to
	// other machines on the network and can be contacted
	// by other machines on the network as if it were a
	// physical computer on the network.
	//
	// Source: https://www.vmware.com/support/ws55/doc/ws_net_configurations_bridged.html
	NETWORK_BRIDGED NetworkType = "bridged"

	// The virtual networking components provided by VMware
	// Workstation make it possible for you to create
	// sophisticated virtual networks. The virtual networks
	// can be connected to one or more external networks,
	// or they may run entirely on the host computer.
	NETWORK_CUSTOM NetworkType = "custom"
)

type VNetDevice string

const (
	// AMD PCnet32 network-card, compatible with old OSes
	NETWORK_DEVICE_VLANCE VNetDevice = "vlance"

	// VMXnet network-card, requires VMware Tools
	// NETWORK_DEVICE_VMXNET VNetDevice = "vmxnet"
	// Intel E1000 network-card, most driver compatible
	NETWORK_DEVICE_E1000 VNetDevice = "e1000"

	// VMXNet3 is the fastest network-card, requires VMware Tools
	// see: http://www.vmware.com/pdf/vsp_4_vmxnet3_perf.pdf
	// It also requires the virtual hardware version to be 7 or later
	NETWORK_DEVICE_VMXNET3 VNetDevice = "vmxnet3"
)

type MacAddressType string
<commit_msg>Adds clarification about adding custom network adapters<commit_after>package vix

import (
	"fmt"
	"net"
	"strconv"
	"strings"
)

// VMware Fusion and Workstation
// come with predefined virtual switches,
// tailored for the most common uses cases.
//
// This type defines the common networking
// scenarios available for you to choose from,
// when adding network adapters to your virtual
// machines.
type NetworkType string

const (
	// Host-only networking provides a network
	// connection between the virtual machine
	// and the host computer, using a virtual
	// Ethernet adapter that is visible to the
	// host operating system. This approach can
	// be very useful if you need to set up an
	// isolated virtual network.
	//
	// If you use host-only networking, your
	// virtual machine and the host-only
	// adapter are connected to a private TCP/IP
	// network. Addresses on this network are
	// provided by the VMware DHCP server.
	//
	// Source: https://www.vmware.com/support/ws55/doc/ws_net_configurations_hostonly.html
	NETWORK_HOSTONLY NetworkType = "hostonly"

	// If you want to connect to the Internet
	// or other TCP/IP network using the host
	// computer's dial-up networking or broadband
	// connection and you are not able to give your
	// virtual machine an IP address on the external
	// network, NAT is often the easiest way to give
	// your virtual machine access to that network.
	//
	// If you use NAT, your virtual machine does not
	// have its own IP address on the external network.
	// Instead, a separate private network is set up
	// on the host computer. Your virtual machine gets
	// an address on that network from the VMware virtual
	// DHCP server. The VMware NAT device passes network
	// data between one or more virtual machines and
	// the external network. It identifies incoming
	// data packets intended for each virtual machine
	// and sends them to the correct destination.
	//
	// If you select NAT, the virtual machine can use
	// many standard TCP/IP protocols to connect to
	// other machines on the external network.
	// For example, you can use HTTP to browse Web
	// sites, FTP to transfer files and Telnet to
	// log on to other computers. In the default
	// configuration, computers on the external network
	// cannot initiate connections to the virtual machine.
	// That means, for example, that the default
	// configuration does not let you use the virtual
	// machine as a Web server to send Web pages to
	// computers on the external network.
	//
	// The NAT device is connected to the VMnet8 virtual switch.
	// Virtual machines connected to the NAT network also use
	// the VMnet8 virtual switch.
	//
	// The NAT device acts as a DNS server for the virtual
	// machines on the NAT network. Actually, the NAT device
	// is a DNS proxy and merely forwards DNS requests
	// from the virtual machines to a DNS server that is
	// known by the host. Responses come back to the NAT
	// device, which then forwards them to the virtual machines.
	//
	// Source: https://www.vmware.com/support/ws55/doc/ws_net_configurations_nat.html
	NETWORK_NAT NetworkType = "nat"

	// If your host computer is on an Ethernet network,
	// this is often the easiest way to give your virtual
	// machine access to that network. Linux and Windows
	// hosts can use bridged networking to connect to
	// both wired and wireless networks.
	//
	// If you use bridged networking, your virtual machine
	// needs to have its own identity on the network.
	// For example, on a TCP/IP network, the virtual
	// machine needs its own IP address. Your network
	// administrator can tell you whether IP addresses
	// are available for your virtual machine and what
	// networking settings you should use in the guest
	// operating system. Generally, your guest operating
	// system may acquire an IP address and other network
	// details automatically from a DHCP server, or you may
	// need to set the IP address and other details manually
	// in the guest operating system.
	//
	// If you use bridged networking, the virtual machine is
	// a full participant in the network. It has access to
	// other machines on the network and can be contacted
	// by other machines on the network as if it were a
	// physical computer on the network.
	//
	// Source: https://www.vmware.com/support/ws55/doc/ws_net_configurations_bridged.html
	NETWORK_BRIDGED NetworkType = "bridged"

	// The virtual networking components provided by VMware
	// Workstation make it possible for you to create
	// sophisticated virtual networks. The virtual networks
	// can be connected to one or more external networks,
	// or they may run entirely on the host computer.
	//
	// If you choose for adding a custom network adapter
	// you also have to provide the virtual switch to
	// which it is going to be attached to.
	NETWORK_CUSTOM NetworkType = "custom"
)

type VNetDevice string

const (
	// AMD PCnet32 network-card, compatible with old OSes
	NETWORK_DEVICE_VLANCE VNetDevice = "vlance"

	// VMXnet network-card, requires VMware Tools
	// NETWORK_DEVICE_VMXNET VNetDevice = "vmxnet"
	// Intel E1000 network-card, most driver compatible
	NETWORK_DEVICE_E1000 VNetDevice = "e1000"

	// VMXNet3 is the fastest network-card, requires VMware Tools
	// see: http://www.vmware.com/pdf/vsp_4_vmxnet3_perf.pdf
	// It also requires the virtual hardware version to be 7 or later
	NETWORK_DEVICE_VMXNET3 VNetDevice = "vmxnet3"
)

type MacAddressType string

{'fraction_non_alphanumeric': 0.06880134428678118, 'fraction_numerical': 0.005227781926811053, 'mean_word_length': 3.2210401891252953, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 6, 'lorem ipsum': 0, 'www.': 8, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5575890', 'n_tokens_mistral': 2960, 'n_tokens_neox': 2853, 'n_words': 1472}