UDP 13139 (For multiplayer)
I only have 1 firewall rule. Allowing the green interface to access the Red interface. And the protocol is set to ALL. Intrusion Detection is set to off for troubleshooting. Any idea why this is occurring?
Edit: I’m aware that there are service groups that can be created, is there an efficient way to do this as several computer play the game at once?
One more Edit: I created a service group with the aforementioned ports and created a DNAT rule, port forwarding to my computer’s IP address. And it didn’t work.
Hello! From my understanding its peer to peer. And Green has default access to Red. Im searching to see if there are servers. I have a service group allowing all of the aforementioned ports at the top of my firewall rules.
I’ll have to export the firewall rules and search through them using Microsoft Excel. It will take some time. I never had this problem with Sophos Firewall so I’m still working through it. Unless you have any other ideas of how to search? Thanks as always!
Rockstar doesn’t provide detailed public information about the exact specifications or locations of their servers. However, the game uses server farms around the world, often located in regions like North America, Europe, and other major markets, to ensure low-latency connections for players.
Overall, the combination of dedicated servers and P2P connections ensures both a seamless experience and flexibility for different regions and players.
Glad to see my fellow GTA Los Santos Buster I also have IPFire on IBM x346 server as my Firewall for entire network at home with many servers. And GTA 5 on my PS5 and also Gaming PC. works fine like a butter and packets are flowing for many many hours as long as I want to. You should also check your root connection itself if your ISP or “OpenDNS” at your network is not blocking the traffic. Check configuration on your gaming machine and speed of your internet connection. Possibly try to change or ask your ISP for different Public IP address.
GTA 5 Online as well as IPFire and my Fiber optic main ISP that i have as of now unfortantely and shamefully still don’t support IPv6.
Because of their comfort and laziness etc.
So I’m talking at this case about changing your Public IPv4 address!
Btw I have IPv6s at every VPS I try and have. Especially Contabo
I find your assertion that the reason that IPFire does not yet support IPv6 is due to our laziness and comfort extremely disparaging.
The IPFire team is very small and they all have day jobs that they need to support to be able to pay their bills so that they can spend the time they do on IPFire related stuff.
IPv6 will be in IPFire-3.x and that continues to have work being done on it, in addition to ongoing maintenance of IPFire-2.x and new features that are placed
All of this has to be done in a manner that ensures that IPFire will continue to be the secure firewall/router offering that it has been for some time.
For IPFire-3.x the current focus is to create a new package management system to create a better build environment for IPFire-3.x compared to IPFire-2.x. It is still called Pakfire but it will be a completely different animal under the hood. A properly working package management / build system is key before working on the other parts of IPFire-3.x
If you want to see some of the work that has been done on that then you can look at the IPFire-3.x Pakfire git repo to see all the commits that are being done now and over the last few years. https://git.ipfire.org/?p=pakfire.git;a=shortlog;h=refs/heads/master
This has not been ignored but it does take a lot of work to get it created.
Meanwhile you can also see all the commits that continue going in to the IPFire-2.x system for maintenance etc purposes. https://git.ipfire.org/?p=ipfire-2.x.git;a=shortlog;h=refs/heads/master
If you look at all the commits for IPFire-2.x over the last year you will see that the number of names is not very large but they are putting a large amount of voluntary time into the project and I think it is not appropriate to imply that they are lazy or that they should be shameful of the work they are doing.
I am, and have always been, extremely proud to be a part of that team.
Hopefully after my input you will reconsider your opinion of the IPFire team.
I do have to give you props for bringing up the fact that the IPFire project is Open Source aka. Free to use. So the priorities and time capabilities of the team behind are surely low.
I appreciate that you are planning on the new IPFire version that will finally eventually support also IPv6!
But this still doesn’t change the incredible extra possibilities and new connections and security features that the IPv6 protocol in IPFire will bring!
Let’s say that IPv4 is already heavily outdated and slowly being discarded. IPv6 will allow people and companies to have access to much MUCH MORE! public facing IP addresses in their network for minimal extra cost.
As the IPv6 space is multiple times larger than the IPv4 one. And there really shouldn’t be scarcity of v6 address in the nearest future and so on.
Me and many others are looking forward to see IPv6 in IPFire! And definitely will appreciate that.
I appreciate everything this team has given us! My only complaint is with myself! I wish I had the additional education and intelligence to work as a programmer.
This issue has me perplexed though. Im going to disable squid proxy server, change my DNS servers, and look at the firewall logs.
I think that will be very useful to do. If we can see why the traffic is being blocked we can then be better placed to figure out how to fix it.
For this debugging stage make sure that all the firewall rules that you have created have the logging checkbox enabled. That way we should be able to catch whatever is blocking it.
I think disabling the proxy server is also a good idea so that the setup is the simplest possible for this debugging stage.
Absolutely! I’ve kept the default firewall rule active for now that is, Green to Red with protocol set to All. I’m also using DNS servers 1.1.1.1 and 1.0.0.1.
I will reply back if I find anything of interest. Thanks as always and thank you for your work with this project.
Here’s just a sample. I’ve disabled IP address blocking by country, disabled Proxy server, disabled IPS, and changed my DNS settings. I’ve also attached a basic router to my network and was able to connect to the game servers. Rockstar games suggests that I enable UPnP (which doesn’t apply here) or that my NAT rules are too strict. Perhaps this firewall is too sophisticated for my skill level!
I think it has to do with the NAT type in my firewall. Its forwarding the ports correctly but it will not form a P2P connection. Someone mentioned that GTA V likes full cone NAT and not static NAT. I think this firewall is great but this might be above my current skill level. I might move to a basic router for now.