1gateways(4) File Formats gateways(4)
2
6 gateways - configuration file for /usr/sbin/in.routed IPv4 network
7 routing daemon
8
10 /etc/gateways
11
14 The /etc/gateways file is used by the routing daemon, in.routed(1M).
15 When the daemon starts, it reads /etc/gateways to find such distant
16 gateways that cannot be located using only information from a routing
17 socket, to discover if some of the local gateways are passive, and to
18 obtain other parameters.
19 The /etc/gateways file consists of a series of lines, each in one of
22 the two formats shown below or consisting of parameters described
23 later. Blank lines and lines starting with "#" are treated as comments.
24 One format specifies networks:
27 net Nname[/mask] gateway Gname metric value <passive | active | external>
29 The other format specifies hosts:
33 host Hname gateway Gname metric value <passive | active | external>
35 Host hname is equivalent to net nname/32.
39 The parameters in the lines shown above are described as follows:
42 Nname or Hname
44 Name of the destination network or host. It can be a symbolic net‐
46 work name or an Internet address specified in dot notation (see
47 inet(3SOCKET)). If it is a name, then it must either be defined in
48 /etc/networks or /etc/hosts, or a naming service must have been
49 started before in.routed(1M).
50 Mask
53 An optional number between 1 and 32 indicating the netmask associ‐
55 ated with Nname.
56 Gname
59 Name or address of the gateway to which RIP responses should be
61 forwarded.
62 Value
65 The hop count to the destination host or network.
67 passive | active | external
70 One of these keywords must be present to indicate whether the gate‐
72 way should be treated as passive or active, or whether the gateway
73 is external to the scope of the RIP protocol. A passive gateway is
74 not expected to exchange routing information, while gateways marked
75 active should be willing to exchange RIP packets. See in.routed(1M)
76 for further details.
77 After turning on debugging in in.routed with the -t option, you can see
81 that lines that follow the format described above create pseudo-inter‐
82 faces. To set parameters for remote or external interfaces, use a line
83 starting with if=alias(Hname), if=remote(Hname), and so forth.
84 For backward compatibility with the previous Solaris in.routed imple‐
87 mentation, three special keyword formats are accepted. If present,
88 these forms must each be on a separate line, and must not be combined
89 on the same line with any of the keywords listed elsewhere in this doc‐
90 ument. These three forms are:
91 norip ifname Disable all RIP processing on the specified inter‐
93 face.
94 noripin ifname Disable the processing of received RIP responses on
97 the specified interface.
98 noripout ifname Disable RIP output on the specified interface.
101 Lines that start with neither net nor host must consist of one or more
105 of the following parameter settings, separated by commas or blanks:
106 if=ifname
108 Indicates that the other parameters on the line apply only to the
110 interface name ifname. If this parameter is not specified, then
111 other parameters on the line apply to all interfaces.
112 subnet=nname[/mask][,metric]
115 Advertises a route to network nname with mask mask and the supplied
117 metric (default 1). This is useful for filling holes in CIDR allo‐
118 cations. This parameter must appear by itself on a line. The net‐
119 work number must specify a full, 32-bit value, as in 192.0.2.0
120 instead of 192.0.2.
121 ripv1_mask=nname/mask1,mask2
124 Specifies that the netmask of the network of which nname/mask1 is a
126 subnet should be mask2. For example, ripv1_mask=192.0.2.16/28,27
127 marks 192.0.2.16/28 as a subnet of 192.0.2.0/27 instead of
128 192.0.2.0/24. It is better to turn on RIPv2 instead of using this
129 facility. See the description of ripv2_out, below.
130 passwd=XXX[|KeyID[start|stop]]
133 Specifies a RIPv2 cleartext password that will be included on all
135 RIPv2 responses sent, and checked on all RIPv2 responses received.
136 Any blanks, tab characters, commas, or "#", "|", or NULL characters
137 in the password must be escaped with a backslash (\). The common
138 escape sequences \n, \r, \t, \b, and \xxx have their usual mean‐
139 ings. The KeyID must be unique but is ignored for cleartext pass‐
140 words. If present, start and stop are timestamps in the form
141 year/month/day@hour:minute. They specify when the password is
142 valid. The valid password with the longest future is used on output
143 packets, unless all passwords have expired, in which case the pass‐
144 word that expired most recently is used. If no passwords are valid
145 yet, no password is output. Incoming packets can carry any password
146 that is valid, will be valid within 24 hours, or that was valid
147 within 24 hours. To protect password secrecy, the passwd settings
148 are valid only in the /etc/gateways file and only when that file is
149 readable only by UID 0.
150 md5_passwd=XXX|KeyID[start|stop]
153 Specifies a RIPv2 MD5 password. Except that a KeyID is required,
155 this keyword is similar to passwd (described above).
156 no_ag
159 Turns off aggregation of subnets in RIPv1 and RIPv2 responses.
161 no_host
164 Turns off acceptance of host routes.
166 no_super_ag
169 Turns off aggregation of networks into supernets in RIPv2
171 responses.
172 passive
175 Marks the interface not to be advertised in updates sent over other
177 interfaces, and turns off all RIP and router discovery through the
178 interface.
179 no_rip
182 Disables all RIP processing on the specified interface. If no
184 interfaces are allowed to process RIP packets, in.routed acts
185 purely as a router discovery daemon.
186 Note that turning off RIP without explicitly turning on router dis‐
188 covery advertisements with rdisc_adv or -s causes in.routed to act
189 as a client router discovery daemon, which does not advertise.
190 no_rip_mcast
193 Causes RIPv2 packets to be broadcast instead of multicast.
195 no_ripv1_in
198 Causes RIPv1 received responses to be ignored.
200 no_ripv2_in
203 Causes RIPv2 received responses to be ignored.
205 ripv2_out
208 Turns on RIPv2 output and causes RIPv2 advertisements to be multi‐
210 cast when possible.
211 ripv2
214 Equivalent to no_ripv1_in and ripv2_out. This enables RIPv2 and
216 disables RIPv1.
217 no_rdisc
220 Disables the Internet Router Discovery Protocol.
222 no_solicit
225 Disables the transmission of Router Discovery Solicitations.
227 send_solicit
230 Specifies that Router Discovery solicitations should be sent, even
232 on point-to-point links, which, by default, only listen to Router
233 Discovery messages.
234 no_rdisc_adv
237 Disables the transmission of Router Discovery Advertisements.
239 rdisc_adv
242 Specifies that Router Discovery Advertisements should be sent, even
244 on point-to-point links, which by default only listen to Router
245 Discovery messages.
246 bcast_rdisc
249 Specifies that Router Discovery packets should be broadcast instead
251 of multicast.
252 rdisc_pref=N
255 Sets the preference in Router Discovery Advertisements to the
257 optionally signed integer N. The default preference is 0. Default
258 routes with higher or less negative preferences are preferred by
259 clients.
260 rdisc_interval=N
263 Sets the nominal interval with which Router Discovery Advertise‐
265 ments are transmitted to N seconds and their lifetime to 3*N.
266 fake_default=metric
269 Has an identical effect to -F net[/mask][=metric] with the network
271 number and netmask coming from the specified interface.
272 pm_rdisc
275 Similar to fake_default. To prevent RIPv1 listeners from receiving
277 RIPv2 routes when those routes are multicast, this feature causes a
278 RIPv1 default route to be broadcast to RIPv1 listeners. Unless mod‐
279 ified with fake_default, the default route is broadcast with a met‐
280 ric of 14. That serves as a poor man's router discovery protocol.
281 trust_gateway=rtr_name[|net1/mask1|net2/mask2|...]
284 Causes RIP packets from that router and other routers named in
286 other trust_gateway keywords to be accepted, and packets from other
287 routers to be ignored. If networks are specified, then routes to
288 other networks will be ignored from that router.
289 redirect_ok
292 Causes RIP to allow ICMP Redirect messages when the system is act‐
294 ing as a router and forwarding packets. Otherwise, ICMP Redirect
295 messages are overridden.
296 rip_neighbor=x.x.x.x
299 By default, RIPv1 advertisements over point-to-point links are sent
301 to the peer's address (255.255.255.255, if none is available), and
302 RIPv2 advertisements are sent to either the RIP multicast address
303 or the peer's address if no_rip_mcast is set. This option overrides
304 those defaults and configures a specific address to use on the
305 indicated interface. This can be used to set a broadcast type
306 advertisement on a point-to-point link.
307
310 in.routed(1M), route(1M), rtquery(1M), inet(3SOCKET),
311 Internet Transport Protocols, XSIS 028112, Xerox System Integration
314 Standard
315SunOS 5.11 20 May 2009 gateways(4)