Re: ipsp_ids_gc panic after 7.1 upgrade

On Thu, Apr 28, 2022 at 12:52:41AM +0300, Vitaliy Makkoveev wrote: > On Thu, Apr 28, 2022 at 12:15:25AM +0300, Vitaliy Makkoveev wrote: > > > On 27 Apr 2022, at 23:24, Kasak wrote: > [ skip ] > > > I???m afraid your patch did not help, it crashed again after three hours > > > > Did it panic

Re: [External] : Using network interface in a pf rule does not work with ipv6.

Hi, On Fri, 29 Apr 2022, at 9:08 PM, Alexandr Nedvedicky wrote: > let there be a rule in pf: > pass in on em0 from any to em0:3 > > now how we are going to deal with situation when address :2 > disappear? shell we keep indexes assigned? shell we reindex? > how this should work

Re: [External] : Using network interface in a pf rule does not work with ipv6.

On 2022/04/29 22:08, Alexandr Nedvedicky wrote: > Hello Ian, > > > > > However, this does not work with IPv6, because vlan10 translates to the > > link-local address (fe80::) instead of the real address on the interface. > > > > This is a bug, IMO. I'm not sure why you'd want the link local

Re: [External] : Using network interface in a pf rule does not work with ipv6.

Hello Ian, > However, this does not work with IPv6, because vlan10 translates to the > link-local address (fe80::) instead of the real address on the interface. > > This is a bug, IMO. I'm not sure why you'd want the link local address in > there... and to my knowledge, there isn't a way of

OpenBSD replies from the 'wrong' interface in traceroutes

Hi, Am using OpenBSD as for routers and am getting quite a few traceroutes which have traversed them and show the wrong IP/rDNS. It seems that OpenBSD sends the reply from the best route, rather than the interface that the traffic came in on - like a real router would do. This manifests in

Using network interface in a pf rule does not work with ipv6.

Hi, It's great in PF to be able use an interface name in a PF rule, and that's internally substituted with the IP address(es) on that interface. This means you can have neat rules like: pass out quick on vlan10 inet from vlan10 to !vlan10:network nat-to lo1 This not only means you are not hard

Odd IPv6 ND behaviour after upgrading to OpenBSD 7.1

Hi, Not sure what the etiquette for this list is, so apologies if this is not appropriate as it's not a confirmed bug... I have a whole bunch of subnets which are static routed to a HSRP address, provided by a pair of Cisco routers, on a linknet VLAN. Actually, there is two VLANs, vlan209 and

Re: macppc panic: vref used where vget required

On Thu, Apr 28, 2022 at 08:47:53PM +0200, Martin Pieuchot wrote: > On 28/04/22(Thu) 16:54, Sebastien Marie wrote: > > On Thu, Apr 28, 2022 at 04:04:41PM +0200, Alexander Bluhm wrote: > > > On Wed, Apr 27, 2022 at 09:16:48AM +0200, Sebastien Marie wrote: > > > > Here a new diff (sorry for the

Re: ipsp_ids_gc panic after 7.1 upgrade

28.04.2022 00:52, Vitaliy Makkoveev пишет: On Thu, Apr 28, 2022 at 12:15:25AM +0300, Vitaliy Makkoveev wrote: On 27 Apr 2022, at 23:24, Kasak wrote: [ skip ] I’m afraid your patch did not help, it crashed again after three hours Did it panic within ipsp_ids_gc() again? I missed,

Re: Garbled screen when booting with UEFI

>If I remove the text mode setting code in efi_video_init() and boot... >- From the Boot Menu (F12): Machine reports that it's in mode 1 but it's >actually in mode 0. Display issues persist. Sorry for the typo here. I meant to say that it reports that it's in mode 0 but it's actually in mode 1.