[Bug 261711] net/wireguard-kmod: Cannot send data over VXLAN / vtnet

2022-10-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711 --- Comment #19 from Kristof Provost --- (In reply to Graham Perrin from comment #18) You'd have to ask the reporter. I've never reproduced this bug. I committed an obvious improvement to vxlan but do not have the setup with (or interest in

Problem reports for n...@freebsd.org that need special attention

2022-10-30 Thread bugzilla-noreply
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

[Bug 261711] net/wireguard-kmod: Cannot send data over VXLAN / vtnet

2022-10-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711 Graham Perrin changed: What|Removed |Added Assignee|k...@freebsd.org |ports-b...@freebsd.org

[Bug 261711] net/wireguard-kmod: Cannot send data over VXLAN / vtnet

2022-10-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711 Kubilay Kocak changed: What|Removed |Added Severity|Affects Only Me |Affects Some People St

[Bug 261711] net/wireguard-kmod: Cannot send data over VXLAN / vtnet

2022-10-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711 --- Comment #22 from Zhenlei Huang --- @G(In reply to Graham Perrin from comment #21) > ^Triage: To progress, this issue needs confirmation of resolution (or explicit > confirmation it doesn't) for the issue as originally reported. > @Rep

[Bug 252596] ping to 255.255.255.255 does not set broadcast MAC

2022-10-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252596 Yuichiro NAITO changed: What|Removed |Added CC||naito.yuich...@gmail.com --- Comm

[Bug 252165] usb network and mii bus media status race condition

2022-10-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252165 m...@netfence.it changed: What|Removed |Added CC||m...@netfence.it --- Comment #27

[Bug 261711] net/wireguard-kmod: Cannot send data over VXLAN / vtnet

2022-10-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711 --- Comment #23 from Alfa --- (In reply to Zhenlei Huang from comment #22) I tried to apply patch to stable/12.2 and it gives me an error. FreeBSD test 12.2-STABLE FreeBSD 12.2-STABLE r369958 GENERIC amd64 root@test:/usr/src/sys/net #

[Bug 261711] net/wireguard-kmod: Cannot send data over VXLAN / vtnet

2022-10-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711 --- Comment #24 from Zhenlei Huang --- Created attachment 237750 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=237750&action=edit stable/12 patch (In reply to Alfa from comment #23) There're some changes of if_vxlan not MFCed t

[Bug 265857] qlnxe: no IPV6 pings between nodes on the same switch until an IPv4 address is set

2022-10-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265857 --- Comment #7 from Zhenlei Huang --- (In reply to Zhenlei Huang from comment #6) Hi benoitc, Any good luck ? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 252165] usb network and mii bus media status race condition

2022-10-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252165 --- Comment #28 from m...@netfence.it --- (In reply to ml from comment #27) P.S. I tried the patch from comment #3, but it doesn't help in my case. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 263721] bge(0): BCM5720 fails to work on Dell PowerEdge R6515

2022-11-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263721 Alexander Shikov changed: What|Removed |Added CC||a.shi...@itcons.net.ua --- Comm

[Bug 241162] Panic in closefp() triggered by nginx (uwsgi with sendfile(2) enabled)

2022-11-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241162 Dmitry Marakasov changed: What|Removed |Added Resolution|--- |Overcome By Events

[Bug 166724] if_re(4): watchdog timeout

2022-11-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724 George Mitchell changed: What|Removed |Added CC||geo...@m5p.com --- Comment #104

[Bug 166724] if_re(4): watchdog timeout

2022-11-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724 --- Comment #105 from László Károlyi --- (In reply to George Mitchell from comment #104) FYI, I use the driver from ports since years, without any errors. It's only the kernel based driver that has this weird phenomenon. Keep using the por

[Bug 166724] if_re(4): watchdog timeout

2022-11-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724 --- Comment #106 from ykla --- (In reply to George Mitchell from comment #104) Which port? Thanks. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.

[Bug 166724] if_re(4): watchdog timeout

2022-11-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724 --- Comment #107 from ykla --- I seem to be replying to the wrong bug? My USB NIC is not a realtek but an ASIX AX88179A, but I have this problem too. -- You are receiving this mail because: You are on the CC list for the bug. You are the

[Bug 252165] usb network and mii bus media status race condition

2022-11-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252165 --- Comment #29 from Ali Abdallah --- (In reply to ml from comment #28) your device doesn't use mii bus rgephy code, but something else. See which part your device uses from sys/dev/mii/ and adapt the workaround accordingly. -- You are r

