Re: [munin-users] option to specify port per client

[Andrey G. <gor...@gm...>]

Both, the set of nodes, and server talk through managed name servers,
so fqdn resolution does not seem to be a concern; the problem is (was)
with knocking 4949

I definitely did search, wonder how could I miss.. thanks!

On 6/28/17, DoubleHP <dou...@do...> wrote:
> On 28/06/17 09:02, Andrey Gorodnov wrote:
>> I've several nodes behind vpn for which i'm obliged to set up port
>> forwarding, unfurtunately munin server cannot reach them via default
>> 4949.
>> i tried to alter settings like below
>>
>> [wooho.example.com <http://wooho.example.com>]
>>     address wooho.example.com <http://wooho.example.com>*:10117
>>
>> *
>> but this doesnt work, and what I get in logs is this...
>> [INFO] starting work in 4155 for
>> wooho.example.com/wooho.example.com:10117:4949
>> <http://wooho.example.com/wooho.example.com:10117:4949>.
>>
>> is there a way to change default 4949 to a port of my liking?
>
> http://lmgtfy.com/?q=munin+port
> first answer.
>
> 1: using a server by name when having troubles with port forwarding is the
> best way to potentially have IPv4/IPv6 resolution problems.
> "wooho.example.com" is really the proof you are willing to trigger issues.
>
> 2: feature is very well documented.
>
>
> --
>  >o_/ DEMAINE Benoīt-Pierre (aka DoubleHP) http://benoit.demaine.info/
> If computing were an exact science, IT engineers would'nt have work \_o<
>
> "So all that's left, Is the proof that love's not only blind but deaf."
> (FAKE TALES OF SAN FRANCISCO, Arctic Monkeys)
>