Hi Ludovic, Thanks for the reply, I had already added the interface in wlc, but then I no longer log in to the portal to authenticate (connection_error). However this way I can already see the dhcp working Thanks
Cumprimentos, *Domingos Varela* Tel. +244 923 229 330 | Luanda - Angola Ludovic Zammit <[email protected]> escreveu no dia quinta, 31/10/2019 à(s) 16:26: > Hello Domingo, > > I think you will need to modify a couple of things in order to make it > work. > > First, change your registration lease time and max lease time to 30 > seconds. > > Then you will need to create a Registration VLAN 212 interface on the > Cisco WLC that forwards the DHCP requests to 10.7.80.100 > > Once you know that the remote device has been placed into the registration > VLAN 212 it should get an IP address. > > Thanks, > > > On Oct 31, 2019, at 10:37 AM, Domingos Varela via PacketFence-users < > [email protected]> wrote: > > Hi, > > I have the configuration so that the registration network works via > routinely, but I can not get registration ip, when the client turns on he > received the production address. > > As the image below, I have the registration interface on the switch core, > from the switch core I can ping the registration interface of PF. > > So I tried to add the registration interface in WLC and already had ip > address of the registration network, but I stopped accessing the portal, > can anyone help to solve this? > <image.png> > <image.png> > <image.png> > Thanks > Regards > > Cumprimentos, > > *Domingos Varela* > Tel. +244 923 229 330 | Luanda - Angola > _______________________________________________ > PacketFence-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/packetfence-users > > >
_______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
