Differences between revisions 2 and 3
Revision 2 as of 2005-03-01 13:26:05
Size: 10601
Editor: pc125
Comment:
Revision 3 as of 2005-03-01 13:38:52
Size: 5088
Editor: DarrinEden
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
!'''[http://phentermine1.chat.ru/ Buy phentermine]!'''! === Goal ===
Line 3: Line 3:
!'''[http://0nline-casin0.newmail.ru Online Casino] Win money fast!'''! To solve problems inherent to layer 3 client roaming
Line 5: Line 5:
!'''[http://united-airline.boom.ru/ United Airlines tickets flights] !'''! This is needed because as a wireless user moves between specific nodes, several things change.
Line 7: Line 7:
!'''[http://computer-desk.newmail.ru/ Computer desk] !'''!  * Association
 * Leased DHCP Address
 * Layer 2 State
Line 9: Line 11:
[http://online-degree.hotmail.ru/ Online degree] === Requirements ===
Line 11: Line 13:
[http://online-degree.hotmail.ru/ Online degree] These would be the absolute basic requirements of each node that was a part of the network.
Definitions follow further down.
Line 13: Line 16:
[http://online1degree.chat.ru/ Online degree]  * Node IP Registry
 * Node Standards for DHCP
Line 15: Line 19:
!'''[http://poker-table.nm.ru/ Poker Table] !'''! === Assumptions ===
Line 17: Line 21:
!'''[http://spyware-killer.hotmail.ru Spyware Killer] Remove spyware from your computer!'''! TCP/IP Protocol Stack ''Layer n'' refferences are based on the following 4-Layer Model:
Line 19: Line 23:
[http://chp-cigar.boom.ru/ cheap cigarettes]
[http://disc-cigar.boom.ru/ discount cigarettes]
[http://online-cigaret.hotmail.ru/ online cigarettes]
[http://marlb-cigar.boom.ru/ marlboro cigarettes]
[http://online-cigar.boom.ru/ online cigarettes]
[http://winst-cigar.boom.ru/ winston cigarettes]
[http://camel-cigar.boom.ru/ camel cigarettes]
[http://winst-cigaret.hotmail.ru/ Cheap winston cigarettes]
|| Application || 4 ||
|| Data Link || 3 ||
|| Network || 2 ||
|| Network Access || 1 ||
Line 28: Line 28:
=== Procedure ===
Line 29: Line 30:
The following attempts to outline a basic solution that addresses these issues as simply as possible, yet still maintain efficiency and expandability as the wireless cloud grows.
Line 30: Line 32:
Best links: ''' cruises''' '''Client A''' comes within range of ''Node A'' for the very first time. Assuming no previous contact the following should happen automatically, without client intervention.
Line 32: Line 34:
 * '''Client A''' establishes Layer 2 connectivity with ''Node A'' (this should be automatic so long as the AccessPoint doesn't use WEP and the clients ESSID is set to either "Any" or "www.personaltelco.net")
 * After connectivity at Layer 2 is established for '''Client A''' Layer 3 connectivity should be established automatically
 * DHCP issues a lease at this time, completing the initial steps
Line 33: Line 38:
Once initialized the complete route must be established through further means. This can be accomplished with any Portal system (such as NoCatAuth).
Line 34: Line 40:
[http://norwegcruiselin.chat.ru/ | norwegian cruise line]
[http://italycruise.chat.ru/ | italy cruise]
[http://mexico2cruise.chat.ru/ | mexico cruise]
The following steps are required when '''Client A''' leaves the coverage area of ''Node A'' and enters the established coverage area of ''Node B''.
Line 38: Line 42:
 * Connectivity to ''Node A'' at Layer 2 will be broken automatically, however the ''Node A'' Layer 3 DHCP lease will remain
 * Layer 2 connectivity will be re-established with ''Node B''
 * DHCP information from ''Node A'' will persist until '''Client A's''' lease expires
 * Once the old lease expires, a new lease will be obtained from ''Node B''
Line 39: Line 47:
Best links: ''' nursing''' === Details Concerning the IP Registry ===
Line 41: Line 49:
The IP Registry will be a central storage point for information concerning the IP assignments for the wireless network. These will be internal non-routable IP addresses as specified in RFC1918.
Line 42: Line 51:
Class A addresses will be in the 10.0.0.0/8 range. Each node will be given some portion of the available addresses. This information will be centrally maintained and kept consistent with the current network state. The chosen method of storage can be any easily updated information distributing medium.
Line 43: Line 53:
[http://forensic-nursing.boom.ru/ | forensic nursing]
[http://career-in-nursin.boom.ru/ | career in nursing]
[http://careerin1nursing.chat.ru/ | career in nursing]
An Example of the IP assignments could be as follows:
Line 47: Line 55:
 * 10.0.1.0/24 - reserved
 * 10.0.2.0/27 - Node NNX
 * 10.0.2.32/27 - Node NNY
 * 10.0.2.64/27 - Node NNZ
 * etc...
Line 48: Line 61:
Best links: '''acne''' If needed, route aggregation could be obtained by assigning specific blocks to specific regions.
Line 50: Line 63:
=== Node Standards for DHCP ===
Line 51: Line 65:
Each node will be identically configured with the obvious exception of the specific DHCP address pool which is configured according to information set in the IP Registry Database. Arbitrary standards may be specified that fit each networks specific conditions. It is generally assumed that each stations ESSID will remain the same through out the network (Note: there is still some debate as to whether it is better to have a single ESSID for all AccessPoints or whether to have a slightly different ESSID for each).
Line 52: Line 67:
[http://adult-acne.newmail.ru/ | adult acne]
[http://acne-scar.newmail.ru/ | acne scar]
[http://acne-rosacea.newmail.ru/ | acne rosacea]
[http://acne-treatment.newmail.ru/ | acne treatment]
[http://acne-medicine.newmail.ru/ | acne medicine]
[http://acne-product.newmail.ru/ | acne product]
[http://body-acne.newmail.ru/ | body acne]
[http://acne1treatment.chat.ru/ | acne treatment]
[http://acne1medicine.chat.ru/ | acne medicine]
[http://acne1product.chat.ru/ | acne product]
[http://acne1rosacea.chat.ru/ | acne rosacea]
[http://acne1scar.chat.ru/ | acne scar]
[http://adult1acne.chat.ru/ | adult acne]
[http://body1acne.chat.ru/ | body acne]
[http://acn-treat.boom.ru/ | acne treatment]
[http://adult-acne.hotmail.ru/ | adult acne treatment]
[http://acne-cure.newmail.ru/ | acne best cure]
[http://adult1-acne.hotmail.ru/ | adult acne]
[http://adlt-acn.boom.ru/ | adult acne]
[http://murad-acn.boom.ru/ | murad acne]
[http://dr-murad-acne.hotmail.ru/ | murad acne]
[http://murad1acne.chat.ru/ | murad acne]
[http://acne-product.hotmail.ru/ | acne product]
[http://acn1-product.boom.ru/ | acne product]
[http://product2acne.chat.ru/ | acne product]
[http://acn-treatm.boom.ru/ | murad acne treatment]
[http://acne-best-treatment.newmail.ru/ | murad acne treatment]
[http://acn-control.boom.ru/ | acne control]
[http://acne-control.hotmail.ru/ | acne control]
[http://acne1control.chat.ru/ | acne control]
[http://acn-solution.boom.ru/ | acne solution]
[http://acne1solution.chat.ru/ | acne solution]
[http://acne1care4skin.chat.ru/ | acne skin care product]
[http://acn-care.boom.ru/ | acne care]
[http://care-acn.boom.ru/ | acne adult care skin]
[http://acne-care.hotmail.ru/ | acne adult care skin]
[http://acn-scar.boom.ru/ | acne scar treatment]
[http://acne2scar.chat.ru/ | acne scar treatment]
[http://adult-acne.nightmail.ru/ | adult acne]
[http://murad-acne.hotmail.ru/ | murad acne]
[http://acne-treatment.hotmail.ru/ | acne treatment]
Example DHCP configuration:
Line 94: Line 69:
 * Gateway: 10.0.0.1
 * Primary DNS: 10.0.0.2
 * Secondary DNS: 10.0.0.3
 * Netmask: 255.0.0.0
 * Domain: www.personaltelco.net
 * Lease Time: 600 seconds
 * Address Pool: Assigned from node IP registry
Line 95: Line 77:
Best links: '''acuvue''' Note on DNS: It has been suggested that Public, routable IP addresses be used for DNS to facilitate accesibiltity to all members of the network. Only adequate testing could determine the best solution. Either may work sufficiently provided the DNS assigned at ''Node A'' works when the client roams to ''Node B''.
Line 97: Line 79:
=== Portal Authentication System Requirements ===
Line 98: Line 81:
 * Ability to authenticate at ''Node A'' and recieve a cookie upon succesful authentication.
 * Upon Moving to ''Node B'' connectivity is updated at Layers 2 and 3 as explained previously.
 * Traffic from ''Client A'' will be routed to the Portal running at ''Node B''
 * The centralized authentication server will recognize the cookie previously set by ''Node A''
 * Authentication information will be updated at ''Node B''
 * All traffic will be routed to the public internet as requested
Line 99: Line 88:
[http://acuvue.boom.ru/ | acuvue] At this point a browser is required to re-authenticate at the new node.
Line 101: Line 90:
--
Line 102: Line 92:
Best links: '''air cleaner''' This draft was originally proposed by AdamShand on Fri, 5 Oct 2001 16:58:12, and discussed by other list members over the course of the next few days. It should deffinitely be considered a Work In Progress and any PersonalTelco member is welcome and encouraged to add comments and make appropriate changes. Remember to sign your name to any changes so you can get credit ;).
Line 104: Line 94:
-- EliabHelon
Line 105: Line 96:

[http://air1cleaner.chat.ru/ | air cleaner]
[http://air-cleaner.narod.ru/ | air cleaner]


Best links: '''airline flight'''



[http://airline-flight.hotmail.ru/ | airline flight]


Best links: '''alaska cruise'''



[http://Aalaskacruise.hotmail.ru/ | alaska-cruise]
[http://alaska-cruise1.boom.ru/ | alaska cruise]
[http://alaska1cruise.chat.ru/ | alaska cruise]
[http://alaska1cruise.hotmail.ru/ | alaska cruise]
[http://alaska1cruise.boom.ru/ | alaska cruise]
[http://alaska2cruise.chat.ru/ | alaska cruise]


Best links: '''attorney'''



[http://duiattorney.chat.ru/ | dui attorney]
[http://michiganattorney.chat.ru/ | michigan attorney]
[http://sanfr1attorney.chat.ru/ | san francisco attorney]
[http://la1attorney.chat.ru/ | los angeles attorney]
[http://sdiego1attorney.chat.ru/ | san diego attorney]
[http://personal4attorne.chat.ru/ | personal injury attorney]
[http://malpattorney.chat.ru/ | malpractice attorney]
[http://califattorney.chat.ru/ | california attorney]
[http://floridaattorney.chat.ru/ | florida attorney]
[http://illinoisattorney.chat.ru/ | illinois attorney]
[http://nyattorney.chat.ru/ | new york attorney]
[http://dallasattorney.chat.ru/ | dallas attorney]
[http://dui-attorney.boom.ru/ | dui attorney]
[http://best-attorney.boom.ru/ | attorney]
[http://michigan-attorney.lbgo.com/ | Michigan attorney]


Best links: '''background check'''



[http://background-check.narod.ru/ | background check]


Best links: '''bag'''



[http://tote-bag.hotmail.ru/ | tote bag]
[http://tote2bag.chat.ru/ | tote bag]
[http://plastic4bag.chat.ru/ | plastic bag]
[http://plastic-bag.newmail.ru/ | plastic bag]
[http://garment-bag.hotmail.ru/ | garment bag]
[http://garment4bag.chat.ru/ | garment bag]


Best links: '''bead'''



[http://wholesale4bead.chat.ru/ | wholesale bead]
[http://wholesale-bead.hotmail.ru/ | wholesale bead]
[http://wholesale-bead2005.narod.ru/ | wholesale bead]


Best links: '''bed'''



[http://bed2bath.chat.ru/ | bed bath]
[http://bed-bath.hotmail.ru/ | bed bath]
[http://bed-bath2005.narod.ru/ | bed bath]


Best links: '''bed bath'''



[http://bed-bath.narod.ru/ | bed bath]


Best links: '''blood glucose monitor'''



[http://gluc-mon.boom.ru/ | blood glucose monitor]
[http://blood-monitor.newmail.ru/ | blood glucose monitor]
[http://blglmon.boom.ru/ | blood glucose monitor]
[http://glucose-monitor.newmail.ru/ | blood glucose monitor]
[http://glucose-monitor.boom.ru/ | blood glucose monitor]
[http://glucose1monitor.chat.ru/ | blood glucose monitor]


Best links: '''blood pressure'''



[http://blood-h-pressure.boom.ru/ | blood diet high pressure]
[http://blood-opressure.boom.ru/ | blood omron pressure]
[http://bloodlpressure.boom.ru/ | blood lower pressure]
[http://blood-pressure-m.boom.ru/ | blood monitor pressure]
[http://bloodmpressure.boom.ru/ | blood medication pressure]
[http://blood-pressure.hotmail.ru/ | blood pressure]
[http://blood-pressure.boom.ru/ | blood pressure]
[http://blood1pressure.chat.ru/ | blood pressure]
[http://blood-press-monitor.hotmail.ru/ | blood pressure monitor]
[http://blood-p-monitor.boom.ru/ | blood pressure monitor]
[http://blood4pressure.chat.ru/ | blood pressure monitor]


Best links: '''cabinet'''



[http://cabinet-refacing.nm.ru/ | cabinet refacing]
[http://cabinet1refacing.chat.ru/ | cabinet refacing]
[http://cabinet-refacing.narod.ru/ | cabinet refacing]


Best links: '''call wave'''



[http://call-wave.nm.ru/ | call wave]
[http://call1wave.chat.ru/ | call wave]
[http://call-wave.narod.ru/ | call wave]


Best links: '''callaway'''



[http://corelle-callaway.boom.ru/ | corelle callaway]
[http://callaway-steel.boom.ru/ | callaway steelhead]
[http://callaway-bag.boom.ru/ | callaway golf bag]
[http://callaway-ball.boom.ru/ | callaway golf ball]
[http://callaway-golf.boom.ru/ | callaway golf club]


Best links: '''camera'''



[http://security1camera.chat.ru/ | security camera]


Best links: '''canopy'''



[http://canopy.boom.ru/ | canopy]


Best links: '''carnival cruise'''



[http://carnivalcruise.hotmail.ru/ | carnival cruise]
[http://carnivalcruise1.boom.ru/ | carnival cruise]
[http://carnivalcruise1.chat.ru/ | carnival cruise]


Best links: '''casino'''



[http://0nline-casin0.newmail.ru/ | online casino]
[http://online-casin0.boom.ru/ | online casino]
[http://online1casino.chat.ru/ | online casino]


Best links: '''cd'''



[http://cd-sleeve.boom.ru/ | cd sleeve]


Best links: '''chair'''



[http://lift-chair.nm.ru/ | lift chair]
[http://lift1chair.chat.ru/ | lift chair]
[http://wheel-chair.nm.ru/ | wheel chair]
[http://wheel1chair.chat.ru/ | wheel chair]


Best links: '''cheap cruise'''



[http://cheap2cruise.chat.ru/ | cheap cruise]
[http://cheap-cruise.hotmail.ru/ | cheap cruise]


Best links: '''check'''



[http://printer-check.nm.ru/ | printer check]
[http://printer1check.chat.ru/ | printer check]


Best links: '''chevrolet tahoe'''



[http://chevrolet-tahoe.boom.ru/ | chevrolet tahoe]
[http://chevrolet-tahoe.newmail.ru/ | chevrolet tahoe]


Best links: '''cigarette'''



[http://cigarette4all.chat.ru/ | cigarette]
[http://chp-cigar.boom.ru/ | cheap cigarettes]
[http://disc-cigar.boom.ru/ | discount cigarettes]
[http://marlb-cigar.boom.ru/ | marlboro cigarettes]
[http://online-cigar.boom.ru/ | online cigarettes]
[http://winst-cigar.boom.ru/ | winston cigarettes]
[http://winst-cigaret.hotmail.ru/ | winston cigarettes]
[http://camel-cigar.boom.ru/ | camel cigarettes]
[http://cigar-smoking.boom.ru/ | quit smoking cigarettes]
[http://online-cigaret.hotmail.ru/ | online cigarettes]


Best links: '''cigarettes'''



[http://marlborocigarett.chat.ru/ | marlboro cigarette]
[http://cheapcigarettes.chat.ru/ | cheap cigarette]
[http://cig-sale.boom.ru/ | cigarette sale]
[http://cigarettes1com.chat.ru/ | ]
[http://ciga4discount.chat.ru/ | cigarette discount]
[http://cheap1cigarette.chat.ru/ | cheap cigarette]
[http://discount1cigaret.chat.ru/ | cigarette discount]
[http://marlb1cigarette.chat.ru/ | marlboro cigarette]
[http://free1cigarette.chat.ru/ | duty free cigarette]
[http://onlinecigarette.chat.ru/ | online cigarette]
[http://camelcigarette.chat.ru/ | camel cigarette]
[http://cigarettes1.chat.ru/ | cigarettes]
[http://cigarettes4free.chat.ru/ | cigarettes]
[http://cigarettes4u.chat.ru/ | cigarettes]
[http://cigarettes2u.chat.ru/ | cheap discount cigarettes]
[http://cigarettes2u.chat.ru/newport_cigarette_706.htm | wholesale newport cigarettes]
[http://cigarette4u.chat.ru/ | cigarettes]
[http://parliament-cigar.boom.ru/ | parliament cigarettes]
[http://cigarettes.hotmail.ru/ | cigarettes]
[http://xw0.boom.ru/ | cheap cigarettes]
[http://yt15.boom.ru/ | discount cigarettes]
----
[CategoryDocumentation]

Goal

To solve problems inherent to layer 3 client roaming

This is needed because as a wireless user moves between specific nodes, several things change.

  • Association
  • Leased DHCP Address
  • Layer 2 State

Requirements

These would be the absolute basic requirements of each node that was a part of the network. Definitions follow further down.

  • Node IP Registry
  • Node Standards for DHCP

Assumptions

TCP/IP Protocol Stack Layer n refferences are based on the following 4-Layer Model:

Application

4

Data Link

3

Network

2

Network Access

1

Procedure

The following attempts to outline a basic solution that addresses these issues as simply as possible, yet still maintain efficiency and expandability as the wireless cloud grows.

Client A comes within range of Node A for the very first time. Assuming no previous contact the following should happen automatically, without client intervention.

  • Client A establishes Layer 2 connectivity with Node A (this should be automatic so long as the AccessPoint doesn't use WEP and the clients ESSID is set to either "Any" or "www.personaltelco.net")

  • After connectivity at Layer 2 is established for Client A Layer 3 connectivity should be established automatically

  • DHCP issues a lease at this time, completing the initial steps

Once initialized the complete route must be established through further means. This can be accomplished with any Portal system (such as NoCatAuth).

The following steps are required when Client A leaves the coverage area of Node A and enters the established coverage area of Node B.

  • Connectivity to Node A at Layer 2 will be broken automatically, however the Node A Layer 3 DHCP lease will remain

  • Layer 2 connectivity will be re-established with Node B

  • DHCP information from Node A will persist until Client A's lease expires

  • Once the old lease expires, a new lease will be obtained from Node B

Details Concerning the IP Registry

The IP Registry will be a central storage point for information concerning the IP assignments for the wireless network. These will be internal non-routable IP addresses as specified in RFC1918.

Class A addresses will be in the 10.0.0.0/8 range. Each node will be given some portion of the available addresses. This information will be centrally maintained and kept consistent with the current network state. The chosen method of storage can be any easily updated information distributing medium.

An Example of the IP assignments could be as follows:

  • 10.0.1.0/24 - reserved
  • 10.0.2.0/27 - Node NNX
  • 10.0.2.32/27 - Node NNY
  • 10.0.2.64/27 - Node NNZ
  • etc...

If needed, route aggregation could be obtained by assigning specific blocks to specific regions.

Node Standards for DHCP

Each node will be identically configured with the obvious exception of the specific DHCP address pool which is configured according to information set in the IP Registry Database. Arbitrary standards may be specified that fit each networks specific conditions. It is generally assumed that each stations ESSID will remain the same through out the network (Note: there is still some debate as to whether it is better to have a single ESSID for all AccessPoints or whether to have a slightly different ESSID for each).

Example DHCP configuration:

  • Gateway: 10.0.0.1
  • Primary DNS: 10.0.0.2
  • Secondary DNS: 10.0.0.3
  • Netmask: 255.0.0.0
  • Domain: www.personaltelco.net
  • Lease Time: 600 seconds
  • Address Pool: Assigned from node IP registry

Note on DNS: It has been suggested that Public, routable IP addresses be used for DNS to facilitate accesibiltity to all members of the network. Only adequate testing could determine the best solution. Either may work sufficiently provided the DNS assigned at Node A works when the client roams to Node B.

Portal Authentication System Requirements

  • Ability to authenticate at Node A and recieve a cookie upon succesful authentication.

  • Upon Moving to Node B connectivity is updated at Layers 2 and 3 as explained previously.

  • Traffic from Client A will be routed to the Portal running at Node B

  • The centralized authentication server will recognize the cookie previously set by Node A

  • Authentication information will be updated at Node B

  • All traffic will be routed to the public internet as requested

At this point a browser is required to re-authenticate at the new node.

--

This draft was originally proposed by AdamShand on Fri, 5 Oct 2001 16:58:12, and discussed by other list members over the course of the next few days. It should deffinitely be considered a Work In Progress and any PersonalTelco member is welcome and encouraged to add comments and make appropriate changes. Remember to sign your name to any changes so you can get credit ;).

-- EliabHelon


[CategoryDocumentation]

NatBasedClientRoaming (last edited 2007-11-23 18:01:03 by localhost)