Jump to content
Not connected, Your IP: 35.173.48.224
Sign in to follow this  
FPyro

Pls help, strange logs!

Recommended Posts

Hey there!

I have this really strange problem, that I don't lose the connection, but that my upload/download drops to 0 for like 10-15 seconds, interrupting my skype calls and gaming for example.

Here are the logs, hope they are of any use.

Would be awesome if you had a solution. Seems to be happening mostly on NL GBbit servers.

I don't think my ISP is to blame in the least for I almost never have any issues with them, perfectly stable ping, very high connection speed (100Mbit/s), no shaping on any protocoll/port!

Thanks a lot in advance.

01.09.2012 - 18:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #3577847 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 18:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #3577845 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 18:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #3577846 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 18:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #3577848 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 18:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #3577849 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 18:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #3577850 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 18:39 VERIFY OK: depth=1, /C=IT/ST=IT/L=Perugia/O=airvpn.org/CN=airvpn.org_CA/emailAddress=info@airvpn.org

01.09.2012 - 18:39 VERIFY OK: nsCertType=SERVER

01.09.2012 - 18:39 VERIFY OK: depth=0, /C=IT/ST=IT/L=Perugia/O=airvpn.org/CN=server/emailAddress=info@airvpn.org

01.09.2012 - 18:39 Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key

01.09.2012 - 18:39 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication

01.09.2012 - 18:39 Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key

01.09.2012 - 18:39 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication

01.09.2012 - 18:39 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA

01.09.2012 - 19:39 TLS: tls_process: killed expiring key

01.09.2012 - 19:39 VERIFY OK: depth=1, /C=IT/ST=IT/L=Perugia/O=airvpn.org/CN=airvpn.org_CA/emailAddress=info@airvpn.org

01.09.2012 - 19:39 VERIFY OK: nsCertType=SERVER

01.09.2012 - 19:39 VERIFY OK: depth=0, /C=IT/ST=IT/L=Perugia/O=airvpn.org/CN=server/emailAddress=info@airvpn.org

01.09.2012 - 19:39 Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key

01.09.2012 - 19:39 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication

01.09.2012 - 19:39 Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key

01.09.2012 - 19:39 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication

01.09.2012 - 19:39 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA

01.09.2012 - 20:16 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1415390 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:16 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1415391 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:16 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1415392 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:16 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1415393 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1456916 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1486330 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1486334 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1486336 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1486338 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1486341 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1486342 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1486344 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1486347 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1486348 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1486350 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1561546 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1561547 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1561548 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1561549 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1561550 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1561551 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1561552 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1561553 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1561554 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1561557 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1561560 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1561563 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1561564 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1561566 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1561567 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1561569 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1561570 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1561572 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1561573 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1561576 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1561577 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1561578 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1561579 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1561580 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:17 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #1561581 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:19 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2013120 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:19 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2013121 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:19 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2013122 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:19 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2013123 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:19 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2013124 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:19 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2013125 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:19 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2013126 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:19 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2013127 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:19 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2013128 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:19 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2013129 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:19 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2013130 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:19 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2013131 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:19 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2013132 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:19 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2013134 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:19 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2013135 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:19 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2013137 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:19 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2013138 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:19 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2013139 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:19 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2013140 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:19 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2013141 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:19 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2013143 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:19 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2013144 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:19 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2013145 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:19 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2013146 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:24 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2599415 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:24 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2599416 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:24 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2599417 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:24 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2599418 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:24 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2599419 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2754808 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2754809 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2754810 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2754811 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2754812 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2754813 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2754814 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2754815 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2754816 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2754817 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2754818 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2754819 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2754820 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2754821 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2754822 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2754823 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2795079 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2795080 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2795081 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2795082 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2795083 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2795084 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2795085 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2795086 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2795087 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2822945 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2822946 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2822947 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2822948 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2822949 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2822950 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:26 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #2822951 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

01.09.2012 - 20:28 Disconnecting...

