"Wilfried Woeber, UniVie/ACOnet" wrote:
[ individual addresses stripped... ]
Leigh,
=From: Leigh Porter <leigh@insnet.net> =Subject: Re: Allocations for "always-on" ISPs = ="Neil J. McRae" wrote: = =And if they need address space the ASP knows, about, they can use some =kind of tunneling mechanism
...now I'm lost! What is the _some_ in "some kind of tunneling mechanism? And how do you propose to take care of the re-configuration on the customer's end for the tunnel? Dynamic DNS with TTL close to 0? Whater it is, it should be available for all of the "popular" operating systems, btw.
Why do you need dynamic DNS? The user turns their box on, their DSL is up and their tunnel client connects to the tunnel server at the ASP site, gets an address and knows how to route to the ASP network and the ASP network knows how to get to the users machine. GRE/IPIP tunnels are very avaliable, not sure about pptp though or anything else that could be used.
=back to the ASP network so they have consistant addressing, even if their =providor uses dynamic addressing.
Which requires some sort of (non-trivial?) static routing entries on the customer's end nodes and/or some sort of routing support by the "basic" transport provider.
No, the ASP network just needs to know that it gets to its customers down tunnels and the customers box should have software intelligent enough to do "route add 10.9.8.0/24 gw tunnel1" Then anything for the ASP gets to go down the tunnel right to their front door and anything for the net goes out the usual route via their NAT things. It also does a lot for security because the ASP boxes do not have to be on routable address space. I do not know what kind of clients these ASP things use though. This is being used now, how do you think lots of people get to their corporate networks from their hotel/whatever dialups? They use pptp or somethig like that, connect to the net, then to their pptp server and talk to their company VPN over that, encrypted probobly. -- Leigh Porter C&W