Quick links:
Product Overview
Installation
Settings and Administration
ADSL
SIP Support
Telephone ports
Network
Firewall
Wireless
VPN
Misc
Licenses
Troubleshooting
This shows you the differences between two versions of the page.
web_gui:advanced_network_configuration [2010/11/12 16:40] mats |
web_gui:advanced_network_configuration [2010/12/14 16:43] (current) mats |
||
---|---|---|---|
Line 7: | Line 7: | ||
==== Add routes ==== | ==== Add routes ==== | ||
+ | {{ :web_gui:advanced_network_configuration.png?300|Advanced Network Configuration in rel 5.30}} | ||
+ | |||
Static additions to the unit's [[wp>Routing_table|routing table]]. | Static additions to the unit's [[wp>Routing_table|routing table]]. | ||
Use this, for example, to make a routed subnet reachable through the unit. For an 'interface route', enter '0.0.0.0' in the "Gateway" field (or leave empty) and select the interface (under "Type"). The default gateway ("Destination" = 0.0.0.0) should not be entered here, but on the [[Network page|main network page]]. | Use this, for example, to make a routed subnet reachable through the unit. For an 'interface route', enter '0.0.0.0' in the "Gateway" field (or leave empty) and select the interface (under "Type"). The default gateway ("Destination" = 0.0.0.0) should not be entered here, but on the [[Network page|main network page]]. | ||
Line 25: | Line 27: | ||
Thus, both the WAN interface and the ET4 hosts can get public IP addresses by DHCP. | Thus, both the WAN interface and the ET4 hosts can get public IP addresses by DHCP. | ||
By setting the WAN interface on a manual faked IP address the router can be made not to interfer - the router will become an ordinary bridged (not firewalled) modem and the ET1-ET3 are not really used. [[wp>IEEE_802.1D|802.1D bridge]] | By setting the WAN interface on a manual faked IP address the router can be made not to interfer - the router will become an ordinary bridged (not firewalled) modem and the ET1-ET3 are not really used. [[wp>IEEE_802.1D|802.1D bridge]] | ||
+ | |||
+ | {{:web_gui:bridge_8021.jpg|}} | ||
The operating mode [[network:operational_modes#WAN SIParator 2|"WAN SIParator 2"]] makes use of this kind of bridge. | The operating mode [[network:operational_modes#WAN SIParator 2|"WAN SIParator 2"]] makes use of this kind of bridge. | ||
Line 58: | Line 62: | ||
** "Poisoned reverse" flag in RFC1058 ** See the "Split horizon" section (2.2.1) in [[http://tools.ietf.org/html/rfc1058|RFC1058]]. | ** "Poisoned reverse" flag in RFC1058 ** See the "Split horizon" section (2.2.1) in [[http://tools.ietf.org/html/rfc1058|RFC1058]]. | ||
+ | |||
+ | ==== NAT ports usage ==== | ||
+ | |||
+ | To perform NAT (Network Address Translation), source port numbers on outgoing packets are modified. | ||
+ | These numbers are selected from a pool of non-well-known port numbers. | ||
+ | This port number range can be configured by the fields **Port start number** and **Pool size**. | ||
+ | The default values should not be changed other than possibly in the [[network:operational_modes#WAN SIParator 1|"WAN SIParator 1"]] (single address [[advanced_network_configuration#Bridge (802.1D) WAN to ET4|802.1D bridge]]) mode, where there is a risk of conflicts with another router/firewall also doing NAT. [[wp>Network_address_translation|NAT]] [[wp>Port_address_translation|PAT]] | ||
+ | |||
===== Extra WAN Interfaces ===== | ===== Extra WAN Interfaces ===== |