XMission Wiki - User contributions [en]

BGP Communities

2025-09-17T18:16:22Z

Garlicky:

= Customer BGP Communities =

BGP customers can prepend, not advertise, and/or control local routing preference of their advertised routes by including community tags in their route advertisements to XMission. 
NOTE: For customers that want to use communities, please reach out to our support team so we can enable this feature on our peer.
Below are communities customers can use to control how their prefixes are routed/advertised:

{| class="wikitable"
|+ Local Preference
! Community !! Description
|-
| 65432:550 || Sets Local-Preference to 550
|-
| 65432:650 || Sets Local-Preference to 650
|-
| 65432:750 || Sets Local-Preference to 750
|-
| 65432:850 || Sets Local-Preference to 850
|-
|}

{| class="wikitable"
|+ Prepend Once
! Community !! Description
|-
| 65001:0 || Prepend Once to all upstream networks
|-
| 65001:19996 || Prepend Once to only Any2West
|-
| 65001:174 || Prepend Once to only Cogent
|-
| 65001:7922 || Prepend Once to only Comcast
|-
| 65001:6939 || Prepend Once to only Hurricane Electric
|-
| 65001:3356 || Prepend Once to only Lumen
|-
| 65001:2914 || Prepend Once to only NTT
|-
| 65001:31230 || Prepend Once to only SIX
|-
| 65001:40519 || Prepend Once to only SLIX
|-
| 65001:12345 || Prepend Once to only SuprNet
|-
| 65001:701 || Prepend Once to only Verizon
|-
|}

{| class="wikitable"
|+ Prepend Twice
! Community !! Description
|-
| 65002:0 || Prepend Twice to all upstream networks
|-
| 65002:19996 || Prepend Twice to only Any2West
|-
| 65002:174 || Prepend Twice to only Cogent
|-
| 65002:7922 || Prepend Twice to only Comcast
|-
| 65002:6939 || Prepend Twice to only Hurricane Electric
|-
| 65002:3356 || Prepend Twice to only Lumen
|-
| 65002:2914 || Prepend Twice to only NTT
|-
| 65002:31230 || Prepend Twice to only SIX
|-
| 65002:40519 || Prepend Twice to only SLIX
|-
| 65002:12345 || Prepend Twice to only Suprnet
|-
| 65002:701 || Prepend Twice to only Verizon
|-
|}

{| class="wikitable"
|+ Prepend Thrice
! Community !! Description
|-
| 65003:0 || Prepend Thrice to all upstream networks
|-
| 65003:19996 || Prepend Thrice to only Any2West
|-
| 65003:174 || Prepend Thrice to only Cogent
|-
| 65003:7922 || Prepend Thrice to only Comcast
|-
| 65003:6939 || Prepend Thrice to only Hurricane Electric
|-
| 65003:3356 || Prepend Thrice to only Lumen
|-
| 65003:2914 || Prepend Thrice to only NTT
|-
| 65003:31230 || Prepend Thrice to only SIX
|-
| 65003:40519 || Prepend Thrice to only SLIX
|-
| 65003:12345 || Prepend Thrice to only SuprNet
|-
| 65003:701 || Prepend Thrice to only Verizon
|-
|}

{| class="wikitable"
|+ No Adevertise
! Community !! Description
|-
| 65000:0 || Do not Advertise to any upstream network
|-
| 65000:19996 || Do not Advertise to Any2West
|-
| 65000:174 || Do not Advertise to Cogent
|-
| 65000:7922 ||| Do not Advertise to Comcast
|-
| 65000:6939 || Do not Advertise to Hurricane Electric
|-
| 65000:3356 || Do not Advertise to Lumen
|-
| 65000:2914 || Do not Advertise to NTT
|-
| 65000:31230 || Do not Advertise to SIX
|-
| 65000:40519 || Do not Advertise to SLIX
|-
| 65000:12345 || Do not Advertise to SuprNet
|-
| 65000:701 || Do not Advertise to Verizon
|-
|}

