[Dnsmasq-discuss] Specify DHCP range based on Mac ADdress
Hello, I am looking to have two dhcp ranges: Range 1- will only be allows to be used by specific MAC Addresses. Range 2- will be used by all other MAC Addresses. ie: dhcp-range=tag:bypass,10.3.0.70,10.3.0.99,72h dhcp-range=tag:!bypass,10.3.0.100,10.3.0.199,72h Found reference here: http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2011q1/004846.html then I would set the following. dhcp-host=00:0e:35:47:9e:5f,set:bypass The question is, can I leave the dhcp options (gateway, dns, ntp,etc) as follows (dhcp-option=42,10.3.0.2), or do I have to assign those also? dhcp-option=tag:bypass,42,10.3.0.2 dhcp-option=tag:!bypass,42,10.3.0.2 Even though it both entries will point to the same location? Thank you ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
[Dnsmasq-discuss] Multiple DHCP ranges
Hello, I am looking to setup two DHCP ranges, one would bypass a proxy and the other wouldn't. dnsmasq should be able to use MAC address of the hardware to decide which range it should fall into. I would like to confirm that the following config would work. dhcp-range=tag:bypass,10.3.0.70,10.3.0.99,72h #2013-09-26 DHCP-RANGE Bypass Proxy HArdware dhcp-range=10.3.0.100,10.3.0.199,72h #2010-10-07 DHCP-RANGE PROXY HARDWARE dhcp-host=00:0e:35:47:9e:5f,set:bypass # Sheilaslaptop dhcp-host=88:c6:63:41:e4:0f,set:bypass #Sheilas-iPod dhcp-host=00:27:09:5e:05:77,set:bypass #Wii dhcp-host=00:1d:c0:03:6e:57,set:bypass #envoy dhcp-host=00:40:ad:1e:d0:cf,set:bypass #webbox150053455 dhcp-host=a0:6c:ec:d9:8f:e9,set:bypass #BLACKBERRY-036A The way I understand the two dhcp-range, is that if the hardware isn't set as bypass, it should fall into the second dhcp-range. Now if I didn't set any tag to the NTP, Gateway, DNS options, they would apply to both ranges, dhcp-option=42,10.3.0.2 #NTP dhcp-option=3,10.3.0.2 #gateway dhcp-option=6,10.3.0.2, 10.3.0.1 #DNS Thank you Philippe ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Hardcoding a DNS entry
Hello Mauricio, thank you for your reply. I have a couple issues/questions: 1- enable-ra seems to be applicable to version 2.60 and beyond, I am running Ubunutu 12.04 LTS, which forces me to stick to 2.59 unfortunately. there is bound to be a way around this, but I haven't figure that out yet. 2- from what I found online, it would see that enable-ra is only applicable to IPV6. I am running ipv4 here. 3- I was hoping that there was a way to manually add entries to the dnsmasq.lease file? For example, if you put into the config file DNS-entry = 192.168.1.1 : Router dnsmasq would add to the dnsmasq.lease file automatically the entry at startup, that way, the association would be made everytime dnsmasq starts up. From what I can tell, it doesn't seem to be the case. Philippe Quoting Mauricio Tavares : On Mon, Jan 21, 2013 at 9:19 PM, Philippe Faure wrote: Hello, I have a question. I have a router (Upstairs_router) which has an ip address of 10.3.0.3. I would like to add that entry into the DNS portion of dnsmasq. I had a look at the man page but couldn't find anything. I was wondering if there was something simple? Do you mean something on the lines of http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2012q1/005533.html ? Thank you Philippe ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
[Dnsmasq-discuss] Hardcoding a DNS entry
Hello, I have a question. I have a router (Upstairs_router) which has an ip address of 10.3.0.3. I would like to add that entry into the DNS portion of dnsmasq. I had a look at the man page but couldn't find anything. I was wondering if there was something simple? Thank you Philippe ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
[Dnsmasq-discuss] DNS query
I have noticed something a little strange in my Log files. ombellenature.com was forwarded to 8.8.4.4. Where it got the response NODATA-IPV6 the promptly tried to add several domain names (which aren't valid) and got NXDOMAIN-IPv6 When it tried again to forward the same request to 8.8.4.4 it got an reply 188.165.218.49, but still then proceeded to try to add domain names. then tried to ask itself again the same question, and kept in the cache NODATA-IPv6. What in the config file might be causing this? see attached log parts. I have noticed that this also occurs with other domains. Thank you Philippe dnsmasq.log Description: Binary data ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
[Dnsmasq-discuss] DHCP setup
Thank you Stefano for your reply. Sorry for the delay. I believe that I have figured out what was going on. We are running vtund. It use iptables to filter what goes over the tunnel or not. After a little digging and trial/error. I was able to find a way a single command that will stop each DHCP server from sending replies to DHCPREQUESTS from other locations. firewall "-t filter -A FORWARD -p udp --dport 67:68 -j DROP"; This will drop any packets that are going to be forwarded over the tunnel for destination ports 67 (DHCPREQUEST) and 68 (DHCPACK). I thought that I would send this to the list for anyone who might be able to use this information. Philippe Quoting Stefano Bridi : I suppose you are using bridged VPN (same subnet in every city) so if you are already in a routed setup drop my email in the recycle bin and please describe better the setup I dont' know if there are settings in dnsmasq to help you in this specific situation.. Anyway you can solve migrating the infrastructure to a routed VPN (big step) Or at least you can filter out the DHCP request from the vpn. A routed setup give you more control and don't forward broadcast everywere, off course you need DNS/WINS working. Stefano On Mon, Oct 4, 2010 at 3:15 AM, Philippe Faure wrote: Hello, I didn't hear back from anyone, so I thought that I would try to see if my request makes sense. I have dnsmasq running on 3 separate servers, each in different cities. They are all connected via a secure tunnel. I was finding that DHCP request made in location A is being answered by the DHCP server in location B. Currently to avoid this issue, I am using: dhcp-host=00:0e:35:f6:d8:af,ignore as a way to stop server B handling requests that typically should be handled by server A. This means that each time new hardware is brought online, the dnsmasq.conf files need to be updated in the other two locations so that they ignore hardware that doesn't belong to them. Do you know if there is a better way of handling this issue? Since what does happen from time to time, is that devices normally associated with Location A do visit Location B. so hen the DHCP assignment comes from the hardware's home location, and not the closest server. Is there a way to use the IP of the local router to accept DHCP request, if the request comes from a router from a different location, pr the tunnel then ignore that request? I believe that this would be a cleaner solution, but just not sure of how to implement it. Even if it is possible. Thank you Philippe ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] DHCP setup
Hello, To be honest, my brother set up the tunneling network, and I was just poking at it out of curiosity. I did do some digging last night and found that we are using vtund as the software to implement the tunnel. Each "node" of the network has an allocated network range (limited by the routers) 192.168.0.1-32 location A 192.168.0.33-64 location B etc Looking into vtund it would seem that we are using iptable like rules to do the filtering. I know that this is now a little off topic, but I believe that the following string would provide what I am looking for. firewall "-t raw -A OUTPUT -i br0 -p udp -s 255.255.255.255 --dport 67 -j DROP"; I have tried: firewall "-t raw -A OUTPUT-p udp -d 255.255.255.255 --destination-port 67:68 -j DROP"; but found that it stopped dnsmasq functioning at all. Has someone else tried to use this setup? Not knowing a lot about iptables, have someone's expert input would be greatly appreciated. Thanks Philippe Quoting Stefano Bridi : I suppose you are using bridged VPN (same subnet in every city) so if you are already in a routed setup drop my email in the recycle bin and please describe better the setup I dont' know if there are settings in dnsmasq to help you in this specific situation.. Anyway you can solve migrating the infrastructure to a routed VPN (big step) Or at least you can filter out the DHCP request from the vpn. A routed setup give you more control and don't forward broadcast everywere, off course you need DNS/WINS working. Stefano On Mon, Oct 4, 2010 at 3:15 AM, Philippe Faure wrote: Hello, I didn't hear back from anyone, so I thought that I would try to see if my request makes sense. I have dnsmasq running on 3 separate servers, each in different cities. They are all connected via a secure tunnel. I was finding that DHCP request made in location A is being answered by the DHCP server in location B. Currently to avoid this issue, I am using: dhcp-host=00:0e:35:f6:d8:af,ignore as a way to stop server B handling requests that typically should be handled by server A. This means that each time new hardware is brought online, the dnsmasq.conf files need to be updated in the other two locations so that they ignore hardware that doesn't belong to them. Do you know if there is a better way of handling this issue? Since what does happen from time to time, is that devices normally associated with Location A do visit Location B. so hen the DHCP assignment comes from the hardware's home location, and not the closest server. Is there a way to use the IP of the local router to accept DHCP request, if the request comes from a router from a different location, pr the tunnel then ignore that request? I believe that this would be a cleaner solution, but just not sure of how to implement it. Even if it is possible. Thank you Philippe ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
[Dnsmasq-discuss] DHCP setup
Hello, I didn't hear back from anyone, so I thought that I would try to see if my request makes sense. I have dnsmasq running on 3 separate servers, each in different cities. They are all connected via a secure tunnel. I was finding that DHCP request made in location A is being answered by the DHCP server in location B. Currently to avoid this issue, I am using: dhcp-host=00:0e:35:f6:d8:af,ignore as a way to stop server B handling requests that typically should be handled by server A. This means that each time new hardware is brought online, the dnsmasq.conf files need to be updated in the other two locations so that they ignore hardware that doesn't belong to them. Do you know if there is a better way of handling this issue? Since what does happen from time to time, is that devices normally associated with Location A do visit Location B. so hen the DHCP assignment comes from the hardware's home location, and not the closest server. Is there a way to use the IP of the local router to accept DHCP request, if the request comes from a router from a different location, pr the tunnel then ignore that request? I believe that this would be a cleaner solution, but just not sure of how to implement it. Even if it is possible. Thank you Philippe
[Dnsmasq-discuss] DHCP setup
Hello, I have dnsmasq running on 3 separate servers, each in different cities. They are all connected via a secure tunnel. I was finding that DHCP request made in location A is being answered by the DHCP server in Location B. Currently to avoid this issue, I am using: dhcp-host=00:0e:35:f6:d8:af,ignore as a way to stop server B handling requests that typically should be handled by server A. Does someone know of a better way of handling this issue? Since what does happen from time to time, is that devices normally associated with Location A do visit Location B, and then will a DHCP reply from the DHCP server in location A. Is there a way to use the IP of the local router to accept DHCP request, if the request comes from a router from a different location, then ignore that request? this would be a cleaner solution. Thank you Philippe
Re: [Dnsmasq-discuss] DNS search Order
I was wondering with version 2.51, will the 10 seconds, and 50 queries be configurable? No easily, it's in the set of parameters at the start of src/config,h that can be changed by recompilation (I wonder if anyone has ever tunned any of those: I doubt it) I am thinking under a light load, where requests are sent out less than once every 10 seconds, then I am sending to every DNS server every time. Just a thought. Philippe
[Dnsmasq-discuss] DNS search Order
Hello, I was wondering how does DNSMASQ use the DNS servers that it knows about. If "strict-order" is enabled, it uses them in the order found in the dnsmasq.conf file. If the first server doesn't reply, or can't answer, then it goes and tries the next one and so on. But if "strict-order" isn't enabled. How does DNSMASQ know which server(s) to contact? Does it use them all all the time? If not how does it determine which server to contact? How long does an entry in the cache remain valid before it checks again? thank you Philippe
[Dnsmasq-discuss] Dnsmasq
Quoting dnsmasq-discuss-requ...@lists.thekelleys.org.uk: Send Dnsmasq-discuss mailing list submissions to dnsmasq-discuss@lists.thekelleys.org.uk To subscribe or unsubscribe via the World Wide Web, visit http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss or, via email, send a message with subject or body 'help' to dnsmasq-discuss-requ...@lists.thekelleys.org.uk You can reach the person managing the list at dnsmasq-discuss-ow...@lists.thekelleys.org.uk When replying, please edit your Subject line so it is more specific than "Re: Contents of Dnsmasq-discuss digest..." Today's Topics: 1. location of cached addresses (Audio Phile) 2. dnsmasq question - running as root or user (Audio Phile) -- Message: 1 Date: Sat, 22 Aug 2009 02:30:18 -0700 (PDT) From: Audio Phile Subject: [Dnsmasq-discuss] location of cached addresses To: dnsmasq-discuss@lists.thekelleys.org.uk Message-ID: <333252.62939...@web36608.mail.mud.yahoo.com> Content-Type: text/plain; charset=us-ascii I read the man page for dnsmasq but still have no idea where dnsmasq stores its list of cached addresses. If the answer is in RAM, is there an option I can use in my /etc/dnsmasq.conf to allow this to be on my file system so that the list survives a reboot? -- Message: 2 Date: Sat, 22 Aug 2009 02:39:59 -0700 (PDT) From: Audio Phile Subject: [Dnsmasq-discuss] dnsmasq question - running as root or user To: dnsmasq-discuss@lists.thekelleys.org.uk Message-ID: <843901.7...@web36608.mail.mud.yahoo.com> Content-Type: text/plain; charset=us-ascii 1) What is the advantage of having dnsmasq run as a non-root user? 2) Is there any kernel module required to do so on 2.6.30? According to some old docs, there was a requirement CONFIG_SECURITY_CAPABILITIES parameter, but it obsolete on kernel versions >2.6.26 (reference 1). Nor does it appear in the config documentation for the latest kernel (reference 2). 1) http://cateee.net/lkddb/web-lkddb/SECURITY_CAPABILITIES.html 2) http://www.kernel.org/doc/menuconfig/x86.html -- ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss End of Dnsmasq-discuss Digest, Vol 51, Issue 13 ***
Re: [Dnsmasq-discuss] TFTP Boot update "for those who find this problem in the future"
The issue isn't really with the boot client, but with my network. I had to pair back the MTU size, so the blocks being handed out are smaller than what is normal (set to 1400). There is something "fishy" with my router, ISP and work network, that it wouldn't let me access the my home server from work. I completely forgot about this limitation till Simon mentioned blocksizes while debugging this problem. (I am going to be replacing the router soon). Because of this limitation, the TFTP had problems. I would suggest to leave things the way they are, but have the tftp-no-blocksize as an option. Since my case is the special case, probably not the norm. Philippe Quoting "richardvo...@gmail.com" : I can't think of a single circumstance where a manufacturer-provided boot PROM would have more appropriate network-specific settings than the TFTP server configuration. Maybe tftp-no-blocksize should be set by default (with a tftp-honor-blocksize to negate it). But I don't use BOOTP remote booting, so Simon probably has good reasons for doing things the way they are. On Mon, Aug 24, 2009 at 8:01 PM, Philippe Faure wrote: It would seem that the network MTU was my limiting factor. With Simon's Help, we were able to find the problem and solution. My config file didn't mention (being that it was too old) the switch, tftp-no-blocksize Adding it, and restarting dnsmasq, the new system booted straight to the install page. I am using a boot client that is part of the motherboard. MB: Asus, M4N78 Pro Nvidia Boot Agent version: 249.0542. Snip from Simon's Email OK, it looks like the client is asking for a blocksize (ie packetsize) of 1456 bytes, and that's too big for your network. Because of that the packets are getting fragmented and that's really confusing the client: in the end the client does something really strange which provokes the "unsupported request" error. Try adding tftp-no-blocksize to /etc/dnsmasq.conf. That will cause dnsmasq to reject the request from the client for bigger blocks, and may be enough to make it all work. Alternatively if you can increase the MTU on the network that might fix things. Philippe ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
[Dnsmasq-discuss] TFTP Boot update "for those who find this problem in the future"
It would seem that the network MTU was my limiting factor. With Simon's Help, we were able to find the problem and solution. My config file didn't mention (being that it was too old) the switch, tftp-no-blocksize Adding it, and restarting dnsmasq, the new system booted straight to the install page. I am using a boot client that is part of the motherboard. MB: Asus, M4N78 Pro Nvidia Boot Agent version: 249.0542. Snip from Simon's Email OK, it looks like the client is asking for a blocksize (ie packetsize) of 1456 bytes, and that's too big for your network. Because of that the packets are getting fragmented and that's really confusing the client: in the end the client does something really strange which provokes the "unsupported request" error. Try adding tftp-no-blocksize to /etc/dnsmasq.conf. That will cause dnsmasq to reject the request from the client for bigger blocks, and may be enough to make it all work. Alternatively if you can increase the MTU on the network that might fix things. Philippe
[Dnsmasq-discuss] TFTP boot
Hello, I am trying to us DNSMASQ to install Ubuntu Server a new machine, but it isn't working. HEre is what I have dhcp-boot=pxelinux.0,fileserver,192.168.0.34 enable-tftp tftp-root=/var/lib/tftpboot dir /var/lib/tftpboot/ drwxrwxrwx 3 nobody nogroup 4.0K 2009-04-17 12:08 . drwxr-xr-x 37 root root4.0K 2009-06-08 15:22 .. lrwxrwxrwx 1 nobody nogroup 33 2009-06-08 15:24 pxelinux.0 -> ubuntu-installer/amd64/pxelinux.0 lrwxrwxrwx 1 nobody nogroup 35 2009-06-08 15:24 pxelinux.cfg -> ubuntu-installer/amd64/pxelinux.cfg drwxr-xr-x 3 nobody nogroup 4.0K 2009-04-17 12:08 ubuntu-installer -rw-r--r-- 1 nobody nogroup 56 2009-04-17 12:08 version.info Contents of pxelinux.cfg include ubuntu-installer/amd64/boot-screens/menu.cfg default ubuntu-installer/amd64/boot-screens/vesamenu.c32 prompt 0 timeout 0 DNSMASQ.log results Aug 20 16:12:26 dnsmasq[4418]: TFTP sent /var/lib/tftpboot/pxelinux.0 to 192.168.0.60 Aug 20 16:12:26 dnsmasq[4418]: TFTP error 0 TFTP Aborted received from 192.168.0.60 Aug 20 16:12:26 dnsmasq[4418]: TFTP failed sending /var/lib/tftpboot/pxelinux.0 to 192.168.0.60 Aug 20 16:12:26 dnsmasq[4418]: TFTP sent /var/lib/tftpboot/pxelinux.0 to 192.168.0.60 The display on the new box states the following: PXE-T04: Unsupoort Request from 192.168.0.60 PXE-E36: Error Received from TFTP server PXE-M0F: Exiting NVIDIA Boot Agent Does anyone have any idea of what the problem is, or where to start looking to fix it? I know that the new box is getting the IP address from the dHCP server, 192.168.0.60, so it is something with the TFTP server. Thank you Philippe
Re: [Dnsmasq-discuss] Dnsmasq-discuss Digest, Vol 49, Issue 9
Hello Jack,
I have worked with Dlink routers. I have found that the LAN IP
Address range need to be include the router's IP address.
Philippe
Message: 1
Date: Wed, 17 Jun 2009 06:04:32 +
From: jack seth
Subject: [Dnsmasq-discuss] Need help accessing my modem through my
router
To:
Message-ID:
Content-Type: text/plain; charset="windows-1252"
Ok, I have a linksys router running dd-wrt firmware which is running
dnsmasq. My lan is on the 192.168.1.0/24 subnet. I would like to
be able to access my dsl modem through the router by its ip address
and its hostname. Of course the modem is connected to the WAN side
of the router, so I added a ip address in the same subnet as the
modems address (which is 192.168.2.254) to my router's wan port
(which is vlan2) with this command
ifconfig vlan2 192.168.2.222 netmask 255.255.255.0
I also added this iptables rule to get traffic back
iptables -I POSTROUTING -t nat -o vlan2 -d 192.168.2.0/24 -j MASQUERADE
Here is the strange stuff that is happening. If I try to access the
modem by ip address (192.168.2.254) it seems the modem redirects the
browser to 'launchmodem.com' (which is one of the ways you can reach
the modem by name) before the homepage will appear. Well this
fails. I figured modifying my 'hosts' file on my notebook (running
Vista Ultimate) would solve the problem and it did. So I thought
instead of modifying my hosts file in Vista I would modify the hosts
file on the router then any computer on the lan would be able to
reach the modem. I did that but it seems that Vista isn't using the
host info from the router. So I tried adding these commands to
dnsmasq
address=/launchmodem/192.168.2.254
address=/launchmodem.com/192.168.2.254
address=/www.launchmodem.com/192.168.2.254
When I do this I can ping the modem FROM THE ROUTER all three ways
i.e 'launchmodem', 'launchmodem.com', and 'www.launchmodem.com' I
can also ping the modem from the router all three ways with these
added to the router's hosts file. However, from my notebook I can
only ping 'launchmodem.com', and 'www.launchmodem.com' but NOT
'launchmodem' (host not found). Another oddity, I can only reach
the modem in my browser with 'launchmodem.com' not with
'www.launchmodem.com' even though I can ping 'www.launchmodem.com'.
Can anyone advise me on what is going on here and how to troubleshoot/fix?
Thanks!
_
Bing? brings you maps, menus, and reviews organized in one place.
Try it now.
http://www.bing.com/search?q=restaurants&form=MLOGEN&publ=WLHMTAG&crea=TEXT_MLOGEN_Core_tagline_local_1x1
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20090617/726cd463/attachment.html
--
Message: 2
Date: Wed, 17 Jun 2009 08:25:40 +0200
From: Rune Kock
Subject: [Dnsmasq-discuss] Fwd: Need help accessing my modem through
my router
To: dnsmasq discussion list
Message-ID:
Content-Type: text/plain; charset=ISO-8859-1
-- Forwarded message --
From: Rune Kock
Date: Wed, Jun 17, 2009 at 08:25
Subject: Re: [Dnsmasq-discuss] Need help accessing my modem through my router
To: jack seth
On Wed, Jun 17, 2009 at 08:04, jack seth wrote:
However, from my notebook I can only ping 'launchmodem.com',
and 'www.launchmodem.com' but NOT 'launchmodem' (host not found).
I think that the Windows ping command does not always use DNS to find
the host. ?Sometimes it uses netbios methods, which usually means
trying a broadcast and see whether anything responds. ?Maybe pinging
launchmodem. with a final dot will change it? ?Or you could try
nslookup, though that has its own set of problems. ?Best would be to
test with a Linux-system instead.
Another
oddity, I can only reach the modem in my browser with 'launchmodem.com' not
with 'www.launchmodem.com' even though I can ping 'www.launchmodem.com'.
Sounds to me like the modem is rejecting that domain when it gets the
http request.
Can anyone advise me on what is going on here and how to troubleshoot/fix?
If in doubt, run wireshark.
--
(\_/) This is Bunny. Copy and paste Bunny
(='.'=) into your signature to help him gain
(")_(") world domination.
--
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
End of Dnsmasq-discuss Digest, Vol 49, Issue 9
**
[Dnsmasq-discuss] Re: IPV6
I know that DNSMASQ doesn't support DHCPv6, is there going to be support for it in the future? Apparently there are specifications for it now. Thank you Jan for this bit of information. But that doesn't help with explaining how to use the DNS portion (configuration). With IPv4 there are time server, dns search orders, etc that can be sent to the client when it connects via DHCP, but if DHCP doesn't exist anymore for IPv6, how is that information sent to each client? First: Yes, after a long time of "No DHCP, it is evil", they gave up and now there is a DHCPv6 (RFC3315), unfortunately it not implemented by dnsmasq. How is the DNS server made aware that the client has connected? The magic words are is Zeroconf/mDNS on FE02::FB and Link Local Multicast Name Resolution (RFC4795) on FF02::1:3. The client should tell other clients by means of multicast that he is there, >and try to find a Service-Provider for "real" DNS over this, where he than can > make a update. Yeah i know, not very convenient when it does not come in one handy program >like dnsmasq... Philippe Greetings Jan Those are all part of DHCP. dnsmasq isn't capable of DHCPv6, you'll need to configure your client some other way (like running a DHCPv6 server or manual configuration). I don't know what you mean by "How is the DNS server made aware that the client has connected?", since DNS connections between clients and servers use UDP which is connectionless (in general only zone transfers between peer servers are TCP). The client isn't connected, it just sends a datagram containing a request and dnsmasq sends a response back to the address whence the datagram came. On Thu, Apr 2, 2009 at 12:55 AM, Philippe Faure wrote: Thank you Richard for your comments. But that doesn't help with explaining how to use the DNS portion (configuration). With IPv4 there are time server, dns search orders, etc that can be sent to the client when it connects via DHCP, but if DHCP doesn't exist anymore for IPv6, how is that information sent to each client? How is the DNS server made aware that the client has connected? Philippe
Re: [Dnsmasq-discuss] IPV6
Thank you Richard for your comments. But that doesn't help with explaining how to use the DNS portion (configuration). With IPv4 there are time server, dns search orders, etc that can be sent to the client when it connects via DHCP, but if DHCP doesn't exist anymore for IPv6, how is that information sent to each client? How is the DNS server made aware that the client has connected? Philippe Quoting "richardvo...@gmail.com" : From the man page: "Dnsmasq supports IPv6 for DNS, but not DHCP. " On Wed, Apr 1, 2009 at 1:39 AM, Philippe Faure wrote: I have read that dnsmasq is ready to support IPv6. I was wondering what is required to enable this function? What changes to the config file are required? I am currently using dnsmasq to distribute IPV4 IP addresses and want to try to move to ipv6? Thanks Philippe ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
[Dnsmasq-discuss] IPV6
I have read that dnsmasq is ready to support IPv6. I was wondering what is required to enable this function? What changes to the config file are required? I am currently using dnsmasq to distribute IPV4 IP addresses and want to try to move to ipv6? Thanks Philippe
[Dnsmasq-discuss] maximum number of "address" lines
Hello, I run a script that takes URLs that display adds, and point them to an un-used Local IP address. for example: address="/123banners.com/192.168.0.35" All of these addresses are in one file which DNSMASQ reads at startup. I have noticed that the number of addresses in this file is now really large. About 17000 redirections. I have tried to start dnsmasq and it comes back with an error on line 13910. There was nothing different about line 13910, and 13909, except for the different url. I was wondering if DNSMASQ had an internal limit of the number of redirects, or the size of input files, or anything else that would cause a problem? Here is what I found in syslog: Nov 26 00:01:33 philserver dnsmasq[22070]: error at line 13910 of /etc/hosts_to_block Nov 26 00:01:33 philserver dnsmasq[22070]: FAILED to start up There was nothing in dnsmasq.log file. Philippe
Re: [Dnsmasq-discuss] DNSMASQ and configuring Win XP boxes to use a Proxy server
Thank you Simon,
Will give that a try.
Philippe
Quoting Simon Kelley :
Philippe Faure wrote:
Hello,
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 /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".
HTH
Simon.
[Dnsmasq-discuss] DNSMASQ and configuring Win XP boxes to use a Proxy server
Hello, 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. Thank you Philippe
[Dnsmasq-discuss] --address command
Hello, Based on the --address command in dnsmasq, it would seem that you have to give it either a domain name, or IP and dnsmasq will always return an IP. I was wondering if it would be possible to have the second parameter work with another domain name, or IP:port? Thank you Philippe
[Dnsmasq-discuss] Cache questions
I have been watching the dnsmasq logs for the past couple of days and founds the following lines: Apr 20 11:54:01 dnsmasq[11788]: cached 82.160.33.10 is -IPv4 Apr 20 11:54:04 dnsmasq[11788]: query[PTR] 10.33.160.82.in-addr.arpa from 192.168.0.34 Apr 20 11:54:04 dnsmasq[11788]: cached 82.160.33.10 is -IPv4 Apr 20 11:54:08 dnsmasq[11788]: query[PTR] 10.33.160.82.in-addr.arpa from 192.168.0.34 Apr 20 11:54:08 dnsmasq[11788]: cached 82.160.33.10 is -IPv4 Apr 20 11:54:11 dnsmasq[11788]: query[PTR] 10.33.160.82.in-addr.arpa from 192.168.0.34 the day before it was: Apr 19 20:49:42 dnsmasq[20313]: cached 58.215.240.84 is -IPv4 Apr 19 20:49:46 dnsmasq[20313]: query[PTR] 84.240.215.58.in-addr.arpa from 192.168.0.34 Apr 19 20:49:46 dnsmasq[20313]: cached 58.215.240.84 is -IPv4 Apr 19 20:49:51 dnsmasq[20313]: query[PTR] 84.240.215.58.in-addr.arpa from 192.168.0.34 and before that it was; Apr 19 03:11:54 dnsmasq[14684]: query[PTR] 210.87.28.218.in-addr.arpa from 192.168.0.34 Apr 19 03:11:54 dnsmasq[14684]: cached 218.28.87.210 is pc0.zz.ha.cn Apr 19 03:11:54 dnsmasq[14684]: query[A] pc0.zz.ha.cn from 192.168.0.34 Apr 19 03:11:54 dnsmasq[14684]: cached pc0.zz.ha.cn is 202.102.224.0 Apr 19 03:12:00 dnsmasq[14684]: query[PTR] 210.87.28.218.in-addr.arpa from 192.168.0.34 Apr 19 03:12:00 dnsmasq[14684]: cached 218.28.87.210 is pc0.zz.ha.cn Apr 19 03:12:00 dnsmasq[14684]: query[A] pc0.zz.ha.cn from 192.168.0.34 Apr 19 03:12:00 dnsmasq[14684]: cached pc0.zz.ha.cn is 202.102.224.0 Every 3-5 seconds, this went on for 12 hours or more. I didn't see anything that would cause this to start. Anyone see this before? Why is it checking cache continuously? Thank you Philippe
Re: [Dnsmasq-discuss] reverse lookups
Yes, I did. I have commented it out and it worked. Thank you Philippe Quoting Simon Kelley : Philippe Faure wrote: Dnsmasq handles local domains nicely (for both forward and reverse lookups): root@fileserver:~$host phil2 phil2.230newport.faure.ca has address 192.168.0.56 root@fileserver:~$host 192.168.0.56 56.0.168.192.in-addr.arpa domain name pointer phil2.230newport.faure.ca. Other IPs in that 192.168.0.0/24 range dont work: root@fileserver:~$host 192.168.0.250 Host 250.0.168.192.in-addr.arpa not found: 3(NXDOMAIN) 192.168.0.250 (and others ips liks 192.168.0.230 etc...) are handled by a second DNS server, but dnsmaq refuses to forward on the requests. I added this conf item with no luck: # Example of routing PTR queries to nameservers: this will send all # address->name queries for 192.168.3/24 to nameserver 10.1.2.3 #server=/3.168.192.in-addr.arpa/10.1.2.3 server=/0.168.192.in-addr.arpa/192.168.0.250 #second name server. I was wondering why it wont forward on the DNS PTR lookup (reverse lookup) if it does not exist in its own DB? Do you have the bogus-priv flag set? That takes priority (which is probably wrong, but it's too late to change now.) Cheers, Simon. ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
[Dnsmasq-discuss] reverse lookups
Dnsmasq handles local domains nicely (for both forward and reverse lookups): root@fileserver:~$host phil2 phil2.230newport.faure.ca has address 192.168.0.56 root@fileserver:~$host 192.168.0.56 56.0.168.192.in-addr.arpa domain name pointer phil2.230newport.faure.ca. Other IPs in that 192.168.0.0/24 range dont work: root@fileserver:~$host 192.168.0.250 Host 250.0.168.192.in-addr.arpa not found: 3(NXDOMAIN) 192.168.0.250 (and others ips liks 192.168.0.230 etc...) are handled by a second DNS server, but dnsmaq refuses to forward on the requests. I added this conf item with no luck: # Example of routing PTR queries to nameservers: this will send all # address->name queries for 192.168.3/24 to nameserver 10.1.2.3 #server=/3.168.192.in-addr.arpa/10.1.2.3 server=/0.168.192.in-addr.arpa/192.168.0.250 #second name server. I was wondering why it wont forward on the DNS PTR lookup (reverse lookup) if it does not exist in its own DB?
[Dnsmasq-discuss] two DNSMASQ server online
I have a unique setup. I have two private networks connected by a VPN connection. Both private networks have DNSMASQ running (using DNS and DHCP functionality). I am finding that a client from network 1 will receive IP address from DHCP server on network 2. Besides ignoring MAC addresss from the other network, which makes it difficult to keep up to date with wireless clients, that keep moving around, is there a way to stop dhcp replies coming from the other network? To add a level complexity. The DNS server built into dnsmasq need to be able to reference each other, since clients on network 1 need to know about clients on network 2. IP addresses have been assigned to each network, so they don't overlap. I don't know if this is something that dnsmasq can handle or if someone else has come across this situation, and found a way to block only DHCP requests to be transferred over the VPN connection? Thank you Philippe
[Dnsmasq-discuss] Logging
Hello, I have found that I left logging enabled, and the dnsmasq.log file is over 500 Mb. I was wondering if in the next release there could be a script that would automatically, maybe once a week, move the current file to dnsmasq.log.1, and so one. once you have done this for 5 weeks, start to zip the files, or just delete them. Something similar to the what happens to the syslog file and messages files. Just a suggestion. Philippe
Re: [Dnsmasq-discuss] Re: Silly question
Thank you. Philippe Quoting Jima : On Thu, 17 Jan 2008, Philippe Faure wrote: /etc/hosts/ 127.0.0.1 localhost 192.68.0.34 fileserver /etc/resolv.conf nameserver 192.168.0.34 #self So...is the 1 missing in /etc/hosts, or just your email? :-) Jima
[Dnsmasq-discuss] Re: Silly question
e # Set the boot file name only when the "red" tag is set. #dhcp-boot=net:red,pxelinux.red-net # An example of dhcp-boot with an external server: the name and IP # address of the server are given after the filename. #dhcp-boot=/var/ftpd/pxelinux.0,boothost,192.168.0.3 # Set the limit on DHCP leases, the default is 150 #dhcp-lease-max=150 # The DHCP server needs somewhere on disk to keep its lease database. # This defaults to a sane location, but if you want to change it, use # the line below. #dhcp-leasefile=/var/lib/misc/dnsmasq.leases # Set the DHCP server to authoritative mode. In this mode it will barge in # and take over the lease for any client which broadcasts on the network, # whether it has a record of the lease or not. This avoids long timeouts # when a machine wakes up on a new network. DO NOT enable this if there's # the slighest chance that you might end up accidentally configuring a DHCP # server for your campus/company accidentally. The ISC server uses # the same option, and this URL provides more information: # http://www.isc.org/index.pl?/sw/dhcp/authoritative.php dhcp-authoritative # Run an executable when a DHCP lease is created or destroyed. # The arguments sent to the script are "add" or "del", # then the MAC address, the IP address and finally the hostname # if there is one. #dhcp-script=/bin/echo # Set the cachesize here. #cache-size=150 # If you want to disable negative caching, uncomment this. #no-negcache # Normally responses which come form /etc/hosts and the DHCP lease # file have Time-To-Live set as zero, which conventionally means # do not cache further. If you are happy to trade lower load on the # server for potentially stale date, you can set a time-to-live (in # seconds) here. #local-ttl= # If you want dnsmasq to detect attempts by Verisign to send queries # to unregistered .com and .net hosts to its sitefinder service and # have dnsmasq instead return the correct NXDOMAIN response, uncomment # this line. You can add similar lines to do the same for other # registries which have implemented wildcard A records. #bogus-nxdomain=64.94.110.11 # If you want to fix up DNS results from upstream servers, use the # alias option. This only works for IPv4. # This alias makes a result of 1.2.3.4 appear as 5.6.7.8 #alias=1.2.3.4,5.6.7.8 # and this maps 1.2.3.x to 5.6.7.x #alias=1.2.3.0,5.6.7.0,255.255.255.0 # Change these lines if you want dnsmasq to serve MX records. # Return an MX record named "maildomain.com" with target # servermachine.com and preference 50 #mx-host=maildomain.com,servermachine.com,50 # Set the default target for MX records created using the localmx option. #mx-target=servermachine.com # Return an MX record pointing to the mx-target for all local # machines. #localmx # Return an MX record pointing to itself for all local machines. #selfmx # Change the following lines if you want dnsmasq to serve SRV # records. These are useful if you want to serve ldap requests for # Active Directory and other windows-originated DNS requests. # See RFC 2782. # You may add multiple srv-host lines. # The fields are # If the domain part if missing from the name (so that is just has the # service and protocol sections) then the domain given by the domain= # config option is used. (Note that expand-hosts does not need to be # set for this to work.) # A SRV record sending LDAP for the example.com domain to # ldapserver.example.com port 289 #srv-host=_ldap._tcp.example.com,ldapserver.example.com,389 # A SRV record sending LDAP for the example.com domain to # ldapserver.example.com port 289 (using domain=) #domain=example.com #srv-host=_ldap._tcp,ldapserver.example.com,389 # Two SRV records for LDAP, each with different priorities #srv-host=_ldap._tcp.example.com,ldapserver.example.com,389,1 #srv-host=_ldap._tcp.example.com,ldapserver.example.com,389,2 # A SRV record indicating that there is no LDAP server for the domain # example.com #srv-host=_ldap._tcp.example.com # The following line shows how to make dnsmasq serve an arbitrary PTR # record. This is useful for DNS-SD. (Note that the # domain-name expansion done for SRV records _does_not # occur for PTR records.) #ptr-record=_http._tcp.dns-sd-services,"New Employee Page._http._tcp.dns-sd-services" # Change the following lines to enable dnsmasq to serve TXT records. # These are used for things like SPF and zeroconf. (Note that the # domain-name expansion done for SRV records _does_not # occur for TXT records.) #Example SPF. #txt-record=example.com,"v=spf1 a -all" #Example zeroconf #txt-record=_http._tcp.example.com,name=value,paper=A4 # For debugging purposes, log each DNS query as it passes through # dnsmasq. log-queries # Log lots of extra information about DHCP transactions. log-facility=/var/log/dnsmasq log-dhcp # Include a another lot of configuration options. #conf-file=/etc/dnsmasq.more.conf #conf-dir=/etc/dnsmasq.d Quoting &quo
[Dnsmasq-discuss] dns not responding with server name
Hello, I have a server called "fileserver" running dnsmasq version 2.39. All PCs can get DHCP leases, ping each other, and find dns responses to systems external to the network. But when I try to ping fileserver from any other Pc, or itself. I get the response that it can't be found. Any assistance would be appreciated. Philippe Here are the contents of relevant files: hosts: 127.0.0.1 localhost # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts resolv.conf: nameserver 192.168.0.34 dnsmasq.conf: # Configuration file for dnsmasq. # # Format is one option per line, legal options are the same # as the long options legal on the command line. See # "/usr/sbin/dnsmasq --help" or "man 8 dnsmasq" for details. # The following two options make you a better netizen, since they # tell dnsmasq to filter out queries which the public DNS cannot # answer, and which load the servers (especially the root servers) # uneccessarily. If you have a dial-on-demand link they also stop # these requests from bringing up the link uneccessarily. # Never forward plain names (without a dot or domain part) domain-needed # Never forward addresses in the non-routed address spaces. bogus-priv #http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2004q4/06.html ## ENTER A gateway value. "3" dhcp-option=3,192.168.0.33 #gateway dhcp-option=6,192.168.0.34 #DNS server 230newport.faure.ca ##dhcp-option=6,192.168.0.33 #DNS server philrouter.faure.ca (gateway) ##dhcp-option=6,192.168.0.33 #DNS server # # Uncomment this to filter useless windows-originated DNS requests # which can trigger dial-on-demand links needlessly. # Note that (amongst other things) this blocks all SRV requests, # so don't use it if you use eg Kerberos. # This option only affects forwarding, SRV records originating for # dnsmasq (via srv-host= lines) are not suppressed by it. #filterwin2k # Change this line if you want dns to get its upstream servers from # somewhere other that /etc/resolv.conf #resolv-file= # By default, dnsmasq will send queries to any of the upstream # servers it knows about and tries to favour servers to are known # to be up. Uncommenting this forces dnsmasq to try each query # with each server strictly in the order they appear in # /etc/resolv.conf #strict-order # If you don't want dnsmasq to read /etc/resolv.conf or any other # file, getting its servers from this file instead (see below), then # uncomment this. no-resolv # If you don't want dnsmasq to poll /etc/resolv.conf or other resolv # files for changes and re-read them then uncomment this. #no-poll # Add other name servers here, with domain specs if they are for # non-public domains. #server=/localnet/192.168.0.1 # Tell dnsmasq not to use resolv.conf at all. Put just "nameserver # 127.0.0.1" there, and tell dnsmasq about its servers in # #/etc/dnsmasq.conf using "server=" # #From email from Simon Kelley 2008-01-10 # server=192.228.28.70 #CIRA server=92.228.28.71 #CIRA server=208.67.222.222 #OPENDNS server=208.67.220.220 #OPENDNS server=207.44.192.61 #NS.Certainkey.com #server=206.47.244.57 #Bell #server=207.164.234.129 #Bell server=4.2.2.1 #UNNET # Example of routing PTR queries to nameservers: this will send all # address->name queries for 192.168.3/24 to nameserver 10.1.2.3 #server=/3.168.192.in-addr.arpa/10.1.2.3 # Add local-only domains here, queries in these domains are answered # from /etc/hosts or DHCP only. #local=/localnet/ # Add domains which you want to force to an IP address here. # The example below send any host in doubleclick.net to a local # webserver. #address=/doubleclick.net/127.0.0.1 # If you want dnsmasq to change uid and gid to something other # than the default, edit the following lines. #user= #group= # If you want dnsmasq to listen for DHCP and DNS 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=eth0 # Or you can specify which interface _not_ to listen on #except-interface=br0 # Or which to listen on by address (remember to include 127.0.0.1 if # you use this.) listen-address=127.0.0.1 listen-address=192.168.0.34 # If you want dnsmasq to provide only DNS service on an interface, # configure it as shown above, and then use the following line to # disable DHCP on it. #no-dhcp-interface= # On systems which support it, dnsmasq binds the wildcard address, # even when it is listening on only some interfaces. It then discards # requests that it shouldn't reply to. This has the advantage of # working even when interfaces come and go and change address. If you # want dnsmasq to really bind only the interfaces it is listening on, # uncomment this option. About the only time you may need this is when # running another nameserver on the same machine. #bi
[Dnsmasq-discuss] log locations
Hello. I am trying to debug a problem of why a PC is getting an IP address outside of the Dhcp server allocated range dhcp-range=192.168.0.47,192.168.0.62,168h but the Ip received is 192.168.0.37 [root@philserver root]$ dnsmasq -v Dnsmasq version 2.22 Copyright (C) 2000-2005 Simon Kelley This software comes with ABSOLUTELY NO WARRANTY. Dnsmasq is free software, and you are welcome to redistribute it under the terms of the GNU General Public License, version 2. I was looking for any of the following: DHCPDISCOVER DHCPOFFER DHCPREQUEST DHCPACK in the syslog file, but couldn't find them. log-queries is not commented. using the default log file location of /var/log/syslog All other dnsmasq requests seem to get logged, but not dhcp initiations. Any assistance would be apprecaited. Philippe
Re: [Dnsmasq-discuss] DHCP Discover messages are not being answered
Hello Carlos, I tried to enter the log-dhcp line into the dnsmasq.conf and I got an error message: /etc/init.d/dnsmasq restart Restarting DNS forwarder and DHCP server: dnsmasqdnsmasq: bad option at line 374 of /etc/dnsmasq.conf This line corresponds to the log-dhcp entry. Version 2.22 cachesize 150 Debian kernel 2.6.8-3-686-smp Sarge version of Debian. thank you Philippe Quoting Carlos Carvalho : Philippe Faure (phili...@faure.ca) wrote on 27 September 2007 22:35: >I was wondering is there was another setup requirement for dnsmasq to add a >dbian box, versus linux? There isn't. >Is there somewhere (besides syslog) which would tell me whether the DHCP >Discover messages are even getting to the dnsmasq server? Put log-queries log-dhcp in dnsmasq.conf. If the query reaches the server dnsmasq will log them, with the answer. If the queries don't appear you could use tcpdump to see if they're on the wire.
[Dnsmasq-discuss] DHCP Discover messages are not being answered
Hello, I have been using dnsmasq for some time now without issue. I am now trying to add another PC to the system. Currently, I have have two PC (windows) both connected to a wireless router which forwards all requests to the dnsmasq. This works without any problems. This third PC (debian etch), is also being added via the wireless network also. As far as I can tell this third PC is connecting to the wireless router (since the router does know it's MAC address). My problem is that the DHCPDISCOVER messages seem to not get answered. I am using DHCP-client as the DHCP client. There is encryption on the wireless router, which I have also setup, otherwise the router wouldn't recognize this third connection. I was wondering is there was another setup requirement for dnsmasq to add a dbian box, versus linux? Is there somewhere (besides syslog) which would tell me whether the DHCP Discover messages are even getting to the dnsmasq server? Any assistance would be appreciated. Thank you Philippe
Re: [Dnsmasq-discuss] dnsmasq.lease file question
Thanks you for this information. How does the Host name play into the dhcp leases? Is the IP handed out based on MAC address, or based on the Host name? thank you Philippe Mr Gabriel wrote: I too have noticed this strange phenomena, and not just in DNSMasq. On almost every DHCP server I have ever used, when I look at the lease file, there is never hardware info for linux boxes. Personally, and my understanding of the underlying mechanics of DHCP is very limited, I thought that all requests for a DHCP address included the mac address, in order for an answer to be directed to the correct machine. Therefore, the DHCP server should already know the hardware address. Why it forgets, and it never gets listed, is beyond me. Maybe someone else could enlighten us :) On Tue, 2007-04-24 at 12:46 -0400, Philippe Faure wrote: Hello, I am running Dnsmasq version 2.2 on a Debian server version 3.1. The Dnsmasq.lease file has the following information stored in it. 1177812457 00:15:e9:a8:e5:28 192.168.0.50 debian-host * 1177928854 00:15:e9:a8:e6:c5 192.168.0.57 carm 01:00:15:e9:a8:e6:c5 1177849379 00:03:2f:3a:f2:e9 192.168.0.54 phil 01:00:03:2f:3a:f2:e9 Why is it that the two windows' boxes have the hardware ID there, while the linux (Ubuntu Feisty, running dhcpcd) only has a *? Is there some setup that I have done properly? if so with the client or server? Do I need to worry about it? This is a tale of two different identifiers: the MAC address and the client identifier. The final item on each line in the leases file is a client identifier. Client identifiers are optional: if one is not provided then the DHCP server just uses the MAC address to track the host, but if a client-id is present, it trumps the MAC address. This has interesting applications: if a machine uses a serial number as its client-id, then replacement of a network interface (changing the MAC address) won't interfere with a DHCP lease. In practice, unless specially configured, common clients either don't send a client-id, or send one derived from the MAC address, so the presence or absence really doesn't matter. In this case, windows sends a client-id but dhclient doesn't. It's not a practical problem either way round, and nothing to worry about. Interestingly, it's possible to have a client-id and no MAC address. Firewire does this, because firewire MAC addresses are larger than the MAC address field in a DHCP packet. Cheers, Simon.
[Dnsmasq-discuss] Linking to private networks
I am in the process of setting up a VPN between multiple private networks. If they are running DNSMASQ would it be a smart idea to enter: server=/internal.myco.com/192.168.10.1 (updated for my name and IP) in all servers (2 or 3 )? Would this allow the routing of internal DNS requests from one network to the other? I was wondering how does the dnsmasq server stopthe problems of loops? Philippe --- Begin Message --- Hello, I am in the process of setting up a VPN between multiple private networks. If they are running DNSMASQ would it be a smart idea to enter: server=/internal.myco.com/192.168.10.1 (updated for my name and IP) in all servers (2 or 3 )? Would this allow the routing of internal DNS requests from one network to the other? I was wondering how does the dnsmasq server stop the problems of loops? Philippe --- End Message ---
[Dnsmasq-discuss] dnsmasq.lease file question
Hello, I am running Dnsmasq version 2.2 on a Debian server version 3.1. The Dnsmasq.lease file has the following information stored in it. 1177812457 00:15:e9:a8:e5:28 192.168.0.50 debian-host * 1177928854 00:15:e9:a8:e6:c5 192.168.0.57 carm 01:00:15:e9:a8:e6:c5 1177849379 00:03:2f:3a:f2:e9 192.168.0.54 phil 01:00:03:2f:3a:f2:e9 Why is it that the two windows' boxes have the hardware ID there, while the linux (Ubuntu Feisty, running dhcpcd) only has a *? Is there some setup that I have done properly? if so with the client or server? Do I need to worry about it? thank you Philippe
[Dnsmasq-discuss] NOtice
I was trying to get access to my interanl PC from the dnsmasq server. the /etc/resolv.conf file had: nameserver 192.168.0.200 #Internet router nameserver 192.168.0.1 #DNSMASQ server I would try to ping the name of an internal PC (name was found in the dnsmasq.leases file). Each time I would ge ta time out stating that the server couldn't find that PC. I then changed the order of the /et/resolv.conf file and put it'self first and the upstream dns server second. the /etc/resolv.conf file hads nameserver 192.168.0.1 #DNSMASQ server nameserver 192.168.0.200 #Internet router I believe that what was happeneing twas that the dnsmasq server would try the internet router for an IP addresss of internal PC's, fail and then not try to next name server. I don't know why. I thought that it should be mentioned here. Philippe
[Dnsmasq-discuss] Setting up DNS with DHCP (fwd)
Hello I managed to get dnsmasq running, well atleast the dhcp protion, last night in 20 mintues. Great piece of software thank you. I have noticed though that the only way for it to work was to point each client DNS requests to my router 192.168.0.200 which acts as the interface to my ISP. not to my dnsmasq server. The server running dnsmasq at 192.168.0.1. the contents of the /etc/resolv.conf file is: nameserver 192.168.0.200 I can't seem to get the internal dns setup to work properly. When I point the dns requests to dnsmasq server no internal nor external requests are completed. I have a feeling that there is a setup issue with dnsmasq but not quite sure where to look. I know that in a previous version of dnsmasq, I would be able to see the client names and their associated IP aderesses, but I can't seem to find this file anymore. Any help in this setup would be appreciated. Philippe
