Is using the source IP address in generating the session ID by servers common? I've seen this behavior with a banking website. You visit the website with IP 18.104.22.168, SSL session is generated and used by the browser for SSL session resumption. Now if your IP changes to 22.214.171.124, and if you just refresh the page, the browser will error out. Firefox will complain about BAD_RECORD_MAC, chrome will just say ssl error. I still don't understand exactly why this happens, because according to the RFC if the session is not recognized a full handshake should be initiated but here everything just fails.
Using firefox with ssl session identifiers disabled doesn't have this problem which is why I think the server is using the source IP to create the session.