b91t test build posted

Moderators: GSH, VSMIT, Red Devil, Commando

User avatar
General BlackDragon
Flying Mauler
Posts: 2406
Joined: Sat Feb 19, 2011 6:37 am
Contact:

Re: b91t test build posted

Post by General BlackDragon » Sat Feb 09, 2013 10:03 am

Norton is evil.
Battlezone Classic Public Forums
*****General BlackDragon*****

User avatar
Zero Angel
Attila
Posts: 1536
Joined: Mon Feb 21, 2011 12:54 am
Contact:

Re: b91t test build posted

Post by Zero Angel » Sat Feb 09, 2013 12:45 pm

RubiconAlpha wrote:
Zero Angel wrote:I have noticed that my antivirus program does not like raknet at all and raknet will refuse to work while my antivirus is enabled.
Same here. Using Norton 360.
Avast! here.
Regulators
Regulate any stealin' of this biometal pool, we're damn good, too
But you can't be any geek off the street
Gotta be handy with the chains if you know what I mean
Earn your keep

Apollo
Sabre
Posts: 456
Joined: Sat Feb 19, 2011 9:51 pm

Re: b91t test build posted

Post by Apollo » Sat Feb 09, 2013 1:00 pm

Seems tobe working quite well, even on 56k. :)

Did you have to run a raknet session from your server GSH?
Activision anet servers for all legacy anet games: Anet Servers
BattleZone Club (Supporting BattleZone 1.4, The Red Odyssey, BattleZone Enhanced, BattleZone 1.5 and Bionite)
BattleZone 1 Community Since 2002

User avatar
Zero Angel
Attila
Posts: 1536
Joined: Mon Feb 21, 2011 12:54 am
Contact:

Re: b91t test build posted

Post by Zero Angel » Sat Feb 09, 2013 3:03 pm

Tried a few things. First tried toggling the punchthroughs in gameprefs. Didn't have any effect.

So I turned on verbose uPNP info and here are my results:

With Avast enabled

Code: Select all

DIAG|          UPNPThread:543  |08:56:57|14223  |List of UPNP devices found on the network :
DIAG|          UPNPThread:543  |08:56:57|14223  | desc: http://192.168.0.1:45556/wps_device.xml
 st: upnp:rootdevice
DIAG|          UPNPThread:543  |08:56:57|14224  | desc: http://192.168.0.1:45555/wps_device.xml
 st: upnp:rootdevice
