Just for fun: https://youtu.be/ZTeqM5gciH8
Le lun. 5 avr. 2021 à 14:37, Ludovic Zammit via PacketFence-users < packetfence-users@lists.sourceforge.net> a écrit : > Hello Antoine, > > Your problem is that the Registration and Isolation VLANs can’t go out of > your Hypervisor so testing in the same hypervisor won’t show much. > > Do a an access VLAN on the switch in front of your hypervisor and you > should get DHCP from PF registration, if none, it’s a VLAN span issue. > > What’s your hypervisor ? > > Make sure to tag the Hypervisor uplink ports and also add the correct VLAN > into the trunk uplinks from PF to the equipments (switches, APs, wireless > controller, etc..) > > Thanks, > > > Ludovic Zammit > lzam...@inverse.ca :: +1.514.447.4918 (x145) :: www.inverse.ca > Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and PacketFence > (http://packetfence.org) > > > > > > > > > On Mar 31, 2021, at 5:39 AM, Antoine JEZEQUEL via PacketFence-users < > packetfence-users@lists.sourceforge.net> wrote: > > Hello everybody, > > I have a problem with my packetfence V10 server. > I currently have a packetfence server with 3 interfaces: A management > interface, a registration interface and a Guest interface. > The Management interface works perfectly, it can contact anyone on its > subnet and vice versa. On the other hand, the 2 other interfaces cannot > contact any host in their subnet, and vice versa. > I created another test server with several interfaces to make sure that > the problem was not with the vlan configurations on our Hypervisor. It > turned out that the problem is not there because I was able to communicate > with several IPs of the registration vlan and Guest, but not with the > registration and guest interface of the packetfence server. > > I performed several tests including server restarts, deletion and addition > of server interfaces from the hypervisor etc ... > > For more information, here are the configurations that are automatically > added in /usr/local/pf/var/ifcfg-ens224 and in > /etc/sysconfig/network-scripts/ifcfg-ens224 when creating an interface + > configuration via the web: > > DEVICE = ens224 > > ONBOOT = yes > BOOTPROTO = static > NM_CONTROLLED = no > IPADDR = 192.168.X.X > NETMASK = 255.255.255.0 > IPV6INIT = no > IPV6ADDR = > > If I do a « ifconfig » command, i can see that interfaces are up > (<UP,BROADCAST,RUNNING,MULTICAST>) > > Has anyone ever had a similar problem? > > Do not hesitate to ask me for any necessary information. > > I hope you can help me! > > Thank you! > > Antoine > _______________________________________________ > PacketFence-users mailing list > PacketFence-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/packetfence-users > > > _______________________________________________ > PacketFence-users mailing list > PacketFence-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/packetfence-users >
_______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
