S
]SK[
Guest
Ive been testing wireless for our company who is looking at putting (a) game server(s) on a wireless network for gamers to use their wireless broadband connection to erm... game.
I currently have an ADSL connection at home with me connecting to it via wireless with 100% Signal Strength and 100% Quality (It is like 3 inches away from other wireless product. Now during gaming the game seems fine but after a while I notice nades and other things kill me when im out of range of them. EG nade kills me when ive blatently gone past it.
Is this me or anyone else get same kinda thing. I mean with decent replies why should that be?
C:\>ping 192.168.1.100
Pinging 192.168.1.100 with 32 bytes of data:
Reply from 192.168.1.100: bytes=32 time<10ms TTL=64
Reply from 192.168.1.100: bytes=32 time<10ms TTL=64
Reply from 192.168.1.100: bytes=32 time<10ms TTL=64
Reply from 192.168.1.100: bytes=32 time<10ms TTL=64
Ping statistics for 192.168.1.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
I currently have an ADSL connection at home with me connecting to it via wireless with 100% Signal Strength and 100% Quality (It is like 3 inches away from other wireless product. Now during gaming the game seems fine but after a while I notice nades and other things kill me when im out of range of them. EG nade kills me when ive blatently gone past it.
Is this me or anyone else get same kinda thing. I mean with decent replies why should that be?
C:\>ping 192.168.1.100
Pinging 192.168.1.100 with 32 bytes of data:
Reply from 192.168.1.100: bytes=32 time<10ms TTL=64
Reply from 192.168.1.100: bytes=32 time<10ms TTL=64
Reply from 192.168.1.100: bytes=32 time<10ms TTL=64
Reply from 192.168.1.100: bytes=32 time<10ms TTL=64
Ping statistics for 192.168.1.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms