OPNWAF - How can I configure a virtual server to listen on a specific IP?

[bimbar]

Quite some time ago, the nginx plugin had the same problem of only being able to bind to a specific port on all interfaces, the same seems to be true for OPNWAF.

Is that the case or am I just unable to find the option, and if true, is it possible to expand this option from "port" to something like "ip:port"?

[bimbar]

I just checked and the same is true for caddy - I find it quite strange that nobody seems to use multiple public IPs perhaps with a variety of services listening on 443 on different IPs.

[franco]

There service bind has been known to be problematic when referring to single IPs.. they cannot be validated and they either exist elsewhere and the service works (unless they disappear and the service breaks) or one has to start linking the virtual IPs to the services for integrity checking, but that won't work for primary interface static addresses at the moment or dynamically assigned ones at all.


Cheers,
Franco

[bimbar]

We had this discussion over nginx, which seems to have worked out just fine, if you remember.

[franco]

I wouldn't call the NGINX plugin a hallmark of maintainability.

I know that people sometimes run into the problem that HAProxy doesn't start on boot because the IP they use is not there yet.


Cheers,
Franco