7:54 p.m.
G'day all,
I've a qustion about the dhcp server configuration in dnsmasq. The
way I've configured it it is listening on eth1 as it ought, but is
offering on eth0 which it oughtn't. What have I missed in the
configuration?
# Configuration file for dnsmasq.
#
interface=eth1
except-interface=eth0
dhcp-range=192.168.1.100,192.168.1.199,255.255.255.0,10m
dhcp-option=28,192.168.1.255
log-queries
log-dhcp
[simon@dell ~]$
and /var/log/messages:
Mar 28 11:45:33 dell dnsmasq[12161]: DHCP packet: transaction-id is
1613319306
Mar 28 11:45:33 dell dnsmasq[12161]: Available DHCP range: 192.168.1.100
--
192.168.1.199
Mar 28 11:45:33 dell dnsmasq[12161]: DHCPDISCOVER(eth1) 192.168.1.103
00:10:5a:62:2a:a5
Mar 28 11:45:33 dell dnsmasq[12161]: DHCPOFFER(eth1) 192.168.1.103
00:10:5a:62:2a:a5
Mar 28 11:45:33 dell dnsmasq[12161]: requested options: 1:netmask,
28:broadcast, 2:time-offset,
3:router,
Mar 28 11:45:33 dell dnsmasq[12161]: requested options: 15:domain-name,
6:dns-server,
12:hostname,
Mar 28 11:45:33 dell dnsmasq[12161]: requested options: 40:nis-domain,
41:nis-server,
42:ntp-server
Mar 28 11:45:33 dell dnsmasq[12161]: sent size: 1 option:
53:message-type 02
Mar 28 11:45:33 dell dnsmasq[12161]: sent size: 4 option:
54:server-identifier
c0:a8:01:01
Mar 28 11:45:33 dell dnsmasq[12161]: sent size: 4 option: 51:lease-time
00:00:02:58
Mar 28 11:45:33 dell dnsmasq[12161]: sent size: 4 option: 58:T1
00:00:01:2c
Mar 28 11:45:33 dell dnsmasq[12161]: sent size: 4 option: 59:T2
00:00:02:0d
Mar 28 11:45:33 dell dnsmasq[12161]: sent size: 4 option: 1:netmask
ff:ff:ff:00
Mar 28 11:45:33 dell dnsmasq[12161]: sent size: 4 option: 3:router
c0:a8:01:01
Mar 28 11:45:33 dell dnsmasq[12161]: sent size: 4 option: 6:dns-server
c0:a8:01:01
Mar 28 11:45:33 dell dnsmasq[12161]: sent size: 11 option:
15:domain-name
6c:6f:63:61:6c:64:6f:6d:61:69:6e
Mar 28 11:45:33 dell dnsmasq[12161]: sent size: 4 option: 28:broadcast
c0:a8:01:ff
Mar 28 11:45:33 dell kernel: [IPTABLES DROP] : IN= OUT=eth0
SRC=192.168.1.9 DST=192.168.1.103 LEN=333 TOS=0x00 PREC=0x00 TTL=64
ID=19755 PROTO=UDP SPT=67 DPT=68 LEN=313
How do I configure dnsmasq to offer dhcp on eth1?
Thanks in advance.
--
Regards,
Simon Slater
Registered Linux User #463789. Be counted at: http://counter.li.org/
5:27 p.m.
On Sat, 2009-03-28 at 11:54 +1100, Simon Slater wrote:
G'day all,
I've a qustion about the dhcp server configuration in dnsmasq. The
way I've configured it it is listening on eth1 as it ought, but is
offering on eth0 which it oughtn't. What have I missed in the
configuration?
# Configuration file for dnsmasq.
#
interface=eth1
except-interface=eth0
dhcp-range=192.168.1.100,192.168.1.199,255.255.255.0,10m
dhcp-option=28,192.168.1.255
log-queries
log-dhcp
[simon@dell ~]$
and /var/log/messages:
Mar 28 11:45:33 dell dnsmasq[12161]: DHCP packet: transaction-id is
1613319306
Mar 28 11:45:33 dell dnsmasq[12161]: Available DHCP range: 192.168.1.100
--
192.168.1.199
Mar 28 11:45:33 dell dnsmasq[12161]: DHCPDISCOVER(eth1) 192.168.1.103
00:10:5a:62:2a:a5
Mar 28 11:45:33 dell dnsmasq[12161]: DHCPOFFER(eth1) 192.168.1.103
00:10:5a:62:2a:a5
Mar 28 11:45:33 dell dnsmasq[12161]: requested options: 1:netmask,
28:broadcast, 2:time-offset,
3:router,
Mar 28 11:45:33 dell dnsmasq[12161]: requested options: 15:domain-name,
6:dns-server,
12:hostname,
Mar 28 11:45:33 dell dnsmasq[12161]: requested options: 40:nis-domain,
41:nis-server,
42:ntp-server
Mar 28 11:45:33 dell dnsmasq[12161]: sent size: 1 option:
53:message-type 02
Mar 28 11:45:33 dell dnsmasq[12161]: sent size: 4 option:
54:server-identifier
c0:a8:01:01
Mar 28 11:45:33 dell dnsmasq[12161]: sent size: 4 option: 51:lease-time
00:00:02:58
Mar 28 11:45:33 dell dnsmasq[12161]: sent size: 4 option: 58:T1
00:00:01:2c
Mar 28 11:45:33 dell dnsmasq[12161]: sent size: 4 option: 59:T2
00:00:02:0d
Mar 28 11:45:33 dell dnsmasq[12161]: sent size: 4 option: 1:netmask
ff:ff:ff:00
Mar 28 11:45:33 dell dnsmasq[12161]: sent size: 4 option: 3:router
c0:a8:01:01
Mar 28 11:45:33 dell dnsmasq[12161]: sent size: 4 option: 6:dns-server
c0:a8:01:01
Mar 28 11:45:33 dell dnsmasq[12161]: sent size: 11 option:
15:domain-name
6c:6f:63:61:6c:64:6f:6d:61:69:6e
Mar 28 11:45:33 dell dnsmasq[12161]: sent size: 4 option: 28:broadcast
c0:a8:01:ff
Mar 28 11:45:33 dell kernel: [IPTABLES DROP] : IN= OUT=eth0
SRC=192.168.1.9 DST=192.168.1.103 LEN=333 TOS=0x00 PREC=0x00 TTL=64
ID=19755 PROTO=UDP SPT=67 DPT=68 LEN=313
How do I configure dnsmasq to offer dhcp on eth1?
Thanks in advance.
I've been slowly plugging away at this and may have found something
useful. After a reboot I got the message:
dnsmasq failed to bind DHCP server socket: address already in use.
In the startup sequence as it scrolls on the screen, dnsmasq is near the
end, but is running:
[root@dell ~]# service dnsmasq status
dnsmasq (pid 2613) is running...
So is the problem with the configuration or at startup? How do I find
what is conflicting for the socket address?
--
Regards,
Simon Slater
Registered Linux User #463789. Be counted at: http://counter.li.org/
12:21 a.m.
On Thu, 2009-04-02 at 09:27 +1100, Simon Slater wrote:
After a reboot I got the message:
dnsmasq failed to bind DHCP server socket: address already in use.
Which may be that something *else* is using it, or that dnsmasq is
starting up in a way that causes problems with itself. I've seen that
sort of thing when there's a network with IPv4 and IPv6 addressing in
use, and a service starts up. It listens to both, and while starting up
complains that the port's already in use while trying to listen to the
second interface (which is really the first, with the IPv6 type of
addresses, as well as IPv4).
In the startup sequence as it scrolls on the screen, dnsmasq is near
the end, but is running:
[root@dell ~]# service dnsmasq status
dnsmasq (pid 2613) is running...
So is the problem with the configuration or at startup? How
do I find what is conflicting for the socket address?
man netstat
e.g. netstat -antuevp
--
[tim@localhost ~]$ uname -r
2.6.27.19-78.2.30.fc9.i686
Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.
1:37 a.m.
On Thu, 2009-04-02 at 15:51 +1030, Tim wrote:
On Thu, 2009-04-02 at 09:27 +1100, Simon Slater wrote:
> After a reboot I got the message:
>
> dnsmasq failed to bind DHCP server socket: address already in use.
Which may be that something *else* is using it, or that dnsmasq is
starting up in a way that causes problems with itself. I've seen that
sort of thing when there's a network with IPv4 and IPv6 addressing in
use, and a service starts up. It listens to both, and while starting up
complains that the port's already in use while trying to listen to the
second interface (which is really the first, with the IPv6 type of
addresses, as well as IPv4).
> In the startup sequence as it scrolls on the screen, dnsmasq is near
> the end, but is running:
> [root@dell ~]# service dnsmasq status
> dnsmasq (pid 2613) is running...
>
> So is the problem with the configuration or at startup? How
> do I find what is conflicting for the socket address?
man netstat
e.g. netstat -antuevp
Thanks Tim,
Now this shows that dnsmasq is using 192.168.122.1:53 with tcp and udp.
This is the link local address on a port for dns. Also udp on
0.0.0.0:67 which is one of the dhcp ports but for all networks?
Does dnsmasq need to use 192.168.122.1?
The first aim is to get dhcp going. Would 0.0.0.0:67 help or get in the
way?
--
Regards,
Simon Slater
Registered Linux User #463789. Be counted at: http://counter.li.org/
10:40 a.m.
On Thu, 2009-04-02 at 17:37 +1100, Simon Slater wrote:
netstat -antuevp
Now this shows that dnsmasq is using 192.168.122.1:53 with tcp and
udp.
This is the link local address on a port for dns. Also udp on
0.0.0.0:67 which is one of the dhcp ports but for all networks?
0.0.0.0 means different things in different circumstances. In this
case, yes, it means it's listening to port 67 on any and all interfaces
that computer has alive.
Does dnsmasq need to use 192.168.122.1?
No idea, though I'd be surprised if it did. What do you want it to use?
For what it's worth, I don't use dnsmasq, I use the BIND DNS server, and
the ISC DHCP server (Fedora has packages for both), and integrate them
together. I know the processes for DNS and DHCP serving, but not the
specifics to making dnsmasq do them.
The first aim is to get dhcp going. Would 0.0.0.0:67 help or get in
the way?
In what way do you mean "0.0.0.0:67"?
If you're setting up your modem/router to be just a modem, and let the
PC do the rest, then you want configure your DHCP server to only service
your LAN. You don't want it trying to assign addresses out to the ISP.
You should probably find how to configure it to only bind to the LAN
interface.
--
[tim@localhost ~]$ uname -r
2.6.27.19-78.2.30.fc9.i686
Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.
7:24 p.m.
On Fri, 2009-04-03 at 02:10 +1030, Tim wrote:
On Thu, 2009-04-02 at 17:37 +1100, Simon Slater wrote:
> netstat -antuevp
>
> Now this shows that dnsmasq is using 192.168.122.1:53 with tcp and
> udp.
> This is the link local address on a port for dns. Also udp on
> 0.0.0.0:67 which is one of the dhcp ports but for all networks?
0.0.0.0 means different things in different circumstances. In this
case, yes, it means it's listening to port 67 on any and all interfaces
that computer has alive.
> Does dnsmasq need to use 192.168.122.1?
No idea, though I'd be surprised if it did. What do you want it to use?
For what it's worth, I don't use dnsmasq, I use the BIND DNS server, and
the ISC DHCP server (Fedora has packages for both), and integrate them
together. I know the processes for DNS and DHCP serving, but not the
specifics to making dnsmasq do them.
> The first aim is to get dhcp going. Would 0.0.0.0:67 help or get in
> the way?
In what way do you mean "0.0.0.0:67"?
If you're setting up your modem/router to be just a modem, and let the
PC do the rest, then you want configure your DHCP server to only service
your LAN. You don't want it trying to assign addresses out to the ISP.
You should probably find how to configure it to only bind to the LAN
interface.
Thanks Tim,
I went back to a fresh dnsmasq.conf (must have missed something
amongst all the comments in the example file) with the bare basics, now
with the correct references to interfaces and addresses, and dhcp worked
straight away. Clients are connecting fine, printing is working, all
good. I'll check out how well the dns and caching is working over the
weekend.
The initial thought was to use bind and ISC dhcp, but after reviewing
old posts to this list, many advocated dnsmasq for small setups like
this. Although their website says it can scale up to service a thousand
or so boxes. So simplicity for now.
--
Hooroo,
Simon
Registered Linux User #463789. Be counted at: http://counter.li.org/
5505
days inactive
5512
days old
5 comments
2 participants
participants (2)
-
Simon Slater -
Tim