Re: dnsmasq configuration
by Tim
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.
15 years, 1 month
Re: dnsmasq configuration
by Simon Slater
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/
15 years, 1 month
dnsmasq configuration
by Simon Slater
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/
15 years, 1 month
Re: Something is Fishy About My Network
by Matthew Flaschen
Kevin J. Cummings wrote:
>> I think you're overstating the complexity of this. It shouldn't be that
>> hard for him to get it working with dnsmasq. Also, what aspect of the
>> configuration do you think is deprecated?
>
> The Linux DHCP server no longer has the right hooks to fix up BIN
> directly.
There is no single "Linux DHCP server". ISC dhcpd (which I assume
you're referring to) is not the only thing that can provide DHCP. As I
said, dnsmasq is a good solution here because it's a single program that
can provide integrated DHCP and DNS.
> It needs another tool to help out.
Right, so don't use dhcpd at all.
Matt Flaschen
15 years, 2 months
Re: Something is Fishy About My Network
by Kevin Cummings
Tim wrote:
> On Thu, 2009-03-05 at 13:02 -0500, Kevin J. Cummings wrote:
>> The Linux DHCP server no longer has the right hooks to fix up BIN
>
> BIND? (Just in case you're referring to something else that I haven't
> guessed at.)
Yes, my keyboard and my fingers don't always agree on what I want to type.
>> directly. It needs another tool to help out. The "old" way of doing
>> that is no longer supported and is deprecated. At least according to
>> the documentation the last time I read it (about 5 years ago).
>
> If you mean the DHCP server needs special configuration to update DNS
> server records, the previous scheme of allowing clients to do that,
> based on what they're address supposedly is, then yes that's out of
> date. Since then, the methodology was to use a shared secrets keyfile
> (/etc/rndc.key).
>
> It's not too hard to integrate the BIND name server with the DHCP server
> Fedora's using, and the skills learnt in doing so are useful for other
> things. But I think the ease of using dnsmasq is supposed to be that
> much of that nitty-gritty work is taken care of already. It might
> depend on what else you want to do, DNS- and DHCP-wise. You can pull
> rabbits out of hats the hard way, I don't know what the limitations of
> using dnsmasq might be.
Agreed.
--
Kevin J. Cummings
kjchome(a)rcn.com
cummings(a)kjchome.homeip.net
cummings(a)kjc386.framingham.ma.us
Registered Linux User #1232 (http://counter.li.org)
15 years, 2 months
Re: Something is Fishy About My Network
by Tim
On Thu, 2009-03-05 at 13:02 -0500, Kevin J. Cummings wrote:
> The Linux DHCP server no longer has the right hooks to fix up BIN
BIND? (Just in case you're referring to something else that I haven't
guessed at.)
> directly. It needs another tool to help out. The "old" way of doing
> that is no longer supported and is deprecated. At least according to
> the documentation the last time I read it (about 5 years ago).
If you mean the DHCP server needs special configuration to update DNS
server records, the previous scheme of allowing clients to do that,
based on what they're address supposedly is, then yes that's out of
date. Since then, the methodology was to use a shared secrets keyfile
(/etc/rndc.key).
It's not too hard to integrate the BIND name server with the DHCP server
Fedora's using, and the skills learnt in doing so are useful for other
things. But I think the ease of using dnsmasq is supposed to be that
much of that nitty-gritty work is taken care of already. It might
depend on what else you want to do, DNS- and DHCP-wise. You can pull
rabbits out of hats the hard way, I don't know what the limitations of
using dnsmasq might be.
--
[tim@localhost ~]$ uname -r
2.6.27.15-78.2.23.fc9.i686
Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.
15 years, 2 months
Re: Something is Fishy About My Network
by Kevin Cummings
Matthew Flaschen wrote:
> Kevin J. Cummings wrote:
>> Suggestion #2 (if you are up to it): Disable DHCP serving in your
>> router and setup a DHCP server on a Linux machine. You can set up the
>> dchp.conf file to do everything your touter is doing. If this machine
>> is also running DNS, there are some ways to get them to talk to each
>> other so that DNS knows the names of machines served by the DHCP server.
>> This is not trivial, and requires in depth knowledge of both protocols
>> to get to work right. Possibly including depricated configuration options.
>
> I think you're overstating the complexity of this. It shouldn't be that
> hard for him to get it working with dnsmasq. Also, what aspect of the
> configuration do you think is deprecated?
The Linux DHCP server no longer has the right hooks to fix up BIN
directly. It needs another tool to help out. The "old" way of doing
that is no longer supported and is deprecated. At least according to
the documentation the last time I read it (about 5 years ago).
> Matt Flaschen
--
Kevin J. Cummings
kjchome(a)rcn.com
cummings(a)kjchome.homeip.net
cummings(a)kjc386.framingham.ma.us
Registered Linux User #1232 (http://counter.li.org)
15 years, 2 months
Re: Something is Fishy About My Network
by Marc Ferguson
On Thu, Mar 5, 2009 at 9:27 AM, Matthew Flaschen
<matthew.flaschen(a)gatech.edu> wrote:
>
> Kevin J. Cummings wrote:
> > Suggestion #2 (if you are up to it): Disable DHCP serving in your
> > router and setup a DHCP server on a Linux machine. You can set up the
> > dchp.conf file to do everything your touter is doing. If this machine
> > is also running DNS, there are some ways to get them to talk to each
> > other so that DNS knows the names of machines served by the DHCP server.
> > This is not trivial, and requires in depth knowledge of both protocols
> > to get to work right. Possibly including depricated configuration options.
>
> I think you're overstating the complexity of this. It shouldn't be that
> hard for him to get it working with dnsmasq. Also, what aspect of the
> configuration do you think is deprecated?
>
> Matt Flaschen
>
> --
> fedora-list mailing list
> fedora-list(a)redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
> Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Thank you all for your feedback. I'll try these things out and reply
with more details when I get home.
--
Marc F.
www.fergytech.com
Registered Linux User: #410978
"When life gives me lemons... I make Linuxaide, hmm good stuff!"
15 years, 2 months
Re: Something is Fishy About My Network
by Matthew Flaschen
Kevin J. Cummings wrote:
> Suggestion #2 (if you are up to it): Disable DHCP serving in your
> router and setup a DHCP server on a Linux machine. You can set up the
> dchp.conf file to do everything your touter is doing. If this machine
> is also running DNS, there are some ways to get them to talk to each
> other so that DNS knows the names of machines served by the DHCP server.
> This is not trivial, and requires in depth knowledge of both protocols
> to get to work right. Possibly including depricated configuration options.
I think you're overstating the complexity of this. It shouldn't be that
hard for him to get it working with dnsmasq. Also, what aspect of the
configuration do you think is deprecated?
Matt Flaschen
15 years, 2 months
Re: Clarification on roles of networking components.
by Simon Slater
On Wed, 2009-03-04 at 15:57 -0500, Flaschen, Matthew S wrote:
> > Now I've caught up on some sleep I can continue with a clearer head.
> > The single server has 2 nics, one internal the other to the dsl
> router.
> > For now internal name resolution and dhcp is the issue, but more
> > internal services will be added down the road, as well as web server
> > usw. I started with dhcpd but this does seem more powerful than I
> need
> > now.
>
> I would say dhcpd is less powerful (for your purposes), because it
> does not integrate DNS and DHCP automatically. Now in many cases
> dhcpd is perfect, but since you want name resolution for all hosts I
> think dnsmasq is a better choice.
>
Yes, thanks Matt. As you pointed out in your first post, I have been
seeing the individual components of a network as disparate entities and
not necessarily linking them together in the right ways.
What would be really helpful would be if someone could point me to an
overview of networking, showing how the various applications, services
and protocols link together, overlap, complement or substitute for each
other, if such a thing exists.
Maybe good for a Fedora Classroom session. Anyone up for it?
--
Regards,
Simon Slater
Registered Linux User #463789. Be counted at: http://counter.li.org/
15 years, 2 months
