On 04/06/2013, at 11:22 AM, Claudio Jeker cje...@diehard.n-r-g.com wrote:
On Mon, Jun 03, 2013 at 11:49:58PM +0100, Stuart Henderson wrote:
On a router running PF and isakmpd, I have a rule like this:
match out on pppoe0 inet all received-on vlan5 nat-to $someip
I was surprised to find
On 4 June 2013 02:48, Stuart Henderson st...@openbsd.org wrote:
On 2013/06/04 02:01, Mike Belopuhov wrote:
On 4 June 2013 00:49, Stuart Henderson s...@spacehopper.org wrote:
On a router running PF and isakmpd, I have a rule like this:
match out on pppoe0 inet all received-on vlan5 nat-to
On a router running PF and isakmpd, I have a rule like this:
match out on pppoe0 inet all received-on vlan5 nat-to $someip
I was surprised to find this being applied to packets received on vlan5
and caught by an ipsec flow; the resulting *encapsulated* (proto ESP) packets
(as in, generated on
Stuart Henderson [s...@spacehopper.org] wrote:
On a router running PF and isakmpd, I have a rule like this:
match out on pppoe0 inet all received-on vlan5 nat-to $someip
I was surprised to find this being applied to packets received on vlan5
and caught by an ipsec flow; the resulting
On 2013/06/04 02:01, Mike Belopuhov wrote:
On 4 June 2013 00:49, Stuart Henderson s...@spacehopper.org wrote:
On a router running PF and isakmpd, I have a rule like this:
match out on pppoe0 inet all received-on vlan5 nat-to $someip
I was surprised to find this being applied to packets
On Mon, Jun 03, 2013 at 11:49:58PM +0100, Stuart Henderson wrote:
On a router running PF and isakmpd, I have a rule like this:
match out on pppoe0 inet all received-on vlan5 nat-to $someip
I was surprised to find this being applied to packets received on vlan5
and caught by an ipsec flow;
