- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Decnet over IP
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-02-2008 05:35 PM
тАО01-02-2008 05:35 PM
Does anyone know how to limit which IP interfaces the port 399 listener uses?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-02-2008 07:01 PM
тАО01-02-2008 07:01 PM
Re: Decnet over IP
DISABLE NODE 0 CSMA-CD STATION CSMACD-1
Use whatever the particular device ENABLE command specified in NET$CSMACD_STARTUP.NCL might be. You will want to DISABLE what the NET$CSMACD_STARTUP.NCL script ENABLEs for your particular target NIC.
To make this DECnet-Plus configuration change survive a reboot, comment out the CREATE and ENABLE lines for the device in the NCL file. This file is located in SYS$MANAGER: for the host.
Other potential options include IP firewalls, depending on what your particular goal might be.
Stephen Hoffman
HoffmanLabs LLC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-02-2008 07:04 PM
тАО01-02-2008 07:04 PM
Re: Decnet over IP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-03-2008 12:41 AM
тАО01-03-2008 12:41 AM
Re: Decnet over IP
DECnet-over-IP works at the transport layer.
I'm pretty sure, that it does not help to disable the CSMA-CD station trying to prevent DECnet-over-IP incoming traffic on that specific LAN interface.
The CSMA-CD station controls the DECnet datalink layer protocols (DECNETV and DECNET as shown by SDA> SHOW LAN).
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-03-2008 11:49 AM
тАО01-03-2008 11:49 AM
Re: Decnet over IP
I'll assume that you want to limit DECnet over IP use to specific NICs. You need to deal with both ports 102 and 399. These show up as OSI transport templates for RFC1006 and RFC1006-Plus in the entity heirarchy you look at with NCL. They're the hook across to the PWIP driver which then gets you out of the DECnet stack into the TCP/IP stack, thus using TCP/IP as a transport for DECnet.
Stopping the DECnet protocol on the NICs isn't going to achieve what you need - in fact if you were only using DECnet over IP you could entirely turn off DECnet at the routing circuit and CSMACD station layers because you've jumped sideways through the PWIP driver into the TCP/IP stack before you reach that far down the layers.
I've not tried to do what you want to achieve, but I would guess that you want to use some kind of filtering capability within the TCP/IP stack, or perhaps within the PWIP driver (if that's possible).
I'd guess it's mostly an inbound problem that you're trying to protect against. The outbound NIC will be selected by the TCP/IP stack based on the target IP address / subnet and the local interface addresses and routes in the usual manner.
By the time the data packets hit the DECnet stack I suspect that all the NIC related information has been stripped off and it's down to IP subnets and IP routing to find the path back when you talk back through the PWIP driver to the TCP/IP stack.
It seems to me that you'd want to interpose a filter at the point where the TCP/IP interface entity attempts to establish the connection to the entity listening on ports 102 and 399.
I have some vague recollection that you can do that kind of thing, probably by writing code and hooking your code into the TCP/IP stack at the point where it attempts to establish a connection (kind of an extra layer of security filtering).
There might also be logical names that help control the behaviour of the ports 102 and 399 listeners.
Much of this kind of behaviour is part of IPsec, so you should try the OpenVMS TCP/IP V5.7 IPsec EAK available at: http://h71000.www7.hp.com/openvms/products/ipsec/index.html - do give it a go and let us know how you get on.
Cheers, Colin (http://www.xdelta.co.uk).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-04-2008 02:07 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-04-2008 11:32 PM
тАО01-04-2008 11:32 PM
Re: Decnet over IP
URL: http://h71000.www7.hp.com/doc/83final/decnetplus/DECNET_PLUS_REL_NOTES.PDF
Extract of section 2.1.3:
2.1.3.1 Added information about Configuring the system to listen to DECnet/IP connections
Version 8.3 The following commands have been added to reflect the new feature described in
Section 2.1.2 for V8.3
$MC NCL SET OSI TRANSPORT RFC1006 LISTENER IPADDRESSES {a.b.c.d, w.x.y.z}
$MC NCL ADD OSI TRANSPORT RFC1006 LISTENER IPADDRESSES {a.b.c.d, w.x.y.z}
$MC NCL REMOVE OSI TRANSPORT RFC1006 LISTENER IPADDRESSES {a.b.c.d,
w.x.y.z}
$MC NCL SHOW OSI TRANSPORT RFC1006 LISTENER IPADDRESSES
These commands will enable or disable DECnet-Plus to listen to inbound DECnet
over IP connections on interfaces having local node IP addresses specified.
However, these commands do not support DECnet-Plus to listen to remote node
IP addresses. This is applicable for both RFC 1006 and RFC 1859.
Cheers, Colin (http://www.xdelta.co.uk).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-06-2008 10:50 AM
тАО01-06-2008 10:50 AM
Re: Decnet over IP
Thanks again to all,
Randy S.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-06-2008 10:54 AM
тАО01-06-2008 10:54 AM