40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log  Not logged in ELOG logo
Entry  Thu Dec 19 21:16:16 2013, Koji, Configuration, General, netgpibdata is working again now 
    Reply  Fri Dec 20 10:08:43 2013, Jamie, Configuration, General, netgpibdata is working again now 
    Reply  Mon Apr 21 22:32:33 2014, rana, Configuration, General, netgpibdata is working again now 
       Reply  Thu Apr 24 22:39:14 2014, rana, Configuration, General, netgpibdata is working again now out.pdf
          Reply  Tue Apr 29 10:01:25 2014, Koji, Configuration, General, netgpibdata is working again now 
    Reply  Wed Sep 3 14:07:18 2014, rana, Configuration, General, netgpibdata is working again now 
Message ID: 10445     Entry time: Wed Sep 3 14:07:18 2014     In reply to: 9497
Author: rana 
Type: Configuration 
Category: General 
Subject: netgpibdata is working again now 

Quote:

I gave the IPs to the bridges. According lines of /etc/hosts in linux1 were updated.

192.168.113.230 WET54G1
192.168.113.231 WET54G2

 I was going through some old Koji elogs to check them for correctness (as I do weekly). I noticed that back in Dec 2013, he made the above illegal modification of IP numbers. 192.168.113.230 was actually the IP for farfalla. Maybe that's why they were conflicting and farfalla not working and Q observing/imagining wireless GPIB dropouts?

I used the Wiki instructions to update the 2 bind9 files with a new number for farfalla (192.168.113.212) which was previously the number for the long dead op240m. Farfalla is restarted and sort of working. 

ELOG V3.1.3-