linux-decnet-user — Discussion for users of DECnet on Linux

Re: [Linux-decnet-user] More on Ubuntu 10.10 and DECnet

[<mik...@ta...>]

Thanks,
I'll stick with that then,

(I tried to look at upstart, but it  gave me a headache)





                                                                           
             Chrissie                                                      
             Caulfield                                                     
             <christine.caulfi                                          To 
             el...@go...         mik...@ta...             
             m>                                                         cc 
                                       Larry Baker <ba...@us...>, Gary  
             30/06/2011 14:56          Lee Phillips                        
                                       <tiv...@gm...>,             
                                       Lin...@li... 
                                       .net                                
                                                                   Subject 
                                       Re: [Linux-decnet-user] More on     
                                       Ubuntu 10.10 and DECnet             
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




To be honest, that's how I prefer to do it!

Chrissie

On 30 Jun 2011, at 14:51, mik...@ta... wrote:

> 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
> **********************************************************************
>
------------------------------------------------------------------------------

> 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 
********************************************************************** 

Re: [Linux-decnet-user] More on Ubuntu 10.10 and DECnet

[Chrissie C. <chr...@go...>]

To be honest, that's how I prefer to do it!

Chrissie

On 30 Jun 2011, at 14:51, mik...@ta... wrote:

> 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 
> ********************************************************************** 
> ------------------------------------------------------------------------------
> 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
> 
> 

Re: [Linux-decnet-user] More on Ubuntu 10.10 and DECnet

[<mik...@ta...>]

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 
********************************************************************** 

Re: [Linux-decnet-user] More on Ubuntu 10.10 and DECnet

[Larry B. <ba...@us...>]

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
>

[Linux-decnet-user] More on Ubuntu 10.10 and DECnet

[Gary L. P. <tiv...@gm...>]

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

Re: [Linux-decnet-user] DECnet for Linux on Ubuntu

[Chrissie C. <chr...@go...>]

I'm sorry you felt brushed off by this list by the Ubuntu comment. But 
there is no-one really supporting DECnet at all at the moment, so it's 
hardly surprising people are not "paying attention" to Ubuntu. Even when 
it was under development the people doing it (mainly me) only had the 
time to work on a few selected distributions - remember this was a hobby 
project and no-one was being paid to work on it. So no matter how high 
profile a distribution may be, if a developer hasn't had the time or 
inclination to install it then they can't comment on it.

For just terminal access then LAT is a far easier solution. It's 
entirely user mode code and doesn't require a lot of complicated messing 
about with MAC addresses that DECnet does so it won't interfere with TCP/IP.

The DECnet code itself still works as far as I am aware. The Kernel 
portion is totally unmaintained so if it gets broken by the other kernel 
developers (as has happened) then it will not get fixed by any DECnet 
developers, sometimes it will get fixed as part of other networking 
patches though. The user land packages are looked-after by Philipp 
Shafft when he has time, but effectively the whole DECnet system is 
orphaned and what you are most likely to get here - and did - is support 
from other users if they feel they can help.

Chrissie

