The following task will focus on the development of an on-premises, Small Office or Home, Wireless Local Area Network consisting of the fewest required peripheral components necessary, including and limited to any number of home routers flashed with ipfire, zeroshell, untangle-ng, ipcop, opnsense, clearos, vyos, fresh tomato, freewrt, pfsense, gargoyle, advanced tomato, lede, openwrt, tomato, or ddwrt, personal computers with multiple nic, with no fewer than one supporting monitor and promiscuous mode operation running debian based LTS or Windows Professional 10 OS, Switches, RaspberryPI, and/or android mobile devices with or without root running Android 3.4 or current version providing topologically optimal replication of WFPS/WiPS application of Indoor Positioning Systems Geographic Location Proximity network environment for the purposes of artificial trilateration.
Implementation of the infrastructure should be contingent upon the integration of a remotely hosted proxy or vpn providing dual primary functionality (1. reverse connectivity 2. Access Point for local host machine that should appear at our artificial locale). This Socks5/VPN public IP address will interface with one, some combination of, or all of Google Maps Geocoding API, Open Cage Data, Mapbox Geocoding API for location coordinate data for use with WiGLE (wigle.net), Radiocells.org, Combain Positioning Service (combain.com), LocationAPI.org, Mozilla Locations Services (location.services.mozilla.com), Mylnikov GEO (mylnikov.org), Navizon (navizon.com), collectively, in-part, or individually to supplement requisite device identifiers of Access Point for the Proxy/VPN, and surrounding networks within the scope of the average range of a normal, consumer grade NIC.. Primary machhine indentifiers such as MAC address and or SSID or device names will be applied accordingly to the devices, components in our infrastructure, ex: AP of remote proxy MAC will be spoofed on router assigned to emulating that network presence in our topology, MAC of near by devices to the remote AP will be assigned to other devices or VMs and configured with spoofed mac to produce beacon entropy, et al.
Next, determine which combination of the following tools, utilities, approaches, methods, and/or technologies hereinbelow will satisfy the above conditions, or, as an alternative, disclose those which will:
Ad-Hoc/ICS connections, Multi-protocol supported proxification at system and kernel level through application management through service level execution/launch, any data encapsulation iterations on the link layer level including but not limited to interface virtualizations eg Tun and Tap, Optical Transport Network frame encapsulation wrappers with or without the purpose of virtualization or emulation of physical layer level, Stateless Network Address Translations, Multi-NAT environments, various implements of tunnelling and port forward/remote port forwarding, CLNS, EIGRP, GTP GPRS Tunnels, HTTP tunnels, ICMP tunnels, NVGRE, Pseudowire, Stunnel, Tunnel Broker, VxLAN, Wireguard, GENEVE, IpinIp, Sit IPv6, Mqtt/dns/sms tunnels, vpnhood, barbatunnel, portfusion, softether.
Implementation of the infrastructure should be contingent upon the integration of a remotely hosted proxy or vpn providing dual primary functionality (1. reverse connectivity 2. Access Point for local host machine that should appear at our artificial locale). This Socks5/VPN public IP address will interface with one, some combination of, or all of Google Maps Geocoding API, Open Cage Data, Mapbox Geocoding API for location coordinate data for use with WiGLE (wigle.net), Radiocells.org, Combain Positioning Service (combain.com), LocationAPI.org, Mozilla Locations Services (location.services.mozilla.com), Mylnikov GEO (mylnikov.org), Navizon (navizon.com), collectively, in-part, or individually to supplement requisite device identifiers of Access Point for the Proxy/VPN, and surrounding networks within the scope of the average range of a normal, consumer grade NIC.. Primary machhine indentifiers such as MAC address and or SSID or device names will be applied accordingly to the devices, components in our infrastructure, ex: AP of remote proxy MAC will be spoofed on router assigned to emulating that network presence in our topology, MAC of near by devices to the remote AP will be assigned to other devices or VMs and configured with spoofed mac to produce beacon entropy, et al.
Next, determine which combination of the following tools, utilities, approaches, methods, and/or technologies hereinbelow will satisfy the above conditions, or, as an alternative, disclose those which will:
Ad-Hoc/ICS connections, Multi-protocol supported proxification at system and kernel level through application management through service level execution/launch, any data encapsulation iterations on the link layer level including but not limited to interface virtualizations eg Tun and Tap, Optical Transport Network frame encapsulation wrappers with or without the purpose of virtualization or emulation of physical layer level, Stateless Network Address Translations, Multi-NAT environments, various implements of tunnelling and port forward/remote port forwarding, CLNS, EIGRP, GTP GPRS Tunnels, HTTP tunnels, ICMP tunnels, NVGRE, Pseudowire, Stunnel, Tunnel Broker, VxLAN, Wireguard, GENEVE, IpinIp, Sit IPv6, Mqtt/dns/sms tunnels, vpnhood, barbatunnel, portfusion, softether.