
System Services
95
14.5.3. Auto DHCP DNS
The FB2700 can also look for specific matching names and IP addresses for forward and reverse DNS that
match machines on your LAN. This is done by telling the FireBrick the
domain
for your local network. Any
name that is within that domain which matches a client name of a DHCP allocation that the FireBrick has made
will return the IP address assigned by DHCP. This is applied in reverse for reverse DNS mapping an IP address
back to a name. You can enable this using the
auto-dhcp
attribute.
14.6. NTP configuration
The NTP service automatically sets the FB2700's real-time-clock using time information provided by a Network
Time Protocol (NTP) server. There are public NTP servers available for use on the Internet, and a factory reset
configuration does not specify an NTP server which means a default of
ntp.firebrick.ltd.uk
. You
can set your preferred NTP server instead.
The NTP service is currently only an NTP client. A future software version is likely to add NTP server
functionality, allowing other NTP clients (typically those in your network) to use the FB2700 as an NTP server.
Configuration of the NTP (client) service typically only requires setting the
timeserver
attribute to specify
one or more NTP servers, using either DNS name or IP address.
14.7. SNMP configuration
The SNMP service allows other devices to query the FB2700 for management related information, using the
Simple Network Management Protocol (SNMP).
As with the HTTP server, access can be restricted to :-
• specific client IP addresses, and/or
• clients connecting from locally-attached Ethernet subnets only.
See Section 14.3.1 for details. The SNMP service defaults to allowing access from anywhere.
The remaining SNMP service configuration attributes are :-
•
community
: specifies the SNMP community name, with a default of
public
•
port
: specifies the port number that the SNMP service listens on - this typically does not need setting, as
the default is the standard SNMP port (161).
14.8. RADIUS configuration
14.8.1. RADIUS server (platform RADIUS)
Chapter 20 provides details of how the platform RADIUS service can be used to steer incoming sessions from
a carrier for L2TP.
14.8.2. RADIUS client
RADIUS is used for authentication and accounting for incoming L2TP connections. Chapter 20 provides details
of how RADIUS is used for L2TP. Appendix F provides details of the specific AVPs used with RADIUS for
L2TP.