Re: [Linux-decnet-user] More on Ubuntu 10.10 and DECnet
Brought to you by:
chrissie_c,
ph3-der-loewe
Menu
▾
▴
Re: [Linux-decnet-user] More on Ubuntu 10.10 and DECnet
|
From: <mik...@ta...> - 2011-06-30 13:51:20
|
Gary,
Don't know if this is any help to anyone,
We've been runing decnet happily on Kubuntu 9.10 for the last year or so
I've installed decnet on 2 new Kubuntu 11.04 machines over last couple of
weeks,
I thought it was working ok on first machine,
but had trouble getting it to work on second machine,
After lots of fiddling & looking at syslogs etc,
I think it's variable when /etc/init.d/decnet script gets run,
so sometimes MAC adress sticks, othertimes it doesn't
think everything else is ok though.
I've resorted to fixing mac adress in /etc/network/interfaces
ie;
#loopback
auto lo
iface lo inet loopback
#primary network interface
auto eth0
iface eth0 inet dhcp
metric 10
#decnet interface
auto eth1
iface eth1 inet dhcp
hwaddress ether AA:00:04:00:03:04
metric 20
It seems to work ok,
it's for a process control application
& I'd be gratetful if anyone can see anything wrong with this,
or a better way of doing it.
Thanks
Larry Baker
<ba...@us...>
To
28/06/2011 21:39 Gary Lee Phillips
<tiv...@gm...>
cc
Lin...@li...
.net
Subject
Re: [Linux-decnet-user] More on
Ubuntu 10.10 and DECnet
Gary,
I have only been casually following your e-mail thread. You might have to
take care of two issues to get your DECnet up and running. These
instructions apply to dnprogs-2.47.tar.gz.
1) Set the proper MAC address. I edit the ifcfg-eth0 configuration file to
specify a MAC address. On CentOS:
Configure the Ethernet MAC address
in /etc/sysconfig/networking/devices/ifcfg-eth0:
# vi /etc/sysconfig/networking/devices/ifcfg-eth0
# Set MAC address for DECnet host address 54.145
MACADDR=AA:00:04:00:91:D8
# Disable MAC address check in TCP/IP startup
#HWADDR=00:E0:81:2E:9E:70
2) Enable multicast reception for the interface. The exact command to do
this may vary from Linux to Linux. On CentOS:
Edit the DECnet startup/shutdown script, /etc/init.d/decnet:
#daemons="dnetd phoned"
daemons="dnetd"
echo -n $"Starting DECnet: "
NODE=`grep executor /etc/decnet.conf| awk '{print $2}'`
echo "$NODE" > /proc/sys/net/decnet/node_address
NAME=`grep executor /etc/decnet.conf| awk '{print $4}'`
echo "$NAME" > /proc/sys/net/decnet/node_name
CCT=`grep executor /etc/decnet.conf | awk '{print $6}'`
echo "$CCT" > /proc/sys/net/decnet/default_device
$prefix/sbin/setether $NODE $CCT $extra_interfaces
for i in $CCT $extra_interfaces
do
ip link set dev $i allmulticast on
done
for i in $daemons
Larry Baker
US Geological Survey
650-329-5608
ba...@us...
On 28 Jun 2011, at 1:25 PM, Gary Lee Phillips wrote:
I got a chance today to try it.
The machine for test was a netbook running Ubuntu 10.10 (Maverick
Meerkat). The kernel version was 2.6.35-8-generic-pae.
I did not try to make DECnet work over the wireless interface (yet)
but connected a standard 10base-T cable to a LAN hub.
I installed three packages from the Ubuntu repository:
libdnet
dnet-common
dnet-progs
One might expect these to have been brought up to date, but
apparently
they do not function in the same way on 10.10 as they do on 10.04,
which is in fact what I heard here.
The main problem I could see was that the MAC address of the ethernet
interface was not altered to the appropriate DECnet address. Of
course, nothing worked.
As root, I did this:
ifconfig eth0 down
ifconfig eth0 hw ether aa:00:04:00:0b:0a
ifconfig eth0 up
This set up the MAC address to match my configured Phase IV address
of 1.11.
With this one change, I found that everything I tried seemed to work,
including dnping, dndir, dntype, dntask, and dnlogin. The only
difficulties I encountered were with proxy on the remote VAX nodes,
and I believe I have to reboot those before they will recognize new
proxies added to the UAF.
Incoming connections initiated by the remote VAX nodes were being
rejected, possibly because dnetd hadn't been stopped and restarted,
but connections initiated by the laptop seemed to work as they
should.
I will look into this further, and see what it might take to convert
the existing /etc/init.d/decnet script to the upstart format. Things
are busy, I'm not sure how soon I'll have that working.
--Gary
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously
valuable.
Why? It contains a definitive record of application performance,
security
threats, fraudulent activity, and more. Splunk takes this data and
makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Project Home Page: http://linux-decnet.wiki.sourceforge.net/
Linux-decnet-user mailing list
Lin...@li...
https://lists.sourceforge.net/lists/listinfo/linux-decnet-user
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Project Home Page: http://linux-decnet.wiki.sourceforge.net/
Linux-decnet-user mailing list
Lin...@li...
https://lists.sourceforge.net/lists/listinfo/linux-decnet-user
**********************************************************************
This transmission is confidential and must not be used or disclosed by anyone other than the intended recipient. Neither Tata Steel Europe Limited nor any of its subsidiaries can accept any responsibility for any use or misuse of the transmission by anyone.
For address and company registration details of certain entities within the Tata Steel Europe group of companies, please visit http://www.tatasteeleurope.com/entities
**********************************************************************
|
