/freebsd/usr.sbin/bsnmpd/modules/ |
H A D | Makefile | diff a7dc31283a053a6c0444813d1432fa83e6ccba9f Mon Apr 24 23:21:49 CEST 2017 Brooks Davis <brooks@FreeBSD.org> Remove the NATM framework including the en(4), fatm(4), hatm(4), and patm(4) devices.
Maintaining an address family and framework has real costs when we make infrastructure improvements. In the case of NATM we support no devices manufactured in the last 20 years and some will not even work in modern motherboards (some newer devices that patm(4) could be updated to support apparently exist, but we do not currently have support).
With this change, support remains for some netgraph modules that don't require NATM support code. It is unclear if all these should remain, though ng_atmllc certainly stands alone.
Note well: FreeBSD 11 supports NATM and will continue to do so until at least September 30, 2021. Improvements to the code in FreeBSD 11 are certainly welcome.
Reviewed by: philip Approved by: harti
|
/freebsd/sys/conf/ |
H A D | config.mk | diff a7dc31283a053a6c0444813d1432fa83e6ccba9f Mon Apr 24 23:21:49 CEST 2017 Brooks Davis <brooks@FreeBSD.org> Remove the NATM framework including the en(4), fatm(4), hatm(4), and patm(4) devices.
Maintaining an address family and framework has real costs when we make infrastructure improvements. In the case of NATM we support no devices manufactured in the last 20 years and some will not even work in modern motherboards (some newer devices that patm(4) could be updated to support apparently exist, but we do not currently have support).
With this change, support remains for some netgraph modules that don't require NATM support code. It is unclear if all these should remain, though ng_atmllc certainly stands alone.
Note well: FreeBSD 11 supports NATM and will continue to do so until at least September 30, 2021. Improvements to the code in FreeBSD 11 are certainly welcome.
Reviewed by: philip Approved by: harti
|
H A D | options | diff a7dc31283a053a6c0444813d1432fa83e6ccba9f Mon Apr 24 23:21:49 CEST 2017 Brooks Davis <brooks@FreeBSD.org> Remove the NATM framework including the en(4), fatm(4), hatm(4), and patm(4) devices.
Maintaining an address family and framework has real costs when we make infrastructure improvements. In the case of NATM we support no devices manufactured in the last 20 years and some will not even work in modern motherboards (some newer devices that patm(4) could be updated to support apparently exist, but we do not currently have support).
With this change, support remains for some netgraph modules that don't require NATM support code. It is unclear if all these should remain, though ng_atmllc certainly stands alone.
Note well: FreeBSD 11 supports NATM and will continue to do so until at least September 30, 2021. Improvements to the code in FreeBSD 11 are certainly welcome.
Reviewed by: philip Approved by: harti
|
H A D | NOTES | diff a7dc31283a053a6c0444813d1432fa83e6ccba9f Mon Apr 24 23:21:49 CEST 2017 Brooks Davis <brooks@FreeBSD.org> Remove the NATM framework including the en(4), fatm(4), hatm(4), and patm(4) devices.
Maintaining an address family and framework has real costs when we make infrastructure improvements. In the case of NATM we support no devices manufactured in the last 20 years and some will not even work in modern motherboards (some newer devices that patm(4) could be updated to support apparently exist, but we do not currently have support).
With this change, support remains for some netgraph modules that don't require NATM support code. It is unclear if all these should remain, though ng_atmllc certainly stands alone.
Note well: FreeBSD 11 supports NATM and will continue to do so until at least September 30, 2021. Improvements to the code in FreeBSD 11 are certainly welcome.
Reviewed by: philip Approved by: harti
|
H A D | files | diff a7dc31283a053a6c0444813d1432fa83e6ccba9f Mon Apr 24 23:21:49 CEST 2017 Brooks Davis <brooks@FreeBSD.org> Remove the NATM framework including the en(4), fatm(4), hatm(4), and patm(4) devices.
Maintaining an address family and framework has real costs when we make infrastructure improvements. In the case of NATM we support no devices manufactured in the last 20 years and some will not even work in modern motherboards (some newer devices that patm(4) could be updated to support apparently exist, but we do not currently have support).
With this change, support remains for some netgraph modules that don't require NATM support code. It is unclear if all these should remain, though ng_atmllc certainly stands alone.
Note well: FreeBSD 11 supports NATM and will continue to do so until at least September 30, 2021. Improvements to the code in FreeBSD 11 are certainly welcome.
Reviewed by: philip Approved by: harti
|
/freebsd/sys/net/ |
H A D | netisr.h | diff a7dc31283a053a6c0444813d1432fa83e6ccba9f Mon Apr 24 23:21:49 CEST 2017 Brooks Davis <brooks@FreeBSD.org> Remove the NATM framework including the en(4), fatm(4), hatm(4), and patm(4) devices.
Maintaining an address family and framework has real costs when we make infrastructure improvements. In the case of NATM we support no devices manufactured in the last 20 years and some will not even work in modern motherboards (some newer devices that patm(4) could be updated to support apparently exist, but we do not currently have support).
With this change, support remains for some netgraph modules that don't require NATM support code. It is unclear if all these should remain, though ng_atmllc certainly stands alone.
Note well: FreeBSD 11 supports NATM and will continue to do so until at least September 30, 2021. Improvements to the code in FreeBSD 11 are certainly welcome.
Reviewed by: philip Approved by: harti
|
/freebsd/usr.sbin/ppp/ |
H A D | physical.c | diff a7dc31283a053a6c0444813d1432fa83e6ccba9f Mon Apr 24 23:21:49 CEST 2017 Brooks Davis <brooks@FreeBSD.org> Remove the NATM framework including the en(4), fatm(4), hatm(4), and patm(4) devices.
Maintaining an address family and framework has real costs when we make infrastructure improvements. In the case of NATM we support no devices manufactured in the last 20 years and some will not even work in modern motherboards (some newer devices that patm(4) could be updated to support apparently exist, but we do not currently have support).
With this change, support remains for some netgraph modules that don't require NATM support code. It is unclear if all these should remain, though ng_atmllc certainly stands alone.
Note well: FreeBSD 11 supports NATM and will continue to do so until at least September 30, 2021. Improvements to the code in FreeBSD 11 are certainly welcome.
Reviewed by: philip Approved by: harti
|
H A D | Makefile | diff a7dc31283a053a6c0444813d1432fa83e6ccba9f Mon Apr 24 23:21:49 CEST 2017 Brooks Davis <brooks@FreeBSD.org> Remove the NATM framework including the en(4), fatm(4), hatm(4), and patm(4) devices.
Maintaining an address family and framework has real costs when we make infrastructure improvements. In the case of NATM we support no devices manufactured in the last 20 years and some will not even work in modern motherboards (some newer devices that patm(4) could be updated to support apparently exist, but we do not currently have support).
With this change, support remains for some netgraph modules that don't require NATM support code. It is unclear if all these should remain, though ng_atmllc certainly stands alone.
Note well: FreeBSD 11 supports NATM and will continue to do so until at least September 30, 2021. Improvements to the code in FreeBSD 11 are certainly welcome.
Reviewed by: philip Approved by: harti
|
/freebsd/rescue/rescue/ |
H A D | Makefile | diff a7dc31283a053a6c0444813d1432fa83e6ccba9f Mon Apr 24 23:21:49 CEST 2017 Brooks Davis <brooks@FreeBSD.org> Remove the NATM framework including the en(4), fatm(4), hatm(4), and patm(4) devices.
Maintaining an address family and framework has real costs when we make infrastructure improvements. In the case of NATM we support no devices manufactured in the last 20 years and some will not even work in modern motherboards (some newer devices that patm(4) could be updated to support apparently exist, but we do not currently have support).
With this change, support remains for some netgraph modules that don't require NATM support code. It is unclear if all these should remain, though ng_atmllc certainly stands alone.
Note well: FreeBSD 11 supports NATM and will continue to do so until at least September 30, 2021. Improvements to the code in FreeBSD 11 are certainly welcome.
Reviewed by: philip Approved by: harti
|
/freebsd/sbin/ |
H A D | Makefile | diff a7dc31283a053a6c0444813d1432fa83e6ccba9f Mon Apr 24 23:21:49 CEST 2017 Brooks Davis <brooks@FreeBSD.org> Remove the NATM framework including the en(4), fatm(4), hatm(4), and patm(4) devices.
Maintaining an address family and framework has real costs when we make infrastructure improvements. In the case of NATM we support no devices manufactured in the last 20 years and some will not even work in modern motherboards (some newer devices that patm(4) could be updated to support apparently exist, but we do not currently have support).
With this change, support remains for some netgraph modules that don't require NATM support code. It is unclear if all these should remain, though ng_atmllc certainly stands alone.
Note well: FreeBSD 11 supports NATM and will continue to do so until at least September 30, 2021. Improvements to the code in FreeBSD 11 are certainly welcome.
Reviewed by: philip Approved by: harti
|
/freebsd/etc/mtree/ |
H A D | BSD.usr.dist | diff a7dc31283a053a6c0444813d1432fa83e6ccba9f Mon Apr 24 23:21:49 CEST 2017 Brooks Davis <brooks@FreeBSD.org> Remove the NATM framework including the en(4), fatm(4), hatm(4), and patm(4) devices.
Maintaining an address family and framework has real costs when we make infrastructure improvements. In the case of NATM we support no devices manufactured in the last 20 years and some will not even work in modern motherboards (some newer devices that patm(4) could be updated to support apparently exist, but we do not currently have support).
With this change, support remains for some netgraph modules that don't require NATM support code. It is unclear if all these should remain, though ng_atmllc certainly stands alone.
Note well: FreeBSD 11 supports NATM and will continue to do so until at least September 30, 2021. Improvements to the code in FreeBSD 11 are certainly welcome.
Reviewed by: philip Approved by: harti
|
/freebsd/include/ |
H A D | Makefile | diff a7dc31283a053a6c0444813d1432fa83e6ccba9f Mon Apr 24 23:21:49 CEST 2017 Brooks Davis <brooks@FreeBSD.org> Remove the NATM framework including the en(4), fatm(4), hatm(4), and patm(4) devices.
Maintaining an address family and framework has real costs when we make infrastructure improvements. In the case of NATM we support no devices manufactured in the last 20 years and some will not even work in modern motherboards (some newer devices that patm(4) could be updated to support apparently exist, but we do not currently have support).
With this change, support remains for some netgraph modules that don't require NATM support code. It is unclear if all these should remain, though ng_atmllc certainly stands alone.
Note well: FreeBSD 11 supports NATM and will continue to do so until at least September 30, 2021. Improvements to the code in FreeBSD 11 are certainly welcome.
Reviewed by: philip Approved by: harti
|
/freebsd/share/man/man4/ |
H A D | Makefile | diff a7dc31283a053a6c0444813d1432fa83e6ccba9f Mon Apr 24 23:21:49 CEST 2017 Brooks Davis <brooks@FreeBSD.org> Remove the NATM framework including the en(4), fatm(4), hatm(4), and patm(4) devices.
Maintaining an address family and framework has real costs when we make infrastructure improvements. In the case of NATM we support no devices manufactured in the last 20 years and some will not even work in modern motherboards (some newer devices that patm(4) could be updated to support apparently exist, but we do not currently have support).
With this change, support remains for some netgraph modules that don't require NATM support code. It is unclear if all these should remain, though ng_atmllc certainly stands alone.
Note well: FreeBSD 11 supports NATM and will continue to do so until at least September 30, 2021. Improvements to the code in FreeBSD 11 are certainly welcome.
Reviewed by: philip Approved by: harti
|
/freebsd/ |
H A D | ObsoleteFiles.inc | diff a7dc31283a053a6c0444813d1432fa83e6ccba9f Mon Apr 24 23:21:49 CEST 2017 Brooks Davis <brooks@FreeBSD.org> Remove the NATM framework including the en(4), fatm(4), hatm(4), and patm(4) devices.
Maintaining an address family and framework has real costs when we make infrastructure improvements. In the case of NATM we support no devices manufactured in the last 20 years and some will not even work in modern motherboards (some newer devices that patm(4) could be updated to support apparently exist, but we do not currently have support).
With this change, support remains for some netgraph modules that don't require NATM support code. It is unclear if all these should remain, though ng_atmllc certainly stands alone.
Note well: FreeBSD 11 supports NATM and will continue to do so until at least September 30, 2021. Improvements to the code in FreeBSD 11 are certainly welcome.
Reviewed by: philip Approved by: harti
|
/freebsd/sys/sys/ |
H A D | param.h | diff a7dc31283a053a6c0444813d1432fa83e6ccba9f Mon Apr 24 23:21:49 CEST 2017 Brooks Davis <brooks@FreeBSD.org> Remove the NATM framework including the en(4), fatm(4), hatm(4), and patm(4) devices.
Maintaining an address family and framework has real costs when we make infrastructure improvements. In the case of NATM we support no devices manufactured in the last 20 years and some will not even work in modern motherboards (some newer devices that patm(4) could be updated to support apparently exist, but we do not currently have support).
With this change, support remains for some netgraph modules that don't require NATM support code. It is unclear if all these should remain, though ng_atmllc certainly stands alone.
Note well: FreeBSD 11 supports NATM and will continue to do so until at least September 30, 2021. Improvements to the code in FreeBSD 11 are certainly welcome.
Reviewed by: philip Approved by: harti
|
/freebsd/sys/modules/ |
H A D | Makefile | diff a7dc31283a053a6c0444813d1432fa83e6ccba9f Mon Apr 24 23:21:49 CEST 2017 Brooks Davis <brooks@FreeBSD.org> Remove the NATM framework including the en(4), fatm(4), hatm(4), and patm(4) devices.
Maintaining an address family and framework has real costs when we make infrastructure improvements. In the case of NATM we support no devices manufactured in the last 20 years and some will not even work in modern motherboards (some newer devices that patm(4) could be updated to support apparently exist, but we do not currently have support).
With this change, support remains for some netgraph modules that don't require NATM support code. It is unclear if all these should remain, though ng_atmllc certainly stands alone.
Note well: FreeBSD 11 supports NATM and will continue to do so until at least September 30, 2021. Improvements to the code in FreeBSD 11 are certainly welcome.
Reviewed by: philip Approved by: harti
|