Hello, Set your interface enp0s29u1u5 at “none” because it looks like it’s your trunk interface,
Then, set correct ip addresses on your interface: [interface enp0s29u1u5.18] enforcement=vlan ip=10.0.18.0 type=internal mask=255.255.255.0 [interface enp0s29u1u5.16] ip=10.0.16.0 type=other mask=255.255.255.0 You can put whatever your want like .1 but not .0 [captive_portal] # # captive_portal.network_detection_ip # # This IP is used as the webserver who hosts the common/network-access-detection.gif which is used to detect if network # access was enabled. # It cannot be a domain name since it is used in registration or quarantine where DNS is blackholed. # It is recommended that you allow your users to reach your packetfence server and put your LAN's PacketFence IP. # By default we will make this reach PacketFence's website as an easy solution. # network_detection_ip=10.0.0.3 Remove the 10.0.0.3 and keep the default 192.95.20.194 ip address. It will break your network detection during the registration process. I will advice you to do those changes in the admin web interface and then restart all service using the cli: /usr/local/pf/bin/pfcmd service pf restart Thanks, Ludovic Zammit lzam...@inverse.ca <mailto:lzam...@inverse.ca> :: +1.514.447.4918 (x145) :: www.inverse.ca <http://www.inverse.ca/> Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu <http://www.sogo.nu/>) and PacketFence (http://packetfence.org <http://packetfence.org/>) > On Oct 16, 2020, at 10:20 AM, Goodspeed, William <william.goodsp...@g3ti.net> > wrote: > > Hey Ludovic, > > I’m Running 10.1 and yes I see that pf-main.pl is present. > > Attached are the conf and screenshot of ipconfig /all for the ethernet > interface of the laptop I am testing with. > > Thank you, > > William > > > > From: Ludovic Zammit <lzam...@inverse.ca <mailto:lzam...@inverse.ca>> > Sent: Friday, October 16, 2020 8:33 AM > To: packetfence-users@lists.sourceforge.net > <mailto:packetfence-users@lists.sourceforge.net> > Cc: Goodspeed, William <william.goodsp...@g3ti.net > <mailto:william.goodsp...@g3ti.net>> > Subject: Re: [PacketFence-users] Getting Registration VLAN DHCP but not > getting Portal > > Hello, > > Which PacketFence version are you running ? Is your server patched with > addons/pf-maint.pl ? > > Share the conf/pf.conf > > Share a screenshot of the ipconfig /all of the testing device. > > Thanks, > > Ludovic Zammit > lzam...@inverse.ca <mailto:lzam...@inverse.ca> :: +1.514.447.4918 (x145) :: > www.inverse.ca <http://www.inverse.ca/> > Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu > <http://www.sogo.nu/>) and PacketFence (http://packetfence.org > <http://packetfence.org/>) > > > > > > On Oct 15, 2020, at 9:56 AM, Goodspeed, William via PacketFence-users > <packetfence-users@lists.sourceforge.net > <mailto:packetfence-users@lists.sourceforge.net>> wrote: > > Good Morning, > > I am trying to get PF set up and I’ve gotten to the point where I can connect > a laptop, PF correctly assigns the switch port the registration VLAN, and it > gets a dhcp address from the registration VLAN I created in PF. When I try to > open a browser and get to the registration page I get a > “err_connection_refused” error and it doesn’t forward me to anything. Any > pointers on where to start looking? I’m running on CentOS 7 and have checked > that firewalld and selinux are disabled. I’m pretty sure that I have followed > the configuration steps correctly but maybe there is something I missed. > > Thank you, > > William G. > _______________________________________________ > PacketFence-users mailing list > PacketFence-users@lists.sourceforge.net > <mailto:PacketFence-users@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/packetfence-users > <https://lists.sourceforge.net/lists/listinfo/packetfence-users> > > <pf.conf><Ethernet IP Config All.PNG>
_______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