[Bug 252165] usb network and mii bus media status race condition

2022-11-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252165 --- Comment #30 from Ali Abdallah --- (In reply to Hans Petter Selasky from comment #26) > Maybe all MII bus code should be executed for the same thread? Not sure what do you mean. The issue is that the ioctl for media status (which invok

[Bug 261711] net/wireguard-kmod: Cannot send data over VXLAN / vtnet

2022-11-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711 --- Comment #25 from Alfa --- (In reply to Zhenlei Huang from comment #24) I successfully patched and builded new kernel but We have a problem with wireguard-kmod in stable/12 . >> root@test:~ # wg-quick up wg0 [#] ifconfig wg create na

[Bug 166724] if_re(4): watchdog timeout

2022-11-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724 --- Comment #108 from George Mitchell --- The port to install is net/realtek-re-kmod, cited in comment #92 and a few others following. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for th

[Bug 261711] net/wireguard-kmod: Cannot send data over VXLAN / vtnet

2022-11-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711 --- Comment #26 from Zhenlei Huang --- (In reply to Alfa from comment #25) > root@test:~ # kldload if_wg > kldload: an error occurred while loading module if_wg. Please check dmesg(8) > for more details. > KLD if_wg.ko: depends on kernel

[Bug 261711] net/wireguard-kmod: Cannot send data over VXLAN / vtnet

2022-11-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711 --- Comment #27 from Zhenlei Huang --- (In reply to Alfa from comment #25) And also please check the if_wg.ko module is not installed from 13.x pkg site. You can verify by `pkg info wireguard-kmod`. Beware the `Architecture` and `FreeBSD_ve

[Bug 261711] net/wireguard-kmod: Cannot send data over VXLAN / vtnet

2022-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711 --- Comment #28 from Alfa --- (In reply to Zhenlei Huang from comment #26) Ok you are right . I cloned stable/12 from git just now and patched vxlan so now i have: FreeBSD test 12.4-STABLE FreeBSD 12.4-STABLE #0 stable/12-n235817-fb7823f

[Bug 261711] net/wireguard-kmod: Cannot send data over VXLAN / vtnet

2022-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711 --- Comment #29 from Zhenlei Huang --- (In reply to Alfa from comment #28) That's good news ! -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 261711] net/wireguard-kmod: Cannot send data over VXLAN / vtnet

2022-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711 --- Comment #30 from Zhenlei Huang --- (In reply to Zhenlei Huang from comment #29) > That's good news ! @Kristof Will this catch up the release window ? 12.4 goes to RC1 recently. It would be bad news if not. -- You are receiving this m

[Bug 261711] net/wireguard-kmod: Cannot send data over VXLAN / vtnet

2022-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711 --- Comment #31 from Kristof Provost --- (In reply to Zhenlei Huang from comment #30) We're pretty late in the cycle for more patches, but it's sufficiently small and self-contained that we might be able to persuade re@ to take it. We do n

[Bug 261711] net/wireguard-kmod: Cannot send data over VXLAN / vtnet

2022-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711 --- Comment #32 from Zhenlei Huang --- (In reply to Kristof Provost from comment #31) > We're pretty late in the cycle for more patches, but it's sufficiently small > and > self-contained that we might be able to persuade re@ to take it.

[Bug 261711] net/wireguard-kmod: Cannot send data over VXLAN / vtnet

2022-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711 --- Comment #33 from Kristof Provost --- (In reply to Zhenlei Huang from comment #32) Remember to 'git cherry-pick -x' so there's a `(cherry picked from commit 8707cb19e68128c181477d87f960182c14e15f12)` line, and you'll have to git commit -

[Bug 261711] net/wireguard-kmod: Cannot send data over VXLAN / vtnet

2022-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711 --- Comment #34 from commit-h...@freebsd.org --- A commit in branch stable/13 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=0156c3f1f7608bb1ce547bed6b60cb084db3e7eb commit 0156c3f1f7608bb1ce547bed6b60cb084db3e7eb Author

[Bug 261711] net/wireguard-kmod: Cannot send data over VXLAN / vtnet

2022-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711 --- Comment #35 from commit-h...@freebsd.org --- A commit in branch stable/12 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=639aebb2aa0b72c569f8779e13351d37f7bb17c6 commit 639aebb2aa0b72c569f8779e13351d37f7bb17c6 Author

[Bug 261711] net/wireguard-kmod: Cannot send data over VXLAN / vtnet

