• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0

UDP Hole Punch?

3 posts in this topic

Game Server is UPnP enabled. works perfectly.
Client has no UPnP protocols on their router so it requires manual port settings.
But these days most games find a way around that problem and i'm guessing they are using Hole Punching.

I've researched it a bit but it's all fuzzy to me. So maybe someone can clarify the steps needed to do a HolePunch on most networks.

currently i have: (all UDP except for the HTTP ofcourse)

[color=DarkOliveGreen]Server[/color] starts, contacts master server via HTTP request and informs it "This is my port/ip/name/etc..."

[color=Navy]Client[/color] loads and makes an HTTP request to the master server and gets the serverlist, including our target [color=DarkOliveGreen]server[/color].

[color=DarkOliveGreen]Server[/color] Listens on: <Server Customized>
[color=DarkOliveGreen]Server[/color] Sends To: 45,000

[color=DarkSlateBlue]Client[/color] Listens On: 45,000
[color=DarkSlateBlue]Client[/color] Sends To: <Server customized>

[color=DarkSlateBlue]Client[/color] does HTTP request to a master server to get the target server's IP and <ServerCustomized>port (working)

The [color=DarkSlateBlue]client[/color] sends UDP request to the [color=DarkOliveGreen]server [/color]join the [color=DarkOliveGreen]server[/color] targeting <ServerCustomized> port. (working)

[color=DarkOliveGreen]Server[/color] hears the [color=DarkSlateBlue]client[/color] request (working)
and replies to [color=DarkSlateBlue]client[/color] listening port 45000 "yes you may join" [b](NOT working)[/b]

as far as i can tell, the[color=DarkOliveGreen] server[/color] is sending it, but the[color=DarkSlateBlue] client[/color] doesn't hear it. I say this because it works on LAN and i haven't found a UPnP enabled tester to try it with over the internet.

to hole punch, do i just need to have the [color=DarkSlateBlue]client[/color] send the initial join request on both
<ServerCustomized> port and the 45000 port to punch a hole?

[size=1]Q: OMG! Why are you doing hole punching?
A:Because i've already found 2/3 testers that DONT have upnp routers (eg: WANPPPConnection:1 and WANIPConnection:1).[/size]

Share this post

Link to post
Share on other sites
I read something about that stuff a long time ago...

Cant you just use <ServerCustomized> for both sending and listening?

I think hole punching works like:

You have clients A and B. Both of them have a fancy NAT so they cannot connect to each other.

So, Both connect to a server C, which doesnt have a fancy NAT like that. Now C has the ports and IPs from which A and B connected to it.

Next, C tells A (or B? idk) the port of B, so that A can connect to B, because that port is already open to incoming stuff from C and thus allows connecting to it.

Something like that. I think its only needed when you want to connect 2 computers together, with both of them behind a NAT.

Go and google how it works :P

Share this post

Link to post
Share on other sites
If you have a server outside of NAT (in this case, that means with working uPnP), then you don't need NAT punch through at all.

> Client makes HTTP request to discover server IP/port
> Client make sUDP connection to server IP/port
> Server replies over the same UDP connect (i.e. the one established by the client)

UDP connections are intrinsically bi-directional, and when the client has connects to the server, you can determine the reply address from the socket.

Share this post

Link to post
Share on other sites
Hole punching (and uPNP) is only needed when both ends of a communication are behind NATs. If one is a public server, no hole punching is needed.
When you do hole punching, you have a spearate "introducer" server that is outside a NAT, and introduces the two endpoints to each other. This is also useful for matchmaking.
The FAQ talks about UDP NAT punching, and has some links to explanations and libraries you can check out.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
Followers 0