"** The Linux Masquerade Application list has a lot of good information regarding applications that work through Linux IP masquerading. This site was recently taken over by Steve Grevemeyer, who implemented it with a full database backend. It's a great resource! "
Generally, any application that uses standard TCP and UDP should work. If you have any suggestion, hints, etc., please see the IP Masquerade Resource for more details.
General Clients:
all supported platforms, file searching client (not all archie clients are supported)
all supported platforms, with the ip_masq_ftp.o kernel module for active FTP connections.
all supported platforms
all supported platforms, WWW surfing
all IRC clients on various supported platforms, DCC is supported via the ip_masq_irc.o module
all supported platforms, USENET news client
all platforms, with ICMP Masquerading kernel option
all supported platforms, email clients
all supported platforms, Secure TELNET/FTP clients
all supported platforms, email servers like Sendmail, Qmail, PostFix, etc.
all supported platforms, remote session
UNIX and Windows based platforms, some variations may not work
Windows(possibly all supported platforms), virtual reality surfing
all supported platforms
Multimedia and Communication Clients:
- MS Netmeeting, Intel Internet Phone Beta , and other H.323 applications - There are now two solutions to accomplish this through IPMASQed connections:
There is a stable BETA 2.2.x kernel module available on the MASQ WWW site or at http://www.coritel.it/projects/nat/implementation.htm to work with Microsoft Netmeeting v3.x code on 2.2.x kernels. There is also another module version on the MASQ WWW site specifically for Netmeeting 2.x with 2.0.x kernels, but this does not support Netmeeting v3.x.
Another commercial solution is the Equivalence's PhonePatch H.323 gateway.
Windows, Client-Server 3D chat program
all supported platforms, with the ip_masq_cuseeme module loaded, please see Section 6.8 for more details.
all supported clients. Requires the Linux kernel to be either compiled with PORTFW support, have the ip_masq_icq module (2.2.x and 2.0.x only), or have a SOCKS proxy running. A full description of this configuration is in Section 6.9.
Windows, Peer-to-peer audio communications, users can reach you only if you initiate the call, but those users cannot call you without a specific port forwarding setup. See Section 6.7for more details.
Windows, network streaming audio
Windows, Peer-to-peer Text audio whiteboard communications, users can reach you only if you initiate the call, but those users cannot call you without a specific port forwarding setup. See Section 6.7for more details.
Windows, network streaming audio, higher quality available with the ip_masq_raudio UDP module
Windows, network streaming audio
Windows, with the ip_masq_vdolive patch
Windows, Client-Server 3D chat program
Games - See Section 6.10for more details on the LooseUDP patch
Works but requires TCP ports 116, 118 and UDP port 6112 IPPORTFWed to the client game machine. See Section 6.7for more details. Please note that FSGS and Bnetd servers still require IPPORTFW because they have not been re-written to be NAT-friendly.
Works with LooseUDP patch and new NAT-friendly -- email David Ranch for the .DLLs from Activision
Works with LooseUDP patch or requires TCP ports 116 and 118 and UDP port 6112 IPPORTFWed to the game machine. See Section 6.7for more details.
Works with LooseUDP patch or requires TCP ports 116 and 118 and UDP port 6112 IPPORTFWed to the game machine. Newer versions of Diablo use only TCP port 6112 and UDP port 6112. See Section 6.7for more details.
Works with LooseUDP patch or requires TCP ports 116 and 118 and UDP port 6112 IPPORTFWed to the game machine. See Section 6.7for more details.
Works right out of the box but requires the ip_masq_quake module if there are more than one Quake I/II/III player behind a MASQ box. Also, this module only supports Quake I and QuakeWorld by default. If you need to support Quake II or non-default server ports, please see the module install section of Section 3.4.3 and Section 3.4.2 rulesets.
Works with the LooseUDP patch, IPPORTFWing TCP, and UDP ports 6112 to the internal MASQed game machine. See Section 6.7for more details.
Works with LooseUDP patch
Other Clients:
Linux, network administration-account package
DOS, a suite containing telnet, ftp, ping, etc.
MS-Windows remotely controls a PC over TCP/IP, but only works if it is a client, but not a host without a specific port forwarding setup. See Section 6.7for more details.
uses NTP - network time protocol
Cannot connect to server
Cannot connect to opposite side
Cannot work at present (it makes invalid assumptions about addresses).