On 25/06/2011 11:31, Bengt Nilsson wrote:
> I guess I am the source of this item.
>
> The story is like follows:
> I needed terminal access from Ubuntu to a very old VAX/VMS 5.5-2H system.
> I installed decnet on a small desktop with Ubuntu 10.04 LTS, working fine.
> After upgrading to 10.10, the response to "dnlogin" was
>
> bnilsson@ubuntu:~$ dnlogin fyvax7
> Cannot connect to fyvax7: Rejected by object
>
> I reported it to this forum, and I got some suggestions, but no real
> solution in the beginning.
> The docs say that decnet must be started before the tcpip networking,
> and I suspected that the new "upstart" boot method was changing the
> order of things between 10.04 and 10.10.
> Upgrading to 11.04 did not improve the state of this behaviour either.
>
> On the forum, I got the suggestion to shut down the network, start
> decnet and restart the networking.
> This worked, I could again use "dnlogin" to connect to my VMS system.
> However, my tcpip now had only access to my own subnet, why, I do not know.
>
>
> Finally, I got the suggestion to skip decnet and use LAT instead.
> For the things I need to do, this was a better solution, without any bad
> side effects as far as I can see.
> So decnet is now removed from my desktop Ubuntu 11.04, I use "llogin"
> instead, and all is working fine.
> I will not put any more time into decnet to make it work for me, at
> least not for the time being.
>
> It seems the installation and startup methods for decnet need some
> tuning before it can be used with the current Ununtu.
> Someone with more knowledge than me need to take the time to intall
> Ubuntu and investigate what is going on. I was surprised to get the
> answer from the developers(?) that "we don't use ubuntu" and that was
> it. As Ubuntu is coming to be more or less mainstream, I would assume it
> needs to be paid attention to.
>
> Incidentally, I can mention that I did the network stop/decnet start
> tests on virtual Ubuntu 11.04 on a VMWare Fusion on my Mac, and that's
> how I found that it was working before I transferred this method to my
> real desktop Ubuntu. So setting up a test system does not need to be a
> great effort, a virtual machine will probably work fine.
>
>
> --
> Bengt Nilsson
> Nanofabrication Laboratory,
> Department of Microtechnology and Nanoscience,
> Chalmers University of Technology,
> SE-412 96 Göteborg, SWEDEN
> e-mail: ben...@ch... <mailto:ben...@ch...>
> tel: +46-31-7728480
>
>
>
>
> 24 jun 2011 kl. 20.18 skrev Gary Lee Phillips:
>
>> I've just joined the list and reading over the recent messages I saw
>> some comments to the effect that "DECnet isn't supported on Ubuntu"
>> (which I take to mean, it doesn't work.)
>>
>> I'm glad I didn't see this last week, because in my ignorance I went
>> ahead and installed the packages (from the Ubuntu repository) onto two
>> desktop machines running Ubuntu 10.04 LTS (Lucid Lynx.)
>>
>> It took a little twiddling with the configuration, but just about
>> everything seems to work as expected.
>>
>> I have Alpha hardware running OpenVMS 8.3 and virtual (SIMH) VAX
>> machines running OpenVMS 7.3. Both DECnet and TCP/IP communications
>> are working between all of them.
>>
>> Please tell me which version of Ubuntu failed to work, because I'll be
>> careful not to upgrade to it. I'll be happy to answer questions about
>> my configuration and network setup.
>>
>> (Note that in order to get a Linux hardware host to communicate with a
>> virtual VAX running on the same host, I had to use a TAP/TUN setup to
>> create a virtual ethernet bridge, but that works well with both TCP/IP
>> and DECnet as far as I can tell.)
>>
>> --Altivo
>>

Re: [Linux-decnet-user] DECnet for Linux on Ubuntu

[Gary L. P. <tiv...@gm...>]

Thanks for the information.

I rather doubt that upstart has anything to do with your problems,
since 10.04 uses it too. I haven't tried DECnet on 10.10 but I have a
laptop with 10.10 so I'll try installing it there and see what
happens.

There have been statements made that the Linux kernel no longer
supports DECnet or, more specifically, that "DECnet support in the
kernel is dead" whatever that means. Those started with versions of
the kernel much earlier than the one I am running. I have kernel
version 2.6.32-32-generic on both Linux systems that are currently
working with DECnet.

As long as existing kernel code is not stripped out, this shouldn't
matter too much, as DECnet itself hasn't changed very much for years
now, and the DECnet on Linux code uses Phase IV which hasn't changed
in more than a decade I think.

One thought on your problem with being restricted just to your local
LAN. DECnet Phase IV does change your hardware MAC address. Within the
local network, this shouldn't matter for more than a minute or so
because the arp databases will age off the old information and pick up
the new address. However, network switches and routers can be slower
to act on a change of that sort. Depending on security requirements at
your installation, they may in fact refuse to recognize a new MAC
address that has not been registered or approved. This can be
remedied, since the substitute address that Phase IV assigns is
predictable based on the Phase IV network address in use.

I'll check on Ubuntu 10.10, since I can easily do that, and report back here.

I can understand how LAT might be all you need, as it was also
recommended to me. But I have other uses for the DECnet protocol and
already had terminal style connections working over TCP/IP and through
serial port emulation. I'm particularly interested in getting X11
working over DECnet, which was apparently possible at one time, but
the links to the code and information on the Sourceforge site are
stale now and go nowhere.

--Gary

On Sat, Jun 25, 2011 at 5:31 AM, Bengt Nilsson
<ben...@ch...> wrote:
> I guess I am the source of this item.
> The story is like follows:
> I needed terminal access from Ubuntu to a very old VAX/VMS 5.5-2H system.
> I installed decnet on a small desktop with Ubuntu 10.04 LTS, working fine.
> After upgrading to 10.10, the response to "dnlogin" was
> bnilsson@ubuntu:~$ dnlogin fyvax7
> Cannot connect to fyvax7: Rejected by object
> I reported it to this forum, and I got some suggestions, but no real
> solution in the beginning.
> The docs say that decnet must be started before the tcpip networking, and I
> suspected that the new "upstart" boot method was changing the order of
> things between 10.04 and 10.10.
> Upgrading to 11.04 did not improve the state of this behaviour either.
> On the forum, I got the suggestion to shut down the network, start decnet
> and restart the networking.
> This worked, I could again use "dnlogin" to connect to my VMS system.
> However, my tcpip now had only access to my own subnet, why, I do not know.
>
> Finally, I got the suggestion to skip decnet and use LAT instead.
> For the things I need to do, this was a better solution, without any bad
> side effects as far as I can see.
> So decnet is now removed from my desktop Ubuntu 11.04, I use "llogin"
> instead, and all is working fine.
> I will not put any more time into decnet to make it work for me, at least
> not for the time being.
> It seems the installation and startup methods for decnet need some tuning
> before it can be used with the current Ununtu.
> Someone with more knowledge than me need to take the time to intall Ubuntu
> and investigate what is going on. I was surprised to get the answer from the
> developers(?) that "we don't use ubuntu"  and that was it. As Ubuntu is
> coming to be more or less mainstream, I would assume it needs to be paid
> attention to.
> Incidentally, I can mention that I did the network stop/decnet start tests
> on virtual Ubuntu 11.04 on a VMWare Fusion on my Mac, and that's how I found
> that it was working before I transferred this method to my real desktop
> Ubuntu. So setting up a test system does not need to be a great effort, a
> virtual machine will probably work fine.
>
> --
> Bengt Nilsson
> Nanofabrication Laboratory,
> Department of Microtechnology and Nanoscience,
> Chalmers University of Technology,
> SE-412 96 Göteborg, SWEDEN
> e-mail: ben...@ch...
> tel: +46-31-7728480
>

Re: [Linux-decnet-user] DECnet for Linux on Ubuntu

[Bengt N. <ben...@ch...>]

I guess I am the source of this item.

The story is like follows:
I needed terminal access from Ubuntu to a very old VAX/VMS 5.5-2H system.
I installed decnet on a small desktop with Ubuntu 10.04 LTS, working fine.
After upgrading to 10.10, the response to "dnlogin" was

bnilsson@ubuntu:~$ dnlogin fyvax7
Cannot connect to fyvax7: Rejected by object

I reported it to this forum, and I got some suggestions, but no real solution in the beginning.
The docs say that decnet must be started before the tcpip networking, and I suspected that the new "upstart" boot method was changing the order of things between 10.04 and 10.10.
Upgrading to 11.04 did not improve the state of this behaviour either.

On the forum, I got the suggestion to shut down the network, start decnet and restart the networking.
This worked, I could again use "dnlogin" to connect to my VMS system. However, my tcpip now had only access to my own subnet, why, I do not know.


Finally, I got the suggestion to skip decnet and use LAT instead.
For the things I need to do, this was a better solution, without any bad side effects as far as I can see.
So decnet is now removed from my desktop Ubuntu 11.04, I use "llogin" instead, and all is working fine.
I will not put any more time into decnet to make it work for me, at least not for the time being.

It seems the installation and startup methods for decnet need some tuning before it can be used with the current Ununtu.
Someone with more knowledge than me need to take the time to intall Ubuntu and investigate what is going on. I was surprised to get the answer from the developers(?) that "we don't use ubuntu"  and that was it. As Ubuntu is coming to be more or less mainstream, I would assume it needs to be paid attention to.

Incidentally, I can mention that I did the network stop/decnet start tests on virtual Ubuntu 11.04 on a VMWare Fusion on my Mac, and that's how I found that it was working before I transferred this method to my real desktop Ubuntu. So setting up a test system does not need to be a great effort, a virtual machine will probably work fine.


--
Bengt Nilsson
Nanofabrication Laboratory,
Department of Microtechnology and Nanoscience,
Chalmers University of Technology,
SE-412 96 Göteborg, SWEDEN
e-mail: ben...@ch...<mailto:ben...@ch...>
tel: +46-31-7728480




24 jun 2011 kl. 20.18 skrev Gary Lee Phillips:

I've just joined the list and reading over the recent messages I saw
some comments to the effect that "DECnet isn't supported on Ubuntu"
(which I take to mean, it doesn't work.)

I'm glad I didn't see this last week, because in my ignorance I went
ahead and installed the packages (from the Ubuntu repository) onto two
desktop machines running Ubuntu 10.04 LTS (Lucid Lynx.)

It took a little twiddling with the configuration, but just about
everything seems to work as expected.

I have Alpha hardware running OpenVMS 8.3 and virtual (SIMH) VAX
machines running OpenVMS 7.3. Both DECnet and TCP/IP communications
are working between all of them.

Please tell me which version of Ubuntu failed to work, because I'll be
careful not to upgrade to it. I'll be happy to answer questions about
my configuration and network setup.

(Note that in order to get a Linux hardware host to communicate with a
virtual VAX running on the same host, I had to use a TAP/TUN setup to
create a virtual ethernet bridge, but that works well with both TCP/IP
and DECnet as far as I can tell.)

--Altivo

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense..
http://p.sf.net/sfu/splunk-d2d-c1
_______________________________________________
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

[Linux-decnet-user] DECnet for Linux on Ubuntu

[Gary L. P. <tiv...@gm...>]

I've just joined the list and reading over the recent messages I saw
some comments to the effect that "DECnet isn't supported on Ubuntu"
(which I take to mean, it doesn't work.)

I'm glad I didn't see this last week, because in my ignorance I went
ahead and installed the packages (from the Ubuntu repository) onto two
desktop machines running Ubuntu 10.04 LTS (Lucid Lynx.)

It took a little twiddling with the configuration, but just about
everything seems to work as expected.

I have Alpha hardware running OpenVMS 8.3 and virtual (SIMH) VAX
machines running OpenVMS 7.3. Both DECnet and TCP/IP communications
are working between all of them.

Please tell me which version of Ubuntu failed to work, because I'll be
careful not to upgrade to it. I'll be happy to answer questions about
my configuration and network setup.

(Note that in order to get a Linux hardware host to communicate with a
virtual VAX running on the same host, I had to use a TAP/TUN setup to
create a virtual ethernet bridge, but that works well with both TCP/IP
and DECnet as far as I can tell.)

--Altivo

Re: [Linux-decnet-user] Supported linux systems?

[Bengt N. <ben...@ch...>]

18 jun 2011 kl. 14.51 skrev Bengt Nilsson:


17 jun 2011 kl. 21.46 skrev Mats Magnusson:

I see that you have solved the problem, but you could probably also
have solved it by installing the LAT programs (a separate protocol that
doesen't need ethernet adress changes e.t.c. and also the protocol
Digital themself used between their terminal servers and computers).


Possibly, but after spending an hour trying to get llogin to connect to anything I realize I am unable to understand the lat principles/documentation.
So I will have to stick to dnlogin for the time being.
Too bad, since I now realize my tcpip is limited to the local subnet when decnet is running.


Eh.. is helps if the LAT services are started on the VMS system which I was trying to connect to! After I started this service I could connect after a while.

I have removed the decnet installation from the Ubuntu since it was not needed, and I use the lat "llogin" instead.
Terminal connection to VMS and all other networking is working fine.

Case SOLVED and thanks for all the fish.



--
Bengt Nilsson
Nanofabrication Laboratory,
Department of Microtechnology and Nanoscience,
Chalmers University of Technology,
SE-412 96 Göteborg, SWEDEN
e-mail: ben...@ch...<mailto:ben...@ch...>
tel: +46-31-7728480

Re: [Linux-decnet-user] Supported linux systems?

[Bengt N. <ben...@ch...>]

17 jun 2011 kl. 21.46 skrev Mats Magnusson:

I see that you have solved the problem, but you could probably also
have solved it by installing the LAT programs (a separate protocol that
doesen't need ethernet adress changes e.t.c. and also the protocol
Digital themself used between their terminal servers and computers).


Possibly, but after spending an hour trying to get llogin to connect to anything I realize I am unable to understand the lat principles/documentation.
So I will have to stick to dnlogin for the time being.
Too bad, since I now realize my tcpip is limited to the local subnet when decnet is running.


On Fri, 17 Jun 2011 16:09:53 +0200 Bengt Nilsson
<ben...@ch...<mailto:ben...@ch...>> wrote:
Thank you very much!

However,

# sudo ifdown eth0

did not work, I got

# Ignoring unknown interface eth0=eth0.
(why?)

but this worked:

# sudo ifconfig eth0 down
# sudo setether 57.5 eth0
# dnlogin fyvax7

Welcome to VAX/VMS V5.5-2H4 on node FYVAX7 Username:



Success!

So I was right, it was the startup order.
For the time being, I can do this manually.
But for the future, the remaining thing would be to adapt to the
"upstart" scheme. But this is beyond me, at least for the moment.


--
(/)
(O.o)
(> <) Copy the bunny to your mails to help him achieve world
/_|_domination. Come join the dark side. We have cookies.

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
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


--
Bengt Nilsson
Nanotekniklaboratoriet
Mikroteknologi och Nanovetenskap
Chalmers Tekniska Högskola
412 96 Göteborg
epost: ben...@ch...<mailto:ben...@ch...>
tel: 031-7728480

Re: [Linux-decnet-user] Supported linux systems?

[Mats M. <mat...@te...>]

I see that you have solved the problem, but you could probably also
have solved it by installing the LAT programs (a separate protocol that
doesen't need ethernet adress changes e.t.c. and also the protocol
Digital themself used between their terminal servers and computers).

On Fri, 17 Jun 2011 16:09:53 +0200 Bengt Nilsson
<ben...@ch...> wrote:
> Thank you very much!
> 
> However,
> 
> # sudo ifdown eth0
> 
> did not work, I got
> 
> # Ignoring unknown interface eth0=eth0.
> (why?)
> 
> but this worked:
> 
> # sudo ifconfig eth0 down
> # sudo setether 57.5 eth0
> # dnlogin fyvax7
> 
>  Welcome to VAX/VMS V5.5-2H4 on node FYVAX7 Username:
> 
> 
> 
> Success!
> 
> So I was right, it was the startup order.
> For the time being, I can do this manually.
> But for the future, the remaining thing would be to adapt to the
> "upstart" scheme. But this is beyond me, at least for the moment.


-- 
(/)
(O.o)
(> <) Copy the bunny to your mails to help him achieve world
/_|_domination. Come join the dark side. We have cookies.

Re: [Linux-decnet-user] Supported linux systems?

[Bengt N. <ben...@ch...>]

Thank you very much!

However,

# sudo ifdown eth0

did not work, I got

# Ignoring unknown interface eth0=eth0.
(why?)

but this worked:

# sudo ifconfig eth0 down
# sudo setether 57.5 eth0
# dnlogin fyvax7

 Welcome to VAX/VMS V5.5-2H4 on node FYVAX7 Username:



Success!

So I was right, it was the startup order.
For the time being, I can do this manually.
But for the future, the remaining thing would be to adapt to the "upstart" scheme.
But this is beyond me, at least for the moment.



17 jun 2011 kl. 13.28 skrev <mik...@ta...<mailto:mik...@ta...>> <mik...@ta...<mailto:mik...@ta...>>:

Hello Bengt,

How many ethernet connection are you using?

The machines i've been using have 2 network cards,

one dedicated to decnet,
one for general use


I've been trying to get the same error as you,
and think i've managed it by  reconfiguring to just use 1 card,

If i restart machine, then network mac adress isn't getting set
(ie; ifconfig shows normal mac address)

Way round it is to:-


i) Shutdown networking
(depends on how network is configured)

sudo ifdown eth0

ii) manually set mac address

sudo setether 1.3 eth0

(substitute your dec node for 1.2)


iii) test decnet


