cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Hair <j...@greenqloud.com>
Subject Re: Not able to setup source-nat for a regular router yet
Date Wed, 15 Mar 2017 16:10:28 GMT
It's coming from the config scripts on the routers, yes. This is version
4.9.2.0 (it's a fork, but should be similar enough to vanilla). I'm not
necessarily noticing problems with it. Connectivity from public IPs on
Isolated networks seem to be working. I'm just wondering what this message
means, and if it can cause problems.

Jeff

On Wed, Mar 15, 2017 at 4:07 PM, Gabriel Beims Bräscher <
gabriel@autonomiccs.com.br> wrote:

> Hi Jeff,
>
> Could you please provide more details (e.g. CloudStack version, CloudStack
> management log)?
> Seems that the log came from [1]. I will check on it.
>
> [1] https://github.com/apache/cloudstack/blob/master/systemvm/
> patches/debian/config/opt/cloud/bin/cs/CsAddress.py
>
> Cheers,
> Gabriel.
>
>
> Em 15/03/2017 07:21, Jeff Hair escreveu:
>
>> Hi,
>>
>> I'm seeing this message in the logs when detaching IPs with
>> disableStaticNat. This is on a network without redundant routers. What
>> exactly dose "Not able to setup source-nat for a regular router yet" mean?
>> Does this cause functionality problems for non-redundant routers?
>>
>> Jeff
>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message