GNU Zebra is a free software (distributed under GNU Generic Public
License) which manages TCP/IP based routing protocols.
It supports BGP-4 protocol as described in RFC1771 (A Border Gateway
Protocol 4) and RIPv1, RIPv2 and OSPFv2.
Zebra uses multithread technology under multithread supported UNIX
kernels. However it can be run under not-multithread supported
UNIX kernels.
Zebra is intended to be used as a Route Server and a Route Reflector.
Zebra is not a toolkit, it provides full routing power under a new
architecture.
WWW: http://www.zebra.org/
===> The following configuration options are available for zebra-0.95a_10:
IPV6=on: IPv6 protocol support
PAM=off: PAM authentication for vtysh
OSPFNSSA=off: undergoing NSSA feature
SNMP=off: SNMP network protocol support
TCPZEBRA=off: TCP/IP socket connection
BGPD=on: BGPD support
OSPF6D=on: OSPF6D support
OSPFD=on: OSPFD support
RIPD=on: RIPD support
RIPNGD=on: RIPNGD support
VTYSH=on: VTYSH support
===> Use 'make config' to modify these settings
To run zebra you should add in your /etc/rc.conf these lines:
defaultrouter="NO"
router_enable="YES"
router="/usr/local/sbin/zebractl"
router_flags="start"
cleanup: Remove expired ports:
2021-10-31 devel/sdl_sge: Upstream no longer maintained
2021-12-31 net/appkonference: Outdated, depends on unsupported version of
net/asterisk
2021-12-31 dns/bind911: End of life, please migrate to a newer version of BIND9
2021-12-31 net/zebra: Abandoned upstream, last release in 2005. Consider
migrating to net/frr7 or net/bird2
2021-12-31 audio/osalp: Abandoned upstream, listed as beta and no new release
since 2008
2021-12-31 games/stransball2: Depends on expired devel/sdl_sge
2021-12-31 devel/rubygem-ruby-sdl-ffi: Depends on expired devel/sdl_sge
2021-12-31 devel/rubygem-rubygame: Depends on expired devel/sdl_sge
2021-12-31 devel/ruby-sdl: Depends on expired devel/sdl_sge
2021-12-31 games/magicmaze: Depends on expired devel/sdl_sge
2021-12-31 games/trophy: Depends on expired devel/clanlib1
2021-12-31 devel/clanlib1: Older than expired and removed devel/clanlib
2021-12-31 www/py-django31: Upgrade to Django 3.2+. Mainstream support ended
(April 6, 2021). Extended support ends December 2021. See
https://www.djangoproject.com/download/
(Only the first 15 lines of the commit message are shown above )
*/*: Remove redundant '-[0-9]*' from CONFLICTS
The conflict checks compare the patterns first against the package
names without version (as reported by "pkg query "%n"), then - if
there was no match - agsinst the full package names including the
version (as reported by "pkg query "%n-%v").
Many CONFLICTS definitions used patterns like "bash-[0-9]*" to filter
for the bash package in any version. But that pattern is functionally
identical with just "bash".
Approved by: portmgr (blanket)
net/zebra: Update MASTER_SITES, deprecate and set expiration date to 2021-12-31
Remove dead mirrors, Zebra's last release was back in 2005 and is
abandoned upstream
Reference: https://www.gnu.org/software/zebra/
Approved by: bdrewery (port maintainer), arrowd (mentor)
Differential Revision: https://reviews.freebsd.org/D32469
Install texinfo files (GNU info) into ${PREFIX}/share/info
After a discussion on the mailing list on moving manpages to
${PREFIX}/share/man for consistency with base where it is
installed in usr/share/man, it appeared the same should happen
to GNU info files which were installed under share in base and
not in ports.
Now texinfo is not in base on any of the supported version of FreeBSD
it is possible to proceed to this move and it is easier to do than
the manpage change.
Other benefit than consistency are less patching: all build tools but
cmake are expecting info files to be under share/info and cmake (patched here)
was having an exception for BSD so the patch makes FreeBSD case less
specific for them
Bump revision of all impacted ports
PR: 232907
exp-run by: antoine
Differential Revision: https://reviews.freebsd.org/D17816
- Fix dependency on net-snmp; net-snmp4 was removed in
2010 in r262994
- Remove redundant :install target on the snmp LIB_DEPENDS
- Remove ABI version from LIB_DEPENDS for snmp
- Use arguments for different zebra services. Default is "-d"
- Update to use OPTIONSNG
- Rename LIBPAM to PAM (shared description)
- Drop my maintainership
PR: ports/170678
Submitted by: jgh
Feature safe: yes
Increase PORTREVISION to silence port upgrading tools if
zebra-devel port was installed (it had PORTREVISION 2,
but less functionality).
Approved by: portmgr (marcus)
Properly zero-out struct ifreq before passing it to the SIOCSIFFLAGS
ioctl(2), so that it doesn't occasionally trigger promisc mode on interface.
Reported/tested by: Vladimir B. Grebenschikov <vova@sw.ru>
update to new zebra 0.91a - some workarounds concerning installation of zebra
info files since sources doesn't contain all info files... - modified
zebractl script to check, if zebra.conf exists, which is needed for every
routing protocol, error message and exit if not found. From the author:
"0.91 is basically a bugfix release. All of IPv6 codes are based upon new RIB
codes" Bugfixes and features see ChangeLog file.
- remove redirection to /dev/null for zebra and routing daemons you should
be able to see error messages if there are any Since daemons are started
using -d options, you should normally see no output... - bumped
PORTREVISION, since its a major win being able to see error messages if
there are any
- start zebra processes with -d option to make sure that one process starts
after the other to prevent core dump. This fixes bgp coredump for Knarf -
set PORTREVISION
unbreak port. note: I tried to build a portname applying to the porters
handbook conventions. Unfortunately it doesn't have a good example for version
numbers like 0.90a. 0.90-alpha would have to be change to 0.90.a. So I
thought it should be done this way for 0.90.a as well. But then you have to
set DISTFILES and WRKSRC (the latter I forgot in a last minute change, sorry,
which broke the port). And even if you get the port running again, then
portlint tells you pretty things how to do it better ... All in all. It
would be fine to add an example in porters handbook for cases like 0.90a,
which should *not* be changed to 0.90.a !
- update to 0.90a - update md5 checksum - make PORTVERSION porters handbook
compliant, had to add DISTFILES so source is still fetchable. Maybe I
misunderstood the description how to transpose version numbers, maybe the
description should be changed, that 0.90a should also be allowed than to use
0.90.a - remove PORTREVISION, since PORTVERSION changed
- configure: fixed logic in if-clause, so that dialog is only called if
BATCH is not defined. Portrevision doesn't need to be bumped, since exactly
this enables/unbreaks package building...
upgrade to new zebra version 0.90 - removed PORTREVISION (new version) - new
configure script: dialog menue allows you to set different zebra compile
time options (if ! BATCH), currently supported: --with-libpam =
enable PAM authentication for vtysh --enable-nssa = enable OSPF NSSA
--enable-snmp = enable SNMP support - please note: port compiles
fine when all options are set, but functionality has not been tested by me.
- silence portlint, trim pkg-comment to <=70 columns - remove unneeded patch
patch, 0.90 now contains fix for memory leak - cosmetic: add patch for
Makefile.in (don't link with -g) - portlint: o.k.
Fix vty memory leak Patch in PR contains typo, got clean patch from zebra anon
cvs server Wrote e-mail to security officer and freebsd-audit to ask for a)
review b) what to do next (FreeBSD Ports Security Advisory?...) concerning
a) the author of zebra already ok'd the patch. converning b) waiting for SO or
fbsd-auditers to respond
zebra-0.89 has been replaced by zebra-0.89a. fix: multiple route entry for
same type of route, which caused problem for BGP implicit withdraw. If
you are using zebra-0.89 and have a problem with multiple BGP routes in zebra
for one prefix, please update.
Rename PLIST.v6 to pkg-plist.v6. (I can't think of a reason why there are two
commands "cat >" and "cat >>" when they both take one argument so I combined
them together so they can do what the "cat" command's name came from.)
