I can't get Captive Portal login page in any browser else Firefox

jetberrocal

Now I think got worst.

I reinstall pfsense 2.3.1 amd64 from cero, even format the HD to make sure no files remained. Did not install any package. I set the LAN IP static, WAN IP takes IP from Cable modem DHCP. I turn off DHCP on LAN interface as the LAN side takes the IPs from the Windows Domain DHCP server.

Added CP zone, with Local Authentication. HTTPS Login unchecked. Added the pfsense IP at Allowed IP Addresses.

The Win7 computer access internet as if CP is turn off, is not blocked.

Shell Output - ipfw -x 2 show

65291 0 0 allow pfsync from any to any
65292 0 0 allow carp from any to any
65301 20 776 allow ip from any to any layer2 mac-type 0x0806,0x8035
65302 0 0 allow ip from any to any layer2 mac-type 0x888e,0x88c7
65303 0 0 allow ip from any to any layer2 mac-type 0x8863,0x8864
65307 0 0 deny ip from any to any layer2 not mac-type 0x0800,0x86dd
65310 131 17105 allow ip from any to table(100) in
65311 155 88607 allow ip from table(100) to any out
65312 0 0 allow ip from any to 255.255.255.255 in
65313 0 0 allow ip from 255.255.255.255 to any out
65314 582 80166 pipe tablearg ip from table(3) to any in
65315 0 0 pipe tablearg ip from any to table(4) in
65316 0 0 pipe tablearg ip from table(3) to any out
65317 672 429906 pipe tablearg ip from any to table(4) out
65318 0 0 pipe tablearg ip from table(1) to any in
65319 0 0 pipe tablearg ip from any to table(2) out
65532 0 0 fwd 127.0.0.1,8002 tcp from any to any dst-port 80 in
65533 0 0 allow tcp from any to any out
65534 0 0 deny ip from any to any
65535 0 0 allow ip from any to any

Shell Output - ipfw -x 2 table all list

–-table(3)---
192.168.56.0/24 2000
---table(4)---
192.168.56.0/24 2001
---table(100)---
192.168.56.1/32 0

Note: the pfsense IP is 192.168.56.1/24, don't know why table(100) has 192.168.56.1/32

Gertjan

@jetberrocal:

…...
...... I turn off DHCP on LAN interface as the LAN side takes the IPs from the Windows Domain DHCP server.
......

Added CP zone, ...............

STOP.
While you set up your portal settings, read the foot note.

https://forum.pfsense.org/index.php?topic=111737.msg632639#msg632639

( => case solved ;) )

jetberrocal

@Gertjan:

@jetberrocal:

…...
...... I turn off DHCP on LAN interface as the LAN side takes the IPs from the Windows Domain DHCP server.
......

Added CP zone, ...............

STOP.
While you set up your portal settings, read the foot note.

https://forum.pfsense.org/index.php?topic=111737.msg632639#msg632639

( => case solved ;) )

OK. I though that there was a posible work around.

Not being the case, for my needs CP in pfsense is not a viable solution. In my case as many others, DHCP and primary DNS must be kept on the Windows Domain Controller.

skron

DHCP Relay (and keeping DNS to DC) is not an option?

jetberrocal

@skron:

DHCP Relay (and keeping DNS to DC) is not an option?

How will I use DHCP Relay?

My DHCP (DC/DNS) server IP is 192.168.56.10 (static, 255.255.255.0)
My pfsense IP is 192.168.56.1 (static, 255.255.255.0) in LAN side, WAN is DHCP assign from cable modem. I do not have any other interface.

jetberrocal

It happens that I have a client that has a Win Server with AD/DNS but without DHCP because it has a Wifi Router that is doing the DHCP Server role.

So I can turn on DHCP on pfsense and configure the router to use the pfsense's dhcp.

How should I configure the pfsense dhcp to register addresses in the AD/DNS?

Once I get this dhcp running I can turn on CP in pfsense

Derelict

No idea why you wouldn't just use Windows DHCP in that case.

jetberrocal

@Derelict:

No idea why you wouldn't just use Windows DHCP in that case.

