https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216460
Kevin Bowling changed:
What|Removed |Added
Resolution|--- |Not Enough Information
Why is it that sometimes I lose network connection and then gain it back
without making any changes.
For example: I cannot update source or pkg repository or ports collection, but
20 minutes ago I could.
Is there a separate network issue that is responsible for me not being able to
update
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236962
Konstantin Belousov changed:
What|Removed |Added
CC||k...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236962
--- Comment #5 from Eugene Grosbein ---
Maybe you'll need to adjust pattern matching as your logs have different format
comparing to logs generated to my FreeBSD 11.2 boxes.
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236962
Eugene Grosbein changed:
What|Removed |Added
CC||eu...@freebsd.org
--- Comment #4
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236962
--- Comment #3 from mar...@herrbischoff.com ---
Rodney, thanks for the information. I cannot change the NICs since the machines
affected are dedicated servers provided by a commercial data center. Since
their pricing is quite competitive, it
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236962
--- Comment #2 from Rodney W. Grimes ---
You might start with this bugzilla search:
https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__all__&content=0x816810ec&list_id=292731&order=Importance&query_format=specific
I searched for yo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236962
Rodney W. Grimes changed:
What|Removed |Added
CC||rgri...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236962
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=236486
Bug ID: 236486
Summary: [igb] txcsum produces broken checksum for I350 Gigabit
Network Connection
Product: Base System
Version: 11.2-STABLE
Hardware: amd64
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216460
tanu_l...@yahoo.com changed:
What|Removed |Added
CC||tanu_l...@yahoo.com
--- Comme
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216460
--- Comment #2 from John Legato ---
Thanks for the reply. In the interest of time, I swapped the card out for a
Mellanox NIC so I'm unable to test the Intel card.
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216460
Kevin Bowling changed:
What|Removed |Added
CC||kbowl...@freebsd.org
--- Comment #
+
|Network Connection link |Network Connection link
|constantly falps|constantly flaps
CC|freebsd-am...@freebsd.org |
Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org
Keywords
> > Plase note that by using link aggregation you can not achieve full speed
> > over
> > a single TCP stream. Onle when multiple streams are in operation you will
> > really get the aggregated speed.
>
> NP, I am have more then 40K TCP stream.
>
> PS: link aggregation with round-roubin policy
On Fri, Sep 2, 2016 at 8:07 AM, Slawa Olhovchenkov wrote:
> On Fri, Sep 02, 2016 at 04:02:20PM +0200, Kajetan Staszkiewicz wrote:
>
>> On day piątek, 2 września 2016 13:02:03 Slawa Olhovchenkov wrote:
>>
>> > > > PS: 100G transmiters and connectiveti too expensive, 2x40G prefer.
>> > >
>> > > You
On Fri, Sep 02, 2016 at 04:02:20PM +0200, Kajetan Staszkiewicz wrote:
> On day piątek, 2 września 2016 13:02:03 Slawa Olhovchenkov wrote:
>
> > > > PS: 100G transmiters and connectiveti too expensive, 2x40G prefer.
> > >
> > > You can put 2x 40GBit/s modules in the CX-4. I'm not sure if you can
On day piątek, 2 września 2016 13:02:03 Slawa Olhovchenkov wrote:
> > > PS: 100G transmiters and connectiveti too expensive, 2x40G prefer.
> >
> > You can put 2x 40GBit/s modules in the CX-4. I'm not sure if you can
> > combine 2x 40GBit/s into a single 80GBit/s.
>
> I can do it by if_lagg.
Pla
On Fri, Sep 02, 2016 at 11:44:20AM +0200, Hans Petter Selasky wrote:
> On 09/02/16 11:31, Slawa Olhovchenkov wrote:
> > On Fri, Sep 02, 2016 at 09:37:25AM +0200, Hans Petter Selasky wrote:
> >
> >> On 09/01/16 23:18, Slawa Olhovchenkov wrote:
> >>> What hardware (NIC) recomended for 60G+ network s
On 09/02/16 11:31, Slawa Olhovchenkov wrote:
On Fri, Sep 02, 2016 at 09:37:25AM +0200, Hans Petter Selasky wrote:
On 09/01/16 23:18, Slawa Olhovchenkov wrote:
What hardware (NIC) recomended for 60G+ network speed?
Chelsio limited to 54Gbit/s
Melanox don't available new drivers for ConnectX-5
On Fri, Sep 02, 2016 at 09:37:25AM +0200, Hans Petter Selasky wrote:
> On 09/01/16 23:18, Slawa Olhovchenkov wrote:
> > What hardware (NIC) recomended for 60G+ network speed?
> >
> > Chelsio limited to 54Gbit/s
> > Melanox don't available new drivers for ConnectX-5 and need too
> > expensive trans
On 09/01/16 23:18, Slawa Olhovchenkov wrote:
What hardware (NIC) recomended for 60G+ network speed?
Chelsio limited to 54Gbit/s
Melanox don't available new drivers for ConnectX-5 and need too
expensive transmiters and connectivity.
Melanox don't available new drivers for ConnectX-4 Lx and also l
What hardware (NIC) recomended for 60G+ network speed?
Chelsio limited to 54Gbit/s
Melanox don't available new drivers for ConnectX-5 and need too
expensive transmiters and connectivity.
Melanox don't available new drivers for ConnectX-4 Lx and also limited
to 54Gbit/s
Intel XL710 also limited to
W dniu 2013-09-09 15:11, Mark van der Meulen pisze:
As far as I can tell, if you are using the links in a lagg then you are going
to need to make the change in /etc/rc.conf and reboot or perhaps restart netif.
I recently came across a similar situation where I had to change the MTU across
a bu
> Hi,
>
> My server is running with 4 Gigabit NICs:
>
> igb0@pci0:5:0:0:class=0x02 card=0x152115d9 chip=0x15218086
> rev=0x01 hdr=0x00
> vendor = 'Intel Corporation'
> device = 'I350 Gigabit Network Connection'
> cl
As far as I can tell, if you are using the links in a lagg then you are going
to need to make the change in /etc/rc.conf and reboot or perhaps restart netif.
I recently came across a similar situation where I had to change the MTU across
a bunch of different bsdrp boxes running as firewalls and
W dniu 2013-09-09 15:02, Marek Salwerowicz pisze:
My server
just to add - I am running the 9.1-RELEASE:
FreeBSD storage1 9.1-RELEASE-p6 FreeBSD 9.1-RELEASE-p6 #0: Wed Aug 21
20:40:52 UTC 2013
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
___
Hi,
My server is running with 4 Gigabit NICs:
igb0@pci0:5:0:0:class=0x02 card=0x152115d9 chip=0x15218086
rev=0x01 hdr=0x00
vendor = 'Intel Corporation'
device = 'I350 Gigabit Network Connection'
class = network
subclass = ethe
A new version of ixgbe was committed this afternoon, 2.5.13, it now has a
compile-time
option of using unsupported optics. Keep in mind that if you have issues
I'm going to
ask if it can be reproduced with supported optics as a first step :)
Cheers,
Jack
On Tue, Jun 18, 2013 at 5:12 PM, Haven
I believe there are two checks, one for Intel specific SFP modules (as some
cards have their EEPROM's configured to only accept Intel branded optics),
which this patch deals with, and another separate check for supported SFP's
which is not addressed by this. Support SFP's include adapters from Fini
Thanks, but this does not work.
ix0:
port 0xece0-0xecff mem
0xdf36-0xdf37,0xdf3c-0xdf3f,0xdf33c000-0xdf33 irq 45
at device 0.1 on pci6
ix0: Using MSIX interrupts with 9 vectors
ix0: Unsupported SFP+ Module
ix0: Hardware Initialization Failure
device_attach: ix0 attach returned
Cool. Any idea of when soon might be?
And about that list of supported SFP+ modules?
Is any Intel 10-GBASE-SR SFP+ module guaranteed to work with this card
and driver?
-Boris
On 06/09/13 22:09, Jack Vogel wrote:
> There will be a driver update soon with the way it should be done, it will
> be i
There will be a driver update soon with the way it should be done, it will
be in the core driver
code and not as here in the shared code.
Regards,
Jack
PS Oh, and the email address should be 'free...@intel.com' now rather than
freebsdnic, it
still ultimately just gets to me however.
On Sun, J
With the following patch the ixgbe (ix) driver
accepts any SFP.
--- ixgbe_phy.c.orig2012-10-01 18:38:31.0 +0200
+++ ixgbe_phy.c 2012-11-13 16:23:18.650609931 +0100
@@ -1186,6 +1186,7 @@
}
ixgbe_get_device_caps(hw, &enforce_sfp);
+ en
I had originally sent this to the freebsd...@mailbox.intel.com address
mentioned in the ixgbe(4) man page, but it unfortunately bounced.
I am running FreeBSD 9.1-RELEASE/amd64 and have a "82598EB 10-Gigabit AF
Dual Port Network Connection" controller. I've been trying to get a
work
Synopsis: [ath] network connection freezes if using WPA-PSK encryption with 2
Atheros WIFI cards on AR9285 chipset connected to same AP
State-Changed-From-To: open->closed
State-Changed-By: vwe
State-Changed-When: Mon Mar 29 19:41:11 UTC 2010
State-Changed-Why:
submitter requests to close t
The following reply was made to PR kern/145123; it has been noted by GNATS.
From: Eugeny N Dzhurinsky
To: bug-follo...@freebsd.org, b...@redwerk.com
Cc:
Subject: Re: kern/145123: network connection freezes if using WPA-PSK
encryption with 2 Atheros WIFI cards on AR9285 chipset connected to
Old Synopsis: network connection freezes if using WPA-PSK encryption with 2
Atheros WIFI cards on AR9285 chipset connected to same AP
New Synopsis: [ath] network connection freezes if using WPA-PSK encryption with
2 Atheros WIFI cards on AR9285 chipset connected to same AP
Responsible-Changed
Synopsis: [ndis] [patch] ndis network driver sometimes loses network connection
Responsible-Changed-From-To: cokane->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Sat Mar 20 02:37:53 UTC 2010
Responsible-Changed-Why:
returned to the pool by request (some time ago.)
h
Synopsis: [ndis] [patch] ndis network driver sometimes loses network connection
Responsible-Changed-From-To: freebsd-net->cokane
Responsible-Changed-By: cokane
Responsible-Changed-When: Wed Jul 2 14:56:51 UTC 2008
Responsible-Changed-Why:
PR refers to a recent commit of changes that I made
Old Synopsis: ndis network driver sometimes loses network connection
New Synopsis: [ndis] [patch] ndis network driver sometimes loses network
connection
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Tue Jun 3 02:46:09 UTC 2
<><><><>NETWORK CONFIG/SETUP: <><><><>
+++ISP -> DSL(high-speed) -> Modem> FreeBSD51 server machine in at Gateway "vr0"
(192.168.0.1)
+++Freebsd machine LAN Interface at "ed0" (192.168.0.3) -> HUB
+++HUB> 1) 192.168.0.2 - WinXP #1 machine 2) 192.168.0.3 - Freebsd machine in at "ed0"
3) 192.16
42 matches
Mail list logo
