|
Size: 2796
Comment:
|
Size: 3687
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| The 40m has two network segments: the LIGO general computing network and an internal "martian" network. | ''' The 40m has two network segments: the LIGO general computing network and an internal "martian" network. ''' |
| Line 5: | Line 5: |
| IP addresses on this network are in the form 131.215.'''114'''.XXX | . IP addresses on this network are in the form 131.215.'''114'''.XXX |
| Line 9: | Line 9: |
| IP addresses on the martian network are in the form 131.215.'''113'''.XXX | . IP addresses on the martian network are in the form 192.168.'''113'''.XXX |
| Line 11: | Line 11: |
| The wireless network is on the martian network. | . The wireless network is on the martian network. |
| Line 13: | Line 13: |
| || Gateway || 131.215.113.2 || | || Gateway || 192.168.113.2 || |
| Line 15: | Line 15: |
| || nameserver || 192.168.113.20 || | |
| Line 19: | Line 20: |
| See also [[Martian Host Table]] for IP address assignments on the martian network. | . See also [[Martian_Host_Table]] for IP address assignments on the martian network. . When you add a new host to the Martian network, choose a name from [[Computers_and_Scripts/Pool_of_Names_for_Computers]]. . To ssh to one of the martian computers from a GC computer, ssh into {{{controls@nodus}}}, then use "name.martian" for the name. i.e. . {{{ssh pianosa.martian }}} |
| Line 23: | Line 30: |
| 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. |
[[https://nodus.ligo.caltech.edu:8081/40m/11916]] --------- |
| Line 26: | Line 33: |
| == How to setup linux1 with a name server == | Below this point the description is too old and is not valild any more (KA, Jan 8, 2015) |
| Line 28: | Line 35: |
| 1) Linux1 needs network interface statically configured. Example on Debian: edit /etc/network/interfaces, make an entry like | --------- |
| Line 30: | Line 37: |
| 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 |
|
| Line 37: | Line 38: |
| (but figure out how on a CentOS box, it'll be different). | == Wireless Network == |
| Line 39: | Line 40: |
| 2) Setup the name system-config-bind (needs to be done locally with GUI). Notes: | . The wireless network is part of the Martian Network. The Martian ethernet is bridged to wireless via a Linksys WRT600N wireless router with IP address https://192.168.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. |
| Line 41: | Line 42: |
| - 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) |
. You can configure the router by accessing its IP address with a web browser. . The password for configuring the wireless AP is {{{ll_admin}}}. |
| Line 45: | Line 45: |
| 3) Add 127.0.0.1 to /etc/resolv.conf before all the other name servers, as in | . The manual for the router is here: [[attachment:WRT600N_Manual.pdf]] |
| Line 47: | Line 47: |
| nameserver 127.0.0.1 | . Here are several screen shots of the configuration screens: [[attachment:screen1.pdf]] [[attachment:screen2.pdf]] [[attachment:screen3.pdf]] [[attachment:screen4.pdf]] |
| Line 49: | Line 49: |
| At this point you should be able to do host name look-ups: "host linux1.martian" If not, fix before continuing | . Here is attached the router's configuration file as of June 7, 2011. The router can reload this file if it gets lost or corrupted. [[attachment:MartianRouter.bin]] |
| Line 51: | Line 51: |
| 4) replace dhcpv6_client with dhclient and add dhcp (the server package). | . Basically, you don't care about the internet setup because you don't connect anything to the WAN port. The physical connection to the router is just one martian LAN cable to one of the LAN ports. |
| Line 53: | Line 53: |
| 5) edit config file (/etc/dhcp3/dhcpd.conf on a Debian system). | . Security is enforced by the MAC address filtering. Only registered machines can connect to the wireless network. Whenever you reset the router (not power cycle), you should register all the lab laptops to the router. |
| Line 55: | Line 55: |
| 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. | . The SSID of the martian wireless network is {{{40MARS}}}. |
| Line 57: | Line 57: |
| 7) when you edit a config file, you'll need to restart the service. for example, with | |
| Line 59: | Line 58: |
| /etc/init.d/bind restart | == Mount linux1 == . If you want to mount ''linux1'' on a computer in order to share data on Martian network, add the following line on the file {{{/etc/fstab}}} . {{{ linux1:/home/cds /cvs/cds nfs rw,bg,soft 0 0 }}} . Then make the directory where the ''linux1'' will be mounted on . {{{ mkdir /cvs && mkdir /cvs/cds }}} . Then reboot the computer. If it's mounted correctly you will find some directories under {{{/cvs/cds/}}} == Firewalling by Router:WRT310N == . A firewall is used for network isolation between a new CDS computer and the existing CDS system. It nicely allows to avoid a network conflict. For this purpose, a network router: ''LINKSYS WRT310N'' has been employed. || '''network address''' || 192.168.113.178 || || || '''internal address'''|| 192.168.1.1 || || || ''' DHCP address ''' || 192.168.1.100-150|| currently disabled || . Anyone can log in to the router by any web browser. The login password is set to {{{admin}}}. |
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 192.168.113.XXX
- The wireless network is on the martian network.
Gateway |
192.168.113.2 |
netmask |
255.255.255.0 |
nameserver |
192.168.113.20 |
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.
When you add a new host to the Martian network, choose a name from Computers_and_Scripts/Pool_of_Names_for_Computers.
To ssh to one of the martian computers from a GC computer, ssh into controls@nodus, then use "name.martian" for the name. i.e.
ssh pianosa.martian
Wireless Network
https://nodus.ligo.caltech.edu:8081/40m/11916
Below this point the description is too old and is not valild any more (KA, Jan 8, 2015)
Wireless Network
The wireless network is part of the Martian Network. The Martian ethernet is bridged to wireless via a Linksys WRT600N wireless router with IP address https://192.168.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.
- You can configure the router by accessing its IP address with a web browser.
The password for configuring the wireless AP is ll_admin.
The manual for the router is here: WRT600N_Manual.pdf
Here are several screen shots of the configuration screens: screen1.pdf screen2.pdf screen3.pdf screen4.pdf
Here is attached the router's configuration file as of June 7, 2011. The router can reload this file if it gets lost or corrupted. MartianRouter.bin
- Basically, you don't care about the internet setup because you don't connect anything to the WAN port. The physical connection to the router is just one martian LAN cable to one of the LAN ports.
- Security is enforced by the MAC address filtering. Only registered machines can connect to the wireless network. Whenever you reset the router (not power cycle), you should register all the lab laptops to the router.
The SSID of the martian wireless network is 40MARS.
Mount linux1
If you want to mount linux1 on a computer in order to share data on Martian network, add the following line on the file /etc/fstab
linux1:/home/cds /cvs/cds nfs rw,bg,soft 0 0
Then make the directory where the linux1 will be mounted on
{{{ mkdir /cvs && mkdir /cvs/cds
}}}
Then reboot the computer. If it's mounted correctly you will find some directories under /cvs/cds/
Firewalling by Router:WRT310N
A firewall is used for network isolation between a new CDS computer and the existing CDS system. It nicely allows to avoid a network conflict. For this purpose, a network router: LINKSYS WRT310N has been employed.
network address |
192.168.113.178 |
|
internal address |
192.168.1.1 |
|
DHCP address |
192.168.1.100-150 |
currently disabled |
Anyone can log in to the router by any web browser. The login password is set to admin.
