> On Thursday 11 August 2005 18:09, Hexren wrote:
>> We tried to run NAT on GRE sessions. That failed with more than 1 host
>> in the NATed network using GRE. ( GRE NAT is after all not really
>> supported as far as I can see,so no big surprise here)
>> The unfortunate thing that I would call a bug
On Thursday 11 August 2005 18:09, Hexren wrote:
> We tried to run NAT on GRE sessions. That failed with more than 1 host
> in the NATed network using GRE. ( GRE NAT is after all not really
> supported as far as I can see,so no big surprise here)
> The unfortunate thing that I would call a bug is th
On Thursday 11 August 2005 17:35, Sergey Lapin wrote:
> >
> > * Bug#3 (critical) *
> >
> >
> > Because route-to for "out" rules did not work well, we decided to
We tried to run NAT on GRE sessions. That failed with more than 1 host
in the NATed network using GRE. ( GRE NAT is after all not really
supported as far as I can see,so no big surprise here)
The unfortunate thing that I would call a bug is that the gateway did
not fail gracefuly (dropping the sess
> Here's more proper description of the problem:
>
> Hi.
>
> While trying to configure pf on our freebsd 5.4 router we have
> encountered three bugs, one of which is minor, second is more serious.
> And the worst of all, because of the second bug we have to use
> workaround and that workaround tr
