Hi All,
After a lot of testing I found out that my problem is appearing when I use
NATTED links as my uplinks. When I use routed ip addresses without NAT my
route-to setup is working for openbsd 4.5 and 4.7. When using route-to over at
least 1 link with NAT (I've tested it with both an openbsd
Hello fellow openbsd fans,
While preparing a test environment for my upgrade to openbsd 4.7 I ran into a
slight problem. My current setup uses route-to rules to send out traffic back
out on the interface it received it on like this:
pass out on $ext_if2 route-to ($ext_if1 $ext_if1_router) from
On Tue, Jul 27 2010 at 04:10, Maikel Verheijen wrote:
Hello fellow openbsd fans,
Hello,
While preparing a test environment for my upgrade to openbsd 4.7 I ran into a
slight problem. My current setup uses route-to rules to send out traffic back
out on the interface it received it on like this:
Em 27-07-2010 05:04, Maikel Verheijen escreveu:
Hello fellow openbsd fans,
While preparing a test environment for my upgrade to openbsd 4.7 I ran into a
slight problem. My current setup uses route-to rules to send out traffic back
out on the interface it received it on like this:
pass out on
I think you need to specify the gateway. On a host I set up
that uses DSL (pppoe(4) so the gw is 0.0.0.1):
pass out on $ext_if1 from $ext_if2 to any route-to ($ext_if2 0.0.0.1)
pass out on $ext_if2 from $ext_if1 to any route-to ($ext_if1 0.0.0.1)
I don't know if your omission of 'to any' affects
5 matches
Mail list logo
