i am worried cause of voxs cgnat and i believe that is the main reason that others are not able to access my server and i don't believe taking control of my router will fix this as i don't have my own public ip address i sent vox an email about this a couple days ago and they have completely ignored me so i am in the dark. i was thinking about trying to figure out how ipv6 works and seeing if i could get a public ip address for that from vox as they would probably be more willing however minecraft bedrock does not support ipv6 only minecarft java does. i honestly feel i am out of options for straight up portforwarding as i feel the odds of vox providing me a ipv4 address are close to zero. if you know of any other possible solutions or something i missed i would really like to hear i am very new and dont know what i am doing any help is appreacted
Networking is not my day job so take what I say with a pinch of salt. Having access to the router would be a requirement to setup a reliable port forwarding connection. It also has some other benefits like managing wifi channels etc.
To my knowledge you need the following for port forwarding to work reliably:
- A public ip assigned to the router. On the Frogfoot network my FTTH connection receives a public ip address and I assume static ips may be limited for business connections. Mikrotik has a dynamic dns function that you can enable on the router. Your friends can then use the dns name to connect to your Minecraft/server pc.
- The server pc needs to be assigned a static ip address. You can either manually assign an address outside of the dhcp range on your router or reserve the ip on the router so that it always assigns the same ip to your pc. The latter would require access to the router. If the ip address of the pc changes, it will likely break the port forwarding rules that you have configured already.
- Connect the server pc directly to the main router via ethernet to avoid having a second router in front of it since that would require port forwarding to be configure on both routers which is messy. Some mesh wifi systems set themselves up in router instead of access point mode.
-You need to add a rule on the router to forward incoming traffic to the static/reserved ip and port of the server pc on your network. It sounds like Vox may have configured this for you.
- Open up the ports on the firewall of the server pc. I am not familiar with configuring the Debian firewall, but you could always ask Grok, Copilot or another AI engine to give you detailed instructions on how to perform these steps on your operating system. On Windows that would require you to add firewall rules for specific port numbers. Services (or the pc) may need to be restarted before rules take effect.
Once all the above steps have been completed, you can use a site like dnschecker dot org which can perform port scanning to check if ports are open.
Given all the steps above is why I suggested that you should try setting it to up using a consumer based router where the configuration is much easier compard to the Mikrotik. If it works on the consumer grade router then you could spend time setting up the mikrotik to do the same. Many LTE or adsl routers have ethernet wan ports which will allow you to use it instead of the Mikrotik. The pppoe username and password can be retrieved from the Vox customer portal if you go that route.