dnlogin fyvax7


iv) restart networking
(again depends on how network is configured)

sudo ifup eth0



Hope this helps,
hopefully, easy solutiion will be to buy additional network card


Regards

Mike









            Bengt Nilsson
            <bengt.nilsson@ch
            almers.se<http://almers.se>>                                                 To
                                      Chrissie Caulfield
            17/06/2011 10:48          <chr...@go...<mailto:chr...@go...>

                                                                       cc
                                      "lin...@li...<mailto:lin...@li...>
                                      e.net<http://e.net>"
                                      <lin...@li...<mailto:lin...@li...>
                                      e.net<http://e.net>>
                                                                  Subject
                                      Re: [Linux-decnet-user] Supported
                                      linux systems?










Thanks for the info.

I am trying to set up a "intelligent terminal" to support a VAX hardware
control system, where the main control is connected via a serial line.
Decnet would be a significant enhancement to the work environment, since
you could open several parallel connections without additional serial
lines. The system has ethernet, but the VMS we have to use is too old to
support ssh.
It is a multi-user system so I prefer Ubuntu since it is more friendly to
the unix-illiterate user.

I suspect (I have stated this before) that my problem has to do with the
Ubuntu "upstart" boot sequence, and it seems decnet is not started before
tcpip. I am not compenent enough to control this, I guess someone who is
should have a look at it and hopefully adapt the package accordingly. Or at
least identfy what the problem is and suggest a fix if possible.

