Differences

This shows you the differences between two versions of the page.

web_gui:advanced_network_configuration [2010/11/09 15:52]
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 26: Line 28:
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]]
-The mode ** Bridge: WAN and host on ET4 share the same IP address ** could be used in cases where the router should act upon some traffic (e.g. SIP in a [[network:operational_modes|"WAN SIParator 1"]]) but the rest should be bridged right through. +{{: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 mode ** Bridge: WAN and host on ET4 share the same IP address ** could be used in cases where the router should act upon some traffic (e.g. SIP in a [[network:operational_modes#WAN SIParator 1|"WAN SIParator 1"]]) but the rest should be bridged right through.
And where the router is not allowed to have a public IP address of its own. And where the router is not allowed to have a public IP address of its own.
The IP address is owned by the host on ET4 (the router not answering to ARP requests). The IP address is owned by the host on ET4 (the router not answering to ARP requests).
Line 56: 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 =====
web_gui/advanced_network_configuration.1289314366.txt.gz · Last modified: 2010/11/09 15:52 by mats
CC Attribution-Noncommercial-Share Alike 3.0 Unported
www.chimeric.de Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0