Re: [Dnsmasq-discuss] What s the dnsmasq/DHCP way to give a host a fixed IP?
Hallo, Matthias, Du meintest am 17.12.14: I have a setup in which the DHCP range is 192.168.2.128 to 192.168.2.250, and I manually give some devices an IP in range 192.168.2.1 to 192.168.2.127, using the dhcp-host line. So that I can use the u32 traffic classifier to split traffic streams. It looks working well. Is there some story about why the static address should be in the DHCP range? I don't know one, but it should be in the interface address ranges that dnsmasq is responsible for. Sure? On my machines I define the dhcp-host IP-addresses outside the dhcp- range, and that works well. p.e. dhcp-range=192.168.0.100,192.168.0.240,3d dhcp-host=20:d3:90:d9:d3:a3,192.168.0.30,Galaxy,90d Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] (no subject)
Hallo, richardvo...@gmail.com, Du meintest am 17.01.13: I strongly suggest you test it from your login shell first, to separate problems in the approach from problems in the cron environment. Run 'ps' to see how many dnsmasq processes you have. If there's more than one, then 'pidof' won't be as useful. More simple: pgrep -l dnsmasq Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] RFE: improve dnsmasq survivability and resilience
Hallo, Gene, Du meintest am 04.11.12: These days many/some systems have made quick bootup speed an important objective. May be. But dnsmasq is a server job, and servers shouldn't boot often. Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Dnsmasq-discuss Digest, Vol 88, Issue 5
Hallo, subhranshu, Du meintest am 05.09.12: i had the DMZ on eth2 which had wrong subnet set on routing, Actually this was by default set for DMZ and i think it was interfering with the eth1 route. which i just fixed and every things seems to be working fine now Computing can be so easy ... Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] dhcp logging and dhcp-range static configuration
Hallo, Simon, Du meintest am 03.09.12: Is there a way to prevent logging the DHCPDISCOVER request for unconfigured hardware address in dhcp-range static mode ? Try dhcp-ignore=!known or possibly the old syntax dhcp-ignore=#known Additional question: When I have 2 NICs, and one of them uses dhcp-host=..., how can I tell dnsmasq that all unlisted clients (which have no dhcp-host-line) must use the other NIC? Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Issues with multiple subnets on dnsmasq
Hallo, subhranshu, Du meintest am 03.09.12: INTERNAL eth1 Link encap:Ethernet HWaddr 00:04:23:c7:52:62 inet addr:172.16.48.4 Bcast:172.16.51.255 Mask:255.255.252.0 DMZ That mask describes 172.16.48.0 ... 172.16.51.255 It includes eth2 eth2 Link encap:Ethernet HWaddr 00:1b:21:0e:1f:46 inet addr:172.16.48.110 Bcast:172.16.49.255 Mask:255.255.254.0 That mask describes 172.16.48.0 ... 172.16.49.255 It's part of eth1 Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Using dhcp-host hostname as address for DNS
Hallo, Simon, Du meintest am 29.07.12: My question is whether it would be possible to have a single line config statement for mac-ip-hostname mapping. But I want to have the DNS entries permanently preserved resp. dns mappings without prior dhcp ip negotiation. Actually this means I don't want DNS to be dynamic. Is this somehow configurable? Yes. Put the hostname-IP address mapping in /etc/hosts and the mac_address-hostname mappings in /etc/dnsmasq.conf in dhcp-host lines. so: in /etc/hosts 1.2.3.4 myhost in /etc/dnsmasq.conf dhcp=host=00:11:22:33:44:55,myhost Perhaps a nasty typo: dhcp-host=00:11:22:33:44:55,myhost Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Using dhcp-host hostname as address for DNS
Hallo, /dev/rob0, Du meintest am 31.07.12: My question is whether it would be possible to have a single line config statement for mac-ip-hostname mapping. But I want to have the DNS entries permanently preserved resp. dns mappings without prior dhcp ip negotiation. Actually this means I don't want DNS to be dynamic. so: in /etc/hosts 1.2.3.4 myhost in /etc/dnsmasq.conf dhcp-host=00:11:22:33:44:55,myhost So this means that I can't maintain my hosts in a single file with only one statement? Single statement, not that I know of. Single file, sure. See -A, --address in the man page. in /etc/dnsmasq.conf : dhcp-host=00:11:22:33:44:55,myhost address=/myhost/1.2.3.4 What about the addresses (not the dhcp-host definition(s)) in a separate file: addn-hosts=/path/to/hosts.LAN and a file /path/to/hosts.LAN like # IP-addressHostname 192.168.0.100 Host100 # etc Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] New job vacancy - see details
Hallo, Jan-Piet, Du meintest am 18.07.12: IMHO, no effort is currently necessary. I follow many mailing-lists, and dnsmasq-discuss is the _only_ one I follow, in which I see spam. Then subscribe the btrfs mailinglist, p.e. ... Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Removing a feature does anyone rely on this?
Hallo, richardvo...@gmail.com, Du meintest am 09.07.12: We wanted dhcp-range=192.168.0.10,static,infinite # (192.168.0.0/24) for the school computers dhcp-range=192.168.18.10,192.168.31.250,30d # (192.168.16.0/20) for the private machines and defined all school computers via dhcp-host= Sometimes/often they got IP adresses from the private net. Assign the #known (or newer, !known) tag to the private dhcp-range, this way it won't ever be used for hosts which have static addresses. Just for clarity: you mean something like dhcp-host=11:22:33:44:55:66,192.168.0.41,pc41 with static address? And not user defined IP address? Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Removing a feature does anyone rely on this?
Hallo, Richard, Du meintest am 09.07.12: We wanted dhcp-range=192.168.0.10,static,infinite # (192.168.0.0/24) for the school computers dhcp-range=192.168.18.10,192.168.31.250,30d # (192.168.16.0/20) for the private machines Assign the #known (or newer, !known) tag to the private dhcp-range, this way it won't ever be used for hosts which have static addresses. ... Yes, the known tag matches all dhcp-host entries, including those converted from /etc/ethers. Thank you - we'll take a (new) try! Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Removing a feature does anyone rely on this?
Hallo, Olaf, Du meintest am 07.07.12: We wanted dhcp-range=192.168.0.10,static,infinite # (192.168.0.0/24) for the school computers dhcp-range=192.168.18.10,192.168.31.250,30d # (192.168.16.0/20) for the private machines and defined all school computers via dhcp-host= I (and many IPCop installations too) am using something like this for a long time, without any problems: # network: GREEN - 1, 192.168.1.200/24 dhcp-range=GREEN_1,192.168.1.101,192.168.1.199,28800 dhcp-option=GREEN_1,option:domain-name,olaf.local [...] Looks good. But how and where is GREEN_1 set/defined? I've studied the dnsmasq man page several times but haven't found the way to tell dnsmasq that (p.e.) eth1 is set to GREEN_1. Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Removing a feature does anyone rely on this?
Hallo, Vincent, Du meintest am 02.07.12: But it seems to be a bit more difficult to change automatically something like dhcp-range=eth0,192.168.0.10,static dhcp-range=eth1,192.168.1,10,static dhcp-range=eth2,192.168.17.10-192.168,28.250 to dhcp-range=eth0,192.168.0.10,static dhcp-range=eth2,192.168.1,10,static dhcp-range=eth1,192.168.17.10-192.168,28.250 when the names of eth1 and eth2 have changed. What about [re]naming those interface names using udev, i.e. xx-persistent-net.rules file in /etc/udev/rules.d/ ? That moves the problem from one place to another. I don't like udev, I don't use udev. Especially with more than 1 NIC it makes more problems than it solves. Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Removing a feature does anyone rely on this?
Hallo, Ed, Du meintest am 02.07.12: [dhcp-range=ethx,...] What about [re]naming those interface names using udev, i.e. xx-persistent-net.rules file in /etc/udev/rules.d/ ? That moves the problem from one place to another. I don't like udev, I don't use udev. Especially with more than 1 NIC it makes more problems than it solves. Although you don't like udev, I think it's an important part of your final solution. Sorry - I disagree. udev moves the problems, it doesn't solve them. Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Removing a feature does anyone rely on this?
Hallo, Simon, Du meintest am 02.07.12: dhcp-range may have an interface name supplied as interface:interface- name . I'd like to use this feature in many schools: eth0 and eth1 for the school clients in the LAN, eth2 for the private clients (especially in the WLAN). And eth3 for DSL/Router into the WAN. [...] Note that you don't need to tell dnsmasq which dhcp-range goes with which interface - it finds that automatically using the IP address and netmask of the interfaces. May be. But our experiments failed. We wanted dhcp-range=192.168.0.10,static,infinite # (192.168.0.0/24) for the school computers dhcp-range=192.168.18.10,192.168.31.250,30d # (192.168.16.0/20) for the private machines and defined all school computers via dhcp-host= Sometimes/often they got IP adresses from the private net. Adding/changing dhcp-range=eth0,... dhcp-range=eth1,... didn't help. There is a third NIC for the DSL/Router, defined as no-dhcp-interface=eth2 Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Removing a feature does anyone rely on this?
Hallo, Simon, Du meintest am 01.07.12: A quote from the man page: dhcp-range may have an interface name supplied as interface:interface- name . The semantics if this are as follows: For DHCP, if any other dhcp-range exists _without_ an interface name, then the interface name is ignored and and dnsmasq behaves as if the interface parts did not exist, [...] This feature was added to facilitate integration with uses such as libvirt, where libvirt could automatically add extra facilities to a single system dnsmasq instance. It has never been used as such, and things like libvirt and openstack and networkmanager have instead gone down the route of running their own private dnsmasq instances. I'd like to use this feature in many schools: eth0 and eth1 for the school clients in the LAN, eth2 for the private clients (especially in the WLAN). And eth3 for DSL/Router into the WAN. Other services (like squid) may allow or disallow something depending on the net range (and therefore on the NIC). The major problem: sometimes a NIC dies and has to be replaced, and then the NIC names may change too. Other services (especially samba and squid) allow something like interfaces=eth0 eth1 local, and that is simple to change by a script which first detects which interfaces serve which net. But it seems to be a bit more difficult to change automatically something like dhcp-range=eth0,192.168.0.10,static dhcp-range=eth1,192.168.1,10,static dhcp-range=eth2,192.168.17.10-192.168,28.250 to dhcp-range=eth0,192.168.0.10,static dhcp-range=eth2,192.168.1,10,static dhcp-range=eth1,192.168.17.10-192.168,28.250 when the names of eth1 and eth2 have changed. It's a problem which happens seldom, and when it happens the system administrator has forgotten that he has to check these entries too. But if there is anyone using it for other than it's intended use, that's going to cause them problems. The best I can do to find out if this is used is to ask on the list. Not perfect, but if no-one here is using it, that's a reasonable indication that it's un-used. I'd be happy if there is a simple (scriptable) solution. Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Dhcp discover client source ip not 0.0.0.0
Hallo, Sen, Du meintest am 22.05.12: Do you know where the faulty request is getting lost? Does dnsmasq log receiving the DHCPDISCOVER? Dnsmasq doesn't log anything. My dnsmasq logs such things as DHCPREQUEST or DHCPACK. Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
[Dnsmasq-discuss] load balancing with interfaces
Hallo, in a school I want to run all schoolish clients (about 150) over eth0, with quasi static IP addresses (dhcp-host=...) and all private clients (private netbooks, smartphones etc.) over eth1 (completely DHCP, lease time 2 days). eth0: 192.168.0.0/24 eth1: 192.168.16.0/20 My dnsmasq configuration: dhcp-range=192.168.0.1,static,300d dhcp-range=192.168.18.10,192.168.31.250,2d It doesn't work as expected. Changing the range definitions to dhcp-range=eth0,192.168.0.1,static,300d dhcp-range=eth1,192.168.18.10,192.168.31.250,2d also doesn't work as expected. Users who use a schoolish client with (p.e.) dhcp-host=00:11:22:33:44:55:66,192.168.0.101,b100-pc1 get a DHCP address from the eth1 range, p.e. 192.168.21.22 What goes wrong? Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] load balancing with interfaces
Hallo, Richard, Du meintest am 11.04.12: [...] Changing the range definitions to dhcp-range=eth0,192.168.0.1,static,300d dhcp-range=eth1,192.168.18.10,192.168.31.250,2d also doesn't work as expected. Users who use a schoolish client with (p.e.) dhcp-host=00:11:22:33:44:55:66,192.168.0.101,b100-pc1 get a DHCP address from the eth1 range, p.e. 192.168.21.22 What goes wrong? If the client is physically connected to eth1, it will get an address which is usable on that network. Your static range will only be given out to client physically connected to eth0, because you've configured it that way. Ok - I'll ask the colleague how he has connected the clients. Thank you! Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] TFTP FIXME message
Hallo, Simon, Du meintest am 01.04.12: my (self made) dnsmasq 2.60 always tells TFTP FIXME: this and the next few must be full strings to be translatable - do not assemble in code/tftpboot when it gets started. What does that message mean? It means that my code builds English sentences on the fly and that makes translating into German difficult (Because the word order different is). The German translation (in the file po/de.po ) is sadly out-of-date, but if anyone wants to work on it, I'll happily try and fix the messages to make it easier. Ok - it's no error message but only a kind of reminder for that nice guy who will fill this file po/de.po. Searching for FIXME only shows this file, searching for translatable only shows network.c (line 785). But then I can't imagine which english text has to be translated. Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] TFTP FIXME message
Hallo, Simon, Du meintest am 02.04.12: TFTP FIXME: this and the next few must be full strings to be translatable - do not assemble in code/tftpboot when it gets started. What does that message mean? [...] The problem is here: #: dnsmasq.c:588 msgid root is msgstr FIXME: this and the next few must be full strings to be translatable - do not assemble in code Ok - I just believe it ... Long time ago I've taken a quick look onto gettext etc. - I decided to put it into cold storage (in german: ich habe es auf die lange Bank geschoben). I'll move the FIXME to a comment for now, pending work on the translation. Thank you - that won't confuse end users like me. Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
[Dnsmasq-discuss] TFTP FIXME message
Hallo, my (self made) dnsmasq 2.60 always tells TFTP FIXME: this and the next few must be full strings to be translatable - do not assemble in code/tftpboot when it gets started. What does that message mean? Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Announce: dnsmasq-2.60.
Hallo, Simon, Du meintest am 05.03.12: thanks to all who have contributed to this significant milestone. Download it from http://www.thekelleys.org.uk/dnsmasq/dnsmasq-2.60.tar.gz http://www.thekelleys.org.uk/dnsmasq/dnsmasq-2.60.tar.lzma Slackware packet: http://helmut.hullen.de/filebox/Linux/slackware/n/dnsmasq-2.60-i486-1hln.txz Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] DHCP over 2 NICs
Hallo, Oliver, Du meintest am 28.02.12: dnsmasq finds the right interface with the static address automaticly. If you write interface=.. you discard the use of the others. Simply delete the interface=.. line and your dnsmasq should run fine. Doesn't help - sorry. One detail: with the interface=lo lines mailing with Thunderbird (from the clients) works. Without it: no mailing. Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
[Dnsmasq-discuss] DHCP over 2 NICs
Hallo, on 2 schools in the neighbourhood we try to connect clients with the server (DHCP and many other services) via DHCP. With 1 NIC all works fine, something like interface=eth0 dhcp-range=192.168.0.220,192.168.0.240,3d allows static addresses (defined on the client), DHCP addresses defined by dhcp-host=... and free addresses from the above range. When we install a second NIC (especially for the private smartphones etc) and add the lines interface=eth1 dhcp-range=192.168.4.10,192.168.4.250,1d then we can see that pinging over the second card works, routing too. When dnsmasq gets started then it also tells the new dhcp range. But if the client has no fixed address then it never gets an IP address for the second NIC. We had reduced the range for the first card, we remmed it out - nothing did help. How have we to tell dnsmasq using the second card (and its dhcp range) too? Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] DHCP over 2 NICs
Hallo, Oliver, Du meintest am 28.02.12: dnsmasq finds the right interface with the static address automaticly. If you write interface=.. you discard the use of the others. Simply delete the interface=.. line and your dnsmasq should run fine. Just for curiosity: a) should we delete a line interface=lo too? b) what about a line for the special NIC for the router/modem: no-dhcp-interface=eth2 Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] DHCP over 2 NICs
Hallo, Oliver, Du meintest am 28.02.12: Just for curiosity: a) should we delete a line interface=lo too? Yes, of course. [...] b) what about a line for the special NIC for the router/modem: no-dhcp-interface=eth2 This is the opposite option of interface=.. Here you can explicitly exclude interfaces from _DHCP_ service (not DNS service!). This can be senseful in some cases. Thank you! Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] dnsmasq-2.59rc1
Hallo, Simon, Du meintest am 13.10.11: I propose to make a new release which fixes these and does nothing else in the next day or two. A release candidate for this is available at http://www.thekelleys.org.uk/dnsmasq/release-candidates/dnsmasq-2.59 rc1.tar.gz Anyone who can please check it out ASAP. Here: Slackware 13.37 (self made), kernel 2.6.39.2 Works (since 5 minutes) without any problem. But nearly all clients only use IPv4. Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] Lease Time Detail
Hallo, Pratik,
Du meintest am 22.09.11:
And can I pls ask u to show me a simple script to do so??? I m
totally naive for scripting so.. Thanks in advance.. :)
Just an example:
Part of /etc/dnsmasq.conf:
dhcp-script=/root/bin/clientname
Script /root/bin/clientname:
#! /bin/bash
# meldet den Client-Name fuer dnsmasq
# wird in der dnsmasq-Konfiguration von dhcp-script aufgerufen
test $DNSMASQ_SUPPLIED_HOSTNAME || exit
export LC_ALL=C
Log=/var/log/clients.log
echo -e ${2}\t${3}\t${DNSMASQ_SUPPLIED_HOSTNAME}\t$(date +%F\ %X) $Log
#
# -
That script has another purpose than you want, but you may see how to
use the dnsmasq variables.
You can see more details via
man dnsmasq
under -6 --dhcp-script
The meaning of ${1} to ${4} is explained under arguments in this
paragraph.
p.e.: ${2} contains the MAC address.
Viele Gruesse!
Helmut
Re: [Dnsmasq-discuss] Announce, dnsmasq-2.58.
Hallo, Simon, Du meintest am 26.08.11: Dnsmasq 2.58 is done, it's available from the usual place http://www.thekelleys.org.uk/dnsmasq/dnsmasq-2.58.tar.gz A slackware packet is available at http://helmut.hullen.de/filebox/Linux/slackware/n/dnsmasq-2.58-i486-1.txz Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] DNSmasq forwarding to DNS doesn't works
Hallo, Jérémie, Du meintest am 26.08.11: In the file resolv.conf: search city.domain.com nameserver 127.0.0.1 nameserver ISP 1 IP address1 nameserver ISP 1 IP address2 nameserver ISP 2 IP address1 nameserver ISP 2 IP address2 nameserver 127.0.0.1 seems to be ok - I use such a line on many systems for the many clients in the LAN. But if I have understood resolv.conf (and relating programs) correctly then only the first 3 nameserver entries (or the last 3?) are taken. Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] excluding sockets
Hallo, richardvo...@gmail.com, Du meintest am 01.06.11: can I exclude the file type socket from backing up? You probably should ask for help with backups on the listserv for your backup software. Sorry - wrong mailing list! Viele Gruesse! Helmut
[Dnsmasq-discuss] excluding sockets
Hallo, can I exclude the file type socket from backing up? Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] dhcp-script on dnsmasq
Hallo, Michael, Du meintest am 15.04.11: Is there a secret chroot or something going on that I don't know about? I'm running dnsmasq 2.57 and whenever I try to run my dhcp-script it bombs out saying failed to execute /tmp/post-lease.sh: No such file or directory However, if I say ls -l /tmp/post-lease.sh its most definitely exists and its chmodded 777 just to be safe. My relevant entry on my dnsmasq.conf is dhcp-script=/tmp/post-lease.sh /tmp is no good choice for a program which has to be executed in this case from dnsmasq. I prefer /root/bin for those scripts because managing dnsmasq is a pure root job; maybe FHS or other rule works propose other directories. What's the contents of your script? Just for testing you may use #! /bin/bash # just for testing Log=/var/log/dnsmasqscript.log date $Log echo Param1 = $1 $Log echo Param2 = $2 $Log echo Param3 = $3 $Log echo Param4 = $4 $Log # Script rights: root:root 700 Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] 2 PXE servers
Hallo, Miguel, Du meintest am 29.03.11: # Tipp von Clemens Fischer, dnsmasq-Mailingliste 12.6.2010 dhcp-mac = set:fog, 00:0d:60:76:4f:1c dhcp-mac = set:fog, 11:22:33:44:55:66 # may be repeated for other machines pxe-service = tag:fog,x86PC,fog,gpxelinux,192.168.0.5 pxe-service = tag:!fog,x86PC,Arktur,gpxelinux,192.168.0.1 # This is my current config in /etc/dnsmasq.conf: bogus-priv conf-file=/etc/dnsmasq/dhcp.conf dhcp-authoritative dhcp-lease-max=1000 dhcp-mac = set:fog, 00:01:2e:bc:2e:49 #MAC for zbox in living room pxe-service = tag:fog,x86PC,fog,gpxelinux,192.168.1.127 #xbmcMaster dhcp-boot=pxelinux.0 dhcp-boot=192.168.1.182 pxe-service=x86PC, pxelinux.0, pxelinux, 192.168.1.182 domain-needed domain=EXAMPLE.com expand-hosts no-negcache strict-order user=nobody I'm assuming that we created the tag fog, then we are using it to identify systems? If so, I could call it anything I want correct? fog and Arktur are just labels without any technical meaning; I've chosen the names of the corresponding hosts. The actual name is shown on the PXE-boot-screen of the client. I'm also assuming that it will read the config in sequence, so if it does not match the first PXE settings it will take the next as default. Or do I have to now list all MAC addresses and assign them to a tag and PXE configuration? Sorry - I don't know. I'm only a user, no code writer. Thanks for your prompt reply, wife has been sick so I have not had time to test this out. Cheers, Miguel On Mon, Mar 28, 2011 at 2:26 AM, Helmut Hullen hul...@t-online.de wrote: Hallo, Miguel, Du meintest am 28.03.11: I need to know if there is a way to configure dnsmasq to send specific MACs to a different PXE server. On my current setup I have a PXE server managed by cobbler, however I have some diskless clients that I need to go to a different PXE server. So I have a global next-server line that points to my cobbler and would like (hoping it can be done) to have a next-server line specific to a client's MAC address. Viele Gruesse! Helmut ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] 2 PXE servers
Hallo, Miguel, Du meintest am 28.03.11: I need to know if there is a way to configure dnsmasq to send specific MACs to a different PXE server. On my current setup I have a PXE server managed by cobbler, however I have some diskless clients that I need to go to a different PXE server. So I have a global next-server line that points to my cobbler and would like (hoping it can be done) to have a next-server line specific to a client's MAC address. # Tipp von Clemens Fischer, dnsmasq-Mailingliste 12.6.2010 dhcp-mac = set:fog, 00:0d:60:76:4f:1c dhcp-mac = set:fog, 11:22:33:44:55:66 # may be repeated for other machines pxe-service = tag:fog,x86PC,fog,gpxelinux,192.168.0.5 pxe-service = tag:!fog,x86PC,Arktur,gpxelinux,192.168.0.1 # Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] logging dns queries
Hallo, Carlos, Du meintest am 18.03.11: [...] I also noticed that the log messages in the /var/log/messages for the DHCP REQUEST/ACK the string after the hostname and before the [pid], (I assume this is the ident parameter to openlog), is 'dnsmasq-dhcp'. Am I to assume that --log-queries will produce a value of 'dnsmasq-dns' No, just dnsmasq. and other messages will produce just 'dnsmasq'? The others are only dnsmasq-tftp. And there's the place I am wishing and hoping: I'd be glad if I could work with something like dnsmasq-query or dnsmasq-dns too, in a way similar to dhcp-script. Viele Gruesse! Helmut
[Dnsmasq-discuss] logging dns queries
Hallo,
under ISC-bind I can log the DNS queries with
# Florian Weimer, d.c.o.u.networking.misc 15.2.2011
logging {
channel query_log {
file /var/log/named-query.log versions 5 size 20m;
print-time yes;
severity debug 3;
};
category queries { query_log; };
};
# -
and it's a fine help for finding p.e. conficker activities.
Can I tell dnsmasq too to log the queries?
Viele Gruesse!
Helmut
Re: [Dnsmasq-discuss] logging dns queries
Hallo, Olaf, Du meintest am 18.03.11: Can I tell dnsmasq too to log the queries? Find manual. Read manual. Look for --log-queries. It works - thank you! But it's not as comfortable as the ISC-bind form: there I can define a special log file only for named queries. Under dnsmasq there's only 1 log file for all messages (if I've understood this nice program right), and then it's an ugly job to find the few interesting lines in a rapidly growing file. In other words: can I tell dnsmasq to use one file for DHCP logging (that works - thanks to Simon), another file for named queries and a third file for all the other stuff? Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] logging dns queries
Hallo, Matthias, Du meintest am 18.03.11: Can I tell dnsmasq too to log the queries? Find manual. Read manual. Look for --log-queries. It works - thank you! But it's not as comfortable as the ISC-bind form: there I can define a special log file only for named queries. If you want BIND, use BIND. It's as simple as that. :-) But I don't want BIND. It's a monster. I believe that Simon's documentation is complete, in other words, all features are documented in the manual page. You believe wrong. Some days ago I was told some features around dhcp-script which I hadn't found in the documentation. And therefore I hope that the programmers know a simple but not yet documented way for separate log files too. Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] How to disable bootp and all pxe boot in Dnsamsq?
Hallo, Frank, Du meintest am 16.03.11: On 03/16/2011 12:46 PM, Helmut Hullen wrote: [rem out] dhcp-boot enable tftp tftp-root what version of dnsmasq you use? I tried this but dnsmasq can not start. dnsmasq-2.5.7 Starting dnsmasq: dnsmasq: missing parameter at line 91 of /etc/dnsmasq.conf Please: what's the contents of line 91? Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] How to disable bootp and all pxe boot in Dnsamsq?
Hallo, Frank, Du meintest am 16.03.11: In my subnet there is an bare metal provision system called linmin which will serve pxe installation, I am also using dnsmasq in same subnet as a programmable DHCP server. now I want to disable all bootp and pxe stuff in dnsmasq because if dnsmasq offers IP during pxe installation, the linmin system will not work. I see from the man page simply ignores parameter will disable the functionality, so I add dhcp-boot in /etc/dnsmasq.conf, unlucky the dnsmasq cannot start error message: Starting dnsmasq: dnsmasq: missing parameter at line 87 of /etc/dnsmasq.conf So what should I do to disable it? thank you. If I don't want PXE-Boot I'd rem out dhcp-boot enable tftp tftp-root Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] Announce: dnsmasq-2.57
Hallo, Simon, Du meintest am 18.02.11: dnsmasq 2.57 is now available at http://www.thekelleys.org.uk/dnsmasq/dnsmasq-2.57.tar.gz Binary for Slackware (current/13.x): http://helmut.hullen.de/filebox/Linux/slackware/n/dnsmasq-2.57-i486-1hln.txz Seems to run as expected - thank you! Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] client name via DHCP
Hallo, Carlos, Du meintest am 11.02.11: I'd be pleased if/when dnsmasq tells the client's hostname at least in one of its log messages. It does for me, with log-dhcp set: [...] I've just tried this additional option: it sends a lot of information - I'm sure I'll need them sometimes. But these informations make it even more difficult to find quickly the names of the clients. For this special purpose dhcp-scriptis a fine solution. Ok - I could grep the informations. But that has problems when the source file is rotated sometimes. Viele Gruesse! Helmut
[Dnsmasq-discuss] client name via DHCP
Hallo, when I use the ISC DHCP, then I can see the name of the Windows client in /var/state/dhcp/dhcp.leases. With dnsmasq as DNS and DHCP server I haven't found this feature - is it somewhere hidden? Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] client name via DHCP
Hallo, Richard,
Du meintest am 10.02.11:
when I use the ISC DHCP, then I can see the name of the Windows
client in /var/state/dhcp/dhcp.leases.
With dnsmasq as DNS and DHCP server I haven't found this feature -
is it somewhere hidden?
[...]
The hostname is in the dnsmasq.leases file. Exact directory depends
on how you installed dnsmasq. If you're using the leasefile-ro
option, then getting this information is dependent on your script
saving it somewhere. If the client doesn't send a hostname, the
hostname column will have * or the mac address.
Sorry - there's a difference:
ISC DHCP shows
lease 192.168.0.60 {
starts 4 2011/02/10 08:13:27;
ends 4 2011/02/24 08:13:27;
cltt 4 2011/02/10 08:13:27;
binding state active;
next binding state free;
rewind binding state free;
hardware ethernet 74:f0:6d:00:7b:f5;
uid \001t\360m\000{\365;
client-hostname KB-PC;
}
and dnsmasq shows
1305130516 74:f0:6d:00:7b:f5 192.168.0.60 Client-A60 01:74:f0:6d:00:7b:f5
The client's own name is KB-PC, dnsmasq reads Client-A60 from a list
on the server (which is completely independent from the real client's
name).
I want to see the real client's name, it's a better help for guessing
who's the owner of the machine.
Viele Gruesse!
Helmut
[Dnsmasq-discuss] cooperation with samba?
Hallo, in the samba mailinglist there was a remark that samba 4 is designed only for the BIND nameserver; look escpecially at http://lists.samba.org/archive/samba/2011-February/160848.html I know that most programmers work in their free time (me too). But I don't like working with the ISC DNS, and I'd like working with dnsmasq under samba 4 too. Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] next server and vendor encapsulated
Hallo, clemens, Du meintest am 12.06.10: I'm searching for a way which looks like the next server option but does not work everytime but only under special conditions. Pseudo code: if MAC = 11.22.33.44.55.66 then goto (PXE-)server 10.11.12.13 if MAC in MAC-list then goto (PXE-)server 172.16.17.18 vendor encapsulated may do this job but it's not well documentated. Might not be needed: dhcp-mac = set:special, 11.22.33.44.55.66 dhcp-mac = set:default, 12.23.34.45.56.67 dhcp-mac = set:default, repeat for other NICs in list pxe-service = tag:special, ..., 10.11.12.13 pxe-service = tag:default, ..., 172.16.17.18 This is the new tagging system in recent versions. It's all in the manual ... Looks nice - thank you! Just an idea: I may put the dhcp-mac = set:special, ... lines into a special file in the directory defined with conf-dir. Perhaps with a leading pxe-service = tag:special, What about defaults, wild cards etc? My favorite solution is (in pseudo code) if exists $conf-dir/mac-special-list then use special pxe server for these MAC addresses else use normal pxe server Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] next server and vendor encapsulated
Hallo, Clemens, Du meintest am 12.06.10: I'm searching for a way which looks like the next server option but does not work everytime but only under special conditions. Pseudo code: if MAC = 11.22.33.44.55.66 then goto (PXE-)server 10.11.12.13 if MAC in MAC-list then goto (PXE-)server 172.16.17.18 dhcp-mac = set:special, 11.22.33.44.55.66 dhcp-mac = set:default, 12.23.34.45.56.67 dhcp-mac = set:default, repeat for other NICs in list pxe-service = tag:special, ..., 10.11.12.13 pxe-service = tag:default, ..., 172.16.17.18 This is the new tagging system in recent versions. It's all in the manual ... My first trial: Dnsmasq version 2.52 - dhcp-mac = set:fog, 11.22.33.44.55.66 # beliebig oft zu wiederholen pxe-service = tag:fog,x86PC,fog,192.168.0.5 pxe-service = tag:!fog,x86PC,Arktur,192.168.0.1 # - But that produces an error message in the pxe-service line(s). What is still wrong? Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] next server and vendor encapsulated
Hallo, Jan, Du meintest am 13.06.10: - dhcp-mac = set:fog, 11.22.33.44.55.66 # beliebig oft zu wiederholen pxe-service = tag:fog,x86PC,fog,192.168.0.5 pxe-service = tag:!fog,x86PC,Arktur,192.168.0.1 # - But that produces an error message in the pxe-service line(s). What is still wrong? The dnsmasq version, the tagging system is new in 2.53 aka 2.54 Compiling 2.55 solved that problem - thank you. For all friends of Slackware 13.x http://arktur.shuttle.de/CD/Zusatzpakete/dnsmasq-2.55-i486-1hln.txz Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] next server and vendor encapsulated
Hallo, clemens, Du meintest am 12.06.10: I'm searching for a way which looks like the next server option but does not work everytime but only under special conditions. Pseudo code: if MAC = 11.22.33.44.55.66 then goto (PXE-)server 10.11.12.13 if MAC in MAC-list then goto (PXE-)server 172.16.17.18 dhcp-mac = set:special, 11.22.33.44.55.66 dhcp-mac = set:default, 12.23.34.45.56.67 dhcp-mac = set:default, repeat for other NICs in list pxe-service = tag:special, ..., 10.11.12.13 pxe-service = tag:default, ..., 172.16.17.18 This is the new tagging system in recent versions. Next try, with dnsmasq-2.55 dhcp-mac = set:fog, 00:0d:60:76:4f:1c pxe-service = tag:fog,x86PC,fog,gpxelinux,192.168.0.5 pxe-service = tag:!fog,x86PC,Arktur,gpxelinux,192.168.0.1 # Messages: Auto-select: fog BOOT Server IP: 192.168.0.5 ... gPXE initialising devices ... - It recognizes the desired next server, it tells the desired string. But then it loads and shows the boot menu of server Arktur, not of server fog. Even when I change the IP address of the second server (which is the DHCP server too) to 192.168.0.5 the system only shows the boot menu from server Arktur = 192.168.0.1 How can/must I tell the machine the place of the desired boot menu? Viele Gruesse! Helmut
[Dnsmasq-discuss] next server and vendor encapsulated
Hallo, I'm searching for a way which looks like the next server option but does not work everytime but only under special conditions. Pseudo code: if MAC = 11.22.33.44.55.66 then goto (PXE-)server 10.11.12.13 if MAC in MAC-list then goto (PXE-)server 172.16.17.18 vendor encapsulated may do this job but it's not well documentated. Where can I get more information? About 3 years ago Simon had mentioned this option too ... Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] segfault - Re: No dnsmasq after starting openVPN?!
Hallo, Jan, Du meintest am 08.06.10: 2.55 in the process of release now. Wow, less than 12 hours later the new (and working, did a --reinstall) version is already in debian/sid. on June 07, 2010 23:24 new release: net-dns/dnsmasq-2.55 :-) (source: http://gitorious.org/jasiu) Gentoo ;-) rant for Gentoo that's normal speed. But for Debian that's more than hyperspeed. /rant Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] tftp 'Permission denied' issue...
Hallo, Steve, Du meintest am 15.05.10: But I do launch with sudo /etc/rc.d/initd/dnsmasq So it seems that it will be run by root. Therefore I need world readable permission on my bootrom.pxe.0. I thought I had that! --- /home/Steve/Shared/workspace/xxx/xxx/ -rwxrwxr-x. 1 Steve Steve 482040 2010-05-13 17:32 bootrom.pxe.0 --- world may need the x rights (go into the next subdir) in the directory tree too. Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] tftp 'Permission denied' issue...
Hallo, Steve, Du meintest am 14.05.10: Can anyone suggest why I get 'Permission denied' for this access? May 14 16:01:27 regret dnsmasq-tftp[13285]: cannot access /home/Steve/Shared/workspace/xxx/xxx/bootrom.pxe.0: Permission denied May 14 16:01:27 regret dnsmasq-tftp[13285]: cannot access /home/Steve/Shared/workspace/xxx/xxx/bootrom.pxe.0: Permission denied ftp_root=/home/Steve/Shared/workspace /home/Steve/Shared/workspace/xxx/xxx/ -rwxrwxr-x. 1 Steve Steve 482040 2010-05-13 17:32 bootrom.pxe.0 Are you allowed to put this directory to /tftpboot with the directory rights 755? Or to /home/Steve/PXE with 755 for /home/Steve and /home/Steve/ PXE? Seems to be a PXE problem. Viele Gruesse! Helmut
[Dnsmasq-discuss] seperate DHCP- and PXE-Server
Hallo, how can I put the PXE server onto another machine than the DHCP server? I have 2 servers in my LAN, 192.168.0.1 and 192.168.0.7 When I stop the dnsmasq on one of the machines and run the other as a PXE and DHCP server, with dhcp-boot=pxelinux.0 then all works fine. When I only stop the DHCP server on the second machine with no-dhcp-interface=eth0 then this machine works as desired: no DHCP (the first machine makes the DHCP server as desired). But when I tell the first machine (which shall work only as the DHCP server, not as the PXE server) dhcp-boot=pxelinux.0,192.168.0.7 it ignores the IP address of the second server and works instead as the LAN PXE server - what goes wrong? Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] seperate DHCP- and PXE-Server
Hallo, , Du meintest am 27.03.10 zum Thema Re: [Dnsmasq-discuss] seperate DHCP- and PXE-Server: how can I put the PXE server onto another machine than the DHCP server? I have 2 servers in my LAN, 192.168.0.1 and 192.168.0.7 You can use proxy DHCP feature of Dnsmasq on the second machine and DHCP-only on first machine. Second server will answer on PXE requests only, first server will answer on DHCP requests only, both servers simultaneously will act as PXE-server. Meaningful parts of configs: Proxy DHCP server: pxe-service=x86PC,Network boot,pxelinux dhcp-range=192.168.0.0,proxy DHCP-only server: dhcp-range=192.168.0.20,192.168.0.50,12h Doesn't work - sorry. The system sees that the DHCP server makes no PXE, but it doesnt't lead the PXE request to the second machine. Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] generating hostname on the fly, base on mac address,
Hallo, Simon, Du meintest am 05.03.10: You could put the name/MAC mappings in a separate file, and load it using dhcp-hostsfile. That's nearly the way I prefer: In file /etc/dnsmasq.conf conf-dir=/etc/dnsmasq.d In directory /etc/dnsmasq.d file dhcp.conf which contains lines like dhcp-host=Thinkpad,192.168.0.41,11:22:33:44:55:66,180d You can re-load the contents of that without having to restart dnsmasq by sending SIGHUP to the process. For sysv or equivalent rc files: case $1 in start) # do something ;; stop) # do something ;; reload) pgrep -x dnsmasq /dev/null killall -HUP dnsmasq # killall for Linux systems ;; *) # do something ;; esac Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] Fwd: troubles with cname
Hallo, Samuel, Du meintest am 04.03.10: Well, that's the day I posted my first message here On 27. february 2010, perhaps written on 26. february 2010 (PST). I though it was a pretty stupid question, but still have no answer... So, I'll assume nobody recieved it, and I send it again... I've got your first mail the same day (27.02.2010). But I don't know a good answer - sorry. Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] List problems.
Hallo, Simon, Du meintest am 04.03.10: It seems that mailman went down at the end of last week, and since then until earlier the morning, no mail was processed for the list. Seems to be a hole from 28 february (no mail) to 3 march. On 4 march I got mail from 1.3. to 3.3. (not many, as few as usual). U-Received: from localhost ([127.0.0.1] helo=thekelleys.org.uk) by thekelleys. org.uk with esmtp (Exim 3.36 #1 (Debian)) id 1Nn5Zl-00055R-01; Thu, 04 Mar 2010 07:34:29 + U-Received: from mx1.redhat.com ([209.132.183.28]) by thekelleys.org.uk with esmtp (Exim 3.36 #1 (Debian)) id 1Nm732-0002n9-00 for dnsmasq- disc...@thekelleys.org.uk; Mon, 01 Mar 2010 14:56:40 + U-Received: from int-mx08.intmail.prod.int.phx2.redhat.com (int-mx08.intmail. prod.int.phx2.redhat.com [10.5.11.21]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o21Eud5H031561 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for dnsmasq-disc...@thekelleys.org.uk; Mon, 1 Mar 2010 09:56:39 - 0500 Looks like a problem in your system. Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] IP address based on switch port number (option 82)
Hallo, Jan, Du meintest am 18.02.10: I see where this will all lead to ... a tag construction tool with dnf generation and Quine?McCluskey minimizer. Quine/McCluskey is an awful way to minimize DNF etc. Slow and greedy. But that's another problem ... Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] How to configure 2 different nets: 1 guestnet, 1 known-host net?
Hallo, Simon, Du meintest am 16.02.10: It's in the man page: The end address may be replaced by the keyword static which tells dnsmasq to enable DHCP for the network specified, but not to dynamically allocate IP addresses: only hosts which have static addresses given via dhcp-host or from /etc/ethers will be served. I'll add an example too. My example (or my problem installation): A school (boarding school, Internat) with clients in computer rooms and (many) private laptops and notebooks. The school clients get static adresses via DHCP (and other privileges) in net 192.168.0.0, and the private clients get their IP adresses (with lower privileges) in net 192.168.1.0. Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] Setting dnsmasq as a orwarder
Hallo, Simon, Du meintest am 05.02.10: The topology would be that dns1 and dns2 are only able to locally resolve requests for their respective domains, and any other requests are routed to dns0, that then forwards them to dns1 or dns2 as appropiate. Is that possible? server=/net1.local/192.168.1.2 Just to reduce my confusion: In the template for dnsmasq.conf (version 2.49) there are examples for server= and for --server=. Is --server= a copypaste error? Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] Help Translating DNSMasq options for NetBoot Mac
Hallo, Max, Du meintest am 30.01.10 zum Thema [Dnsmasq-discuss] Help Translating DNSMasq options for NetBoot Mac: option root-path nfs:192.168.33.1: /var/lib/tftpboot:Diag106NetBoot.nbi/NetBoot.dmg; dhcp-option=net:AppleNBI-i386,option:root-path,nfs:192.168 .33.1: /var/lib/tftpboot:Diag106NetBoot.nbi/NetBoot.dmg Your root-path option looks strange (for me): must be a directory, no file. Is NetBoot.dmg a directory? Is tftpboot:Diag106NetBoot.nbi a subdirectory? Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] more than one DHCP net
Hallo, Simon, Du meintest am 29.01.10: With one card I set the dhcp range via dhcp-range=192.168.0.60,192.168.0.240,3d Can I add the second card via a second line dhcp-range=192.168.1.20,192.168.1.240,3d The answer is simple - yes, that will work fine. Thank you - I'll try! Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] windows' hostname
Hallo, Brad, Du meintest am 02.12.09: Can dnsmasq set the hostname for a windows station? I ghosted an image across 5 computers and now they all have the same hostname. [...] You are going to have more problems than just the hostname with your Windows systems. They also have duplicate system identifications (SIDs). You will need to run a program like NewSID (http://technet.microsoft.com/en-us/sysinternals/bb897418.aspx) on each system. You can change the hostname as well at this time. Take a look at http://blogs.technet.com/markrussinovich/archive/2009/11/03/3291024.aspx especially SID Duplication (ok - it's not related in any way to dnsmasq) Regards, Brad ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] router won't query itsself
Hallo, JD, jd1...@gmail.com meinte am 12.08.09 in dnsmasq zum Thema Re: [Dnsmasq-discuss] router won't query itsself: /etc/resolv.conf must ONLY contain nameserver 127.0.0.1 AND /etc/dnsmasq.conf must set resolv-file=/etc/resolv.dnsmasq Or whatever you decide to call that file, which contains the list of the real nameservers. Just a (not tested) idea: pppoe and router connections into the WAN lead (in many distributions) to a file /etc/ppp/resolv.conf which contains the 2 nameservers the ISP proposes. resolv-file may lead to this file. Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] extension of configuration files
Hallo, Simon, Du meintest am 06.07.09: Under my slackware installation I'll write my special slackware extension watcher ... it first has to look what's the name of conf- dir. Ugly. There's an alternative which is backwards compatible: extend the --conf-dir option optionally allow extensions which should _NOT_ be used, so the correct form to solve the initial problem would be --conf-dir=/etc/dnsmasq.d,.new I guess that for completeness, more than one extension should be allowed. Sounds very good - thank you! Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] extension of configuration files
Hallo, Simon, Du meintest am 06.07.09: --conf-dir=/etc/dnsmasq.d,.new I guess that for completeness, more than one extension should be allowed. http://www.thekelleys.org.uk/dnsmasq/test-releases/dnsmasq-2.50test6.tar.gz which implements it (many extensions). Works like a charm - thank you! One more problem solved. Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] extension of configuration files
Hallo, RevRagnarok, Du meintest am 05.07.09 zum Thema Re: [Dnsmasq-discuss] extension of configuration files: Could dnsmasq exclude *.new files from reading? Some other programs do so. By extension, it should probably just ignore everything not *.conf, since other package managers use other methods, e.g. .rpmnew and .rpmold. Sounds reasonable. Please keep the traffic in the mailing list! Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] extension of configuration files
Hallo, Rance, Du meintest am 05.07.09: Could dnsmasq exclude *.new files from reading? Some other programs do so. By extension, it should probably just ignore everything not *.conf, since other package managers use other methods, e.g. .rpmnew and .rpmold. I think this is a great idea but I don't think it belongs in dnsmasq proper. I think it makes the code base bigger for no real feature gain. ??? Instead of include $conf-dir/* there would be include $conf-dir/*.conf Nothing more to do. This is something that could be handled in an init script stanza prior to actually launching dnsmasq. set a variable for the main config file parse it looking for config_dir if found, check contents for updated scripts (test will be different for each distro I suspect) mv the updated files to config_dir.update start dnsmasq the normal way I may not write (and test, and debug) such a wrapper ... Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] DNSMASQ and configuring Win XP boxes to use a Proxy server
Hallo, Simon, Du meintest am 05.02.09: But that happens with the above line and also without it - for what is the option good? I'm confused, if you set Automatic proxy then Firefox should find the proxy via WPAD. Is that working? Oh - I just see that WPAD is a special protocol. Not an arbitrary name of a file. The last years I have worked with netscape.pac - it's Java style, like the *.js files for netscape and firefox. It's the Proxy Auto Config protocol (is it a protocol?). I'll have to read and work with WPAD some time. Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] DNSMASQ and configuring Win XP boxes to use a Proxy server
Hallo, Simon, Du meintest am 05.02.09: Oh - I just see that WPAD is a special protocol. Not an arbitrary name of a file. I'll have to read and work with WPAD some time. http://www.ietf.org/proceedings/99nov/I-D/draft-ietf-wrec-wpad-01.txt and http://wpad.com/ (among the warnings from the german wikipedia side about WPAD) But some of the WPAD warnings are not exclusively only for (not) using WPAD. Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] DNSMASQ and configuring Win XP boxes to use a Proxy server
Hallo, Simon,
Du meintest am 24.10.08 zum Thema Re: [Dnsmasq-discuss] DNSMASQ and configuring
Win XP boxes to use a Proxy server:
I was wondering is someone has managed to get Windows XP boxes setup
so that they would get proxy details from DNSMASQ? Any details would
be appreciated.
If someone has a suggestion on a better/easier way, I would be
willing to entertain the idea.
In /etc/dnsmasq.conf:
dhcp-option=252,http://central/wpad.dat;
and then in www-root/wpad.dat:
function FindProxyForURL(url, host)
{
if (isPlainHostName(host) ||
isInNet(host, 192.168.0.0, 255.255.252.0))
return DIRECT;
else
return PROXY central:3128;
}
My http server and proxy is called central.
I've now tried it - doesn't work. Sorry.
Configuration:
PXE boot (RIPlinux),
the file (your name: wpad.dat) exists,
if I choose the firefox option
Edit/Preferences/Advanced/Network/Settings/Automatic proxy ...
then it works as desired.
And the DHCP part of dnsmasq works well too.
But without the special firefox entry the client doesn't see the proxy
options - how can I test if (and/or how) the dhcp-option 252 does work?
Viele Gruesse!
Helmut
Re: [Dnsmasq-discuss] Multiple Resolv Files?
Hallo, Petri, Du (petri.savilahti) meintest am 07.11.08: Is it possible to read nameservers from multiple resolv files? For example from the normal /etc/resolv.conf and the /etc/ppp/resolv.conf. If I have understood the mechanics correct: first hit wins. And /etc/ resolv.conf is asked/searched first. Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] Multiple Resolv Files?
Hallo, Simon, Du (simon) meintest am 07.11.08: Is it possible to read nameservers from multiple resolv files? For example from the normal /etc/resolv.conf and the /etc/ppp/resolv.conf. Yes, you can specify as many as you like and dnsmasq will use the one which was altered last. Ok - I changed /etc/resolv.conf last ... But there is (or may be) another problem: The ppp daemon may change /etc/ppp/resolv.conf (you can tell him what and where to change). And in this file you cannot tell domain xyz and the LAN nameserver, the ppp daemon writes it completely new. Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] Reverse DNS
Hallo, shacky, Du (shacky83) meintest am 04.10.08: But dnsmasq does not restart: server:~# /etc/init.d/dnsmasq restart Restarting DNS forwarder and DHCP server: dnsmasqdnsmasq: error at line 29 of /etc/dnsmasq.conf. What is the content of this line? Might it be dnsmasqdnsmasq? Viele Gruesse! Helmut
[Dnsmasq-discuss] whois doesn't find entries
Hallo, dnsmasq seem to have sometimes problems with whois (and related programs). whois 128.163.2.43 doesn't send a whois entry, but when I change from dnsmasq to bind I get the desired information. The above IP address is just an example, not the only problematic address. Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] bad command line options: illegal repeated flag
Hallo, Simon, Du (simon) meintest am 27.07.08: installed. When it launches from /etc/init.d/dnsmasq, it reports: Shutting down dnsmasq: [ OK ] Starting dnsmasq: dnsmasq: bad command line options: illegal repeated flag [FAILED] running sh -x /etc/init.d/dnsmasq will tell you what's happening. I'd prefer sh -x /etc/init.d/dnsmasq start Viele Gruesse! Helmut
Re: [Dnsmasq-discuss] 2.43rc5
Hallo, Simon, Du (simon) meintest am 10.07.08: Is there. This (I hope) fixes the capabilties bug seen by Jean, Olaf and Jamie. Works under Slackware 11.0 and 12.1 - thank you! Viele Gruesse! Helmut