Anyway, whatever I do I get this message:

bnilsson@ubuntu:~$ dnlogin fyvax7
Cannot connect to fyvax7: Rejected by object

Is there ay way I can I invoke a more detailed error message?

17 jun 2011 kl. 11.05 skrev Chrissie Caulfield:

     Nothing is really 'supported' in the sense that you get guaranteed
     response to problems. But if you just want a system that will run
     DECnet
     then any Linux system will do.

     It helps if the distribution ships with the DECnet kernel module, I
     know
     that Debian and Fedora do and I *think* that SuSE used to. If you
     have a
     distribution that doesn't then you'll have to build your own kernel.
     The
     easy way to check for this is just to type "modprobe decnet" in a
     root
     shell - if it doesn't return an error then off you go :-)

     Debian also has the DECnet userspace programs packaged and part of
     the
     distro and it's moderately easy to set up. As far as I know no other
     distribution does this and there are no 3rd party packages that work.

     Having said that, it's pretty easy to build the software from source.

     The FAQ has some details about distriutions, but I'm not sure how
     up-to-date it is, sadly.

     http://sourceforge.net/apps/mediawiki/linux-decnet/index.php?title=FAQ6


     Chrissie

     On 17/06/11 09:33, Bengt Nilsson wrote:

           What linux flavors are supported for running Decnet?

           Obvously, Ubuntu seems not supported.


     ------------------------------------------------------------------------------

     EditLive Enterprise is the world's most technically advanced content
     authoring tool. Experience the power of Track Changes, Inline Image
     Editing and ensure content is compliant with Accessibility Checking.
     http://p.sf.net/sfu/ephox-dev2dev
     _______________________________________________
     Project Home Page: http://linux-decnet.wiki.sourceforge.net/

     Linux-decnet-user mailing list
     Lin...@li...<mailto:Lin...@li...>
     https://lists.sourceforge.net/lists/listinfo/linux-decnet-user


