Differences between revisions 20 and 31 (spanning 11 versions)
← Revision 20 as of 2004-08-05 10:34:49 →
Size: 4212
Editor: nat-wv
Comment:
← Revision 31 as of 2004-08-05 14:31:11 →
Size: 5354
Editor: nat-wv
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
subversion repository  subversion repository.
Line 6: Line 6:
( http://svn.personaltelco.net/svn/ptp )      * http://svn.personaltelco.net/svn/ptp
Line 8: Line 8:
to build a Captive Portal Personal Telco Branded router on a computer with two ethernet cards. To build a Captive Portal Personal Telco Branded router on a computer with two ethernet cards and
subversion installed on the computer used to run node-preconfig.sh
Line 25: Line 26:
256M Swap           256M Swap
Line 27: Line 28:
256M /           256M /
Line 29: Line 30:
512M /var           512M /var
Line 31: Line 32:
1G /home           1G /home
Line 36: Line 37:
Perform a minimal stable install easily accomplished with a Debian Stable r3 or r2 netinst disk. 1. Perform a minimal stable install easily accomplished with a Debian Stable r3 or r2 netinst disk.
Line 38: Line 39:
Install with a 2.4 kernel      1. Install with a 2.4 kernel
Line 40: Line 41:
boot: bf2.4           * boot: bf24
Line 43: Line 44:
Do not run taskel '''Do not run taskel'''
Line 45: Line 46:
Do not run dselect '''Do not run dselect'''

2. Installation will Reboot to finish installation
     2. Upon Reboot
 
          * only create the root user
          * tell the mail subsystem to do nothing
          * enable all choices
          * for encrypting passwords
          * answer the default for most other questions (More detail later)
Line 48: Line 58:
Upon reboot, only create the root user, tell the mail subsystem to do nothing, enable all choices
for encrypting passwords, and answer the default for most other questions (More detail later) 		'''Do not run taskel'''
Line 51: Line 60:

Do not run taskel

Do not run dselect 		'''Do not run dselect'''
Line 58: Line 64:
Go to http://maps.personaltelco.net/ 1. Go to http://maps.personaltelco.net/
Line 60: Line 66:
Create an entry in nodedb which contains the details of the node location. Please use the naming scheme 2. Create an entry in nodedb which contains the details of the node location.
     2. Please use the naming scheme
Line 62: Line 69:
'Personal Telco - Node Name'           * 'Personal Telco - Node Name'
                a. Could this be expanded to Personal Telco - Quadrant - Neighborhood - Node Name ?
                       * e.g. Personal Telco - NE - Kerns - Urban Grind
                       * Personal Telco - NW - Pearl - Urban Grind
Line 64: Line 74:
Could this be expanded to Personal Telco - Quadrant - Neighborhood - Node Name ?

e.g. Personal Telco - NE - Kerns - Urban Grind
     Personal Telco - NW - Pearl - Urban Grind

Document the Node number which was assigned to the location. 		3. Document the Node number which was assigned to the location.
Line 76: Line 81:
Go to the wiki page NetworkAddressAllocations and define the network that will be used for the node.

'''Please use network allocations that are efficient for the network you are installing'''

ie. You probably don't need to use a full /24 		1. Go to the wiki page NetworkAddressAllocations
     * define the network that will be used for the node.
     a. '''Please use network allocations that are efficient for the network you are installing'''
          * ie. You probably don't need to use a full /24
Line 84: Line 88:
Create a working directory to run the builder script node-preconfig.sh 1. Create a working directory to run the builder script node-preconfig.sh
     1. If you have a local copy of the ptp repository on the machine your are performing this on '''do this step outside of the repository tree'''
Line 86: Line 91:
If you have a local copy of the repository on the machine your are performing this stop on '''do this
outside of the repository tree''' 		          * mkdir builder
          * cd builder
Line 89: Line 94:
mkdir builder 2. Get the script from subversion that will do the configuration
          * wget http://svn.personaltelco.net/svn/ptp/code/trunk/builder/node-preconfig.sh
Line 91: Line 97:
cd builder 3. Prepare the script for execution
          * chmod 755 node-preconfig.sh
Line 93: Line 100:
wget http://svn.personaltelco.net/svn/ptp/code/trunk/builder/node-preconfig.sh 4. Run node-preconfig.sh with the -s option
Line 95: Line 102:
chmod 755 node-preconfig.sh           * ./node-preconfig.sh -s
Line 97: Line 104:
Now run node-preconfig.sh with the -s option

./node-preconfig.sh -s

and complete the following questions in a way that is applicable to your node location: 		5. Complete the following questions in a way that is applicable to your node location
Line 104: Line 107:
[aaronb@laptop builder]$ ./node-preconfig.sh -s           * [aaronb@laptop builder]$ ./node-preconfig.sh -s
Line 106: Line 109:
Node number: 608                     Node number: 608
Line 108: Line 111:
Location (20 char. or less): Urban Grind - Pearl District                     Location (20 char. or less): Urban Grind - Pearl District
Line 110: Line 113:
Contact: ops@personaltelco.net                     Contact: ops@personaltelco.net
Line 112: Line 115:
Hostname: grank                     Hostname: grank
Line 114: Line 117:
Domain: personaltelco.net                     Domain: personaltelco.net
Line 116: Line 119:
FQDN is grank.personaltelco.net                     FQDN is grank.personaltelco.net
Line 118: Line 121:
Internet IP address (or 'dhcp'): dhcp                     Internet IP address (or 'dhcp'): dhcp
Line 120: Line 123:
Internet DNS address 1: 64.122.195.142                     Internet DNS address 1: 64.122.195.142
Line 122: Line 125:
Internet DNS address 2 (or 'none'): 198.107.22.251                     Internet DNS address 2 (or 'none'): 198.107.22.251
Line 124: Line 127:
PTPnet IP address: 10.11.47.1                     PTPnet IP address: 10.11.47.1
Line 126: Line 129:
PTPnet network address: 10.11.47.0                     PTPnet network address: 10.11.47.0
Line 128: Line 131:
PTPnet network mask: 255.255.255.0                     PTPnet network mask: 255.255.255.0
Line 130: Line 133:
PTPnet broadcast address: 10.11.47.255                     PTPnet broadcast address: 10.11.47.255
Line 132: Line 135:
PTPnet DHCP server pool start address: 10.11.47.50                     PTPnet DHCP server pool start address: 10.11.47.50
Line 134: Line 137:
PTPnet DHCP server pool finish address: 10.11.47.200                     PTPnet DHCP server pool finish address: 10.11.47.200
Line 136: Line 139:


This will create and commit the configuration files for your node into the repository 		          * This will create and commit the configuration files for your node into the repository
Line 142: Line 143:
From the command line on the machine that is going to be the captive portal router perform these steps
as root in root's home directory. 		=== From the command line on the machine that is going to be the captive portal router ===
     * perform these steps as root in root's home directory.
Line 145: Line 146:
apt-get install wget 1. Install wget
     *apt-get install wget
Line 147: Line 149:
wget http://svn.personaltelco.net/svn/ptp/code/trunk/builder/node.sh 2. Use wget to retreive node.sh
     * wget http://svn.personaltelco.net/svn/ptp/code/trunk/builder/node.sh
Line 149: Line 152:
chmod 755 node.sh 3. Make the script executabe
     * chmod 755 node.sh
Line 151: Line 155:
./node.sh [NODEID]

ie..

./node.sh 608 		4. Run the script
     * ./node.sh [NODEID]
          * example: ./node.sh 608
Line 161: Line 163:



---

[CategorySoftware]
[CategoryNode]
[CategoryNuCab]
[CategoryDocumentation]
[CategoryNetwork]

How to use Builder to create a Node

This page is intended to formalize how to use the current Builder scripts in the PTP subversion repository.

To build a Captive Portal Personal Telco Branded router on a computer with two ethernet cards and subversion installed on the computer used to run node-preconfig.sh

The current state of builder is a working proof of concept. In the future all of the fuctionality of these process will be part of Adhocracy.

Step One (Prepare the Hardware)

For a matter of maintaining support and stability in a rational way we have choosen to use Debian Woody (Stable) as the Linux distribution to build upon. These scripts expect to find a computer that has a minimal debian install, two ethernet cards, and a connection to the Internet.

partition the hard disk

Currently the most common hard drive size that we have been using is a 2G drive. Normally this is the way the partitions are created.

  • 256M Swap 256M / 512M /var 1G /home

install Debian Woody

1. Perform a minimal stable install easily accomplished with a Debian Stable r3 or r2 netinst disk.

  1. Install with a 2.4 kernel
    • boot: bf24

Do not run taskel

Do not run dselect

2. Installation will Reboot to finish installation

  1. Upon Reboot
    • only create the root user
    • tell the mail subsystem to do nothing
    • enable all choices
    • for encrypting passwords
    • answer the default for most other questions (More detail later)

Do not run taskel

Do not run dselect

Step Two (Create Nodedb Entry)

1. Go to http://maps.personaltelco.net/

2. Create an entry in nodedb which contains the details of the node location.

  1. Please use the naming scheme
    • 'Personal Telco - Node Name'
      1. Could this be expanded to Personal Telco - Quadrant - Neighborhood - Node Name ?
        • e.g. Personal Telco - NE - Kerns - Urban Grind
        • Personal Telco - NW - Pearl - Urban Grind

3. Document the Node number which was assigned to the location.

Step Three (Create Configuration Files)

Define Network Address Allocation

1. Go to the wiki page NetworkAddressAllocations

  • define the network that will be used for the node.

  • Please use network allocations that are efficient for the network you are installing

    • ie. You probably don't need to use a full /24

Create files with node-preconfig.sh

1. Create a working directory to run the builder script node-preconfig.sh

  1. If you have a local copy of the ptp repository on the machine your are performing this on do this step outside of the repository tree

    • mkdir builder
    • cd builder

2. Get the script from subversion that will do the configuration

3. Prepare the script for execution

  • chmod 755 node-preconfig.sh

4. Run node-preconfig.sh with the -s option

  • ./node-preconfig.sh -s

5. Complete the following questions in a way that is applicable to your node location

  • [aaronb@laptop builder]$ ./node-preconfig.sh -s
    • Node number: 608 Location (20 char. or less): Urban Grind - Pearl District

      Contact: ops@personaltelco.net Hostname: grank Domain: personaltelco.net FQDN is grank.personaltelco.net Internet IP address (or 'dhcp'): dhcp Internet DNS address 1: 64.122.195.142 Internet DNS address 2 (or 'none'): 198.107.22.251 PTPnet IP address: 10.11.47.1 PTPnet network address: 10.11.47.0 PTPnet network mask: 255.255.255.0 PTPnet broadcast address: 10.11.47.255 PTPnet DHCP server pool start address: 10.11.47.50 PTPnet DHCP server pool finish address: 10.11.47.200

  • This will create and commit the configuration files for your node into the repository

Step Four (Make it all come together)

From the command line on the machine that is going to be the captive portal router

  • perform these steps as root in root's home directory.

1. Install wget

  • apt-get install wget

2. Use wget to retreive node.sh

3. Make the script executabe

  • chmod 755 node.sh

4. Run the script

  • ./node.sh [NODEID]
    • example: ./node.sh 608

And now watch it go. When this finished reboot the machine and you should now have a working Personal Telco Captive Portal Machine including all services to provide the network infrustructure at the location with all configuration files stored and managed in subversion.

---

[CategorySoftware] [CategoryNode] [CategoryNuCab] [CategoryDocumentation] [CategoryNetwork]

UsingBuilderHowTo (last edited 2012-04-25 13:48:08 by DanRasmussen)