The fact that FreeBSD 11 has almost five years of support left is part
of what makes this a good time to remove support from 12. Updating 11
to support newer cards certainly makes sense.
-- Brooks
On Fri, Apr 07, 2017 at 06:30:05AM -0700, Kevin Bowling wrote:
> For consideration, stable/11 will
On Fri, 7 Apr 2017, ?ukasz W?jcik wrote:
?W>they're not the only ones. Just my 5cents. The other thing is that ATM/NATM
?W>infrastructure in FreeBSD seems to never have been
?W>
?W>finished.
That's true. ITU-T used to produce poor-quality ATM standards at a much
higher rate than anybody could fo
For consideration, stable/11 will be supported until September 30, 2021
which provides a pretty long window to transition.
On Fri, Apr 7, 2017 at 6:15 AM, Łukasz Wójcik
wrote:
> Oh, and mbpool DMA syncing does not work at all and -- at least in patm
> driver -- causes various issues.
>
> This of
Oh, and mbpool DMA syncing does not work at all and -- at least in patm
driver -- causes various issues.
This of course can be easily worked around if you choose to let ATM
ecosystem stay. If my client agrees,
I could also share a patch for patm to make it work with newer ProSUM
hardware.
Hi Brooks,
AFAIK Prosum still manufactures PROATM155M card that utilizes patm
driver (which is by the way a little bit outdated and does
not support newer variants of ProSUM cards). I also have clients that
still use ATM and prosum cards and FreeBSD. My guess is that
they're not the only o
Hi,
> On 7 Apr 2017, at 00:57, Brooks Davis wrote:
>
> As previously threatened, I plan to remove NATM support next week. This
> includes the drivers en(4), fatm(4), hatm(4), and patm(4). None of
> these devices have been manufactured in the last 20 years so it is time
> to move on.
I don’t h
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217637
Kubilay Kocak changed:
What|Removed |Added
URL||https://reviews.freebsd.org
On 04/07/2017 03:40, Takahiro Kurosawa wrote:
What if you change the line:
pass in inet proto tcp to port { ssh }
to:
pass in inet proto tcp to port { ssh } no state
close, but I had to use the "no state" on the "pass out" rules as well.
Now it looks like that:
-
