For a new problem, you really need a new thread. The config in this thread has been working for many of us for years. If it doesn't work for you, then it's something new, a game-specific issue, or unrelated to this thread in some other way.
regardless of what i do, following the whole steps mentioned here:
upnp does not seem to allow the packets, you can see the packet answers always to be blocked in the system-logs :-(
i use 2.0-RC2 (i386) built on Sun May 15 20:43:07 EDT 2011
now i defined NAT by hand and it works…
but why not upnp ?
i used the following upnp rule: allow 1-65535 xxx.xxx.xxx.xxx/32 1-65535
anyone any ideas ?
i even created a pass-rule for the upne ports from lan-network to lan-address as stated in http://forum.pfsense.org/index.php/topic,33024.0.html
but it still does not work, there are simply no mapping in the upnp status...
Hi, just for those who is looking for solution of OPEN NAT in pfSense 2.4.5 and could not get it working with private IP on WAN (192.168..., 10.10..., 172.16...) using UPNP. You are behind second NAT of your internet provider and you have to add this line to /var/etc/miniupnpd.conf with your public IP:
ext_ip=XXX.XXX.XXX.XXX (<=write your public IP here)
setting manual PORT in console advanced network settings and opening that port in NAT is also recommended.
Ich habe das gleiche Problem mit 2 PC's. kann ich für die beiden PC's die gleichen Ports (3075 und 1024) verwenden wie bei X-BOX oder werden für die PC Spieler andere Ports von Activision
I will agree that i don't understand it either, but Pfsense is an enterprise grade firewall where this type of configuration would typically not be needed, consumer routers are aimed at this type of setup and generally aimed at flat networks.
Consumer routers cater for what a user at home may do and may have at home, such as consoles, an enterprise firewall is aimed at a different market and while this can be changed via code, plugs etc, you'll have to bear with it.
V3 also has an interesting setup
I hope you find a solution that is suitable until then
I woke up this morning. Looked at the outbound port mapping again. I just realized, there is an "Auto created dynamic port mapping rule for my LAN to WAN".
I moved the static port mapping above the auto created one. and it is NOW Working.
Ok, you are not going to believe this, but I fixed it. Found a random post on the internet suggesting to disable all lan cards not being used. I diabled my hyperv nic and all others not in use and it worked perfectly.
Yes, I would have expected that to show open. I would think 99.9% of connecting clients are behind NAT.
You could try opening UPnP without any restrictions and see if that allows it. Then check to see what it's actually opening.
Can I ask why you are going to let them connect directly, and not just have your servers listed in the Steam Client? I run Ark boxes as well, and all mine are listed in the Steam client for them to use. This is how the game is designed to run, and is probably why you are seeing this problem.
I got it working now. I put the router into AP mode instead of router which gave it a 192.168.1.0/24 address instead of a 10...*/24 address. After that, I set up a static IP and changed the NAT type to hybrid for the specified IP. Mods, please feel free to close the post as I should have read the pinned thread to begin with.
I just happened to check back on these forums, it has been quite a while. And noticed a few people asking what happened.
I never found a good solution, and I believe (maybe incorrectly) that the issue's root cause is the underlying BSD Packet filter (pf) from what I read, pf is only capable of setting up a symmetrical NAT. Which maybe ideal for many enterprise applications, causes problems with gaming. Many games need a cone nat to operate properly (This is what "gaming mode" does on most consumer routers that have it). UPnP is also supposed to resolve this, but at the time (3 years ago) minupnp was not solving the issue, and I solved it by using another router installation that was based on Linux's netfiltering (iptables). Still like PFsense, but it never worked correctly for my setup with multiple xboxes behind one nat, all trying to play together in the same party.
I found this command on reddit it seems to work if on PC with Xbox App:
netsh int ipv6 set teredo enterpriseclient
Also I might be mistaken, but Warframe and Destiny 2 both use server side matchmaking and no peer2peer BS, so both XBones should be able to play togehter without any change from the default at all (e.g. both with NAT strict as they don't necessary need inbound ports and fall back to server side connectivity).
I did a full howto for Xbox One without UPnP/DMZ.
Topic : https://forum.netgate.com/topic/144291/howto-multiples-xbox-play-together-without-upnp-dmz
Howto : pdf : https://forum.netgate.com/assets/uploads/files/1560932072924-pfsense_multiples_xboxone_v0.1.zip
We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.
Subscribe to our Newsletter
Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.