On Tue, Jul 21, 2020 at 10:02:55AM +1000, David Gwynne wrote:
> kn@ pointed me at this, and we came up with the following. firstly, we
> narrowed the problem down to pcap not actually looking at the header to
> decide if a packet was ipv4 or ipv6:
dlg did the hard work, really - without him I'd
On Mon, Jul 20, 2020 at 05:45:52PM +0200, Klemens Nanni wrote:
> On Sun, Jul 19, 2020 at 02:24:36PM +0200, Matthieu Herrb wrote:
> > Trying to look at IPv6 traffic on my wireguard VPN with
> >
> > tcpdump -n -i wg0 ip6
> >
> > also shows all IPv4 traffic. Other interfacees seem to filter the v6
Hi,
I am Having an DRM: Atomic Update Failure on Thinkpad x230 - OpenBSD 6.7 and
someone on IRC suggested to send my dmesg to @bugs, I've also got complete
systemfreeze today, which I will investigate further, if I have more time on my
hands. I don't know if it's related, so I am mentioning
On Mon, Jul 13, 2020 at 03:47:13PM +0100, Mark Willson wrote:
> Folks,
>
> The segmentation fault occurs when the string to replace is just the
> "^" anchor (beginning-of-line) and the point is on an empty line.
> Issue occurs on a -current system dated July 11th. (dmesg below).
>
> The
On Sun, Jul 19, 2020 at 02:24:36PM +0200, Matthieu Herrb wrote:
> Trying to look at IPv6 traffic on my wireguard VPN with
>
> tcpdump -n -i wg0 ip6
>
> also shows all IPv4 traffic. Other interfacees seem to filter the v6
> protocol correctly.
This happens for all interfaces without link-layer,
On 20 Jul 2020, at 15:15, Stuart Henderson wrote:
Moving to bugs@:
In gmane.os.openbsd.misc, Anton Kasmov wrote:
I am using OpenBSD 6.7
iked does not respect mixing ports in the source and the destination
of
traffic selectors.
Such policy in iked.conf
ikev2 "epsilon" active \
Moving to bugs@:
In gmane.os.openbsd.misc, Anton Kasmov wrote:
> I am using OpenBSD 6.7
> iked does not respect mixing ports in the source and the destination of
> traffic selectors.
>
> Such policy in iked.conf
> ikev2 "epsilon" active \
> proto tcp \
> from ::::30 to
On Mon, Jul 20, 2020 at 09:08:15AM +0200, Peter J. Philipp wrote:
> Hi,
>
> I have a screenshot of a kernel panic when I typed cu in a snapshot that
> I just downloaded.
>
> The panic string is:
>
> panic: kernel diagnositc assertion "p->p_wchan == NULL" failed: file
>
Hi,
I have a screenshot of a kernel panic when I typed cu in a snapshot that
I just downloaded.
The panic string is:
panic: kernel diagnositc assertion "p->p_wchan == NULL" failed: file
"/usr/src/sys/kern/kern_sched.c", line 353
Unfortunately I don't have very much time today so that's all
