Port Forwarding
-
I am having trouble forwarding my ports for BMS 4.32. Does anyone know how to help.
-
Are you trying to host a server?
How are you connected to the Internet? Need details (router? simple modem? brand/model?)
-
I have helped a few people figure this one out. As WolfKeeper says, we need more information.
Basically, the process goes like this:
1. Log into your router, usually by entering 192.168.1.1 or 192.168.0.1 into your web browser.
2. Enter user name and password. The default user name is “admin” and the default password is “password”. You might want to change these later on for security reasons.
3. Click on the option for port forwarding.
4. Create a new entry for ports 2934-2935 for Falcon, and 9987-9989 for IVC if you want to use that. IIRC Falcon uses the UDP protocol, but you can always select the tcp/udp protocol to be safe.
5. (really part of step 4) These ports need to be forwarded to your internal ip address, which will be something like 192.168.1.27, or something like that. To get your internal ip, the fail safe method is to open the command (dos) prompt from start\programs\accessories. In the dos prompt window type “ipconfig” and you will see a bunch of stuff. Usually the first thing that looks like an ip address is your internal ip address assigned to your computer by your router. Forward the ports above to this ip address.
6. Next, go to the WAN settings in your router. Some will have a setting like “respond to pings,” and you need to enable that to host Falcon. Other routers will say something different, but look for something that has to do with communications from other machines and set it appropriately.
7. Now, you need to tell your friends your external ip address. Just type something like “my ip” into a browser search and you will see it. This is the ip address your friends enter to connect to your machine.
8. Finally, MAKE SURE EVERYONE HAS SELECTED THE SAME THEATER. I once spent an hour with my buddy wondering why we couldn’t do multiplayer when one of us had the Strong DPRK theater selected.
9. Open falcon, and set the ip to 0.0.0.0 in the comms window, select an appropriate bandwidth in kb/s, disable the IVC buttons, and click connect. Voila, you are now hosting Falcon. Be sure to have your friends enter in a bandwidth, too, or everything will be entirely f’d up.
If you can do that and want to host IVC, we can help you with that, too.
Hope that helps.
-
router is netgear wndr3400v2.
-
See if this helps:
http://portforward.com/english/routers/port_forwarding/Netgear/WNDR3400v2/Falcon_4.htm
If you want to support IVC, you’ll need to repeat adding forward for those ports 9987-9989.
-
I have tried portforward .com and nothing has worked as i have followed the steps provided
-
See if this helps:
http://portforward.com/english/routers/port_forwarding/Netgear/WNDR3400v2/Falcon_4.htm
If you want to support IVC, you’ll need to repeat adding forward for those ports 9987-9989.
That’s a good site to start with, but notice that they omit the step to check the WAN settings. I can only guess that’s a ploy to frustrate people and get them to buy their port forwarding utility.:mad:
See here:
-
Isn’t that just allowing responses to ICMP packets? Not sure that’s really required, unless BMS uses it to confirm there’s a server out there.
-
I could never host Falcon until I checked that box. It was like magic. Similar story for a friend who had always wondered why he couldn’t host. It probably depends on the router.
-
router is netgear wndr3400v2.
I’ve got the same router. Find the Port screen under Advanced and set it this way:
Your internal IP is likely different, so be sure to use yours.
-
Notice that it better be “port forwarding” and not port triggering. You may be able to set a triggered rule, but it needs more.
Also I can tell that you only need UDP 2934-2935. It was wider earlier, but today this is enough.You can not fix the source ports, only the target ports. (I think even that may be possible, but then it needs tuning each client with some magic spells.)
For IVC you don’t need the rules at all, UNLESS you are hosting the IVC server (or hosting the ivc locally with Falcon4). But if you use external IVC server, then you don’t need the rules.
-
Unless your hosting you should not need to forward any ports.
-
Unless your hosting you should not need to forward any ports.
This is only true when there’s only one client. When there are multiple clients, they will try and establish a mesh network. In effect, every client can be viewed as a server then. It won’t fall apart immediately when only one client in a MP has no port forwarding as it will be able to establish connections with other clients through their open ports, but if two or more clients have no port forwarding, they won’t be able to complete the mesh network. BMS has a fallback mechanism in that case: traffic between clients that cannot connect to each other, is routed through the host. Of course, this creates more lag, and takes up bandwidth. Better to configure your router and firewall correctly.
IVC is different. It uses a star topology and as such, each client only connects to the server. There is no need for a client to have open ports, only for the server.
-
Interesting. Could this possibly be the cause for f’d up debriefs (i.e. ordinance released from one jet shows up on another, multiple pilot instances… etc) that we all see from time to time in MP flights?
-
Interesting. Could this possibly be the cause for f’d up debriefs (i.e. ordinance released from one jet shows up on another, multiple pilot instances… etc) that we all see from time to time in MP flights?
I can’t rule that out. The debriefs have never been perfect as far as I remember. But in my experience the FU’s you describe often occur when people reconnect, e.g. after being shot down and joining another flight.
-
This is only true when there’s only one client. When there are multiple clients, they will try and establish a mesh network. In effect, every client can be viewed as a server then. It won’t fall apart immediately when only one client in a MP has no port forwarding as it will be able to establish connections with other clients through their open ports, but if two or more clients have no port forwarding, they won’t be able to complete the mesh network. BMS has a fallback mechanism in that case: traffic between clients that cannot connect to each other, is routed through the host. Of course, this creates more lag, and takes up bandwidth. Better to configure your router and firewall correctly.
IVC is different. It uses a star topology and as such, each client only connects to the server. There is no need for a client to have open ports, only for the server.
You Nailed it. The First Battle For Sinai we ran, we had lot of clients with unopened ports and the Lag was very bad. After we added this line set g_bHostAllowsDubiousConnections 0 in the Server .cfg lag was almost gone.
Every client had to open there Ports in order to fly on the server. Other things like Speed Test to the server location and assigning custom connection bandwidth also helped.
-
So break NAT without static port mappings to work around bugs? Oh, bother…
-
So break NAT without static port mappings to work around bugs? Oh, bother…
Not sure if I understand you correctly. But in case I do: I didn’t mention that RAKNET has a NAT traversal algorithm. However, this will only work with certain types of NAT’s. So to err on the safe side: open your ports.
-
That’s not true. Only static mappings work where src port is preserved through NAT. This is very uncommon. It’s been discussed some time back but apparently @mrivers has a different idea of TCP/IP…
-
That’s not true. Only static mappings work where src port is preserved through NAT. This is very uncommon. It’s been discussed some time back but apparently @mrivers has a different idea of TCP/IP…
I believe you’re misinformed. Source ports may be renumbered. In fact, I’ve found that there are lots of NAT implementations that won’t preserve the source port (outbound) even when you define a port-forwarding rule (inbound).
When setting up the connections, the server notes the actual source port of a client (what NAT made of it), and the source port that client “thinks” it uses (the port used by the PC running BMS behind the NAT). The server sends both ports to the clients that are already connected, and these clients subsequently try to connect to the new client using both these ports. Also the other way around, so the new client receives two ports of all the existing clients and tries to connect the other way around. This gives a total of 4 chances to connect each pair of clients. Unfortunately, as I said before, it won’t work for all NAT implementations.