https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287229
--- Comment #4 from Lucas Aubard ---
Yes, I confirm I am talking about IP-level reassembly. We tested it with
ICMP/IPCMv6 Echo Requests/Replies.
Unfortunately, I can not yet give you access to the platform. The work is
currently being pair
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287244
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286322
--- Comment #19 from Paige Thompson ---
SYSCTL_BOOL(_net_inet6_ip6, OID_AUTO, source_address_validation,
CTLFLAG_VNET | CTLFLAG_RW, &VNET_NAME(ip6_sav), true,
"Drop incoming packets with source address that is a local address");
>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285422
Mark Linimon changed:
What|Removed |Added
Status|New |Open
--
You are receiving this mai
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286322
--- Comment #18 from Paige Thompson ---
2 things I almost forgot:
- the NDP entries are listed as permanent so I'm not sure if that implies that
they are configured from discovery or if they were made static
- On linux I'm not sure what
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286322
--- Comment #17 from Paige Thompson ---
(In reply to Marek Zarychta from comment #16)
> perhaps it is working correctly
Indeed, the thought crossed my mind. The only problem I have with that is:
1. This works (Linux)
ip link add vrf1 ty
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287229
Michael Tuexen changed:
What|Removed |Added
CC||tue...@freebsd.org
--- Comment #3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287229
Olivier Cochard changed:
What|Removed |Added
CC||oliv...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286322
--- Comment #16 from Marek Zarychta ---
(In reply to Paige Thompson from comment #15)
It looks like a breakthrough. At least, the workaround has been found!
It's unclear whether we can attribute this failure to
net.inet6.ip6.source_address
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286322
--- Comment #13 from Paige Thompson ---
root@fbsdshell:/home/admin # ifconfig epair127 create
epair127a
root@fbsdshell:/home/admin # ifconfig epair127a inet6 fcff::a/64
root@fbsdshell:/home/admin # ifconfig epair127b inet6 fcff::b/64 fib
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287229
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286322
--- Comment #15 from Paige Thompson ---
Summary of things so far:
net.inet6.ip6.source_address_validation does not appear to be working correctly
when its set to 1 (default.) Turning it off allows me to use the desired
configuration, but
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286322
--- Comment #14 from Paige Thompson ---
Just took a guess ... wow
root@fbsdshell:/home/admin # sysctl net.inet6.ip6.source_address_validation=0
net.inet6.ip6.source_address_validation: 1 -> 0
root@fbsdshell:/home/admin # ping6 fcff::b
PING
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287163
--- Comment #10 from punkt.de Hosting Team ---
The IP address constraint - must be put on the bridge, never on a member
interface - is in the handbook section on bridging:
https://docs.freebsd.org/en/books/handbook/advanced-networking/#net
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287163
Marek Zarychta changed:
What|Removed |Added
CC||zarych...@plan-b.pwste.edu.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287163
--- Comment #8 from Martin Birgmeier ---
(In reply to punkt.de Hosting Team from comment #7)
It is probably not clear in my original description that this is about a bridge
setup where the addresses are "correctly" assigned. I am trying to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287163
punkt.de Hosting Team changed:
What|Removed |Added
CC||m...@punkt.de
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287163
--- Comment #6 from Martin Birgmeier ---
(In reply to Kevin Bowling from comment #4)
This setup is just to prepare for attaching bhyve tapX devices, to get bridged
networking with bhyve. They are created and destroyed dynamically when bhyv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287163
--- Comment #5 from Lexi Winter ---
> Its network interface is bridged to em0 (using vboxnet);
> it is not possible to bridge to bridge0, doing so generates
> an error message
i don't know anything about VirtualBox, but from the bridge(4)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286322
--- Comment #12 from Paige Thompson ---
nevermind, that actually doesn't work my theory is because that is going to the
same FIB "lo0" and it will have to be a static NDP entry
ifconfig epair9a inet6 2001:470:b56f::2 prefixlen 64
ifconfi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286322
--- Comment #11 from Paige Thompson ---
Yep, that works:
➜ sq ifconfig epair9a inet6 2001:470:b56f::2 prefixlen 64
➜ sq ifconfig epair9b inet6 2001:470:b56f::1 prefixlen 64
➜ sq route add -inet6 -host 2001:470:b56f::1 -iface lo0
ad
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286322
--- Comment #10 from Paige Thompson ---
TLDR I think I just figured out I can replicate this "working behavior if I
create the route manually I just have to specify lo0 as the interface:
route add -inet6 -host 2001:470:b56f::2 -iface lo0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286322
--- Comment #9 from Paige Thompson ---
I just tested using a 2000::/3 scoped address and it's the same problem,,
➜ ~ sudo ifconfig epair9a inet6 2001:470:B56F::2 prefixlen 64
➜ ~ sudo ifconfig epair9b inet6 2001:470:B56F::1 prefixlen 64
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287163
Kevin Bowling changed:
What|Removed |Added
CC||kbowl...@freebsd.org
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287163
--- Comment #3 from Martin Birgmeier ---
Regarding the doubts about using the native em0 instead of net/intel-em-kmod
(issue 2. in this bug report): They are unfortunately justified.
Because the bridge setup did not work, I reverted to em0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287163
--- Comment #2 from Martin Birgmeier ---
(In reply to Lexi Winter from comment #1)
In fact up till now I used the "wrong" configuration for em0 + bridge0:
- Start out with em0 only
- Create bridge0: ifconfig bridge0 create
- Add em0: ifcon
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287163
Lexi Winter changed:
What|Removed |Added
CC||i...@freebsd.org
--- Comment #1 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287163
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287135
--- Comment #2 from Christine Caulfield ---
It's not so much that we explicitly want the message to be truncated, what we
really want is consistency across platforms. If FreeBSD behaves differently
than others - including older versions of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287135
--- Comment #1 from Michael Tuexen ---
I would be interested why an application wants to use a SOCK_SEQPACKET packet
and also expects message loss when providing a too small receive buffer?
>From my understanding SOCK_SEQPACKET and SOCK_STR
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287135
Mark Linimon changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287150
Lexi Winter changed:
What|Removed |Added
CC||i...@freebsd.org
Assignee|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287150
Mark Linimon changed:
What|Removed |Added
Keywords||regression
Assignee|b...@
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255749
Zhenlei Huang changed:
What|Removed |Added
Assignee|n...@freebsd.org |z...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286759
Mark Johnston changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286689
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
Stat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286720
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
Stat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286631
--- Comment #1 from Michael Tuexen ---
Can you provide a .pcap file or even better a BBLog file showing the issue?
That would most likely allow me to write a packetdrill reproducer.
--
You are receiving this mail because:
You are the assi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281938
Michael Tuexen changed:
What|Removed |Added
Resolution|--- |Works As Intended
Sta
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281938
--- Comment #7 from Michael Tuexen ---
(In reply to nakayamakenjiro from comment #0)
If we are in the code path you mention, we are in the body of
if (len + optlen + ipoptlen > tp->t_maxseg) {
flags &= ~TH_FIN;
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286762
Mark Linimon changed:
What|Removed |Added
Summary|igc driver doesn't properly |igc driver doesn't properly
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286762
aaron.s...@baesystems.com changed:
What|Removed |Added
Summary|igc driver doesn't properly |igc driver doesn't prope
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286949
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262828
--- Comment #23 from Andrey V. Elsukov ---
(In reply to Andrey V. Elsukov from comment #18)
I was not entirely correct. ND code uses CARP mac address when populates
source-link address option. But then, when ethernet header is filled, it u
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286762
--- Comment #1 from aaron.s...@baesystems.com ---
Created attachment 260550
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=260550&action=edit
force igc link status check
Here's a patch that will force the link status check when t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254445
Lexi Winter changed:
What|Removed |Added
Assignee|n...@freebsd.org |i...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254675
Kurt Jaeger changed:
What|Removed |Added
Summary|ICMP Unreach needfrag is|ICMP Unreach needfrag is
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254675
m...@luckie.org.nz changed:
What|Removed |Added
CC||m...@luckie.org.nz
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254445
Lexi Winter changed:
What|Removed |Added
CC||i...@freebsd.org
--- Comment #2 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286812
Michael Tuexen changed:
What|Removed |Added
Assignee|n...@freebsd.org |tue...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286796
--- Comment #20 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=af907bb624141bd1aa1bd4586ea5b72d80780197
commit af907bb624141bd1aa1bd4586ea5b72d80780197
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286796
--- Comment #19 from rz-rp...@h-ka.de ---
(In reply to Konstantin Belousov from comment #12)
After applying the patch I repeated the action which triggered the panic seven
times, just to be sure.
No panic happened.
Thank you all, Ralf
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286796
rz-rp...@h-ka.de changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241106
Zhenlei Huang changed:
What|Removed |Added
Status|Open|Closed
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286812
Lexi Winter changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receivi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286796
--- Comment #18 from Rick Macklem ---
(In reply to Konstantin Belousov from comment #17)
Agreed. Thanks for finding and fixing the bug.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286796
--- Comment #17 from Konstantin Belousov ---
(In reply to Rick Macklem from comment #16)
It might be due to NODEBUG kernel config use by the reporter. It might change
stack layout somewhat, and might indeed expose different garbage value.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286796
--- Comment #16 from Rick Macklem ---
(In reply to Konstantin Belousov from comment #12)
This patch definitely looks ok and is needed.
(You can consider it reviewed by me.)
What is a little weird is that I don't see crashes?
I guess it dep
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286796
--- Comment #15 from Rick Macklem ---
(In reply to Konstantin Belousov from comment #14)
You are more than welcome to commit it. And I agree
we should wait until the reporter confirms it fixes the
problem.
--
You are receiving this mail b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286796
--- Comment #14 from Konstantin Belousov ---
(In reply to Rick Macklem from comment #13)
I planned to commit myself after your review and confirmation that the issue
is fixed. But go ahead if you want to.
--
You are receiving this mail b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286796
--- Comment #13 from Rick Macklem ---
(In reply to Konstantin Belousov from comment #12)
Oops, I just got around to looking at this.
Would you like to commit the patch or would you rather I do it?
--
You are receiving this mail because:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286796
--- Comment #12 from Konstantin Belousov ---
The kgdb trace is indeed useful.
I see that the issue came from e4c7b2b6053f2.
Please try the following change.
commit aa52aeb2f2ad00d89649d16474d1fab8196de9fe
Author: Konstantin Belousov
Date
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286796
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
Keywords
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286762
Mark Linimon changed:
What|Removed |Added
Keywords||IntelNetworking
Assignee|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286759
Mark Linimon changed:
What|Removed |Added
Summary|Fatal trap 12: page fault |Fatal trap 12: page fault
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254997
Mark Linimon changed:
What|Removed |Added
CC||bugmeis...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254675
Mark Linimon changed:
What|Removed |Added
CC||bugmeis...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254863
Mark Linimon changed:
What|Removed |Added
Assignee|n...@freebsd.org |bugmeis...@freebsd.org
Res
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199478
Gleb Smirnoff changed:
What|Removed |Added
Resolution|--- |FIXED
Status|In Progre
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286720
Zhenlei Huang changed:
What|Removed |Added
CC||chandrakanth.patil@broadcom
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199478
Mark Linimon changed:
What|Removed |Added
Assignee|test...@freebsd.org |n...@freebsd.org
Status
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275920
Kristof Provost changed:
What|Removed |Added
Assignee|k...@freebsd.org |n...@freebsd.org
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275920
Mark Linimon changed:
What|Removed |Added
Status|New |In Progress
Assignee|n...
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283426
Mark Linimon changed:
What|Removed |Added
Assignee|n...@freebsd.org |k...@freebsd.org
Statu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285545
Mark Linimon changed:
What|Removed |Added
Flags||mfc-stable14?,
|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286720
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286689
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
Keywords
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285492
--- Comment #2 from Konstantin Belousov ---
It could be fixed by 89e0e3814e8ca205db7523f6ce6c63cebe4bfb0d
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285492
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280390
--- Comment #24 from Tatsuki Makino ---
(In reply to Andrey V. Elsukov from comment #22 & #23)
> I still doesn't understand your problem.
Me too :)
As a result of being stingy with the money I pay upstream (removing services
like phone a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280390
--- Comment #23 from Andrey V. Elsukov ---
(In reply to Tatsuki Makino from comment #21)
> The results of ipfw -D show indicated that more than 2 packets were captured
> due to the ipv6-icmp rule, this patch may be meaningful :)
When you
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280390
--- Comment #22 from Andrey V. Elsukov ---
I still doesn't understand your problem. NPTv6 is stateless and doesn't need
any keep-state rules. We use NPTv6 many years and it works as is without any
patches.
--
You are receiving this mail b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280390
--- Comment #21 from Tatsuki Makino ---
(In reply to Tatsuki Makino from comment #20)
In the end, I came back to the method of using this :)
I wanted to keep one_pass enabled, so I used a strange method with dynamic
rules, but with the fol
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286631
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245103
Marek Zarychta changed:
What|Removed |Added
Attachment #260060|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286111
--- Comment #8 from Egor ---
> Is setting "bgp any peer" really your intention
I want to use this draft to discover bgp
peers(https://datatracker.ietf.org/doc/html/draft-xu-idr-neighbor-autodiscovery-12),
and it's already works fine with f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286322
--- Comment #8 from Lexi Winter ---
> Interface epair (4) will probably not work correctly if one endpoint is in
> FIB different then another endpoint
but this is the bug, isn't it? i think this should work, but it does not.
btw, earlie
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286260
--- Comment #15 from Marek Zarychta ---
Thank you, Sir, for fixing this subtle bug. It was a truly honourable
experience to report it, retract it, and finally witness how it was expertly
tracked down and resolved.
--
You are receiving thi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286260
Rick Macklem changed:
What|Removed |Added
Resolution|--- |FIXED
Status|In Progres
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286260
--- Comment #13 from commit-h...@freebsd.org ---
A commit in branch releng/14.3 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=2773c07181a772d5748e97bf4b26e7ffe4d444d7
commit 2773c07181a772d5748e97bf4b26e7ffe4d444d7
Auth
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286260
--- Comment #12 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=70369e4c2c1a882fcf9abf293b305f4f8a0b0c16
commit 70369e4c2c1a882fcf9abf293b305f4f8a0b0c16
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286260
--- Comment #11 from commit-h...@freebsd.org ---
A commit in branch stable/14 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=37abcf06f2100eeca41dbd67f8ca8228903ce5e8
commit 37abcf06f2100eeca41dbd67f8ca8228903ce5e8
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286322
--- Comment #7 from Marek Zarychta ---
The above tests from comment #5 are working fine in both 15.0-CURRENT and
14.3-STABLE. Interface epair (4) will probably not work correctly if one
endpoint is in FIB different then another endpoint, at
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286322
--- Comment #6 from Paige Thompson ---
(In reply to Marek Zarychta from comment #5)
Hi Marek,
It should work but it doesn’t, not for IPv6 anyway. All of my testing is done
on a fresh system but for what this is worth:
https://paige.bio/p
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286260
Rick Macklem changed:
What|Removed |Added
Flags||mfc-stable13?
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286260
Rick Macklem changed:
What|Removed |Added
Status|Open|In Progress
--- Comment #10 from Ri
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286260
--- Comment #9 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=68daa781c1f12e1cfef768030eaff970c3d35543
commit 68daa781c1f12e1cfef768030eaff970c3d35543
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245103
Marek Zarychta changed:
What|Removed |Added
Attachment #252676|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245103
Li-Wen Hsu changed:
What|Removed |Added
See Also||https://reviews.freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286322
Marek Zarychta changed:
What|Removed |Added
CC||zarych...@plan-b.pwste.edu.
1 - 100 of 3480 matches
Mail list logo
