Pppoe, Defining a vlan, Section 3.4.5, “pppoe – Amer Networks E5Web GUI User Manual
Page 171
It is important to understand that the administrator should treat a VLAN interface just like a
physical interface in that they require both appropriate IP rules and routes to exist in the cOS
Core configuration for traffic to flow through them. For example, if no IP rule with a particular
VLAN interface as the source interface is defined allowing traffic to flow then packets arriving on
that interface will be dropped.
VLAN advanced settings
There is a single advanced setting for VLAN:
Unknown VLAN Tags
What to do with VLAN packets tagged with an unknown ID.
Default: DropLog
Example 3.16. Defining a VLAN
This simple example defines a virtual LAN called VLAN10 with a VLAN ID of 10. The IP address of
the VLAN is assumed to be already defined in the address book as the object vlan10_ip.
Command-Line Interface
Device:/> add Interface VLAN VLAN10
Ethernet=lan
IP=vlan10_ip
Network=all-nets
VLANID=10
InControl
Follow the same steps used for the Web Interface below.
Web Interface
1.
Go to: Network > Interfaces and VPN > VLAN > Add > VLAN
2.
Now enter:
•
Name: Enter a name, for example VLAN10
•
Interface: lan
•
VLAN ID: 10
•
IP Address: vlan10_ip
•
Network: all-nets
3.
Click OK
3.4.5. PPPoE
Chapter 3: Fundamentals
171