Questo sito utilizza cookie di profilazione (propri e di terze parti) per ottimizzare la tua esperienza online e per inviarti pubblicità in linea con le tue preferenze. Continuando a utilizzare questo sito senza modificare le tue preferenze acconsenti all’uso dei cookie. Se vuoi saperne di più o negare il consenso a tutti o ad alcuni cookie clicca qui>
The website that you are visiting also provides Arabian language. Do you wish to switch language version?
يوفر موقع الويب الذي تزوره المحتوى باللغة العربية أيضًا. هل ترغب في تبديل إصدار اللغة؟
The website that you are visiting also provides Russia language Do you wish to switch language version?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
The scenario is as follow: the customer had an USG FW which was acting as a DHCP server and VLANs: VLAN 100 Teachers( 192.168.100.0/24) and VLAN 101 for Students(GW 192.168.101.0/24) . Vlan 1 was the management VLAN for the devices: FW-AC-SW-AP. Wireless clients could get an IP address from the service-vlan but the issue was with the wired stations. When the customer connected a station to the second port GE0/0/1 of AP4051, he could receive an IP from VLAN1 since it was allowed on the path to DHCP server . But, when he made an wired profile for the second port with mode endpoint, ipv4 learning and untagged VLAN 100, the station didn’t get an IP from VLAN 100.
I tested this scenario and I confirmed that it can work for a wired
station to get IP from a separate VLAN
or from service vlan that is configured on AC. Below was my config and scenario
- topology used :
- -cellphone gets IP from VLAN 101 which is the service-vlan :
- --PC gets IP from VLAN 102 which is configured on DHCP server also :
- -configuration that I used for wired port :
- --configuration on AP after reboot :
Whole configurations :
I advised to check that the AP has the same configuration for the G1
port interface and also that the service vlan is allowed on the way to DHCP