Quick links:
Product Overview
Installation
Settings and Administration
ADSL
SIP Support
Telephone ports
Network
Firewall
Wireless
VPN
Misc
Licenses
Troubleshooting
Differences
This shows you the differences between two versions of the page.
|
web_gui:extra_wan_interfaces [2010/11/09 13:41] mats |
web_gui:extra_wan_interfaces [2010/11/19 10:46] (current) tibor |
||
|---|---|---|---|
| Line 7: | Line 7: | ||
| A common configuration of this is the "TriplePlay", where voice and video are sent by "ipwan2", "ipwan3" etc. and other Internet traffic uses the standard WAN interface ("LINE" or "ET0"). | A common configuration of this is the "TriplePlay", where voice and video are sent by "ipwan2", "ipwan3" etc. and other Internet traffic uses the standard WAN interface ("LINE" or "ET0"). | ||
| - | Read more: [[network:extrawan|Extra WAN interfaces / Virtual circuits]] | + | Read more: [[network:extrawan|Extra WAN interfaces / Virtual circuits description]] |
| + | {{ :web_gui:extra_wan_interfaces.png?308|Extra WAN Interfaces in rel 5.30}} | ||
| ===== Common interface parameters ===== | ===== Common interface parameters ===== | ||
| Line 20: | Line 21: | ||
| **Gateway** The address of the next router up in the network. For the Internet interface, this is the unit's [[wp>Default_gateway|Default gateway]]. | **Gateway** The address of the next router up in the network. For the Internet interface, this is the unit's [[wp>Default_gateway|Default gateway]]. | ||
| For the other interfaces, this is the "next hop" i.e. the address of the router that takes care of the packet sent upstreams on this particular channel (subnet). | For the other interfaces, this is the "next hop" i.e. the address of the router that takes care of the packet sent upstreams on this particular channel (subnet). | ||
| - | Leave empty when using DHCP or PPPoE/PPPoA. | + | :!: Leave empty when using DHCP or PPPoE/PPPoA. |
| **Access type** The protocol and/or method of acquiring the IP address. | **Access type** The protocol and/or method of acquiring the IP address. | ||
| Line 27: | Line 28: | ||
| **User (PPP), Password (PPP)** Username and password if a Point-to-Point protocol (PPPoE, PPPoA) is used. [[wp>Point-to-Point_Protocol|PPP]] [[wp>PPPoE]] [[wp>PPPoA]] | **User (PPP), Password (PPP)** Username and password if a Point-to-Point protocol (PPPoE, PPPoA) is used. [[wp>Point-to-Point_Protocol|PPP]] [[wp>PPPoE]] [[wp>PPPoA]] | ||
| - | **IGMP Proxy** Check this if the interface is the upstream interface for the IGMP Proxy. | + | **IGMP Proxy** Check this if the interface is the upstream interface for the [[network:extrawan#IGMP proxy]]. |
| This is typically used for multicast traffic, such as video. NB! Only one such interface may be selected. | This is typically used for multicast traffic, such as video. NB! Only one such interface may be selected. | ||
| - | If none are selected, the normal WAN interface is the upstream IGMP interface. | + | :!: If none are selected, the normal WAN interface is the upstream IGMP interface. |
| If multicast is to be used, it must be enabled on the security settings too. | If multicast is to be used, it must be enabled on the security settings too. | ||
| Line 36: | Line 37: | ||
| Notably, the SIP traffic is specially marked by values 4, 7, 261 or 262. | Notably, the SIP traffic is specially marked by values 4, 7, 261 or 262. | ||
| The value 4 corresponds to the "Use WAN Interface with special SIP QoS" checkbox on the SIP page. | The value 4 corresponds to the "Use WAN Interface with special SIP QoS" checkbox on the SIP page. | ||
| - | The numbers used here are internal class identifications and does not necessarily imply any priority value. | + | :!: The numbers used here are internal class identifications and does not necessarily imply any priority value. |
| The "line" interface should have no QoS routing - it is the default internet interface. | The "line" interface should have no QoS routing - it is the default internet interface. | ||
| Line 77: | Line 78: | ||
| A //VLAN Id// is a value between 0 and 4094 defining the identification of the particular channel (network). | A //VLAN Id// is a value between 0 and 4094 defining the identification of the particular channel (network). | ||
| - | All or none of the //VLAN Id// fields must be filled in. | + | :!: All or none of the //VLAN Id// fields must be filled in. |
| If VLAN tags are used and a single interface should receive non-tagged traffic, its //VLAN Id// field should be set to the (fictitious) value 4096. | If VLAN tags are used and a single interface should receive non-tagged traffic, its //VLAN Id// field should be set to the (fictitious) value 4096. | ||
| It is also possible to have extra WAN interfaces on the Ethernet WAN port using only non-VLAN-tagged traffic. | It is also possible to have extra WAN interfaces on the Ethernet WAN port using only non-VLAN-tagged traffic. | ||
| In this case, the "channels" are separated by IP subnets only (IP address plus subnet mask). | In this case, the "channels" are separated by IP subnets only (IP address plus subnet mask). | ||
| - | However, broadcast packets will be reveived on all IP interfaces, with implications to for example DHCP services. | + | However, broadcast packets will be reveived on all IP interfaces, with implications to for example DHCP services (see also [[network:extrawan#Non-VLAN tag case|description page]]). |
| In practise, it is as if multiple IP interfaces would be connected to WAN through the same Ethernet switch (hub). | In practise, it is as if multiple IP interfaces would be connected to WAN through the same Ethernet switch (hub). | ||
| In this case, the //VLAN Id// fields should be left empty. | In this case, the //VLAN Id// fields should be left empty. | ||
| Line 94: | Line 95: | ||
| The bridge is like connecting through a hardware switch/hub. [[wp>IEEE_802.1D|IEEE 802.1D bridge standard]] | The bridge is like connecting through a hardware switch/hub. [[wp>IEEE_802.1D|IEEE 802.1D bridge standard]] | ||
| - | The ordinary WAN "Internet" interface cannot be bridged here, this is done on the [[Advanced Network Configuration#Bridge (802.1D) WAN to ET4|Advanced Network page]] instead, however only possible bridging to the ET4 port. | + | :!: The ordinary WAN "Internet" interface cannot be bridged here, this is done on the [[Advanced Network Configuration#Bridge (802.1D) WAN to ET4|Advanced Network page]] instead, however only possible bridging to the ET4 port. |
| ===== Extra QoS classifiers ===== | ===== Extra QoS classifiers ===== | ||
| - | As packets come in on a LAN port they may be marked with QoS tags, this is done by the "classifiers". The QoS tag value, if set, will force the router to send the packet out by a particular WAN interface - if one is configured for that "QoS routing" value. By setting up the search profiles in the table here, one may direct packets with certain source/destination IP addresses/ports, DiffServ bits etc. to the correct WAN interface. Select the WAN interface implicitly by using the "QoS routing" dropdown box. Additionaly, one can use the "Set DiffServ bits" field (7 bits, e.g. "1000000") to set DiffServ bits in those packets that match the profile. | + | As packets come in on a LAN port they may be marked with QoS tags, this is done by the "classifiers". |
| + | The QoS tag value, if set, will force the router to send the packet out by a particular WAN interface - if one is configured for that "QoS routing" value. | ||
| + | By setting up the search profiles in the table here, one may direct packets with certain source/destination IP addresses/ports, DiffServ bits etc. to the correct WAN interface. | ||
| + | Select the WAN interface implicitly by using the "QoS routing" dropdown box. Additionaly, one can use the "Set DiffServ bits" field (7 bits, e.g. "1000000") to set DiffServ bits in those packets that match the profile. | ||
| Thus, the settings here only apply to upstream traffic. | Thus, the settings here only apply to upstream traffic. | ||
| - | **Order** The order may be important when the "classifier" evaluates a packet. A low order number profile (=row) will be tried before a higher order: if a match the higher order will not be evaluated for a that packet. This implies that a more specific profile should be placed before the more general. | + | **Order** The order may be important when the "classifier" evaluates a packet. |
| + | A low order number profile (=row) will be tried before a higher order: if a match the higher order will not be evaluated for a that packet. | ||
| + | This implies that a more specific profile should be placed before the more general. | ||
| - | **QoS routing** This directs on which output interface the packets will go, that is, those packets conforming to the IP address(es), port(s) etc. The numbers used in the dropdown box are internal class identifications and does not necessarily imply any priority value. | + | **QoS routing** This directs on which output interface the packets will go, that is, those packets conforming to the IP address(es), port(s) etc. |
| + | The numbers used in the dropdown box are internal class identifications and does not necessarily imply any priority value. | ||
