Official forums for BZFlag.org

Whenever I go in as observer mode, after like 5 minutes it says that everyone is NR, and on the radar and screen, everything is floating around and other crap like that. Any suggestions?

Mine has done that for like forever

I realize this is an ancient topic but I have the same problem.

Any fix for this?

A search of the sourceforge tracker found a three year old bug report:
http://sourceforge.net/tracker/index.ph ... tid=103248

this happens to me

Nothing. And none of the posts on this page have done anything to help c2water solve his problem.

I think it's something to do with your connection, if I'm not mistaken. Every time this happens to me, my dns server is down.

I have a router that might be causing it. I've tried activating something called DMZ on the router's web interface for the computer I have the client on but everything still goes NR after about 4 minutes. The DMZ feature is what I use to expose my server when I'm running it.

What router are you using when it happens? When my Linksys/Cisco is on, it does not happen. Only with the D-Link router does it occur, it has to do with how D-Link handles low-priority packets I have heard.

Yep - I have heard that it is D-Link's router's problem. Happens to me with my router (which is D-Link).

-Tanner

Yes! It is D-Link. Is there any workaround?

I, too, have a D-Link and have experienced the not responding problem. At one point, I never became NR, and then it started back up again. I don't know what changed in my D-Link router, but it has made me believe there is a reason that causes it, and is fixable.

Either that, or I'm losing my mind.

that used to happen to me too...but i was using a netgear router, not a d-link.

it hasnt happened since i started using a linksys one (wrt54g)

I just started having that problem day before yesterday, but it's consistent now. I can only observe for about five minutes before other players randomly go in and our of NR (note that I never fully disconnect - I still get a very few player updates)

guys this topic is 2 frigen years old!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! bet that feels embarasing

You weren't even born yet, were you?

chicken fingers wrote:guys this topic is 2 frigen years old!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! bet that feels embarasing

Yeah, I can't imagine what it feels like to type in bold AND underlined text.

Ziiing!

omg jees ya guys can't give it a break i bet the guy doesen't even play anymore jeese this topic is so frigen old just let it go im more than 2 year old by a ligshot and im emphasising those words with bold underline.

Actually, that looks kinda fun. Let me try that!

WE WOULD ALL APPRECIATE IF VERY MUCH IF YOU SPELLED YOUR WORDS CORRECTLY, OR AT LEAST MADE A VALID ATTEMPT AT IT. USING INCORRECT GRAMMAR IS ONLY CUTE TO YOUR MOTHER.

(!!!!?!!!111one*bang*!!!)

Seriously, you can do whatever you like (although there is a risk of your posts being deleted). People who ask you to use good English are really trying to help you out.

QuantumBeep

what router are you using? I have this same issue with d-link, an IIRC its rather unfixable, its a router time-out problem

chicken fingers wrote:guys this topic is 2 frigen years old!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! bet that feels embarasing

It was revived by someone who said:
"I realize this is an ancient topic but I have the same problem."
They were asking if anyone had found a solution to the problem in the last 2 years, since clearly, the original poster wasn't the only one looking for help.

ooh...burn

anyway, you should try disabling as much of your firewall as possible (open port 5154, turn off SPI, make sure "respond to pings on internet port" is on, etc.)

My router is an SMC - it's got some age on it, so I can easily see it being a defect, bug, or even outright breakage.

Tanner wrote:Yep - I have heard that it is D-Link's router's problem. Happens to me with my router (which is D-Link).

-Tanner

i have that problem on router "Netgear 802.11g FWG114P"

I suspect that, if you were to put in the effort to research it, you'd find that a single model of support chip for wireless routers would be at fault; probably a network controller chip, not a router CPU/flash ROM.

In other words, all the routers that have this flaw probably use the same flawed chip.

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.