--
Bengt Nilsson
Nanotekniklaboratoriet
Mikroteknologi och Nanovetenskap
Chalmers Tekniska Högskola
412 96 Göteborg
epost: ben...@ch...<mailto:ben...@ch...>
tel: 031-7728480




------------------------------------------------------------------------------

EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Project Home Page: http://linux-decnet.wiki.sourceforge.net/

Linux-decnet-user mailing list
Lin...@li...<mailto: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
**********************************************************************

--
Bengt Nilsson
Nanotekniklaboratoriet
Mikroteknologi och Nanovetenskap
Chalmers Tekniska Högskola
412 96 Göteborg
epost: ben...@ch...<mailto:ben...@ch...>
tel: 031-7728480

Re: [Linux-decnet-user] Supported linux systems?

[Bengt N. <ben...@ch...>]

Thanks for the info.

I am trying to set up a "intelligent terminal" to support a VAX hardware control system, where the main control is connected via a serial line. Decnet would be a significant enhancement to the work environment, since you could open several parallel connections without additional serial lines. The system has ethernet, but the VMS we have to use is too old to support ssh.
It is a multi-user system so I prefer Ubuntu since it is more friendly to the unix-illiterate user.

I suspect (I have stated this before) that my problem has to do with the Ubuntu "upstart" boot sequence, and it seems decnet is not started before tcpip. I am not compenent enough to control this, I guess someone who is should have a look at it and hopefully adapt the package accordingly. Or at least identfy what the problem is and suggest a fix if possible.