01.09.2012 - 20:28 SIGTERM received, sending exit notification to peer

01.09.2012 - 20:28 TCP/UDP: Closing socket

01.09.2012 - 20:28 Disconnected.

01.09.2012 - 20:28 C:\WINDOWS\system32\route.exe DELETE 10.4.0.1 MASK 255.255.255.255 10.4.0.113

01.09.2012 - 20:28 Route deletion via IPAPI succeeded [adaptive]

01.09.2012 - 20:28 C:\WINDOWS\system32\route.exe DELETE 95.211.191.33 MASK 255.255.255.255 192.168.178.1

01.09.2012 - 20:28 Route deletion via IPAPI succeeded [adaptive]

01.09.2012 - 20:28 C:\WINDOWS\system32\route.exe DELETE 0.0.0.0 MASK 128.0.0.0 10.4.0.113

01.09.2012 - 20:28 Route deletion via IPAPI succeeded [adaptive]

01.09.2012 - 20:28 C:\WINDOWS\system32\route.exe DELETE 128.0.0.0 MASK 128.0.0.0 10.4.0.113

01.09.2012 - 20:28 Route deletion via IPAPI succeeded [adaptive]

01.09.2012 - 20:28 Closing TUN/TAP interface

01.09.2012 - 20:28 SIGTERM[hard,] received, process exiting

01.09.2012 - 20:28 Login...

01.09.2012 - 20:28 Login success.

01.09.2012 - 20:29 Contacting service...

01.09.2012 - 20:29 Connecting...

01.09.2012 - 20:29 OpenVPN 2.2.2 Win32-MSVC++ [sSL] [LZO2] [PKCS11] built on Dec 15 2011

01.09.2012 - 20:29 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables

01.09.2012 - 20:29 LZO compression initialized

01.09.2012 - 20:29 Control Channel MTU parms [ L:1558 D:138 EF:38 EB:0 ET:0 EL:0 ]

01.09.2012 - 20:29 Socket Buffers: R=[8192->8192] S=[8192->8192]

01.09.2012 - 20:29 Data Channel MTU parms [ L:1558 D:1450 EF:58 EB:135 ET:0 EL:0 AF:3/1 ]

01.09.2012 - 20:29 Local Options hash (VER=V4): '22188c5b'

01.09.2012 - 20:29 Expected Remote Options hash (VER=V4): 'a8f55717'

01.09.2012 - 20:29 UDPv4 link local: [undef]

01.09.2012 - 20:29 UDPv4 link remote: 31.193.12.98:443

01.09.2012 - 20:29 TLS: Initial packet from 31.193.12.98:443, sid=3bc5b2f5 82e58526

01.09.2012 - 20:29 VERIFY OK: depth=1, /C=IT/ST=IT/L=Perugia/O=airvpn.org/CN=airvpn.org_CA/emailAddress=info@airvpn.org

01.09.2012 - 20:29 VERIFY OK: nsCertType=SERVER

01.09.2012 - 20:29 VERIFY OK: depth=0, /C=IT/ST=IT/L=Perugia/O=airvpn.org/CN=server/emailAddress=info@airvpn.org

01.09.2012 - 20:29 Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key

01.09.2012 - 20:29 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication

01.09.2012 - 20:29 Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key

01.09.2012 - 20:29 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication

01.09.2012 - 20:29 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA

01.09.2012 - 20:29 [server] Peer Connection Initiated with 31.193.12.98:443

01.09.2012 - 20:29 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)

01.09.2012 - 20:29 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 10.4.0.1,comp-lzo no,route 10.4.0.1,topology net30,ping 10,ping-restart 120,ifconfig 10.4.2.62 10.4.2.61'

01.09.2012 - 20:29 OPTIONS IMPORT: timers and/or timeouts modified

01.09.2012 - 20:29 OPTIONS IMPORT: LZO parms modified

01.09.2012 - 20:29 OPTIONS IMPORT: --ifconfig/up options modified

