Access Pi remotetly over the internet

This have little to do with Raspberry really, as it's just a networking problem.

What you have to do is to forward on your router, one port to the raspberry Pi camera port.

This greatly depends on your router and service provider.

A graphic explanation would be as follows:

If you put it down to network topology:

Of course IPs and ports will have to match your network ones.

That have some issues:

• It's a security risk. You would need to sort out encryption and authoritation on your raspberry before to start.
• The IPs must be static in both your router and your raspberry. In your router you can set a free no-ip dynamic DNS account to fix it - Free Dynamic DNS - Managed DNS - Managed Email - Domain Registration - No-IP - but on your Raspberry you will need to configure the network interface by hand and avoid to use DHCP.

Other than that, this is easily doable.

Reading your question again, is not that clear your camera is connected and being served by your Pi.

Can you connect to your raspberry on your internal network and see the camera's image ?

If not, that would be your first step.

On the other hand, as you mentioned BT, a quick search returned this page about how to configure port forwarding on BT routers http://bt.custhelp.com/app/answers/detail/a_id/8790/~/does-the-bt-home-hub-allow-game-and-application-sharing%2Fport-forwarding%3F

Iago Rubio wrote:
- but on your Raspberry you will need to configure the network interface by hand and avoid to use DHCP.

With this statement I disagree. I have a bunch of raspberry pi's and Linux x86 machines that have a static DHCP addresses. I personally hand-configure them in my dhcpd.conf file. But a friend of mine has a "web gui" on his router where the static assignment is only a click away.

The advantage of this method is that as long as the mac address stays the same, the machine will end up with the same IP address. Even when, for example, you upgrade and end up with a default: we use DHCP setup again.

Of course you can configure DHCP to serve always the same IP but the easiest path - for someone that is asking such basic questions - is to simply configure a static IP address. You avoid to have to explain the concepts related to dynamic host configuration.

Anyway, I don't use to use DHCP but for dynamic IPs. In my networks every static IP is configured statically, and the DHCP range is just for phones, tablets or laptops of guests.

That lets me use firewall rules to isolate DHCP served IPs from static ones. And I am also kind of lazy to reconfigure the DHCP static entries each time the router needs a factory reset, gets a firmware update or simply is changed by my ISP.

Anyway, the important bit here is you need a fixed IP in your Raspberry either by setting it statically or by setting up the DHCP server to serve always the same IP.

I am sure we will agree on this ;-)

The pi has the piCamera on it and a PIR device and works well and can be 'seen' by my in-house PC. It will be running stand-alone normally.

OK, thanks, I will look into doing this tonight.

Cheers.

Iago Rubio wrote:

 

Of course you can configure DHCP to serve always the same IP but the easiest path - for someone that is asking such basic questions - is to simply configure a static IP address. You avoid to have to explain the concepts related to dynamic host configuration.

On the other hand, for my friend, just clicking "always assign this address to this device" is easier than configuring the static IP address. If the router in question happens to have that option, that is IMHO the easiest route. But indeed, a close second is the "then configure a static IP manually".