It's like the port is not open on the interface (443)

Le 2018-02-18 à 22:19, E.P. a écrit :
>
> Here it is, Fabrice
>
> 10.0.254.3 is the WiFi client and 172.16.0.222 is PF.
>
> Tcpdump.pcap is attached and it is made right on PF
>
> The second capture is made on the laptop connected to guest WiFi.
>
> It contains pings to PF but all TCP SYN requests all are answered with
> RST.
>
>  
>
> Eugene
>
>  
>
> *From:*Durand fabrice via PacketFence-users
> [mailto:[email protected]]
> *Sent:* Sunday, February 18, 2018 10:51 AM
> *To:* [email protected]
> *Cc:* Durand fabrice <[email protected]>
> *Subject:* Re: [PacketFence-users] Access to PF captive portal is blocked
>
>  
>
> Hello Eugene,
>
> do you have the capture ?
>
> Regards
> Fabrice
>
> Le 2018-02-15 à 23:12, E.P. via PacketFence-users a écrit :
>
>     Hi Fabrice,
>
>     I dare sending it again believing my previous email fell into cracks.
>
>     Can you please advise what could be wrong (see below)
>
>      
>
>     Eugene
>
>      
>
>      
>
>     *From:* E.P. [mailto:[email protected]]
>     *Sent:* Wednesday, February 14, 2018 1:08 AM
>     *To:* [email protected]
>     <mailto:[email protected]>
>     *Subject:* Access to PF captive portal is blocked
>
>      
>
>     Hello folks,
>
>     I really hope someone who ran into a similar problem will shed
>     some light.
>
>     Feeling bad we don’t hear anything from Fabrice or someone from
>     inverse.
>
>     I have an out-of-band deployment of PF and my WiFi client gets
>     connected and redirected to PF
>
>     I see redirects by capturing the traffic on PF by tcpdump.
>
>     But… I see that PF sends TCP resets even for TCP SYN packet coming
>     from the client.
>
>     It seems to me it is just iptables firewall that blocks it.
>
>     Why ? Where am I supposed to enter those IP addresses that are
>     allowed to go through captive portal registration?
>
>     I do allow PF IP address in the pre-authorization access list and
>     my ping to FQDN of PF succeeds normally.
>
>     It is only HTTP(s) doesn’t go through.
>
>     Even manually entered URL in the client browser doesn’t open up
>     any page, i.e. https://pf.blabla.com/captive-portal or
>     https://172.16.0.222/captive-portal
>
>      
>
>     Eugene
>
>
>
>
>     
> ------------------------------------------------------------------------------
>
>     Check out the vibrant tech community on one of the world's most
>
>     engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
>
>
>     _______________________________________________
>
>     PacketFence-users mailing list
>
>     [email protected]
>     <mailto:[email protected]>
>
>     https://lists.sourceforge.net/lists/listinfo/packetfence-users
>
>  
>

-- 
Fabrice Durand
[email protected] ::  +1.514.447.4918 (x135) ::  www.inverse.ca
Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and PacketFence 
(http://packetfence.org) 

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to