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,
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
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)
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
Ah that's the problem. If I use /Aruba or anything else I get the Not
Implemented. Get to /Aruba is not supported.
On Thu, Mar 12, 2020, 5:53 PM Durand fabrice via PacketFence-users <
packetfence-users@lists.sourceforge.net> wrote:
> In this case, is it a webauth setup ? (
>
In this case, is it a webauth setup ?
(https://packetfence.org/doc/PacketFence_Network_Devices_Configuration_Guide.html#_webauth)
If it's the case, the portal URL must be https://PACKETFENCESERVER/Aruba .
https://github.com/inverse-inc/packetfence/blob/devel/lib/pf/web/constants.pm#L105
Le
The bluedogrv SSID issues have been pretty much solved. I just did some
tweaking to the bindings, and connection profile and people had to forget
the network as the certificate changes made a few devices freak out. Little
issues here and there but nothing major. it's really the captive portal
Do you have the logs related to this radius request ? (packetfence.log)
It looks to me that you are doing 802.1x + web auth.
For the ssid BlueDogRV, just configure it like
https://packetfence.org/doc/PacketFence_Network_Devices_Configuration_Guide.html#_all_aruba_os
(Secure SSID and not like
User-Name = "host/ta-00614.BluedogRV.lan"
NAS-IP-Address = 192.168.100.217
NAS-Port = 0
Service-Type = Framed-User
Framed-MTU = 1100
State = 0x2880f3b42988e97dfdf00d5089857e6a
Called-Station-Id = "f0:5c:19:c2:13:96"
Calling-Station-Id = "9c:30:5b:1c:06:4b"
NAS-Identifier = "Aruba_Wireless"
Ok so first there is no ssid sent in the radius request so you can't use
a filter based on the ssid.
So what you can do (removed the ssid):
[Wireless_EAP]
filter_match_style=all
description=Wireless_EAP
sources=tacos-MachineAuth
filter=connection_type:Wireless-802.11-EAP
autoregister=enabled
Okay so this is the one from today. get's matched to the Ethernet profile
and denied.
Mar 11 08:57:01 NAC1 packetfence_httpd.aaa: httpd.aaa(9641) INFO:
[mac:00:24:d7:90:be:84] handling radius autz request: from switch_ip =>
(192.168.100.216), connection_type => Wireless-802.11-EAP,switch_mac =>
Here is the portal debug log for the our Aruba IAP's. first log is redirect
URL set to https://PACKETFENCESERVER/. Second is set to
https://PACKETFENCESERVER/Aruba::Instant_Access
NAC1 packetfence_httpd.portal: httpd.portal(1228) DEBUG:
[mac:30:24:32:a3:ef:ad] hitting handler with URI
Yep I'm scrubbing them now. It's also matching clients connecting on
wireless-eap to wired-eap
On Tue, Mar 10, 2020, 4:53 PM Durand fabrice via PacketFence-users <
packetfence-users@lists.sourceforge.net> wrote:
> Hello,
>
> can you provide the packetfence.log file and the profiles.conf file ?
>
Hello,
can you provide the packetfence.log file and the profiles.conf file ?
Regards
Fabrice
Le 20-03-10 à 15 h 19, Zacharry Williams via PacketFence-users a écrit :
Hey all,
Randomly it matched the correct connection profile, one time. Is this
like a 9.3 bug where connection profiles
Hey all,
Randomly it matched the correct connection profile, one time. Is this like
a 9.3 bug where connection profiles aren't being match?
On Mon, Mar 9, 2020 at 3:06 PM Zacharry Williams
wrote:
> Hey all,
>
> I've been working on setting up a guest LAN and a byod LAN for a few days
> now.
Hey all,
I've been working on setting up a guest LAN and a byod LAN for a few days
now. When I use a PSK or AD Authentication it works fine, but the captive
portal isn't working like I think it should be.
I revisited the guide a few times to check and I don't think i'm missing
any settings. I
From: Morris, Andi [mailto:amor...@cardiffmet.ac.uk]
Sent: 13 June 2014 14:47
To: 'packetfence-users@lists.sourceforge.net'
Subject: Re: [PacketFence-users] Captive portal issues - page can't be displayed
This makes no difference I'm afraid.
Cheers,
Andi
From: Louis Munro [mailto:lmu
Hi Andi,
Remove the fake_mac_enabled below and restart PF.
I believe this is a bug in the configurator.
Regards,
--
Louis Munro
lmu...@inverse.ca :: www.inverse.ca
+1.514.447.4918 *125 :: +1 (866) 353-6153
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
This makes no difference I'm afraid.
Cheers,
Andi
From: Louis Munro [mailto:lmu...@inverse.ca]
Sent: 13 June 2014 14:33
To: packetfence-users@lists.sourceforge.net
Subject: Re: [PacketFence-users] Captive portal issues - page can't be displayed
Hi Andi,
Remove the fake_mac_enabled below
Hi all,
For some reason my captive portal doesn't show users any websites, including
the Packetfence captive portal. In IE I get the 'Page Cannot be displayed'
error, and Chrome I get the linkhelp.clients.google.com error message where it
reports Something is currently interfering with your
On 2014-06-12, at 11:18 , Morris, Andi amor...@cardiffmet.ac.uk wrote:
Hi all,
For some reason my captive portal doesn’t show users any websites, including
the Packetfence captive portal. In IE I get the ‘Page Cannot be displayed’
error, and Chrome I get thelinkhelp.clients.google.com
Andi,
Please also post your conf/networks.conf file.
Regards,
--
Louis Munro
lmu...@inverse.ca :: www.inverse.ca
+1.514.447.4918 *125 :: +1 (866) 353-6153
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
(www.packetfence.org)
On 2014-06-12, at 13:34 , Louis Munro
22 matches
Mail list logo
