We're having issues with the clients not getting redirected to the captive
portal. From what I can find, all of the DNS requests return 192.0.2.1 now. Is
this supposed to work? Our clients sit idle and cant get to the portal even if
we manually enter the dns or ip address. Currently we're runnin
If it's a layer 2 registration network then the dns will answer with the
ip 192.0.2.1 (to fix the samsung captive portal detection)
So check to see if the ip is on the lo interface (ip a), if it's the
case check to see if the haproxy-portal is listening on this ip (netstat
-nlp| grep 443)
Al
Looks like the ip is assigned:
1: lo: mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet 192.0.2.1/32 scope link lo
valid_l
Hum weird, when you try to ping 192.0.2.1 from your device can you see
the request on the registration interface ?
It's sounds to me that you have something local on your device that
route 192.168.2.1 somewhere, can you verify the routing table ?
Regards
Fabrice
Le 20-06-05 à 12 h 01, Ryan