2022-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711 --- Comment #36 from commit-h...@freebsd.org --- A commit in branch releng/12.4 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=a9c3d5de9ac8ae8090881f20c894d3577d97e92a commit a9c3d5de9ac8ae8090881f20c894d3577d97e92a Auth

[Bug 263046] drivers for BCM57504 NetXtreme-E quad-port NICs ?

2022-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263046 Warner Losh changed: What|Removed |Added CC||i...@freebsd.org --- Comment #10 fro

[Bug 255264] Unable to add default route for fib

2022-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255264 d...@sunsaturn.com changed: What|Removed |Added CC||d...@sunsaturn.com --- Comment

[Bug 252165] usb network and mii bus media status race condition

2022-11-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252165 --- Comment #31 from m...@netfence.it --- (In reply to Ali Abdallah from comment #29) Doh! Should have been obvious! (At least to someone more expert than me :) Anyway, I made the same changes to ukphy and now LAN seems to work perfectly: I

Problem reports for n...@freebsd.org that need special attention

2022-11-06 Thread bugzilla-noreply
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

[Bug 261711] net/wireguard-kmod: Cannot send data over VXLAN / vtnet

2022-11-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711 Kristof Provost changed: What|Removed |Added Resolution|--- |FIXED Status|Open

[Bug 264428] tcp: Crash in sbsndptr: panic: "%s: sockbuf %p and mbuf %p clashing" .. in sbsndptr (...) at /root/open_source/uinet/sys/kern/uipc_sockbuf.c:1025

2022-11-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264428 Gleb Smirnoff changed: What|Removed |Added Status|Open|Closed Resolution|---

[Bug 241191] route flush panic with RADIX_MPATH

2022-11-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241191 --- Comment #12 from Gleb Smirnoff --- (In reply to Andrey Linkevich from comment #6) Do you have any update? Does the bug reproduce in FreeBSD 13 or FreeBSD 14? -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 266973] [e1000] incorrect behavior when media and mediaopt are set to 100BaseTX full-duplex

2022-11-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266973 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|n...@freebsd.org -- You are receiv

[Bug 266973] [e1000] incorrect behavior when media and mediaopt are set to 100BaseTX full-duplex

2022-11-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266973 Franco Fichtner changed: What|Removed |Added CC||fra...@opnsense.org --- Comment

[Bug 223959] [pf] page fault in pf_purge_expired_states+0xf5 -> pf_state_expires+0x75 on 11.1-STABLE r326255

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223959 Kubilay Kocak changed: What|Removed |Added Keywords||crash -- You are receiving this m

[Bug 252485] [re] [panic] Panic in if_re.c (Realtek RTL8111/8168/8411)

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252485 Kubilay Kocak changed: What|Removed |Added Keywords||crash -- You are receiving this m

[Bug 260393] [tcp] Page Fault tcp_output/tcp_input

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393 --- Comment #103 from commit-h...@freebsd.org --- A commit in branch stable/13 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=c1f9a81e7bfe354dfa4f191d5180426f76bc514b commit c1f9a81e7bfe354dfa4f191d5180426f76bc514b Autho

[Bug 173478] [netinet] [patch] icmp forward bandwithlimit

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=173478 Graham Perrin changed: What|Removed |Added Keywords||patch --- Comment #5 from Graham P

[Bug 183407] [rc.d] [patch] Routing restart returns non-zero exitcode in case of no extra routing parameter or missing atm/ipx

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183407 Graham Perrin changed: What|Removed |Added Keywords||patch --- Comment #9 from Graham P

[Bug 235699] Kernel panics when setting IP address if net.link.ether.inet.garp_rexmit_count=2

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235699 Kubilay Kocak changed: What|Removed |Added Keywords||crash -- You are receiving this m

[Bug 191786] [bce] [patch] bce link state changes to same state are ignored by lagg

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191786 Graham Perrin changed: What|Removed |Added Keywords||patch --- Comment #4 from Graham P

[Bug 124021] [ip6] [panic] page fault in nd6_output()

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=124021 Graham Perrin changed: What|Removed |Added Keywords||crash --- Comment #5 from Graham P

[Bug 236853] panic: page fault on rtsock.c

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236853 Kubilay Kocak changed: What|Removed |Added Keywords||crash -- You are receiving this m

[Bug 229918] panic: Assertion ifsd_m[next] == NULL failed at /usr0/freebsd/base/head/sys/net/iflib.c:3151

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229918 Kubilay Kocak changed: What|Removed |Added Keywords||crash -- You are receiving this m

