Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 27 subscribers
  • Views 3522 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Could not associate packet to any connection in Captive Portal

Franchesco Alba

Hi,

 

We've found a problem witch captive portal from a branch who use MPLS to communicate. 

This is the log:

2018-05-08 18:27:38
Invalid Traffic
Denied
  
0
    
172.16.0.254
192.168.53.5
8090
49867
TCP
0
01001
Open PCAP
Could not associate packet to any connection.

 

The IP 172.16.0.254 is the Sophos Lan IP. The 192.168.53.5 is the client who tried to authenticated with captive portal. 

When the client tries to access a website, the access is asked for auth in captive portal. Then the user click in login and browsers redirects to 172.16.0.254:8090, then the connection is refused. 

 

I don't know to resolve the "Could not associate packet to any connection". We created the rule Bypass Stateful Inspection Between Networks between the 172.16.0.0/16 and 192.168.0.0/16 and the problem persist. 



This thread was automatically locked due to age.