If we need to make an exception we can do it and properly document the
reason but by default we should just use the default login class.
rc.d uses daemon or the login class provided in login.conf.d so this has
no impact there.
discussed with sthen@, tb@ and robert@
praying that my grep/sed skills did not break anything and still
believing in portbump :-)
if a port needs 2.x then set MODPY_VERSION=${MODPY_DEFAULT_VERSION_2}.
This commit doesn't change any versions currently used; it may be that
some ports have MODPY_DEFAULT_VERSION_2 but don't require it, those
should be cleaned up in the course of updating ports where possible.
Python module ports providing py3-* packages should still use
FLAVOR=python3 so that we don't have a mixture of dependencies some
using ${MODPY_FLAVOR} and others not.
ExaBGP is software which can inject routes with arbitrary next-hops into
your network (i.e. source IPv4/IPv6 routes using both IPv4 and IPv6 BGP
connections, either from a configuration file or third party applications),
inject flowspec routes, or pass received routes in textual form to a
third-party application.
Potential uses include:
- announce IPv4/IPv6 routes with arbitrary next-hops into your network
* injection of service IPs like AS112 announcement
* temporary route redirection (adding more specific routes with
different next-hop)
* injection of flow routes to handle DDOS
- source flow routes.
- track changes in the global routing table.
- add the received default route to an host.
- filter and/or modify routes using your own logic.
ExaBGP is for injecting or performing complex route mangling with BGP,
it is not intended to transform a server into a BGP router.
