Re: [Dnsmasq-discuss] load balanced dnsmasq?
On Tue, Jul 20, 2010 at 21:32, richardvo...@gmail.com wrote: >> > >> > I think richardvoigt meant to separate the configurations of the DHCP >> > servers to make them ignore requests they don't have entries for, if >> > that is possible. > > No, that wouldn't be redundant and that's not what I'm suggesting. > Of course I do suggest an automated solution for pushing configuration > updates to all the servers from a single source. Yes... this will happen with a very low frequency or never... I will manually rsync from a single source at first... If this happens more than twice, I'll write a little script to do this. >> >> Anyway, do you think that configuring static dhcp mac/ip/hostname >> assignments in a redundant way in the servers and the ip/hostname >> relationship also in /etc/hosts is a bad thing to do? > > It's perfectly fine. Potential drawbacks are having dynamic leases > scattered all over or having configs get out of sync. Excellent. Thanx a lot for your help. -- Mariano Absatz - El Baby www.clueless.com.ar
Re: [Dnsmasq-discuss] load balanced dnsmasq?
On Tue, Jul 20, 2010 at 16:05, clemens fischer wrote: > Mariano Absatz wrote: > > (please don't top post) Sorry about that... I usually follow the "posting convention" I see and since richardvoigt had top-posted, I did the same. > >> So, given that, I may write down the static IP/hostname assignments in >> every dnsmasq server and that would give the correct name in every >> server. >> >> All would have the same MAC/IP/hostname configuration in dnsmasq.conf >> so even if there are dhcp collisions (e.g. because 2 servers got a >> broadcast request), they would all reply the same configuration and >> the clients should be happy enough, would they? > > I think richardvoigt meant to separate the configurations of the DHCP > servers to make them ignore requests they don't have entries for, if > that is possible. > > I was going to suggest splitting the network into a number of smaller > sub networks connected by switches, and maybe using dhcp-relay, another > fine product of simon. Well... the 50 machines are actually connected to 5 different switches with 1Gbps uploads to a main switch where the 2 or 3 servers also connect with 1Gbps. I don't need subnetting among the machines (and I think I wouldn't like to do it, because that might add up routing problems) so I don't see an advantage in relaying dhcp... Anyway, do you think that configuring static dhcp mac/ip/hostname assignments in a redundant way in the servers and the ip/hostname relationship also in /etc/hosts is a bad thing to do? Thanx for your answers (and patience). Regards. -- Mariano Absatz - El Baby www.clueless.com.ar
Re: [Dnsmasq-discuss] load balanced dnsmasq?
So, given that, I may write down the static IP/hostname assignments in every dnsmasq server and that would give the correct name in every server. All would have the same MAC/IP/hostname configuration in dnsmasq.conf so even if there are dhcp collisions (e.g. because 2 servers got a broadcast request), they would all reply the same configuration and the clients should be happy enough, would they? On Tue, Jul 20, 2010 at 10:04, richardvo...@gmail.com wrote: > The basic rule for running multiple instances is to not give them > overlapping pools. Since you use only reservations, this shouldn't be a > problem. > However: the automatically generated dns entries when the address is given > out over DHCP won't be visible to other servers, you'll have to use > permanent records if you want to contact those nodes by name. That wouldn't > be feasible for dynamic mappings, but with reservations it's straightforward > albeit more work. > > On Mon, Jul 19, 2010 at 6:34 PM, Mariano Absatz wrote: >> >> Hi, >> >> is there a way to "load balance" among dnsmasq servers? >> >> I have a network of a half dozen servers (with static IPs which I >> write down in /etc/hosts for dnsmasq to publish), plus about 50 >> computers which get their IP and hostname from dnsmasq and use it to >> resolve dns, especifically, to know the IP of the servers and other >> PCs with very little "outside" queries... queries to outside dns are >> mostly done on behalf of the servers which need to connect to the >> outer world. >> >> What's more, for the 50 computers, I have compiled the MAC addresses >> and I'm giving them always the same IP/hostname (and no, I can't >> configure static IP in every computer). >> >> It seems that every now and then, one of the computers boot and can't >> get its own address via DHCP (I see nothing in the dnsmasq log so I >> think it may have missed a bunch of DHCP requests from the client at >> some point)... other thing that I also see happen is that cilents >> query dns and get no answer back...a few moments later, the same query >> gets an answer. >> >> I suspect that at some point, dnsmasq can't handle all the requests it >> gets (it is running on a busy server... but I also have seen something >> similar -dns queries not being answered- on a less busy server). >> >> I'd like to be able to put dnsmasq on 2 or 3 servers and that anyone >> of them be able to, at least, resolve dns... ideally, it'd be nice if >> it could also handle dhcp requests. >> >> Any suggestions? >> >> TIA -- Mariano Absatz - El Baby www.clueless.com.ar
[Dnsmasq-discuss] load balanced dnsmasq?
Hi, is there a way to "load balance" among dnsmasq servers? I have a network of a half dozen servers (with static IPs which I write down in /etc/hosts for dnsmasq to publish), plus about 50 computers which get their IP and hostname from dnsmasq and use it to resolve dns, especifically, to know the IP of the servers and other PCs with very little "outside" queries... queries to outside dns are mostly done on behalf of the servers which need to connect to the outer world. What's more, for the 50 computers, I have compiled the MAC addresses and I'm giving them always the same IP/hostname (and no, I can't configure static IP in every computer). It seems that every now and then, one of the computers boot and can't get its own address via DHCP (I see nothing in the dnsmasq log so I think it may have missed a bunch of DHCP requests from the client at some point)... other thing that I also see happen is that cilents query dns and get no answer back...a few moments later, the same query gets an answer. I suspect that at some point, dnsmasq can't handle all the requests it gets (it is running on a busy server... but I also have seen something similar -dns queries not being answered- on a less busy server). I'd like to be able to put dnsmasq on 2 or 3 servers and that anyone of them be able to, at least, resolve dns... ideally, it'd be nice if it could also handle dhcp requests. Any suggestions? TIA -- Mariano Absatz - El Baby www.clueless.com.ar
Re: [Dnsmasq-discuss] reducing SPOFs
On Wed, Jun 16, 2010 at 06:33, Andrew Elwell wrote: > > > if so, is the simplest way to sync /etc/hosts from my master onto it > > and run in DNS only mode? > > OK - following up my own post incase anyone looks through the archives > for debugging > > got this working - main (dnsmasq does DHCP and DNS) server is 192.168.1.251 > second box (linksys with dd-wrt) just doing DNS is 192.168.1.2 > > altered dnsmasq.conf on master to include > dhcp-option=6,192.168.1.251,192.168.1.2 > > and the linksys box has an scp'd copy of my master /etc/hosts I have a question about this setup... IIRC, clients can choose whichever dns server they like, there isn't a preference implied in the order in which they're handled, is it? In this case, about half the queries in your network will hit the router rather than you dnsmasq box. If they try to resolve a dynamic (dhcp) host (like when you try to ping another pc in your lan using its name), if the query is handled to the linksys it will answer with nxdomain... Or am I wrong in the previous assumption? > and runs dnsmasq with the following config: > > interface=br0 > resolv-file=/tmp/resolv.dnsmasq > domain=example.com (well, not really) > expand-hosts > bogus-priv > domain-needed > no-resolv > no-poll > server=208.67.222.222 > server=208.67.220.220 > bogus-nxdomain=67.215.65.132 > log-queries > no-dhcp-interface=br0 > -- Mariano Absatz - El Baby www.clueless.com.ar
Re: [Dnsmasq-discuss] dhcp configuration with al fixed addresses
On Fri, May 28, 2010 at 22:02, richardvo...@gmail.com wrote: > From 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. Thanx a lot, Richard. I hadn't noticed that sentence in the manpage. Now it's working great. -- Mariano Absatz - El Baby www.clueless.com.ar
[Dnsmasq-discuss] manpage bug?
Hi, I think I spotted an error in the manpage... The manpage says: -G, --dhcp-host=[][,id:|*][,net:][,][,][,][,ignore] However, if I put a line like: dhcp-host=,net:,, it doesn't work... I have to swap the order of net: and like: dhcp-host=,,net:, for it to work... I'm using dnsmasq 2.52. Regards. -- Mariano Absatz - El Baby www.clueless.com.ar
[Dnsmasq-discuss] dhcp configuration with al fixed addresses
Hi, I want to configure a dhcp server where ALL the IPs are fixed. However, if I don't configure a dhcp-range, dhcp won't work (even when I have a bunch of dhcp-host's). What should I do, then? Do I configure a dhcp-range with a dummy IP in it (and then use dhcp-ignore=myTag,#known)? Or is there a more elegant solution for it? TIA -- Mariano Absatz - El Baby www.clueless.com.ar
Re: [Dnsmasq-discuss] "dhcp-ignore = myTag, #known" was not what I thought
Simon Kelley escribió el 06/12/08 19:04: > Mariano Absatz wrote: >> >> 1) does "dhcp-range" allow me to match more than one tag? or to match >> one (or more) and set another one? > > > It allows you to match more than one, but they're combined as AND, so > > dhcp-range=net:tag1, net:tag2, .. > > > means use that range if tag1 is set AND tag2 is set. > > If you want to OR them, just repeat the ranger statement > > dhcp-range=net:tag1, 192.168.0.1, 192.168.0.10 > dhcp-range=net:tag2, 192.168.0.1, 192.168.0.10 > > will use 192.168.0.1-192.168.0.10 of tag1 is set OR tag2 is set. > > You can match one (or more) tags, as above, and set a tag too > > dhcp-range=net:tag1, net:tag2, newtag, .. > > newtag is set when this range is used. There can only be one tag set > on a range. > >> >> 2) when I write: >> >> # OUR PCs ## >> dhcp-host=00:22:33:44:55:01,192.168.1.101,net:tagIKnowYou,mycompany-PC-01 >> >> dhcp-host=00:22:33:44:55:02,192.168.1.101,net:tagIKnowYou,mycompany-PC-02 >> >> dhcp-host=00:22:33:44:55:03,192.168.1.101,net:tagIKnowYou,mycompany-PC-03 >> >> >> >> I am *setting* (and not trying to */match/*) the tag "tagIKnowYou" >> for these hosts, am I? > You're setting it. > > It's probably worth enumerating all the ways that tags can be set. > > 1) The name of the interface on which a DHCP request is recived is set > as a tag (2.46 and later only) > > 2) Tags can be set based on a match of circuit-id, subscriber-id and > remote-id in an RFC3046 realy agent option. > > 3) Tags can be set based on the MAC address with --dhcp-mac > > 4) If a dhcp-host line is used (or an implied one derived from > /etc/ethers) then "known" is set as a tag > > 5) If the used config line includes net: then that is set. > > 6) For BOOTP requests ONLY, tag "bootp" is set, and incoming > "filename" field (which isn't strictly an filename in BOOTP) is used > as a tag > > 7) Tags are set based in the vendor class and user class. > > At this point, if any set tags match a dhcp-ignore tag then the > request is discarded. > > Then a dhcp-range is selected, based on the current tag set, available > IP addresses etc. > > 8) Any tag in the DHCP range line is set. > > Finally, dhcp-options are added, filtered using the current tag set. > Great explanation... I understood everything and re-wrote my configuration accordingly (anyway, I have to wait till Tuesday to test it since I'm remote now and tomorrow is a National Holiday here). I thank you once again for your time and patience. -- Mariano Absatz - "El Baby" el.b...@gmail.com www.clueless.com.ar -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- bashian roulette: [ $(($RANDOM%6)) -eq 0 ] && rm -rf ~ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- * TagZilla 0.066 * http://tagzilla.mozdev.org
Re: [Dnsmasq-discuss] "dhcp-ignore = myTag, #known" was not what I thought
Mariano Absatz escribió el 06/12/08 09:13: > now, a couple of related questions... > > 1) does "dhcp-range" allow me to match more than one tag? or to match > one (or more) and set another one? > > 2) when I write: > # OUR PCs ## > dhcp-host=00:22:33:44:55:01,192.168.1.101,net:tagIKnowYou,mycompany-PC-01 > dhcp-host=00:22:33:44:55:02,192.168.1.102,net:tagIKnowYou,mycompany-PC-02 > dhcp-host=00:22:33:44:55:03,192.168.1.103,net:tagIKnowYou,mycompany-PC-03 > > > I am *setting* (and not trying to */match/*) the tag "tagIKnowYou" for > these hosts, am I? Well.. now I re-read the example and I see this is not so, that is, the lines above try to match (and not set) the tag. So, question #1 above remains and I add another one: Is there any other means than "dhcp-range" to */set/* a tag? TIA. -- Mariano Absatz - "El Baby" el.b...@gmail.com www.clueless.com.ar -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- I don't suffer from insanity. I enjoy every minute of it. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- * TagZilla 0.066 * http://tagzilla.mozdev.org
Re: [Dnsmasq-discuss] "dhcp-ignore = myTag, #known" was not what I thought
Simon Kelley escribió el 05/12/08 19:00: > Mariano Absatz wrote: >> >> How should I configure my dnsmasq to prevent unknown MACs from >> getting an IP in the "tagIKnowYou" range? > > You don't need to set your own tags at all, just use the "known" tag, > which will be set whenever a dhcp-host matches the MAC address. > > Then do > > dhcp-range=net:known,192.168.1.101,192.168.1.120,4h > dhcp-range=net:#known,192.168.1.161,192.168.1.174,4h > > That way, 192.168.1.101... will only be used when the MAC address is > known, and 192.168.1.161... will only be used when the MAC address is > not known. > > > It's important to understand the two uses of tags in dhcp-range > > dhcp-range=,.. > > will _set_ the tag if that range is used. > > dhcp-range=net:tag,... > > will _use_ the range if the tag is set. Now I get it... thank you... now, a couple of related questions... 1) does "dhcp-range" allow me to match more than one tag? or to match one (or more) and set another one? 2) when I write: # OUR PCs ## dhcp-host=00:22:33:44:55:01,192.168.1.101,net:tagIKnowYou,mycompany-PC-01 dhcp-host=00:22:33:44:55:02,192.168.1.101,net:tagIKnowYou,mycompany-PC-02 dhcp-host=00:22:33:44:55:03,192.168.1.101,net:tagIKnowYou,mycompany-PC-03 I am *setting* (and not trying to */match/*) the tag "tagIKnowYou" for these hosts, am I? Thanx a lot, Simon, for your help, and for a truly amazing piece of software that let me finally get rid of ISC's awful servers... Regards. -- Mariano Absatz - "El Baby" el.b...@gmail.com www.clueless.com.ar -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- I am a Marxist--of the Groucho tendency. Anonymous, French slogan -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- * TagZilla 0.066 * http://tagzilla.mozdev.org
Re: [Dnsmasq-discuss] Re: "dhcp-ignore = myTag, #known" was not what I thought
Brad Morgan escribió el 05/12/08 14:42: In the local wired net I'm using one class "C" network, but I have 2 different ranges (with different treatment in my firewall). I want to give IP addresses in one range only to MACs I know, and in the other range to others... Why make this more complicated that it needs to be? Make the range for the MACs you know only big enough for the MACs you know. You have to edit the file every time you add one so expand the range then. What this doesn't do is allow for non-consecutive addresses in the known range, but if you have the case where the known addresses must remain fixed per machine, then just assign addresses on each machine manually. Hi Brad, well, yes... I can do that (in fact, I'm doing this right now), but anyway, it seems to me like a workaround... How does "dhcp-ignore" works, anyway? What I'm trying to do is not possible? Thanx. -- Mariano Absatz - "El Baby" el.b...@gmail.com www.clueless.com.ar -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Dain bramaged -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- * TagZilla 0.066 * http://tagzilla.mozdev.org
[Dnsmasq-discuss] Re: "dhcp-ignore = myTag, #known" was not what I thought
Mariano Absatz escribió el 05/12/08 13:50: In the local wired net I'm using one class "C" network, but I have 2 different ranges (with different treatment in my firewall). I want to give IP addresses in one range only to MACs I know, and in the other range to others, so I wrote part of my configuration as in the file attached... in particular: Of course... I forgot to attach the sample config... here it goes... -- Mariano Absatz - "El Baby" el.b...@gmail.com www.clueless.com.ar -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Clark's Law: Sufficiently advanced cluelessness is indistinguishable from malice. J. Porter Clark (NASA), 1994 http://groups.google.com/group/alt.config/msg/595eee6098155967 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- * TagZilla 0.066 * http://tagzilla.mozdev.org ### INTERFACES ### # 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= # Or you can specify which interface _not_ to listen on #except-interface= # Or which to listen on by address (remember to include 127.0.0.1 if # you use this.) #listen-address= # 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. #ESTO YA LO PUSIMOS EN 00-options.conf #bind-interfaces # Red interna powerminds interface=eth3 ## DYNAMIC RANGES # # tagIKnowYou dhcp-range=tagIKnowYou,192.168.1.101,192.168.1.120,4h ### REJECT UNKNOWN CLIENTS IN THIS NETWORK # (see STATIC below) dhcp-ignore=tagIKnowYou,#known ## OPTIONS dhcp-option=net:tagIKnowYou,option:router,0.0.0.0 # router = this server dhcp-option=net:tagIKnowYou,option:dns-server,0.0.0.0 # dns-server = this server dhcp-option=net:tagIKnowYou,option:nis-domain,powerminds # nis-domain = samba dhcp-option=net:tagIKnowYou,option:nis-server,192.168.1.13 # nis-server = samba dhcp-option=net:tagIKnowYou,option:ntp-server,0.0.0.0 # ntp-server = this server ### tagAllTheRest # dhcp-range=tagAllTheRest,192.168.1.161,192.168.1.174,4h ## OPTIONS dhcp-option=net:tagAllTheRest,option:router,0.0.0.0 # router = this server dhcp-option=net:tagAllTheRest,option:dns-server,0.0.0.0 # dns-server = this server dhcp-option=net:tagAllTheRest,option:nis-domain,powerminds # nis-domain = samba dhcp-option=net:tagAllTheRest,option:nis-server,192.168.1.13 # nis-server = samba dhcp-option=net:tagAllTheRest,option:ntp-server,0.0.0.0 # ntp-server = this server ### STATIC # ### SERVERS ### # samba: server interno powerminds dhcp-host=00:1c:c4:c2:6b:0c,net:tagAllTheRest,192.168.1.13,samba # backupNAS: NAS local dhcp-host=00:0d:a2:02:48:7b,net:tagAllTheRest,192.168.1.29,backupNAS ### PRINTERS ## dhcp-host=00:1e:0b:e5:46:17,net:tagAllTheRest,192.168.1.7,laser1 # mfp2: impresora laser color multifuncion dhcp-host=00:18:fe:9d:17:30,net:tagAllTheRest,192.168.1.5,mfp2 # OUR PCs ## dhcp-host=00:22:33:44:55:01,192.168.1.101,net:tagIKnowYou,mycompany-PC-01 dhcp-host=00:22:33:44:55:02,192.168.1.101,net:tagIKnowYou,mycompany-PC-02 dhcp-host=00:22:33:44:55:03,192.168.1.101,net:tagIKnowYou,mycompany-PC-03
[Dnsmasq-discuss] "dhcp-ignore = myTag, #known" was not what I thought
Hi, I just discovered that I got wrong what "dhcp-ignore" does... I'll try to explain what I want and what I did and see if someone can explain me what I got wrong or, better yet, a way to do what I want :-) I'm using 2.45 (but can upgrade to 2.46 if needed). I'm using dnsmasq in a firewall with three "internal" legs (2 different wifi networks and a local wired net). In the local wired net I'm using one class "C" network, but I have 2 different ranges (with different treatment in my firewall). I want to give IP addresses in one range only to MACs I know, and in the other range to others, so I wrote part of my configuration as in the file attached... in particular: dhcp-range=tagIKnowYou,192.168.1.101,192.168.1.120,4h dhcp-ignore=tagIKnowYou,#known dhcp-range=tagAllTheRest,192.168.1.161,192.168.1.174,4h dhcp-host=00:22:33:44:55:66,192.168.1.101,net:tagIKnowYou,mycompany-PC-01 dhcp-host=00:22:33:44:55:02,192.168.1.101,net:tagIKnowYou,mycompany-PC-02 dhcp-host=00:22:33:44:55:03,192.168.1.101,net:tagIKnowYou,mycompany-PC-03 At first everything went the way I wanted... my three known PCs got their addresses from the first range (192.168.1.101, 192.168.1.102 and 192.168.1.103) and all the rest got address from the second range... But when we hook up a new computer and I didn't notice that my second range was too little, instead of rejecting the DHCPREQUEST for not having enough IPs, it gave it an IP from the first range (192.168.1.104). I thought that the line: dhcp-ignore=tagIKnowYou,#known would prevent this, but clearly I'm understanding it wrong... or I hit a bug? How should I configure my dnsmasq to prevent unknown MACs from getting an IP in the "tagIKnowYou" range? TIA. -- Mariano Absatz - "El Baby" el.b...@gmail.com www.clueless.com.ar -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Common sense is the collection of prejudices acquired by age eighteen. Albert Einstein, (attributed) US (German-born) physicist (1879 - 1955) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- * TagZilla 0.066 * http://tagzilla.mozdev.org
Re: [Dnsmasq-discuss] RFC: Split up the default configuration file
Rance Hall escribió el 22/10/08 11:59: On Tue, Oct 21, 2008 at 2:59 PM, RevRagnarok wrote: On Tue, Oct 21, 2008 at 1:53 PM, Rune Kock wrote: I find that dnsmasq's configuration file can be somewhat intimidating for newbies. There are quite a lot of options, but only a few of them are really needed for a typical newbie-setup. What about splitting the current dnsmasq.conf into 5 files: In that case you may as well have an /etc/dnsmasq.conf.d/ subdirectory with what you listed as possible names but other names being possible. That seems to be the "new way" of having configuration files so that other packages can drop their own configs into it without having to edit global files. However, I personally only use the DNS masquerade, as it was originally written for, so doesn't really matter too much to me. ;) Aaron I think I like the /etc/dnsmasq.conf.d/ approach. it makes sense that the dhcp vars and tftp vars can/should be split in different files as a way to keep things straight. For bacwards compatibility the stock /etc/dnsmasq.conf maybe should have a "configuration-directory" option and set that to /etc/dnsmasq.conf.d/ that way old configs still work as people give themselves time to migrate to the new strategy. I think it'd be a great idea to split the config file within /etc/dnsmasq.conf.d ... I did that in my installation... I created a general configuration file with user, group, log-facility, and the like, then one file for each service configuration options (dhcp, dns, tftp)... and then some (but I have a somehow weird setup)... Other thing that would be great would be to update the comments and options within the sample config file(s)... I kinda copied info from "man dnsmasq" into my files... -- Mariano Absatz - "El Baby" el.b...@gmail.com www.clueless.com.ar -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Good programming is 99% sweat and 1% coffee. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- * TagZilla 0.066 * http://tagzilla.mozdev.org
