sysmo-bts
/
meta-sysmocom-bsp
9
1
Fork 0
Code Issues Pull Requests Releases Activity

dnsmasq: Initial configuration for sysmocom 

This is untested but in the assembled IDU eth2 is the NJB
link and the range/netmask was taken from the ISC DHCPD
configuration file.
This commit is contained in:
Holger Hans Peter Freyther 2015-02-13 09:48:22 +01:00
parent e69ac76dc0
commit d1bca38043
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
recipes-extra/dnsmasq/files/sysmocom-idu/dnsmasq.conf
View File

@ -72,7 +72,7 @@ bogus-priv
# If you want dnsmasq to listen for requests only on specified interfaces
# (and the loopback) give the name of the interface (eg eth0) here.
# Repeat the line for more than one interface.
#interface=
interface=eth2
# Or you can specify which interface _not_ to listen on
#except-interface=
# Or which to listen on by address (remember to include 127.0.0.1 if
@ -114,13 +114,14 @@ bogus-priv
# repeat this for each network on which you want to supply DHCP
# service.
#dhcp-range=192.168.0.50,192.168.0.150,12h
dhcp-range=10.0.0.10,10.0.0.200,2h
#dhcp-range=10.0.0.10,10.0.0.200,2h
# This is an example of a DHCP range where the netmask is given. This
# is needed for networks we reach the dnsmasq DHCP server via a relay
# agent. If you don't know what a DHCP relay agent is, you probably
# don't need to worry about this.
#dhcp-range=192.168.0.50,192.168.0.150,255.255.255.0,12h
dhcp-range=172.16.2.2,172.16.3.254,255.255.254.0,168h
# This is an example of a DHCP range with a network-id, so that
# some DHCP options may be set only for this network.