Re: [Nagios-users] only_from = 127.0.0.1
Replies embedded below... Marc Powell wrote: On Apr 23, 2009, at 12:53 PM, Kevin Keane wrote: Top-posting means that you put what you have to say at the top of the reply the way I do it here. Bottom-posting means that you put your reply below the original message. Don't forget about the best method, inline reply. Yes, I should have said inline reply instead of bottom posting everywhere (and my description also wasn't quite accurate. Should have been you put your reply below the point you are replying to). True bottom posting is possibly the worst of all options, but I did mean the style that you, correctly, call inline reply. Of course, if there is only one point you are responding to, inline replying and bottom posting are one and the same. In the original Internet culture, bottom-posting was preferred, and some Actually, no. inline replying was and still is preferred for technical mailling lists. I'd hazard to say that's true the technical users on this list as well. I've been around Usenet ever since Compuserve (remember them?) started offering newsgroups, so I do remember the inline-replying culture quite well. And you may have a point. Many of the technical users of today (especially the experienced ones who tend to be the most prolific posters) are old-timers like myself, which would explain the preference among technical users. On the other hand, many people who started using the Net in this century, including even people with IT college degrees, have never seen inline replies, and don't even think to look below. The day you subscribe to a list via digest mode, you'll fully understand why. ;) LOL, don't get me started on digest mode! If I had my way, either Digest mode would be eliminated, or it would only be offered on lists that also have a good Web interface so you can properly respond to older posts as well as current ones (that's one of the reasons I much prefer Yahoo groups to Sourceforge mailing lists). In my mind, most of the time top posting actually is better because the reply stands out more than the original question - which usually is what you want. Not if you want to make multiple points without entirely restating what you're replying to. Try to make my responses sensible in a top or bottom posting context without doing that. Agreed to some extent; in fact, I think I also listed that as an advantage of inline reply (which I erroneously called bottom posting). I'm saying to an extent because if you overdo it, you can also end up with a completely chopped up discussion. It gets particularly convoluted in political flame wars... I also usually add one other enhancement when I do use inline replying: I attach a note to the top Replies embedded below because many people I reply to, especially in private emails, aren't familiar with inline replying and otherwise wouldn't think to look below. In this case, of course, it's unnecessary; I just did it for illustration purposes. My personal rule: if there already is a longer thread, stick with whatever style it has. That's great! If it's a top or bottom post, you're increasing the redundancy of what's stored/sent in everyone's mail client, in the archives and most terribly, in the digests. by the number of replies to that thread. That's got nothing much to do with top- or bottom- or inline-replying. Cutting irrelevant old stuff out is a good thing no matter which style you are using, although some people go overboard and cut out everything at all (that's a fourth style of replying, and another universally bad one: no quoting at all), and then you don't know what they are replying to. * technically speaking, there is a still-valid RFC that specifies bottom-posting, but in practical terms it has been obsoleted by history. That's arguable, but could approach the passion level of a discussion of religion. Is it getting hot here or what? :-)) -- Kevin Keane Owner The NetTech Find the Uncommon: Expert Solutions for a Network You Never Have to Think About Office: 866-642-7116 http://www.4nettech.com This e-mail and attachments, if any, may contain confidential and/or proprietary information. Please be advised that the unauthorized use or disclosure of the information is strictly prohibited. The information herein is intended only for use by the intended recipient(s) named above. If you have received this transmission in error, please notify the sender immediately and permanently delete the e-mail and any copies, printouts or attachments thereof. -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects
Re: [Nagios-users] only_from = 127.0.0.1
On Apr 24, 2009, at 2:10 AM, Kevin Keane wrote I've been around Usenet ever since Compuserve (remember them?) started Indeed. To date myself, I used to run a BBS on my C=64 ;) That certainly doesn't make me the most experienced around but I've been through a good part of the Internet history. That's arguable, but could approach the passion level of a discussion of religion. Is it getting hot here or what? :-)) heh, nah, but I think we're in close enough agreement to let it go G. -- Marc -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
[Nagios-users] only_from = 127.0.0.1
Can anybody tell me how I use domains names instead of IP address in the
nrpe file, I have read somewhere that you can use tcp wrappers which I have
tried.
My nrpe file looks like this:
# default: on
# description: NRPE (Nagios Remote Plugin Executor)
service nrpe
{
flags = REUSE
socket_type = stream
port= 5666
wait= no
user= nagios
group = nagios
server = /usr/local/nagios/bin/nrpe
server_args = -c /usr/local/nagios/etc/nrpe.cfg --inetd
log_on_failure += USERID
disable = no
only_from = 127.0.0.1
}
And my hosts.allow looks like
#
# hosts.allow This file describes the names of the hosts which are
# allowed to use the local INET services, as decided
# by the '/usr/sbin/tcpd' server.
#
nrpe: 17.0.0.1 monitor.domain.co.uk
But I'm still getting Could not complete SSL handshake, is the above
configuration correct or can I not use domain names instead of IP's
Thanks
Martyn
--
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] only_from = 127.0.0.1
On Thursday April 23 2009 11:07:06 am Martyn wrote:
Can anybody tell me how I use domains names instead of IP address in the
nrpe file, I have read somewhere that you can use tcp wrappers which I have
tried.
My nrpe file looks like this:
# default: on
# description: NRPE (Nagios Remote Plugin Executor)
service nrpe
{
flags = REUSE
socket_type = stream
port= 5666
wait= no
user= nagios
group = nagios
server = /usr/local/nagios/bin/nrpe
server_args = -c /usr/local/nagios/etc/nrpe.cfg --inetd
log_on_failure += USERID
disable = no
only_from = 127.0.0.1
}
And my hosts.allow looks like
#
# hosts.allow This file describes the names of the hosts which are
# allowed to use the local INET services, as decided
# by the '/usr/sbin/tcpd' server.
#
nrpe: 17.0.0.1 monitor.domain.co.uk
But I'm still getting Could not complete SSL handshake, is the above
configuration correct or can I not use domain names instead of IP's
You have to adjust the olny_from line, your hosts.allow allows 17.0.0.1 to
connect to nrpe, but xinetd rejects the request, because you just allows
connections from 127.0.0.1 (or is there the 2 missing in the hosts.allow
line?)
you can simply write the domain name to only_from.
If you use the hosts.allow you could even exclude the only_from line from the
xinetd configuration by setting 3 in front of the line.
Greetings,
Christian
Thanks
Martyn
--
Christian Schneemann
-
SUSE LINUX Products GmbH,
Maxfeldstr. 5, D - 90409 Nürnberg
Phone: +49 (0)911 - 740 53 0
e-mail: cschneem...@suse.de
-
SUSE LINUX Products GmbH, GF: Markus Rex
HRB 16746 (AG Nürnberg)
--
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] only_from = 127.0.0.1
I changed the line as suggested but I still get the SSL handshake issue, the
host.domain.co.uk is made up on here but I have the real one in the live
config, again thanks for your time
# default: on
# description: NRPE (Nagios Remote Plugin Executor)
service nrpe
{
flags = REUSE
socket_type = stream
port= 5666
wait= no
user= nagios
group = nagios
server = /usr/local/nagios/bin/nrpe
server_args = -c /usr/local/nagios/etc/nrpe.cfg --inetd
log_on_failure += USERID
disable = no
only_from = 127.0.0.1 192.168.3.247 host.domain.co.uk
}
-Original Message-
From: Christian Schneemann [mailto:cschneem...@suse.de]
Sent: 23 April 2009 11:05
To: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] only_from = 127.0.0.1
On Thursday April 23 2009 11:07:06 am Martyn wrote:
Can anybody tell me how I use domains names instead of IP address in
the nrpe file, I have read somewhere that you can use tcp wrappers
which I have tried.
My nrpe file looks like this:
# default: on
# description: NRPE (Nagios Remote Plugin Executor) service nrpe {
flags = REUSE
socket_type = stream
port= 5666
wait= no
user= nagios
group = nagios
server = /usr/local/nagios/bin/nrpe
server_args = -c /usr/local/nagios/etc/nrpe.cfg --inetd
log_on_failure += USERID
disable = no
only_from = 127.0.0.1
}
And my hosts.allow looks like
#
# hosts.allow This file describes the names of the hosts which are
# allowed to use the local INET services, as decided
# by the '/usr/sbin/tcpd' server.
#
nrpe: 17.0.0.1 monitor.domain.co.uk
But I'm still getting Could not complete SSL handshake, is the above
configuration correct or can I not use domain names instead of IP's
You have to adjust the olny_from line, your hosts.allow allows 17.0.0.1 to
connect to nrpe, but xinetd rejects the request, because you just allows
connections from 127.0.0.1 (or is there the 2 missing in the hosts.allow
line?)
you can simply write the domain name to only_from.
If you use the hosts.allow you could even exclude the only_from line from
the xinetd configuration by setting 3 in front of the line.
Greetings,
Christian
Thanks
Martyn
--
Christian Schneemann
-
SUSE LINUX Products GmbH,
Maxfeldstr. 5, D - 90409 Nürnberg
Phone: +49 (0)911 - 740 53 0
e-mail: cschneem...@suse.de
-
SUSE LINUX Products GmbH, GF: Markus Rex HRB 16746 (AG Nürnberg)
--
Stay on top of everything new and different, both inside and around Java
(TM) technology - register by April 22, and save $200 on the JavaOne (SM)
conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
--
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] only_from = 127.0.0.1
On Thursday April 23 2009 01:01:41 pm Martyn wrote:
I'm not being ignorant but as I complete novice on none windows boxes, how
do I put setting 3 in front of the line
Sorry, it should be #, no 3 (dumb shift mistake).
just comment the line out by putting the # in the front of the line:
# only_from = 127.0.0.1
Sorry for that,
Christian
Many thanks for your reply
Martyn
-Original Message-
From: Christian Schneemann [mailto:cschneem...@suse.de]
Sent: 23 April 2009 11:05
To: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] only_from = 127.0.0.1
On Thursday April 23 2009 11:07:06 am Martyn wrote:
Can anybody tell me how I use domains names instead of IP address in
the nrpe file, I have read somewhere that you can use tcp wrappers
which I have tried.
My nrpe file looks like this:
# default: on
# description: NRPE (Nagios Remote Plugin Executor) service nrpe {
flags = REUSE
socket_type = stream
port= 5666
wait= no
user= nagios
group = nagios
server = /usr/local/nagios/bin/nrpe
server_args = -c /usr/local/nagios/etc/nrpe.cfg --inetd
log_on_failure += USERID
disable = no
only_from = 127.0.0.1
}
And my hosts.allow looks like
#
# hosts.allow This file describes the names of the hosts which are
# allowed to use the local INET services, as decided
# by the '/usr/sbin/tcpd' server.
#
nrpe: 17.0.0.1 monitor.domain.co.uk
But I'm still getting Could not complete SSL handshake, is the above
configuration correct or can I not use domain names instead of IP's
You have to adjust the olny_from line, your hosts.allow allows 17.0.0.1
to connect to nrpe, but xinetd rejects the request, because you just allows
connections from 127.0.0.1 (or is there the 2 missing in the hosts.allow
line?)
you can simply write the domain name to only_from.
If you use the hosts.allow you could even exclude the only_from line from
the xinetd configuration by setting 3 in front of the line.
Greetings,
Christian
Thanks
Martyn
--
Christian Schneemann
-
SUSE LINUX Products GmbH,
Maxfeldstr. 5, D - 90409 Nürnberg
Phone: +49 (0)911 - 740 53 0
e-mail: cschneem...@suse.de
-
SUSE LINUX Products GmbH, GF: Markus Rex HRB 16746 (AG Nürnberg)
---
- --
Stay on top of everything new and different, both inside and around Java
(TM) technology - register by April 22, and save $200 on the JavaOne (SM)
conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when
::: reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
--
Christian Schneemann
-
SUSE LINUX Products GmbH,
Maxfeldstr. 5, D - 90409 Nürnberg
Phone: +49 (0)911 - 740 53 0
e-mail: cschneem...@suse.de
-
SUSE LINUX Products GmbH, GF: Markus Rex
HRB 16746 (AG Nürnberg)
--
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] only_from = 127.0.0.1
Please don't top-post. The only valid reason to do it is to mention something entirely unrelated to the content email you're responding to (such as asking someone to stop top-posting ;-)) Martyn wrote: I'm not being ignorant but as I complete novice on none windows boxes, how do I put setting 3 in front of the line He meant you should escape the line by adding a hash-char (#) to the beginning of the line containing 'only_from = 127.0.0.1'. I expect his fingers slipped so the shift-key didn't get pressed properly. -- Andreas Ericsson andreas.erics...@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] only_from = 127.0.0.1
I'm not being ignorant but as I complete novice on none windows boxes, how
do I put setting 3 in front of the line
Many thanks for your reply
Martyn
-Original Message-
From: Christian Schneemann [mailto:cschneem...@suse.de]
Sent: 23 April 2009 11:05
To: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] only_from = 127.0.0.1
On Thursday April 23 2009 11:07:06 am Martyn wrote:
Can anybody tell me how I use domains names instead of IP address in
the nrpe file, I have read somewhere that you can use tcp wrappers
which I have tried.
My nrpe file looks like this:
# default: on
# description: NRPE (Nagios Remote Plugin Executor) service nrpe {
flags = REUSE
socket_type = stream
port= 5666
wait= no
user= nagios
group = nagios
server = /usr/local/nagios/bin/nrpe
server_args = -c /usr/local/nagios/etc/nrpe.cfg --inetd
log_on_failure += USERID
disable = no
only_from = 127.0.0.1
}
And my hosts.allow looks like
#
# hosts.allow This file describes the names of the hosts which are
# allowed to use the local INET services, as decided
# by the '/usr/sbin/tcpd' server.
#
nrpe: 17.0.0.1 monitor.domain.co.uk
But I'm still getting Could not complete SSL handshake, is the above
configuration correct or can I not use domain names instead of IP's
You have to adjust the olny_from line, your hosts.allow allows 17.0.0.1 to
connect to nrpe, but xinetd rejects the request, because you just allows
connections from 127.0.0.1 (or is there the 2 missing in the hosts.allow
line?)
you can simply write the domain name to only_from.
If you use the hosts.allow you could even exclude the only_from line from
the xinetd configuration by setting 3 in front of the line.
Greetings,
Christian
Thanks
Martyn
--
Christian Schneemann
-
SUSE LINUX Products GmbH,
Maxfeldstr. 5, D - 90409 Nürnberg
Phone: +49 (0)911 - 740 53 0
e-mail: cschneem...@suse.de
-
SUSE LINUX Products GmbH, GF: Markus Rex HRB 16746 (AG Nürnberg)
--
Stay on top of everything new and different, both inside and around Java
(TM) technology - register by April 22, and save $200 on the JavaOne (SM)
conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
--
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] only_from = 127.0.0.1
That has now done the trick but I'm a little confused as to why this work
under host.allow and not when used in my nrpe file, does anybody have the
answer to that?
Its on Centos 5.3, I'm going to try Fedora to see if that is the same
Thanks for your help
Martyn
PS what his top posting, once I find out I will stop it
-Original Message-
From: Christian Schneemann [mailto:cschneem...@suse.de]
Sent: 23 April 2009 12:06
To: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] only_from = 127.0.0.1
On Thursday April 23 2009 01:01:41 pm Martyn wrote:
I'm not being ignorant but as I complete novice on none windows boxes,
how do I put setting 3 in front of the line
Sorry, it should be #, no 3 (dumb shift mistake).
just comment the line out by putting the # in the front of the line:
# only_from = 127.0.0.1
Sorry for that,
Christian
Many thanks for your reply
Martyn
-Original Message-
From: Christian Schneemann [mailto:cschneem...@suse.de]
Sent: 23 April 2009 11:05
To: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] only_from = 127.0.0.1
On Thursday April 23 2009 11:07:06 am Martyn wrote:
Can anybody tell me how I use domains names instead of IP address in
the nrpe file, I have read somewhere that you can use tcp wrappers
which I have tried.
My nrpe file looks like this:
# default: on
# description: NRPE (Nagios Remote Plugin Executor) service nrpe {
flags = REUSE
socket_type = stream
port= 5666
wait= no
user= nagios
group = nagios
server = /usr/local/nagios/bin/nrpe
server_args = -c /usr/local/nagios/etc/nrpe.cfg --inetd
log_on_failure += USERID
disable = no
only_from = 127.0.0.1
}
And my hosts.allow looks like
#
# hosts.allow This file describes the names of the hosts which are
# allowed to use the local INET services, as decided
# by the '/usr/sbin/tcpd' server.
#
nrpe: 17.0.0.1 monitor.domain.co.uk
But I'm still getting Could not complete SSL handshake, is the above
configuration correct or can I not use domain names instead of IP's
You have to adjust the olny_from line, your hosts.allow allows
17.0.0.1 to connect to nrpe, but xinetd rejects the request, because
you just allows connections from 127.0.0.1 (or is there the 2 missing
in the hosts.allow
line?)
you can simply write the domain name to only_from.
If you use the hosts.allow you could even exclude the only_from line
from the xinetd configuration by setting 3 in front of the line.
Greetings,
Christian
Thanks
Martyn
--
Christian Schneemann
-
SUSE LINUX Products GmbH,
Maxfeldstr. 5, D - 90409 Nürnberg
Phone: +49 (0)911 - 740 53 0
e-mail: cschneem...@suse.de
-
SUSE LINUX Products GmbH, GF: Markus Rex HRB 16746 (AG Nürnberg)
---
- --
Stay on top of everything new and different, both inside and around
Java
(TM) technology - register by April 22, and save $200 on the JavaOne
(SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when
::: reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
--
Christian Schneemann
-
SUSE LINUX Products GmbH,
Maxfeldstr. 5, D - 90409 Nürnberg
Phone: +49 (0)911 - 740 53 0
e-mail: cschneem...@suse.de
-
SUSE LINUX Products GmbH, GF: Markus Rex HRB 16746 (AG Nürnberg)
--
Stay on top of everything new and different, both inside and around Java
(TM) technology - register by April 22, and save $200 on the JavaOne (SM)
conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
--
Stay on top of everything new and different, both inside and
around Java (TM) technology
Re: [Nagios-users] only_from = 127.0.0.1
On Thursday 23 April 2009 13:35:26 Martyn wrote:
That has now done the trick but I'm a little confused as to why this work
under host.allow and not when used in my nrpe file, does anybody have the
answer to that?
As I've written in the first mail, hosts.allow is the first instance which
looks if the IP is allowed to connect to this service, then xinetd looks at
the only_from and compares the IPs.
Your only_from contains just 127.0.0.1, thats localhost, nothing else as your
server itself is allowed to connect to nrpe.
This has nothing to do with nagios/nrpe, please read about networking, xinetd,
and linux in generall if you are not familiar with it.
Greetings
Its on Centos 5.3, I'm going to try Fedora to see if that is the same
Thanks for your help
Martyn
PS what his top posting, once I find out I will stop it
-Original Message-
From: Christian Schneemann [mailto:cschneem...@suse.de]
Sent: 23 April 2009 12:06
To: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] only_from = 127.0.0.1
On Thursday April 23 2009 01:01:41 pm Martyn wrote:
I'm not being ignorant but as I complete novice on none windows boxes,
how do I put setting 3 in front of the line
Sorry, it should be #, no 3 (dumb shift mistake).
just comment the line out by putting the # in the front of the line:
# only_from = 127.0.0.1
Sorry for that,
Christian
Many thanks for your reply
Martyn
-Original Message-
From: Christian Schneemann [mailto:cschneem...@suse.de]
Sent: 23 April 2009 11:05
To: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] only_from = 127.0.0.1
On Thursday April 23 2009 11:07:06 am Martyn wrote:
Can anybody tell me how I use domains names instead of IP address in
the nrpe file, I have read somewhere that you can use tcp wrappers
which I have tried.
My nrpe file looks like this:
# default: on
# description: NRPE (Nagios Remote Plugin Executor) service nrpe {
flags = REUSE
socket_type = stream
port= 5666
wait= no
user= nagios
group = nagios
server = /usr/local/nagios/bin/nrpe
server_args = -c /usr/local/nagios/etc/nrpe.cfg --inetd
log_on_failure += USERID
disable = no
only_from = 127.0.0.1
}
And my hosts.allow looks like
#
# hosts.allow This file describes the names of the hosts which are
# allowed to use the local INET services, as decided
# by the '/usr/sbin/tcpd' server.
#
nrpe: 17.0.0.1 monitor.domain.co.uk
But I'm still getting Could not complete SSL handshake, is the above
configuration correct or can I not use domain names instead of IP's
You have to adjust the olny_from line, your hosts.allow allows
17.0.0.1 to connect to nrpe, but xinetd rejects the request, because
you just allows connections from 127.0.0.1 (or is there the 2 missing
in the hosts.allow
line?)
you can simply write the domain name to only_from.
If you use the hosts.allow you could even exclude the only_from line
from the xinetd configuration by setting 3 in front of the line.
Greetings,
Christian
Thanks
Martyn
--
Christian Schneemann
-
SUSE LINUX Products GmbH,
Maxfeldstr. 5, D - 90409 Nürnberg
Phone: +49 (0)911 - 740 53 0
e-mail: cschneem...@suse.de
-
SUSE LINUX Products GmbH, GF: Markus Rex HRB 16746 (AG Nürnberg)
---
- --
Stay on top of everything new and different, both inside and around
Java
(TM) technology - register by April 22, and save $200 on the JavaOne
(SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when
::: reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
--
Christian Schneemann
-
SUSE LINUX Products GmbH,
Maxfeldstr. 5, D - 90409 Nürnberg
Phone: +49 (0)911 - 740 53 0
e-mail: cschneem...@suse.de
-
SUSE LINUX Products GmbH, GF: Markus Rex HRB 16746 (AG Nürnberg)
---
- --
Stay on top of everything new and different, both inside and around Java
(TM) technology - register by April 22, and save $200 on the JavaOne (SM)
conference, June 2-5, 2009, San
Re: [Nagios-users] only_from = 127.0.0.1
On Apr 23, 2009, at 6:35 AM, Martyn wrote: That has now done the trick but I'm a little confused as to why this work under host.allow and not when used in my nrpe file, does anybody have the answer to that? NRPE's allowed_hosts only accepts ip addresses, not domain names. -- Marc -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] only_from = 127.0.0.1
On Apr 23, 2009, at 6:35 AM, Martyn wrote: PS what his top posting, once I find out I will stop it http://en.wikipedia.org/wiki/Posting_style, specifically http://en.wikipedia.org/wiki/Posting_style#Top-posting -- Marc -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] only_from = 127.0.0.1
On Apr 23, 2009, at 6:35 AM, Martyn wrote: PS what his top posting, once I find out I will stop it http://en.wikipedia.org/wiki/Posting_style, specifically http://en.wikipedia.org/wiki/Posting_style#Top-posting -- Marc -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null Apologies, Outlooks default. -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] only_from = 127.0.0.1
On Thursday 23 April 2009 13:47:38 Marc Powell wrote: On Apr 23, 2009, at 6:35 AM, Martyn wrote: That has now done the trick but I'm a little confused as to why this work under host.allow and not when used in my nrpe file, does anybody have the answer to that? NRPE's allowed_hosts only accepts ip addresses, not domain names. That's not correct, domain names work here too. Christian -- Marc --- --- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when ::: reporting any issue. Messages without supporting info will risk being ::: sent to /dev/null -- SUSE Linux Products GmbH Maxfeldstr. 5, D - 90409 Nürnberg Phone: +49 (0)911 - 740 53 0 e-mail: cschneem...@suse.de SUSE Linux Products GmbH, GF: Markus Rex HRB 16746 (AG Nürnberg) -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] only_from = 127.0.0.1
On Apr 23, 2009, at 7:03 AM, Christian Schneemann wrote: NRPE's allowed_hosts only accepts ip addresses, not domain names. That's not correct, domain names work here too. I stand corrected. I could swear I looked at the code for that just a few weeks ago but I'm wrong. -- Marc -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] only_from = 127.0.0.1
Top-posting means that you put what you have to say at the top of the reply the way I do it here. Bottom-posting means that you put your reply below the original message. Which of the two styles is preferred is largely a matter of personal taste, rather than right or wrong, actually*. Both have advantages, and some people tend to get very passionate about their particular style. I have seen moderators on both sides of the issue admonish members don't top-post or don't bottom-post. In the original Internet culture, bottom-posting was preferred, and some people still like it better. Bottom posting makes most sense when you combine multiple thoughts in a single post, and want to be able to respond to each one individually. In my mind, most of the time top posting actually is better because the reply stands out more than the original question - which usually is what you want. The majority of mailing lists that I am on seems to have switched to primarily top-posting, though, and most of the big email programs make it quite difficult to do bottom-posting. When you hit Reply, the cursor is usually positioned at the top of the page, not at the bottom. My personal rule: if there already is a longer thread, stick with whatever style it has. The one thing you don't want to happen is having to look for the next reply because somebody switched style in the middle. If there is no pattern to follow (such as in this case), and I only want to respond to a post as a whole rather than individual points, I use top posting. * technically speaking, there is a still-valid RFC that specifies bottom-posting, but in practical terms it has been obsoleted by history. Martyn wrote: PS what his top posting, once I find out I will stop it -- Kevin Keane Owner The NetTech Find the Uncommon: Expert Solutions for a Network You Never Have to Think About Office: 866-642-7116 http://www.4nettech.com This e-mail and attachments, if any, may contain confidential and/or proprietary information. Please be advised that the unauthorized use or disclosure of the information is strictly prohibited. The information herein is intended only for use by the intended recipient(s) named above. If you have received this transmission in error, please notify the sender immediately and permanently delete the e-mail and any copies, printouts or attachments thereof. -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] only_from = 127.0.0.1
On Apr 23, 2009, at 12:53 PM, Kevin Keane wrote: Top-posting means that you put what you have to say at the top of the reply the way I do it here. Bottom-posting means that you put your reply below the original message. Don't forget about the best method, inline reply. In the original Internet culture, bottom-posting was preferred, and some Actually, no. inline replying was and still is preferred for technical mailling lists. I'd hazard to say that's true the technical users on this list as well. The day you subscribe to a list via digest mode, you'll fully understand why. ;) In my mind, most of the time top posting actually is better because the reply stands out more than the original question - which usually is what you want. Not if you want to make multiple points without entirely restating what you're replying to. Try to make my responses sensible in a top or bottom posting context without doing that. The majority of mailing lists that I am on seems to have switched to primarily top-posting, fooey. heh though, and most of the big email programs make it quite difficult to do bottom-posting. When you hit Reply, the cursor is usually positioned at the top of the page, not at the bottom. Double fooey. It's laziness. Not configuring the client to do it or get as close as possible and not using the highlight-delete combo :P I used Outlook for years, arguably the initiator of the top-posting epidemic, and had no problems responding in text/plain and inline. My personal rule: if there already is a longer thread, stick with whatever style it has. That's great! If it's a top or bottom post, you're increasing the redundancy of what's stored/sent in everyone's mail client, in the archives and most terribly, in the digests. by the number of replies to that thread. Brilliant G. My personal rule is to use the style of the person who appears to be most able to answer whatever question I have ;) That's almost always inline as hackers see top/bottom posting as a waste of space/bandwidth/time. * technically speaking, there is a still-valid RFC that specifies bottom-posting, but in practical terms it has been obsoleted by history. That's arguable, but could approach the passion level of a discussion of religion. -- Marc -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
