atc » networking http://blog.beplacid.net Musings of technology, sport, life et al Thu, 10 Jun 2010 10:24:24 +0000 http://wordpress.org/?v=2.9.2 en hourly 1 Xbox Live home network port forwarding http://blog.beplacid.net/2009/04/21/xbox-live-home-network-port-forwarding/ http://blog.beplacid.net/2009/04/21/xbox-live-home-network-port-forwarding/#comments Tue, 21 Apr 2009 11:15:40 +0000 atc http://blog.beplacid.net/?p=68 I’ve moved house and being nowhere near the router that connects us to the net, I had to purchase an Xbox Wireless Adapter (rip-off!). Once it was setup, I had to test the network connection. For some reason UPnP wasn’t working even when enabled on the Linksys WRT54GR, so I had to set up port forwarding. The ports needed by Xbox Live are as follows:

  • TCP 80
  • UDP 88
  • TCP & UDP 3074
  • TCP & UDP 53

I found those details on the official knowledge base article found here. Hope that helps!

]]> http://blog.beplacid.net/2009/04/21/xbox-live-home-network-port-forwarding/feed/ 0 Virtualbox 2.1.x VBoxAddIf no longer exists (command not found) http://blog.beplacid.net/2009/02/16/virtualbox-21x-vboxaddif-no-longer-exists-command-not-found/ http://blog.beplacid.net/2009/02/16/virtualbox-21x-vboxaddif-no-longer-exists-command-not-found/#comments Mon, 16 Feb 2009 23:30:25 +0000 atc http://blog.beplacid.net/?p=64 or, “What happened to VboxAddIf?!”

I decided to upgrade to Virtualbox 2.1 the other day as I wanted to keep up to date. It’s a great bit of software.

One of the VMs I use regularly runs Debian and serves as a development environment and a nagios server for monitoring the various sites I host here at beplacid.net. Unfortunately, a command I relied on regularly was VBoxAddIf to setup a bridged network device between my host (also Debian) and the guest instance. According to this bug report, networking has been completely rewritten in VirtualBox 2.x, therefore VBoxAddIf (the script) is no longer relevant.

There are two ways you can fix this: use the GUI to configure the VM to use one of your host devices, or if you’re headless, setup the network using VBoxManage modifyvm. The user manual (section 8.5.3) has the best collection of information on it. For me, I do the following to force the VM to use my previously created bridge device br0. It’ll do for now until I’ve got more time to investigate and do it properly:

VBoxManage modifyvm debian -nic1 hostif -hostifdev1 br0

You’ll need to run the command while the VM is not running.

]]> http://blog.beplacid.net/2009/02/16/virtualbox-21x-vboxaddif-no-longer-exists-command-not-found/feed/ 0 Pyela – Python Eternal Lands APIs http://blog.beplacid.net/2008/07/27/pyela-python-eternal-lands-apis/ http://blog.beplacid.net/2008/07/27/pyela-python-eternal-lands-apis/#comments Sun, 27 Jul 2008 10:55:33 +0000 atc http://blog.beplacid.net/2008/07/27/pyela-python-eternal-lands-apis/ Some time ago, I began hacking away at a simple API (Application Programming Interface) for Eternal Lands written in Python. I intended to write something that was quick and concise, and that would be easy to reuse. Using a typical OO approach, I finally came up with ‘Pyela – Python Eternal Lands API’.

Pyela is an object oriented (OO) API for communicating with an Eternal Lands server. It aims to be a simple wrapper for socket operations and messages that pertain to the undocumented Eternal Lands Network Protocol. A demonstration of the API is easy to see in the Pyela – GUI application, which is a Eternal Lands chat client written using Pyela. You can download that here.

Pyela is released under the GPL3 and is open to patches and any suggestions you may have and is hosted by Google code – pyela.googlecode.com.

]]> http://blog.beplacid.net/2008/07/27/pyela-python-eternal-lands-apis/feed/ 0