HOME ESR EXPERIMENTS LABS etc
overview Control System beam optics AP-network Vacuum NORTH ARC SOUTH ARC COOLER LINE TARGET LINE INJECTION
  AP/ESR internal privat network, Page 1 of 1  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Collapse | Expand  Show only new entries    6 Entries 
Entry  Wed Jan 20 11:16:00 2021, Jan Glorius, General, GATEWAY  
The gateway to the privat network is at the moment: atpnuc004

One can login using 'stoe_exp' or 'litv-exp' users.
Please do not use this machine for any experiment control or change the network settings!
Entry  Wed Jan 20 11:24:25 2021, Jan Glorius, General, atpnuc004: network settings interfaces 
The current network settings on atpnuc004 are documented here.

network devices (see 'interfaces' in the attachment)
eno1 - 140.181.90.221 - GSI-network
usb_eth0 - 192.168.0.1 - ESR-network

port forwarding (see 'interfaces' in the attachment):
telnet to PowerNodes {GSI: atpnuc004:992[0-3] - ESR: 192.168.0.2[0-3]:23}
Entry  Wed Jan 27 10:44:45 2021, Jan, General, debian10: USB-ethernet adapter  
Currently we are using 
LINKSYS USB ETHERNET ADAPTER - GIGABIT USB 3.0 (Model-Nr. USB3GIG-EJ)
These work as plug-and-play with debian10. 

To assign a permanent name for the network adapter (e.g. as listed by 'ip a' command) one needs to edit/create
the file 
/etc/udev/rules.d/70-persistent-net.rules 
and add for each adapter:
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="XX.XX.XX.XX.XX.XX", NAME="usb_eth0"

Then reload the rules with:
sudo udevadm control --reload-rules

The device with the given MAC address will now always be loaded as "usb_eth0".
Entry  Wed Jan 27 11:30:07 2021, Jan, General, debian10: useful network commands  
< ip a > 
overview on netwerk devices, ip-add etc

< ifdown usb_eth0 > & < ifup usb_eth0 >
unload and reload network settings for device "usb_eth0"

< nmap -sn 192.168.0.0/24 >
scan the local network for active hosts
Entry  Thu Jan 28 10:12:21 2021, Jan, General, debain10: static name for USB device 
When using USB/serial ports for slow control, it is advisable to manually bind a certain device to a certain device name.
This is the procedure:

1. connect the device and check the current assignment: 
sudo dmesg
the device might be connected as /dev/ttyUSB0 or similar

2. check the device attributes:
udevadm info --name=/dev/ttyUSB0 --attribute-walk
note unique attributes, e.g., ATTRS{idVendor}=="XXXX" and ATTRS{idProduct}=="YYYY" or ATTRS{serial}=="ZZZZ" and others

3. add a new local rule:
sudo nano /etc/udev/rules.d/10-local.rules
add the a line as:
ACTION=="add", ATTRS{idVendor}=="XXXX", ATTRS{idProduct}=="YYYY", SYMLINK+="my_device_name"

4. reload the rules:
sudo udevadm trigger

5. check and reset usb:
lsusb
check again your device, look for PRODUCT_ID:VENDOR_ID, then reset:
usbreset PRODUCT_ID:VENDOR_ID

5. verify
udevadm info /dev/ttyUSB0
this should show at the end:
E: DEVLINKS=/dev/my_device_name
and probably some more DEVLINKS in the same line
so 
udevadm info /dev/my_device_name
should also work
Entry  Wed Jan 20 11:19:03 2021, Jan Glorius, Components, List of components/IPs  
This is a list of network components and their reserved IP addresses inside the private network.


IP               component
192.168.0.1      atpnuc004 (gateway)

192.168.0.20     E127 PowerNode1 (Gude Power Control 8031)
192.168.0.21     E127 PowerNode2 (Gude Power Control 8031)
192.168.0.22     dN=0 PowerNode3 (Gude Power Control 8031)
192.168.0.23     soon: PowerNode4 (Gude Power Control 8031)

192.168.0.40     RaspberryPi LN2-control
192.168.0.41     CAEN HV for HPGe detectors
ELOG V3.1.5-fc6679b