Anyway, whatever I do I get this message:

bnilsson@ubuntu:~$ dnlogin fyvax7
Cannot connect to fyvax7: Rejected by object

Is there ay way I can I invoke a more detailed error message?

17 jun 2011 kl. 11.05 skrev Chrissie Caulfield:

Nothing is really 'supported' in the sense that you get guaranteed
response to problems. But if you just want a system that will run DECnet
then any Linux system will do.

It helps if the distribution ships with the DECnet kernel module, I know
that Debian and Fedora do and I *think* that SuSE used to. If you have a
distribution that doesn't then you'll have to build your own kernel. The
easy way to check for this is just to type "modprobe decnet" in a root
shell - if it doesn't return an error then off you go :-)

Debian also has the DECnet userspace programs packaged and part of the
distro and it's moderately easy to set up. As far as I know no other
distribution does this and there are no 3rd party packages that work.
Having said that, it's pretty easy to build the software from source.

The FAQ has some details about distriutions, but I'm not sure how
up-to-date it is, sadly.

http://sourceforge.net/apps/mediawiki/linux-decnet/index.php?title=FAQ6

Chrissie

On 17/06/11 09:33, Bengt Nilsson wrote:

What linux flavors are supported for running Decnet?

Obvously, Ubuntu seems not supported.