01.09.2012 - 20:29 OPTIONS IMPORT: route options modified

01.09.2012 - 20:29 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified

01.09.2012 - 20:29 ROUTE default_gateway=192.168.178.1

01.09.2012 - 20:29 TAP-WIN32 device [Local Area Connection 3] opened: \\.\Global\{2CD8A934-2B91-4638-B55A-E353FF6A3209}.tap

01.09.2012 - 20:29 TAP-Win32 Driver Version 9.9

01.09.2012 - 20:29 TAP-Win32 MTU=1500

01.09.2012 - 20:29 Notified TAP-Win32 driver to set a DHCP IP/netmask of 10.4.2.62/255.255.255.252 on interface {2CD8A934-2B91-4638-B55A-E353FF6A3209} [DHCP-serv: 10.4.2.61, lease-time: 31536000]

01.09.2012 - 20:29 Successful ARP Flush on interface [34] {2CD8A934-2B91-4638-B55A-E353FF6A3209}

01.09.2012 - 20:29 TEST ROUTES: 2/2 succeeded len=1 ret=1 a=0 u/d=up

01.09.2012 - 20:29 C:\WINDOWS\system32\route.exe ADD 31.193.12.98 MASK 255.255.255.255 192.168.178.1

01.09.2012 - 20:29 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=10 and dwForwardType=4

01.09.2012 - 20:29 Route addition via IPAPI succeeded [adaptive]

01.09.2012 - 20:29 C:\WINDOWS\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 10.4.2.61

01.09.2012 - 20:29 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4

01.09.2012 - 20:29 Route addition via IPAPI succeeded [adaptive]

01.09.2012 - 20:29 C:\WINDOWS\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 10.4.2.61

01.09.2012 - 20:29 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4

01.09.2012 - 20:29 Route addition via IPAPI succeeded [adaptive]

01.09.2012 - 20:29 C:\WINDOWS\system32\route.exe ADD 10.4.0.1 MASK 255.255.255.255 10.4.2.61

01.09.2012 - 20:29 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4

01.09.2012 - 20:29 Route addition via IPAPI succeeded [adaptive]

01.09.2012 - 20:29 Initialization Sequence Completed

01.09.2012 - 20:29 Starting Management Interface...

01.09.2012 - 20:29 Checking...

01.09.2012 - 20:30 Retrieve statistics...

01.09.2012 - 20:30 Replay-window backtrack occurred [1]

01.09.2012 - 20:30 Connected.

01.09.2012 - 20:30 Replay-window backtrack occurred [5]

01.09.2012 - 20:30 Replay-window backtrack occurred [6]

01.09.2012 - 20:31 Replay-window backtrack occurred [7]

01.09.2012 - 20:31 Replay-window backtrack occurred [12]

01.09.2012 - 20:31 Replay-window backtrack occurred [16]

Share this post


Link to post

@FPyro

Hello!

The logs show that either duplicate packets are being received or packets are arriving out of correct order. Seeing the last lines of the logs ("Replay-window backtrack occurred") the second option is more probable. If the problem was born only recently, maybe it is just a temporary peering issue between our servers and your ISP. Rarely it may also be a symptom of a defective Ethernet cable or network card, router issues or WiFi problems. Please try connections to VPN servers' TCP ports to mitigate the problem and also test different servers. Finally, just in case, if you have the chance, try to replace momentarily cable and router and if possible also the computer. Change only one item at a time to determine if the problem is in the hardware.

Kind regards

Share this post


Link to post

Hi!

Thanks for your reply.

I can assure you that my hardware is perfectly alright, no problems with the router or network card or cable and I don't use WiFi.

Using TCP to connect might solve the "problem", but I would like to avoid that at all cost, since I sometimes use the VPN for gaming and using Skype and TCP increases ping and delay and drastically decreases speeds.

Usually I disconnect before gaming, but I was running some bandwidth intensive application in the background as well. Could that have something to do with it? It never does when I'm not connected, so it has to do something with openVPN or the server, right?

