[Bug 122954] [lagg] IPv6 EUI64 incorrectly chosen for lagg devices

2017-12-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=122954 Josh Paetzel changed: What|Removed |Added Status|In Progress |Closed CC|

[Bug 118727] [netgraph] [patch] [request] add new ng_pf module

2017-12-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=118727 Josh Paetzel changed: What|Removed |Added CC||jpaet...@freebsd.org St

[Bug 122989] [swi] [panic] 6.3 kernel panic in swi1: net

2017-12-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=122989 Josh Paetzel changed: What|Removed |Added Status|In Progress |Closed Resolution|---

run0 wifi device causes kernel panics in 11.1

2017-12-09 Thread Yuri
This started happening after I updated revision from Aug 1, 2017 to Dec 6, 2017. The crash stack begins at syscall_fast. Yuri ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any m

Re: [Bug 122954] [lagg] IPv6 EUI64 incorrectly chosen for lagg devices

2017-12-09 Thread Eugene Grosbein
10.12.2017 1:29, bugzilla-nore...@freebsd.org wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=122954 > > Josh Paetzel changed: > >What|Removed |Added > > Stat

Re: [Bug 122954] [lagg] IPv6 EUI64 incorrectly chosen for lagg devices

2017-12-09 Thread Josh Paetzel
On Sat, Dec 9, 2017, at 02:29 PM, Eugene Grosbein wrote: > 10.12.2017 1:29, bugzilla-nore...@freebsd.org wrote: > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=122954 > > > > Josh Paetzel changed: > > > >What|Removed |Added > > ---

Re: [Bug 122954] [lagg] IPv6 EUI64 incorrectly chosen for lagg devices

2017-12-09 Thread Eugene Grosbein
10.12.2017 4:03, Josh Paetzel wrote: > On Sat, Dec 9, 2017, at 02:29 PM, Eugene Grosbein wrote: >> 10.12.2017 1:29, bugzilla-nore...@freebsd.org wrote: >> >>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=122954 >>> >>> Josh Paetzel changed: >>> >>>What|Removed

[Bug 224218] Kernel panic in SCTP/IpV6 server mode

2017-12-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224218 Conrad Meyer changed: What|Removed |Added Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org

[Bug 224218] Kernel panic in SCTP/IpV6 server mode

2017-12-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224218 --- Comment #2 from Shreesh Holla --- Created attachment 188676 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=188676&action=edit Crash info file -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 224218] Kernel panic in SCTP/IpV6 server mode

2017-12-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224218 --- Comment #3 from Shreesh Holla --- The stacktrace from the vmcore is: Fatal double fault: eip = 0xc06dcf21 esp = 0xeeafbfd8 ebp = 0xeeafc1b8 cpuid = 1; apic id = 02 panic: double fault cpuid = 1 KDB: stack backtrace: #0 0xc0bc1b3e at kdb

[Bug 224218] Kernel panic in SCTP/IpV6 server mode

2017-12-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224218 Michael Tuexen changed: What|Removed |Added CC||tue...@freebsd.org --- Comment #4

[Bug 224218] Kernel panic in SCTP/IpV6 server mode

2017-12-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224218 --- Comment #5 from Shreesh Holla --- The issue seems to be if you use an actual IPV6 address i.e. not ::1. Well I could not connect from an external machine when listener was on ::1. So the listener should be listening on the local IPv6 ad