Differences between revisions 6 and 47 (spanning 41 versions)

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.104
nameserver	131.215.125.1
nameserver	131.215.139.100
nameserver	131.215.254.99

See the Martian host table for IP address assignments on the martian network.
When you want to add a new host to the Martian network read this.
To ssh to one of the martian computers from a GC computer, ssh into controls@nodus, then use name (or name.martian) for the name. i.e.
```
ssh pianosa.martian 
```

Wireless Network

On Jan 6th, 2016, the martian wifi router was replaced to Netgear R6400. Link to the corresponding ELOG entry https://nodus.ligo.caltech.edu:8081/40m/11916

This router supports 2GHz network (11g) named "40MARS" and 5GHz network (11ac) "40MARS_5G". These two SSIDs are hidden.

Wireless Bridge for GPIB instruments

On Jan 8th, 2016, a new wireless bridge (NETGEAR EX3700) for GPIB instruments is installed.

Device Name: EX3700_1, Fixed IP: 192.168.113.233

It accepts ethernet (wired) device with fixed IP of 192.168.113.XXX

How_To_Configure_NETGEAR_EX3700

Nameserver and DHCP

chiara runs the DNS and DHCP for the Martian network, set up largely in the manner detailed in this website.

Configuration files can be found at

chiara:/etc/bind/named.conf.local
chiara:/etc/dhcp/dhcpd.conf

and other files in those same directories.

Mount linux1

If you want to mount the /cvs/cds NFS filesystem on a computer already on the martian network, add the following line to the file /etc/fstab

chiara:/home/cds              /cvs/cds        nfs     rw,bg,nfsvers=3

Then make the directory where the linux1 will be mounted, and try to mount the filesystem via

mkdir -p /cvs/cds
sudo mount /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.

-  ⇤ ← Revision 6 as of 2008-09-17 17:32:59 → 
  Size: 2796
  Editor: JoeBetzwieser
  Comment:
+   ← Revision 47 as of 2017-02-15 19:31:02 → ⇥
  Size: 2908
  Editor: EricquinteroATligoDOTorg
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 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:
-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:
-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:
-The wireless network is on the martian network.
+ . The wireless network is on the martian network.
 Line 13:
-|| Gateway    || 131.215.113.2    ||
+|| Gateway    || 192.168.113.2    ||
 Line 15:
+|| nameserver || 192.168.113.104  ||
-Line 19:
+Line 20:
-See also [[Martian Host Table]] for IP address assignments on the martian network.
+ . See the [[Martian_Host_Table|Martian host table]] for IP address assignments on the martian network.

 . When you want to add a new host to the Martian network [[CDS/How_to_join_martian | read this]].

 . To ssh to one of the martian computers from a GC computer, ssh into `controls@nodus`, then use `name` (or `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.
+On Jan 6th, 2016, the martian wifi router was replaced to Netgear R6400. Link to the corresponding ELOG entry [[https://nodus.ligo.caltech.edu:8081/40m/11916]]
-Line 26:
+Line 32:
-== How to setup linux1 with a name server ==
+This router supports 2GHz network (11g) named "40MARS" and 5GHz network (11ac) "40MARS_5G". These two SSIDs are hidden.
-Line 28:
+Line 34:
-) Linux1 needs network interface statically configured.  Example on Debian:  edit /etc/network/interfaces, make an entry like
+== Wireless Bridge for GPIB instruments ==
-Line 30:
+Line 36:
-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
+On Jan 8th, 2016, a new wireless bridge (NETGEAR EX3700) for GPIB instruments is installed.
-Line 37:
+Line 38:
-(but figure out how on a CentOS box, it'll be different).
+Device Name: EX3700_1, Fixed IP: 192.168.113.233
-Line 39:
+Line 40:
-) Setup the name system-config-bind (needs to be done locally with GUI).  Notes:
+It accepts ethernet (wired) device with fixed IP of 192.168.113.XXX
-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)
+[[How_To_Configure_NETGEAR_EX3700]]
-Line 45:
+Line 44:
-) Add 127.0.0.1 to /etc/resolv.conf before all the other name servers, as in
+== Nameserver and DHCP ==
`chiara` runs the DNS and DHCP for the Martian network, set up largely in the manner detailed in [[https://blogging.dragon.org.uk/dns-with-bind9-and-dhcp-on-ubuntu-14-04/|this website]].
 Line 47:
-nameserver 127.0.0.1
+Configuration files can be found at{{{
chiara:/etc/bind/named.conf.local
chiara:/etc/dhcp/dhcpd.conf
}}}
-Line 49:
+Line 52:
-At this point you should be able to do host name look-ups:  "host linux1.martian"  If not, fix before continuing
+and other files in those same directories.
-Line 51:
+Line 54:
-) replace dhcpv6_client with dhclient and add dhcp (the server package).
+== Mount linux1 ==
If you want to mount the `/cvs/cds` NFS filesystem on a computer already on the martian network, add the following line to the file {{{/etc/fstab}}}{{{
chiara:/home/cds              /cvs/cds        nfs     rw,bg,nfsvers=3
}}}
-Line 53:
+Line 59:
-) edit config file (/etc/dhcp3/dhcpd.conf on a Debian system).
+Then make the directory where the ''linux1'' will be mounted, and try to mount the filesystem via {{{
mkdir -p /cvs/cds
sudo mount /cvs/cds}}}
-Line 55:
+Line 63:
-) 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.
+== 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.
-Line 57:
+Line 66:
-) when you edit a config file, you'll need to restart the service.  for example, with
+|| '''network address''' || 192.168.113.178 || ||
|| '''internal address'''|| 192.168.1.1 || ||
|| ''' DHCP address '''  || 192.168.1.100-150|| currently disabled ||
-Line 59:
+Line 70:
-/etc/init.d/bind restart
+ . Anyone can log in to the router by any web browser. The login password is set to {{{admin}}}.