What do you mean by "temporary perring issue between our servers and your ISP" though?

Could it also have something to do with an outside attack or portscan, probe, whatever they do?

And what is this replay thing anyway? Can it be disabled?

Thank you

Share this post


Link to post

Hi!

Thanks for your reply.

I can assure you that my hardware is perfectly alright, no problems with the router or network card or cable and I don't use WiFi.

Using TCP to connect might solve the "problem", but I would like to avoid that at all cost, since I sometimes use the VPN for gaming and using Skype and TCP increases ping and delay and drastically decreases speeds.

Hello!

We apologize for the delay, your issue deserved an extensive and careful evaluation.

If TCP reduces your speed drastically in comparison with UDP (let's say more than 15%) then there may be a high rate of packet loss, unfortunately, or a replay attack (see below). With TCP, each lost packet is properly resent thanks to its extensive error-correction implementation, but this is of course not the best solutions for performance of some applications (VoIP, online gaming, real A/V streaming...).

Usually I disconnect before gaming, but I was running some bandwidth intensive application in the background as well. Could that have something to do with it? It never does when I'm not connected, so it has to do something with openVPN or the server, right?

It seems really related to the OpenVPN connection, see below.

What do you mean by "temporary perring issue between our servers and your ISP" though?

You might like to read here:

http://en.wikipedia.org/wiki/Peering

Could it also have something to do with an outside attack or portscan, probe, whatever they do?

And what is this replay thing anyway? Can it be disabled?

A replay attack is a form of network attack in which a valid data transmission is maliciously or fraudulently repeated or delayed. This is carried out either by the originator (of course not in our case!!!) or by an adversary who intercepts the data and retransmits it, possibly as part of a masquerade attack by IP packet substitution. OpenVPN will reject correctly the fraudulent packets and no injection is possible. However the attack, if well organized, will slow down considerably your VPN connections. If your problem occurs on EVERY Air server, then it's extremely unlikely that you are the target of a replay attack, UNLESS your adversary has the ability to monitor your own ISP line.

However, the "Authenticate/Decrypt packet error: bad packet ID (may be a replay)" log entries do really suggest a replay attack against you even before the connection to our servers. If this an attack, then the adversary is not attacking our servers in general, he/she is attacking you specifically.

About the "Replay-window backtrack occurred", this is the consequence of the problem. OpenVPN writes in the log this event. Please read here. Although it is not 100% sure, it might mitigate your problem without having to use TCP:

http://openvpn.net/archive/openvpn-users/2004-09/msg00068.html

It is not sure that the above will improve your connectivity for online gaming, you will have to test various parameters. But it is sure that it may lower your security if you are under attack. The risk is forcing OpenVPN to accept fraudulent packets as valid packets. The directive to set the n parameter is replay-window in your .ovpn configuration file.

See the OpenVPN manual:

--replay-window n [t]

Use a replay protection sliding-window of size n and a time window of t seconds.

By default n is 64 (the IPSec default) and t is 15 seconds.

This option is only relevant in UDP mode, i.e. when either --proto udp is specifed, or no --proto option is specified.

When OpenVPN tunnels IP packets over UDP, there is the possibility that packets might be dropped or delivered out of order. Because OpenVPN, like IPSec, is emulating the physical network layer, it will accept an out-of-order packet sequence, and will deliver such packets in the same order they were received to the TCP/IP protocol stack, provided they satisfy several constraints.

(a) The packet cannot be a replay (unless --no-replay is specified, which disables replay protection altogether).

(B) If a packet arrives out of order, it will only be accepted if the difference between its sequence number and the highest sequence number received so far is less than n.

© If a packet arrives out of order, it will only be accepted if it arrives no later than t seconds after any packet containing a higher sequence number.

If you are using a network link with a large pipeline (meaning that the product of bandwidth and latency is high), you may want to use a larger value for n. Satellite links in particular often require this.

If you run OpenVPN at --verb 4, you will see the message "Replay-window backtrack occurred [x]" every time the maximum sequence number backtrack seen thus far increases. This can be used to calibrate n.

There is some controversy on the appropriate method of handling packet reordering at the security layer.

Namely, to what extent should the security layer protect the encapsulated protocol from attacks which masquerade as the kinds of normal packet loss and reordering that occur over IP networks?

The IPSec and OpenVPN approach is to allow packet reordering within a certain fixed sequence number window.

OpenVPN adds to the IPSec model by limiting the window size in time as well as sequence space.

OpenVPN also adds TCP transport as an option (not offered by IPSec) in which case OpenVPN can adopt a very strict attitude towards message deletion and reordering: Don't allow it. Since TCP guarantees reliability, any packet loss or reordering event can be assumed to be an attack.

In this sense, it could be argued that TCP tunnel transport is preferred when tunneling non-IP or UDP application protocols which might be vulnerable to a message deletion or reordering attack which falls within the normal operational parameters of IP networks.

So I would make the statement that one should never tunnel a non-IP protocol or UDP application protocol over UDP, if the protocol might be vulnerable to a message deletion or reordering attack that falls within the normal operating parameters of what is to be expected from the physical IP layer. The problem is easily fixed by simply using TCP as the VPN transport layer.

Kind regards

Share this post


Link to post

Hello!

Thank you very much for your detailed answer.

Yes, TCP does indeed reduce my speed by a HUGE amount.

On Cassio for example I just performed a speedtest 2x getting about 36Mbit/s download and 5Mbit/s upload speed.

Then I reconnected on the same port (443) with TCP and the speed dropped to 11Mbit/s down and 1.7Mbit/s upload speed!

But packet loss is not the case as far as I can tell because performing the test on pingtest.net with UDP protocol, there is 0% packets loss.

Well, I don't care much about that, seeing that UDP works fine... except for this attack issue.

The issue does in fact not happen on every server! It's very obvious when using NL Gbit/s servers. Checking my logs now, there are hours of flawless connectivity with Cassio.

Of course I wouldn't want to change any parameters if it meant being more vulnerable to certain attacks.

Have a nice day

Share this post


Link to post

Hello!

Thank you very much for your detailed answer.

Yes, TCP does indeed reduce my speed by a HUGE amount.

On Cassio for example I just performed a speedtest 2x getting about 36Mbit/s download and 5Mbit/s upload speed.

Then I reconnected on the same port (443) with TCP and the speed dropped to 11Mbit/s down and 1.7Mbit/s upload speed!

But packet loss is not the case as far as I can tell because performing the test on pingtest.net with UDP protocol, there is 0% packets loss.

Well, I don't care much about that, seeing that UDP works fine... except for this attack issue.

The issue does in fact not happen on every server! It's very obvious when using NL Gbit/s servers. Checking my logs now, there are hours of flawless connectivity with Cassio.

Of course I wouldn't want to change any parameters if it meant being more vulnerable to certain attacks.

Have a nice day ;)

Hello!

Can you please tell us, at your convenience, how the "Authenticate/Decrypt packet error: bad packet ID" problem was solved on your system? Did it disappear by itself or did you do something?

Kind regards

Share this post


Link to post

Hi!

As far as I can tell the problem you refer to is solved. I didn't notice any errors of this kind lately whenever I checked the logs. I've not been checking the logs on a daily basis though so it still might have come up occasionally.

I did indeed change some things:

I used to have the same IP from my provider for a long time, but now I turn of my router for longer periods of time to have the lease-time expire to get a new ip almost every day.

Also, I recently installed the new 2.3 Beta version of OpenVPN.

When using UDP on NL/DE servers I still have sudden drops in (especially) upload speed for a few seconds with the upload being literally zero for that time.

Now, using the new Herculis, everything seems just absolutely perfect

Thank you.

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Security Check
    Play CAPTCHA Audio
    Refresh Image
Sign in to follow this  

×
×
  • Create New...