Coyote Point Systems Equalizer Spezifikationen Seite 81

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 594
  • Inhaltsverzeichnis
  • FEHLERBEHEBUNG
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 80
In this example, neither the 192.168.211.0/24 nor the 192.168.105.0/24 networks can access the Internet directly.
The administrator configures Equalizer to provide outbound NAT service for these networks by using an IP
address on the 10.0.0.0/24 network when these internal networks need to talk to the Internet.
When configuring outbound NAT, the internal local network that is being configured for outbound NAT must use
the routing information for the external network which it is using NAT through. In the example above, the default
gateway for the 192.168.211.0/24 network will really be on the 10.0.0.0/24 network.
This is logical when you remember it this way: If Equalizer is sending a packet from the 192.168.211.0/24 network
to a host on the Internet, it has to be sent through the gateway of the external network, rather than the internal
network.
When Outbound NAT is enabled for a local network that contains attached destination networks, the destination
networks automatically inherit the same outbound NAT configuration.
Note - Outbound NAT is not supported for IPv6.
Network Permissions: Local networks configured in Equalizer use a
default deny
permission scheme. This means
that if an Administrator wants to route between two networks using Equalizer, they must explicitly enable
permissions between that pair of networks.
Note that permissions are not symmetrical: it is possible to configure a solution where one network can talk to
another but not vice-versa. For most configurations, permissions are necessary on both networks: if network 'A'
needs to route to network 'B', a permission must be added to 'A' for 'B' and another permission must be added to
'B' for 'A'.
Permissions are only necessary when using Equalizer to route packets. They are not required for Application
Traffic Management. That is, when an Equalizer cluster is paired with a server (by adding a server pool containing
that server to the cluster), Equalizer knows that any packets associated with a connection for that cluster should
be allowed on the server network.
Copyright © 2013 Coyote Point Systems. A subsidiary of Fortinet, Inc.
All Rights Reserved.
81
Equalizer Administration Guide
Seitenansicht 80
1 2 ... 76 77 78 79 80 81 82 83 84 85 86 ... 593 594

Kommentare zu diesen Handbüchern

Keine Kommentare