Differences

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

web_gui:extra_wan_interfaces [2010/11/09 13:58]
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 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.
Line 82: Line 83:
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 (see [[network:extrawan|Extra WAN interfaces]]). +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.
web_gui/extra_wan_interfaces.1289307490.txt.gz · Last modified: 2010/11/09 13:58 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