Re: [pf] NAT64 rule for *outgoing* packets

Benno, all, The gateway is running unbound with dns64 module enabled. The gateway does use the resolver for it's own resolving of names. I found a better solution by running two instances of unbound on the gateway. One instance for the client networks with dns64 module enabled, and one instance fo

OpenBSD on SBC?

Hi, is there an OpenBSD-compatible SBC (Singe Board Computer) that comes close to raspberryPi size-wise? I saw some x86-based SBCs on kickstarter a while ago, but lost track of the projects and their OpenBSD compatibility. I know so far: - soekris - pcengines More? Bonus points for working on-b

Re: [pf] NAT64 rule for *outgoing* packets

kernel for this issue? Cheers, Dan > On 7 Jun 2016, at 14:48, Dan Lüdtke wrote: > > Hi, > > my setup: [host]--[router]--[internet] > > [Host] can ping legacy internet hosts via NAT64. Works fine. Corresponding > line in pf.conf reads: > pass in quick on $if_lan inet

[pf] NAT64 rule for *outgoing* packets

Hi, my setup: [host]--[router]--[internet] [Host] can ping legacy internet hosts via NAT64. Works fine. Corresponding line in pf.conf reads: pass in quick on $if_lan inet6 from $if_lan:network to 64:ff9b::/96 af-to inet from ($if_wan) However, [router] can not ping legacy internet hosts via NAT