https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282982
--- Comment #2 from Quentin Thébault ---
Indeed.
Following the workaround you proposed in comment 7 of that bug
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280132#c7), the jail can
ping outside with no issue.
But the host is still
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282982
Zhenlei Huang changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265714
--- Comment #13 from j...@cybersashi.com ---
Is there any information regarding what i225 and i226 NVM versions are
considered stable with the FreeBSD driver (i.e. what NVM version(s) are you and
Netgate successfully using)?
--
You are rec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282982
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=265714
--- Comment #12 from Kevin Bowling ---
(In reply to mike from comment #11)
To confirm you are setting that on both sides on boot?
I am not sure what to make of the instability so far, it is sounding like the
PHY FW you have is buggy which
Hi,
I'm trying to help someone at a different department at $DAYJOB and am
stuck on setting up a 464XLAT on FreeBSD.
Right now I'm trying this guide:
https://forums.freebsd.org/threads/nat64-464xlat.73741/
However, it does not seem to be correct. The person said they got it
working but did
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282535
Alexander Ziaee changed:
What|Removed |Added
Status|New |In Progress
--
You are receivin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265714
--- Comment #11 from m...@sentex.net ---
(In reply to mike from comment #10)
this is only on the J1900 CPU.(Baytrail chipset)
It does not seem to have an impact on the Jasper Lake box
--
You are receiving this mail because:
You are the a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265714
--- Comment #10 from m...@sentex.net ---
Created attachment 255461
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=255461&action=edit
hw.igc.eee_setting=0
Interesting, setting that to zero makes iperf3 fail after a few seconds wit
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256587
Mark Linimon changed:
What|Removed |Added
Flags||mfc-stable13?
Assignee|n.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265714
--- Comment #9 from Kevin Bowling ---
(In reply to mike from comment #8)
Whoops sorry AIM has been on my mind most recently. I meant:
hw.igc.eee_setting=0
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265714
--- Comment #8 from m...@sentex.net ---
(In reply to Kevin Bowling from comment #7)
Cable is a store bought cat 6, so machine crimped. Right now both boxes were
cross over to each other. No switch. With AIM=0 I get slower performance just
s
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282805
--- Comment #10 from Jung-uk Kim ---
Another possible solution is porting Linux driver via linuxkpi.
https://github.com/Aquantia/AQtion
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/ethernet/aquantia/a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282805
--- Comment #9 from Viljo Hakala ---
Is anyone willing to contribute on this? Please contact, if you
need compensation or resources.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282805
Jung-uk Kim changed:
What|Removed |Added
CC||j...@freebsd.org
--- Comment #4 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282805
--- Comment #8 from Jung-uk Kim ---
(In reply to Viljo Hakala from comment #7)
This patch added support for AQC113 to NetBSD driver.
https://mail-index.netbsd.org/source-changes/2023/01/14/msg142808.html
http://cvsweb.netbsd.org/bsdweb.cgi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265714
--- Comment #7 from Kevin Bowling ---
(In reply to mike from comment #6)
If this is on a datacenter cable plant do you have access to a cable certifier
or can you eliminate that from the situation by plugging it into say a 10ft
cable?
What
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282805
--- Comment #7 from Viljo Hakala ---
(In reply to Jung-uk Kim from comment #6)
My question is still valid. Is anyone working on this yet?
How do you organize the development further?
--
You are receiving this mail because:
You are the as
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282805
--- Comment #6 from Jung-uk Kim ---
(In reply to Brad Smith from comment #5)
Never mind. I just saw the OP also filed the upstream PR.
https://github.com/Aquantia/aqtion-freebsd/issues/32
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282805
Brad Smith changed:
What|Removed |Added
CC||b...@comstyle.com
--- Comment #5 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265714
--- Comment #6 from m...@sentex.net ---
Created attachment 255456
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=255456&action=edit
hardware info and sysctl output post test
Hardware info and sysctl output
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282805
Viljo Hakala changed:
What|Removed |Added
CC||hakala.vi...@gmail.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282535
--- Comment #4 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=c94d6389e428fac55946bfcdbbc3162c06a9278e
commit c94d6389e428fac55946bfcdbbc3162c06a9278e
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265714
--- Comment #5 from m...@sentex.net ---
(In reply to Kevin Bowling from comment #4)
I dont think I have the old hardware anymore with the i225 chipset. I will
however test with i226 to see how it performs
--
You are receiving this mail be
24 matches
Mail list logo
