summaryrefslogtreecommitdiff
path: root/sys/netinet6/ip6_forward.c
AgeCommit message (Collapse)Author
2002-06-09whitespace cleanupJun-ichiro itojun Hagino
2002-06-08sync with latest KAME in6_ifaddr/prefix/default router manipulation.Jun-ichiro itojun Hagino
behavior changes: - two iocts used by ndp(8) are now obsolete (backward compat provided). use sysctl path instead. - lo0 does not get ::1 automatically. it will get ::1 when lo0 comes up.
2002-06-07'fall through' is not a valid LINT keyword.Jun-ichiro itojun Hagino
2002-05-29attach nd_ifinfo structure to if_afdata.Jun-ichiro itojun Hagino
split IPv6 MTU (advertised by RA) from real link MTU. sync with kame
2001-12-07whitespace/comment sync with kameJun-ichiro itojun Hagino
2001-11-30unifdef OLDIP6OUTPUTJun-ichiro itojun Hagino
2001-11-26add fastroute options similar to what is found in ipfjasoni
ok dhartmei@, frantzen@
2001-09-29filter forwarded ipv6 packets; checked by itojun, tested byjasoni
mcbride@countersiege.com
2001-07-18sync with draft-ietf-ipngwg-p2p-pingpong-00.txt. apply special behaviorJun-ichiro itojun Hagino
only if ip6_dst is "neighbor" within p2p prefix. sync with kame
2001-06-22do not forward packet back into point-to-point link, if the packet hasJun-ichiro itojun Hagino
destination address that matches the p2p interface. this would lead us to pingpong (= chews bandwidth, can be attacked from remote).
2001-06-09No need for net/net_osdep.hAngelos D. Keromytis
2001-03-30enable FAKE_LOOPBACK_IF case by default.Jun-ichiro itojun Hagino
now traffic on loopback interface will be presented to bpf as normal wire format packet (without KAME scopeid in s6_addr16[1]). fix KAME PR 250 (host mistakenly accepts packets to fe80::x%lo0). sync with kame.
2001-02-16get rid of #ifdef IPV6FIREWALL (never used, will never be used)Jun-ichiro itojun Hagino
2001-02-16sync whitespace/comment with kame. to help merge tasksJun-ichiro itojun Hagino
2001-02-16kill register declarations. to sync with kame better.Jun-ichiro itojun Hagino
2000-07-27do not forward packet with :: in the source.Jun-ichiro itojun Hagino
this is not in the spec - we had rough consensus on it in ipngwg, spec will get updated to include this behavior.
2000-06-30suppress too noisy warning on forward-over-loopback case. from kameJun-ichiro itojun Hagino
2000-06-03do not bark even if forwarding to loopback, since it is commonJun-ichiro itojun Hagino
to route packet to be rejected/dropped to loopback. (sync with kame)
2000-05-19correct "telnet fe80::1%lo0".Jun-ichiro itojun Hagino
2000-05-19never forward packet with link-local address.Jun-ichiro itojun Hagino
experimental support for new loopback packet handling (with FAKE_LOOPBACK_IF, rcvif will be set to real outgoing interface, not the loopback, to honor scope) sync with kame.
2000-02-28bring in recent KAME changes (only important and stable ones, as usual).Jun-ichiro itojun Hagino
- remove net.inet6.ip6.nd6_proxyall. introduce proxy NDP code works just like "arp -s". - revise source address selection. be more careful about use of yet-to-be-valid addresses as source. - as router, transmit ICMP6_DST_UNREACH_BEYONDSCOPE against out-of-scope packet forwarding attempt. - path MTU discovery takes care of routing header properly. - be more strict about mbuf chain parsing. - nuke xxCTL_VARS #define, they are for BSDI. - disable SIOCSIFDSTADDR_IN6/SIOCSIFNETMASK_IN6 ioctl, they do not fit IPv6 model where multiple address on interface is normal. (kernel side supports them for a while for backward compat, the support will be nuked shortly) - introduce "default outgoing interface" (for spec conformance in very rare case)
2000-02-07fix include file path related to ip6.Jun-ichiro itojun Hagino
1999-12-10Remove remaining unnecessary ifdefs (itojun will hate me for this :-)Angelos D. Keromytis
1999-12-08bring in KAME IPv6 code, dated 19991208.Jun-ichiro itojun Hagino
replaces NRL IPv6 layer. reuses NRL pcb layer. no IPsec-on-v6 support. see sys/netinet6/{TODO,IMPLEMENTATION} for more details. GENERIC configuration should work fine as before. GENERIC.v6 works fine as well, but you'll need KAME userland tools to play with IPv6 (will be bringed into soon).