DIAG|          UPNPThread:543  |08:56:57|14239  |UPnP device found. Is it an IGD ? : http://192.168.0.1:45556/
DIAG|          UPNPThread:543  |08:56:57|14239  |Trying to continue anyway
DIAG|          UPNPThread:543  |08:56:57|14239  |Local LAN ip address : 192.168.0.102
DIAG| RaknetServerBrowser:173  |08:56:58|14786  |Raknet master server returned blank data. Nothing to fill in a server list from :( 
DIAG|         WSInterface:212  |08:56:58|14794  |Determined private IP address: 192.168.0.102
With Avast disabled, I was able to see Red Devil's game.

Code: Select all

DIAG|          UPNPThread:543  |08:59:03|13111  |List of UPNP devices found on the network :
DIAG|          UPNPThread:543  |08:59:03|13111  | desc: http://192.168.0.1:45556/wps_device.xml
 st: uuid:9ae5b61a-0cd4-25c6-553c-9094e4fd5507
DIAG|          UPNPThread:543  |08:59:03|13112  | desc: http://192.168.0.1:45556/wps_device.xml
 st: upnp:rootdevice
DIAG|          UPNPThread:543  |08:59:03|13126  |UPnP device found. Is it an IGD ? : http://192.168.0.1:45556/
DIAG|          UPNPThread:543  |08:59:03|13126  |Trying to continue anyway
DIAG|          UPNPThread:543  |08:59:03|13126  |Local LAN ip address : 192.168.0.102
DIAG|         WSInterface:212  |08:59:04|13458  |Determined private IP address: 192.168.0.102
I was also able to resolve the problem by adding Battlezone 2 as an exception for the 'web shield' module for Avast.
Regulators
Regulate any stealin' of this biometal pool, we're damn good, too
But you can't be any geek off the street
Gotta be handy with the chains if you know what I mean
Earn your keep

User avatar
Axeminister
Sabre
Posts: 442
Joined: Sat Feb 19, 2011 4:03 pm
Location: Texas, USA
Contact:

Re: b91t test build posted

Post by Axeminister » Sat Feb 09, 2013 3:25 pm

I have a game up for testing DM.
He who does not advance themselves, endlessly becomes themselves.

http://www.reverbnation.com/tunepak/3606640

yeah
Rattler
Posts: 84
Joined: Mon Mar 14, 2011 3:01 am

Re: b91t test build posted

Post by yeah » Sun Feb 10, 2013 1:02 am

Just a follow up on the natnegotiation error that i posted above and that was experienced by others as well.
After testing a bit with some other guys one likely explanation seems to be that this happens when a servers crashes or hangs while still being listed on raknet. With gamespy we got "could not connect" ot time out error or something like that (don't recall the exact wording) and it seems that with raknet this results in that natnegotiation error.

Another thing I noticed (but which might be an old problem) is problem with running a server and a client behid the same router. The server seems to run fine as long as only local clients or only clients from internet join, but if they mix the internet clients seems to lag out constantly. Also this seems to happen only within the game itself while the chat lobby seems to be fine.

Commando
Flying Mauler
Posts: 2176
Joined: Fri Feb 18, 2011 6:41 pm

Re: b91t test build posted

Post by Commando » Sun Feb 10, 2013 1:55 am

My crash attempting to join Yeah's game.

yeah
Rattler
Posts: 84
Joined: Mon Mar 14, 2011 3:01 am

Re: b91t test build posted

Post by yeah » Sun Feb 10, 2013 2:12 am

Commando wrote:My crash attempting to join Yeah's game.
you crashed/lagged out as soon as I had a local cient (behind the same router)joining the server otherwise you seemed to be doing fine.

User avatar
Juggernaut
Thunderbolt
Posts: 189
Joined: Sun Mar 13, 2011 8:12 pm

Re: b91t test build posted

Post by Juggernaut » Sun Feb 10, 2013 5:07 pm

No antivirus programs running.
Specs:
Windows 7 64bit
Linksys WRT54G wifi router with port forwards disabled, UPNP enabled.
Stock BZ2 install, 1.3 PB6.2 patched to B91t (Raknet).

Last night, I was getting: "natnegotiate failed: unknown error" when attempting to join Yeah's and Red Devil's servers. I was able to join Yeah's server however, by clicking Join IP button without issue. I could not connect to Red Devil's server via Join IP or Join Game buttons. "natnegotiate failed: unknown error" came up for Red Devil's either way. "natnegotiate failed: unknown error" only came up for Yeah's server if I clicked 'Join Game'.

This morning, I was able to join Yeah's server without issue, clicking on the Join Game button. I am still unable to connect to Red Devil's server. *NOTE* -> Red Devil's server's ping and player fields show up as '???'.

I tried hosting a game last night and this morning, I get: "Raknet client connect failing with status code 17" shortly after creating game.

Thank you GSH for working on this!!
Last edited by Juggernaut on Sun Feb 10, 2013 5:14 pm, edited 1 time in total.
Specs:
Win 10 Pro 64bit OS
i5 3570K @4.5Ghz CPU
16GB DDR31600 Corsair RAM
MSI Z77A-G41 MOBO
Crucial 256GB SSD | 500GB WD HDD
EVGA REF GTX-970 4GB ACX 2.1 GPU
27" LG D2743 Cinema 3D IPS LED @1920x1080 60Hz
ASUS Xonar DGX APU
Cable Internet - 35Mb/6Mb

User avatar
Cyber
Sabre
Posts: 202
Joined: Sun Feb 20, 2011 5:46 pm

Re: b91t test build posted

Post by Cyber » Sun Feb 10, 2013 5:14 pm

Win8 64bit, no antivirus.

I joined yeah's game, took a while but worked. I also saw Red Devil's host, but playerlist was empty and I couldn't join there.

I tried to set up a game too, but got code '16' and the game wasn't visible for others.

Thanks for working on it.
Teamspeak 3: teamspeak.com
TS3 Server(Ugonland): 74.91.115.34

User avatar
GSH
Patch Creator
Posts: 2481
Joined: Fri Feb 18, 2011 4:55 pm
Location: USA
Contact:

Re: b91t test build posted

Post by GSH » Sun Feb 10, 2013 7:09 pm

For now, if a b91t (BZ2+RakNet) server is behind a router that speaks UPNP, I strongly recommend that that server have UPNP on and any manual port forwarding of port 17770 off. Let UPNP do its work, and it's a lot simpler. If you're hosting, the UPNP state is now shown at the bottom of the create session name/password/message dialog-- and you want it to say "UPNP: Ports successfully redirected for hosting."

I've personally hosted many BZ2+RakNet (though other builds than b91t), had outside joiners as well as other machines on my LAN join that game. No lagouts, no problems. Once again, verify firewall settings : hardware and/or software -- wboth Windows Firewall and some antivirus programs could be breaking things.

Quick summary of status codes you're likely to see. There may be more data printed on the console if you hit control-~ to look.

16 : ID_CONNECTION_REQUEST_ACCEPTED (this is NOT an error!)
17 : ID_CONNECTION_ATTEMPT_FAILED
18 : ID_ALREADY_CONNECTED
19 : ID_NEW_INCOMING_CONNECTION (this is NOT an error!)
20 : ID_NO_FREE_INCOMING_CONNECTIONS
21 : ID_DISCONNECTION_NOTIFICATION
22 : ID_CONNECTION_LOST
23 : ID_CONNECTION_BANNED
24 : ID_INVALID_PASSWORD
25 : ID_INCOMPATIBLE_PROTOCOL_VERSION
26 : ID_IP_RECENTLY_CONNECTED
62 : ID_NAT_TARGET_NOT_CONNECTED
63 : ID_NAT_TARGET_UNRESPONSIVE
64 : ID_NAT_CONNECTION_TO_TARGET_LOST
65 : ID_NAT_ALREADY_IN_PROGRESS
66 : ID_NAT_PUNCHTHROUGH_FAILED
67 : ID_NAT_PUNCHTHROUGH_SUCCEEDED (not an error, this is NAT success)

-- GSH

yeah
Rattler
Posts: 84
Joined: Mon Mar 14, 2011 3:01 am

Re: b91t test build posted

Post by yeah » Sun Feb 10, 2013 7:20 pm

Just another follow up. I saw a people people joining the test server and mostly seem to work for them. However i think I restarted it twice. As in between i couldn't join it myself anymore. So if somebody tried to join during the restart he might have seen natnegotiation error. Another thing i just realized is that, when my internet connections drops shortly, which happens once a day by design and othewise rarely due to a short provider hiccup, then my new connection might get a new (dynamic) IP. In such a case my server is still running but it has the wrong IP registered RaKnet (at least temporary or even for good if BZ doesn't update raknet within a server session) and hence other players will most likely get a natnegotiation error too. All in all some of the natnegotiation errors might be due to the normal connectivity hiccups in the internet. No idea though whether that explains all or just some of them and at this point it is just an educated guees or speculation anyhow. In any case it is worth to test it several times, to makle sure that not a temporary connectivity issue or a stalled/crashed was the problem.
As far as Red devil is concerned i couln't join it again either and it is still listed with ??? instead of a ping number, but my guess is he hasn't restarted it yet.

User avatar
GSH
Patch Creator
Posts: 2481
Joined: Fri Feb 18, 2011 4:55 pm
Location: USA
Contact:

Re: b91t test build posted

Post by GSH » Sun Feb 10, 2013 8:48 pm

If you're hosting and walking away, I recommend increasing {BZ2InstallDir}\addon\config\GamePrefs.ini::UPNPTimeout:
// How long UPNP is registered with your local router (if it's enabled
// & working). I think this is in seconds. Default time of 21600 is
// 6 hours, which should work for most BZ2 games.
UPNPTimeout = 21600
One week is 604800 seconds.

-- GSH

User avatar
Juggernaut
Thunderbolt
Posts: 189
Joined: Sun Mar 13, 2011 8:12 pm

Re: b91t test build posted

Post by Juggernaut » Mon Feb 11, 2013 12:35 am

*UPDATE* FIXED!! -- I upgraded the firmware for the router listed below to: Firmware Version: v4.30.16 (from v4.30.7) --- this seems to have fixed my broken UPNP issue. I can now host, and below 'server message' before launch it says: "UPNP ports successfully redirected for hosting" (before the firmware it would fail). Upon launch I no longer get a raknet error in shell. UPNP is enabled by default, no port forwards exist. If others have issues with natneg aka upnp ports forwarding automatically "natnegotiate failed: unknown error", you may want to upgrade the firmware on your router. In my case, upnp is broken with the older firmware I was using on a very common router (Linksys wrt54gl).

Specs:
Clean install of BZ2 v1.3PB62 patched with b91t
Win 7 64 bit
Linksys wrt54gl v1.1 w/ upnp on and port forwarding off
Firmware Version: v4.30.7

I can join yeah's server fine.
If I host, others can see me, but get: "natnegotiate failed: unknown error" and cannot connect.

I still get: "natnegotiate failed: unknown error" when joining Red Devil's server.

When hosting, I see error "natnegotiate failed" status under server message before launch.
Upon launch, I get: "Raknet client connect failing with status code 17" in shell. Others can see me but cannot join. They get: "natnegotiate failed: unknown error"

If I forward my ports (17770-17772), people can join.
However, I still get natnegotiate failed listed under 'server message' before launch.
Upon launch, I get "Raknet client connect incoming with status code 16" (note, i get code 16 and 'incoming' vs 'failing' vs 17 if I forward ports). But others are able to join fine.

Another interesting thing I notice, is the host's IP is listed as their local IP address, not public (e.g. 192.168.1.101) when typing \ip in shell. The public IP is only listed when clicking the Join IP button.

Other things I tried, disabled QOS, ensured port forwards were disabled, UPNP to ON, and set my local adapter to DHCP (I usually set to static). Windows Firewall Off and or made sure bzone.exe was added to exception list. None of which made a difference.

I will try updating the firmware on the wrt54gl and report back. It's possible upnp is broke on my router, although it works for other programs. hmmm
Specs:
Win 10 Pro 64bit OS
i5 3570K @4.5Ghz CPU
16GB DDR31600 Corsair RAM
MSI Z77A-G41 MOBO
Crucial 256GB SSD | 500GB WD HDD
EVGA REF GTX-970 4GB ACX 2.1 GPU
27" LG D2743 Cinema 3D IPS LED @1920x1080 60Hz
ASUS Xonar DGX APU
Cable Internet - 35Mb/6Mb

yeah
Rattler
Posts: 84
Joined: Mon Mar 14, 2011 3:01 am

Re: b91t test build posted

Post by yeah » Mon Feb 11, 2013 6:18 am

Since this is very recent, it might be of interested here (security issues with upnp):

https://community.rapid7.com/community/ ... -dont-play
http://news.yahoo.com/exclusive-researc ... ector.html

Post Reply