[Bug 222107] ifconfig down / up panics the kernel (non-sleepable iflib ctx lock held)

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222107 Kubilay Kocak changed: What|Removed |Added Keywords||crash -- You are receiving this m

[Bug 117733] [patch] [request] allow to tee(1) to sockets, descriptors

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=117733 Graham Perrin changed: What|Removed |Added Keywords||patch --- Comment #5 from Graham P

[Bug 254303] Fatal trap 12: page fault while in kernel mode ((frr 7.5_1 + Freebsd 13 Beta3) zebra crashes server when routes are populated)

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254303 Kubilay Kocak changed: What|Removed |Added Keywords||crash -- You are receiving this m

[Bug 238789] panic: mutex so_rcv not owned at /usr/src/sys/kern/uipc_socket.c:2359

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238789 Kubilay Kocak changed: What|Removed |Added Keywords||crash -- You are receiving this m

[Bug 255882] vxlan(4): kernel panic when unloading module if vxlan interface in VNET jails not shutdown before jail shutdown

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255882 Kubilay Kocak changed: What|Removed |Added Keywords||crash -- You are receiving this m

[Bug 227963] panic on shutdown - if_delmulti_ifma : Fatal trap 9: general protection fault while in kernel mode

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227963 Kubilay Kocak changed: What|Removed |Added Keywords||crash -- You are receiving this m

[Bug 231023] ip6_savecontrol_v4 panic

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231023 Kubilay Kocak changed: What|Removed |Added Keywords||crash -- You are receiving this m

[Bug 235649] panic: general protection fault in vlan_ioctl+0xfc

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235649 Kubilay Kocak changed: What|Removed |Added Keywords||crash -- You are receiving this m

[Bug 251154] mlx4en sometimes panics on ACPI S3 suspend/resume

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251154 Kubilay Kocak changed: What|Removed |Added Keywords||crash -- You are receiving this m

[Bug 266486] panic in iflib: Assertion CPU_COUNT(&ctx->ifc_cpus) > 0 failed at /usr/src/sys/net/iflib.c:5150

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266486 Kubilay Kocak changed: What|Removed |Added Keywords||crash -- You are receiving this m

[Bug 151937] [patch] netstat(1) utility lack support of displaying rtt related counters of tcp sockets

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=151937 Graham Perrin changed: What|Removed |Added Keywords||patch --- Comment #4 from Graham P

[Bug 252626] ixl: panic on attach of X722 on-motherboard interfaces

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252626 Kubilay Kocak changed: What|Removed |Added Keywords||crash -- You are receiving this m

[Bug 95277] [netinet] [patch] IP Encapsulation mask_match() returns wrong results

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=95277 Graham Perrin changed: What|Removed |Added Keywords||patch --- Comment #10 from Graham P

[Bug 151996] [patch] new tcpdrop(8) option to select interactively connections to drop

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=151996 Graham Perrin changed: What|Removed |Added Keywords||patch --- Comment #3 from Graham P

[Bug 108197] [panic] [gif] [ip6] if_delmulti reference counting panic

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=108197 Graham Perrin changed: What|Removed |Added Keywords||crash --- Comment #18 from Graham

[Bug 246819] Kernel panic with ifconfig destroy

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246819 Kubilay Kocak changed: What|Removed |Added Keywords||crash -- You are receiving this m

[Bug 185967] [lagg] [patch] Link Aggregation LAGG: LACP not working in 10.0

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185967 Graham Perrin changed: What|Removed |Added Keywords||patch --- Comment #20 from Graham

[Bug 254725] [tcp] 13.0-RC4 crash tcp_lro

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254725 Kubilay Kocak changed: What|Removed |Added Keywords||crash -- You are receiving this m

[Bug 246706] [netgraph] kernel panic due to corrupted memory

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246706 Kubilay Kocak changed: What|Removed |Added Keywords||crash -- You are receiving this m

[Bug 38554] [patch] changing interface ipaddress doesn't seem to work

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=38554 Graham Perrin changed: What|Removed |Added Keywords||patch --- Comment #12 from Graham P

[Bug 133969] [dummynet] [panic] page fault in ready_event_wfq, sys/netinet/ip_dummynet.c:745

2022-11-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=133969 Kubilay Kocak changed: What|Removed |Added Keywords||crash -- You are receiving this m

