[Bug 206721] FreeBSDs DHCP client(dhclient) does not support the interface-mtu option(option 26).

2016-09-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206721 Ben Woods changed: What|Removed |Added CC||no...@freebsd.org --- Comment #6 from

[Bug 208392] [ PATCH ] dhclient: add support for interface-mtu (26)

2016-09-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208392 Ben Woods changed: What|Removed |Added Status|New |Closed Resolution|---

[Bug 212283] network watchdog timeout with some raw sockets usage

2016-09-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212283 --- Comment #7 from Mathieu Arnold --- So, I tried your patch for ntraceroute, the problem is still there, the bge0 gets a watchdog timeout and the network still freezes for a minute or so. -- You are receiving this mail because: You are

netgraph/ng_base.c causing panic daily

2016-09-02 Thread Donald Baud via freebsd-net
I need help troubleshooting what seems to be race conditions with hooks in netgraph/ng_base.c Not sure what to look for in order to stop those daily panics on a machine running net/mpd5 with a few hundreds l2tp sessions. I'm suspecting a crash being caused by: /usr/src/sys/modules/netgraph/netg

[Bug 206721] FreeBSDs DHCP client(dhclient) does not support the interface-mtu option(option 26).

2016-09-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206721 Conrad E. Meyer changed: What|Removed |Added Resolution|--- |FIXED Status|New

[Bug 206721] FreeBSDs DHCP client(dhclient) does not support the interface-mtu option(option 26).

2016-09-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206721 --- Comment #4 from commit-h...@freebsd.org --- A commit references this bug: Author: cem Date: Fri Sep 2 21:14:30 UTC 2016 New revision: 305306 URL: https://svnweb.freebsd.org/changeset/base/305306 Log: dhclient: add support for interf

[Bug 212283] network watchdog timeout with some raw sockets usage

2016-09-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212283 --- Comment #6 from commit-h...@freebsd.org --- A commit references this bug: Author: mat Date: Fri Sep 2 21:12:22 UTC 2016 New revision: 421276 URL: https://svnweb.freebsd.org/changeset/ports/421276 Log: Fix on 11. PR: 212

Re: 60G+ network connection

2016-09-02 Thread sthaug
> > 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

Re: 60G+ network connection

2016-09-02 Thread Alan Somers
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

Re: 60G+ network connection

2016-09-02 Thread Slawa Olhovchenkov
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

Re: 60G+ network connection

2016-09-02 Thread Kajetan Staszkiewicz
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

[Bug 195692] Feature request: Make devd read MAC addresses

2016-09-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195692 Jilles Tjoelker changed: What|Removed |Added Status|New |Closed CC|

Re: 60G+ network connection

2016-09-02 Thread Slawa Olhovchenkov
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

Re: 60G+ network connection

2016-09-02 Thread Hans Petter Selasky
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

Re: 60G+ network connection

2016-09-02 Thread Slawa Olhovchenkov
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

Re: 60G+ network connection

2016-09-02 Thread Hans Petter Selasky
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