TLS Error: incoming packet authentication failed from
-
I read about float too but it looks more like covering the symptom than fixing the issue.
I will wait with that one and see if any of the OPENVPN experts maybe stops in and has a fix for the base issue than just suppressing the issue warning.
Hopefully a OPENVPN expert shows up.
-
Still having found an answer to this one, if I figure it out I will post a solution.
If any of your have an answer, I am still looking.
I know it isn't a hard down, but I like having a clean log,
-
Supposedly it means someone is trying a replay attack on your VPN. That I'm sure you knew.
I have seen that error, but the day I saw It in my logs I was using my VPN down near the White House.
Maybe thats just nothing, or maybe its something. I don't know.
I haven't seen that error again but I haven't fired up the VPN in DC since then either.
I suppose to reproduce the error I could go stand outside the Pentagon on VPN and see if it pops up again. ::) -
I suppose to reproduce the error I could go stand outside the Pentagon on VPN and see if it pops up again. ::)
You're on the "no fly" list now, so I guess that might take some time to get back there. :P
-
I wouldn't need to fly there. I can take a walk there… Or ride a bicycle. But the Metro is quicker.
Now, the real question is why the heck would I want to spend more time there than absolutely necessary?
I do like Dupont Circle from time to time, but its hardly Gangnam. DC is boring.
(I was being FORCED to parade around museums AGAIN by yet ANOTHER visiting friend or I wouldn't have been there.)
It just hit me when I checked my logs to compare notes with Honeybadger that the only time I've seen that error I was in DC.
If someone did manage to overheat a mainframe and chew through that particular VPN they would be rewarded with a tunnel that just goes back to the internet and no where else. Quite an accomplishment. I will be turning it on again next time I go to see if it happens again though.