[Bug 266048] [ixgbe] 82599ES reports IPv4 UDP with zero checksum as input errors

2022-11-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266048 --- Comment #5 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=8526120ad41ca47367b43f8f4459e0fa61285571 commit 8526120ad41ca47367b43f8f4459e0fa61285571 Author:

[Bug 237973] pf: implement egress keyword to simplify rules across different hardware

2022-11-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237973 d...@rabson.org changed: What|Removed |Added CC||d...@rabson.org --- Comment #21 f

[Bug 265857] qlnxe: no IPV6 pings between nodes on the same switch until an IPv4 address is set

2022-11-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265857 --- Comment #8 from benoitc --- I will try, so just changing the mtu using ifconfif ? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 237973] pf: implement egress keyword to simplify rules across different hardware

2022-11-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237973 --- Comment #22 from Goran Mekić --- I created a port in https://github.com/mekanix/freebsd-ports/tree/port/egress-monitor but it compiles only if you use root account. If anyone knows how to fix that I would be grateful. For now you can tr

[Bug 237973] pf: implement egress keyword to simplify rules across different hardware

2022-11-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237973 --- Comment #23 from d...@rabson.org --- For the root account problem, it looks like bsd.prog.mk always specifies root user. I guess you could workaround by overriding do-install in the port? -- You are receiving this mail because: You are

[Bug 237973] pf: implement egress keyword to simplify rules across different hardware

2022-11-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237973 --- Comment #24 from Goran Mekić --- I was missing one USES=uidfix, so that's sorted out, and I did create service file for it, but before I submit the port I want the "initial scan" implemented and that is: get the current default route an

[Bug 165059] vtnet(4): Networking breaks with a router using virtio net driver on KVM host

2022-11-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165059 Kubilay Kocak changed: What|Removed |Added Severity|Affects Only Me |Affects Some People Keyw

[Bug 165059] vtnet(4): Networking breaks with a router using virtio net driver on KVM host

2022-11-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165059 Kubilay Kocak changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 237973] pf: implement egress keyword to simplify rules across different hardware

2022-11-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237973 --- Comment #25 from Goran Mekić --- I created a port for egress-monitor in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267731 so please take any discussion about that port to that PR. -- You are receiving this mail because: You are

[Bug 165059] vtnet(4): Networking breaks with a router using virtio net driver on KVM host

2022-11-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165059 --- Comment #27 from elico --- (In reply to Kubilay Kocak from comment #26) I will try to test later on. Since Ubuntu 14.04 is not supported anymore I will try to reproduce on later versions of Ubuntu 20.04/22.04 and Oracle Linux 8. I will

Problem reports for n...@freebsd.org that need special attention

2022-11-13 Thread bugzilla-noreply
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

[Bug 165059] vtnet(4): Networking breaks with a router using virtio net driver on KVM host

2022-11-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165059 --- Comment #28 from elico --- (In reply to elico from comment #27) OK so just to mention the NAT related documents are at: http://draft.scyphus.co.jp/freebsd/nat.html and ontop of Oracle Enterprise Linux 8 KVM host the issue exists on 12.

[Bug 265857] qlnxe: no IPV6 pings between nodes on the same switch until an IPv4 address is set

2022-11-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265857 --- Comment #9 from benoitc --- changing the mtu didn't fix the issue. Howerver I can consistently reproduce the following: once the cards are put in promiscuuous mode they are able to reach each others. Disabling promiscuous mode after d

[Bug 265857] qlnxe: no IPV6 pings between nodes on the same switch until an IPv4 address is set

2022-11-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265857 --- Comment #10 from Zhenlei Huang --- (In reply to benoitc from comment #8) Sorry for late response. I'm lost in lots of mails. > I will try, so just changing the mtu using ifconfif ? Yes and no. Steps on node1: 1. ifconfig ql0 inet6

[Bug 265857] qlnxe: no IPV6 pings between nodes on the same switch until an IPv4 address is set

2022-11-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265857 --- Comment #11 from benoitc --- Created attachment 238090 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=238090&action=edit timeout after setting mtu -- You are receiving this mail because: You are the assignee for the bug.

[Bug 265857] qlnxe: no IPV6 pings between nodes on the same switch until an IPv4 address is set

2022-11-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265857 --- Comment #12 from benoitc --- (In reply to Zhenlei Huang from comment #10) I've tried it but got no ping: https://bugs.freebsd.org/bugzilla/attachment.cgi?id=238090 I'm not sure why i can access to them, but they can't ping each others.

