Re: [TCPIP V5.4] Session Disconnects (and DISCONNECT)
From: Matt Muggeridge (Matt.Muggeridge_at_hp.com)
Date: 02/20/04
- Next message: issinoho: "Changing IP address"
- Previous message: Matt Muggeridge: "Re: [TCPIP V5.4] Session Disconnects (and DISCONNECT)"
- In reply to: JF Mezei: "Re: [TCPIP V5.4] Session Disconnects (and DISCONNECT)"
- Next in thread: Peter 'EPLAN' LANGSTOEGER: "Re: [TCPIP V5.4] Session Disconnects (and DISCONNECT)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 20 Feb 2004 01:17:21 GMT
Without trying to hijack this thread too much...
> Another suggestion I would make is some sort of hook to have a process
> notified whenever that node makes an outgoing call which fails to connect.
(so
> that we can trigger fault isolation in the network.
I see this as a separate system administration function. Failure to connect
somewhere usually results in the user realising they specified the wrong
nodename, or a call to the network administrator because they checked their
typing and still can't connect. In my mind, that seems more than
sufficient. Why have a process automatically notified anytime a connect
fails? It seems the process would have to include responses like: "oops
you mistyped the remote nodename again..."
If you want reachability confirmation to specific/important end-points, then
a separate process to monitor that would be in order.
Matt.
-- ------------------------------------------------------------- OpenVMS TCP/IP Engineering Enterprise Computing Group Hewlett-Packard Company Gold Coast, AUSTRALIA ------------------------------------------------------------- "JF Mezei" <jfmezei.spamnot@istop.com> wrote in message news:40355DE7.AE7173FA@istop.com... > Surfer boy Matt Muggeridge wrote: > > > > 3) Is there a chance that a lexical function (F$GETDVI comes to mind) will > > > (in the very near future) give me IP information (like the local IP > > address > > > In the very near future... no. If you can email me your requirement (the > > more detail the better) it will be added to our requirements list and > > reviewed during the next cycle. > > I would second this request. Being able to easily get information about where > a BG device is coming from and going to would be very good. > > When you're under attack, you want tools that get you the iformation ASAP to > track hackers. > > Another suggestion I would make is some sort of hook to have a process > notified whenever that node makes an outgoing call which fails to connect. (so > that we can trigger fault isolation in the network.
- Next message: issinoho: "Changing IP address"
- Previous message: Matt Muggeridge: "Re: [TCPIP V5.4] Session Disconnects (and DISCONNECT)"
- In reply to: JF Mezei: "Re: [TCPIP V5.4] Session Disconnects (and DISCONNECT)"
- Next in thread: Peter 'EPLAN' LANGSTOEGER: "Re: [TCPIP V5.4] Session Disconnects (and DISCONNECT)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|