XMission Wiki - User contributions [en]

Dialup Access Numbers

2010-01-25T23:35:15Z

Josh:

'''Utah'''
:Area code 801
::Salt Lake City - 801-990-0900
::Ogden - 801-409-0900
::Provo - 801-437-0900
::Orem - 801-437-0900
::Heber - 1-801-437-0900
:Area code 435
::Bear River - 435-279-9090
::Beaver - 435-261-4013
::Brigham City - 435-553-4055
::Logan - 435-213-4013
::Minersville - 435-386-1728
::Park City - 435-655-0900
::Richfield - 435-633-4055
::St. George - 435-772-9416
::Salina - 435-633-4055
::Tooele - 435-579-0900

For a text list of numbers in other states, click here:

[http://wiki.xmission.com/numbers.txt http://wiki.xmission.com/numbers.txt]

Dialup Access Numbers

2010-01-25T23:32:08Z

Josh: Replacing page with ''''Utah''' :Area code 801 ::Salt Lake City - 801-990-0900 ::Ogden - 801-409-0900 ::Provo - 801-437-0900 ::Orem - 801-437-0900 ::Heber - 1-801-437-0900 :Area code 435 ::Bear Riv...'

How Secure Web (SSL) Works

2009-01-22T19:34:50Z

Josh: /* Your Options */

{{hostingheader}}
==Overview==
Most web sites will use SSL encryption for collecting personal or confidential information. You'll most often see the use of SSL encryption when purchasing something online or viewing private statistics or documents. You'll notice that the URL (or web address) will start with https:// instead of http://. Your browser will recognize this is secure. The process is usually very smooth on the client's side. This may be an option that you're looking into for your web site hosted by XMission.

In more detail, SSL, Secure Sockets Layer, is the leading security protocol on the Internet. When an SSL session is started, the browser sends its public key to the server so that the server can securely send a secret key to the browser. The browser and server exchange data via secret key encryption during that session.

An SSL certificate is a unique digital ID that can be used to verify the identity of a person, web site, or JavaScript/Java Applet. The certificate always includes a public key, the name of the entity it identifies, an expiration date, the name of the certificate authority (CA) that issued the certificate, the digital signature of the CA, and a serial number. These certificates use public key cryptography to sign and authenticate signatures and are protected by public and private key pairs linked by cryptographic algorithms. These keys have the ability to encrypt and decrypt information.

==Your Options==
If you'd like to use SSL encryption for your web site/domain hosted on XMission, you have a few options.

The first, and easiest, would be to use XMission's certificate. To do this, change the URL's of the pages you wish to secure to https://www.xmission.com/~username/securepage.html where you replace user name with your XMission user name and securepage.html with the page you wish to secure. This could, however, be a problem for you if you have your own domain name. Reason being, you must use the XMission domain in the URL instead of www.yourdomain.com. For more details about using this method, please refer to the [http://wiki.xmission.com/index.php/Hosting:SSL_Tutorial SSL Tutorial].

If you have your own domain and you do not wish to use the XMission domain in the pages you wish to secure, you may get a certificate signed by XMission. A certificate signed by XMission is free of charge to any XMission customer. Once again, however, there is a problem with this method. Your visitors will be prompted with "Unknown Authority" (or something similar, depending on the browser used) when they first visit the secured pages. This has the possibility of scaring off potential clients or customers that are easily spooked by "hackers" or viruses. A certificate signed by XMission, however, is just as secure as a certificate signed by a public CA. You can request a certificate signed by XMission by filling out the request form.

The last means of using SSL with XMission would be to purchase a signed certificate and key from GeoTrust or another CA. When this is done, you will need to upload the signed certificate (public key) and the RSA key (private key) in PEM format. To make this process more secure, you may request that XMission generate the RSA key to be kept on XMission and send you the unsigned certificate. You can then have the certificate signed and returned to XMission with less threat of the RSA private key (which will not leave XMission's hands) being seen by another party.

To complete SSL Certificate process, please email [mailto:ssl@xmission.com ssl@xmission.com] with the following information:

* Do you want a certificate signed by XMission, or signed by another CA such as GeoTrust?
* Your XMission account name.
* Name of organization.
* Which department of this organization is this for?
* Website to be certified (i.e. www.domain.com or store.domain.com)
* Contact email for website (e.g. webmaster@domain.com)
* City
* State
* Country
* SSL Certificate approver email address? (e.g. ssladmin@domain.com, or whois admin/tech contact)

Important: A site with multiple domain names pointing to the SSL certified site needs to give strong consideration to purchasing a wildcard SSL service. Otherwise the site visitor will be presented with a browser error regarding the non-matching SSL certificate.

<div class="messagebox metadata">'''Note''': If you requested that XMission send you a blank certificate to be signed by another CA, the certificate will be emailed to the account you specified as your XMission account name. You'll need to upload the signed certificate to your home directory and notify us at [mailto:ssl@xmission.com ssl@xmission.com] to complete the process.</div>

===Public CA's===
Here is a small list of public CA's you can purchase certificates from (in alphabetical order).

*[http://www.abaecom.com/ ABAecom]
*[http://www.digsigtrust.com/ Digital Signature Trust Co.]
*[http://www.e-certify.com/ E-Certify]
*[http://www.entrust.net/ Entrust]
*[http://www.equifax.com/ Equifax]
*[http://www.globalsign.com/ GlobalSign]
*[http://www.tc-trustcenter.com/ TC Trustcenter]
*[http://www.thawte.com/ Thawte]
*[http://www.valicert.com/ Valicert]
*[http://www.verisign.com/ Verisign]

{{footer}}
[[Category:Hosting|SSL]]

How Secure Web (SSL) Works

2009-01-22T19:33:00Z

Josh: /* Your Options */

{{hostingheader}}
==Overview==
Most web sites will use SSL encryption for collecting personal or confidential information. You'll most often see the use of SSL encryption when purchasing something online or viewing private statistics or documents. You'll notice that the URL (or web address) will start with https:// instead of http://. Your browser will recognize this is secure. The process is usually very smooth on the client's side. This may be an option that you're looking into for your web site hosted by XMission.

In more detail, SSL, Secure Sockets Layer, is the leading security protocol on the Internet. When an SSL session is started, the browser sends its public key to the server so that the server can securely send a secret key to the browser. The browser and server exchange data via secret key encryption during that session.

An SSL certificate is a unique digital ID that can be used to verify the identity of a person, web site, or JavaScript/Java Applet. The certificate always includes a public key, the name of the entity it identifies, an expiration date, the name of the certificate authority (CA) that issued the certificate, the digital signature of the CA, and a serial number. These certificates use public key cryptography to sign and authenticate signatures and are protected by public and private key pairs linked by cryptographic algorithms. These keys have the ability to encrypt and decrypt information.

==Your Options==
If you'd like to use SSL encryption for your web site/domain hosted on XMission, you have a few options.

The first, and easiest, would be to use XMission's certificate. To do this, change the URL's of the pages you wish to secure to https://www.xmission.com/~username/securepage.html where you replace user name with your XMission user name and securepage.html with the page you wish to secure. This could, however, be a problem for you if you have your own domain name. Reason being, you must use the XMission domain in the URL instead of www.yourdomain.com. For more details about using this method, please refer to the [http://wiki.xmission.com/index.php/Hosting:SSL_Tutorial SSL Tutorial].

If you have your own domain and you do not wish to use the XMission domain in the pages you wish to secure, you may get a certificate signed by XMission. A certificate signed by XMission is free of charge to any XMission customer. Once again, however, there is a problem with this method. Your visitors will be prompted with "Unknown Authority" (or something similar, depending on the browser used) when they first visit the secured pages. This has the possibility of scaring off potential clients or customers that are easily spooked by "hackers" or viruses. A certificate signed by XMission, however, is just as secure as a certificate signed by a public CA. You can request a certificate signed by XMission by filling out the request form.

The last means of using SSL with XMission would be to purchase a signed certificate and key from GeoTrust or another CA. When this is done, you will need to upload the signed certificate (public key) and the RSA key (private key) in PEM format. To make this process more secure, you may request that XMission generate the RSA key to be kept on XMission and send you the unsigned certificate. You can then have the certificate signed and returned to XMission with less threat of the RSA key (which will won't leave XMission's hands) to be seen by another party.

To complete SSL Certificate process, please email [mailto:ssl@xmission.com ssl@xmission.com] with the following information:

* Do you want a certificate signed by XMission, or signed by another CA such as GeoTrust?
* Your XMission account name.
* Name of organization.
* Which department of this organization is this for?
* Website to be certified (i.e. www.domain.com or store.domain.com)
* Contact email for website (e.g. webmaster@domain.com)
* City
* State
* Country
* SSL Certificate approver email address? (e.g. ssladmin@domain.com, or whois admin/tech contact)

Important: A site with multiple domain names pointing to the SSL certified site needs to give strong consideration to purchasing a wildcard SSL service. Otherwise the site visitor will be presented with a browser error regarding the non-matching SSL certificate.

<div class="messagebox metadata">'''Note''': If you requested that XMission send you a blank certificate to be signed by another CA, the certificate will be emailed to the account you specified as your XMission account name. You'll need to upload the signed certificate to your home directory and notify us at [mailto:ssl@xmission.com ssl@xmission.com] to complete the process.</div>

===Public CA's===
Here is a small list of public CA's you can purchase certificates from (in alphabetical order).

*[http://www.abaecom.com/ ABAecom]
*[http://www.digsigtrust.com/ Digital Signature Trust Co.]
*[http://www.e-certify.com/ E-Certify]
*[http://www.entrust.net/ Entrust]
*[http://www.equifax.com/ Equifax]
*[http://www.globalsign.com/ GlobalSign]
*[http://www.tc-trustcenter.com/ TC Trustcenter]
*[http://www.thawte.com/ Thawte]
*[http://www.valicert.com/ Valicert]
*[http://www.verisign.com/ Verisign]

{{footer}}
[[Category:Hosting|SSL]]

How Secure Web (SSL) Works

2009-01-22T19:18:23Z

Josh: /* Your Options */

{{hostingheader}}
==Overview==
Most web sites will use SSL encryption for collecting personal or confidential information. You'll most often see the use of SSL encryption when purchasing something online or viewing private statistics or documents. You'll notice that the URL (or web address) will start with https:// instead of http://. Your browser will recognize this is secure. The process is usually very smooth on the client's side. This may be an option that you're looking into for your web site hosted by XMission.

In more detail, SSL, Secure Sockets Layer, is the leading security protocol on the Internet. When an SSL session is started, the browser sends its public key to the server so that the server can securely send a secret key to the browser. The browser and server exchange data via secret key encryption during that session.

An SSL certificate is a unique digital ID that can be used to verify the identity of a person, web site, or JavaScript/Java Applet. The certificate always includes a public key, the name of the entity it identifies, an expiration date, the name of the certificate authority (CA) that issued the certificate, the digital signature of the CA, and a serial number. These certificates use public key cryptography to sign and authenticate signatures and are protected by public and private key pairs linked by cryptographic algorithms. These keys have the ability to encrypt and decrypt information.

==Your Options==
If you'd like to use SSL encryption for your web site/domain hosted on XMission, you have a few options.

The first, and easiest, would be to use XMission's certificate. To do this, change the URL's of the pages you wish to secure to https://www.xmission.com/~username/securepage.html where you replace user name with your XMission user name and securepage.html with the page you wish to secure. This could, however, be a problem for you if you have your own domain name. Reason being, you must use the XMission domain in the URL instead of www.yourdomain.com. For more details about using this method, please refer to the [http://wiki.xmission.com/index.php/Hosting:SSL_Tutorial SSL Tutorial].

If you have your own domain and you do not wish to use the XMission domain in the pages you wish to secure, you may get a certificate signed by XMission. A certificate signed by XMission is free of charge to any XMission customer. Once again, however, there is a problem with this method. Your visitors will be prompted with "Unknown Authority" (or something similar, depending on the browser used) when they first visit the secured pages. This has the possibility of scaring off potential clients or customers that are easily spooked by "hackers" or viruses. A certificate signed by XMission, however, is just as secure as a certificate signed by a public CA. You can request a certificate signed by XMission by filling out the request form.

The last means of using SSL with XMission would be to purchase a signed certificate and key from GeoTrust or another CA. When this is done, you will need to upload the signed certificate (public key) and the RSA key (private key) in PEM format. To make this process more secure, you may request that XMission generate the RSA key to be kept on XMission and send you the unsigned certificate. You can then have the certificate signed and returned to XMission with less threat of the RSA key (which will won't leave XMission's hands) to be seen by another party.

To complete SSL Certificate process, please email [mailto:ssl@xmission.com ssl@xmission.com] with the following information:

* Do you want a certificate signed by XMission, or signed by another CA such as GeoTrust?
* Your XMission account name.
* Name of organization.
* Which department of this organization is this for?
* Website to be certified (i.e. www.domain.com or store.domain.com)
* Contact email for website (e.g. webmaster@domain.com)
* City
* State
* Country
* SSL Certificate approver email address? (e.g. ssladmin@domain.com, or whois admin/tech contact)

Important: A site with multiple domains pointing to the SSL certified site need to give strong consideration to purchasing a wildcard SSL service. Otherwise the site visitor will be presented with a browser notice regarding the non-matching SSL certificate.

<div class="messagebox metadata">'''Note''': If you requested that XMission send you a blank certificate to be signed by another CA, the certificate will be emailed to the account you specified as your XMission account name. You'll need to upload the signed certificate to your home directory and notify us at [mailto:ssl@xmission.com ssl@xmission.com] to complete the process.</div>

===Public CA's===
Here is a small list of public CA's you can purchase certificates from (in alphabetical order).

*[http://www.abaecom.com/ ABAecom]
*[http://www.digsigtrust.com/ Digital Signature Trust Co.]
*[http://www.e-certify.com/ E-Certify]
*[http://www.entrust.net/ Entrust]
*[http://www.equifax.com/ Equifax]
*[http://www.globalsign.com/ GlobalSign]
*[http://www.tc-trustcenter.com/ TC Trustcenter]
*[http://www.thawte.com/ Thawte]
*[http://www.valicert.com/ Valicert]
*[http://www.verisign.com/ Verisign]

{{footer}}
[[Category:Hosting|SSL]]

IP Address Justification

2008-12-18T16:57:27Z

Josh: IP Address Justification Request Form

'''IP Address Justification Request Form'''

Please submit the following form to colocates@xmission.com or your sales agent.

:XMission account name:

:Current number of hosts, users, or terminals on the network.

:Current number of remote access users.

:Current number and type of network devices (such as servers, routers, switches, etc.).

:Current number of firewalls (including the # of DMZs being used).

Below, please include any additional information about your network or business
practices that you feel would justify additional IPs. It is helpful to include
a 3 month projected number for all of the previous items, especially if excess
IPs are being requested to accommodate for near term growth.

----

'''REFERENCE: IP Subnet Chart'''

<table border="0" cellpadding="4" cellspacing="1" cols="4" width="450">
<tr>
<th colspan="4">Class C Address Space</th>
</tr>
<tr bgcolor="#5d7790">
<th width="48">Prefix</th>
<th width="116">Subnet Mask</th>

<th width="91">Host</th>
<th width="143">Usable</th>
</tr>
<tr bgcolor="#eeeeee">
<td width="48">/32</td>
<td width="116">255.255.255.255</td>
<td width="91">1</td>

<td width="143">1</td>
</tr>
<tr bgcolor="#dddddd">
<td width="48">/31</td>
<td width="116">255.255.255.254</td>
<td width="91">2</td>
<td width="143">0</td>

</tr>
<tr bgcolor="#eeeeee">
<td width="48">/30</td>
<td width="116">255.255.255.252</td>
<td width="91">4</td>
<td width="143">2</td>
</tr>

<tr bgcolor="#dddddd">
<td width="48">/29</td>
<td width="116">255.255.255.248</td>
<td width="91">8</td>
<td width="143">6</td>
</tr>
<tr bgcolor="#eeeeee">
<td width="48">/28</td>

<td width="116">255.255.255.240</td>
<td width="91">16</td>
<td width="143">14</td>
</tr>
<tr bgcolor="#dddddd">
<td width="48">/27</td>
<td width="116">255.255.255.224</td>

<td width="91">32</td>
<td width="143">30</td>
</tr>
<tr bgcolor="#eeeeee">
<td width="48">/26</td>
<td width="116">255.255.255.192</td>
<td width="91">64</td>

<td width="143">62</td>
</tr>
<tr bgcolor="#dddddd">
<td width="48">/25</td>
<td width="116">255.255.255.128</td>
<td width="91">128</td>
<td width="143">126</td>

</tr>
<tr bgcolor="#eeeeee">
<td width="48">/24</td>
<td width="116">255.255.255.0</td>
<td width="91">256</td>
<td width="143">254</td>
</tr>
</table>

MySQL FAQ

2008-12-17T16:49:16Z

Josh:

{{archived}}
==What is SQL?==
SQL stands for "Structured Query Language". SQL is the most common standardized language used to access databases.

XMission uses MySQL, which is a very popular open-source database management system.

==What version of MySQL does XMission use?==
XMission currently has two versions of MySQL running: version 5.0.24a and version 4.1.11. The current version is also displayed when you log in to the MySQL server.

==How much does a database at XMission cost?==
If you have a Deluxe Hosting or Pro Hosting account, an SQL database is included in your account package. For any other account type, the charge is $5 per month.

==How do I get a database set up for my account?==
To add a database to your account, either [mailto:support@xmission.com email support@xmission.com] or contact sales.

==How do I log in to my database?==
Depending on your MySQL version, you will need to connect to a different host. For MySQL version 4.x, the server name is ''mysql-41.xmission.com''
<div class="messagebox metadata">'''Note''': ''mysql.xmission.com'' is the same machine, and will work for legacy purposes.</div>

For MySQL version 5.x the server name is ''mysql-50.xmission.com''

To use a web interface to access your database, visit https://phpmyadmin.xmission.com/

To connect directly to the database from our shell server:
#telnet or ssh to ''shell.xmission.com''
#<tt>mysql -u acctname -h servername -p databasename</tt>
#This will prompt you for a password, which is not necessarily the same as your login password.

For example: to connect to a MySQL version 5.x database, you would use:
<tt>mysql -u acctname -h mysql-50.xmission.com -p databasename</tt>

==What can I use to access my database?==
There isn't a "recommended" method to access your database, but here is a list of the more popular programing languages connection methods which we support.

'''perl''' : DBI module

'''python''' : mysql module or MySQLdb module

'''php''' : php has been compiled with the mysql functions built in

'''C''' : The header and libraries for mysql are installed so #include <mysql/mysql.h> will need to be present in your source files.

'''C++''' : same as C, but we also have mysql++ headers and libraries on XMission servers. To use this, #include <sqlplus>

'''Java''' : JDBC classes are available

==What do I do if I forgot my password?==
[mailto:support@xmission.com Email support@xmission.com] to have your password reset.

==Do I have a size limit (quota) for my database?==

Yes. The size of your database counts against your /home quota, which is 100MB default for most account types. Pro Hosting accounts get 200MB /home storage, and additional storage can be purchased.

==Can I use stored routines?==

Our MySQL 5.0 server support stored functions, procedures, triggers, and other such routines. Since it is a shared server, we do not allow users to create or edit their own routines. If you would like to have a routine installed, please contact support, providing a full copy of the routine you'd like installed. We will install the routine if we decide the code does not cause any problems or cause an unreasonable support burden. If you would like more complete control over database routines, please consider our [[VPS]] or [[Colocate]] products.

==Where can I get more information about using MySQL?==

Thorough documentation can be found at [http://www.mysql.com MySQL.com].

{{Footer}}
[[Category:Hosting Archives|MySQL FAQ]]
[[Category:FAQ|MySQL]]

Cisco IOS Config

2008-09-04T18:13:58Z

Josh: New page: If you are using an IOS based Cisco router for your DSL connection, this sample IOS configuration file should help you out. ip subnet-zero ! ip dhcp excluded-address 10.0.0.1...

If you are using an IOS based Cisco router for your DSL connection, this sample IOS configuration file should help you out.

ip subnet-zero 
! 
ip dhcp excluded-address 10.0.0.1 
!--- the DHCP pool will not lease this address; it's used by ethernet interface 
! 
ip dhcp pool <pool name> 
network 10.0.0.0 255.0.0.0 
!--- you need to adjust this for your range of addresses 
default-router 10.0.0.1 
!--- default gateway will be assigned to local devices 
! 
interface FastEthernet0/0 
!--- you may need to alter this interface name depending on hardware 
ip address 10.0.0.1 255.0.0.0 
!--- replace with your network address block 
no ip directed-broadcast 
no ip mroute-cache 
! ip nat inside 
! uncomment above if you want nat 
! 
interface ATM0 
no ip address 
no ip directed-broadcast 
no ip mroute-cache 
no atm ilmi-keepalive 
pvc 0/32 
!--- pvc 0/32 is Qwest DMT default 
encapsulation aal5mux ppp dialer 
dialer pool-member 1 
! 
! 
interface Dialer0 
ip unnumbered Ethernet0 
! remove above if you want nat 
!ip address negotiated 
!ip nat outside 
! uncomment above two if you want nat 
no ip directed-broadcast 
encapsulation ppp 
dialer pool 1 
dialer-group 1 
ppp pap sent-username <username> password <password> 
!--- replace with xmission account user/pass 
! 
!ip nat inside source list 11 interface Dialer0 overload 
!access-list 11 permit 10.0.0.0 0.0.0.255 
! uncomment above for nat 
ip classless 
ip route 0.0.0.0 0.0.0.0 Dialer0 
no ip http server 
!