Configuration Notes |
Configuration Files
nat32.ini | The list of selected interfaces and connectivity type indicators. |
ifn1.ini, ifn2.ini | Interface settings for each configured interface. |
console.ini | The initial Console window size (cols:rows), show state H=hide, N=normal, F=full-screen
Browser embedding (E). |
screen.ini | The Console screen buffer size (cols:rows). |
nat32.js | A custom Javascript file generated each time NAT32 starts. |
mynat32.htm | A shortcut to mynat32.htm that will always connect the default web browser to the correct NAT32 Server Port. |
Script Files | |
startup.txt | executed when NAT32 starts, specifies default settings |
user.txt | executed after startup.txt has completed (user-defined) |
exit.txt | executed when NAT32 terminates |
dialup.txt | executed before dialing takes place (user-defined) |
hangup.txt | executed before a hangup takes place (user-defined) |
connect.txt | executed after a connection has been dialed |
disconnect.txt | executed after a connection is terminated |
change.txt | executed after an IP address change has occurred |
url.txt | Urls that are loaded into the Address Bar when a Web window is activated |
dhcpd.ini | The DHCP Server initialization file (user-defined) |
dhcp.tcl | A Tcl script that is executed whenever the DHCP Server performs an action |
Notes
Script files can contain any NAT32 command, including names of files containing NAT32 commands, Tcl scripts and even Windows commands.
File readme.htm contains a list of changes in each build. If a new WinPkFilter driver is available, the build information will indicate this, and you must install the new version before you run that build.
File url.txt contains URLs that are displayed in a Web window's combobox prior to the Typed URLs fetched from the Registry.
You may need to modify file startup.txt, but note that custom settings should be placed in file user.txt, which is executed after startup.txt has completed. File user.txt is not overwritten when you reinstall NAT32.