diff options
| author | Donald Sharp <sharpd@cumulusnetworks.com> | 2016-09-16 20:59:35 -0400 |
|---|---|---|
| committer | Donald Sharp <sharpd@cumulusnetworks.com> | 2016-09-16 20:59:35 -0400 |
| commit | 166b75c2595b0720b91f0c34dd64ede9d899d558 (patch) | |
| tree | cb8589e46120d0c9ec2df07b47f292d817e281fc /lib/zebra.h | |
| parent | bb374626bbf21a49db0b6baef3e807c880dfbde7 (diff) | |
lib, ospfd: Remove ospf specific #define from zebra.h
zebra.h should not know or care about ospf specific code
Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
Diffstat (limited to 'lib/zebra.h')
| -rw-r--r-- | lib/zebra.h | 20 |
1 files changed, 0 insertions, 20 deletions
diff --git a/lib/zebra.h b/lib/zebra.h index 884cd76e8a..9a9a12f41f 100644 --- a/lib/zebra.h +++ b/lib/zebra.h @@ -318,26 +318,6 @@ struct in_pktinfo #endif /* - * OSPF Fragmentation / fragmented writes - * - * ospfd can support writing fragmented packets, for cases where - * kernel will not fragment IP_HDRINCL and/or multicast destined - * packets (ie TTBOMK all kernels, BSD, SunOS, Linux). However, - * SunOS, probably BSD too, clobber the user supplied IP ID and IP - * flags fields, hence user-space fragmentation will not work. - * Only Linux is known to leave IP header unmolested. - * Further, fragmentation really should be done the kernel, which already - * supports it, and which avoids nasty IP ID state problems. - * - * Fragmentation of OSPF packets can be required on networks with router - * with many many interfaces active in one area, or on networks with links - * with low MTUs. - */ -#ifdef GNU_LINUX -#define WANT_OSPF_WRITE_FRAGMENT -#endif - -/* * IP_HDRINCL / struct ip byte order * * Linux: network byte order |