Sorry to be off topic but does anybody know of a trick to get back into an instagram account? I was stupid forgot my login password. I would appreciate any help you can give me!
@Simon Phillip Thanks so much for your reply. I got to the site on google and Im waiting for the hacking stuff atm. Takes a while so I will reply here later with my results.
Not clear why IDLE state refuses "All TCP connections" it is a little contradictory (at least for me) when in this state is supposed that idle state will listen for TCP connections. Could you please clarify ? in advance thank you!!
my understanding is that it will refuse all TCP connections up until there is a start event triggered automatically or manually. After the start event, it will initiate TCP connections to the BGP peer it is trying to establish adjacencies with.
I dont understand why R1 sends a notification messages, while R2 sends a keepalive. How does R2 thinks his config is fine while it is not matching the one from his neighbor. I would expect both systems to send a notification. I dont understand how one side sees everything as fine while the other side sees a problem.
+Mauricio Quesada Because the information sent to R1, from R2, did not match the configuration that R1 was told it should expect from R2. Inside the OPEN sent from R1 was R1's RID, BGP version, ASN, and Hold time. Inside the OPEN sent from R2 is R2's RID, BGP version, ASN, and Hold Time. So R2 receives R1's OPEN (with R1's RID, BGP version, ASN, and Hold Time) and has no issues with it. The reason is because the config that R1 sent TO R2 matched the neighbor statements, no duplicate RID, etc. On the other hand, R1 looked at R1's OPEN and and found a conflict. The neighbor statement on R1 said "neighbor R2 remote-as x" while the ASN that R2 reported to be in was different. So R1 sends the notification.
After getting confused with multiple articles and videos, finally someone who can explain it clearly
Someone has finally explained this very well. Thank you ipexert.
Thanks for the great info.. Appreciate your time sir..
Simply Awesome!!!! Thank You..
Excellent Video Thanks for the quality content.
very nice video, well explained with pcap. Thank you
Thanks JP, the best video on BGP state machine so far.
Sorry to be off topic but does anybody know of a trick to get back into an instagram account?
I was stupid forgot my login password. I would appreciate any help you can give me!
@Rhys Dominick Instablaster :)
@Simon Phillip Thanks so much for your reply. I got to the site on google and Im waiting for the hacking stuff atm.
Takes a while so I will reply here later with my results.
@Simon Phillip it did the trick and I now got access to my account again. Im so happy:D
Thanks so much, you saved my ass !
@Rhys Dominick happy to help =)
Nice video thanks for sharing
Excellent video. Congrats, well done!
JP, YOU KNOW YOUR STUFF BRO!
until what time notification message will be sent ?
Very well explained ...Thanks a lot .. :).
Outstanding. I like the use of WireShark to bring things from an academic concept to how this applies as a real world application.
Thanks JP for this nice vedio....
Not clear why IDLE state refuses "All TCP connections" it is a little contradictory (at least for me) when in this state is supposed that idle state will listen for TCP connections. Could you please clarify ? in advance thank you!!
my understanding is that it will refuse all TCP connections up until there is a start event triggered automatically or manually. After the start event, it will initiate TCP connections to the BGP peer it is trying to establish adjacencies with.
I dont understand why R1 sends a notification messages, while R2 sends a keepalive. How does R2 thinks his config is fine while it is not matching the one from his neighbor. I would expect both systems to send a notification. I dont understand how one side sees everything as fine while the other side sees a problem.
+Mauricio Quesada Because the information sent to R1, from R2, did not match the configuration that R1 was told it should expect from R2. Inside the OPEN sent from R1 was R1's RID, BGP version, ASN, and Hold time. Inside the OPEN sent from R2 is R2's RID, BGP version, ASN, and Hold Time. So R2 receives R1's OPEN (with R1's RID, BGP version, ASN, and Hold Time) and has no issues with it. The reason is because the config that R1 sent TO R2 matched the neighbor statements, no duplicate RID, etc. On the other hand, R1 looked at R1's OPEN and and found a conflict. The neighbor statement on R1 said "neighbor R2 remote-as x" while the ASN that R2 reported to be in was different. So R1 sends the notification.
Not a single Dislike???
Example of perfect video
Awesome video, BGP is making more and more sense lol.
This was very helpful.
Thanks
the best
good explanation
Badre Hamdane
Badre Hamdane