Home
last modified time | relevance | path

Searched refs:RARP (Results 1 – 20 of 20) sorted by relevance

/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/rarpd/rarpd/
H A D0001-rarpd.8-add-man-file.patch20 +.TH RARP 8 "7 April 2000" "rarpd" "Linux Programmer's Manual"
22 +rarpd \- Reverse Address Resolution Protocol (RARP) daemon
27 +is a daemon which responds to RARP requests.
28 +RARP is used by some machines at boot time to discover their IP address.
42 +) before it decides to respond to the RARP request.
49 +Respond to ARP as well as RARP requests.
H A D0004-rarpd.init-add-new-init-file.patch37 +# Description: RARP (Reverse Address Resolution Protocol) is a protocol \
39 +# their own IP addresses from the RARP server. \
H A D0003-rarpd.c-bug-fix.patch224 - syslog(LOG_INFO, "RARP request from %s on if%d", tmpbuf, sll.sll_ifindex);
240 + syslog(LOG_INFO, "RARP request from %s on %s", tmpbuf, tmpname);
249 + syslog(LOG_INFO, "RARP response to %s %s on %s", tmpbuf,
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/rarpd/
H A Drarpd_ss981107.bb1 SUMMARY = "The RARP daemon."
2 DESCRIPTION = "RARP (Reverse Address Resolution Protocol) is a protocol which \
4 the RARP server. Some machines (e.g. SPARC boxes) use this protocol instead \
8 You should install rarpd if you want to set up a RARP server on your \
/openbmc/linux/Documentation/admin-guide/nfs/
H A Dnfsroot.rst39 DHCP, BOOTP and RARP is safe.
110 If RARP is used to determine
167 rarp: use RARP
168 both: use both BOOTP and RARP but not DHCP
199 #PROTO: <DHCP|BOOTP|RARP|MANUAL> (depending on configuration method)
357 The nfsroot code in the kernel and the RARP support have been written
/openbmc/u-boot/cmd/
H A Dnet.c80 return netboot_common(RARP, cmdtp, argc, argv); in do_rarpb()
H A DKconfig1299 Boot image via network using RARP/TFTP protocol
/openbmc/linux/net/ipv4/
H A DKconfig111 supplied on the kernel command line or by BOOTP or RARP protocols.
150 bool "IP: RARP support"
156 discovered automatically at boot time using the RARP protocol (an
158 here. Note that if you want to use RARP, a RARP server must be
/openbmc/u-boot/include/
H A Dnet.h531 BOOTP, RARP, ARP, TFTPGET, DHCP, PING, DNS, NFS, CDP, NETCONS, SNTP, enumerator
/openbmc/qemu/qapi/
H A Dnet.json906 # @initial: Initial delay (in ms) before sending the first GARP/RARP
909 # @max: Maximum delay (in ms) between GARP/RARP announcement packets
936 # Trigger generation of broadcast RARP frames to update network
/openbmc/u-boot/net/
H A Dnet.c496 case RARP: in net_loop()
1406 case RARP: in net_check_prereq()
/openbmc/linux/net/bridge/netfilter/
H A DKconfig105 This option adds the ARP match, which allows ARP and RARP header field
/openbmc/u-boot/board/freescale/m547xevb/
H A DREADME254 rarpboot- boot image via network using RARP/TFTP protocol
/openbmc/linux/Documentation/admin-guide/
H A Dkernel-parameters.rst122 IP_PNP IP DHCP, BOOTP, or RARP is enabled.
/openbmc/u-boot/board/freescale/m5373evb/
H A DREADME237 rarpboot- boot image via network using RARP/TFTP protocol
/openbmc/u-boot/board/freescale/m54455evb/
H A DREADME326 rarpboot- boot image via network using RARP/TFTP protocol
/openbmc/qemu/
H A Dhmp-commands.hx896 .help = "Trigger GARP/RARP announcements",
902 Trigger a round of GARP/RARP broadcasts; this is useful for explicitly
/openbmc/qemu/docs/interop/
H A Dvhost-user.rst1334 Ask vhost user back-end to broadcast a fake RARP to notify the migration
1342 back-end to construct and broadcast the fake RARP.
/openbmc/linux/drivers/net/ethernet/hisilicon/hns3/
H A Dhns3_enet.c124 HNS3_RX_PTYPE_ENTRY(2, 0, COMPLETE, RARP, PKT_HASH_TYPE_NONE),
/openbmc/u-boot/
H A DREADME2045 network operations like ARP, RARP, TFTP, or BOOTP
3514 rarpboot- boot image via network using RARP/TFTP protocol