Hi Stuart, thanks for your hints and pushing me in the right direction....
Thomas 2017-06-21 2:49 GMT+02:00 Stuart Henderson <[email protected]>: > On 2017-06-20, miraculli . <[email protected]> wrote: > > For every aiohttp instance I created one vether(4) and assigned > 10.0.0.x/24 > > to it > > Don't put addresses from the same /24 onto a bunch of different > interfaces. Use one /24 and the others should be /32 aliases, all on a > single interface. > > > Right now the main problem is that relayd(8) dosen´t listen (on > 0.0.0.0:80), > > as httpd does for example. What I´m missing here? > > Your expectations don't match your current config. You would get that > behaviour with a "relay" but you use "redirect" so relayd isn't supposed > to bind to a port itself, instead it adds a PF rdr-to rule to the relayd > anchor to forward traffic to the relevant backend. > > - from relayd.conf(5) :- > > Redirections > Redirections are translated to pf(4) rdr-to rules for stateful > forwarding to a target host from a health-checked table on > layer 3. > > Relays > Relays allow application layer load balancing, TLS acceleration, > and general purpose TCP proxying on layer 7. > > > -- +49.179.1448024 Karl-Kunger-Straße 68 D - 12435 Berlin
