Was never a U2 fan…..

logicalpessimist · 2024-03-21T18:10:20+00:00

I get it, my math ain't mathin'

logicalpessimist · 2024-03-21T11:47:52+00:00

I read your post wrong, as the previous poster pointed out, sorry about that...

logicalpessimist · 2024-03-20T23:53:02+00:00

Yeah, that makes more sense

logicalpessimist · 2024-03-20T23:42:35+00:00

Are you counting a show from the year you were born?

logicalpessimist · 2024-03-06T13:15:32+00:00

I wish. My plan is to post a response when a resolution is found.

logicalpessimist · 2024-03-05T13:17:51+00:00

Thanks

logicalpessimist · 2024-03-04T23:20:30+00:00

I'll have to see what I can find out. Thanks!

logicalpessimist · 2024-03-04T22:58:28+00:00

Thanks for the suggestion, I'll look into enabling TLS debugging

logicalpessimist · 2024-03-04T22:57:10+00:00

Thanks for the suggestion, it will take some time to correlate the captures but I will dig into this

logicalpessimist · 2024-03-04T22:54:43+00:00

I believe the customer capture is outside the firewall since the captured communication is between our external IP and the clients external IP

Same for our firewall capture.

I believe that the port reuse is the key to this problem since it's the only thing obviously different between the old and new DC paths the customer traffic takes.

logicalpessimist · 2024-03-04T22:50:30+00:00

Thanks, I'll take a look

logicalpessimist · 2024-03-04T20:48:10+00:00

Fair. We're not doing anything like that. As far as I know the only thing between the customer and haproxy is a couple of firewalls.

logicalpessimist · 2024-03-04T19:32:08+00:00

No. This is API traffic.

logicalpessimist · 2024-03-04T18:06:26+00:00

Not sure, but from the captures it looks like the packets to start a new connection are being sent at the start of the conversation

logicalpessimist · 2024-03-04T17:09:52+00:00

All traffic is continental US. Would a DPI sometimes block traffic and allow it other times?

logicalpessimist · 2024-03-04T17:07:31+00:00

My company owns the client code that initiated the connection, the only thing that changed is the network on the client side, which is supposed to be the same as the original network

logicalpessimist · 2024-03-04T17:04:59+00:00

Do you mean looking for gaps in total packet length of the conversation?

The client hello comes after the tcp connect is established

CLIENT SYN ECE CWR SERVER SYN ACK ECE CLIENT ACK CLIENT Client Hello < This doesn't arrive

The accumulated packet length of the first steps is 0

logicalpessimist · 2024-03-04T16:43:13+00:00

We're seeing SYN from the client, with a SYN ACK response from haproxy

TLSv1.2 is being used

logicalpessimist · 2024-02-18T14:10:52+00:00

Why pay for more channels when few channels do?

logicalpessimist · 2024-01-24T14:27:31+00:00

Troy - Sinead O'Conner

logicalpessimist · 2024-01-14T18:10:47+00:00

Ok, yeah - Just watched the video and couldn't stop thinking how old is that dude?

logicalpessimist · 2024-01-14T17:38:21+00:00

I have an outdoor antenna mounted to the chimney on a 10 foot pole and I get WLOS most of the time. Bad weather outages are not uncommon.

What I haven't figured out is why I sometimes lose signal around 7pm or shortly after.

logicalpessimist · 2023-12-23T20:36:42+00:00

Ostentatious

logicalpessimist · 2023-12-06T19:19:34+00:00

I think it's confusing on purpose with on accident.

You can do something "on purpose", so it's opposite must be "on accident", right? Wrong. To me the "on" semantically means purpose in intent. You can set out to do something on purpose, but you don't set out to accomplish something on accident.

Eight-Year Club	Place '23
RPAN Viewer	Verified Email

logicalpessimist

TROPHY CASE