BGP Communities

2025-09-17T18:08:16Z

Garlicky: /* Customer BGP Communities */

= Customer BGP Communities =

BGP customers can prepend, not advertise, and/or control local routing preference of their advertised routes by including community tags in their route advertisements to XMission. 
NOTE: For customers that want to use communities, please reach out to our support team so we can enable this feature on our peer.
Below are communities customers can use to control how their prefixes are routed/advertised:

{| class="wikitable"
|+ Local Preference
! Community !! Description
|-
| 65432:550 || Sets Local-Preference to 550
|-
| 65432:650 || Sets Local-Preference to 650
|-
| 65432:750 || Sets Local-Preference to 750
|-
| 65432:850 || Sets Local-Preference to 850
|-
|}

{| class="wikitable"
|+ Prepend Once
! Community !! Description
|-
| 65001:0 || Prepend Once to all upstream networks
|-
| 65001:174 || Prepend Once to only Cogent
|-
| 65001:7922 || Prepend Once to only Comcast
|-
| 65001:6939 || Prepend Once to only Hurricane Electric
|-
| 65001:3356 || Prepend Once to only Lumen
|-
| 65001:2914 || Prepend Once to only NTT
|-
| 65001:40519 || Prepend Once to only SLIX
|-
| 65001:701 || Prepend Once to only Verizon
|-
|}

{| class="wikitable"
|+ Prepend Twice
! Community !! Description
|-
| 65002:0 || Prepend Twice to all upstream networks
|-
| 65002:174 || Prepend Twice to only Cogent
|-
| 65002:7922 || Prepend Twice to only Comcast
|-
| 65002:6939 || Prepend Twice to only Hurricane Electric
|-
| 65002:3356 || Prepend Twice to only Lumen
|-
| 65002:2914 || Prepend Twice to only NTT
|-
| 65002:40519 || Prepend Twice to only SLIX
|-
| 65002:701 || Prepend Twice to only Verizon
|-
|}

{| class="wikitable"
|+ Prepend Thrice
! Community !! Description
|-
| 65003:0 || Prepend Thrice to all upstream networks
|-
| 65003:174 || Prepend Thrice to only Cogent
|-
| 65003:7922 || Prepend Thrice to only Comcast
|-
| 65003:6939 || Prepend Thrice to only Hurricane Electric
|-
| 65003:3356 || Prepend Thrice to only Lumen
|-
| 65003:2914 || Prepend Thrice to only NTT
|-
| 65003:40519 || Prepend Thrice to only SLIX
|-
| 65003:701 || Prepend Thrice to only Verizon
|-
|}

{| class="wikitable"
|+ No Adevertise
! Community !! Description
|-
| 65000:0 || Do not Advertise to any upstream network
|-
| 65000:174 || Do not Advertise to Cogent
|-
| 65000:7922 ||| Do not Advertise to Comcast
|-
| 65000:6939 || Do not Advertise to Hurricane Electric
|-
| 65000:3356 || Do not Advertise to Lumen
|-
| 65000:2914 || Do not Advertise to NTT
|-
| 65000:40519 || Do not Advertise to SLIX
|-
| 65000:701 || Do not Advertise to Verizon
|-
|}

BGP Communities

2025-09-17T17:31:31Z

Garlicky: Created page with "= Customer BGP Communities = BGP customers can prepend, not advertise, and/or control local routing preference of their advertised routes by including community tags in their route advertisements to XMission. NOTE: For customers that want to use communities, please reach out to our support team so we can enable this feature on our peer. Below are communities customers can use to control how their prefixes are routed/advertised: {| class="wikitable" |+ Local Pref..."

= Customer BGP Communities =

BGP customers can prepend, not advertise, and/or control local routing preference of their advertised routes by including community tags in their route advertisements to XMission. 
NOTE: For customers that want to use communities, please reach out to our support team so we can enable this feature on our peer.
Below are communities customers can use to control how their prefixes are routed/advertised:

