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
Stefan's efforts on this are appreciated.
Our Fitlet3 units may have slight differences, but in case it is
helpful, I've included the following:
Intel Elkhart Lake Ethernet on Compulab Fitlet3 with PCI Product ID:
4ba1 and 4bb1 not recognized.
Regards,
Ted
Output of pcidump; pcidump -vv
On Sun, Oct 15, 2023 at 04:56:17PM -, Stuart Henderson wrote:
>On 2023-10-15, rea...@catastrophe.net wrote:
>> What is a better way to configure iked on site-obsd so that it does not
>> encapsulate local traffic on the 10.89.2.0/24 network? Obviously my
>> understanding is incorrect, so any
On 15.10.2023. 18:56, Stuart Henderson wrote:
> On 2023-10-15, rea...@catastrophe.net wrote:
>> What is a better way to configure iked on site-obsd so that it does not
>> encapsulate local traffic on the 10.89.2.0/24 network? Obviously my
>> understanding is incorrect, so any help is appreciated.
On Oct 15 11:48, Nick Holland wrote:
> On 10/12/23 13:54, Karel Lucas wrote:
> > Is it already known when openBSD 7.4 will be released? I would like to
> > know that, because of a project I am working on.
>
> The answer to your question is already out there, but I offer this
> procedural tip:
>
On 2023-10-15, rea...@catastrophe.net wrote:
> What is a better way to configure iked on site-obsd so that it does not
> encapsulate local traffic on the 10.89.2.0/24 network? Obviously my
> understanding is incorrect, so any help is appreciated.
You should be able to add a bypass flow in
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
On 2023-10-14, Manuel Kuklinski wrote:
> Thank you again - can you possibly direct me in the correct way to "dump
> the environment"? I guess you don't mean `env`?
Yes, env - e.g. "(date; env) >> /tmp/env.log
On Sun, Oct 15, 2023 at 09:15:07AM -0500, rea...@catastrophe.net wrote:
[..]
Some numbers got transposed in this message. All the devices are truly on
10.99.2.0/24 (even when 10.89.2 was in the original email)
>site-obsd# ping -qc2 r1
>PING r1 (10.89.2.1): 56 data bytes
On 10/12/23 13:54, Karel Lucas wrote:
Is it already known when openBSD 7.4 will be released? I would like to
know that, because of a project I am working on.
The answer to your question is already out there, but I offer this
procedural tip:
IF you wish to follow releases, start your project
Greetings -
I have a hub that is terminating IPsec connections from various sites. One
site is running 7.3 and has downlinks to other routers on vlan2. When I try
and ping from the site-obsd (the OpenBSD machine at site) to the router,
there are no issues and that device is getting DHCP addresses
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
14 matches
Mail list logo
