Wrong Server-IP with multihomed server

[Onno van der Leun]

On do, 2018-12-20 at 09:16 -0500, Thomas Markwalder wrote:
> 
> I believe your issue stems from defining classes within subnets.
> Classes 
> are globally defined.  When packets arrive, they are classified
> before 
> anything else.  While our configuration parser does not (currently)
> emit 
> an error when you define classes within subnets, it does appear to
> cause 
> oddities in behavior.  More over, you are defining the same class 
> twice.  The server is only going to retain the last one of that name.
> 
> Try extracting your class definition out of the subnets and define
> it 
> once at the global level:

He he awesome, thanks Thomas!
My colleague just confirmed that this was indeed the cause/issue. Like
you said, at least a warning from the config parser would be nice ;o)
Especially because lots of examples we'd find showed the class def
within the subnet definition.

Problem solved. We kinda already figured it had to be something that
simple. Thanks again!

Cheers,
Onno.