The session browser logs display BGP port 179 sessions trying to connect to the same destination peer address, in 2 different zones, the correct zone and the captive portal zone, is this normal? We are not using Captive Portal, but I do see it enabled under Device>User Identification>Captive Portal Settings.
Is BGP being used on the internal network?
This is likely caused by User Identification being enabled on the zone where your BGP isset up. if this zone does not need to have inbound connections matched against user-ID (typically the untrust or some kind of external zone), you can disable that option in the zone configuration
It is normal. Captive portal as destination zone in session browser even if it is disabled.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!
The Live Community thanks you for your participation!