{| class="wikitable"
|+ Local Preference
! Community !! Description
|-
| 6260:550 || Sets Local-Preference to 550
|-
| 6260:650 || Sets Local-Preference to 650
|-
| 6260:750 || Sets Local-Preference to 750
|-
| 6260:850 || Sets Local-Preference to 850
|-
|}

{| class="wikitable"
|+ Prepend Once
! Community !! Description
|-
| 62601:0 || Prepend Once to all upstream networks
|-
| 62601:174 || Prepend Once to only Cogent
|-
| 62601:7922 || Prepend Once to only Comcast
|-
| 62601:6939 || Prepend Once to only Hurricane Electric
|-
| 62601:3356 || Prepend Once to only Lumen
|-
| 62601:2914 || Prepend Once to only NTT
|-
| 62601:40519 || Prepend Once to only SLIX
|-
| 62061:701 || Prepend Once to only Verizon
|-
|}

{| class="wikitable"
|+ Prepend Twice
! Community !! Description
|-
| 62602:0 || Prepend Twice to all upstream networks
|-
| 62602:174 || Prepend Twice to only Cogent
|-
| 62602:7922 || Prepend Twice to only Comcast
|-
| 62602:6939 || Prepend Twice to only Hurricane Electric
|-
| 62602:3356 || Prepend Twice to only Lumen
|-
| 62602:2914 || Prepend Twice to only NTT
|-
| 62602:40519 || Prepend Twice to only SLIX
|-
| 62062:701 || Prepend Twice to only Verizon
|-
|}

{| class="wikitable"
|+ Prepend Thrice
! Community !! Description
|-
| 62603:0 || Prepend Thrice to all upstream networks
|-
| 62603:174 || Prepend Thrice to only Cogent
|-
| 62603:7922 || Prepend Thrice to only Comcast
|-
| 62603:6939 || Prepend Thrice to only Hurricane Electric
|-
| 62603:3356 || Prepend Thrice to only Lumen
|-
| 62603:2914 || Prepend Thrice to only NTT
|-
| 62603:40519 || Prepend Thrice to only SLIX
|-
| 62063:701 || Prepend Thrice to only Verizon
|-
|}

{| class="wikitable"
|+ No Adevertise
! Community !! Description
|-
| 62600:0 || Do not Advertise to any upstream network
|-
| 62600:174 || Do not Advertise to Cogent
|-
| 62600:7922 ||| Do not Advertise to Comcast
|-
| 62600:6939 || Do not Advertise to Hurricane Electric
|-
| 62600:3356 || Do not Advertise to Lumen
|-
| 62600:2914 || Do not Advertise to NTT
|-
| 62600:40519 || Do not Advertise to SLIX
|-
| 62600:701 || Do not Advertise to Verizon
|-
|}

Peering Policy

2023-10-04T15:38:57Z

Garlicky: /* Peering Information */

== Operational Requirements ==
#Both parties provide an escalation path for resolving network issues in a timely fashion. Issues of a non-emergency technical nature should be responded to within 48 hours.
#Both parties shall be responsive to unsolicited bulk email, hacking, Denial of Service, and other network security and abuse issues. A good faith effort should be made to provide a qualified network engineer to trace ongoing network attacks within a reasonable amount of time.
#Both parties shall provide access to a route server, looking glass, or similar service for the purposes of routing audits, diagnostics, and troubleshooting.
#Both parties shall work quickly and diligently to establish additional capacity to accommodate traffic growth.

