Logging and Shell Access
By
Daniel Schuhmann,
published on February 9, 2006
Source: Tom's Guide US | Keywords: ipcop, linux, firewall, ipcop
Source: Tom's Guide US | Keywords: ipcop, linux, firewall, ipcop
Contents
- 1. Introduction
- 2. How Many NICs?
- 3. Installing the System
- 4. LAN Interface Setup
- 5. Configuring the WAN and DHCP server
- 6. Configuring the WAN and DHCP server, C more
- 7. Installation Wrap-up
- 8. IPCop Feature Tour
- 9. Features - DHCP Server
- 10. Port Forwarding and Dynamic DNS
- 11. Proxy Server
- 12. Monitoring Features
- 13. Logging and Shell Access
- 14. Closing Thoughts
13. Logging and Shell Access
Although log files are much more boring than the interactive status diagrams, the system log can be especially helpful when a problem actually does occur. The log files can be accessed through the Logs tab.

Figure 35: Dynamic DNS update failure log entry
For those more comfortable with a command line interface, IPCop provides direct shell access (to the "root" user only). This can also come in handy if the web interface becomes unresponsive. Figure 36 illustrates a shutdown now -r sequence

Figure 36: A command line shutdown
Of course, installing additional software is also possible through the command line. However, we recommend leaving anything that goes beyond the normal IPCop installation to the seasoned Linux professional. After all, additional software may even compromise the router's security!
- Previous page Monitoring Features
- Next page Closing Thoughts