Go to file
Ameya Dharkar 9da60d0a19 Zebra: Build nelink message for RMAC updates
- Function "zfpm_netlink_encode_mac()" builds a netlink message for RMAC updates.

- To build a netlink message for RMAC updates, we use "ndmsg" in rtlink.

- FPM Message structure is:
  FPM header -> nlmsg header -> ndmsg fields -> ndmsg attributes

- Netlink message will look like:
  {'ndm_type': 0, 'family': 7, '__pad': (), 'header': {'flags': 1281,
   'length':64, 'type': 28, 'pid': 0, 'sequence_number': 0}, 'state': 2,
   'flags': 22, 'attrs': [('NDA_LLADDR', 'b2:66:eb:b9:5b:d3'),
   ('NDA_DST', '10.100.0.2'), ('NDA_MASTER', 11), ('NDA_VNI', 1000)],
   'ifindex': 18}

- Message details:
  nlmsghdr.nlmsg_type = RTM_NEWNEIGH(28) or RTM_DELNEIGH(29)
  nlmsghdr.nlmsg_flags = NLM_F_REQUEST | NLM_F_CREATE | NLM_F_REPLACE for "add" ,
  			 "NLM_F_REQUEST" for delete.
  ndmsg.ndm_family = AF_BRIDGE
  ndmsg.ndm_ifindex = vxlan_if (ifindex)
  ndmsg.ndm_state = NUD_REACHABLE
  ndmsg.ndm_flags |= NTF_SELF | NTF_MASTER | NTF_EXT_LEARNED
  Attribute "NDA_LLADDR" for MAC address
  Attribute "NDA_DST" for remote vtep ip
  Attribute "NDA_MASTER" for bridge interface ifindex.
  Attribute "NDA_VNI" for VNI id.

Signed-off-by: Ameya Dharkar <adharkar@vmware.com>
2019-06-17 12:05:38 -07:00
.github
alpine
babeld
bfdd
bgpd Merge pull request #4505 from ton31337/feature/autocomplete_bgp_peer-group 2019-06-17 13:53:48 -04:00
debian
doc Merge pull request #4505 from ton31337/feature/autocomplete_bgp_peer-group 2019-06-17 13:53:48 -04:00
docker docker: Docker binary image on Debian Buster 2019-06-11 16:58:21 -04:00
eigrpd eigrpd: Fix endianness issue in packets 2019-06-14 13:04:07 +02:00
fpm
gdb
grpc
include
isisd lib: make "%Ld" work for int64_t 2019-06-12 19:35:43 +02:00
ldpd ldpd: Fix shutdown 2019-06-11 14:55:10 +03:00
lib lib: Prevent infinite loop in fd handling (#4516) 2019-06-14 23:48:36 +02:00
m4
nhrpd
ospf6d
ospfclient
ospfd
pbrd zebra,pbrd: Update pbrd to handle NHT properly 2019-06-10 14:36:30 -04:00
pimd lib/clippy: error out on unsupported bits 2019-06-12 19:22:59 +02:00
pkgsrc
python lib/clippy: expand some macros 2019-06-12 19:23:00 +02:00
qpb
redhat
ripd
ripngd
sharpd *: fix some dumb printf format warnings 2019-06-11 13:34:57 +02:00
snapcraft
solaris
staticd
tests eliminate snprintf from AF_INET/AF_INET6 prefix2str, add prefix2str test (#4521) 2019-06-14 21:48:34 +02:00
tools tools: add vim snippet 2019-06-12 19:35:43 +02:00
vrrpd
vtysh
watchfrr *: fix some dumb printf format warnings 2019-06-11 13:34:57 +02:00
yang
zebra Zebra: Build nelink message for RMAC updates 2019-06-17 12:05:38 -07:00
.clang-format
.dir-locals.el
.dockerignore
.gitignore
bootstrap.sh
buildtest.sh
changelog-auto.in
config.version.in
configure.ac Merge pull request #4500 from opensourcerouting/clippy-improve 2019-06-13 15:06:24 -04:00
COPYING
COPYING-LGPLv2.1
defaults.h
Makefile.am build: improve clippy options 2019-06-12 19:22:59 +02:00
README.md
stamp-h.in

FRRouting

FRR is free software that implements and manages various IPv4 and IPv6 routing protocols. It runs on nearly all distributions of Linux and BSD as well as Solaris and supports all modern CPU architectures.

FRR currently supports the following protocols:

  • BGP
  • OSPFv2
  • OSPFv3
  • RIPv1
  • RIPv2
  • RIPng
  • IS-IS
  • PIM-SM/MSDP
  • LDP
  • BFD
  • Babel
  • PBR
  • OpenFabric
  • EIGRP (alpha)
  • NHRP (alpha)

Installation & Use

Packages are available for various distributions on our releases page.

Snaps are also available here.

Instructions on building and installing from source for supported platforms may be found here.

Once installed, please refer to the user guide for instructions on use.

Community

The FRRouting email list server is located here and offers the following public lists:

Topic List
Development dev@lists.frrouting.org
Users & Operators frog@lists.frrouting.org
Announcements announce@lists.frrouting.org

For chat, we currently use Slack. You can join by clicking the "Slack" link under the Participate section of our website.

Contributing

FRR maintains developer's documentation which contains the project workflow and expectations for contributors. Some technical documentation on project internals is also available.

We welcome and appreciate all contributions, no matter how small!

Security

To report security issues, please use our security mailing list:

security [at] lists.frrouting.org