== Technical Requirements ==
#Both parties shall announce consistent routes across all interconnection points.
#Both parties are expected to register their routes in a public Internet Routing Registry (IRR) database, for the purposes of filtering. Both parties shall make good faith efforts to keep this information up to date.
#Both parties shall make every reasonable effort to restrict the transmission of Denial of Service attacks and packets with forged source addresses from their network.
#Both parties shall announce only their own routes and the routes of their transit customers to the other party. No other routes are permitted, and may be filtered if detected.
#Neither party shall establish a static route, a route of last resort, or otherwise send traffic to the other party for a route not announced via BGP. Neither party shall alter, sell, or give next-hops to a third party. These activities are considered theft of service, and will be prosecuted to the fullest extent of the law.
#Neither party shall announce to the other the more specific routes of prefixes learned via a third party transit customer.
#BGP MD5 authentication is preferred, but not required.
#Peers are expected to aggregate their routes. Anything smaller than a IPv4 /24 will be dropped.

== General Policy ==
#XMission reserves the right to change this policy at any time.
#In the event of a severe or quality-of-service impacting violation of these policies, the interconnection may be temporarily suspended without notice.
#Any interconnection may be terminated for any reason, with 30 days notice.
#All requirements must be met at the time the request for Peering is made, and must continue to be met for the duration of the interconnection.
#XMission reserves the right to accept or decline any interconnection request for any reason.

== Peering Information ==

'''ASN:''' 6315

'''[http://www.radb.net/query/ IRR AS-SET]:''' AS-XMISSION

'''[http://www.peeringdb.com/view.php?asn=6315 PeeringDB]'''

'''Suggested IPv4 Max Prefix:''' 75

'''Suggested IPv6 Max Prefix:''' 15

'''Contact:''' [mailto:peering@xmission.com peering@xmission.com]

[[Category:FAQ]][[Category:About]]

XMission Email:Outlook 2010

2019-07-12T23:46:59Z

Garlicky:

1. Click on the ''File'' menu, then go to the ''Info'' submenu and click on the ''Account Settings'' button.
:[[Image:2010-1.png]]
 
 
 
2. Click the ''New...'' button underneath the ''E-mail'' Tab.
:[[Image:2010-2.png]]
 
 
 
3. Before filling in any information check the box labeled ''Manually configure server settings or additional server types'' and click ''Next''.
:[[Image:2010-3.png]]
 
 
 
4. Select ''Internet E-mail'' from the options presented and click ''Next''.
:[[Image:2010-4.png]]
 
 
 
5. Select your preference from the ''Account Type'' drop down menu and Fill out the information on this window as seen below and then click on the ''More Settings...'' button. 
:[[Image:XM_2007-5.png]]
 
 
 
6. Goto the ''Outgoing Server'' tab and check the box that says ''My outgoing server (SMTP) requires authentication'' and make sure ''Use same settings as my incoming mail server'' is selected underneath that.
:[[Image:2010-6.png]]
 
 
 
7. Click the ''Finish'' button. You should now be able to send and receive mail.
:[[Image:2010-7.png]]

[[Category:Client Email Configuration|XMission Email|Outlook 2010]]
[[Category:XMission Email|Outlook 2010]]

Mirrors

2019-02-08T00:34:27Z

Garlicky: /* Debian */

= Mirrors =

XMission runs a publicly available software repository, consisting of GNU/Linux and BSD operating systems, popular software applications, such as Firefox and MediaWiki, as well as archives such as Project Gutenberg.

Use of this server is provided free of charge, provided that you find it useful. You are welcome to change your operating system's repository to point to "mirrors.xmission.com" to get your software updates. At a minimum, the server is updated daily, with some popular software updated more frequently.

The mirrors.xmission.com server is available using the following protocols:

* <nowiki>ftp://mirrors.xmission.com</nowiki>
* <nowiki>http://mirrors.xmission.com</nowiki>
* <nowiki>https://mirrors.xmission.com</nowiki>
* <nowiki>nfs://mirrors.xmission.com/mirrors</nowiki>
* <nowiki>rsync://mirrors.xmission.com</nowiki>

If you find this server useful, please considering purchasing services from us. See https://xmission.com for more information.

Instructions for how to use mirrors.xmission.com for your operating system are as follows:

== CentOS ==

