There's a new version of War2Observe that fixes the crash issue,
download from the downloads page today!
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Static IP. wireless net gear router. IPv4 address stays the same
Hahaha, I think most people on the server pay taxes TK.
you been playing ff7? they got ff9 out now on steam.gtfo from this thread you stupid bitch. start a thread about ff7, ff9 or pm him. dumb whore
The admins do us good when we get banned. It's a blessing in reality!this is a thread about sepi and his banStfu, this is a thread about sepi and his banIf I mentioned your chickens it would all be better then?
Thank you!
Sorry, I haven't Tapatalk and like programs.
OK so I fired up the router (it's a NETGEAR WNDR4500) and discovered I had reflashed the stock firmware before mothballing it, so I put DD-WRT back on it, probably better to start from a clean install anyway. Its build 26138 – about 18 months old.
After the standard setup stuff – gateway address, DHCP, DNS etc. I just plugged in the port (6112) and the local IP of my gaming machine (for the purposes of this exercise I called it 192.168.3.33) and I was able to host without issue. But... I'm not using a VPN so that may be a causing problems.
OK So…. Port forwarding:
It's in the NAT section. This is not actually network address translation, but from a coding perspective its right there in the part thats deciding where to send packets based on transport layer info (which is a big part of what NAT does), so it makes sense that it would be grouped there on the config page. The important thing is that 'port from' and 'port to' are both the same so nothing is being translated, its just sending everything stamped with a '6112' to LAN address 192.168.3.33. In fact this should safeguard the passage of port 6112 traffic through any NAT that the router is a party to, although it won't help you if somebody upstream is switching ports on you.
Some protocols can safely pass through NAT, or actually they would be totally destroyed by NAT so they are given a pass. Things like IPsec, so if you have an option to use one of these, it might help.
This is general discussion u know, not server related.
i hope youre not working in IT xDDDif IDLE_TIME > 6h then kick player to "away" channel
total number of non-bots = total - people_in_away_channel
OR just filter them off the list, numb nuts.
Sent from my Motorola DynaTAC 8000X using Tapatalk
