# Chapter 2 - GateD Trouble Shooting

## 2.1 Getting HELP!

If you need assistance or have any questions, don't bang your head against the wall. Post to the mailing list. There are many people with GateD experience who may be able to take a moment to help.

When reporting a problem with GateD, several pieces of information will greatly assist in debugging:

1. GateD version (R4_0Beta_0).

2. What system it is running on, hardware, software and versions.

3. Your configuration file.

4. The interface configuration.

It helps to provide this, as both the output of `netstat -in` (`netstat -i -n` on BSD 4.2based systems) and an `ifconfig` for each interface (`ifconfig -a` will work for some versions of SunOS 4 and later.

5. The routing table.

The Routing table may be listed by using i.e. `netstat -rn` (`netstat -r -n`on BSD 4.2based systems)

6. GateD's idea of the Routing table.

To get this, start GateD with `-t` (which is short for `-tgeneral`). Setting tracing options in the config file will not get all of this information because GateD scans the interfaces before parsing the config file. So you must specify tracing on the command line.

7. Dump GateD Routing Table.

To get this start GateD and do a "gdc dump" using the gdc utility gated provides.

8. Trace output of your problem.

If it is a RIP problem, turn on RIP tracing. If it is an EGP problem, turn on EGP tracing.

Send Bug reports to either:

- Merit GateD Staff at

or

- gated-people mail list

The GateD family of users and developers provides a large amount of information to newcomers. We are working on lists of Frequent Asked questions for new users. Please check the GateD Home page FAQ documentation.

Last updated April 27, 1997

gated@gated.merit.edu