summaryrefslogtreecommitdiffstats
path: root/usr.sbin/ppp/ipv6cp.c
Commit message (Collapse)AuthorAgeFilesLines
* Ethernet vlan(4) interfaces have valid Ethernet link layer addresses butjhb2010-08-061-0/+1
| | | | | | | | use a different interface type (IFT_L2VLAN vs IFT_ETHER). Treat IFT_L2VLAN interfaces like IFT_ETHER interfaces when handling link layer addresses. Reviewed by: syrinx (bsnmpd) MFC after: 1 week
* Conditionally add the interface name and address if availablebz2009-04-201-1/+1
| | | | | | | | | | so that a ppp running in `receiver' (server) mode can properly update routes, for example to update the MTU. Submitted by: loos.br gmail.com (Luiz Otavio O Souza) PR: bin/130159 PR: kern/125079, kern/122068, bin/126892 MFC after: 3 days
* Add a radius_Flush() function that waits for the response (or timeout) tobrian2005-01-271-0/+1
| | | | | | | | | | | | | | any pending RADIUS transaction. Use this before sending RAD_STOP RADIUS messages so that we definitely ``stop'' the session. It was discovered that sometimes when the link timed out, we got lucky enough to have an un-ACK'd RADIUS accounting transaction in progress, resulting in the RAD_STOP message failing to send. Original report found on: A russion news group Text translated by: glebius Tested by: Alexey Popov llp at iteranet dot com MFC after: 7 days
* Make ppp WARNS=5 cleanbrian2004-09-051-5/+7
|
* Do RADIUS accounting on IPV6CP.ume2003-06-191-2/+41
| | | | MFC after: 1 week
* Install routes specified by Framed-IPv6-Route. Since the formatume2003-06-191-1/+1
| | | | | | of Framed-IPv6-Route is user defined, it follows Framed-IP-route. MFC after: 1 week
* MYADDR6 in ppp.link{up,down} should match even when IPCP is enabled.ume2003-06-161-24/+20
| | | | MFC after: 1 week
* Add missing header for system_Select() prototypekris2003-06-121-0/+1
|
* Set link-local address of tun interface with prefixlen = 64ume2003-04-041-1/+1
| | | | | | | | | instead of 128. It makes RA happy. Reported by: rafa@dif.um.es, SHIRASAKI Yasuhiro <yasuhiro@nttv6.jp> Reviewed by: SHIRASAKI Yasuhiro <yasuhiro@nttv6.jp> MFC after: 1 week
* Once ppp session is over, the route to ff02::tun0/32 wasume2003-03-251-1/+12
| | | | | deleted, and never came back. Now, the route to ff02::tun0/32 is installed at the end of IPV6CP negitiaton.
* Since ppp.link{up,down} is invoked at the end of IPCP negotiation, ifume2003-03-251-2/+32
| | | | | | we need ppp.link{up,down}, we couldn't disable IPCP. Now, if IPCP is disabled, ppp.link{up,down} is invoked at the end of IPV6CP negotiation.
* - made ppp compliant to RFC 2472 (based on a patch from anotherbrian2002-08-291-47/+147
| | | | | | | | | contributor) - support ipv6cpretry and ipv6cpretries, which are IPv6 versions of ipcpretry and ipcpretries. - improve handling of IPv6 link-local addresses Submitted by: JINMEI Tatuya <jinmei@isl.rdc.toshiba.co.jp>
* Include the correct file (stdarg.h) and use va_list rather than _BSD_VA_LIST_brian2002-08-271-0/+1
| | | | Suggested by: mike
* Make the way FSM options are processed easier to read by using structuresbrian2002-04-161-49/+35
| | | | | | | | | | | instead of u_char *. The changes are cosmetic except: RecvConfigAck() now displays the options that are being ACK'd Huge (bogus) options sent from the peer won't cause an infinite loop SendIdent and ReceiveIdent are displayed consistenlty with other FSM data LCP AUTHPROTO options that aren't understood are NAK'd, not REJ'd
* Add a missing % in a format string.brian2001-08-191-1/+1
| | | | | Not spotted by: FreeBSD's gcc version 2.95.3 20010315 (release) Spotted by: OpenBSD's gcc version 2.95.3 20010125 (prerelease)
* Back out the previous fix to deal with kernels that don't support IPv6,brian2001-08-181-11/+12
| | | | | | | | | | | | | | | and implement a far more subtle and correct fix. The reason behind the infinite loop was that ppp was trying to make up initial IPv6 numbers and wasn't giving up when it failed unexpectedly to assign the addresses it just fabricated to it's interface (thinking that the reason was because another interface was using the same address). It now attempts this up to 100 times before just failing and trying to muddle along (in reality, this should never happen more than a couple of times unless our random number generator doesn't work). Also, when IPv6 is not available, don't even try to assign the IPv6 interface address in the first place...
* Run correctly on a machine built without AF_INET6 supportbrian2001-08-181-1/+7
|
* Specify the gateway address when updating the MTU and send/recv pipebrian2001-08-161-3/+13
| | | | | | | | | | sizes on a route. IMHO this shouldn't be necessary (the destination & mask/prefixlen should be enough), but without it, the default route update under OpenBSD will fail. Thanks to: Russell T Hunt <alaric@MIT.EDU>
* o Add ipv6 support, abstracting most NCP addresses into opaquebrian2001-08-141-0/+601
structures (well, they're treated as opaque). It's now possible to manage IPv6 interface addresses and routing table entries and to filter IPV6 traffic whether encapsulated or not. IPV6CP support is crude for now, and hasn't been tested against any other implementations. RADIUS and IPv6 are independent of eachother for now. ppp.linkup/ppp.linkdown aren't currently used by IPV6CP o Understand all protocols(5) in filter rules rather than only a select few. o Allow a mask specification for the ``delete'' command. It's now possible to specifically delete one of two conflicting routes. o When creating and deleting proxy arp entries, do it for all IPv4 interface addresses rather than doing it just for the ``current'' peer address. o When iface-alias isn't in effect, don't blow away manually (via ``iface add'') added interface addresses. o When listening on a tcp server (diagnostic) socket, bind so that a tcp46 socket is created -- allowing both IPv4 and IPv6 connections. o When displaying ICMP traffic, don't display the icmp type twice. When display traffic, display at least some information about unrecognised traffic. o Bump version Inspired after filtering work by: Makoto MATSUSHITA <matusita@jp.FreeBSD.org>
OpenPOWER on IntegriCloud