Prev: Slackware 11 installs but won't boot - help!
Next: memory stick
From: Rich Grise on 1 Nov 2006 13:20
On Wed, 01 Nov 2006 02:39:08 +0100, Kees Theunissen wrote:
> Rich Grise wrote:
>> While booting my brand new 11.0 system on the brand new box, I get this
>> message:
>>
>> dnsmasq: failed to create listening socket: Address already in use
>>
>> and I have no idea what it means. I'm pretty sure this is the first
>> release that I've ever even heard of such a thing - didn't it used to be
>> iptables?
>
> I certainly isn't new to slack 11.
>
> Here on a slack 10.2:
>
> [ snip example]
>
> Looks like you'r trying to start two different nameservers or dhcp
> servers.
>

Thanks for this!

But, I've never used dnsmasq before - I've always (9.0, 9.1, 10.0, 10.2)
copied the "IP Masquerading" script from the HOWTO, which invokes iptables.

Guess I might have to back up a little and do some more RTFM here. :-)

Thanks!
Rich



From: Rich Grise on 1 Nov 2006 13:42
On Wed, 01 Nov 2006 02:39:08 +0100, Kees Theunissen wrote:
> Rich Grise wrote:
>> While booting my brand new 11.0 system on the brand new box, I get this
>> message:
>>
>> dnsmasq: failed to create listening socket: Address already in use
....
> Looks like you'r trying to start two different nameservers or dhcp
> servers.

Yes, it looks like that to me, too, but I don't know how to resolve it,
yet.

Would dhcpcd or rc.inet1.conf have anything to do with that "already in
use" stuff? How do I find out _which_ address is already in use? Is
that somewhere in the comments in the default dnsmasq.conf? (which I've
only started delving into less than an hour ago, but I'm impatient with
myself).

Thanks,
Rich

From: Old Man on 1 Nov 2006 17:45
Rich Grise wrote:

>
> But, I've never used dnsmasq before - I've always (9.0, 9.1, 10.0, 10.2)
> copied the "IP Masquerading" script from the HOWTO, which invokes
> iptables.

Don't be confused by the "masq" in dnsmasq. It does not perform the
same "ip masquerading" function that iptables performs. It does dns and,
optionally, dhcp. I think it is called dnsmasq because it is well suited
to small, private "ip masquerading" networks, providing dynamic addresses
and names to machines on the private network.

If, I'm being pedantic or telling you stuff you already get, I'll gladly
apologize.

--
Old Man

"I could be wrong again
I remember once in August 1993
I was wrong, and I could be wrong again" - Paul Simon
From: Rich Grise on 3 Nov 2006 14:59
On Wed, 01 Nov 2006 17:45:08 -0500, Old Man wrote:
> Rich Grise wrote:
>
>> But, I've never used dnsmasq before - I've always (9.0, 9.1, 10.0, 10.2)
>> copied the "IP Masquerading" script from the HOWTO, which invokes
>> iptables.
>
> Don't be confused by the "masq" in dnsmasq. It does not perform the
> same "ip masquerading" function that iptables performs. It does dns and,
> optionally, dhcp. I think it is called dnsmasq because it is well suited
> to small, private "ip masquerading" networks, providing dynamic addresses
> and names to machines on the private network.
>
> If, I'm being pedantic or telling you stuff you already get, I'll gladly
> apologize.

Please, no apologies necessary! I appreciate you taking the time to give
me a hand with this.

Thanks!
Rich

 | 
Pages: 1
Prev: Slackware 11 installs but won't boot - help!
Next: memory stick