SOLVED:connection issues, Nat and other.

This is for troubleshooting of problems with the FAF client and Forged Alliance game.

Moderator: PhilipJFry

SOLVED:connection issues, Nat and other.

Postby jhvisto » 27 Feb 2012, 22:56

everytime i try to join comes error : 2012-02-27 22:38:56,776 ERROR faf.client Unknown server action received: {"command": "game_launch", "uid": "3381", "mod": "faf"} <-where uid and timestamp is different. livereplays works fine, but no gaming for me until somebody tells me what to do, just reinstalled fa and faf. port's are open and still nothing.
Last edited by jhvisto on 02 Mar 2012, 15:06, edited 1 time in total.
Only in death does duty end.
jhvisto
Crusader
 
Posts: 24
Joined: 27 Feb 2012, 21:09
Location: Finland/pori
Has liked: 0 time
Been liked: 0 time

Re: Unknown server action received

Postby Ze_PilOt » 27 Feb 2012, 22:57

Don't worry, it's normal. If you have a problem, it's not related to that message.
Nossa wrote:I've never played GPG or even heard of FA until FAF started blowing up.
User avatar
Ze_PilOt
Supreme Commander
 
Posts: 8985
Joined: 24 Aug 2011, 18:41
Location: fafland
Has liked: 18 times
Been liked: 376 times
FAF User Name: Ze_PilOt

Re: Unknown server action received

Postby jhvisto » 27 Feb 2012, 22:59

how it's not related? no other error messages..
Only in death does duty end.
jhvisto
Crusader
 
Posts: 24
Joined: 27 Feb 2012, 21:09
Location: Finland/pori
Has liked: 0 time
Been liked: 0 time

Re: Unknown server action received

Postby jhvisto » 27 Feb 2012, 23:05

2012-02-27 23:02:13,568 DEBUG faf.updater writeToServer(UPDATE, [gamedata, murderparty.faf, bb66683c22d908ca3140451b7bd527ab])
2012-02-27 23:02:13,638 DEBUG faf.updater handleAction(UP_TO_DATE)
2012-02-27 23:02:13,638 DEBUG faf.updater file : murderparty.faf
2012-02-27 23:02:13,638 DEBUG faf.updater murderparty.faf is up to date.
2012-02-27 23:02:13,638 DEBUG faf.updater Updates applied successfully.
2012-02-27 23:02:13,640 DEBUG faf.updater Disconnected from server at 2012-02-27 23:02:13
2012-02-27 23:02:13,714 DEBUG faf.updater Update finished at 2012-02-27 23:02:13
2012-02-27 23:02:13,868 ERROR faf.client Unknown server action received: {"args": ["/init murderparty.lua"], "command": "game_launch", "uid": "3397", "mod": "murderparty"}
2012-02-27 23:02:19,683 DEBUG faf.chat Away:lobby

latest.
Only in death does duty end.
jhvisto
Crusader
 
Posts: 24
Joined: 27 Feb 2012, 21:09
Location: Finland/pori
Has liked: 0 time
Been liked: 0 time

Re: Unknown server action received

Postby thygrrr » 28 Feb 2012, 09:43

Does FAF crash??? It shouldn't. The error in the logs is normal. The client should operate fine without understanding that command (it's a new protocol the server speaks in addition to the one your 0.5.x version of FAF speaks).
I waited ten years for Supreme Commander (1997-2007)
and have not a single day felt disappointed with it!

Image
User avatar
thygrrr
Contributor
 
Posts: 783
Joined: 18 Nov 2011, 17:08
Location: Germany
Has liked: 2 times
Been liked: 3 times

Re: Unknown server action received

Postby jhvisto » 28 Feb 2012, 14:01

