Bindings tab
The Bindings tab is central to the security of the WinGate firewall. Binding a
service to an interface means that that service is only accessible if the
connection comes in on that interface. With WinGate, bindings can be configured to
allow access on one, several or all of the available interfaces. The Bindings
tab lists all the available interfaces. LAN cards, Dialer profiles and the
localhost address will be included. You can select the interfaces that are allowed
access to the service.
For example
On most LANs, you want your WWW proxy to only be accessible to the people on
you network. Simply select the
In the picture above, we have bindings to the LAN card and 203.96.8.238, which
is on the Internet. We specified this card so we can let people look at our
web pages. We would enable this by selecting the
Note that with out a binding to 127.0.0.1, the local machine can not use that
service.
Lite users:
Lite users will find that their remote control service can only bind to
127.0.0.7. This is a license restriction. Upgrading to Pro will allow the service to
be accessed from machines other than the localhost. This demonstrates the
working of bindings. Only machines connecting to 127.0.0.1 can connect, and because
that has to be the machine that WinGate is on, then you can only connect to
WinGate on the local machine.
Typical Binding suggestions:
Allow binding to only your LAN addresses for the telnet proxy.
Allow all bindings for a mapping to a SMTP server.
If you run a WWW server through WinGate, allow all interfaces.
In general you do not need bindings to your dialer profiles.
Security tips:
For the best security, only bind each service to your LAN card and localhost.
If you have multiple segments, bind to each segment. Don
Back to services