------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
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


--
Bengt Nilsson
Nanotekniklaboratoriet
Mikroteknologi och Nanovetenskap
Chalmers Tekniska Högskola
412 96 Göteborg
epost: ben...@ch...<mailto:ben...@ch...>
tel: 031-7728480

Re: [Linux-decnet-user] Supported linux systems?

[Chrissie C. <chr...@go...>]

Nothing is really 'supported' in the sense that you get guaranteed 
response to problems. But if you just want a system that will run DECnet 
then any Linux system will do.

It helps if the distribution ships with the DECnet kernel module, I know 
that Debian and Fedora do and I *think* that SuSE used to. If you have a 
distribution that doesn't then you'll have to build your own kernel. The 
easy way to check for this is just to type "modprobe decnet" in a root 
shell - if it doesn't return an error then off you go :-)

Debian also has the DECnet userspace programs packaged and part of the 
distro and it's moderately easy to set up. As far as I know no other 
distribution does this and there are no 3rd party packages that work. 
Having said that, it's pretty easy to build the software from source.

The FAQ has some details about distriutions, but I'm not sure how 
up-to-date it is, sadly.

http://sourceforge.net/apps/mediawiki/linux-decnet/index.php?title=FAQ6

Chrissie

On 17/06/11 09:33, Bengt Nilsson wrote:
>
> What linux flavors are supported for running Decnet?
>
> Obvously, Ubuntu seems not supported.
>

[Linux-decnet-user] Supported linux systems?

[Bengt N. <ben...@ch...>]

What linux flavors are supported for running Decnet?

Obvously, Ubuntu seems not supported.

BN

Re: [Linux-decnet-user] [PATCH net-next 1/2] net: Remove casts of void *

[David M. <da...@da...>]

From: Joe Perches <jo...@pe...>
Date: Mon, 13 Jun 2011 19:21:26 -0700

> Unnecessary casts of void * clutter the code.
> 
> These are the remainder casts after several specific
> patches to remove netdev_priv and dev_priv.
> 
> Done via coccinelle script:
> 
> $ cat cast_void_pointer.cocci
> @@
> type T;
> T *pt;
> void *pv;
> @@
> 
> - pt = (T *)pv;
> + pt = pv;
> 
> Signed-off-by: Joe Perches <jo...@pe...>

Applied.