no, it doesn't crash. it just won't let me join game, i do not know what else to do, i opened ports, took firewall and antivirus off, and still nothing.. :(

fa.log:
Code: Select all
info: GPGNET: setting nat handler to 0x114ba004
info: LOBBY: Game port 6112[UDP] opened.
info: LOBBY: starting with local uid of 14252 [jhvisto]
info: GPGNET: entering lobby state.
info: GPGNET: sending nat packet to 91.229.20.50:30351
info: GPGNET: sending nat packet to 87.61.171.12:80
info: GPGNET: sending nat packet to 87.61.171.12:80
info: NET: using deflate compression for sends to 0x573dab0c.boanqu2.dynamic.dsl.tele.dk:80.
info: LOBBY: Connecting to host "solskin" [0x573dab0c.boanqu2.dynamic.dsl.tele.dk:80, uid=7349]
info: Can't add chat text -- no chat display
info: text="Connecting to game host..."
info: NET: using deflate compression for sends to smtp.xo-care.com:61936.
info: LOBBY: rejecting unexpected connection from smtp.xo-care.com:61936
info: GPGNET: received nat packet from 212.242.93.190:61936
info: GPGNET: received nat packet from 212.242.93.190:61936
info: GPGNET: received nat packet from 87.61.171.12:80
info: GPGNET: received nat packet from 87.61.171.12:80
info: GPGNET: sending nat packet to 212.242.93.190:61936
info: GPGNET: sending nat packet to 212.242.93.190:61936
info: NET: using deflate compression for sends to smtp.xo-care.com:61936.
info: LOBBY: Adding peer "TCleric" [smtp.xo-care.com:61936, uid=7344]
info: Can't add chat text -- no chat display
info: text="Connecting to TCleric..."
info: GPGNET: sending nat packet to 189.30.244.190:16010
info: GPGNET: sending nat packet to 189.30.244.190:16010
info: NET: using deflate compression for sends to 189-30-244-190.paebv701.dsl.brasiltelecom.net.br:16010.
info: LOBBY: Adding peer "MAc" [189-30-244-190.paebv701.dsl.brasiltelecom.net.br:16010, uid=2475]
info: Can't add chat text -- no chat display
info: text="Connecting to MAc..."
info: GPGNET: sending nat packet to 212.242.93.190:61936
info: GPGNET: sending nat packet to 212.242.93.190:61936
info: NET: using deflate compression for sends to 177.17.148.33.static.host.gvt.net.br:6112.
info: LOBBY: rejecting unexpected connection from 177.17.148.33.static.host.gvt.net.br:6112
info: GPGNET: received nat packet from 177.17.148.33:6112
info: GPGNET: received nat packet from 177.17.148.33:6112
info: NET: using deflate compression for sends to 189-69-123-206.dsl.telesp.net.br:6112.
info: LOBBY: rejecting unexpected connection from 189-69-123-206.dsl.telesp.net.br:6112
info: GPGNET: received nat packet from 189.30.244.190:16010
info: GPGNET: received nat packet from 189.69.123.206:6112
info: GPGNET: received nat packet from 189.69.123.206:6112
info: GPGNET: sending nat packet to 177.17.148.33:6112
info: GPGNET: sending nat packet to 177.17.148.33:6112
info: NET: using deflate compression for sends to 177.17.148.33.static.host.gvt.net.br:6112.
info: LOBBY: Adding peer "Caulus" [177.17.148.33.static.host.gvt.net.br:6112, uid=3970]
info: Can't add chat text -- no chat display
info: text="Connecting to Caulus..."
info: GPGNET: sending nat packet to 212.242.93.190:61936
info: GPGNET: sending nat packet to 212.242.93.190:61936
info: GPGNET: sending nat packet to 87.61.171.12:80
info: GPGNET: sending nat packet to 87.61.171.12:80
info: GPGNET: sending nat packet to 87.61.171.12:80
info: GPGNET: sending nat packet to 87.61.171.12:80
info: GPGNET: sending nat packet to 177.17.148.33:6112
info: GPGNET: sending nat packet to 177.17.148.33:6112
info: GPGNET: sending nat packet to 177.17.148.33:6112
info: GPGNET: sending nat packet to 177.17.148.33:6112
info: GPGNET: sending nat packet to 189.30.244.190:16010
info: GPGNET: sending nat packet to 189.30.244.190:16010
info: GPGNET: sending nat packet to 189.69.123.206:6112
info: GPGNET: sending nat packet to 189.69.123.206:6112
info: GPGNET: sending nat packet to 189.69.123.206:6112
info: GPGNET: sending nat packet to 189.69.123.206:6112
info: GPGNET: setting nat handler to 0x00000000
info: CNetTCPBuf::Read(): recv() failed: WSAEINTR
info: Run time: 0h00m09s
Only in death does duty end.
jhvisto
Crusader
 
Posts: 24
Joined: 27 Feb 2012, 21:09
Location: Finland/pori
Has liked: 0 time
Been liked: 0 time

Re: Unknown server action received

Postby Ze_PilOt » 28 Feb 2012, 14:44

info: GPGNET: sending nat packet to 87.61.171.12:80

That is VERY wrong. It it's not allowed.

First because port 80 is reserved for http connections, second because it's for TCP and not UDP, and mostly because port 0 to 1023 are reserved by the OS and can't be used by FA.

As it's the first packet you send, I guess this is the hoster of the game. That would explain why you can't join.

So you have to tell solskin to change is game port to 6112 or any other in about that range.
Nossa wrote:I've never played GPG or even heard of FA until FAF started blowing up.
User avatar
Ze_PilOt
Supreme Commander
 
Posts: 8985
Joined: 24 Aug 2011, 18:41
Location: fafland
Has liked: 18 times
Been liked: 376 times
FAF User Name: Ze_PilOt

Re: Unknown server action received

Postby jhvisto » 28 Feb 2012, 16:54

well that was only example of randomlog. more here:

Code: Select all
info: Hooked /lua/gamecolors.lua with /schook/lua/gamecolors.lua
info: /rating
info: GPGNET: setting nat handler to 0x221b1004
info: LOBBY: Game port 6112[UDP] opened.
info: LOBBY: starting with local uid of 14252 [jhvisto]
info: GPGNET: entering lobby state.
info: GPGNET: sending nat packet to 91.229.20.50:30351
info: GPGNET: sending nat packet to 94.175.4.16:6111
info: GPGNET: sending nat packet to 94.175.4.16:6111
info: NET: using deflate compression for sends to cpc10-hari12-2-0-cust15.hari.cable.virginmedia.com:6111.
info: LOBBY: Connecting to host "edizon" [cpc10-hari12-2-0-cust15.hari.cable.virginmedia.com:6111, uid=4953]
info: Can't add chat text -- no chat display
info: text="Connecting to game host..."
info: GPGNET: sending nat packet to 92.8.43.46:6112
info: GPGNET: sending nat packet to 92.8.43.46:6112
info: NET: using deflate compression for sends to host-92-8-43-46.as43234.net:6112.
info: LOBBY: Adding peer "CelticSoul" [host-92-8-43-46.as43234.net:6112, uid=1417]
info: Can't add chat text -- no chat display
info: text="Connecting to CelticSoul..."
info: GPGNET: received nat packet from 94.175.4.16:6111
info: GPGNET: received nat packet from 94.175.4.16:6111
info: GPGNET: received nat packet from 92.8.43.46:6112
info: GPGNET: received nat packet from 92.8.43.46:6112
info: GPGNET: sending nat packet to 46.162.65.155:6112
info: GPGNET: sending nat packet to 46.162.65.155:6112
info: NET: using deflate compression for sends to c-46-162-65-155.cust.bredband2.com:6112.
info: LOBBY: Adding peer "Nantsu" [c-46-162-65-155.cust.bredband2.com:6112, uid=14261]
info: Can't add chat text -- no chat display
info: text="Connecting to Nantsu..."
info: Minimized false
info: GPGNET: sending nat packet to 94.175.4.16:6111
info: GPGNET: sending nat packet to 94.175.4.16:6111
info: GPGNET: sending nat packet to 94.175.4.16:6111
info: GPGNET: sending nat packet to 94.175.4.16:6111
info: GPGNET: sending nat packet to 92.8.43.46:6112
info: GPGNET: sending nat packet to 92.8.43.46:6112
info: GPGNET: sending nat packet to 92.8.43.46:6112
info: GPGNET: sending nat packet to 92.8.43.46:6112
info: Minimized true
info: GPGNET: received nat packet from 46.162.65.155:6112
info: GPGNET: received nat packet from 46.162.65.155:6112
info: GPGNET: sending nat packet to 46.162.65.155:6112
info: GPGNET: sending nat packet to 46.162.65.155:6112
info: GPGNET: sending nat packet to 46.162.65.155:6112
info: GPGNET: sending nat packet to 46.162.65.155:6112
info: Minimized false
info: GPGNET: sending nat packet to 46.162.65.155:6112
info: GPGNET: sending nat packet to 46.162.65.155:6112
info: NET: using deflate compression for sends to c-46-162-65-155.cust.bredband2.com:6112.
info: LOBBY: Adding peer "Nantsu" [c-46-162-65-155.cust.bredband2.com:6112, uid=14261]
info: Can't add chat text -- no chat display
info: text="Connecting to Nantsu..."
info: GPGNET: received nat packet from 46.162.65.155:6112
info: GPGNET: received nat packet from 46.162.65.155:6112
info: GPGNET: sending nat packet to 46.162.65.155:6112
info: GPGNET: sending nat packet to 46.162.65.155:6112
info: GPGNET: sending nat packet to 46.162.65.155:6112
info: GPGNET: sending nat packet to 46.162.65.155:6112
info: Minimized true
info: GPGNET: sending nat packet to 46.162.65.155:6112
info: GPGNET: sending nat packet to 46.162.65.155:6112
info: NET: using deflate compression for sends to c-46-162-65-155.cust.bredband2.com:6112.
info: LOBBY: Adding peer "Nantsu" [c-46-162-65-155.cust.bredband2.com:6112, uid=14261]
info: Can't add chat text -- no chat display
info: text="Connecting to Nantsu..."
info: GPGNET: received nat packet from 46.162.65.155:6112
info: GPGNET: received nat packet from 46.162.65.155:6112
info: GPGNET: sending nat packet to 46.162.65.155:6112
info: GPGNET: sending nat packet to 46.162.65.155:6112
info: GPGNET: sending nat packet to 46.162.65.155:6112
info: GPGNET: sending nat packet to 46.162.65.155:6112
info: CNetTCPBuf::Read(): recv() failed: WSAEINTR
info: Run time: 0h01m43s


ports are right but after waited, ~2 min and aborted, still nothing, this happenes every time i try toi join game, it just sending and receiving nat packets and doesn't do anything. only button abort, works like it should be.
Only in death does duty end.
jhvisto
Crusader
 
Posts: 24
Joined: 27 Feb 2012, 21:09
Location: Finland/pori
Has liked: 0 time
Been liked: 0 time

Re: Unknown server action received

Postby Ze_PilOt » 28 Feb 2012, 17:11

You seems to receive UDP correctly (the receive packets messages), so my guess is that you block sending packets. Otherwise, you would connect and have a lot more of receive/sending messages.
Nossa wrote:I've never played GPG or even heard of FA until FAF started blowing up.
User avatar
Ze_PilOt
Supreme Commander
 
Posts: 8985
Joined: 24 Aug 2011, 18:41
Location: fafland
Has liked: 18 times
Been liked: 376 times
FAF User Name: Ze_PilOt

Re: Unknown server action received

Postby jhvisto » 28 Feb 2012, 23:17

i do not know anymore what could block, my testserver is at [url]jhvisto.dyndns.org[/url] and it works now fine, after serious telnetting to modem and code: ip nat loopback on. so port 80 is open to another pc with apahce, also other ports are open to this pc, 6112, 9103, 30350-30351. Still nothing,
Last try was here:
Code: Select all
info: GPGNET: setting nat handler to 0x1147b004
info: LOBBY: Game port 6112[UDP] opened.
info: LOBBY: starting with local uid of 14252 [jhvisto]
info: GPGNET: entering lobby state.
info: GPGNET: sending nat packet to 91.229.20.50:30351
info: GPGNET: sending nat packet to 217.140.180.11:6112
info: GPGNET: sending nat packet to 217.140.180.11:6112
info: NET: using deflate compression for sends to pc-180-11.cable.aina.net:6112.
info: LOBBY: Connecting to host "Chosen" [pc-180-11.cable.aina.net:6112, uid=224]
info: Can't add chat text -- no chat display
info: text="Connecting to game host..."
info: GPGNET: received nat packet from 94.21.72.255:30351
info: GPGNET: received nat packet from 94.21.72.255:30351
info: GPGNET: received nat packet from 217.140.180.11:6112
info: GPGNET: received nat packet from 217.140.180.11:6112
info: GPGNET: received nat packet from 46.162.65.155:6112
info: GPGNET: received nat packet from 46.162.65.155:6112
info: NET: using deflate compression for sends to 94-21-72-255.pool.digikabel.hu:30351.
info: NET: using deflate compression for sends to 81-175-231-184.bb.dnainternet.fi:6112.
info: NET: using deflate compression for sends to c-46-162-65-155.cust.bredband2.com:6112.
info: NET: using deflate compression for sends to catv-80-99-156-136.catv.broadband.hu:60399.
info: NET: using deflate compression for sends to bas7-hamilton14-1279491014.dsl.bell.ca:6112.
info: NET: using deflate compression for sends to 60-241-64-10.static.tpgi.com.au:6112.
info: NET: using deflate compression for sends to 99-119-188-233.lightspeed.hstntx.sbcglobal.net:6112.
info: LOBBY: rejecting unexpected connection from 94-21-72-255.pool.digikabel.hu:30351
info: LOBBY: rejecting unexpected connection from 81-175-231-184.bb.dnainternet.fi:6112
info: LOBBY: rejecting unexpected connection from c-46-162-65-155.cust.bredband2.com:6112
info: LOBBY: rejecting unexpected connection from catv-80-99-156-136.catv.broadband.hu:60399
info: LOBBY: rejecting unexpected connection from bas7-hamilton14-1279491014.dsl.bell.ca:6112
info: LOBBY: rejecting unexpected connection from 60-241-64-10.static.tpgi.com.au:6112
info: LOBBY: rejecting unexpected connection from 99-119-188-233.lightspeed.hstntx.sbcglobal.net:6112
info: GPGNET: received nat packet from 217.140.180.11:6112
info: GPGNET: received nat packet from 217.140.180.11:6112
info: GPGNET: received nat packet from 76.67.123.198:6112
info: GPGNET: received nat packet from 76.67.123.198:6112
info: GPGNET: received nat packet from 99.119.188.233:6112
info: GPGNET: received nat packet from 99.119.188.233:6112
info: GPGNET: received nat packet from 81.175.231.184:6112
info: GPGNET: received nat packet from 81.175.231.184:6112
info: GPGNET: received nat packet from 80.99.156.136:60399
info: GPGNET: received nat packet from 80.99.156.136:60399
info: GPGNET: received nat packet from 60.241.64.10:6112
info: GPGNET: received nat packet from 60.241.64.10:6112
info: GPGNET: received nat packet from 217.140.180.11:6112
info: GPGNET: received nat packet from 217.140.180.11:6112
info: GPGNET: sending nat packet to 99.119.188.233:6112
info: GPGNET: sending nat packet to 99.119.188.233:6112
info: NET: using deflate compression for sends to 99-119-188-233.lightspeed.hstntx.sbcglobal.net:6112.
info: LOBBY: Adding peer "commanderdrvr" [99-119-188-233.lightspeed.hstntx.sbcglobal.net:6112, uid=12767]
info: Can't add chat text -- no chat display
info: text="Connecting to commanderdrvr..."
info: GPGNET: sending nat packet to 60.241.64.10:6112
info: GPGNET: sending nat packet to 60.241.64.10:6112
info: NET: using deflate compression for sends to 60-241-64-10.static.tpgi.com.au:6112.
info: LOBBY: Adding peer "Anaryl" [60-241-64-10.static.tpgi.com.au:6112, uid=7417]
info: Can't add chat text -- no chat display
info: text="Connecting to Anaryl..."
info: GPGNET: sending nat packet to 81.175.231.184:6112
info: GPGNET: sending nat packet to 81.175.231.184:6112
info: NET: using deflate compression for sends to 81-175-231-184.bb.dnainternet.fi:6112.
info: LOBBY: Adding peer "Jor" [81-175-231-184.bb.dnainternet.fi:6112, uid=308]
info: Can't add chat text -- no chat display
info: text="Connecting to Jor..."
info: GPGNET: sending nat packet to 94.21.72.255:30351
info: GPGNET: sending nat packet to 94.21.72.255:30351
info: NET: using deflate compression for sends to 94-21-72-255.pool.digikabel.hu:30351.
info: LOBBY: Adding peer "Mumee" [94-21-72-255.pool.digikabel.hu:30351, uid=13289]
info: Can't add chat text -- no chat display
info: text="Connecting to Mumee..."
info: GPGNET: sending nat packet to 94.21.72.255:30351
info: GPGNET: sending nat packet to 94.21.72.255:30351
info: GPGNET: sending nat packet to 94.21.72.255:30351
info: GPGNET: sending nat packet to 94.21.72.255:30351
info: GPGNET: sending nat packet to 46.162.65.155:6112
info: GPGNET: sending nat packet to 46.162.65.155:6112
info: GPGNET: sending nat packet to 46.162.65.155:6112
info: GPGNET: sending nat packet to 46.162.65.155:6112
info: GPGNET: sending nat packet to 76.67.123.198:6112
info: GPGNET: sending nat packet to 76.67.123.198:6112
info: NET: using deflate compression for sends to bas7-hamilton14-1279491014.dsl.bell.ca:6112.
info: LOBBY: Adding peer "VoiceofReason" [bas7-hamilton14-1279491014.dsl.bell.ca:6112, uid=1309]
info: Can't add chat text -- no chat display
info: text="Connecting to VoiceofReason..."
info: GPGNET: sending nat packet to 80.99.156.136:60399
info: GPGNET: sending nat packet to 80.99.156.136:60399
info: NET: using deflate compression for sends to catv-80-99-156-136.catv.broadband.hu:60399.
info: LOBBY: Adding peer "eldariel" [catv-80-99-156-136.catv.broadband.hu:60399, uid=13503]
info: Can't add chat text -- no chat display
info: text="Connecting to eldariel..."
info: GPGNET: sending nat packet to 46.162.65.155:6112
info: GPGNET: sending nat packet to 46.162.65.155:6112
info: NET: using deflate compression for sends to c-46-162-65-155.cust.bredband2.com:6112.
info: LOBBY: Adding peer "Nantsu" [c-46-162-65-155.cust.bredband2.com:6112, uid=14261]
info: Can't add chat text -- no chat display
info: text="Connecting to Nantsu..."
info: GPGNET: sending nat packet to 99.119.188.233:6112
info: GPGNET: sending nat packet to 99.119.188.233:6112
info: GPGNET: sending nat packet to 99.119.188.233:6112
info: GPGNET: sending nat packet to 99.119.188.233:6112
info: GPGNET: sending nat packet to 81.175.231.184:6112
info: GPGNET: sending nat packet to 81.175.231.184:6112
info: GPGNET: sending nat packet to 81.175.231.184:6112
info: GPGNET: sending nat packet to 81.175.231.184:6112
info: GPGNET: sending nat packet to 80.99.156.136:60399
info: GPGNET: sending nat packet to 80.99.156.136:60399
info: GPGNET: sending nat packet to 80.99.156.136:60399
info: GPGNET: sending nat packet to 80.99.156.136:60399
info: GPGNET: sending nat packet to 60.241.64.10:6112
info: GPGNET: sending nat packet to 60.241.64.10:6112
info: GPGNET: sending nat packet to 60.241.64.10:6112
info: GPGNET: sending nat packet to 60.241.64.10:6112
info: GPGNET: received nat packet from 80.99.156.136:60399
info: GPGNET: received nat packet from 80.99.156.136:60399
info: GPGNET: sending nat packet to 80.99.156.136:60399
info: GPGNET: sending nat packet to 80.99.156.136:60399
info: GPGNET: received nat packet from 76.67.123.198:6112
info: GPGNET: received nat packet from 76.67.123.198:6112
info: GPGNET: sending nat packet to 80.99.156.136:60399
info: GPGNET: sending nat packet to 80.99.156.136:60399
info: GPGNET: received nat packet from 80.99.156.136:60399
info: GPGNET: received nat packet from 80.99.156.136:60399
info: GPGNET: received nat packet from 99.119.188.233:6112
info: GPGNET: received nat packet from 99.119.188.233:6112
info: GPGNET: received nat packet from 80.99.156.136:60399
info: GPGNET: received nat packet from 80.99.156.136:60399
info: GPGNET: received nat packet from 80.99.156.136:60399
info: GPGNET: received nat packet from 80.99.156.136:60399
info: GPGNET: received nat packet from 80.99.156.136:60399
info: GPGNET: received nat packet from 80.99.156.136:60399
info: GPGNET: received nat packet from 80.99.156.136:60399
info: GPGNET: received nat packet from 80.99.156.136:60399
info: GPGNET: received nat packet from 80.99.156.136:60399
info: GPGNET: received nat packet from 80.99.156.136:60399
info: GPGNET: received nat packet from 99.119.188.233:6112
info: GPGNET: received nat packet from 99.119.188.233:6112
info: GPGNET: sending nat packet to 80.99.156.136:60399
info: GPGNET: sending nat packet to 80.99.156.136:60399
info: GPGNET: sending nat packet to 80.99.156.136:60399
info: GPGNET: sending nat packet to 80.99.156.136:60399
info: GPGNET: sending nat packet to 99.119.188.233:6112
info: GPGNET: sending nat packet to 99.119.188.233:6112
info: GPGNET: sending nat packet to 99.119.188.233:6112
info: GPGNET: sending nat packet to 99.119.188.233:6112
info: GPGNET: sending nat packet to 80.99.156.136:60399
info: GPGNET: sending nat packet to 80.99.156.136:60399
info: GPGNET: sending nat packet to 80.99.156.136:60399
info: GPGNET: sending nat packet to 80.99.156.136:60399
info: GPGNET: sending nat packet to 80.99.156.136:60399
info: GPGNET: sending nat packet to 80.99.156.136:60399
info: GPGNET: sending nat packet to 80.99.156.136:60399
info: GPGNET: sending nat packet to 80.99.156.136:60399
info: GPGNET: received nat packet from 80.99.156.136:60399
info: GPGNET: received nat packet from 80.99.156.136:60399
info: GPGNET: received nat packet from 76.67.123.198:6112
info: GPGNET: received nat packet from 76.67.123.198:6112
info: GPGNET: received nat packet from 80.99.156.136:60399
info: GPGNET: received nat packet from 80.99.156.136:60399
info: GPGNET: received nat packet from 80.99.156.136:60399
info: GPGNET: received nat packet from 80.99.156.136:60399
info: GPGNET: received nat packet from 99.119.188.233:6112
info: GPGNET: received nat packet from 99.119.188.233:6112
info: GPGNET: sending nat packet to 99.119.188.233:6112
info: GPGNET: sending nat packet to 99.119.188.233:6112
info: GPGNET: sending nat packet to 99.119.188.233:6112
info: GPGNET: sending nat packet to 99.119.188.233:6112
info: GPGNET: received nat packet from 99.119.188.233:6112
info: GPGNET: received nat packet from 99.119.188.233:6112
info: GPGNET: received nat packet from 99.119.188.233:6112
info: GPGNET: received nat packet from 99.119.188.233:6112
info: GPGNET: received nat packet from 60.241.64.10:6112
info: GPGNET: received nat packet from 60.241.64.10:6112
info: GPGNET: sending nat packet to 99.119.188.233:6112
info: GPGNET: sending nat packet to 99.119.188.233:6112
info: GPGNET: sending nat packet to 99.119.188.233:6112
info: GPGNET: sending nat packet to 99.119.188.233:6112
info: GPGNET: sending nat packet to 99.119.188.233:6112
info: GPGNET: sending nat packet to 99.119.188.233:6112
info: GPGNET: sending nat packet to 99.119.188.233:6112
info: GPGNET: sending nat packet to 99.119.188.233:6112
info: GPGNET: sending nat packet to 60.241.64.10:6112
info: GPGNET: sending nat packet to 60.241.64.10:6112
info: GPGNET: sending nat packet to 60.241.64.10:6112
info: GPGNET: sending nat packet to 60.241.64.10:6112
info: GPGNET: received nat packet from 99.119.188.233:6112
info: GPGNET: received nat packet from 99.119.188.233:6112
info: GPGNET: received nat packet from 99.119.188.233:6112
info: GPGNET: received nat packet from 99.119.188.233:6112
info: GPGNET: received nat packet from 99.119.188.233:6112
info: GPGNET: received nat packet from 99.119.188.233:6112
info: GPGNET: received nat packet from 99.119.188.233:6112
info: GPGNET: received nat packet from 99.119.188.233:6112
info: GPGNET: received nat packet from 99.119.188.233:6112
info: GPGNET: received nat packet from 99.119.188.233:6112
info: GPGNET: received nat packet from 60.241.64.10:6112
info: GPGNET: received nat packet from 60.241.64.10:6112
info: GPGNET: received nat packet from 60.241.64.10:6112
info: GPGNET: received nat packet from 60.241.64.10:6112
info: GPGNET: received nat packet from 60.241.64.10:6112
info: GPGNET: received nat packet from 60.241.64.10:6112
info: GPGNET: received nat packet from 60.241.64.10:6112
info: GPGNET: received nat packet from 60.241.64.10:6112
info: GPGNET: received nat packet from 60.241.64.10:6112
info: GPGNET: received nat packet from 60.241.64.10:6112
info: GPGNET: sending nat packet to 60.241.64.10:6112
info: GPGNET: sending nat packet to 60.241.64.10:6112
info: GPGNET: sending nat packet to 60.241.64.10:6112
info: GPGNET: sending nat packet to 60.241.64.10:6112
info: GPGNET: sending nat packet to 60.241.64.10:6112
info: GPGNET: sending nat packet to 60.241.64.10:6112
info: GPGNET: sending nat packet to 60.241.64.10:6112
info: GPGNET: sending nat packet to 60.241.64.10:6112
info: GPGNET: sending nat packet to 60.241.64.10:6112
info: GPGNET: sending nat packet to 60.241.64.10:6112
info: GPGNET: sending nat packet to 60.241.64.10:6112
info: GPGNET: sending nat packet to 60.241.64.10:6112
info: GPGNET: received nat packet from 60.241.64.10:6112
info: GPGNET: received nat packet from 60.241.64.10:6112
info: GPGNET: received nat packet from 60.241.64.10:6112
info: GPGNET: received nat packet from 60.241.64.10:6112
info: GPGNET: received nat packet from 60.241.64.10:6112
info: GPGNET: received nat packet from 60.241.64.10:6112
info: GPGNET: received nat packet from 60.241.64.10:6112
info: GPGNET: received nat packet from 60.241.64.10:6112
info: Minimized true
info: Minimized false
info: Minimized true
info: Minimized false
info: GPGNET: setting nat handler to 0x00000000
info: CNetTCPBuf::Read(): recv() failed: WSAEINTR
info: Run time: 0h02m24s


now there are those rejecting messages, how that can be?
Only in death does duty end.
jhvisto
Crusader
 
Posts: 24
Joined: 27 Feb 2012, 21:09
Location: Finland/pori
Has liked: 0 time
Been liked: 0 time

Next

Return to Tech Support

Who is online

Users browsing this forum: No registered users and 1 guest