I hope you found this video helpful, please like, subscribe and click the notification bell so you won't miss future videos. Thanks for your support! ❤
Hi Ferds, thanks for the video, I'm network engineer from China, and I got few questions for you. Let's say my bgp stuck in active state. that at least means, when it was under connect state, it receives an explicit tcp failure message (conn refused or conn failed) not a timeout, and then it transits to active state. then if within the conn retry timer period, the tcp still cant come up it will fail back to connect state, and then it will loop btw connect and active states, am i right on this? or can you help to verify this in your environment? if firewall blocks tcp syn, or the return traffic or just an router in the path configured with an ACL blocking tcp 179, then what will happen, will this cause a connect to active transition? and is this consider as a tcp failure or tcp timeout (assume we dont know what is the exact reason why the tcp cant establish). so to make my question short, when i send a tcp syn to my peer, and there's no response or firewall is blocking, or high latency caused timeout, will these cases cause connect to active transition? and if check the RFC, it said that under connect state, if CR timer expires, it will remain at connect state, can you give an example? under what circumstances, the cr timer will expire under connect state? Subscribed and Thanks in advance
I hope you found this video helpful, please like, subscribe and click the notification bell so you won't miss future videos. Thanks for your support! ❤
yes, you're right. port 179 should not be blocked. 😊
Hi Ferds, thanks for the video, I'm network engineer from China, and I got few questions for you.
Let's say my bgp stuck in active state. that at least means, when it was under connect state, it receives an explicit tcp failure message (conn refused or conn failed) not a timeout, and then it transits to active state.
then if within the conn retry timer period, the tcp still cant come up it will fail back to connect state, and then it will loop btw connect and active states, am i right on this? or can you help to verify this in your environment?
if firewall blocks tcp syn, or the return traffic or just an router in the path configured with an ACL blocking tcp 179, then what will happen, will this cause a connect to active transition? and is this consider as a tcp failure or tcp timeout (assume we dont know what is the exact reason why the tcp cant establish).
so to make my question short, when i send a tcp syn to my peer, and there's no response or firewall is blocking, or high latency caused timeout, will these cases cause connect to active transition?
and if check the RFC, it said that under connect state, if CR timer expires, it will remain at connect state, can you give an example? under what circumstances, the cr timer will expire under connect state?
Subscribed and Thanks in advance