DirectConnect vs EasyConnect

You don't need to know this!

Unless Presence's menu bar icon is red, Presence is working and there's nothing else you have to do. But if you want to delve further, read on.

The Basics

I know about networking. What does Presence require for DirectConnect to work?

Presence runs as a network service on port 8889. Presence tries UPnP and NAT-PMP to open this to the internet. If this fails, you could try configuring your network yourself, adding your own port mapping, etc. If you do this, then:

Presence is using EasyConnect, but I want to use DirectConnect

If you're on a network you can configure yourself (eg. most home networks), your network can probably be configured to make DirectConnect work. Some help is provided, but bear in mind:

A more detailed explanation (optional)

By DirectConnect, we just mean Presence running as a normal network service on your Mac. Connections from the internet reach your public IP address, pass through your router (via a port mapping) to Presence on your Mac. Other services on your Mac are not exposed, so this is secure.

Presence uses UPnP or NAT-PMP to automatically add a port mapping to your router, but a number of things can prevent this working: your Mac is behind multiple routers (eg. a DSL modem and a separate router or Airport), your router doesn't allow itself to be configured (common on non-home networks, but on some home ones too), or your router is buggy (all too common unfortunately). The Connection pane will tell you what's wrong.

If DirectConnect fails, Presence uses EasyConnect. With EasyConnect, your Mac connects to our server, so it is only necessary to make an outward connection. This works in many more situations - if you have an internet connection, EasyConnect should work. This is similar to the way Skype allows computers to connect to each other.

Because all traffic goes via our server, EasyConnect is slower than DirectConnect. That's also why we have to limit your data and charge you for extras.