Jump to content

KayOneX-24

Members
  • Content Count

    294
  • Joined

  • Last visited

  • Days Won

    6

Reputation Activity

  1. Like
    KayOneX-24 got a reaction from Sgt-Greco in R1 DumaOS Briefly Delayed   
    Is the update for the R1 available yet?
    No? It's already been a while since April 16th. I'm not kidding guys.
    Let's face the state we loyal customers are in.
    In my opinion, there won't be an update for the R1 any time soon.
    Release dates have been missed with vague arguments about new release dates.
    And even bugfixes for the R1 haven't been released since more than 2 years.
    We were promised a lot of features for the R1, such as anti-jitter/spike.
     
    Maybe this whole "Router Revolution" advertising was just that - marketing!?
     
    Take a look at Netgear. Even the XR500 lacks the features from above and even there
    hasn't been an update recently bringing revolutionary features to the router. Mostly bugfixes.
     
    Maybe the DumaOS isn't exactly that what Netduma had expected.
    Maybe this is due to hardware limitations or some other issues.
     
    I think for me it's time to leave this community for a longer period of time and to turn to other gaming routers meaningwhile.
     
    I still hope that all of you get the desired update for the R1 one day.
     
    For me personally, I don't care anymore... Sadly!
     
    A little more transparancy of Netduma could help quite a bit and ensure that the community stays strong in supporting Netduma in the future. We were the paying customers that had made Netduma what they are today.
    I'm very disappointed of them.
  2. Like
    KayOneX-24 got a reaction from JOE1305 in Woran liegt das? Ww2   
    @Toni:
    Leider ist es so, dass alle Mühe für Call Of Duty umsonst ist!
    Ich habe es über viele Jahre versucht, meine Verbindung zu optimieren.
    Ich habe sogar teuer den neuen XR500 gekauft.
    Aber... Es bringt einfach wenig bei Call Of Duty.
    Du kannst die Verbindung optimieren, dass du keinen Bufferbloat-Effekt hast.
    Du kannst deine Verbindung auch von deinem ISP optimieren lassen.
    Und du kannst den Geofilter nutzen, um die Verbindung nochmals zu optimieren.
    All das, und so schreibt es schon der Joe, bringt dir gar nichts, wenn ein Spieler
    mit schlechter Verbindung deinem Spiel beitritt. Dann nämlich versucht das Spiel,
    deine Leitung zu kompensieren. Es gibt unzählige Beispiele dafür im Internet bei
    YouTube.
     
    Darum habe ich vor einigen Monaten aufgehört, aktiv Call Of Duty bzw. generell Online zu spielen.
    Es macht einfach keinen Spaß mehr!
  3. Like
    KayOneX-24 got a reaction from ilsant0 in R1 DumaOS Briefly Delayed   
    I have had the XR500 with DumaOS installed on it for quite a while now.
    One thing I can say for sure is that my gameplay was much better with the old R1 compared to the XR500.
    In regards of the bufferbloat issue the XR500 was definitely not as effective as the R1 is.
     
    You can test it easily yourself if you own both devices by running a simple test at DSLReports.com.
    Now you can argue that DSLReports is inaccurate and just the results of PingPlotter matter.
    Most people - me included - use the trial version of PingPlotter. In the trial version you cannot
    switch between different internet protocols (TCP, UDP, ICMP etc...). I can just guess, but I believe
    that most people are also using the trial version that lacks the option to switch between the protocols.
    In the testing context it means that PingPlotter checks each hop by "pinging" it seperately while using the ICMP protocol.
    Instead, DSLReports.com uses UDP for testing. And UDP is the protocol that most games, for e.g. Call Of Duty, use.
     
    In my opinion DSLReports gives me more detailed information on what's going on behind the scene.
    And that is the point where I can see the results of both devices compared to each other.
    At the end of the day the R1 has better results than the XR500 for me.
    Gaming felt even better with the R1 compared to the XR500.
    That is the reason why I had demanded a refund at Amazon for my XR500.
    I have sent my XR500 back to Amazon and have my money back.
    Sadly true!
     
    I wish I could report better, because I really like Netduma.
    Maybe some time later I will buy another XR500 for testing. Maybe my device was faulty.
    I can only be convinced into buying another XR500 if there is a big firmware update that fixes
    all issues and adds Ping Assist (which it still lacks) as well and if it gets positive reviews by
    independent sources.
     
    Best regards,
    KayOneX-24
  4. Like
    KayOneX-24 got a reaction from benjammin1980 in R1 DumaOS Briefly Delayed   
    I have had the XR500 with DumaOS installed on it for quite a while now.
    One thing I can say for sure is that my gameplay was much better with the old R1 compared to the XR500.
    In regards of the bufferbloat issue the XR500 was definitely not as effective as the R1 is.
     
    You can test it easily yourself if you own both devices by running a simple test at DSLReports.com.
    Now you can argue that DSLReports is inaccurate and just the results of PingPlotter matter.
    Most people - me included - use the trial version of PingPlotter. In the trial version you cannot
    switch between different internet protocols (TCP, UDP, ICMP etc...). I can just guess, but I believe
    that most people are also using the trial version that lacks the option to switch between the protocols.
    In the testing context it means that PingPlotter checks each hop by "pinging" it seperately while using the ICMP protocol.
    Instead, DSLReports.com uses UDP for testing. And UDP is the protocol that most games, for e.g. Call Of Duty, use.
     
    In my opinion DSLReports gives me more detailed information on what's going on behind the scene.
    And that is the point where I can see the results of both devices compared to each other.
    At the end of the day the R1 has better results than the XR500 for me.
    Gaming felt even better with the R1 compared to the XR500.
    That is the reason why I had demanded a refund at Amazon for my XR500.
    I have sent my XR500 back to Amazon and have my money back.
    Sadly true!
     
    I wish I could report better, because I really like Netduma.
    Maybe some time later I will buy another XR500 for testing. Maybe my device was faulty.
    I can only be convinced into buying another XR500 if there is a big firmware update that fixes
    all issues and adds Ping Assist (which it still lacks) as well and if it gets positive reviews by
    independent sources.
     
    Best regards,
    KayOneX-24
  5. Like
    KayOneX-24 got a reaction from Locosano in R1 DumaOS Briefly Delayed   
    I have had the XR500 with DumaOS installed on it for quite a while now.
    One thing I can say for sure is that my gameplay was much better with the old R1 compared to the XR500.
    In regards of the bufferbloat issue the XR500 was definitely not as effective as the R1 is.
     
    You can test it easily yourself if you own both devices by running a simple test at DSLReports.com.
    Now you can argue that DSLReports is inaccurate and just the results of PingPlotter matter.
    Most people - me included - use the trial version of PingPlotter. In the trial version you cannot
    switch between different internet protocols (TCP, UDP, ICMP etc...). I can just guess, but I believe
    that most people are also using the trial version that lacks the option to switch between the protocols.
    In the testing context it means that PingPlotter checks each hop by "pinging" it seperately while using the ICMP protocol.
    Instead, DSLReports.com uses UDP for testing. And UDP is the protocol that most games, for e.g. Call Of Duty, use.
     
    In my opinion DSLReports gives me more detailed information on what's going on behind the scene.
    And that is the point where I can see the results of both devices compared to each other.
    At the end of the day the R1 has better results than the XR500 for me.
    Gaming felt even better with the R1 compared to the XR500.
    That is the reason why I had demanded a refund at Amazon for my XR500.
    I have sent my XR500 back to Amazon and have my money back.
    Sadly true!
     
    I wish I could report better, because I really like Netduma.
    Maybe some time later I will buy another XR500 for testing. Maybe my device was faulty.
    I can only be convinced into buying another XR500 if there is a big firmware update that fixes
    all issues and adds Ping Assist (which it still lacks) as well and if it gets positive reviews by
    independent sources.
     
    Best regards,
    KayOneX-24
  6. Like
    KayOneX-24 got a reaction from N3CR0 in R1 DumaOS Briefly Delayed   
    I have had the XR500 with DumaOS installed on it for quite a while now.
    One thing I can say for sure is that my gameplay was much better with the old R1 compared to the XR500.
    In regards of the bufferbloat issue the XR500 was definitely not as effective as the R1 is.
     
    You can test it easily yourself if you own both devices by running a simple test at DSLReports.com.
    Now you can argue that DSLReports is inaccurate and just the results of PingPlotter matter.
    Most people - me included - use the trial version of PingPlotter. In the trial version you cannot
    switch between different internet protocols (TCP, UDP, ICMP etc...). I can just guess, but I believe
    that most people are also using the trial version that lacks the option to switch between the protocols.
    In the testing context it means that PingPlotter checks each hop by "pinging" it seperately while using the ICMP protocol.
    Instead, DSLReports.com uses UDP for testing. And UDP is the protocol that most games, for e.g. Call Of Duty, use.
     
    In my opinion DSLReports gives me more detailed information on what's going on behind the scene.
    And that is the point where I can see the results of both devices compared to each other.
    At the end of the day the R1 has better results than the XR500 for me.
    Gaming felt even better with the R1 compared to the XR500.
    That is the reason why I had demanded a refund at Amazon for my XR500.
    I have sent my XR500 back to Amazon and have my money back.
    Sadly true!
     
    I wish I could report better, because I really like Netduma.
    Maybe some time later I will buy another XR500 for testing. Maybe my device was faulty.
    I can only be convinced into buying another XR500 if there is a big firmware update that fixes
    all issues and adds Ping Assist (which it still lacks) as well and if it gets positive reviews by
    independent sources.
     
    Best regards,
    KayOneX-24
  7. Like
    KayOneX-24 got a reaction from Victor-Yout in R1 DumaOS Briefly Delayed   
    I have had the XR500 with DumaOS installed on it for quite a while now.
    One thing I can say for sure is that my gameplay was much better with the old R1 compared to the XR500.
    In regards of the bufferbloat issue the XR500 was definitely not as effective as the R1 is.
     
    You can test it easily yourself if you own both devices by running a simple test at DSLReports.com.
    Now you can argue that DSLReports is inaccurate and just the results of PingPlotter matter.
    Most people - me included - use the trial version of PingPlotter. In the trial version you cannot
    switch between different internet protocols (TCP, UDP, ICMP etc...). I can just guess, but I believe
    that most people are also using the trial version that lacks the option to switch between the protocols.
    In the testing context it means that PingPlotter checks each hop by "pinging" it seperately while using the ICMP protocol.
    Instead, DSLReports.com uses UDP for testing. And UDP is the protocol that most games, for e.g. Call Of Duty, use.
     
    In my opinion DSLReports gives me more detailed information on what's going on behind the scene.
    And that is the point where I can see the results of both devices compared to each other.
    At the end of the day the R1 has better results than the XR500 for me.
    Gaming felt even better with the R1 compared to the XR500.
    That is the reason why I had demanded a refund at Amazon for my XR500.
    I have sent my XR500 back to Amazon and have my money back.
    Sadly true!
     
    I wish I could report better, because I really like Netduma.
    Maybe some time later I will buy another XR500 for testing. Maybe my device was faulty.
    I can only be convinced into buying another XR500 if there is a big firmware update that fixes
    all issues and adds Ping Assist (which it still lacks) as well and if it gets positive reviews by
    independent sources.
     
    Best regards,
    KayOneX-24
  8. Like
    KayOneX-24 got a reaction from ChriscomIT in R1 DumaOS Briefly Delayed   
    I have had the XR500 with DumaOS installed on it for quite a while now.
    One thing I can say for sure is that my gameplay was much better with the old R1 compared to the XR500.
    In regards of the bufferbloat issue the XR500 was definitely not as effective as the R1 is.
     
    You can test it easily yourself if you own both devices by running a simple test at DSLReports.com.
    Now you can argue that DSLReports is inaccurate and just the results of PingPlotter matter.
    Most people - me included - use the trial version of PingPlotter. In the trial version you cannot
    switch between different internet protocols (TCP, UDP, ICMP etc...). I can just guess, but I believe
    that most people are also using the trial version that lacks the option to switch between the protocols.
    In the testing context it means that PingPlotter checks each hop by "pinging" it seperately while using the ICMP protocol.
    Instead, DSLReports.com uses UDP for testing. And UDP is the protocol that most games, for e.g. Call Of Duty, use.
     
    In my opinion DSLReports gives me more detailed information on what's going on behind the scene.
    And that is the point where I can see the results of both devices compared to each other.
    At the end of the day the R1 has better results than the XR500 for me.
    Gaming felt even better with the R1 compared to the XR500.
    That is the reason why I had demanded a refund at Amazon for my XR500.
    I have sent my XR500 back to Amazon and have my money back.
    Sadly true!
     
    I wish I could report better, because I really like Netduma.
    Maybe some time later I will buy another XR500 for testing. Maybe my device was faulty.
    I can only be convinced into buying another XR500 if there is a big firmware update that fixes
    all issues and adds Ping Assist (which it still lacks) as well and if it gets positive reviews by
    independent sources.
     
    Best regards,
    KayOneX-24
  9. Like
    KayOneX-24 reacted to RL317 in R1 DumaOS Briefly Delayed   
    Hey Luke, Fraser or Iain,
     
    As the release was only to be delayed by "a few more weeks at the absolute most", and it's been a few more weeks, could we please at least have some info on what's happening if the update itself isn't to be deployed yet?
     
    Many thanks,
    Every patiently waiting Netduma fanboy.
  10. Like
    KayOneX-24 got a reaction from ChriscomIT in R1 DumaOS Briefly Delayed   
    I haven't been around here for a long while.
    I have just seen that the DumaOS hasn't been released, yet.
    Too bad! 
    I had stopped actively gaming some months ago...
    Perhaps, I will make my friend a gift... My R1.
  11. Like
    KayOneX-24 reacted to Netduma Fraser in Led leuchtet rot   
    Selon l'âge de votre ordinateur portable, il est probable que 100mbps est la limite du port Ethernet sur l'ordinateur portable. La couleur peut également représenter si Internet n'est pas utilisé via cet appareil au moment où je crois.
  12. Like
    KayOneX-24 got a reaction from ChriscomIT in A7Legit Passed Away :(   
    Rest in peace, brother. 
    Your gamplays were one of the best I have ever seen in Black Ops III.
    And the way of how you played it made it look so easy.
    We will will miss you, but never forget you.
    Condolences to your family and your friends.
     
    Best regards, KayOneX-24
  13. Like
    KayOneX-24 got a reaction from Januszek45Seict in Issues with CyberGhost VPN   
    Hello!
     
    It's been a while since my last post.
    I'm still very happy with my Netduma R1 and I'm using it everyday for gaming.
    Unfortunately, it's been a while since my VPN (CyberGhost VPN) has stopped working.
    I did no changes to the configuration or username and password, but it just doesn't want
    to work.
    I've tried many things like generating new certificates and so on, but it doesn't help.
     
    The user data (username and password) is typed in correctly into the boxes in the Neduma settings-
     
    For a better understanding I would like to show you my configuration file:
     
     
    - Long text begins here -
     
     
    client remote 1-us.cg-dialup.net 443 dev tun  proto tcp auth-user-pass resolv-retry infinite  redirect-gateway def1 persist-key persist-tun nobind cipher AES-256-CBC auth MD5 ping 15 ping-exit 90 ping-timer-rem script-security 2 remote-cert-tls server route-delay 5 verb 4 comp-lzo <ca> -----BEGIN CERTIFICATE----- Lines removed due to security reasons... -----END CERTIFICATE----- </ca> <cert> -----BEGIN CERTIFICATE----- Lines removed due to security reasons... -----END CERTIFICATE----- </cert> <key> -----BEGIN PRIVATE KEY----- Lines removed due to security reasons... -----END PRIVATE KEY----- </key>     - Long text ends here -     After trying to connect to the VPN servers this is what the log displays...     - Long text begins again -     Sun Sep 17 13:19:27 2017 us=900939 WARNING: file '/tmp/vpncred' is group or others accessible Sun Sep 17 13:19:27 2017 us=901178 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Sun Sep 17 13:19:27 2017 us=981642 LZO compression initialized Sun Sep 17 13:19:27 2017 us=990866 Control Channel MTU parms [ L:1556 D:140 EF:40 EB:0 ET:0 EL:0 ] Sun Sep 17 13:19:27 2017 us=991368 Socket Buffers: R=[87380->131072] S=[16384->131072] Sun Sep 17 13:19:28 2017 us=20161 Data Channel MTU parms [ L:1556 D:1450 EF:56 EB:135 ET:0 EL:0 AF:3/1 ] Sun Sep 17 13:19:28 2017 us=20585 Attempting to establish TCP connection with [AF_INET]207.244.77.236:443 [nonblock] Sun Sep 17 13:19:29 2017 us=21277 TCP connection established with [AF_INET]207.244.77.236:443 Sun Sep 17 13:19:29 2017 us=21465 TCPv4_CLIENT link local: [undef] Sun Sep 17 13:19:29 2017 us=21596 TCPv4_CLIENT link remote: [AF_INET]207.244.77.236:443 Sun Sep 17 13:19:29 2017 us=127249 TLS: Initial packet from [AF_INET]207.244.77.236:443, sid=1352c952 ecb47c69 Sun Sep 17 13:19:29 2017 us=128056 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this Sun Sep 17 13:19:29 2017 us=495240 VERIFY OK: depth=1, C=RO, L=Bucharest, O=CyberGhost S.A., CN=CyberGhost Root CA, [email protected] Sun Sep 17 13:19:29 2017 us=517015 Validating certificate key usage Sun Sep 17 13:19:29 2017 us=517261 ++ Certificate has key usage  00a0, expects 00a0 Sun Sep 17 13:19:29 2017 us=517434 VERIFY KU OK Sun Sep 17 13:19:29 2017 us=517647 Validating certificate extended key usage Sun Sep 17 13:19:29 2017 us=517851 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication Sun Sep 17 13:19:29 2017 us=518031 VERIFY EKU OK Sun Sep 17 13:19:29 2017 us=518195 VERIFY OK: depth=0, C=RO, L=Bucharest, O=CyberGhost S.A., CN=CyberGhost VPN Server Washington-S04-I01, [email protected] Sun Sep 17 13:19:29 2017 us=518806 TLS_ERROR: BIO read tls_read_plaintext error: error:100AE081:lib(16):func(174):reason(129): error:1408D010:lib(20):func(141):reason(16) Sun Sep 17 13:19:29 2017 us=519044 TLS Error: TLS object -> incoming plaintext read error Sun Sep 17 13:19:29 2017 us=519211 TLS Error: TLS handshake failed Sun Sep 17 13:19:29 2017 us=520365 Fatal TLS error (check_tls_errors_co), restarting Sun Sep 17 13:19:29 2017 us=520809 TCP/UDP: Closing socket Sun Sep 17 13:19:29 2017 us=521340 SIGUSR1[soft,tls-error] received, process restarting Sun Sep 17 13:19:29 2017 us=521579 Restart pause, 5 second(s) Sun Sep 17 13:19:34 2017 us=521835 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Sun Sep 17 13:19:34 2017 us=522077 Re-using SSL/TLS context Sun Sep 17 13:19:34 2017 us=522218 LZO compression initialized Sun Sep 17 13:19:34 2017 us=522826 Control Channel MTU parms [ L:1556 D:140 EF:40 EB:0 ET:0 EL:0 ] Sun Sep 17 13:19:34 2017 us=523113 Socket Buffers: R=[87380->131072] S=[16384->131072] Sun Sep 17 13:19:34 2017 us=524478 Data Channel MTU parms [ L:1556 D:1450 EF:56 EB:135 ET:0 EL:0 AF:3/1 ] Sun Sep 17 13:19:34 2017 us=524747 Attempting to establish TCP connection with [AF_INET]38.95.111.41:443 [nonblock] Sun Sep 17 13:19:35 2017 us=525337 TCP connection established with [AF_INET]38.95.111.41:443 Sun Sep 17 13:19:35 2017 us=525528 TCPv4_CLIENT link local: [undef] Sun Sep 17 13:19:35 2017 us=525656 TCPv4_CLIENT link remote: [AF_INET]38.95.111.41:443 Sun Sep 17 13:19:35 2017 us=690431 TLS: Initial packet from [AF_INET]38.95.111.41:443, sid=530c2cd8 aef68002 Sun Sep 17 13:19:36 2017 us=245286 VERIFY OK: depth=1, C=RO, L=Bucharest, O=CyberGhost S.A., CN=CyberGhost Root CA, [email protected] Sun Sep 17 13:19:36 2017 us=258392 Validating certificate key usage Sun Sep 17 13:19:36 2017 us=258636 ++ Certificate has key usage  00a0, expects 00a0 Sun Sep 17 13:19:36 2017 us=258796 VERIFY KU OK Sun Sep 17 13:19:36 2017 us=258999 Validating certificate extended key usage Sun Sep 17 13:19:36 2017 us=259194 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication Sun Sep 17 13:19:36 2017 us=259384 VERIFY EKU OK Sun Sep 17 13:19:36 2017 us=259551 VERIFY OK: depth=0, C=RO, L=Bucharest, O=CyberGhost S.A., CN=CyberGhost VPN Server LosAngeles-S12-I01, [email protected] Sun Sep 17 13:19:36 2017 us=260014 TLS_ERROR: BIO read tls_read_plaintext error: error:100AE081:lib(16):func(174):reason(129): error:1408D010:lib(20):func(141):reason(16) Sun Sep 17 13:19:36 2017 us=260240 TLS Error: TLS object -> incoming plaintext read error Sun Sep 17 13:19:36 2017 us=260462 TLS Error: TLS handshake failed Sun Sep 17 13:19:36 2017 us=261456 Fatal TLS error (check_tls_errors_co), restarting Sun Sep 17 13:19:36 2017 us=261895 TCP/UDP: Closing socket Sun Sep 17 13:19:36 2017 us=262370 SIGUSR1[soft,tls-error] received, process restarting Sun Sep 17 13:19:36 2017 us=262607 Restart pause, 5 second(s) Sun Sep 17 13:19:41 2017 us=262866 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Sun Sep 17 13:19:41 2017 us=263094 Re-using SSL/TLS context Sun Sep 17 13:19:41 2017 us=263221 LZO compression initialized Sun Sep 17 13:19:41 2017 us=263810 Control Channel MTU parms [ L:1556 D:140 EF:40 EB:0 ET:0 EL:0 ] Sun Sep 17 13:19:41 2017 us=264100 Socket Buffers: R=[87380->131072] S=[16384->131072] Sun Sep 17 13:19:41 2017 us=265457 Data Channel MTU parms [ L:1556 D:1450 EF:56 EB:135 ET:0 EL:0 AF:3/1 ] Sun Sep 17 13:19:41 2017 us=265758 Attempting to establish TCP connection with [AF_INET]207.244.77.236:443 [nonblock] Sun Sep 17 13:19:42 2017 us=266358 TCP connection established with [AF_INET]207.244.77.236:443 Sun Sep 17 13:19:42 2017 us=266547 TCPv4_CLIENT link local: [undef] Sun Sep 17 13:19:42 2017 us=266678 TCPv4_CLIENT link remote: [AF_INET]207.244.77.236:443 Sun Sep 17 13:19:42 2017 us=370730 TLS: Initial packet from [AF_INET]207.244.77.236:443, sid=9893fbac ee052bde Sun Sep 17 13:19:42 2017 us=737629 VERIFY OK: depth=1, C=RO, L=Bucharest, O=CyberGhost S.A., CN=CyberGhost Root CA, [email protected] Sun Sep 17 13:19:42 2017 us=752033 Validating certificate key usage Sun Sep 17 13:19:42 2017 us=752276 ++ Certificate has key usage  00a0, expects 00a0 Sun Sep 17 13:19:42 2017 us=752506 VERIFY KU OK Sun Sep 17 13:19:42 2017 us=752722 Validating certificate extended key usage Sun Sep 17 13:19:42 2017 us=752919 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication Sun Sep 17 13:19:42 2017 us=753080 VERIFY EKU OK Sun Sep 17 13:19:42 2017 us=753237 VERIFY OK: depth=0, C=RO, L=Bucharest, O=CyberGhost S.A., CN=CyberGhost VPN Server Washington-S04-I01, [email protected] Sun Sep 17 13:19:42 2017 us=754247 TLS_ERROR: BIO read tls_read_plaintext error: error:100AE081:lib(16):func(174):reason(129): error:1408D010:lib(20):func(141):reason(16) Sun Sep 17 13:19:42 2017 us=754482 TLS Error: TLS object -> incoming plaintext read error Sun Sep 17 13:19:42 2017 us=754654 TLS Error: TLS handshake failed Sun Sep 17 13:19:42 2017 us=755637 Fatal TLS error (check_tls_errors_co), restarting Sun Sep 17 13:19:42 2017 us=756672 TCP/UDP: Closing socket Sun Sep 17 13:19:42 2017 us=757172 SIGUSR1[soft,tls-error] received, process restarting Sun Sep 17 13:19:42 2017 us=757412 Restart pause, 5 second(s) Sun Sep 17 13:19:47 2017 us=757669 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Sun Sep 17 13:19:47 2017 us=757895 Re-using SSL/TLS context Sun Sep 17 13:19:47 2017 us=758025 LZO compression initialized Sun Sep 17 13:19:47 2017 us=758620 Control Channel MTU parms [ L:1556 D:140 EF:40 EB:0 ET:0 EL:0 ] Sun Sep 17 13:19:47 2017 us=758908 Socket Buffers: R=[87380->131072] S=[16384->131072] Sun Sep 17 13:19:47 2017 us=760197 Data Channel MTU parms [ L:1556 D:1450 EF:56 EB:135 ET:0 EL:0 AF:3/1 ] Sun Sep 17 13:19:47 2017 us=760538 Attempting to establish TCP connection with [AF_INET]167.160.123.22:443 [nonblock] Sun Sep 17 13:19:48 2017 us=761145 TCP connection established with [AF_INET]167.160.123.22:443 Sun Sep 17 13:19:48 2017 us=761332 TCPv4_CLIENT link local: [undef] Sun Sep 17 13:19:48 2017 us=761467 TCPv4_CLIENT link remote: [AF_INET]167.160.123.22:443 Sun Sep 17 13:19:48 2017 us=907843 TLS: Initial packet from [AF_INET]167.160.123.22:443, sid=329b99f3 cdb10cec Sun Sep 17 13:19:49 2017 us=412302 VERIFY OK: depth=1, C=RO, L=Bucharest, O=CyberGhost S.A., CN=CyberGhost Root CA, [email protected] Sun Sep 17 13:19:49 2017 us=452293 Validating certificate key usage Sun Sep 17 13:19:49 2017 us=452582 ++ Certificate has key usage  00a0, expects 00a0 Sun Sep 17 13:19:49 2017 us=452743 VERIFY KU OK Sun Sep 17 13:19:49 2017 us=452953 Validating certificate extended key usage Sun Sep 17 13:19:49 2017 us=453153 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication Sun Sep 17 13:19:49 2017 us=453316 VERIFY EKU OK Sun Sep 17 13:19:49 2017 us=453477 VERIFY OK: depth=0, C=RO, L=Bucharest, O=CyberGhost S.A., CN=CyberGhost VPN Server Jackson-S02-I04, [email protected] Sun Sep 17 13:19:49 2017 us=454220 TLS_ERROR: BIO read tls_read_plaintext error: error:100AE081:lib(16):func(174):reason(129): error:1408D010:lib(20):func(141):reason(16) Sun Sep 17 13:19:49 2017 us=454471 TLS Error: TLS object -> incoming plaintext read error Sun Sep 17 13:19:49 2017 us=454646 TLS Error: TLS handshake failed Sun Sep 17 13:19:49 2017 us=455626 Fatal TLS error (check_tls_errors_co), restarting Sun Sep 17 13:19:49 2017 us=456060 TCP/UDP: Closing socket Sun Sep 17 13:19:49 2017 us=457970 SIGUSR1[soft,tls-error] received, process restarting Sun Sep 17 13:19:49 2017 us=458219 Restart pause, 5 second(s) Sun Sep 17 13:19:54 2017 us=458475 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Sun Sep 17 13:19:54 2017 us=458719 Re-using SSL/TLS context Sun Sep 17 13:19:54 2017 us=458870 LZO compression initialized Sun Sep 17 13:19:54 2017 us=459488 Control Channel MTU parms [ L:1556 D:140 EF:40 EB:0 ET:0 EL:0 ] Sun Sep 17 13:19:54 2017 us=459775 Socket Buffers: R=[87380->131072] S=[16384->131072] Sun Sep 17 13:19:54 2017 us=461141 Data Channel MTU parms [ L:1556 D:1450 EF:56 EB:135 ET:0 EL:0 AF:3/1 ] Sun Sep 17 13:19:54 2017 us=461440 Attempting to establish TCP connection with [AF_INET]38.95.109.54:443 [nonblock] Sun Sep 17 13:19:55 2017 us=462050 TCP connection established with [AF_INET]38.95.109.54:443 Sun Sep 17 13:19:55 2017 us=462240 TCPv4_CLIENT link local: [undef] Sun Sep 17 13:19:55 2017 us=462372 TCPv4_CLIENT link remote: [AF_INET]38.95.109.54:443 Sun Sep 17 13:19:55 2017 us=627113 TLS: Initial packet from [AF_INET]38.95.109.54:443, sid=39688c86 3075cc14 Sun Sep 17 13:19:56 2017 us=189073 VERIFY OK: depth=1, C=RO, L=Bucharest, O=CyberGhost S.A., CN=CyberGhost Root CA, [email protected] Sun Sep 17 13:19:56 2017 us=201162 Validating certificate key usage Sun Sep 17 13:19:56 2017 us=201404 ++ Certificate has key usage  00a0, expects 00a0 Sun Sep 17 13:19:56 2017 us=201564 VERIFY KU OK Sun Sep 17 13:19:56 2017 us=201772 Validating certificate extended key usage Sun Sep 17 13:19:56 2017 us=201969 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication Sun Sep 17 13:19:56 2017 us=202130 VERIFY EKU OK Sun Sep 17 13:19:56 2017 us=202293 VERIFY OK: depth=0, C=RO, L=Bucharest, O=CyberGhost S.A., CN=CyberGhost VPN Server LosAngeles-S05-I03, [email protected] Sun Sep 17 13:19:56 2017 us=202746 TLS_ERROR: BIO read tls_read_plaintext error: error:100AE081:lib(16):func(174):reason(129): error:1408D010:lib(20):func(141):reason(16) Sun Sep 17 13:19:56 2017 us=202974 TLS Error: TLS object -> incoming plaintext read error Sun Sep 17 13:19:56 2017 us=203144 TLS Error: TLS handshake failed Sun Sep 17 13:19:56 2017 us=204130 Fatal TLS error (check_tls_errors_co), restarting Sun Sep 17 13:19:56 2017 us=204609 TCP/UDP: Closing socket Sun Sep 17 13:19:56 2017 us=205042 SIGUSR1[soft,tls-error] received, process restarting Sun Sep 17 13:19:56 2017 us=205201 Restart pause, 5 second(s) Sun Sep 17 13:20:01 2017 us=205394 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Sun Sep 17 13:20:01 2017 us=205614 Re-using SSL/TLS context Sun Sep 17 13:20:01 2017 us=205741 LZO compression initialized Sun Sep 17 13:20:01 2017 us=206333 Control Channel MTU parms [ L:1556 D:140 EF:40 EB:0 ET:0 EL:0 ] Sun Sep 17 13:20:01 2017 us=206618 Socket Buffers: R=[87380->131072] S=[16384->131072] Sun Sep 17 13:20:01 2017 us=207921 Data Channel MTU parms [ L:1556 D:1450 EF:56 EB:135 ET:0 EL:0 AF:3/1 ] Sun Sep 17 13:20:01 2017 us=208149 Attempting to establish TCP connection with [AF_INET]23.81.27.205:443 [nonblock] Sun Sep 17 13:20:02 2017 us=208817 TCP connection established with [AF_INET]23.81.27.205:443 Sun Sep 17 13:20:02 2017 us=209007 TCPv4_CLIENT link local: [undef] Sun Sep 17 13:20:02 2017 us=209135 TCPv4_CLIENT link remote: [AF_INET]23.81.27.205:443 Sun Sep 17 13:20:02 2017 us=328379 TLS: Initial packet from [AF_INET]23.81.27.205:443, sid=039a1d1f f57e248d Sun Sep 17 13:20:02 2017 us=742692 VERIFY OK: depth=1, C=RO, L=Bucharest, O=CyberGhost S.A., CN=CyberGhost Root CA, [email protected] Sun Sep 17 13:20:02 2017 us=754406 Validating certificate key usage Sun Sep 17 13:20:02 2017 us=754647 ++ Certificate has key usage  00a0, expects 00a0 Sun Sep 17 13:20:02 2017 us=754808 VERIFY KU OK Sun Sep 17 13:20:02 2017 us=755015 Validating certificate extended key usage Sun Sep 17 13:20:02 2017 us=755214 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication Sun Sep 17 13:20:02 2017 us=755376 VERIFY EKU OK Sun Sep 17 13:20:02 2017 us=755535 VERIFY OK: depth=0, C=RO, L=Bucharest, O=CyberGhost S.A., CN=CyberGhost VPN Server Chicago-S03-I03, [email protected] Sun Sep 17 13:20:02 2017 us=755996 TLS_ERROR: BIO read tls_read_plaintext error: error:100AE081:lib(16):func(174):reason(129): error:1408D010:lib(20):func(141):reason(16) Sun Sep 17 13:20:02 2017 us=756223 TLS Error: TLS object -> incoming plaintext read error Sun Sep 17 13:20:02 2017 us=756447 TLS Error: TLS handshake failed Sun Sep 17 13:20:02 2017 us=757444 Fatal TLS error (check_tls_errors_co), restarting Sun Sep 17 13:20:02 2017 us=757878 TCP/UDP: Closing socket Sun Sep 17 13:20:02 2017 us=758352 SIGUSR1[soft,tls-error] received, process restarting Sun Sep 17 13:20:02 2017 us=758592 Restart pause, 5 second(s) Sun Sep 17 13:20:07 2017 us=758859 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Sun Sep 17 13:20:07 2017 us=759084 Re-using SSL/TLS context Sun Sep 17 13:20:07 2017 us=759211 LZO compression initialized Sun Sep 17 13:20:07 2017 us=759804 Control Channel MTU parms [ L:1556 D:140 EF:40 EB:0 ET:0 EL:0 ] Sun Sep 17 13:20:07 2017 us=760090 Socket Buffers: R=[87380->131072] S=[16384->131072] Sun Sep 17 13:20:07 2017 us=761406 Data Channel MTU parms [ L:1556 D:1450 EF:56 EB:135 ET:0 EL:0 AF:3/1 ] Sun Sep 17 13:20:07 2017 us=761707 Attempting to establish TCP connection with [AF_INET]64.20.33.206:443 [nonblock] Sun Sep 17 13:20:08 2017 us=762305 TCP connection established with [AF_INET]64.20.33.206:443 Sun Sep 17 13:20:08 2017 us=762492 TCPv4_CLIENT link local: [undef] Sun Sep 17 13:20:08 2017 us=762624 TCPv4_CLIENT link remote: [AF_INET]64.20.33.206:443 Sun Sep 17 13:20:08 2017 us=859689 TLS: Initial packet from [AF_INET]64.20.33.206:443, sid=0829361b 75075856 Sun Sep 17 13:20:09 2017 us=198629 VERIFY OK: depth=1, C=RO, L=Bucharest, O=CyberGhost S.A., CN=CyberGhost Root CA, [email protected] Sun Sep 17 13:20:09 2017 us=210354 Validating certificate key usage Sun Sep 17 13:20:09 2017 us=210596 ++ Certificate has key usage  00a0, expects 00a0 Sun Sep 17 13:20:09 2017 us=210756 VERIFY KU OK Sun Sep 17 13:20:09 2017 us=210960 Validating certificate extended key usage Sun Sep 17 13:20:09 2017 us=211158 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication Sun Sep 17 13:20:09 2017 us=211320 VERIFY EKU OK Sun Sep 17 13:20:09 2017 us=211480 VERIFY OK: depth=0, C=RO, L=Bucharest, O=CyberGhost S.A., CN=CyberGhost VPN Server NewJersey-S01-I04, [email protected] Sun Sep 17 13:20:09 2017 us=211973 TLS_ERROR: BIO read tls_read_plaintext error: error:100AE081:lib(16):func(174):reason(129): error:1408D010:lib(20):func(141):reason(16) Sun Sep 17 13:20:09 2017 us=212206 TLS Error: TLS object -> incoming plaintext read error Sun Sep 17 13:20:09 2017 us=212441 TLS Error: TLS handshake failed Sun Sep 17 13:20:09 2017 us=213404 Fatal TLS error (check_tls_errors_co), restarting Sun Sep 17 13:20:09 2017 us=213762 TCP/UDP: Closing socket Sun Sep 17 13:20:09 2017 us=214161 SIGUSR1[soft,tls-error] received, process restarting Sun Sep 17 13:20:09 2017 us=214321 Restart pause, 5 second(s) Sun Sep 17 13:20:14 2017 us=214516 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Sun Sep 17 13:20:14 2017 us=214743 Re-using SSL/TLS context Sun Sep 17 13:20:14 2017 us=214870 LZO compression initialized Sun Sep 17 13:20:14 2017 us=215465 Control Channel MTU parms [ L:1556 D:140 EF:40 EB:0 ET:0 EL:0 ] Sun Sep 17 13:20:14 2017 us=215750 Socket Buffers: R=[87380->131072] S=[16384->131072] Sun Sep 17 13:20:14 2017 us=218194 Data Channel MTU parms [ L:1556 D:1450 EF:56 EB:135 ET:0 EL:0 AF:3/1 ] Sun Sep 17 13:20:14 2017 us=218683 Attempting to establish TCP connection with [AF_INET]207.244.77.237:443 [nonblock] Sun Sep 17 13:20:15 2017 us=219484 TCP connection established with [AF_INET]207.244.77.237:443 Sun Sep 17 13:20:15 2017 us=219670 TCPv4_CLIENT link local: [undef] Sun Sep 17 13:20:15 2017 us=219802 TCPv4_CLIENT link remote: [AF_INET]207.244.77.237:443 Sun Sep 17 13:20:15 2017 us=322024 TLS: Initial packet from [AF_INET]207.244.77.237:443, sid=a53cced5 19afd506 Sun Sep 17 13:20:15 2017 us=680278 VERIFY OK: depth=1, C=RO, L=Bucharest, O=CyberGhost S.A., CN=CyberGhost Root CA, [email protected] Sun Sep 17 13:20:15 2017 us=692558 Validating certificate key usage Sun Sep 17 13:20:15 2017 us=692803 ++ Certificate has key usage  00a0, expects 00a0 Sun Sep 17 13:20:15 2017 us=692962 VERIFY KU OK Sun Sep 17 13:20:15 2017 us=693169 Validating certificate extended key usage Sun Sep 17 13:20:15 2017 us=693366 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication Sun Sep 17 13:20:15 2017 us=693529 VERIFY EKU OK Sun Sep 17 13:20:15 2017 us=693689 VERIFY OK: depth=0, C=RO, L=Bucharest, O=CyberGhost S.A., CN=CyberGhost VPN Server Washington-S04-I02, [email protected] Sun Sep 17 13:20:15 2017 us=694145 TLS_ERROR: BIO read tls_read_plaintext error: error:100AE081:lib(16):func(174):reason(129): error:1408D010:lib(20):func(141):reason(16) Sun Sep 17 13:20:15 2017 us=694372 TLS Error: TLS object -> incoming plaintext read error Sun Sep 17 13:20:15 2017 us=694540 TLS Error: TLS handshake failed Sun Sep 17 13:20:15 2017 us=695521 Fatal TLS error (check_tls_errors_co), restarting Sun Sep 17 13:20:15 2017 us=695957 TCP/UDP: Closing socket Sun Sep 17 13:20:15 2017 us=696836 SIGUSR1[soft,tls-error] received, process restarting Sun Sep 17 13:20:15 2017 us=697072 Restart pause, 5 second(s) Sun Sep 17 13:20:20 2017 us=697331 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Sun Sep 17 13:20:20 2017 us=697559 Re-using SSL/TLS context Sun Sep 17 13:20:20 2017 us=697686 LZO compression initialized Sun Sep 17 13:20:20 2017 us=698278 Control Channel MTU parms [ L:1556 D:140 EF:40 EB:0 ET:0 EL:0 ] Sun Sep 17 13:20:20 2017 us=698564 Socket Buffers: R=[87380->131072] S=[16384->131072] Sun Sep 17 13:20:20 2017 us=699857 Data Channel MTU parms [ L:1556 D:1450 EF:56 EB:135 ET:0 EL:0 AF:3/1 ] Sun Sep 17 13:20:20 2017 us=700083 Attempting to establish TCP connection with [AF_INET]38.95.111.42:443 [nonblock] Sun Sep 17 13:20:21 2017 us=700742 TCP connection established with [AF_INET]38.95.111.42:443 Sun Sep 17 13:20:21 2017 us=701036 TCPv4_CLIENT link local: [undef] Sun Sep 17 13:20:21 2017 us=701189 TCPv4_CLIENT link remote: [AF_INET]38.95.111.42:443 Sun Sep 17 13:20:21 2017 us=873468 TLS: Initial packet from [AF_INET]38.95.111.42:443, sid=5654da97 1ffcd9cb Sun Sep 17 13:20:22 2017 us=436662 VERIFY OK: depth=1, C=RO, L=Bucharest, O=CyberGhost S.A., CN=CyberGhost Root CA, [email protected] Sun Sep 17 13:20:22 2017 us=448440 Validating certificate key usage Sun Sep 17 13:20:22 2017 us=448686 ++ Certificate has key usage  00a0, expects 00a0 Sun Sep 17 13:20:22 2017 us=448846 VERIFY KU OK Sun Sep 17 13:20:22 2017 us=449052 Validating certificate extended key usage Sun Sep 17 13:20:22 2017 us=449249 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication Sun Sep 17 13:20:22 2017 us=449414 VERIFY EKU OK Sun Sep 17 13:20:22 2017 us=449573 VERIFY OK: depth=0, C=RO, L=Bucharest, O=CyberGhost S.A., CN=CyberGhost VPN Server LosAngeles-S12-I02, [email protected] Sun Sep 17 13:20:22 2017 us=450031 TLS_ERROR: BIO read tls_read_plaintext error: error:100AE081:lib(16):func(174):reason(129): error:1408D010:lib(20):func(141):reason(16) Sun Sep 17 13:20:22 2017 us=450257 TLS Error: TLS object -> incoming plaintext read error Sun Sep 17 13:20:22 2017 us=450425 TLS Error: TLS handshake failed Sun Sep 17 13:20:22 2017 us=451409 Fatal TLS error (check_tls_errors_co), restarting Sun Sep 17 13:20:22 2017 us=451841 TCP/UDP: Closing socket Sun Sep 17 13:20:22 2017 us=452359 SIGUSR1[soft,tls-error] received, process restarting Sun Sep 17 13:20:22 2017 us=452601 Restart pause, 5 second(s) Sun Sep 17 13:20:27 2017 us=452855 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Sun Sep 17 13:20:27 2017 us=453112 Re-using SSL/TLS context Sun Sep 17 13:20:27 2017 us=453279 LZO compression initialized Sun Sep 17 13:20:27 2017 us=453911 Control Channel MTU parms [ L:1556 D:140 EF:40 EB:0 ET:0 EL:0 ] Sun Sep 17 13:20:27 2017 us=454196 Socket Buffers: R=[87380->131072] S=[16384->131072] Sun Sep 17 13:20:27 2017 us=455479 Data Channel MTU parms [ L:1556 D:1450 EF:56 EB:135 ET:0 EL:0 AF:3/1 ] Sun Sep 17 13:20:27 2017 us=455683 Attempting to establish TCP connection with [AF_INET]167.160.123.19:443 [nonblock] Sun Sep 17 13:20:28 2017 us=456223 TCP connection established with [AF_INET]167.160.123.19:443 Sun Sep 17 13:20:28 2017 us=457951 TCPv4_CLIENT link local: [undef] Sun Sep 17 13:20:28 2017 us=458226 TCPv4_CLIENT link remote: [AF_INET]167.160.123.19:443 Sun Sep 17 13:20:28 2017 us=604738 TLS: Initial packet from [AF_INET]167.160.123.19:443, sid=3006ebc2 695ec63d Sun Sep 17 13:20:29 2017 us=107736 VERIFY OK: depth=1, C=RO, L=Bucharest, O=CyberGhost S.A., CN=CyberGhost Root CA, [email protected] Sun Sep 17 13:20:29 2017 us=119419 Validating certificate key usage Sun Sep 17 13:20:29 2017 us=119666 ++ Certificate has key usage  00a0, expects 00a0 Sun Sep 17 13:20:29 2017 us=119828 VERIFY KU OK Sun Sep 17 13:20:29 2017 us=120032 Validating certificate extended key usage Sun Sep 17 13:20:29 2017 us=120230 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication Sun Sep 17 13:20:29 2017 us=120448 VERIFY EKU OK Sun Sep 17 13:20:29 2017 us=120622 VERIFY OK: depth=0, C=RO, L=Bucharest, O=CyberGhost S.A., CN=CyberGhost VPN Server Jackson-S02-I01, [email protected] Sun Sep 17 13:20:29 2017 us=121083 TLS_ERROR: BIO read tls_read_plaintext error: error:100AE081:lib(16):func(174):reason(129): error:1408D010:lib(20):func(141):reason(16) Sun Sep 17 13:20:29 2017 us=121313 TLS Error: TLS object -> incoming plaintext read error Sun Sep 17 13:20:29 2017 us=121487 TLS Error: TLS handshake failed Sun Sep 17 13:20:29 2017 us=122467 Fatal TLS error (check_tls_errors_co), restarting Sun Sep 17 13:20:29 2017 us=122909 TCP/UDP: Closing socket Sun Sep 17 13:20:29 2017 us=123387 SIGUSR1[soft,tls-error] received, process restarting Sun Sep 17 13:20:29 2017 us=123623 Restart pause, 5 second(s)     - Long text ends again -     Is there anything that I could do to solve this issue? I'm proud to be part of this community and I would like to thank you in advance for your help.   Best regards,   KayOneX-24
  14. Like
    KayOneX-24 got a reaction from cranium2001 in A7Legit Passed Away :(   
    Rest in peace, brother. 
    Your gamplays were one of the best I have ever seen in Black Ops III.
    And the way of how you played it made it look so easy.
    We will will miss you, but never forget you.
    Condolences to your family and your friends.
     
    Best regards, KayOneX-24
  15. Like
    KayOneX-24 got a reaction from ColonicBoom in A7Legit Passed Away :(   
    Rest in peace, brother. 
    Your gamplays were one of the best I have ever seen in Black Ops III.
    And the way of how you played it made it look so easy.
    We will will miss you, but never forget you.
    Condolences to your family and your friends.
     
    Best regards, KayOneX-24
  16. Like
    KayOneX-24 got a reaction from Sgt-Greco in A7Legit Passed Away :(   
    Rest in peace, brother. 
    Your gamplays were one of the best I have ever seen in Black Ops III.
    And the way of how you played it made it look so easy.
    We will will miss you, but never forget you.
    Condolences to your family and your friends.
     
    Best regards, KayOneX-24
  17. Like
    KayOneX-24 got a reaction from sncjez in A7Legit Passed Away :(   
    Rest in peace, brother. 
    Your gamplays were one of the best I have ever seen in Black Ops III.
    And the way of how you played it made it look so easy.
    We will will miss you, but never forget you.
    Condolences to your family and your friends.
     
    Best regards, KayOneX-24
  18. Like
    KayOneX-24 got a reaction from N3CR0 in A7Legit Passed Away :(   
    Rest in peace, brother. 
    Your gamplays were one of the best I have ever seen in Black Ops III.
    And the way of how you played it made it look so easy.
    We will will miss you, but never forget you.
    Condolences to your family and your friends.
     
    Best regards, KayOneX-24
  19. Like
    KayOneX-24 reacted to lukasz in A7Legit Passed Away :(   
    Spoczywaj w spokoju dobry kolego, niech po tamtej stronie będzie ci lepeij niż po tej.
  20. Like
    KayOneX-24 reacted to antithesis in A7Legit Passed Away :(   
    Roger that. One of Australia's most famous lifesavers of the 80s and 90s died yesterday from a heart attack. Professional lifesaving is the beach equivalent of a triathlon (swap the bike for a surf ski). The guy was incredibly fit as he continued training until the day he died and he was only 47.
     
    Diet and exercise play a part in heart disease, but even the fittest among us are not immune.
     

    Judging by the sincerity of the family's posts (and the genuine Aussie bogan lingo), it looks legit. The man can't confirm it himself, his silence should be cause for concern.
     
    RIP A7 and thanks for all of your help :salute:
  21. Like
    KayOneX-24 reacted to titofuenla in A7Legit Passed Away :(   
    Terrible news, great player and best person, rest in peace A7
  22. Like
    KayOneX-24 reacted to Miss Vendetta in A7Legit Passed Away :(   
    Wow... devastating. I haven't been on here in quite sometime but he was always so helpful and kind..
    Rest in peace <3
  23. Like
    KayOneX-24 reacted to wrathoftank in A7Legit Passed Away :(   
    A7 was always a great person to interact with, Rest in Peace A7
  24. Like
    KayOneX-24 reacted to Netduma Fraser in A7Legit Passed Away :(   
    If you weren't aware we're trying to get some suggestions for a tournament in A7's honour, if you'd like to contribute you can do so here: 
     
    http://forum.netduma.com/topic/22046-tournament-in-honour-of-a7legit-suggestions/
  25. Like
    KayOneX-24 reacted to sncjez in A7Legit Passed Away :(   
    Sad news indeed.
     
    Really quite shocked to see this he was a good lad.
×
×
  • Create New...