{"id":258,"date":"2009-06-30T09:07:28","date_gmt":"2009-06-30T09:07:28","guid":{"rendered":"https:\/\/fir3netwp.gmsrrpobkbd.com\/2009\/06\/30\/bgp\/"},"modified":"2021-07-24T19:04:10","modified_gmt":"2021-07-24T19:04:10","slug":"bgp","status":"publish","type":"post","link":"https:\/\/www.fir3net.com\/Firewalls\/Check-Point\/bgp.html","title":{"rendered":"Invalid MD5 digest – BGP Traffic Through Check Point"},"content":{"rendered":"

Issue<\/strong><\/span><\/p>\n

When allowing eBGP traffic through a Check Point Firewall you may receive the following error message on your BGP peered routers. (This error may occur at the point of pushing a policy to your Check Point Firewall),<\/span><\/p>\n

TCP-6-BADAUTH: Invalid MD5 digest from [Source IP]:[Source Port] to [Dest IP]:179<\/strong><\/span><\/p>\n

Solution<\/span><\/strong><\/p>\n

This is down to the Check Point State Table and the TCP sequence number of the BGP Traffic changing at the point of policy push.<\/span><\/p>\n

To prevent this occurring you will need to change the following settings,<\/span><\/p>\n