On Tue, Sep 15, 2020 at 12:42:27PM +0900, YASUOKA Masahiko wrote: > It's not clear for me why non-existing rdomain is accepted but > non-existing rtable is rejected. I suppose we can make pf(4) can > handle a packet for the non-existing routing table as if the routing > table is empty. Probably possible, but not without further tests or even changes to pf; I did not want to imply that dynamic `rtable' in pf.conf cannot be done.
- Re: diff: pfctl: error message for nonexisting rtable Klemens Nanni
- Re: diff: pfctl: error message for nonexisting rt... YASUOKA Masahiko
- Re: diff: pfctl: error message for nonexistin... Klemens Nanni
- Re: diff: pfctl: error message for nonexi... YASUOKA Masahiko
- Re: diff: pfctl: error message for no... Klemens Nanni
- Re: diff: pfctl: error message f... YASUOKA Masahiko
- Re: diff: pfctl: error messa... YASUOKA Masahiko
- Re: diff: pfctl: error message for nonexisting rtable Klemens Nanni
- Re: diff: pfctl: error message for nonexisting rt... Klemens Nanni
- Re: diff: pfctl: error message for nonexistin... YASUOKA Masahiko
- Re: diff: pfctl: error message for nonexi... Klemens Nanni
- Re: diff: pfctl: error message for nonexistin... Klemens Nanni
- Re: diff: pfctl: error message for nonexi... Klemens Nanni
- Re: diff: pfctl: error message for no... Alexandr Nedvedicky
