/titanic_44/usr/src/cmd/cmd-inet/sbin/dhcpagent/ |
H A D | dhcpagent.dfl | 38 # An interface name alone specifies IPv4 DHCP. For DHCPv6, append ".v6". 46 # By default, when the DHCP agent is sent a SIGTERM (typically when 48 # than released. Dropping an address does not notify the DHCP server 50 # for subsequent use by the same client. If DHCP is later restarted 57 # the link status transitions from down to up, DHCP will ask the server 63 # received, the DHCP server is notified that the address is available 65 # DHCP receives SIGTHAW or a link-up event, DHCP will attempt to verify 72 # By default, the DHCP agent waits 3 seconds to collect OFFER 82 # By default, the DHCP agent does not send out a client identifier 83 # (and hence, the chaddr field is used by the DHCP server as the [all …]
|
H A D | README | 23 Architectural Overview for the DHCP agent 30 The Solaris DHCP agent (dhcpagent) is a DHCP client implementation 41 When a DHCP agent implementation is only required to control a single 43 state-machine, as shown in RFC2131. However, when a DHCP agent is 48 Given that DHCP's behavior can be expressed concisely as a state 58 The DHCP agent consists of roughly 30 source files, most with a 91 DHCP agent implementation. Note that there is of course much more 123 which must be maintained for each DHCP-controlled interface (such as a 151 the maximum MTU) and its connections to DHCP-related state (the 161 For IPv4, each DHCP state machine manages a single IP address and [all …]
|
H A D | README.v6 | 47 - RFCs 2131 and 2132: IPv4 DHCP 52 - dhcpagent(1M): Solaris DHCP client 53 - dhcpinfo(1): Solaris DHCP parameter utility 88 interface under DHCP's control. It also represents the shared state 89 with the DHCP server that granted the address, the address itself, 93 that are under DHCP control. IP interfaces not under DHCP control 103 timers. The name of the logical IP interface under DHCP's control 128 dhcp_pkt; "packet.h"). PKT is just the RFC 2131 DHCP packet 153 DHCPv6 naturally has some commonality with IPv4 DHCP, but also has 156 Unlike IPv4 DHCP, DHCPv6 relies on link-local IP addresses to do its [all …]
|
/titanic_44/usr/src/lib/libdhcputil/ |
H A D | README.inittab | 32 Currently, each DHCP-related utility that needs to handle DHCP options 37 Originally, when only the DHCP server needed to be concerned with DHCP 38 options, not having a standard API for managing and parsing DHCP 39 options was understandable. Now, with four consumers of DHCP options 44 places where DHCP option information is stored (dhcptags(4), 49 single configuration for applications to receive their DHCP option 50 knowledge from and general routines for encoding and decoding DHCP 57 some degree) the semantics of DHCP options. It is primarily a 60 new DHCP options, but this should be rare. 114 category (i.e., defined by the DHCP standard), and is option code [all …]
|
/titanic_44/usr/src/cmd/cmd-inet/etc/dhcp/ |
H A D | inittab | 27 # This file provides information about all supported DHCP options, for 28 # use by DHCP-related programs. This file should only be modified to 31 # If you need to configure the Solaris DHCP server to support the vendor 121 # DHCP packet fields. Code field is byte offset into DHCP packet.
|
/titanic_44/usr/src/cmd/cmd-inet/lib/nwamd/ |
H A D | README | 130 connect, DHCP requests etc). 135 DHCP requests, WLAN scans etc that cannot hold up event processing in 273 DHCP response. This auxiliary state can then also be used diagnostically by 320 is activated above such a link, and that NCU uses DHCP, a timeout 331 NWAM_AUX_STATE_IF_DHCP_TIMED_OUT DHCP timed out on interface 334 of a mix of static and DHCP-acquired addresses. This means that 345 edge case here is that when DHCP information comes 348 is that if we have a static/DHCP mix, and if we rely on 351 has been assigned and before the DHCP information has 354 check if the (logical) interface associated is DHCP, and
|
H A D | ipf.conf.dfl | 34 # Allow DHCP: in to client port, out to server port
|
H A D | llp.c | 186 static const char DHCP[] = "dhcp"; in parse_llp_config() local 249 } else if (strcasecmp(srcstr, DHCP) == 0) { in parse_llp_config()
|
H A D | ipf6.conf.dfl | 34 # Allow DHCP: in to client port, out to server port
|
/titanic_44/usr/src/cmd/cmd-inet/etc/ |
H A D | services | 58 bootps 67/udp # BOOTP/DHCP server 59 bootpc 68/udp # BOOTP/DHCP client
|
H A D | ipsecinit.sample | 78 # invocation. (E.g. the DNS server is on-subnet, or DHCP
|
/titanic_44/usr/src/lib/libsecdb/ |
H A D | exec_attr.txt | 42 DHCP Management:suser:cmd:::/usr/lib/inet/dhcp/svcadm/dhcpconfig:uid=0 43 DHCP Management:suser:cmd:::/usr/lib/inet/dhcp/svcadm/dhtadm:uid=0 44 DHCP Management:suser:cmd:::/usr/lib/inet/dhcp/svcadm/pntadm:uid=0
|
H A D | prof_attr.txt | 41 DHCP Management:::Manage the DHCP service:auths=solaris.dhcpmgr.*;help=RtDHCPMngmnt.html
|
H A D | auth_attr.txt | 54 solaris.dhcpmgr.:::DHCP Service Management::help=DhcpmgrHeader.html 55 solaris.dhcpmgr.write:::Modify DHCP Service Configuration::help=DhcpmgrWrite.html
|
/titanic_44/usr/src/grub/grub-0.97/docs/ |
H A D | grub.info-2 | 57 a configuration file in a BOOTP/DHCP server. For now, GRUB uses the tag 77 See the manual of your BOOTP/DHCP server for more information. The 712 * dhcp:: Initialize a network device via DHCP 831 Initialize a network device via the "DHCP" protocol. Currently, 837 fetch and load a configuration file specified by your DHCP server 1145 Override a TFTP server address returned by a BOOTP/DHCP/RARP
|
H A D | grub.texi | 1456 TFTP is supported at the moment. The latter is either BOOTP, DHCP or a 1465 (@pxref{dhcp}) or @command{rarp} (@pxref{rarp}) for BOOTP, DHCP or RARP, 1526 configuration file in a BOOTP/DHCP server. For now, GRUB uses the tag 1551 the BOOTP/DHCP server. This can be used to generate answers specific 1554 See the manual of your BOOTP/DHCP server for more information. The 2195 * dhcp:: Initialize a network device via DHCP 2336 Initialize a network device via the @dfn{DHCP} protocol. Currently, 2342 fetch and load a configuration file specified by your DHCP server 2638 Override a TFTP server address returned by a BOOTP/DHCP/RARP server. The
|
H A D | grub.info | 1295 TFTP is supported at the moment. The latter is either BOOTP, DHCP or a 1303 (*note rarp::) for BOOTP, DHCP or RARP, respectively. Each command will 1363 a configuration file in a BOOTP/DHCP server. For now, GRUB uses the tag 1383 See the manual of your BOOTP/DHCP server for more information. The 2016 * dhcp:: Initialize a network device via DHCP 2135 Initialize a network device via the "DHCP" protocol. Currently, 2141 fetch and load a configuration file specified by your DHCP server 2449 Override a TFTP server address returned by a BOOTP/DHCP/RARP
|
H A D | grub.info-1 | 1295 only TFTP is supported at the moment. The latter is either BOOTP, DHCP 1304 (*note rarp::) for BOOTP, DHCP or RARP, respectively. Each command will
|
/titanic_44/exception_lists/ |
H A D | packaging | 66 # The following files are used by the DHCP service, the 67 # standalone's DHCP implementation, and the kernel (nfs_dlboot). 220 # and libdhcputil for the benefit of DHCP-related networking commands such
|
/titanic_44/usr/src/cmd/cmd-inet/usr.lib/wpad/ |
H A D | README | 681 should be started before DHCP client. 710 when a static IP address is configured or when DHCP client is
|
/titanic_44/usr/src/grub/grub-0.97/ |
H A D | NEWS | 242 BOOTP server, a DHCP server or a RARP server.
|
H A D | ChangeLog | 436 DHCP code. 1620 * netboot/etherboot.h (ETH_MAX_MTU): Because some DHCP/BOOTP
|