Infrastructure: Difference between revisions
imported>Echarlie |
imported>Echarlie No edit summary |
||
| Line 16: | Line 16: | ||
Most other VTLUUG-owned servers are currently stored in [[user:dsetareh|Ali]]'s basement, with the exception of [[infrastructure:sunway|sunway]] | Most other VTLUUG-owned servers are currently stored in [[user:dsetareh|Ali]]'s basement, with the exception of [[infrastructure:sunway|sunway]] | ||
and a SuperMicro server, which were all transferred to WUVT. The list of these machines includes [[Infrastructure:Wood|Wood | and a SuperMicro server, which were all transferred to WUVT. The list of these machines includes [[Infrastructure:Wood|Wood], | ||
[[Infrastructure:Temp88191|our router]], and a variety of other servers, including our old LXC hosts, the mirror, and a DEC Alpha server. | [[Infrastructure:Temp88191|our router]], and a variety of other servers, including our old LXC hosts, the mirror, and a DEC Alpha server. | ||
| Line 41: | Line 41: | ||
to the internal network on the 10.99.x.x/16 subnet. In the future, it may be wise to bridge this network to an | to the internal network on the 10.99.x.x/16 subnet. In the future, it may be wise to bridge this network to an | ||
ethernet port on cyberdelia, so that a switch can be used to network our other services. When we have rackspace | ethernet port on cyberdelia, so that a switch can be used to network our other services. When we have rackspace | ||
to do so, | to do so, VPN/[[Iodine]] access to the internal network will be necessary. | ||
In theory, services can be provided via a hidden service (read: [[Tor]]), but that introduces other complications. | In theory, services can be provided via a hidden service (read: [[Tor]]), but that introduces other complications. | ||
Alternately, services can require use of the [[Infrastructure:IPsec|VPN]] on [[Infrastructure:acidburn|acidburn]], | Alternately, services can require use of the [[Infrastructure:IPsec|VPN]] on [[Infrastructure:acidburn|acidburn]], | ||
[[Iodine]], or [[Secure Shell|ssh tunnelling]], although all of these limit usage to members with a shell account. | [[Iodine]], or [[Secure Shell|ssh tunnelling]], although all of these limit usage to members with a shell account. | ||
== Services == | == Services == | ||
| Line 58: | Line 57: | ||
* [[Infrastructure:Razor|Razor]] | * [[Infrastructure:Razor|Razor]] | ||
** LDAP | ** LDAP | ||
* Infrastructure:Milton|Milton]]/[[Infrastructure:Sczi|Sczi]] | * [[Infrastructure:Milton|Milton]]/[[Infrastructure:Sczi|Sczi]] | ||
** Website | ** Website | ||
*** Wiki | *** Wiki | ||
| Line 181: | Line 180: | ||
Until recently, VTLUUG ran a Gopher server on Milton, with a small welcome page and access to /files. Git hosting was also provided; authenticated access was over SSH with [https://github.com/tv42/gitosis gitosis] and public access was via Gitweb and the insecure Git protocol. | Until recently, VTLUUG ran a Gopher server on Milton, with a small welcome page and access to /files. Git hosting was also provided; authenticated access was over SSH with [https://github.com/tv42/gitosis gitosis] and public access was via Gitweb and the insecure Git protocol. | ||
vtluug.org/public/$user/ was previously a source directory of files placed in a user's $HOME/public directory on NFS. | vtluug.org/public/$user/ was previously a source directory of files placed in a user's $HOME/public directory on NFS. <nowiki>[When? I thought it was always users.vtluug.org?]</nowiki> | ||
< | |||
VTLUUG members also ran '''mirror.ece.vt.edu''', although it was never an official VTLUUG project. The IPv4 allocation for this domain is still available. | VTLUUG members also ran '''mirror.ece.vt.edu''', although it was never an official VTLUUG project. The IPv4 allocation for this domain is still available. | ||
| Line 294: | Line 292: | ||
| | | | ||
|- | |- | ||
| | | | ||
| 172.xx.xx.xx (ECE DHCP) | | 172.xx.xx.xx (ECE DHCP) | ||
| snapfeed | | snapfeed | ||