Hello Fabrice, thank you very very much, you pointed me to the right direction; there was a misconfiguration on my client, about the DNS. Now it works perfectly, even with SAML Thank you Best Regards Marco
Il giorno gio 22 set 2022 alle ore 20:07 Fabrice Durand <oeufd...@gmail.com> ha scritto: > Hello Marco, > > the packetfence dns server is supposed to return the ip address of the > captive portal (this one 66.70.255.147). > so check to see with tcpdump per example if it´s the case (capture from > the server on the inline l2 interface). > Regards > Fabrice > > > Le jeu. 22 sept. 2022 à 09:03, Marco Naimoli <marco.naim...@unipd.it> a > écrit : > >> Hello, just a little update: if I set browser (in the client) to http://[ip >> of pf inlinel2 interface]/captive_portal everything >> works as expected, the client registers successfully and its status >> becomes registered >> Best Regards >> Marco >> >> >> Il giorno gio 22 set 2022 alle ore 11:30 Marco Naimoli < >> marco.naim...@unipd.it> ha scritto: >> >>> Hello Fabrice, thank you for the answer; for simplicity I started from >>> scratch with a new installation and configured >>> the internal interface as inline l2, following the guide, but I was >>> unable to add "portal" as additional service: when I save, >>> the service disappear from the input field. >>> DHCP on that interface works; I've configured also a connection profile >>> with null authentication and filter "Network" >>> with the network of the internal interface. Ip forwarding is >>> enabled, management network has a default gateway and can connect to any >>> site on internet; client gets ip address >>> from packetfence and appears on the "Nodes" section with the status of >>> "Unregistered", but still the registration page >>> doesn't appear when I try to connect to a http:// site (like >>> http://www.google.com). I've also tried to set >>> 0.0.0.0/0 on connection profile filter, but nothing changes. >>> I also tried to enable "Portal" on the management interface >>> Any hint, direction ? I've read the chapter 10 "Adding inline >>> enforcement to existing installation": is there other configurations >>> on other chapters? >>> Thank you >>> Best Regards >>> Marco >>> >>> >>> Il giorno gio 22 set 2022 alle ore 04:02 Fabrice Durand < >>> oeufd...@gmail.com> ha scritto: >>> >>>> Hello Marco, >>>> >>>> you can try the inline setup. >>>> One interface is configured as inline l2 and the other one as the >>>> management interface (facing internet) >>>> So when you plug something in the inline network you should be able to >>>> see the portal. (it´s really the first thing you need to achieve) >>>> Btw you will have to add more config in order to do SAML. >>>> >>>> Regards >>>> Fabrice >>>> >>>> >>>> Le mar. 20 sept. 2022 à 14:23, Marco Naimoli via PacketFence-users < >>>> packetfence-users@lists.sourceforge.net> a écrit : >>>> >>>>> Hi, I'm new to PacketFence; I've installed a new instance (ZEN) and >>>>> would like to configure a >>>>> (simple) captive portal with SAML authentication; >>>>> it should be something like >>>>> client --> PacketFence ---> internet >>>>> Is this kind of setup supported ? In the documentation I find only >>>>> examples that involves the configuration of a switch >>>>> I've tried to configure it, but the client is never redirect to the >>>>> Identity Provider (I've configured the passthrough with the Identity >>>>> Provider hostname) >>>>> Is there any example about a Captive portal setup other than the >>>>> official documentation ? >>>>> Thank you >>>>> Marco >>>>> _______________________________________________ >>>>> 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
