Page 1 of 1

Everyone Going NR?

Posted: Wed Jan 02, 2008 1:12 am
by OPTIMUSprime
This has started to happen for about 1-2 weeks now. It happens on nearlly every map. Itssss Fustrating! Plzz Help

Posted: Wed Jan 02, 2008 1:19 am
by silver surfer
It means not reseaving...meaning that something is wrong with your computer... the server your on... or the other persons computer

Posted: Wed Jan 02, 2008 1:54 am
by A Meteorite
silver surfer wrote:It means not reseaving...meaning that something is wrong with your computer... the server your on... or the other persons computer
I assume you mean "receiving." If so, not at all. Please don't post on issues that you are not sure about.

This problem has already been discussed and others have this same problem. This person here seems to have well researched the problem and made an informative conclusion (although I have not personally verified it nor has a dev verified it): http://my.bzflag.org/bb/viewtopic.php?p=119276#119276
sp unit 262 wrote:I just realized what the exact problem and the solution to it is.

BZFlag use two protocols to communicate between the client and the sever, TCP and UDP.
The wiki entry on the Network Protocol is out dated but the basic should be the same. You should read the "Client/Server Communication" and " Client/Client Communication".
http://my.bzflag.org/w/Network_Protocol

The problem is that router only forward packet from a server if a computer inside the network has sent a packet recently. I believe what is happening is that the UDP connection is being cut because the client doesn't send packets over the UDP connection unless the tank deviates from what DR would suggest (and if your dead or an observer there is no tank). The reason the TCP connection doesn't get cut is because you have tell the sever that the packet has been received (by sending a packet).

The solution is to have the client send a keep-alive packet ever minute or so if it hasn't sent any data in the past minute.
By the way, I too, had this problem on my D-Link router (which seems to cause others trouble as well). I can not recall if my homemade pfSense router has this problem, but in either case it is definitely not a problem with your computer or the server.

Posted: Wed Jan 02, 2008 1:59 am
by ducktape
Are you talking about When in Observer or playing? I know A Meteorite probably already fixed your problem but i would just like to know.

Posted: Wed Jan 02, 2008 2:00 am
by blast
NR means "Not Responding".

Posted: Wed Jan 02, 2008 5:42 am
by Sky King
I want to make sure too that we're not mixing apples and oranges here...

I have noticed on several servers over the past week where I see everyone as [nr]... and when I leave and rejoin the server, it turns out that 2/3 of all the players got booted. My point being that the [nr] issue may not be on your end at all.

Interestingly, each time it has happened, the following have been true:
1. A reasonable number of people, usually about one third, seem to survive the hiccup just fine; and
2. It affects different players differently. For some, the BZ client closed, for others, they just see everyone as [nr], and for others, the client freezes. It happened last night on missile wars, and we tried to determine if there was any OS or client version correlation to how each person was affected, but no pattern was found.

Posted: Wed Jan 02, 2008 6:04 am
by ducktape
blast wrote:NR means "Not Responding".
Oh sorry I didnt specify, I meant Is everyone go NR while you are playing or when you are in observer?

Posted: Wed Jan 02, 2008 3:42 pm
by too much loving
It is possible that your internet connection is unstable and that you temporarily lose connection to the internet. (I have this problem at home)

Next time everyone goes [NR], try to exit bzflag and open a random webpage in a internet explorer. If internet explorer complaints that it cannot access the webpage, then your internet connection is probably unstable.

Posted: Wed Jan 02, 2008 4:58 pm
by ZGMF-X20A Strike Freedom
i get nr when either the server goes down or my internet goes. Sometimes though i have had the problem occour only with certain other players and i assume its to do with their internet.

Hope that helped.

Posted: Thu Jan 03, 2008 10:23 am
by OPTIMUSprime
I Pretty Sure i Fixed it. It has to do with your Router Network. As soon As i Unplugged My Router and Directed straight from Modem to Computer My InternetEx. Starts working, Bz starts Working Fine.

Contact Your IP if you still have problems.

Posted: Thu Jan 03, 2008 7:04 pm
by Teppic
too much loving wrote:It is possible that your internet connection is unstable and that you temporarily lose connection to the internet. (I have this problem at home)
I get this with my modem too, treat it as an invitation to get really close to that annoying camper, then wait for the connection to re-establish :P

Posted: Fri Jan 04, 2008 12:41 am
by OPTIMUSprime
The Connection Re-Establishes? lol. I Haven't put up with Going "NR" long enough to Relise is Re-Connects

Posted: Fri Jan 04, 2008 1:07 am
by Wreckage
On the occasion that happens to me, it usually does re-establish within 20 seconds. Only a couple times it does not.

Re: Everyone Going NR?

Posted: Fri Jan 04, 2008 3:06 am
by Wabbits With A Laptop
I keep on getting kicked out of every server because everyone becomes NR once I spawn.Any ways to fix that problem??????

Posted: Fri Jan 04, 2008 4:51 am
by OPTIMUSprime
wabbitswithalaptop Are you running Off a Router Network?

Posted: Fri Jan 04, 2008 10:11 pm
by Wabbits With A Laptop
OPTIMUSprime, what do you mean?

Posted: Sat Jan 05, 2008 12:36 am
by anomaly
One reason this could be a router issue for you is that TCP is a connection based protocol and UDP is not. As long as there is a TCP connection (you are connected to the bzflag server) the router will keep the port open for TCP. But UDP will require packets to be somewhat continuous to keep the connection "alive". If you don't move or fire for awhile its possible that the port closing for UDP traffic on your router's firewall. After some seconds it may re-open the port for UDP and NR's will start responding again. This is essentually what sp unit 262 was saying. TCP will wait for a response to complete a transaction, but UDP doesn't require any response.

You may be able to search the forums or the modem/router manufacturer's web site for info.

Posted: Sat Jan 05, 2008 4:42 am
by OPTIMUSprime
Do Youhave a Router thatYou connected to, instead of just straight from modem to computer?