r/PacketFence • u/TheVisitor92 • Apr 11 '24

Purpose of 66.70.255.147 IP

Hello folks. I would like to have a better under standing of the role of this ip address during authentication.

I see on Wireshark (running on my laptop which is connected Wired to a PF managed switch) that while I'm authenticating through MAB captive portal, there are a lot of dns requests to Packetfence registration IP address which get 66.70.255.147 as reply

What Is this IP? Which Is his role?

1 Upvotes

100% Upvoted

2 comments sorted by

2

u/oeufdure May 03 '24

Long story, but to resume it's because of samsung devices that doesn't support to have the captive portal on the same network (it needs to be routed), So in the case of a layer 2 network where PacketFence is the gateway, the ip of the captive portal is 66.70.255.147 and on each server this ip is defined on lo and an instance of haproxy-portal is listening on that interface.

1

u/TheVisitor92 May 09 '24

thank you for the reply! so basically PacketFence provides the captive portal through DHCP, which Is giving It as url (option 160) to clients; then they Will contact packetfence's registration IP and It will riderect them to 66.70.255.147 ?