Broadband Static IP's

[n3il123]

Hi

After an hour on the phone to BT I am still none the wiser .. I have a BT residential phone line with broadband through BT, I have a couple of PC's behind a router, i need a static IP for one of the clients that I am working for, now I know the only way that I can get this is by upgrading to business broadband, however not one of the people that I spoke to could answer the (I thought) simple question, do I need a static IP for each of the PC's on the "network" or do I only need a static IP for router?

Am I missing something? or is this much more complicated then I thought?

Thanks in advance

N3

[trooperiziz]

You need a static IP for the router only, and use the router to route the traffic to the PC you want accordingly.

[tinman0]

router gets the static ip (if it needs it).

the router using Network Address Translation (NAT) then gives the PCs on the private side an ip address and works out who is talking to what on the Internet. some routers have NAT turned off as default for some unknown reason.

[malman]

tinman0 said:

router gets the static ip (if it needs it).

the router using Network Address Translation (NAT) then gives the PCs on the private side an ip address and works out who is talking to what on the Internet. some routers have NAT turned off as default for some unknown reason.

That would be for when you want a routed connection with multiple statics for running say 2 or more ssl websites.

[tuffer]

If you use Plus Net you can get a static IP address if you need one, costs an extra £1 a month I think.

[sp60]

Depends what your client needs you to have a static IP for.
Most likely to be a VPN tunnel in which case, as previously mentioned, 1 static IP address for the router is all that is needed. You will also need a router capable of vpn tunnelling, which most are these days.
Presumeably this is to allow your client to get access to one of your pc's for some reason, in which case you are going to need to learn a little about vpn setup and networking before your can get this all working.

[Plotloss]

Dyndns.org not suffice?

[Mr E]

Plotloss said:

Dyndns.org not suffice?

Exactly what I was about to suggest.

[Julian64]

For a lot of things yes but not if you want to cross someones router.


By the way on a similar thread when you have a statis IP and you have a www.name.com. How do you match the two together?

[ATG]

Freeola give you a fixed IP as standard, 8Mb/s or however fast your line will support downstream / 448kb/s upstream ... up to 60GB download per month (or it might be unlimited, can't remember) plus all the usual stuff for the princely sum of £15 a month for the first three months and £25 a month thereafter. No connection fee. Minimum contract term of 3 months. Not a lot wrong with that. (It's something like £10 a month if you limit yourself to 3GB download capacity).

[Plotloss]

Julian64 said:

For a lot of things yes but not if you want to cross someones router.

Eh?

[BliarsGoing]

Plotloss said:

Julian64 said:

For a lot of things yes but not if you want to cross someones router.

Eh?

Roughly translates to "a lot of VPN endpoints need to connect to an IP address not a DNS entry".

[Julian64]

Plotloss said:

Julian64 said:

For a lot of things yes but not if you want to cross someones router.

Eh?

If you want access inside someones router.

In other words you are WAN, and you want access to a computer behind a router or in its DMZ.

In this scenario you will need a static IP, so the router can be told to let you in.

[Plotloss]

But thats VPN endpoints specifically, rerouted traffic can traverse routers perfectly happily.

However, surely DynDNS is just another DNS server so traffic will arrive with an IP header to an IP address through the tunnel?

I dont have a VPN set up currently but I thought DynDNS was pretty transparent all things considered.

[BliarsGoing]

If you're going to create a filter rule on a router it will need to know the IP address of the incoming device. As it can change with dynamic IP sooner or later the rule will stop functioning.

Last time I looked all Demon accounts used static IP.

[ATG]

Plotloss said:

But thats VPN endpoints specifically, rerouted traffic can traverse routers perfectly happily.

However, surely DynDNS is just another DNS server so traffic will arrive with an IP header to an IP address through the tunnel?

I dont have a VPN set up currently but I thought DynDNS was pretty transparent all things considered.

Ah, i think I see what Julian is saying ... its not the router with the non-static IP, its the one that's hosting the VPN ... i.e. the office router. if it has to be told in advance which external IP addresses it should allow in, then having a non-static IP address at home is a problem and dydns is of no use.


... what BlairsGoingMaybe just said

Edited by ATG on Tuesday 3rd October 11:33

[Julian64]

ATG said:

Plotloss said:

But thats VPN endpoints specifically, rerouted traffic can traverse routers perfectly happily.

However, surely DynDNS is just another DNS server so traffic will arrive with an IP header to an IP address through the tunnel?

I dont have a VPN set up currently but I thought DynDNS was pretty transparent all things considered.

Ah, i think I see what Julian is saying ... its not the router with the non-static IP, its the one that's hosting the VPN ... i.e. the office router. if it has to be told in advance which external IP addresses it should allow in, then having a non-static IP address at home is a problem and dydns is of no use.


... what BlairsGoingMaybe just said

Edited by ATG on Tuesday 3rd October 11:33

wot he said

[Plotloss]

It is possible though, just not if you want to lock it down with client IPs

Not all VPNs insist on knowing the IP address of the client.

I dont think the Netgear ones do, for example.

[BliarsGoing]

Julian64 said:

ATG said:

Plotloss said:

But thats VPN endpoints specifically, rerouted traffic can traverse routers perfectly happily.

However, surely DynDNS is just another DNS server so traffic will arrive with an IP header to an IP address through the tunnel?

I dont have a VPN set up currently but I thought DynDNS was pretty transparent all things considered.

Ah, i think I see what Julian is saying ... its not the router with the non-static IP, its the one that's hosting the VPN ... i.e. the office router. if it has to be told in advance which external IP addresses it should allow in, then having a non-static IP address at home is a problem and dydns is of no use.


... what BlairsGoingMaybe just said

Edited by ATG on Tuesday 3rd October 11:33

wot he said

From inside the corporate network you could ping the DDNS entry of the SOHO router, access any services that it was hosting via port forwarding etc BUT the corporate firewall would need the IP address of the SOHO router to allow traffic to enter the corporate network. As that IP address changes it'll break sooner or later. Most corporate firewalls are configured by rules that need an explicit IP address/mask combination as opposed to a DNS entry of any sort. Performing DNS lookups on incoming packets would slow the corporate router down significantly.

[BliarsGoing]

Plotloss said:

It is possible though, just not if you want to lock it down with client IPs

Not all VPNs insist on knowing the IP address of the client.

I dont think the Netgear ones do, for example.

IPSec or PPTP? The prob is the head office router needs to know the IP of the connecting Netgear if it's an IPSEC VPN. PPTP VPN's will work quite happily over dynamic IP.