ติดตั้ง Steam
เข้าสู่ระบบ
|
ภาษา
简体中文 (จีนตัวย่อ)
繁體中文 (จีนตัวเต็ม)
日本語 (ญี่ปุ่น)
한국어 (เกาหลี)
български (บัลแกเรีย)
Čeština (เช็ก)
Dansk (เดนมาร์ก)
Deutsch (เยอรมัน)
English (อังกฤษ)
Español - España (สเปน)
Español - Latinoamérica (สเปน - ลาตินอเมริกา)
Ελληνικά (กรีก)
Français (ฝรั่งเศส)
Italiano (อิตาลี)
Bahasa Indonesia (อินโดนีเซีย)
Magyar (ฮังการี)
Nederlands (ดัตช์)
Norsk (นอร์เวย์)
Polski (โปแลนด์)
Português (โปรตุเกส - โปรตุเกส)
Português - Brasil (โปรตุเกส - บราซิล)
Română (โรมาเนีย)
Русский (รัสเซีย)
Suomi (ฟินแลนด์)
Svenska (สวีเดน)
Türkçe (ตุรกี)
Tiếng Việt (เวียดนาม)
Українська (ยูเครน)
รายงานปัญหาเกี่ยวกับการแปลภาษา
Simple NAT aka one-to-one NAT. I'm not a fan of leaving ports permanently open or having to disable and re-enable port forwarding rules every time I want to play and then quit. This is why I like port triggering but it seems that port triggering won't work with WA unfortunately.
My problem is that I, like most people behind a router, do use DHCP. Also, unless I'm mistaken, doesn't port forwarding leave the forwarded ports open (as long as the rule is enabled)?
I've been using the the WormKit NAT module that uses a proxy server in France; it would be nice if there was a solution that didn't involve using a proxy server, especially one in another country, or having to forward port(s).
PS I recognize your alias, and as I have just started playing WA again, it's neat to see that you're still developing various tools and patches for the Worms universe, many thanks!
Er, yes; what's the issue with this? If you're using a NAT as a firewall, you're Doing It Wrong.
Assuming you don't use IRC, have you tried it with the trigger port of 6667?
Please try this module:
http://dump.thecybershadow.net/12f9e36a797c74325bc68fec6b2d8974/wkPortTrigger.zip
When W:A starts listening on a port, it connects to the same server/port as the WormNAT2 module (proxy.worms2d.info, port 17018), but doesn't do anything else.
I've seen somewhere that you have to open 17010 17011 17012 6667 and 1007 in TCP/UDP
I'm not sure you have to open all of the 5 ports but it works for me
1. The ability to change the TCP listening port for the main game connection.
2. The ability to communicate this port to others on the same network.
3. The ability for other game instances on the same network to understand and use the port number in the broadcasted game announcement.
But even so, this is only the port for the main connection. There are also the UDP broadcasting ports (which is what I thought you were asking about initially). There is no way to negotiate them, so they would have to be changed by all players to the same values, otherwise they wouldn't "see" each other on the same LAN.
Why do you want to change the port?