Free scanning tunneling microscope software for windows

GIT is a utility to link two or more LANs together for network gameplay by tunneling packets over the internet via UDP, TCP, or even through a socks proxy.
It is very configurable, allowing only certain frame types, IPX packet types,
IPv4 protocols, IPX socket destinations, or TCP/UDP ports to be forwarded.
Unlike many other tunnel programs that send all packets over the internet, GIT is very friendly to low-bandwidth users, by not forwarding NetBIOS or other unneeded sockets by default.
It can also be used to bridge many configurations of IPX or IPv4 packets and frames from once point to another. Formerlly known as the Gamers IPX tunnel, GIT now tunnels TCP and UDP ports as well, in order to work with modern games.
New in GIT v0.99 is the configuration wizard, which allows you to answer a few questions to easily set up GIT for a particular program.
.git files can be run and will start GIT or talk to an existing GIT to display
the wizard pages needed for that script.
Please note that the Auto Configure button for the scripts will re-use all of
the saved settings from the last time you ran that script, so if your IP address
or any remote IP addresses have changed, you will need to run through the wizard again instead of using the Auto Configure button.
See the file "Wizard Scripts.txt" for information on creating your own scripts.
There is also a Save Profile option that will save all your current settings to
a wizard script that you can easily restore using the wizard later.
The host list can be stored as-in or the profile can create a textbox that will prompt to edit the host list when you run the profile script.
GIT puts your ethernet adaptor into promiscuous mode in order to sniff all
ethernet packets and analyze which ones are part of your network game traffic.
GIT then sends these packets to another instance of GIT running on the
opposite LAN, which will receive the packet and broadcast it onto that LAN
as if the two were physically connected.
Only one computer in each LAN needs to be running GIT for the entire LANs to be linked together.

System requirements:
- WinPcap 4.1 Beta 4

Enhancements:
- Dont Send Unicast - This replaces the old option named "Only if broadcast" but is only enforced on the sending side of the tunnel. Previously the option could reject packets on the receiving end of the GIT tunnel as well, but this is no longer the case.
- Dont Send Broadcast - This option compliments the previous option, and when combined with the previous option replaces the old option named "Receive only". This option is useful on a switched network with 2 or more copies of GIT running where GIT is forwarding unicast packets. Check this option on all but 1 copy of GIT in order to prevent duplicate forwarding of broadcast packets from the same network.
- Dont Send Routable - This option prevents any packets that should be routable over the internet from being tunneled. The only non-routable addresses that will still be tunneled are 192.168.x.x, 172.16-31.x.x, 10.x.x.x, and 169.254.x.x
- Also Match Source Port - This option allows the TCP/UDP port lists to forward packets if the source port matches a port in the list. Previously only the destination ports were matched, as is still the case for IPX sockets. This option should be checked on both sides of the tunnel if used.
- Forward ARP - This allows GIT to tunnel ARP requests and replies, in case some program requires it.
- Use Old Reforward Prevention Method for IPX/IPv4 Frames - Checking this option will resort to the method used up to GIT v0.97, which is to alter packets with a flag in order to not reforward them. Not checking this option will keep track of the source MAC addresses of all packets received from the tunnel and sent to the local network. Each MAC address is remembered for 30 seconds in order to prevent re-forwarding the same packet back that GIT had just created. Up to 256 MAC addresses can be remembered at once, otherwise packets may start getting duplicated once the table fills up. This should be unlikely though since it requires more than 256 unique computers to all have their packets tunneled at once in less then 30 seconds. ARP packets always use the MAC address method regardless of this setting.