summaryrefslogtreecommitdiffstats
path: root/usr.sbin/rtadvd/config.c
Commit message (Collapse)AuthorAgeFilesLines
* Cleanup of userland __P usekevlo2007-11-071-3/+3
|
* avoid heap overrunsuz2006-03-231-1/+1
| | | | | Obtained from: KAME MFC after: 1 day
* fixed a typo in commentsuz2005-11-171-1/+1
|
* added an ioctl option in kernel so that ndp/rtadvd can change some ↵suz2005-10-191-0/+30
| | | | | | | | NDP-related kernel variables based on their configurations (RFC2461 p.43 6.2.1 mandates this for IPv6 routers) Obtained from: KAME Reviewd by: ume, gnn MFC after: 2 weeks
* removed compilation warningsuz2004-10-221-0/+1
| | | | PR: bin/71624
* - supported a string notation for xxflags.ume2003-08-151-225/+279
| | | | | | | | | | | | | | | | | | | | | | - deprecate routes#N, as it is hard to keep consistency with rtprefixN. accept any number of "rtprefix", "rtrefix0", ..., "rtprefix99". - deprecate "addrs#N", as it is difficult for users to keep consistency with "addrN". accept 100 prefix info in maximum - like "addr", "addr0" ... "addr99". WARNS=2 clean on netbsd. old configuration file should work just fine. behavior change: previously, we rejected "addrN" if there's "addr", and we rejected "addr" if there is "addrN". now we accept both without problem. - when an advertised prefix configured from the kernel has been added or invalidated, notice the change in a short delay. - when invalidating a prefix, do not bark even if there is inconsistency about prefix lifetimes. - wrap more specific route info code into ROUTEINFO. Obtained from: KAME MFC after: 1 week
* malloc() may return NULL.ume2003-08-121-0/+5
| | | | | Obtained from: KAME MFC after: 1 week
* reduce #ifdef.ume2003-08-111-5/+0
| | | | MFC after: 1 week
* use strlcpy() and snprintf().ume2003-08-111-1/+1
| | | | | Obtained from: KAME MFC after: 1 week
* use int64_t instead of long long.ume2003-08-111-2/+2
| | | | | Obtained from: KAME MFC after: 1 week
* Drop MIP6 code. We don't support MIP6 yet.ume2003-08-081-88/+0
| | | | MFC after: 1 week
* KNF, correct typos and cleanup spaces.ume2003-08-081-8/+5
| | | | | Obtained from: KAME MFC after: 1 week
* __FUNCTION__ --> __func__ume2003-08-081-53/+53
| | | | | Obtained from: KAME MFC after: 1 week
* - fixed byte order of route lifetimes in route info opptions.suz2003-04-101-2/+2
| | | | | | | - corrected wording in a log message. Obtained from: KAME MFC after: 1 week
* Use assignment, not equivalence test.njl2003-04-051-1/+1
| | | | No response from: suz
* fixed invalid pointer referencesuz2003-04-021-0/+1
| | | | Obtained from: KAME
* Fix typos, mostly s/ an / a / where appropriate and a few s/an/and/schweikh2002-12-301-2/+2
| | | | Add FreeBSD Id tag where missing.
* Do not issue deprecated ioctl.ume2002-06-151-0/+8
| | | | | Obtained from: KAME MFC after: 2 weeks
* Changed the behavior when an interface-direct prefix being advertisedume2002-06-131-16/+93
| | | | | | | | | | | was removed from the kernel; Advertise the prefix with zero lifetimes rather than to remove the prefix from the prefix list to be advertised. This will help renumber a receiving host by deprecating the address derived from the old prefix. Obtained from: KAME MFC after: 2 weeks
* Skip duplicated prefixes in get_prefix().ume2002-06-011-12/+18
| | | | Obtained from: KAME
* sprintf -> snprintfume2002-06-011-17/+25
| | | | Obtained from: KAME
* Sync with recent KAME.ume2001-06-111-79/+317
| | | | | | | | | | | | | | | | | | This work was based on kame-20010528-freebsd43-snap.tgz and some critical problem after the snap was out were fixed. There are many many changes since last KAME merge. TODO: - The definitions of SADB_* in sys/net/pfkeyv2.h are still different from RFC2407/IANA assignment because of binary compatibility issue. It should be fixed under 5-CURRENT. - ip6po_m member of struct ip6_pktopts is no longer used. But, it is still there because of binary compatibility issue. It should be removed under 5-CURRENT. Reviewed by: itojun Obtained from: KAME MFC after: 3 weeks
* zero-cleared allocated prefix information when configured.ume2001-01-231-0/+2
| | | | Obtained from: KAME
* make it easier to handle $FreeBSD$ tags (amount of diff matters).itojun2001-01-211-2/+1
|
* Sync with latest KAMEkris2000-07-051-18/+125
| | | | Obtained from: KAME
* Added several socket close() which were mistakenly forgotten.shin2000-03-091-0/+1
| | | | Reported by: Hidetoshi Shimokawa <simokawa@sat.t.u-tokyo.ac.jp>
* Forbid include of soem inet6 header files from wrong placeshin2000-02-101-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | KAME put INET6 related stuff into sys/netinet6 dir, but IPv6 standard API(RFC2553) require following files to be under sys/netinet. netinet/ip6.h netinet/icmp6.h Now those header files just include each following files. netinet6/ip6.h netinet6/icmp6.h Also KAME has netinet6/in6.h for easy INET6 common defs sharing between different BSDs, but RFC2553 requires only netinet/in.h should be included from userland. So netinet/in.h also includes netinet6/in6.h inside. To keep apps portability, apps should not directly include above files from netinet6 dir. Ideally, all contents of, netinet6/ip6.h netinet6/icmp6.h netinet6/in6.h should be moved into netinet/ip6.h netinet/icmp6.h netinet/in.h but to avoid big changes in this stage, add some hack, that -Put some special macro define into those files under neitnet -Let files under netinet6 cause error if it is included from some apps, and, if the specifal macro define is not defined. (which should have been defined if files under netinet is included) -And let them print an error message which tells the correct name of the include file to be included. Also fix apps which includes invalid header files. Approved by: jkh Obtained from: KAME project
* libipsec and IPsec related apps. (and some KAME related man pages)shin2000-01-061-0/+639
Reviewed by: freebsd-arch, cvs-committers Obtained from: KAME project
OpenPOWER on IntegriCloud