The main repository configuration file for CentOS is <code>/etc/yum.repos.d/CentOS-Base.repo</code>. Below is an example configuration for the "base" repository.

<pre>[base]
name=CentOS-$releasever - Base
baseurl=http://mirrors.xmission.com/centos/$releasever/os/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6</pre>

CentOS supports the <code>ftp://</code>, <code>http://</code> and <code>https://</code> protocols in the <code>baseurl</code> line

== Debian ==

The main repository configuration file for Debian is <code>/etc/apt/sources.list</code>. Below is an example configuration using the Debian Stable release:

<pre>deb http://mirrors.xmission.com/debian/ stable main non-free contrib
deb-src http://mirrors.xmission.com/debian/ stable main non-free contrib
</pre>

Debian supports the <code>ftp</code>, <code>http</code> and <code>https</code> protocols in the "deb" and "deb-src" lines. For Debian to grab packages via SSL using <code>apt(8)</code>, you need to install the <code>apt-transport-https</code> package first before changing your URL:

<pre>$ sudo aptitude install apt-transport-https</pre>

== EPEL ==

EPEL (Extra Packages for Enterprise Linux) is an extra repository mainly for RHEL and CentOS systems. The main repository configuration file for EPEL is <code>/etc/yum.repos.d/epel.repo</code>. Below is an example configuration for the "epel" repository.

<pre>[epel]
name=Extra Packages for Enterprise Linux 6 - $basearch
baseurl=http://mirrors.xmission.com/fedora-epel/6/$basearch
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6</pre>

As with CentOS, the following protocols are supported in the <code>baseurl</code> line for EPEL: <code>ftp://</code>, <code>http://</code> and <code>https://</code>.

== Fedora ==

The main repository configuration file for Fedora is <code>/etc/yum.repos.d/fedora.repo</code>. Below is an example configuration for the "fedora" repository.

<pre>[fedora]
name=Fedora $releasever - $basearch
baseurl=http://mirrors.xmission.com/fedora/linux/releases/$releasever/Everything/$basearch/os/
enabled=1
metadata_expire=7d
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearch</pre>

Fedora supports the <code>ftp://</code>, <code>http://</code> and <code>https://</code> protocols in the <code>baseurl</code> line.

== Gentoo ==

By default, <code>distfiles.gentoo.org</code> is used over HTTP. To override the default behavior, and add Xmission as a primary server, you can set the <code>GENTOO_MIRRORS</code> variable in <code>/etc/portage/make.conf</code>.

<pre>GENTOO_MIRRORS="http://mirrors.xmission.com/gentoo/ ${GENTOO_MIRRORS}"</pre>

Portage supports syncing its tree with <code>ftp</code>, <code>http</code>, <code>https</code>, and <code>rsync</code> in the <code>GENTOO_MIRRORS</code> variable.

== Ubuntu ==

The main repository configuration file for Ubuntu is <code>/etc/apt/sources.list</code>. Below is an example configuration using the Ubuntu 12.04 "precise" LTS release, including the security updates:

<pre>deb http://mirrors.xmission.com/ubuntu precise main restricted universe multiverse
deb-src http://mirrors.xmission.com/ubuntu precise main restricted universe multiverse
deb http://mirrors.xmission.com/ubuntu precise-updates main restricted universe multiverse
deb-src http://mirrors.xmission.com/ubuntu precise-updates main restricted universe multiverse
deb http://mirrors.xmission.com/ubuntu-archive precise main restricted universe multiverse
deb-src http://mirrors.xmission.com/ubuntu-archive precise main restricted universe multiverse</pre>

Ubuntu supports the <code>ftp</code>, <code>http</code>, and <code>https</code> protocols in the "deb" and "deb-src" lines. For Ubuntu to grab packages via SSL using <code>apt(8)</code>, you need to install the <code>apt-transport-https</code> package first before changing your URL:

<pre>$ sudo aptitude install apt-transport-https</pre>

[[Category: Getting Started]]