|
Size: 1017
Comment:
|
Size: 2796
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| The 40m has two network segments: the general Caltech network and an internal "martian" network. | The 40m has two network segments: the LIGO general computing network and an internal "martian" network. |
| Line 3: | Line 3: |
| = Caltech network = | = LIGO Caltech network = |
| Line 24: | Line 24: |
| the same as given above for the Martian network. | the same as given above for the Martian network. The configuration password for the wireless AP is written in a manilla folder in the usual place where equipment manuals are kept. == How to setup linux1 with a name server == 1) Linux1 needs network interface statically configured. Example on Debian: edit /etc/network/interfaces, make an entry like iface eth0 inet static name Marvell Technology Group Ltd. Yukon Gigabit Ethernet 10/100/1000Base-T Adapter address 131.215.113.20 netmask 255.255.255.0 broadcast 131.215.113.255 network 131.215.131.0 (but figure out how on a CentOS box, it'll be different). 2) Setup the name system-config-bind (needs to be done locally with GUI). Notes: - periods are important - the forward look up (name to IP address) can list multiple names for the same IP address. use this to give IP addresses to "services" not just specific computers. For example, "ns.martian" is the name server, and can have the same IP address as "linux1.martian". - in named.conf.options be sure to enable all the interfaces that are needed, including the loop-back device (127.0.0.1) 3) Add 127.0.0.1 to /etc/resolv.conf before all the other name servers, as in nameserver 127.0.0.1 At this point you should be able to do host name look-ups: "host linux1.martian" If not, fix before continuing 4) replace dhcpv6_client with dhclient and add dhcp (the server package). 5) edit config file (/etc/dhcp3/dhcpd.conf on a Debian system). 6) turn off all other dhcp servers on network (linksys thing), and try rebooting something and see if it picks up an IP address and gets told the correct gateway and name server blah blah blah. 7) when you edit a config file, you'll need to restart the service. for example, with /etc/init.d/bind restart |
The 40m has two network segments: the LIGO general computing network and an internal "martian" network.
LIGO Caltech network
IP addresses on this network are in the form 131.215.114.XXX
Martian network
IP addresses on the martian network are in the form 131.215.113.XXX
The wireless network is on the martian network.
Gateway |
131.215.113.2 |
netmask |
255.255.255.0 |
nameserver |
131.215.125.1 |
nameserver |
131.215.139.100 |
nameserver |
131.215.254.99 |
See also Martian Host Table for IP address assignments on the martian network.
Wireless Network
The wireless network is part of the Martian Network. The Martian ethernet is bridged to wireless via a Linksys Wireless-G access point with IP address 131.215.113.220. Note that the wireless access point is only bridging the wired and wireless networks--it does not do NAT. To access the outside world, your network settings should be the same as given above for the Martian network. The configuration password for the wireless AP is written in a manilla folder in the usual place where equipment manuals are kept.
How to setup linux1 with a name server
1) Linux1 needs network interface statically configured. Example on Debian: edit /etc/network/interfaces, make an entry like
iface eth0 inet static
- name Marvell Technology Group Ltd. Yukon Gigabit Ethernet 10/100/1000Base-T Adapter address 131.215.113.20 netmask 255.255.255.0 broadcast 131.215.113.255 network 131.215.131.0
(but figure out how on a CentOS box, it'll be different).
2) Setup the name system-config-bind (needs to be done locally with GUI). Notes:
- periods are important - the forward look up (name to IP address) can list multiple names for the same IP address. use this to give IP addresses to "services" not just specific computers. For example, "ns.martian" is the name server, and can have the same IP address as "linux1.martian". - in named.conf.options be sure to enable all the interfaces that are needed, including the loop-back device (127.0.0.1)
3) Add 127.0.0.1 to /etc/resolv.conf before all the other name servers, as in
nameserver 127.0.0.1
At this point you should be able to do host name look-ups: "host linux1.martian" If not, fix before continuing
4) replace dhcpv6_client with dhclient and add dhcp (the server package).
5) edit config file (/etc/dhcp3/dhcpd.conf on a Debian system).
6) turn off all other dhcp servers on network (linksys thing), and try rebooting something and see if it picks up an IP address and gets told the correct gateway and name server blah blah blah.
7) when you edit a config file, you'll need to restart the service. for example, with
/etc/init.d/bind restart