[Bug 221530] if_ixl: add a way to disable/enable lldp handling by the NIC

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221530 Krzysztof Galazka changed: What|Removed |Added CC||krzysztof.gala...@intel.com --

[Bug 221530] if_ixl: add a way to disable/enable lldp handling by the NIC

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221530 --- Comment #5 from Nikita Kozlov --- Thanks, I will try that when I will have some time ! -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org m

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

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224218 --- Comment #19 from Michael Tuexen --- OK, I setup a Release 11.1 i386 VM and a HEAD i386 VM and installed nmap. Using ncat --sctp -l IPv6_address on these VMs I can NOT reproduce the issue. I used ::1 and a client on the same VM, used a g

[Bug 224247] RFC 6980 requires to drop fragmented IPv6 neighbour discovery

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224247 Conrad Meyer changed: What|Removed |Added CC||c...@freebsd.org Assignee

[Bug 224247] [patch] RFC 6980 requires to drop fragmented IPv6 neighbour discovery

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224247 Conrad Meyer changed: What|Removed |Added Summary|RFC 6980 requires to drop |[patch] RFC 6980 requires

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

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224218 --- Comment #20 from Shreesh Holla --- (In reply to Michael Tuexen from comment #19) That's strange. That's exactly what I did for the panic. So maybe there is something else on my systems. I am using vm's too of vmware desktop. I will try

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

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224218 --- Comment #21 from Michael Tuexen --- I'm using VMWare Fusion. The VM uses a single processor core and 256MB of RAM. I installed FreeBSD from FreeBSD-11.1-RELEASE-i386-dvd1.iso. Let me know what you find... -- You are receiving this mai

[Bug 224247] [patch] RFC 6980 requires to drop fragmented IPv6 neighbour discovery

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224247 Kristof Provost changed: What|Removed |Added CC||k...@freebsd.org --- Comment #2

Changes to route(8) or routing between r325235 and r326782?

Hello list :) "Something" which changes how routing works has landed in 11-STABLE between r325235 and r326782. Until now I have had a script which deletes routing table entries which point to lo0, in order to keep traffic from "shortcutting" over lo0, to make it possible to use pf to filter traff

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

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224218 --- Comment #22 from Shreesh Holla --- (In reply to Michael Tuexen from comment #21) Here is what I may have which just be causing it. I backed out my change from loader.conf and it went into panic immediately when I made an sctp connection

Re: Changes to route(8) or routing between r325235 and r326782?

Thomas Steen Rasmussen wrote: > $ sudo route delete 185.96.180.10 > route: writing to routing socket: Address already in use > delete host 185.96.180.10 fib 0: gateway uses the same route I think this is the cause: https://reviews.freebsd.org/D12747 https://bugs.freebsd.org/bugzilla/show_bug.c

Re: Changes to route(8) or routing between r325235 and r326782?

On 12.12.2017 09:31, Thomas Steen Rasmussen wrote: > After upgrading to r326782 I get the following error when trying to > delete the lo0 entry (I have an rc.d script to do it): > > $ sudo route delete 185.96.180.10 > route: writing to routing socket: Address already in use > delete host 185.96.