On 2023-10-16 07:59:06, Peter Hessler wrote:
On 2023 Oct 16 (Mon) at 07:53:37 +0200 (+0200), Harald Dunkel wrote:
:/etc/hostname.vlan111:
:vnetid 111
:parent re0
You need to add "up" here.
The "up" in hostname.vlan111 makes no difference for the
configuration of the pfsync0 interface, I
On 2023 Oct 16 (Mon) at 07:53:37 +0200 (+0200), Harald Dunkel wrote:
:/etc/hostname.vlan111:
:vnetid 111
:parent re0
You need to add "up" here.
:
:/etc/hostname.pfsync0:
:syncdev vlan111 up
:
:vlan111: flags=8002 mtu 1500
^^^
no UP flag, so the parent interface is not
Hi folks,
sorry, I had hoped somebody knew the answer and that the man page
could be fixed.
I have just limited test equipment for verification, so I have setup
a vlan interface for pfsync and tried some combinations. Result:
Apparently there is no difference between
up
syncdev
On 2023-10-15, Harald Dunkel wrote:
> Hi folks,
>
> I learned that pfsync has been rewritten for 7.4 and that
>
> up
> syncdev em7
>
> doesn't work anymore. What about
>
> up syncdev em7
>
> (one line), as suggested in the current pfsync(4)?
Suggest you either use the syntax
Harald Dunkel(ha...@afaics.de) on 2023.10.15 06:51:08 +0200:
> Hi folks,
>
> I learned that pfsync has been rewritten for 7.4 and that
>
> up
> syncdev em7
>
> doesn't work anymore. What about
>
> up syncdev em7
>
> (one line), as suggested in the current pfsync(4)?
Did you
On 15.10.2023. 6:51, Harald Dunkel wrote:
> Hi folks,
>
> I learned that pfsync has been rewritten for 7.4 and that
>
> up
> syncdev em7
>
> doesn't work anymore. What about
>
> up syncdev em7
>
> (one line), as suggested in the current pfsync(4)?
>
>
> Regards
> Harri
>
could
Hi folks,
I learned that pfsync has been rewritten for 7.4 and that
up
syncdev em7
doesn't work anymore. What about
up syncdev em7
(one line), as suggested in the current pfsync(4)?
Regards
Harri
7 matches
Mail list logo