Difference between revisions of "Archive:Sarn"

From Tardis
Jump to: navigation, search
Line 1: Line 1:
{{XenSystem
+
{{Server
 
|name=Sarn
 
|name=Sarn
|dom0=[[WOTAN]]
+
|os=Debian Linux (Lenny 2.6.26-2-xen-686)
|cpu=1
 
|ram=160 Mb
 
|os=Debian Linux (Lenny 2.6.18-6-xen-686)
 
 
|dns=sarn.xen.tardis.ed.ac.uk
 
|dns=sarn.xen.tardis.ed.ac.uk
 
|ipv4=193.62.81.16
 
|ipv4=193.62.81.16
|ipv6=
+
|ipv6=none
 +
|hardware=domU on [[WOTAN]] with 160B RAM
 +
|services=Used by [[User:blip2]] for parsing PunkBuster streams
 +
|other=
 
}}
 
}}
  
'''Sarn''' is a virtual machine running on [[WOTAN]]. It is being used by [[User:blip2]] for parsing PunkBuster streams.
 
 
The system uses the proprietary PBUCON system to connect to a dynamic list of servers and receive the punkbuster logs from each via encrypted udp packets. Servers must be correctly configured to allow a connection to be established and a connection will only be established once a server has been checked and approved manually (more to prevent any old server being added via the web interface than security).
 
The system uses the proprietary PBUCON system to connect to a dynamic list of servers and receive the punkbuster logs from each via encrypted udp packets. Servers must be correctly configured to allow a connection to be established and a connection will only be established once a server has been checked and approved manually (more to prevent any old server being added via the web interface than security).
 +
 
A separate port is required for each connection due to the way the PBUCON system works. Mainly so it doesn't get confused between servers as the header system isn't particularly robust. An internal UDP port is also required to provide an interface to send commands to the PBUCON process.
 
A separate port is required for each connection due to the way the PBUCON system works. Mainly so it doesn't get confused between servers as the header system isn't particularly robust. An internal UDP port is also required to provide an interface to send commands to the PBUCON process.
  
 
[[Category:Xen Systems]]
 
[[Category:Xen Systems]]

Revision as of 17:16, 18 March 2010

Sarn
Operating System: Debian Linux (Lenny 2.6.26-2-xen-686)
Hostname: sarn.xen.tardis.ed.ac.uk
IPv4: 193.62.81.16
IPv6: none
Hardware:
domU on WOTAN with 160B RAM
Primary Services:
Used by User:blip2 for parsing PunkBuster streams
Other Information:

The system uses the proprietary PBUCON system to connect to a dynamic list of servers and receive the punkbuster logs from each via encrypted udp packets. Servers must be correctly configured to allow a connection to be established and a connection will only be established once a server has been checked and approved manually (more to prevent any old server being added via the web interface than security).

A separate port is required for each connection due to the way the PBUCON system works. Mainly so it doesn't get confused between servers as the header system isn't particularly robust. An internal UDP port is also required to provide an interface to send commands to the PBUCON process.