Traven Network Configuration

IP allocation

Traven is on the 69.90.134.128/25 subnet, gateway 69.90.134.129.

interface	url	ip no.
eth0	traven.indymedia.org	248
eth0:1	publish.indymedia.org.uk	249
eth0:2	publish.armenia.indymedia.org	252
eth0:3	publish.nyc.indymedia.org	253
eth0:4	earth	191
eth0:5	sun	192
eth0:6	moon	193
eth0:7	biotech	194
eth1	reserved for IPMI card	251

We are currently allocated 191-197, 248-249, 251-253

Apache is set up to use wild cards for http and https, this means that you can't test stuff using IP addresses before dns switches are made, the way around this is to edit your /etc/hosts file locally.

Sites awaiting allocation

• IMC Poland
• IMC Euskal-Herria
• IMC Bolivia (to be moved from the dutch mir server)
• IMC Ecuador (to be moved from kosmos)
• IMC Romania (to be moved from kosmos)
• IMC Qollasuyu (to be moved from kosmos)

Other notes

Traven has two network interfaces, eth0 and eth1. Currently only eth0 is physically connected. Its primary IP address is 69.90.134.248, and this is what is in DNS for traven.indymedia.org.

We're not sure which network interface the IPMI card talks to -- it might require eth1 connecting. We might also prefer to have it using a different interface to the main one -- possibly on a physically separate network that is only accessible from other trusted machines in the rack.

As an aside, some very odd behaviour occurred with an earlier configuration, where .249 was assigned to eth1, but nevertheless the machine responded on that IP even though eth1 had no physical connection (ie presumably eth0 was issuing bogus ARP responses for .249, and the kernel was accepting packets addressed to that IP on the wrong interface...)

Firewall

This is configured from /etc/init.d/iptables, which is run during boot prior to bringing up the network interfaces. Essentially it allows only ssh, www and https traffic, plus munin from the local subnet.

---

-- GarconDuMonde - 02 Jun 2005