# Advanced Mode - Configuration Scenarios
Complete examples for common use cases with both UCI and TR-181 configuration methods.
---
## Scenario 1: Simple Home Router (Transparent Bridge)
**Use Case**: All ports bridged together for simple home network
**Network Topology**:
```
All LAN ports + WAN → br-wan (no VLANs)
```
### UCI Configuration
```bash
uci set netmode.global.mode='advanced'
uci set netmode.mode_4_supprted_args_1.value='wan'
uci set netmode.mode_4_supprted_args_2.value='bridge:transparent'
uci set netmode.mode_4_supprted_args_3.value='ALL'
uci commit netmode && service netmode restart
```
### TR-181 Configuration
```xml
Device.X_IOWRT_EU_NetMode.Mode
advanced
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.1.Value
wan
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.2.Value
bridge:transparent
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.3.Value
ALL
```
**Result**:
- Single bridge interface `br-wan`
- All ports untagged
- DHCP client enabled
---
## Scenario 2: Traditional LAN Bridge with Routed WAN
**Use Case**: Classic router setup with LAN bridge and separate routed WAN
**Network Topology**:
```
All LAN ports → br-lan (bridge)
WAN port → wan (routed interface)
```
### UCI Configuration
```bash
uci set netmode.global.mode='advanced'
uci set netmode.mode_4_supprted_args_1.value='lan,wan'
uci set netmode.mode_4_supprted_args_2.value='bridge:transparent,route:transparent'
uci set netmode.mode_4_supprted_args_3.value='ALL_LAN,WAN'
uci commit netmode && service netmode restart
```
### TR-181 Configuration
```xml
Device.X_IOWRT_EU_NetMode.Mode
advanced
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.1.Value
lan,wan
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.2.Value
bridge:transparent,route:transparent
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.3.Value
ALL_LAN,WAN
```
**Result**:
- Bridge interface `br-lan` with all LAN ports only
- Routed interface `wan` on WAN port
- Traditional router topology
---
## Scenario 3: ISP Internet Service (Single VLAN)
**Use Case**: ISP requires VLAN 100 on WAN port for internet access
**Network Topology**:
```
WAN.100 (tagged) + LAN1-4 (untagged) → br-internet.100
```
### UCI Configuration (Bridge VLAN Filtering - Recommended)
```bash
uci set netmode.global.mode='advanced'
uci set netmode.mode_4_supprted_args_1.value='internet'
uci set netmode.mode_4_supprted_args_2.value='brvlan:wan-tagged:100'
uci set netmode.mode_4_supprted_args_3.value='ALL'
uci commit netmode && service netmode restart
```
### UCI Configuration (Traditional VLAN Devices)
```bash
uci set netmode.global.mode='advanced'
uci set netmode.mode_4_supprted_args_1.value='internet'
uci set netmode.mode_4_supprted_args_2.value='bridge:wan-tagged:100'
uci set netmode.mode_4_supprted_args_3.value='ALL'
uci commit netmode && service netmode restart
```
### TR-181 Configuration
```xml
Device.X_IOWRT_EU_NetMode.Mode
advanced
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.1.Value
internet
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.2.Value
brvlan:wan-tagged:100
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.3.Value
ALL
```
**Result**:
- WAN port tagged with VLAN 100
- LAN ports untagged
- DHCP client enabled
---
## Scenario 4: ISP Dual Service (Internet + IPTV)
**Use Case**: ISP provides Internet on VLAN 1499 and IPTV on VLAN 1510
**Network Topology**:
```
Internet: WAN.1499 (tagged) + LAN1-2 (untagged) → br-internet.1499
IPTV: WAN.1510 (tagged) + LAN3-4 (untagged) → br-tv.1510
```
### UCI Configuration
```bash
uci set netmode.global.mode='advanced'
uci set netmode.mode_4_supprted_args_1.value='internet,tv'
uci set netmode.mode_4_supprted_args_2.value='brvlan:wan-tagged:1499,brvlan:wan-tagged:1510-n'
uci set netmode.mode_4_supprted_args_3.value='LAN1-LAN2-WAN,LAN3-LAN4-WAN'
uci commit netmode && service netmode restart
```
### TR-181 Configuration
```xml
Device.X_IOWRT_EU_NetMode.Mode
advanced
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.1.Value
internet,tv
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.2.Value
brvlan:wan-tagged:1499,brvlan:wan-tagged:1510-n
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.3.Value
LAN1-LAN2-WAN,LAN3-LAN4-WAN
```
**Result**:
- Internet bridge on VLAN 1499 with LAN1-2
- IPTV bridge on VLAN 1510 with LAN3-4 (proto=none, no DHCP)
- Both services use WAN port with respective VLANs
---
## Scenario 5: ISP Triple-Play (Internet + IPTV + VoIP)
**Use Case**: Full triple-play service with Internet, IPTV, and VoIP
**Network Topology**:
```
Internet: WAN.100 (tagged) + LAN1-2 (untagged) → br-internet.100
IPTV: WAN.200 (tagged) + LAN3 (untagged) → br-tv.200
VoIP: WAN.300 (tagged) + LAN4 (untagged) → br-voip.300
```
### UCI Configuration
```bash
uci set netmode.global.mode='advanced'
uci set netmode.mode_4_supprted_args_1.value='internet,tv,voip'
uci set netmode.mode_4_supprted_args_2.value='brvlan:wan-tagged:100,brvlan:wan-tagged:200-n,brvlan:wan-tagged:300-n'
uci set netmode.mode_4_supprted_args_3.value='LAN1-LAN2-WAN,LAN3-WAN,LAN4-WAN'
uci commit netmode && service netmode restart
```
### TR-181 Configuration
```xml
Device.X_IOWRT_EU_NetMode.Mode
advanced
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.1.Value
internet,tv,voip
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.2.Value
brvlan:wan-tagged:100,brvlan:wan-tagged:200-n,brvlan:wan-tagged:300-n
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.3.Value
LAN1-LAN2-WAN,LAN3-WAN,LAN4-WAN
```
**Result**:
- Internet on VLAN 100 with DHCP (LAN1-2)
- IPTV on VLAN 200 without DHCP (LAN3)
- VoIP on VLAN 300 without DHCP (LAN4)
---
## Scenario 6: Routed Multi-Service (Internet + IPTV + Management)
**Use Case**: Multiple routed services on different VLANs with NAT/firewall
**Network Topology**:
```
WAN.100 → wan (routed, DHCP, firewall)
WAN.200 → iptv (routed, DHCP, firewall)
WAN.300 → mgmt (routed, DHCP, firewall)
```
### UCI Configuration
```bash
uci set netmode.global.mode='advanced'
uci set netmode.mode_4_supprted_args_1.value='wan,iptv,mgmt'
uci set netmode.mode_4_supprted_args_2.value='route:vlan:100,route:vlan:200,route:vlan:300'
uci set netmode.mode_4_supprted_args_3.value='WAN,WAN,WAN'
uci commit netmode && service netmode restart
```
### TR-181 Configuration
```xml
Device.X_IOWRT_EU_NetMode.Mode
advanced
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.1.Value
wan,iptv,mgmt
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.2.Value
route:vlan:100,route:vlan:200,route:vlan:300
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.3.Value
WAN,WAN,WAN
```
**Result**:
- Three separate routed interfaces
- Each with own firewall zone
- All with DHCP clients enabled
---
## Scenario 7: Hybrid Setup (Routed Internet + Bridged IPTV)
**Use Case**: Internet needs routing/NAT, but IPTV needs transparent bridge to STBs
**Network Topology**:
```
WAN.100 → wan (routed, firewall)
WAN.200 + LAN1-3 → br-iptv.200 (bridged, transparent)
```
### UCI Configuration
```bash
uci set netmode.global.mode='advanced'
uci set netmode.mode_4_supprted_args_1.value='wan,iptv'
uci set netmode.mode_4_supprted_args_2.value='route:vlan:100,brvlan:wan-tagged:200-n'
uci set netmode.mode_4_supprted_args_3.value='WAN,LAN1-LAN2-LAN3-WAN'
uci commit netmode && service netmode restart
```
### TR-181 Configuration
```xml
Device.X_IOWRT_EU_NetMode.Mode
advanced
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.1.Value
wan,iptv
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.2.Value
route:vlan:100,brvlan:wan-tagged:200-n
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.3.Value
WAN,LAN1-LAN2-LAN3-WAN
```
**Result**:
- WAN interface routed with firewall
- IPTV bridged transparently to LAN ports
- Firewall enabled (because of routed interface)
---
## Scenario 8: Corporate Network with Trunk Port
**Use Case**: LAN1 is trunk port to managed switch, other ports are access ports
**Network Topology**:
```
VLAN 200: LAN1 (tagged) + WAN (tagged) + LAN2-3 (untagged) → br-corporate.200
```
### UCI Configuration
```bash
uci set netmode.global.mode='advanced'
uci set netmode.mode_4_supprted_args_1.value='corporate'
uci set netmode.mode_4_supprted_args_2.value='brvlan:mixed:200:LAN1-WAN'
uci set netmode.mode_4_supprted_args_3.value='LAN1-LAN2-LAN3-WAN'
uci commit netmode && service netmode restart
```
### TR-181 Configuration
```xml
Device.X_IOWRT_EU_NetMode.Mode
advanced
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.1.Value
corporate
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.2.Value
brvlan:mixed:200:LAN1-WAN
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.3.Value
LAN1-LAN2-LAN3-WAN
```
**Result**:
- LAN1 and WAN tagged (trunk ports)
- LAN2-3 untagged (access ports)
- All on VLAN 200
---
## Scenario 9: Enterprise Multi-VLAN (Separate Networks)
**Use Case**: Separate networks for guest, corporate, and management
**Network Topology**:
```
Guest: WAN.100 (tagged) + LAN1 (untagged) → br-guest.100
Corporate: WAN.200 (tagged) + LAN2-3 (untagged) → br-corporate.200
Management: WAN.300 (tagged) + LAN4 (untagged) → br-mgmt.300
```
### UCI Configuration
```bash
uci set netmode.global.mode='advanced'
uci set netmode.mode_4_supprted_args_1.value='guest,corporate,mgmt'
uci set netmode.mode_4_supprted_args_2.value='brvlan:wan-tagged:100-n,brvlan:wan-tagged:200-n,brvlan:wan-tagged:300'
uci set netmode.mode_4_supprted_args_3.value='LAN1-WAN,LAN2-LAN3-WAN,LAN4-WAN'
uci commit netmode && service netmode restart
```
### TR-181 Configuration
```xml
Device.X_IOWRT_EU_NetMode.Mode
advanced
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.1.Value
guest,corporate,mgmt
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.2.Value
brvlan:wan-tagged:100-n,brvlan:wan-tagged:200-n,brvlan:wan-tagged:300
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.3.Value
LAN1-WAN,LAN2-LAN3-WAN,LAN4-WAN
```
**Result**:
- Guest network on VLAN 100 (no DHCP)
- Corporate network on VLAN 200 (no DHCP)
- Management network on VLAN 300 (DHCP enabled)
---
## Scenario 10: Wholesale QinQ Provider
**Use Case**: Service provider supporting multiple customers with QinQ (802.1ad)
**Network Topology**:
```
Customer A: All ports double-tagged (S-tag 100, C-tag 10)
Customer B: All ports double-tagged (S-tag 100, C-tag 20)
```
### UCI Configuration
```bash
uci set netmode.global.mode='advanced'
uci set netmode.mode_4_supprted_args_1.value='customer_a,customer_b'
uci set netmode.mode_4_supprted_args_2.value='bridge:qinq:10:100-n,bridge:qinq:20:100-n'
uci set netmode.mode_4_supprted_args_3.value='LAN1-LAN2-WAN,LAN3-LAN4-WAN'
uci commit netmode && service netmode restart
```
### TR-181 Configuration
```xml
Device.X_IOWRT_EU_NetMode.Mode
advanced
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.1.Value
customer_a,customer_b
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.2.Value
bridge:qinq:10:100-n,bridge:qinq:20:100-n
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.3.Value
LAN1-LAN2-WAN,LAN3-LAN4-WAN
```
**Result**:
- Customer A bridge with C-tag 10, S-tag 100
- Customer B bridge with C-tag 20, S-tag 100
- Both without DHCP (proto=none)
**Note**: QinQ requires traditional `bridge:` mode, not available with `brvlan:` mode.
---
## Scenario 11: MACVLAN Multi-Service (Different MAC Addresses)
**Use Case**: ISP requires different MAC addresses for Internet and IPTV services
**Network Topology**:
```
WAN (default MAC) → wan (routed)
WAN (custom MAC) → iptv (routed)
```
### UCI Configuration
```bash
uci set netmode.global.mode='advanced'
uci set netmode.mode_4_supprted_args_1.value='wan,iptv'
uci set netmode.mode_4_supprted_args_2.value='route:transparent,route:macvlan:AA:BB:CC:DD:EE:FF'
uci set netmode.mode_4_supprted_args_3.value='WAN,WAN'
uci commit netmode && service netmode restart
```
### TR-181 Configuration
```xml
Device.X_IOWRT_EU_NetMode.Mode
advanced
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.1.Value
wan,iptv
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.2.Value
route:transparent,route:macvlan:AA:BB:CC:DD:EE:FF
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.3.Value
WAN,WAN
```
**Result**:
- WAN interface with default MAC
- IPTV interface with custom MAC (AA:BB:CC:DD:EE:FF)
- Both routed with firewall
---
## Scenario 12: Standalone VLAN Interface
**Use Case**: WAN as standalone VLAN interface (no bridge, no routing, for custom protocols)
**Network Topology**:
```
WAN.2501 → wan (standalone, proto=dhcp)
```
### UCI Configuration
```bash
uci set netmode.global.mode='advanced'
uci set netmode.mode_4_supprted_args_1.value='wan'
uci set netmode.mode_4_supprted_args_2.value='direct:vlan:2501'
uci set netmode.mode_4_supprted_args_3.value='WAN'
uci commit netmode && service netmode restart
```
### TR-181 Configuration
```xml
Device.X_IOWRT_EU_NetMode.Mode
advanced
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.1.Value
wan
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.2.Value
direct:vlan:2501
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.3.Value
WAN
```
**Result**:
- WAN.2501 VLAN device created
- No bridge, no routing layer
- proto=none (manual configuration needed)
---
## Scenario 13: All Ports Tagged (Managed Network)
**Use Case**: All ports need VLAN tags for managed switch environment
**Network Topology**:
```
VLAN 100: All ports tagged → br-mgmt.100
```
### UCI Configuration
```bash
uci set netmode.global.mode='advanced'
uci set netmode.mode_4_supprted_args_1.value='mgmt'
uci set netmode.mode_4_supprted_args_2.value='brvlan:tagged:100'
uci set netmode.mode_4_supprted_args_3.value='ALL'
uci commit netmode && service netmode restart
```
### TR-181 Configuration
```xml
Device.X_IOWRT_EU_NetMode.Mode
advanced
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.1.Value
mgmt
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.2.Value
brvlan:tagged:100
Device.X_IOWRT_EU_NetMode.SupportedModes.4.SupportedArguments.3.Value
ALL
```
**Result**:
- All ports (LAN + WAN) tagged with VLAN 100
- Single bridge with VLAN filtering
- DHCP client enabled
---
## Quick Reference: Configuration Cheat Sheet
### Interface Types
| Type | Syntax | When to Use |
|------|--------|-------------|
| Transparent Bridge | `bridge:transparent` | Simple home network, no VLANs |
| Bridge VLAN Filtering (Tagged) | `brvlan:tagged:VID` | All ports need VLAN tags, modern approach |
| Bridge VLAN Filtering (WAN Tagged) | `brvlan:wan-tagged:VID` | ISP VLAN on WAN, LAN untagged (recommended) |
| Bridge VLAN Filtering (Mixed) | `brvlan:mixed:VID:PORTS` | Custom trunk/access port setup |
| Traditional Tagged Bridge | `bridge:tagged:VID` | Legacy systems, all ports tagged |
| Traditional WAN Tagged | `bridge:wan-tagged:VID` | Legacy ISP VLAN setup |
| QinQ Bridge | `bridge:qinq:CVID:SVID` | Wholesale provider, double tagging |
| Routed VLAN | `route:vlan:VID` | Need routing/NAT per service |
| Routed MACVLAN | `route:macvlan:MAC` | Different MAC per service |
| Direct VLAN | `direct:vlan:VID` | Standalone VLAN for custom protocols |
### Modifiers
| Modifier | Effect | Example |
|----------|--------|---------|
| `-n` | Disable DHCP client (proto=none) | `brvlan:wan-tagged:100-n` |
| `-d` | Disable interface | `route:vlan:200-d` |
### Port Specifications
| Syntax | Meaning |
|--------|---------|
| `ALL` | All LAN + WAN ports |
| `WAN` | WAN port only |
| `LAN1-LAN2-WAN` | LAN1, LAN2, and WAN |
| `LAN1-LAN3` | LAN1 and LAN3 only |
### MAC Address Macros
| Macro | Description | Example Result |
|-------|-------------|----------------|
| `BaseMACAddress` | Base MAC from `fw_printenv -n ethaddr` | `94:3F:0C:D5:76:00` |
| `BaseMACAddressP1` | Base MAC + 1 | `94:3F:0C:D5:76:01` |
| `BaseMACAddressP2` | Base MAC + 2 | `94:3F:0C:D5:76:02` |
| `BaseMACAddressPN` | Base MAC + N | `BaseMACAddressP5` → `94:3F:0C:D5:76:05` |
| Explicit MAC | Direct assignment | `AA:BB:CC:DD:EE:FF` |
---
**Document Version**: 1.0
**Last Updated**: 2025-12-12