I tried Captive Portal with DHCP in the AD, but it did not work. Also in this thread was directed to the note referred by Gertjan on: June 21, 2016, 04:55:46 am , implying that DHCP must be done by pfsense as CP works correctly.

It was suggested to use DHCP relay but I do not how could I use that for this situation.

jetberrocal

OH! Still does not work.

I turn dhcp off in the AD server and turn on dhcp on pfsense. The PC aquired the IP succesfully as can be seen on the dhcp leases in pfsense.

But chrome does not call the CP login page.

Derelict

Is the AD DHCP server in the same subnet as your clients? If not you will have to use DHCP relay to get there and put the proper scope in the DHCP Server.

What happens if you go to http://10.10.10.10/ in chrome?

jetberrocal

My network is really simple.

My LAN is 192.168.56.x, 255.255.255.0
AD has static IP 192.168.56.10
pfsense has static IP 192.168.56.1
DHCP server sets:
from 192.168.56.100 to 192.168.56.254
DNS = 192.168.56.10
Gateway = 192.168.56.1

WAN is DHCP assigned by the Cable modem

Trying http://10.10.10.10 gives me "took too long to respond" error

ipfw zone list
Currently defined contexts and their members:
2: em1,

Shell Output - ipfw -x 2 show

65291 0 0 allow pfsync from any to any
65292 0 0 allow carp from any to any
65301 66 2424 allow ip from any to any layer2 mac-type 0x0806,0x8035
65302 0 0 allow ip from any to any layer2 mac-type 0x888e,0x88c7
65303 0 0 allow ip from any to any layer2 mac-type 0x8863,0x8864
65307 0 0 deny ip from any to any layer2 not mac-type 0x0800,0x86dd
65310 1569 143858 allow ip from any to table(100) in
65311 1456 434214 allow ip from table(100) to any out
65312 13 4327 allow ip from any to 255.255.255.255 in
65313 0 0 allow ip from 255.255.255.255 to any out
65314 0 0 pipe tablearg ip from table(3) to any in
65315 0 0 pipe tablearg ip from any to table(4) in
65316 0 0 pipe tablearg ip from table(3) to any out
65317 0 0 pipe tablearg ip from any to table(4) out
65318 878 108115 pipe tablearg ip from table(1) to any in
65319 858 899391 pipe tablearg ip from any to table(2) out
65532 282 14933 fwd 127.0.0.1,8002 tcp from any to any dst-port 80 in
65533 223 25436 allow tcp from any to any out
65534 2141 218858 deny ip from any to any
65535 0 0 allow ip from any to any

Shell Output - ipfw -x 2 table all list

–-table(1)---
192.168.56.100/32 mac 08:00:27:e8:c0:b4 2002
---table(2)---
192.168.56.100/32 mac 08:00:27:e8:c0:b4 2003
---table(100)---
192.168.56.1/32 0

Note: The table(100) has 192.168.56.1/32 instead of /24. I have not added any Allow IP nor Allow Host at the zone.

Gertjan

@jetberrocal:

Note: The table(100) has 192.168.56.1/32 instead of /24. I have not added any Allow IP nor Allow Host at the zone.

Table 100 contains the IP of the Captive Portal NIC.

@jetberrocal:

My network is really simple.

My LAN is 192.168.56.x, 255.255.255.0
AD has static IP 192.168.56.10
pfsense has static IP 192.168.56.1
DHCP server sets:
from 192.168.56.100 to 192.168.56.254
DNS = 192.168.56.10
Gateway = 192.168.56.1

Ok.
and what are these setting on the device that you used to :
@jetberrocal:

Trying http://10.10.10.10 gives me "took too long to respond" error

Who is this IP :
@jetberrocal:

–-table(1)---
192.168.56.100/32 mac 08:00:27:e8:c0:b4 2002
---table(2)---
192.168.56.100/32 mac 08:00:27:e8:c0:b4 2003
---table(100)---
192.168.56.1/32 0

?
Table 1 and 2 contain the "logged in users" - so "192.168.56.100" has been logged in successfully.

jetberrocal

