| To: | Nathan Scott <nathans@xxxxxxxxxx>, Mark Jerome Layba Bautista <MJBautista@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] tcp/udp ports used for pmlogger |
| From: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
| Date: | Thu, 8 Sep 2016 18:26:34 +1000 |
| Cc: | pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <1833072902.6196620.1473316082994.JavaMail.zimbra@xxxxxxxxxx> |
| References: | <B195C350AB599F489BFCA6492EB349AC38E490D8@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <1833072902.6196620.1473316082994.JavaMail.zimbra@xxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 |
On 08/09/16 16:28, Nathan Scott wrote:
> Yes, pmlogger talks to remote pmcd processes on port 44321 by
> default. This can be configured - see PCPIntro(1) man page discussion
> if needed esp. the PMCD_PORT and PMPROXY_PORT references, and HOST
> SPECIFICATION sections.
This is correct, but there is a bit more to the story ...
>From qa/README ...
Firewalls can get in the way. In addition to the standard pmcd port(s)
(TCP ports 44321, 44322 and 44323) one needs to open ports to allow
incoming connections and outgoing connections on a range of ports
for pmdatrace, pmlogger connections via pmlc, and some QA tests.
Opening the TCP range 4320 to 4350 (inclusive) should suffice.
So, you depending on usage patterns (particularly if you want to use pmlc to
control a remote pmlogger) you may need to drill a few more holes in the
firewall.
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] tcp/udp ports used for pmlogger, Bautista, Mark Jerome Layba |
|---|---|
| Next by Date: | Re: [pcp] PCP Updates: ipv6 Configuration, Dave Brolley |
| Previous by Thread: | Re: [pcp] tcp/udp ports used for pmlogger, Nathan Scott |
| Next by Thread: | Re: [pcp] tcp/udp ports used for pmlogger, Mark Goodwin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |