SETUP
Chapter 5 – Setup
Network Interfaces
For configuration management of network interfaces, go to Setup > Network Interfaces > Network Interfaces
Configuration . This section displays the list of network interfaces. Click on the pencil icon to the right of a particular interface in order to edit its configuration. Refer to possible configurations in the table below.
Bridge
This section allows you to create a bridge between network interfaces. All LAN network interfaces are added into the bridge (br0) by default.
Just LAN interfaces are allowed under bridge including Ethernet (eth0, eth1, eth2) and wlan1 (Wi-Fi Access Point).
With this bridge interface added, it is possible to assign any number of LAN interfaces (of both Ethernet and Wi-Fi
AP types) to a specified bridge. Only one bridge interface is supported.
IPv6 support is also available under the bridge using Static IP mode.
Slave Interfaces
Slave interfaces such as Ethernet (eth0, eth1, eth2) or Wi-Fi AP ( wlan1 ) do not have their own IP addresses and are not configured as DHCP clients by default. Static IP address mode is implemented on the bridge level.
Ethernet Interface
The Ethernet interface can be configured as either LAN or WAN . Ethernet interface as LAN can be set to use static pre-set IPv4 or IPv6 addresses or dynamically obtain an IPv4/IPv6 address over DHCP in DHCP client mode. When configured as WAN , only IPv4 is available.
PPP interface
The PPP interface is only allowed to be WAN . The PPP interface listed in the Network Interfaces page can only have its mode changed. Options are PPP and PPP addresses-only modes. IPv6 WAN support is also an option with the PPP interface (configurable fields vary with network carrier).
Wi-Fi integration
Wi-Fi integration is enabled by adding two network interfaces: wlan0 (used exclusively for Wi-Fi as WAN
(STATION) mode) and wlan1 (used exclusively for AP mode). The Web UI as well as API back-end has been modified to add support and validation rules in order to assign LAN interface(s) to a bridge, and removing them from under the bridge.
NOTE: Wi-Fi availability depends on model. Consult the appropriate manual for details.
40
Network configurations
Refer to the following table for the possible network configurations:
Interface Direction Type IP Mode
Br0 N/A
Eth0, Eth1, Eth2 LAN
BRIDGE
Ethernet
STATIC
STATIC
Bridge Mode
Br0
N/A
IPv4/IPv6
Support
Both
Both mPower TM Edge Intelligence Conduit AEP Software Guide
SETUP
Eth0, Eth1, Eth2 LAN
Eth0, Eth1, Eth2 LAN
Eth0, Eth1, Eth2 WAN
Eth0, Eth1, Eth2 WAN
Eth0, Eth1, Eth2 WAN
Wlan0
Wlan0
Wlan1
Wlan1 ppp0 ppp0
WAN
WAN
LAN
LAN
WAN
WAN
Ethernet
Ethernet
Ethernet
Ethernet
Ethernet
Wi-Fi as WAN
Wi-Fi as WAN
Wi-Fi AP
Wi-Fi AP
Cellular
Cellular
DHCP Client
N/A
STATIC
DHCP Client
DHCP Client -
Addresses Only
N/A
Br0
N/A
N/A
N/A
DHCP Client
DHCP Client -
Addresses Only
STATIC
N/A
PPP
PPP - Addresses
Only
N/A
N/A
N/A
Br0
N/A
N/A
Both
N/A
IPv4 only
IPv4 only
IPv4 only
IPv4 only
IPv4 only
IPv4 only
IPv4 only
Both
Both
IPv6 Example Configurations
Configuration Example #1: Cellular WAN, Delegated LAN
This example is the most typical configuration. The admin user enables IPv6 on the Cellular Configuration, configures the bridge interface on the device in Delegated Prefix mode and, configures all LAN interfaces that will perform IPv6 as slaves of the bridge interface. The LAN networks “under” the bridge will all have the whole 64 bit prefix delegated to them. The bridge and Cellular WAN interfaces will have the same IPv6 address. In this manner, the router will act as the gateway to the Internet for all the LAN devices that have delegated addresses.
WAN interface is configured in Automatic Client IPv6 Mode.
All LAN interfaces are connected to the bridge interface.
The bridge interface is configured in the Delegated Prefix mode.
The whole /64 prefix is delegated to the LAN network.
The Bridge interface and Cellular WAN interface have the same IPv6 address.
mPower TM Edge Intelligence Conduit AEP Software Guide 41
SETUP
Configuration Example #2: No IPv6 WAN, Static LAN
This example is essentially the same as the old mode where IPv6 was not supported. The devices have Internet access via IPv4, but not via IPv6. On the LAN side, the admin user assigns a static IPv6 address to the br0 (bridge) interface and all the IPv6 addresses on the LAN side will be assigned by the user. In this case, the device may be managed through the LAN interface over IPv6.
IPv6 support disabled on WAN interface or IPv6 is not supported on cellular provider.
Devices in LAN1 will see each other.
Devices in LAN1 will not have Internet access over IPv6.
42
Configuration Example #3: Cellular WAN, Static LAN with valid addresses
This example is typically the second most widely used IPv6 scenario since not all ISPs support prefix delegation automatically. In this case, the cellular provider or ISP provides the admin user with global address of the device is and the IPv6 prefix that needs to be assigned to the LAN devices. The LAN devices are all programmed with a valid
IPv6 address statically by the admin user with the knowledge of what IPv6 prefix to use provided by the Cellular
Provider / ISP. All the LAN devices can access the Internet via IPv6 if they have a global IPv6 address configured.
mPower TM Edge Intelligence Conduit AEP Software Guide
It is known exactly what IPv6 subnet is assigned to the device by the cellular provider/ISP.
All devices in LAN1 will have IPv6 Internet access.
SETUP
Configuration Example #4: Cellular WAN, Static LAN with user-selected addresses
For this example, the LAN has IPv6 addresses, but they're not in the recognized range of addresses the cellular provider/ISP have specified with a prefix. The LAN devices will network with each other over IPv6, but do not have
Internet access via IPv6. The device can ping IPv6 addresses on the Cellular WAN. However, since the LAN devices don’t have globally routable addresses recognized by the cellular provider/ISP, they get their packets dropped on the WAN link.
LAN subnet is outside of the range of addresses provided by the cellular provider/ISP.
Devices in LAN can see each other via IPv6.
Devices in LAN do not have Internet access via IPv6.
The router can ping IPv6 addresses.
All packets with invalid IPv6 addresses are dropped on the WAN link.
mPower TM Edge Intelligence Conduit AEP Software Guide 43
SETUP
Configuration Example #5: Cellular WAN, Static LAN, Delegated Prefix LAN
This scenario is a combination of examples #1 and #3. The difference is the Static LAN2 does not have Internet access because the prefix for the statically assigned addresses on that LAN do not match the delegated prefix from the cellular provider/ISP. The devices on LAN1 got their IPv6 addresses from the router that is using the delegated prefix from the cellular provider/ISP, so those devices have Internet access via IPv6. This example demonstrates the difference in behavior for the LAN networks based on the prefix delegation.
User configured LAN1 in Delegated Prefix IPv6 mode.
User configured LAN2 in Static IPv6 mode with user-selected addresses
Devices in LAN2 will see each other.
Devices in LAN1 will have Internet access via IPv6.
Devices in LAN2 will not have Internet access via IPv6.
44
Configuration Example #6: No IPv6 WAN, Static LAN
For this example, IPv6 is enabled on the LAN interface but disabled on the WAN side or not supported by the cellular provider/ISP. The delegation fails. This results in LAN1 not receiving delegated IPv6 addresses as it should, but only link-local IPv6 addresses. LAN2 has statically defined IPv6 addresses, but does not have Internet access since the device does not have an established IPv6 connection.
IPv6 support disabled on WAN interface or IPv6 is not supported by cellular provider/ISP.
Delegation fails.
Devices in LAN1 will not get any IPv6 addresses (except link-local).
Devices in LAN2 will see each other and have IPv6 addresses.
No IPv6 Internet access.
mPower TM Edge Intelligence Conduit AEP Software Guide