The device I am using for testing is a Win 7 Pro attached to the AD, that is assign an IP by the DHCP. Since is only one the IP assigned is the first DHCP assign value which is 192.168.56.100.

The test device using Chrome sometimes shows the CP Login page and I can logging successfully. Thus the table shows in this occasion the device MACs.

BUT after successful login, the trigger page is shown, but no other page. The network is broken as if the login were unsuccessful but worst because the CP no longer is trigger. (I close the browser, and remove/delete the line from the CP status in Diagnostics)

I cant ping any Internet address not even resolve the addresses.

I thought this was because the DHCP server was in the AD and not the pfsense, but I turn off the dhcp in the AD and activated the dhcp in pfsense and still have the same bad behavior.

Gertjan

Consider this : if you address your browser to the right pace (the captive portal IP address) you should see the login page.
A DHCP server gives more as a IP address for a client-device.
It also hands over the gateway (and a DNS, etc), which should be pfSense, and not some other IP.

First the gateway is inaccessible, but a browser startup up will be 'captured' by the portal interface. Authentication will make the firewall in front of the portal transparent, and of you go …

What is the gateway that your server offers to its clients ?
What is the gateway your clients are using ?

jetberrocal

@Gertjan:

Consider this : if you address your browser to the right pace (the captive portal IP address) you should see the login page.
A DHCP server gives more as a IP address for a client-device.
It also hands over the gateway (and a DNS, etc), which should be pfSense, and not some other IP.

First the gateway is inaccessible, but a browser startup up will be 'captured' by the portal interface. Authentication will make the firewall in front of the portal transparent, and of you go …

What is the gateway that your server offers to its clients ?
What is the gateway your clients are using ?

Gateway = 192.168.56.1 (Set by DHCP clients, Set manually for static clients)
DNS = 192.168.56.10 (Set by DHCP, , Set manually for static clients)
pfsense = 192.168.56.1 (see attach png for pfsense dashboard)

ipconfig output:
Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : jetdom.local
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter
Physical Address. . . . . . . . . : 08-00-27-E8-C0-B4
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::9990:1817:5cc5:4efb%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.56.100(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, June 27, 2016 11:39:45 AM
Lease Expires . . . . . . . . . . : Tuesday, June 28, 2016 8:00:03 PM
Default Gateway . . . . . . . . . : 192.168.56.1
DHCP Server . . . . . . . . . . . : 192.168.56.1
DHCPv6 IAID . . . . . . . . . . . : 235405351
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-8B-C6-D4-08-00-27-E8-C0-B4

DNS Servers . . . . . . . . . . . : 192.168.56.10
NetBIOS over Tcpip. . . . . . . . : Enabled

pfsense_status.png_thumb

Gertjan

Humm.
Can't find anything wrong.

When your "192.168.56.100" is logged in - you can check that using the pfSEnse GUI Captive portal Satuts page - or inspecting table '100' using the ipfw show …. test - the barrier "capive-portal-pfsense" will be inexistent for that device ("192.168.56.100") - it's like the captive portal has been shut down for this device.
So : my question is : if you shut down the portal function, does the 'internet' access work ?

jetberrocal

I turn off the zone, and the Internet access started to work.

jetberrocal

To clarify. The pfsense IP is 192.168.56.1/24, but CP table(100) is register with 192.168.56.1/32. I dont know why /32.

Gertjan

@jetberrocal:

To clarify. The pfsense IP is 192.168.56.1/24,

pfSense has an IP on it's LAN - it is 192.168.56.1 (or written as 192.168.56.1/32 ;) )

@jetberrocal:

but CP table(100) is register with 192.168.56.1/32. I dont know why /32.

It means : This IP only - because the mask is '32'

edit : change the IPv4 firewall rule : remove the source (LAN net) and make it "all"

jetberrocal

Why pfsense IP is written as 192.168.56.1/32 when the LAN Interface is setup as 192.168.56.1/24

I can't select /32 when setting the interface.

I only have the default firewall rules. You mean to change the IP4 default rule?
What would be the implication?

pfsenseConsole.png_thumb