[Bug 265857] qlnxe: no IPV6 pings between nodes on the same switch until an IPv4 address is set

2022-11-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265857 --- Comment #13 from benoitc --- Comment on attachment 238090 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=238090 timeout after setting mtu wrong ipv6. But when I tried without the interface: ``` ping6 fe80::b67a:f1ff:fe7a:9c

[Bug 265857] qlnxe: no IPV6 pings between nodes on the same switch until an IPv4 address is set

2022-11-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265857 --- Comment #14 from benoitc --- forget about the last comment. So the weird stuff is the following: i'm able to ping ::10 from ::11, ::12; ::13 using the public address on the same switch. This machine has a mellanox card (mce) ::11, ::1

[Bug 265857] qlnxe: no IPV6 pings between nodes on the same switch until an IPv4 address is set

2022-11-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265857 --- Comment #15 from Zhenlei Huang --- (In reply to benoitc from comment #14) > i'm able to ping ::10 from ::11, ::12; ::13 using the public address on the > same > switch. This machine has a mellanox card (mce) Do you mean the machine h

[Bug 265857] qlnxe: no IPV6 pings between nodes on the same switch until an IPv4 address is set

2022-11-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265857 --- Comment #16 from Zhenlei Huang --- (In reply to benoitc from comment #13) > wrong ipv6. But when I tried without the interface: > ``` > ping6 fe80::b67a:f1ff:fe7a:9c10 > ping6: UDP connect: Network is unreachable > ``` While ping lin

[Bug 265857] qlnxe: no IPV6 pings between nodes on the same switch until an IPv4 address is set

2022-11-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265857 --- Comment #17 from benoitc --- (In reply to Zhenlei Huang from comment #15) So to give a better idea I have 4 machines plugged to this switch. 3 with a qlnxe card (::11, ::12, ::13) and one with a mellanox card ::10 : |- ::11 m

[Bug 265857] qlnxe: no IPV6 pings between nodes on the same switch until an IPv4 address is set

2022-11-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265857 --- Comment #18 from benoitc --- (In reply to Zhenlei Huang from comment #16) Yes I did that. each machines can ping others using their local-link address afaik. Even without having to set the MTU. -- You are receiving this mail because

[Bug 265857] qlnxe: no IPV6 pings between nodes on the same switch until an IPv4 address is set

2022-11-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265857 --- Comment #19 from benoitc --- (In reply to Zhenlei Huang from comment #16) Yes I did that. each machines can ping others using their local-link address afaik. Even without having to set the MTU. -- You are receiving this mail because

[Bug 265857] qlnxe: no IPV6 pings between nodes on the same switch until an IPv4 address is set

2022-11-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265857 --- Comment #20 from Zhenlei Huang --- (In reply to benoitc from comment #17) > A, B, C , D can ping each others using the local link IP `fe080::` Why I got confused is that the attachment shows that ping from node2 to node1 with link-

[Bug 265857] qlnxe: no IPV6 pings between nodes on the same switch until an IPv4 address is set

2022-11-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265857 --- Comment #21 from benoitc --- (In reply to Zhenlei Huang from comment #20) > Why I got confused is that the attachment shows that ping from node2 to node1 > with link-local address fails . I tested after reboot without mtu set and it w

[Bug 265857] qlnxe: no IPV6 pings between nodes on the same switch until an IPv4 address is set

2022-11-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265857 --- Comment #22 from Zhenlei Huang --- (In reply to benoitc from comment #1) > looking at the source code: > https://cgit.freebsd.org/src/tree/sys/dev/qlnx/qlnxe/qlnx_os.c#n2675 > it seems that this snippet initialising the ha record : >

[Bug 265857] qlnxe: no IPV6 pings between nodes on the same switch until an IPv4 address is set

2022-11-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265857 --- Comment #23 from Zhenlei Huang --- (In reply to Zhenlei Huang from comment #22) > So when adding IPv6 addresses to the interface, it will be initialised (the > same with IPv4). That's why changing MTU does not help. -- You are recei

[Bug 265857] qlnxe: no IPV6 pings between nodes on the same switch until an IPv4 address is set

2022-11-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265857 --- Comment #24 from Zhenlei Huang --- I suspect some multicast packets are discarded. Can you do a tcpdump capture on D while ping6 A -> B, and ping6 A -> D ? Make sure clear neighbor cache on both side before every ping. tcpdump listern

<    2   3   4   5   6   7   8   9   10   11   >