HP-UX Reference (11i v1 00/12) - 4 File Formats (vol 8)
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man4/!!!intro.4
________________________________________________________________
___ ___
g
gated.conf(4) gated.conf(4)
The interface physical addresses are useful for IS-IS, for IP protocols, they are not currently used, but may
be in the future.
Reading kernel variables
At startup, GateD reads some special variables out of the kernel. This is usually done with the nlist (or
kvm_nlist) system call, but some systems use different methods.
The variables read include the status of UDP checksum creation and generation, IP forwarding and kernel
version (for informational purposes). On systems where the routing table is read directly from kernel
memory, the root of the hash table or radix tree routing table is read. On systems where interface physical
addresses are not supplied by other means, the root of the interface list is read.
Special route flags
The later BSD based kernel support the special route flags described here.
RTF_REJECT
Instead of forwarding a packet like a normal route, routes with RTF_REJECT cause packets to be
dropped and unreachable messages to be sent to the packet originators. This flag is only valid
on routes pointing at the loopback interface.
RTF_BLACKHOLE
Like the RTF_REJECT flag, routes with RTF_BLACKHOLE cause packets to be dropped, but
unreachable messages are not sent. This flag is only valid on routes pointing at the loopback
interface.
RTF_STATIC
When GateD starts, it reads all the routes currently in the kernel forwarding table. Besides
interface routes, it usually marks everything else as a remnant from a previous run of GateD
and deletes it after a few minutes. This means that routes added with the route command will
not be retained after GateD has started.
To fix this the RTF_STATIC flag was added. When the route command is used to install a route
that is not an interface route it sets the RTF_STATIC flag. This signals to GateD that said route
was added by the systems administrator and should be retained.
Kernel Configuration
kernel {
options
[ nochange ]
[ noflushatexit ]
[ remnantholdtime time ]
;
routes number ;
flash
[ limit number ]
[ type interface | interior | all ]
;
background
[ limit number ]
[ priority flash | higher | lower ]
;
traceoptions trace_options ;
};
options option_list
Configure kernel options. The valid options are:
nochange
On systems supporting the routing socket this insures that changes operations will
not be performed, only deletes and adds. This is useful on early versions of the routing
socket code where the change operation was broken.
noflushatexit
During normal shutdown processing GateD deletes all routes from the kernel forward-
ing table that do not have a retain indication. The noflushatexit option prevents
route deletions at shutdown. Instead, routes are changed and added to make sure that
HP-UX Release 11i: December 2000 − 38 − Section 4−−109
___
___