Asus DSL-N12HP users manual in English - Page 90

Automatically Add Clients With Following DHCP Vendor IDs, video. The LAN interfaces are LAN1, LAN2

Page 90 highlights

Automatically Add Clients With Following DHCP Vendor IDs: Add support to automatically map LAN interfaces to PVC's using DHCP vendor ID (option 60). The local DHCP server will decline and send the requests to a remote DHCP server by mapping the appropriate LAN interface. This will be turned on when Interface Grouping is enabled. For example, imagine there are 4 PVCs (0/33, 0/36, 0/37, 0/38). VPI/ VCI=0/33 is for PPPoE while the other PVCs are for IP set-top box (video). The LAN interfaces are LAN1, LAN2, LAN3, and LAN4. The Interface Grouping configuration will be: 1. Default: LAN1, LAN2, LAN3, and LAN4. 2. Video: nas_0_36, nas_0_37, and nas_0_38. The DHCP vendor ID is "Video". If the onboard DHCP server is running on "Default" and the remote DHCP server is running on PVC 0/36 (i.e. for set-top box use only). LAN side clients can get IP addresses from the CPE's DHCP server and access the Internet via PPPoE (0/33). If a set-top box is connected to ETH1 and sends a DHCP request with vendor ID "Video", the local DHCP server will forward this request to the remote DHCP server. The Interface Grouping configuration will automatically change to the following: 1. Default: LAN2, LAN3, and LAN4 2. Video: nas_0_36, nas_0_37, nas_0_38, and LAN1 90

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181

90
Automatically Add Clients With Following DHCP Vendor IDs:
Add support to automatically map LAN interfaces to PVC's using
DHCP vendor ID (option 60). The local DHCP server will decline
and send the requests to a remote DHCP server by mapping the
appropriate LAN interface. This will be turned on when Interface
Grouping is enabled.
For example, imagine there are 4 PVCs (0/33, 0/36, 0/37, 0/38). VPI/
VCI=0/33 is for PPPoE while the other PVCs are for IP set-top box
(video). The LAN interfaces are LAN1, LAN2, LAN3, and LAN4.
The Interface Grouping configuration will be:
1.
Default: LAN1, LAN2, LAN3, and LAN4.
2.
Video: nas_0_36, nas_0_37, and nas_0_38. The DHCP vendor
ID is "Video".
If the onboard DHCP server is running on "Default" and the
remote DHCP server is running on PVC 0/36 (i.e. for set-top box
use only). LAN side clients can get IP addresses from the CPE's
DHCP server and access the Internet via PPPoE (0/33).
If a set-top box is connected to ETH1 and sends a DHCP request
with vendor ID "Video", the local DHCP server will forward this
request to the remote DHCP server. The Interface Grouping
configuration will automatically change to the following:
1.
Default: LAN2, LAN3, and LAN4
2.
Video: nas_0_36, nas_0_37, nas_0_38, and LAN1